[Yahoo-eng-team] [Bug 1301449] Re: ODL ML2 driver doesn't notify active/inactive ports

2014-04-07 Thread OpenStack Infra
Reviewed:  https://review.openstack.org/85511
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=01380b7c67ba2ef1f923d0cf4265dd2d20e31093
Submitter: Jenkins
Branch:milestone-proposed

commit 01380b7c67ba2ef1f923d0cf4265dd2d20e31093
Author: Robert Kukura kuk...@noironetworks.com
Date:   Thu Apr 3 17:01:00 2014 -0400

ML2: ODL driver sets port status

The OpenDaylight mechanism driver does not depend on an L2 agent to
plug the port. Now that nova waits for notification that the port
status is ACTIVE, the ML2 driver API is extended so that the mechanism
driver that binds a port can optionally set the port status, and the
OpenDaylight mechanism driver uses this to set the port status to
ACTIVE.

Closes-Bug: 1301449
Change-Id: I171c405f36b4f2354d9585e8ae3dfa50ddaa9a7e
(cherry picked from commit a9e3074aa9f442c2fff1ba058ac8ed585c6caa24)


** Changed in: neutron
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1301449

Title:
  ODL ML2 driver doesn't notify active/inactive ports

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  The nova-event-callback blueprint [1] implemented the notifications of
  active/down ports to Nova. Before effectively starting an instance,
  Nova compute waits for a VIF plugged notification from Neutron.

  I'm running ODL ML2 driver in a devstack using the master branch and I
  notice that the ODL driver doesn't notify back the Nova API. Hence
  with the default settings, the VM creation always fails.

  As a workaround, set the following parameters in your nova.conf:
  vif_plugging_timeout = 10
  vif_plugging_is_fatal = False

  With this configuration, I'm able to boot and connect to the instances
  but the Neutron ports are always reported as DOWN [2].

  [1] https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
  [2] http://paste.openstack.org/show/74861/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1301449/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1301449] Re: ODL ML2 driver doesn't notify active/inactive ports

2014-04-04 Thread Mark McClain
** Changed in: neutron
Milestone: juno-1 = icehouse-rc2

** No longer affects: neutron/icehouse

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1301449

Title:
  ODL ML2 driver doesn't notify active/inactive ports

Status in OpenStack Neutron (virtual network service):
  Fix Committed

Bug description:
  The nova-event-callback blueprint [1] implemented the notifications of
  active/down ports to Nova. Before effectively starting an instance,
  Nova compute waits for a VIF plugged notification from Neutron.

  I'm running ODL ML2 driver in a devstack using the master branch and I
  notice that the ODL driver doesn't notify back the Nova API. Hence
  with the default settings, the VM creation always fails.

  As a workaround, set the following parameters in your nova.conf:
  vif_plugging_timeout = 10
  vif_plugging_is_fatal = False

  With this configuration, I'm able to boot and connect to the instances
  but the Neutron ports are always reported as DOWN [2].

  [1] https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
  [2] http://paste.openstack.org/show/74861/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1301449/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp