commit f3557786e2a9f026a16d2fd3b8fa9243bc4c70a9
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/87728 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=f3557786e2a 9f026a16d2fd3b8 fa9243bc4c70a9
Committed: https:/
Submitter: Jenkins
Branch: stable/havana
commit f3557786e2a9f02 6a16d2fd3b8fa92 43bc4c70a9
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.
Conflicts: dashboard/ dashboards/ project/ instances/ tests.py dashboard/ dashboards/ project/ instances/ views.py
openstack_
openstack_
Closes-Bug: #1265032 21e7b4d05cd3b76 783f826735f 530b7792cd77491 64ae3fc663)
Change-Id: I0382fa9a4a9fff
(cherry picked from commit 715d6b822838009