API: get the status of a locked instance
Currently we only support locking/unlocking an instance but we are not able
to query whether the instance is locked or not.
This proposal is to add the lock status to the detailed view of an instance.
Add following output to the response body of
GET /v2/45210fba73d
servers/
Following lock info will be added in addition to
existing output info.
+------
| Parameter | Type | Description |
+======
| locked | boolean | whether the instance is locked |
+------
| locked_by | string | User locked the instance, current |
| | | valid value are 'admin' and 'owner' |
+------
If the locked is True, following info will be added into output:
+------
| Parameter | Data |
+======
| locked | True |
+------
| locked_by | 'admin' |
+------
If the locked is false, this will return following info:
+------
| Parameter | Data |
+======
| locked | False |
+------
| locked_by | None |
+------
Both v2 and v3 API will be affected.
* In v2 API, extension os-server-
advertise the extra information.
alias: os-server-
name: ServerLockStatus
namespace: http://
When the new extension "os-server-
2 new fields 'locked', 'locked_by' will be added to
the os-hypervisor API.
Blueprint information
- Status:
- Started
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- jichenjc
- Direction:
- Needs approval
- Assignee:
- jichenjc
- Definition:
- Pending Approval
- Series goal:
- Accepted for trunk
- Implementation:
-
Slow progress
- Milestone target:
-
next
- Started by
- Thierry Carrez
- Completed by
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add lock status into return of instance info
Approved as spec is approved. --johnthetubaguy 17th October 2014
Gerrit topic: https:/
Addressed by: https:/
Add lock status into v2 API
Bumping to k-2 -- mikal 9 Dec 2014
only see v2 code, and not v2.1 code, so this is not all up for review. This has missed the Feature Freeze Proposal deadline, unapproving this blueprint. --johnthetubaguy 26th Jan 2015
No need to address v2.1 code since it's already there
so only v2 code is enough and all features are submitted , so please help to remove this unapproving, thanks
Work Items
Dependency tree
* Blueprints in grey have been implemented.
