Configuration parameters should be stored in the Database

Registered by Craig Vyvial on 2014-01-31

Currently the configuration-management blueprint has the parameters stored in a json file that is loaded from the datastore version manager and used for the parameter validation.

We need to store these parameters in the database and manage it from the api or management api.

The configuration parameters will be associated with the datastore version id rather than the manager because this makes an easier reference for the database.

Blueprint information

Status:
Complete
Approver:
Michael Basnight
Priority:
Medium
Drafter:
Craig Vyvial
Direction:
Approved
Assignee:
Craig Vyvial
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Craig Vyvial on 2014-02-12
Completed by
Nikhil Manchanda on 2014-09-09

Related branches

Sprints

Whiteboard

After discussion with hub_cap, deferred to Juno - not advanced enough and not absolutely essential

Gerrit topic: https://review.openstack.org/#q,topic:bp/configuration-parameters-in-db,n,z

Addressed by: https://review.openstack.org/79850
    Datastore Configuration Parameters stored in db

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.