Quantum should either be fully optional or not optional
Bug #893466 reported by
Gabriel Hurley
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
High
|
Gabriel Hurley |
Bug Description
Right now Quantum is a code dependency for dashboard, but using having a running quantum endpoint and enabling quantum in the dashboard is not. The wiki refers to it as "quantum endpoint (optional)" which is leading to confusion.
We should either stop referring to quantum as optional and just let it be enabled/disabled as a service, or we should make it truly optional and not include it as a dependency and wrap the code imports in "try: import quantum, except ImportError" blocks so it doesn't fail if it's not installed.
Changed in horizon: | |
status: | New → Confirmed |
Changed in horizon: | |
milestone: | none → essex-3 |
importance: | Undecided → High |
Changed in horizon: | |
assignee: | nobody → Gabriel Hurley (gabriel-hurley) |
Changed in horizon: | |
milestone: | essex-3 → essex-4 |
Changed in horizon: | |
milestone: | essex-4 → 2012.1 |
Changed in horizon: | |
milestone: | 2012.1 → essex-4 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Isn't this an issue with "plugins?" (I'm using plugins to denote the panels in https:/ /github. com/openstack/ horizon/ tree/master/ horizon/ horizon/ dashboards/ nova
Should dashboard be able:
* have plugins that can be disabled/enabled (via a UI like jenkins or a conf file)
* if a plugin doesn't load, it should marked as disabled and the admin can see the traceback
As folks add support for more projects, having this might be valuable