Eliminate usage of oslo.cfg dependency

Registered by Joshua Harlow on 2013-09-07

In order to not depend on oslo.cfg and force users of taskflow into using the *global* oslo.cfg 'model'. Instead we should make sure that as a library any configuration we depend on can be provided by simple objects to whatever is going to use that configuration. This will ensure a easier transition to an oslo sub-library (if and when that occurs).

Releavant discussion: http://openstack.10931.n7.nabble.com/Oslo-db-Configuration-options-td18075.html#a18089

Blueprint information

Status:
Complete
Approver:
Joshua Harlow
Priority:
High
Drafter:
Joshua Harlow
Direction:
Approved
Assignee:
Joshua Harlow
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Joshua Harlow on 2013-09-12
Completed by
Joshua Harlow on 2013-09-12

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/eliminate-oslo-cfg,n,z

Addressed by: https://review.openstack.org/45553
    Move toward using a storage engine model

Addressed by: https://review.openstack.org/45746
    Remove the common config since its not needed

Addressed by: https://review.openstack.org/45770
    Remove usage of oslo.db and oslo.config

Gerrit topic: https://review.openstack.org/#q,topic:storage-checks,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.