loading configuration parameters from trove-manage better

[Craig Vyvial]

Loading the configuration parameters from the trove-manage command requires the version uuid to be passed in. I have found over the last couple days that this is extremely inconvenient. We should allow someone to pass in the datastore name and version name and look up the version uuid by these.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/122517

[Amrith Kumar (amrith)]

Craig, what's the importance of this, in your opinion as the person who reported this and is assigned as the person who will be fixing it. I'm confused by previous update that considers it at once Critical and then Low.

[Denis M. (dmakogon)]

First i marked thi bug as 'critical' by the mistake (bad touchpad), and then, immediately, i fixed this it by marking bug as 'low'. Let me explain why, for the person who's doing bug-report reviews when i don't see any stack traces but the description only i'm trying to look up over the code to find place when it doesn't behave as it should be (or fails). If it works, but can become more advanced - automatically this bug becomes low-priority among existing ones, because it doesn't affect main functionality.

[Craig Vyvial (cp16net)]

This bug is to make your life better when working with the trove-manage command because you will likely not want to look up the uuid of the datastore version that you want to load up these configuration parameters.

I learned after writing this a couple times it was a terrible idea since you should already know the names of the datastore and version you want.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/122517
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=518dd2f64743c369451f5cd1fb1ef6f6606acff9
Submitter: Jenkins
Branch: master

commit 518dd2f64743c369451f5cd1fb1ef6f6606acff9
Author: Craig Vyvial <email address hidden>
Date: Thu Sep 18 15:10:24 2014 -0500

    loading configuration parameters from trove-manage better

    It is a pain to load the configuration parameters when setting up
    a new environment. Since theres no way to get the uuid of the
    datastore version that is created you must get it by looking in
    the database.

    Closes-Bug: #1371297
    Change-Id: If8cea0aaf38878bb04abe6e27b9bfd77d5684bce