2
=================================================================
5
The rescue extension lets you put a server into a "rescue" status when the virtual instance will be replaced with a "rescue" image and have its existing drive attached as a second disk so that a root user can log in and troubleshoot problems with the virtual server.
7
To put a server into "rescue" state, you do not have to be an administrator. The only requirement is that the base image used to build your instance must still be available.
9
To obtain current information the extensions available to you, issue an EXTENSION query on the OpenStack system where it is installed, such as http://mycloud.com/v1.1/tenant/extensions.
18
http://docs.openstack.org/ext/rescue/api/v1.1
24
Josh Kearney <josh@jk0.org>
42
This extension enables rescue capabilities for OpenStack Compute servers so that virtual instances running in the cloud may be put in a rescue status.
44
Sample Query Responses
45
~~~~~~~~~~~~~~~~~~~~~~
47
As shown below, responses to an EXTENSION query in XML or JSON provide basic information about the extension.
49
Extension Query Response: XML::
52
Extension Query Response: JSON::
54
{"extensions": [{"updated": "2011-08-18T00:00:00+00:00", "name": "Rescue", "links": [], "namespace": "http://docs.openstack.org/ext/rescue/api/v1.1", "alias": "os-rescue", "description": "Instance rescue mode"}]}
57
Document Change History
58
~~~~~~~~~~~~~~~~~~~~~~~
60
============= =====================================
61
Revision Date Summary of Changes
62
2011-09-16 Initial draft
63
2012-03-30 Reformat of content
64
============= =====================================
69
This extension to the OpenStack Compute API enables rescue of running instances.
71
This support is provided by the addition of new actions and states.
92
Changes to the Cloud Servers Specification
93
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
95
A new action added to the 4.3 Server Actions section.
100
============= ==================
102
POST /servers/id/rescue
103
============= ==================
105
Normal Response Code(s): 202
107
Error Response Code(s): computeFault (400, 500, …), serviceUnavailable (503), unauthorized (401), forbidden (403), badRequest (400), badMethod (405), overLimit (413), itemNotFound (404), badMediaType (415), buildInProgress (409)
109
Status Transition: ACTIVE -> RESCUING -> ACTIVE
111
This operation places the server into RESCUING status.