Datastore types and versions
Datastore types management will allow users of Trove to select database type and version on db engine from the list provided by operator. Operator will have possibility to control datastore types, add new and deactivate old versions.
To implement this capability users can specify datastore type and optional version of engine on instance create.
Datastore Type is a family of database engines, like mysql, mongodb, cassandra.
Datastore Version defines engine version of selected datastore type and contains list of system packages which provides this datastore.
Blueprint information
- Status:
- Complete
- Approver:
- Michael Basnight
- Priority:
- High
- Drafter:
- Daniel Morris
- Direction:
- Approved
- Assignee:
- Andrey Shestakov
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
- Implemented
- Milestone target:
- 2014.1
- Started by
- Andrey Shestakov
- Completed by
- Andrey Shestakov
Related branches
Related bugs
Sprints
Whiteboard
Couple of thoughts:
1. Do we need to add "status": "UNSUPPORTED" -- will we actually be listing unsupported DB Types?
<dem>
The thought here is that imagine a provider wants to introduce a new database type for test/dev. They may want to have customers be able to provision it, but the provider does not want to support it with their SLA. A good example of this would be MySQL 5.6. It just GA'ed within the last two weeks. You might want to make that package available, but it might be another 6 months to a year before a provider would want to support it fully with backups, monitoring, replication, etc. I am open to tweaking the status types if need be.
</dem>
2. "typeRef": ""href": "https:/
<dem>
In this case, typeRef would be an optional parameter so it would not break backwards compatibility. If you do not specify a typeRef, then it will choose the type that has DEFAULT
.</dem>
Gerrit topic: https:/
Addressed by: https:/
Support service types
Work Items
Dependency tree
* Blueprints in grey have been implemented.