Notify nova when ports are ready
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Undecided
|
Gauvain Pocentek |
Bug Description
https:/
commit 827cc5170546e88
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_
Neutron will then signal nova: network_
will either be 'completed' or 'failed' given the neutron port status.
Neutron also notifies nova when a port goes from status:
PORT_
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_
in neutron to prevent neutron from sending the notification and setting:
vif_
interaction where an instance will be booted without waiting for the network
to be ready.
DocImpact
implements blueprint: nova-event-callback
Change-Id: I4177124485b986
Changed in openstack-manuals: | |
status: | New → Confirmed |
tags: | added: config-reference |
Fix proposed to branch: master /review. openstack. org/81013
Review: https:/