disabling datastores is too complicated

Bug #1613376 reported by Matt Fischer
10
This bug affects 2 people
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_version_update [-h]
                                             datastore version_name manager
                                             image_id packages active

[DEV] root@bfd02-trove-001:# trove-manage datastore_version_update mysql 5.6-108 mysql 684981ab-b614-439d-98a4-e4d5fe498b69 mysql 0
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.

Amrith Kumar (amrith)
Changed in trove:
status: New → Confirmed
importance: Undecided → Medium
Amrith Kumar (amrith)
Changed in trove:
assignee: nobody → Amrith (amrith)
Amrith Kumar (amrith)
Changed in trove:
assignee: Amrith Kumar (amrith) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.