Re: [openstack-dev] [Magnum] Proposed Changes to Magnum Core
Jay has been rockin. +1 from me ! Regards -steve On 01/02/2015 04:59 PM, Adrian Otto wrote: Magnum Cores, I propose the following addition to the Magnum Core group[1]: + Jay Lau (jay-lau-513) Please let me know your votes by replying to this message. Thanks, Adrian [1] https://review.openstack.org/#/admin/groups/473,members Current Members ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa] Using DevStack for multi-node setup
Hi, I’m using DevStack to deploy OpenStack on a multi-node setup: Controller, Network, Compute as 3 separate nodes Since the Controller node is stacked first, during which the Network node is not yet ready, it fails to create the router instance and the public network. Both have to be created manually. Is this the expected behavior? Is there a workaround to have DevStack create them? Thanks, Danny ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][L2-Gateway] Meetings announcement
Sukhdev, Since the term is quite broad and has meant many things in the past, can you define what you're thinking of when you say 'L2 gateway'? Cheers, -- Ian. On 2 January 2015 at 18:28, Sukhdev Kapur sukhdevka...@gmail.com wrote: Hi all, HAPPY NEW YEAR. Starting Monday (Jan 5th, 2015) we will be kicking of bi-weekly meetings for L2 Gateway discussions. We are hoping to come up with an initial version of L2 Gateway API in Kilo cycle. The intent of these bi-weekly meetings is to discuss issues related to L2 Gateway API. Anybody interested in this topic is invited to join us in these meetings and share your wisdom with the similar minded members. Here is the details of these meetings: https://wiki.openstack.org/wiki/Meetings#Networking_L2_Gateway_meeting I have put together a wiki for this project. Next week is the initial meeting and the agenda is pretty much open. We will give introduction of the members of the team as well the progress made so far on this topic. If you would like to add anything to the agenda, feel free to update the agenda at the following wiki: https://wiki.openstack.org/wiki/Meetings/L2Gateway Look forward to on the IRC. -Sukhdev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][stable] pep8 busted on stable/juno?
On 1/1/2015 11:16 PM, Matt Riedemann wrote: Is it just me or is stable/juno pep8 busted? mriedem@ubuntu:~/git/nova$ git checkout stable/juno Switched to branch 'stable/juno' Your branch is up-to-date with 'origin/stable/juno'. mriedem@ubuntu:~/git/nova$ tox -r -e pep8 pep8 recreate: /home/mriedem/git/nova/.tox/pep8 pep8 installdeps: -r/home/mriedem/git/nova/requirements.txt, -r/home/mriedem/git/nova/test-requirements.txt pep8 develop-inst: /home/mriedem/git/nova pep8 runtests: PYTHONHASHSEED='0' pep8 runtests: commands[0] | flake8 ./nova/tests/compute/test_resources.py:30:1: H302 import only modules.'from nova.tests.fake_instance import fake_instance_obj' does not import a module ./nova/tests/compute/test_rpcapi.py:31:1: H302 import only modules.'from nova.tests.fake_instance import fake_instance_obj' does not import a module ERROR: InvocationError: '/home/mriedem/git/nova/.tox/pep8/bin/flake8' ___ summary ___ ERROR: pep8: commands failed mriedem@ubuntu:~/git/nova$ Here is the cherry pick fix: https://review.openstack.org/#/c/144760/ -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron][qa] need some eyes on new(ish) gate bug 1407190
https://bugs.launchpad.net/neutron/+bug/1407190 Looks like this started on 12/29. I checked the neutron commits around that time and there are some related to ports/interfaces and openvswitch but I'm not sure that they contributing to this issue. I've put a bunch of notes and log links in the bug report, basically there is a race in a tempest test where it creates a server and adds two ports to it (so a total of three), it waits for each port to be ACTIVE before continuing, and then does a show port call by port ID and server ID and expects the port to be the same as what it originally created. When this fails, the expected port_status is 'ACTIVE' but the actual port_status is 'BUILD'. I've found in the logs where nova/neutron are seeing the port going to 'BUILD' state but I don't know enough about the neutron code to tell what actually triggers this change, the only place I see 'BUILD' used is in the nova event notifier code in neutron which is related to the vif plug/unplug callback on nova server boot. This isn't the top gate bug, but it's got a significant number of hits and seems like something that we should be able to reasonably get a quick handle on given I think we know when it started (12/29 according to logstash, I caught it before the 10 day index in logstash passed). -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
