trove-manage db_load_datastore_config_parameters will fail if
the datastore_version on which it's being run is marked as
inactive (aka active is set to 0).
this is not correct, because it's completely reasonable to want
to update/refresh a datastore_version's configuration-group's
parameters even if it's inactive.
examples:
- you're working on rolling out a new datastore_version, so
you have it marked as active=0 until the go-live date.
- you've rolled out a new datastore_version and want to
mark the old version as inactive. instances built prior
to the inactivation are still on the old version, and
can still utilize their still-assigned configuration-groups,
hence the parameters should be updateable by the
administrator.
Reviewed: https:/ /review. openstack. org/129145 /git.openstack. org/cgit/ openstack/ trove/commit/ ?id=7d26dfe906f 3509c48fa7a1404 8e742c6d7268cb
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7d26dfe906f3509 c48fa7a14048e74 2c6d7268cb
Author: amcrn <email address hidden>
Date: Thu Oct 16 23:14:20 2014 -0700
Config Group Load Fails If DS Version Inactive
trove-manage db_load_ datastore_ config_ parameters will fail if
the datastore_version on which it's being run is marked as
inactive (aka active is set to 0).
this is not correct, because it's completely reasonable to want group's
to update/refresh a datastore_version's configuration-
parameters even if it's inactive.
examples: groups, ator.
- you're working on rolling out a new datastore_version, so
you have it marked as active=0 until the go-live date.
- you've rolled out a new datastore_version and want to
mark the old version as inactive. instances built prior
to the inactivation are still on the old version, and
can still utilize their still-assigned configuration-
hence the parameters should be updateable by the
administr
Change-Id: I7682fe240c5737 438b084d813cf7c e80b4ecca9b
Closes-Bug: #1379563