network topology order
Bug #1234950 reported by
Kevin Fox
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Wishlist
|
Aleš Křivák |
Bug Description
Often when three or more networks are involved, with one external, one internal attached to a router which is attached to external (aka tenant public), and one or more backend networks the view often (always?) displays in the following order:
external, private backend*, tenant public
This causes the display to look very backwards to what one might expect and lines to cross that would not normally need to.
A more intuative ordering would be:
external networks, tenant networks attached to routers attached to external networks, tenant networks with no routers.
Thanks,
Kevin
Changed in horizon: | |
importance: | Undecided → Medium |
milestone: | none → icehouse-1 |
status: | New → Confirmed |
tags: | added: topology-view |
Changed in horizon: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in horizon: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in horizon: | |
milestone: | icehouse-3 → icehouse-rc1 |
Changed in horizon: | |
milestone: | icehouse-rc1 → next |
Changed in horizon: | |
milestone: | juno-3 → juno-rc1 |
Changed in horizon: | |
milestone: | juno-rc1 → next |
Changed in horizon: | |
assignee: | Facundo Farias (facundo-farias) → Aleš Křivák (aleskrivak) |
Changed in horizon: | |
status: | In Progress → Fix Released |
Changed in horizon: | |
milestone: | next → none |
To post a comment you must log in.
I have a patch to fix this now, but I'm trying to get it through legal. The openstack contributor agreement is proving to be a challenge.