OpenStack Compute (nova)

remove-periodic-heal-network

Registered by Aaron Rosen

Currently nova returns cached data for network resources. This is annoying for users because if you associate a floating ip via the neutron api it could take a very long time for the cache to be updated with the floatingip that the instance has. Instead of reading these values from the cache it would make sense to query neutron directly. Doing this would allow us to remove the constant polling that all of the nova-compute nodes do on neutron to update their cache.

Note: we'll still need the network cache to keep track of nic ordering on the instance (and update it when new interfaces are added and removed).

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Aaron Rosen
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

I'm familiar with the problems you want to solve here, however going direct to the neutron API is not a scalable solution until things like: https://bugs.launchpad.net/neutron/+bug/1214115 and https://blueprints.launchpad.net/neutron/+spec/instance-nw-info-api are addressed. I would much prefer to see a method to mark nova's cache as dirty instead of just ignoring it completely. --geekinutah

Sounds like this should move to the openstack-dev list. Please post a link to the thread on this blueprint once you start it. --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
I'm familiar with the problems you want to solve here, however going direct to the neutron API is not a scalable solution until things like: https://bugs.launchpad.net/neutron/+bug/1214115 and https://blueprints.launchpad.net/neutron/+spec/instance-nw-info-api are addressed. I would much prefer to see a method to mark nova's cache as dirty instead of just ignoring it completely. --geekinutah

Sounds like this should move to the openstack-dev list. Please post a link to the thread on this blueprint once you start it. --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.