Previously when a user accesses the network topology panel
horizon resolves VM console URL when returning server data.
This requires one API call to nova per VM, and this causes
a scaling issue.
Actually there is no need to resolves VM console URL when
the network topology. A console URL corresponding to a requested
VM can be resolved when a user actually accesses a console.
This reduces the number of API calls drastically and addresses
the scaling issue reported in the bug report.
Change-Id: Icc667449e2988e6227012a6e899835a97ce0d738
Closes-Bug: #1723142
(cherry picked from commit 974f0418efdf171132747ded4a556df7b7af03d1)
Reviewed: https:/ /review. openstack. org/529052 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=4906c986b57 eea9b53e5b0f600 6917c72fb5fcc0
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 4906c986b57eea9 b53e5b0f6006917 c72fb5fcc0
Author: Akihiro Motoki <email address hidden>
Date: Thu Nov 30 20:45:07 2017 +0900
Redirect VM console dynamically
Previously when a user accesses the network topology panel
horizon resolves VM console URL when returning server data.
This requires one API call to nova per VM, and this causes
a scaling issue.
Actually there is no need to resolves VM console URL when
the network topology. A console URL corresponding to a requested
VM can be resolved when a user actually accesses a console.
This reduces the number of API calls drastically and addresses
the scaling issue reported in the bug report.
Change-Id: Icc667449e2988e 6227012a6e89983 5a97ce0d738 132747ded4a556d f7b7af03d1)
Closes-Bug: #1723142
(cherry picked from commit 974f0418efdf171