May 2015 - dev - Rdo List Archives

[Rdo-list] neutron added python-six build dependency

by Ihar Hrachyshka

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, neutron just added [1] a new 'six' dependency to be able to build a source tarball. Now, delorean/kilo crashes [2] (it seems it crashes for CentOS only. I suspect python-six is available in default Fedora image, that's why). It goes like this: - - sdist rebuild tries to parse setup.cfg - - setup.cfg has a hook to import inside neutron.* - - since [1] adds a six library usage into neutron/__init__.py, sdist call now fails. I wonder what's the best way to handle it? From one side, it's probably the easiest to add python-six build dependency to neutron packages. From the other side, it's not really a neutron dependency but a delorean+neutron one. Building from tarballs should not need it. [1]: https://review.openstack.org/#/c/181277/ [2]: http://trunk.rdoproject.org/centos70/96/09/96091cb976e5f858fcd53fb079855 5020eac94b8_33cfff38/rpmbuild.log Comments? Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVUi+CAAoJEC5aWaUY1u570EAIAJPzfMrccMyykY/rnbAfhsNb 5E6KKYIpUuKKl6aodNQjxQtG6fhn5KzbNwknXrvA6saDjxWnELFX7SAjb0Y4ntma hsFnZOwSpjp0jPeFwOiVWNou2gX9W9q7u6hfBhGEY7TDhZ+w8bJ/fgtK8RHwdRXi CnVCR13cyWmqqa81atMTxBZH88JybePUtPgr1nYONRbWolwgj4R/j1oQodlCp8At 01oU69w3pggMdh0/95lnA3UMH2DfxPFXoA1bjPHjtHpuJdkr+tgDOd/CASMknMBk rQ4hE5+sSIt4+g95ju/B/fR7nSmmholwQwtLszaeGS5cDWzDXTMQ/f1+EKusHtU= =9HoC -----END PGP SIGNATURE-----

9 years, 6 months

2
3
0 / 0

[Rdo-list] nova.conf.sample doesn't include all options available

by Belmiro Moreira

Hi, In RDO nova (2014.2.2) the "nova.conf.sample" doesn't include the [database] configuration group. Any reason to not have it? It would help deployers if nova.conf.sample has all configuration options available. Some options of [database] configuration group are included in nova-dist.conf, though. thanks, Belmiro

9 years, 6 months

2
1
0 / 0

[Rdo-list] Moving Docs builds of RDO-Manager

by Jaromir Coufal

Hi Ben, I wanted to sync with you if we could coordinate the movement of documentation from: https://repos.fedorapeople.org/repos/openstack-m/instack-undercloud/* to: https://repos.fedorapeople.org/repos/openstack-m/docs/* with following sub-directories: * ../docs/master * ../docs/sprint4 * ../docs/sprint5 (doesn't exist yet) etc. Since we don't have any date for testing day yet, I think we can do it this week. For old sites, I don't think that we can somehow control redirects, so I would suggest to place there temporary index.html file with information that docs moved and direct people to new location (example: http://paste.openstack.org/show/215975/). Thanks -- Jarda

9 years, 6 months

2
4
0 / 0

[Rdo-list] Test day: Thanks, and bugs

by Rich Bowen

Thank you so much to everyone that participated in the test days. It looks like 24 tickets were opened - http://tm3.org/testdaybugs - as well as a few that have already been closed. -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

9 years, 6 months

3
2
0 / 0

[Rdo-list] packaging lifecycles

by Jeff Weber

Is there any documentation which describes the packaging lifecycles for RDO packages? I'm currently using the Juno el-7 packages, and was curious since kilo is coming out now if updates will stop being built there. The 2014.2.3 update has been out for a bit, but I wasn't able to find where if anywhere this might be in the pipeline for update. What is the lifecycle for these kinds of updates? Do you just follow upstream for releases and EOL or stop once a new release is available? Is it possible to get involved with helping on older releases which aren't EOL but don't have updates if they're not normally going to be done?

9 years, 6 months

6
8
0 / 0

[Rdo-list] [RDO] RDO blog roundup, May 11, 2015

by RDO Forum

rbowen started a discussion. RDO blog roundup, May 11, 2015 --- Follow the link below to check it out: https://www.rdoproject.org/forum/discussion/1015/rdo-blog-roundup-may-11-... Have a great day!

9 years, 6 months

4
4
0 / 0

[Rdo-list] OpenStack Meetups, week of May 11, 2015

by Rich Bowen

The following are the meetups I'm aware of in the coming week where OpenStack and/or RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://rdoproject.org/Events If there's a meetup in your area, please consider attending. If you attend, please consider taking a few photos, and possibly even writing up a brief summary of what was covered. --Rich * Tue May 12 in Beijing, CN: 2015 China OpenStack 企业就绪论坛 - http://www.meetup.com/China-OpenStack-User-Group/events/221992827/ * Tue May 12 in Taipei, TW: 只要你對OpenStack有興趣都歡迎來參加 - http://www.meetup.com/Taipei-OpenCloud-Meetup/events/222348949/ * Tue May 12 in Taipei, TW: OpenStack Taiwan User group meetup - http://www.meetup.com/OpenStack-Taiwan-User-Group/events/222363618/ * Tue May 12 in Athens, GR: High Availability in OpenStack - http://www.meetup.com/Athens-OpenStack-User-Group/events/222128761/ * Tue May 12 in Washington, DC, US: Ceph at Comcast - http://www.meetup.com/Ceph-DC/events/221843869/ * Wed May 13 in Vancouver, BC, CA: OpenStack cloud management platform + demo - http://www.meetup.com/Vancouver-OpenStack-Meetup/events/222400382/ * Wed May 13 in Berlin, DE: Heading for Vancouver - http://www.meetup.com/OpenStack-User-Group-Berlin/events/221817807/ * Wed May 13 in Buenos Aires, AR: OpenStack hands on - http://www.meetup.com/openstack-argentina/events/222305435/ * Wed May 13 in Porto Alegre, BR: 2º Hangout OpenStack Brasil 2015 - http://www.meetup.com/Openstack-Brasil/events/222182172/ * Thu May 14 in Budapest, HU: OpenStack 2015 May - http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/222396966/ * Thu May 14 in Singapore, SG: Singapore OpenStack UG meetup - http://www.meetup.com/OpenStack-Singapore/events/221538390/ -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

9 years, 6 months

1
0
0 / 0

[Rdo-list] rdo-manager now using openstack-puppet-modules

by James Slagle

Hi, I just wanted to make everyone aware that rdo-manager is now using openstack-puppet-modules[0] instead of git cloning from github. Please keep this in mind if you're expecting to see updates to the puppet modules...those updates will need to make their way into openstack-puppet-modules before they're available to rdo-manager. The change will be live shortly once the current-passed-ci symlink is updated[1]. We're pulling o-p-m from delorean kilo[2] currently. [0] https://review.gerrithub.io/#/c/232065/ [1] http://trunk-mgt.rdoproject.org/repos/current-passed-ci/ [2] http://trunk.rdoproject.org/kilo/centos7/latest-RDO-kilo-CI/ -- -- James Slagle --

9 years, 6 months

1
0
0 / 0

[Rdo-list] [Fedocal] Reminder meeting : RDO packaging meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO packaging meeting on 2015-05-13 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO packaging irc meeting ([agenda](https://etherpad.openstack.org/p/RDO-Packaging)) Every week on #rdo on freenode Source: https://apps.fedoraproject.org/calendar/meeting/2017/

9 years, 6 months

1
0
0 / 0

[Rdo-list] Defects in Kilo RC2 Packaging

by Steven Dake (stdake)

Hi, I recently ported Kolla (OpenStack running in containers – http://github.com/stackforge/kolla) and found the following defects: 1. Glance has missing dependencies in its package Specifically +RUN yum -y install openstack-glance python-oslo-log python-oslo-policy && yum clean all Is needed to get glance to operate. Oslo-log and oslo-policy should be added to the dependencies. You wouldn¹t notice this on an AIO install because other packages probably have those packages as dependencies. 2. Neutron for whatever reason depends on a file fwwas_driver.ini which has been removed from the master of neutron. But the agents will exit if its not in the config directory. I used juno¹s version of fwaas_driver.ini to get the agents to stop exiting. 3. The file dnsmasq-neutron.conf is misconfigured in the default installation. This causes the neutron agents to exit. I delete the file during docker build which fixes the problem. I¹m not sure what this config file is supposed to look like. 4. A critical bug was found in both Juno and Kilo versions of nova. If I launch approximately 20 Vms via a heat resource group with floating ips, only about 7 of the Vms get ports assigned. The others do get their ports assigned because they can access dhcp and metadata server, so their networking is operational. Neutron port-list shows their ports are active. However nova-list does not show their IPs from the instance info cache. My only workaround to this problem is to run the icehouse version of nova (api, conductor, scheduler, compute) which works perfectly. I have filed a bug with a 100% reliable easy to use reproducer and more details and logs here: https://bugzilla.redhat.com/show_bug.cgi?id=1213547 Interestingly in my informal tests icehouse nova is about 4x faster at placing Vms in the active state as compared to juno or kilo, so that may need some attention as well. Just watching top, it appears neutron-server is much busier (~35% cpu utilization of 1 core during the entire ->ACTIVE process) with the juno/kilo releases. Note I spent about 7 days trying to debug this problem but the code literally calls IP assignments in about 40 different places in the code base, including exchanges over RPC and python-neutronclient, so it is very difficult to track. I would appreciate finding a nova expert to debug the problem further. Other than those problems, RDO Kilo RC2 looks spectacular and works perfectly in my dead chicken testing. Nice job guys! Regards -steve

9 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev May 2015