Additional state field for ops
With the OS API 1.1 spec almost complete, the current OS API has fields that do not map to any state in the spec. Fields such as 'shutoff' and 'shutdown' are not valid states.
DPrince has mapped some of the issues here. http://
I am proposing another column that would represent actual state of the VM that could get polled to return the state of the VM and the current 'state' column in the instances table would reflect what I think of as the billing status of the vm. The state of the vm would be in 'active' as long as it isn't doing another operation defined in the spec. Shutdown/Shutoff would not be returned from the api 'state' field. The 'state' field should reflect the allowed states with the api 1.1 spec. The additional field could be exposed via an admin api call to represent state transitions more granularly (migration steps between hosts, status of snaps to swift, etc).
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Undefined
- Drafter:
- Paul Voccio
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Vish Ishaya
- Completed by
- Vish Ishaya