Datastore type manager move to the Datastore version manger

Registered by Craig Vyvial on 2013-12-18

A datastore version should have a manager associate with it rather than the datastore type. There is nothing on a datastore version to key off of for the validation rules of configurations. We were using the datastore type manager. This is something that is specific to the setup of the system and if we move the datastore manager to the datastore version manager then we can have "shared" managers as well as a custom manager if someone so desired. This will allow for more flexibility in deployments and validations.

This is how it looks today to setup a datastore:

datastore_update MySQL mysql ""
datastore_version_update MySQL "5.5" $IMAGE_ID "mysql-server-5.5" 1
datastore_version_update MySQL "5.6" $IMAGE_ID "mysql-server-5.6" 1

This would change to:

datastore_update MySQL ""
datastore_version_update MySQL "5.5" mysql $IMAGE_ID "mysql-server-5.5" 1
datastore_version_update MySQL "5.6" mysql $IMAGE_ID "mysql-server-5.6" 1
(where "mysql" is the name of the manager)

enabling you in the future to do something like:

datastore_version_update MySQL "5.7" mysql57 $IMAGE_ID "mysql-server-5.7" 1

Blueprint information

Status:
Complete
Approver:
Michael Basnight
Priority:
Medium
Drafter:
Craig Vyvial
Direction:
Approved
Assignee:
Craig Vyvial
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Craig Vyvial on 2013-12-18
Completed by
Michael Basnight on 2014-01-21

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/move-manager-to-datastore-version,n,z

Addressed by: https://review.openstack.org/63289
    move datastore manager to the datastore version

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.