An abstraction for datastores with respect to start/stop/status and control

Registered by Amrith Kumar on 2014-03-20

Currently the mechanism for the guest agent to start/stop/interrogate and control the data store is implemented in an abstraction that does not best reflect the needs of each data store. This blue print (wiki page to follow) will describe an abstraction that will address this. At issue is the fact that each data store is slightly different and the current implementation runs the risk of unexpected side-effects.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Amrith Kumar
Direction:
Needs approval
Assignee:
Amrith Kumar
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Amrith Kumar on 2016-01-15

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.