Trove refactoring for better pluggability

Registered by Denis M. on 2013-09-02

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:
milestone icon ongoing
Completed by
Nikhil Manchanda on 2014-04-16

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.