commit 715d6b822838009530b7792cd7749164ae3fc663
Author: Assaf Muller <email address hidden>
Date: Sun Dec 29 16:44:46 2013 +0200
Get instance networking information from Neutron
project/instances, admin/instances and the instance details page
all get networking information from Nova. However, with Neutron
enabled, floating IP associations are done direcly with Neutron,
meaning that Nova's DB will fall out of sync and thus the GUI
won't reflect successful floating IP associations until Nova
polls Neutron again and updates its DB. The polling can take
up to several minutes to complete for consecutive floating IP
operations.
The solution is to update instances' networking information from
Neutron immediately after the call to list Nova instances.
Reviewed: https:/ /review. openstack. org/64448 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=715d6b82283 8009530b7792cd7 749164ae3fc663
Committed: https:/
Submitter: Jenkins
Branch: master
commit 715d6b822838009 530b7792cd77491 64ae3fc663
Author: Assaf Muller <email address hidden>
Date: Sun Dec 29 16:44:46 2013 +0200
Get instance networking information from Neutron
project/ instances, admin/instances and the instance details page
all get networking information from Nova. However, with Neutron
enabled, floating IP associations are done direcly with Neutron,
meaning that Nova's DB will fall out of sync and thus the GUI
won't reflect successful floating IP associations until Nova
polls Neutron again and updates its DB. The polling can take
up to several minutes to complete for consecutive floating IP
operations.
The solution is to update instances' networking information from
Neutron immediately after the call to list Nova instances.
Closes-Bug: #1265032 21e7b4d05cd3b76 783f826735f
Change-Id: I0382fa9a4a9fff