Add vendor extensible framework in valence

Registered by Anusha on 2017-06-01

As valence is a controller for managing dis aggregated hardware, this blueprint is to add extensible framework inside valence to provide provision for the vendors who would like to manage the dis aggregated hardware through valence , but doesn't support redfish.

Blueprint information

Status:
Complete
Approver:
Mrittika Ganguli
Priority:
Undefined
Drafter:
Anusha
Direction:
Needs approval
Assignee:
Anusha
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Anusha on 2017-12-05
Completed by
Anusha on 2018-01-12

Related branches

Sprints

Whiteboard

Please add a short diagram of how Valence will call a layer which is not redfish..

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-vendor-extensible-framework,n,z

Addressed by: https://review.openstack.org/486970
    Add 'type' to podmanager DB

Addressed by: https://review.openstack.org/492103
    Add manager.py to redirect to respective podmanager

Addressed by: https://review.openstack.org/498734
    Update Node controller to make it generic

Addressed by: https://review.openstack.org/499468
    Update podmanager controller to use generic interface

Addressed by: https://review.openstack.org/501973
    Update Rack and Systems controller to be generic

Addressed by: https://review.openstack.org/505488
    Modify Ironic driver to support multi-podm arch

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-device-orchestration,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.