Notify nova when ports are ready

Bug #1292317 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Undecided
Gauvain Pocentek

Bug Description

https://review.openstack.org/75253
commit 827cc5170546e88e5c4ab721f69b8501371e3948
Author: Aaron Rosen <email address hidden>
Date: Thu Feb 20 16:18:11 2014 -0800

    Notify nova when ports are ready

    The following patch adds a callback from neutron to nova that notifies nova
    when a port for an instance is *ready to be used*. After nova receives this
    event it will then start the instance in a hope that when it comes up
    its networking should be in working order.

    NOTE: *ready to be used* currently means that a plugin changes the status
    in the db associated with a port from:
    NO_VALUE/PORT_STATUS_DOWN/PORT_STATUS_ACTIVE to ACTIVE/ERROR.

    Neutron will then signal nova: network_vif_plugged:<status> where status
    will either be 'completed' or 'failed' given the neutron port status.

    Neutron also notifies nova when a port goes from status:
    PORT_STATUS_ACTIVE to PORT_STATUS_DOWN and sends nova a network_vif_unplugged
    event.

    Currently this patch breaks multiregion support (i.e previously you could
    back multiple nova regions by one neutron server) though now since neutron
    needs to notify nova we'll need to add a way to determine which region a
    given port is in.

    For now the work around for this would be to set: notify_nova_port_active=False
    in neutron to prevent neutron from sending the notification and setting:
    vif_plugging_is_fatal=False in nova.conf. Doing this will keep the current
    interaction where an instance will be booted without waiting for the network
    to be ready.

    DocImpact

    implements blueprint: nova-event-callback

    Change-Id: I4177124485b986706fcf8e73b928024b5d82b822

Changed in openstack-manuals:
status: New → Confirmed
tags: added: config-reference
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/81013

Changed in openstack-manuals:
assignee: nobody → Gauvain Pocentek (gpocentek)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/81013
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=bb9d38971d164b27843014d8fea4f30033a788ae
Submitter: Jenkins
Branch: master

commit bb9d38971d164b27843014d8fea4f30033a788ae
Author: Gauvain Pocentek <email address hidden>
Date: Mon Mar 17 17:45:49 2014 +0100

    Update flags and tables for neutron

    Remove unneeded xi:include (metadata agent is not a plug-in)

    Provide tables for new plugins and ML2 mechanisms

    To avoid breaking the large tables appearance by using xrefs, the
    bigswitch table is generated twice (one table for the ML2 mechanism, one
    table for the standalone plugin). This is a (hopefully) temporary
    change. Tables generations will probably be updated in Juno.

    Change-Id: I27573975c83c5b25682135a4ea3ab852fec170ea
    Closes-Bug: #1291785
    Closes-Bug: #1292317
    Closes-Bug: #1292318
    Closes-Bug: #1294402
    Closes-Bug: #1294405
    Closes-Bug: #1294961

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.