Trove refactoring for better pluggability
Registered by
Denis M.
Trove as a project should be refactored for better module reusage and possibility for injecting new service types without causing any harm to default project structure.
It is criticaly important to current project, because of trove is almost hard-coded to deploy mysql/percona databases, it means that there is any chance to extend provisioning and managing instances with another (not hard-coded) service-types.
Blueprint information
- Status:
- Complete
- Approver:
- Michael Basnight
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Denis M.
- Definition:
- Obsolete
- Series goal:
- Proposed for future
- Implementation:
- Unknown
- Milestone target:
- ongoing
- Started by
- Completed by
- Nikhil Manchanda
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Trove instance model refactoring
(?)