Operational status for Quantum resources
The goal of this blueprint is to introduce the concept of "Operational Status" for resources managed by Quantum.
According to the decisions taken during the Essex design summit, this will be done in the following way:
- The concept of "Operational status" will be added, as an attribute, to each Quantum resource
The "Operational status" represents the current avaiability state of the network resources abstracted by the Quantum API object
The "Operational status" is a read-only attribute avaiable for each Quantum resource. Attribute name will be 'operational-
- The API will allow operations on Quantum objects regardless of its operational status. The API will not block or refuse operations on API objects.
More information on slides from the design summit:
http://
Etherpad from the design summit:
http://
Blueprint information
- Status:
- Complete
- Approver:
- dan wendlandt
- Priority:
- High
- Drafter:
- Salvatore Orlando
- Direction:
- Needs approval
- Assignee:
- Salvatore Orlando
- Definition:
- Pending Approval
- Series goal:
- Proposed for essex
- Implementation:
- Implemented
- Milestone target:
- 2012.1
- Started by
- Salvatore Orlando
- Completed by
- dan wendlandt
Related branches
Related bugs
Sprints
Whiteboard
Salvatore, I've been chatting with Anne about how to create a branch of the API-docs that correspond to a 1.1 version of the API.
Gerrit topic: https:/
Addressed by: https:/
blueprint api-operational
Addressed by: https:/
blueprint api-framework-essex
Gerrit topic: https:/