manila-ui setup things should be defined in its own devstack plugin
Bug #1540369 reported by
Valeriy Ponomaryov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Shared File Systems Service (Manila) |
Invalid
|
Low
|
Unassigned | ||
| manila-ui |
Invalid
|
Low
|
Unassigned | ||
Bug Description
For the moment all actions that are required for Manila UI installation using devstack are done in Manila project. But it is incorrect and we should use "devstack plugin" approach for it in Manila UI project. And in Manila we should just enable/disable it.
| tags: | added: devstack manila-ui |
| Changed in manila: | |
| importance: | Undecided → Low |
| description: | updated |
| Changed in manila: | |
| assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
| description: | updated |
| Changed in manila-ui: | |
| importance: | Undecided → Low |
| assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
| Changed in manila: | |
| assignee: | Valeriy Ponomaryov (vponomaryov) → nobody |
| Changed in manila-ui: | |
| assignee: | Valeriy Ponomaryov (vponomaryov) → nobody |
| Changed in manila: | |
| milestone: | none → newton-1 |
Revision history for this message
| Tom Barron (tpb) wrote | #1 |
| Changed in manila: | |
| status: | New → Invalid |
| Changed in manila-ui: | |
| status: | New → Invalid |
| Changed in manila: | |
| milestone: | newton-1 → none |
To post a comment you must log in.
I don't think there is any longer a valid issue here. manila-ui plugin is independently is toggled in local.conf independently of manila - plugging in manila in devstack no longer enables manila-ui by default.