disabling datastores is too complicated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Scenario: You've pulled in some new datastores and want to disable the old ones so that users are using the newest versions of the databases.
All you want to do is say "Disable mysql 5.6.108". This requires this arcane and complex trove-manage command:
usage: trove-manage datastore_
[DEV] root@bfd02-
Datastore version '5.6-108' updated.
manager - why?
image_id - double why?
packages - why?
All that seems to be needed is "mysql 5.6-108 0 (disabled)". Everything is just makes using the tool more complicated.
Changed in trove: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in trove: | |
assignee: | nobody → Amrith (amrith) |
Changed in trove: | |
assignee: | Amrith Kumar (amrith) → nobody |