4 Documents Ganeti version |version|
11 Ganeti supports a remote API for enable external tools to easily
12 retrieve information about a cluster's state. The remote API daemon,
13 *ganeti-rapi*, is automatically started on the master node. By default
14 it runs on TCP port 5080, but this can be changed either in
15 ``.../constants.py`` or via the command line parameter *-p*. SSL mode,
16 which is used by default, can also be disabled by passing command line
23 ``ganeti-rapi`` reads users and passwords from a file (usually
24 ``/var/lib/ganeti/rapi/users``) on startup. Changes to the file will be
27 Each line consists of two or three fields separated by whitespace. The
28 first two fields are for username and password. The third field is
29 optional and can be used to specify per-user options. Currently,
30 ``write`` is the only option supported and enables the user to execute
31 operations modifying the cluster. Lines starting with the hash sign
32 (``#``) are treated as comments.
34 Passwords can either be written in clear text or as a hash. Clear text
35 passwords may not start with an opening brace (``{``) or they must be
36 prefixed with ``{cleartext}``. To use the hashed form, get the MD5 hash
37 of the string ``$username:Ganeti Remote API:$password`` (e.g. ``echo -n
38 'jack:Ganeti Remote API:abc123' | openssl md5``) [#pwhash]_ and prefix
39 it with ``{ha1}``. Using the scheme prefix for all passwords is
40 recommended. Scheme prefixes are not case sensitive.
44 # Give Jack and Fred read-only access
46 fred {cleartext}foo555
48 # Give write access to an imaginary instance creation script
49 autocreator xyz789 write
51 # Hashed password for Jessica
52 jessica {HA1}7046452df2cbb530877058712cf17bd4 write
55 .. [#pwhash] Using the MD5 hash of username, realm and password is
56 described in :rfc:`2617` ("HTTP Authentication"), sections 3.2.2.2 and
57 3.3. The reason for using it over another algorithm is forward
58 compatibility. If ``ganeti-rapi`` were to implement HTTP Digest
59 authentication in the future, the same hash could be used.
60 In the current version ``ganeti-rapi``'s realm, ``Ganeti Remote
61 API``, can only be changed by modifying the source code.
67 The protocol used is JSON_ over HTTP designed after the REST_ principle.
68 HTTP Basic authentication as per :rfc:`2617` is supported.
70 .. _JSON: http://www.json.org/
71 .. _REST: http://en.wikipedia.org/wiki/Representational_State_Transfer
73 HTTP requests with a body (e.g. ``PUT`` or ``POST``) require the request
74 header ``Content-type`` be set to ``application/json`` (see :rfc:`2616`
75 (HTTP/1.1), section 7.2.1).
78 A note on JSON as used by RAPI
79 ++++++++++++++++++++++++++++++
81 JSON_ as used by Ganeti RAPI does not conform to the specification in
82 :rfc:`4627`. Section 2 defines a JSON text to be either an object
83 (``{"key": "value", …}``) or an array (``[1, 2, 3, …]``). In violation
84 of this RAPI uses plain strings (``"master-candidate"``, ``"1234"``) for
85 some requests or responses. Changing this now would likely break
86 existing clients and cause a lot of trouble.
90 Unlike Python's `JSON encoder and decoder
91 <http://docs.python.org/library/json.html>`_, other programming
92 languages or libraries may only provide a strict implementation, not
93 allowing plain values. For those, responses can usually be wrapped in an
94 array whose first element is then used, e.g. the response ``"1234"``
95 becomes ``["1234"]``. This works equally well for more complex values.
100 # Insert code to get response here
101 response = "\"1234\""
103 decoded = JSON.parse("[#{response}]").first
105 Short of modifying the encoder to allow encoding to a less strict
106 format, requests will have to be formatted by hand. Newer RAPI requests
107 already use a dictionary as their input data and shouldn't cause any
114 According to :rfc:`2616` the main difference between PUT and POST is
115 that POST can create new resources but PUT can only create the resource
116 the URI was pointing to on the PUT request.
118 Unfortunately, due to historic reasons, the Ganeti RAPI library is not
119 consistent with this usage, so just use the methods as documented below
122 For more details have a look in the source code at
123 ``lib/rapi/rlib2.py``.
126 Generic parameter types
127 -----------------------
129 A few generic refered parameter types and the values they allow.
134 A boolean option will accept ``1`` or ``0`` as numbers but not
135 i.e. ``True`` or ``False``.
140 A few parameter mean the same thing across all resources which implement
146 Bulk-mode means that for the resources which usually return just a list
147 of child resources (e.g. ``/2/instances`` which returns just instance
148 names), the output will instead contain detailed data for all these
149 subresources. This is more efficient than query-ing the sub-resources
155 The boolean *dry-run* argument, if provided and set, signals to Ganeti
156 that the job should not be executed, only the pre-execution checks will
159 This is useful in trying to determine (without guarantees though, as in
160 the meantime the cluster state could have changed) if the operation is
161 likely to succeed or at least start executing.
166 Force operation to continue even if it will cause the cluster to become
167 inconsistent (e.g. because there are not enough master candidates).
172 You can access the API using your favorite programming language as long
173 as it supports network connections.
178 Ganeti includes a standalone RAPI client, ``lib/rapi/client.py``.
187 wget -q -O - https://CLUSTERNAME:5080/2/info
191 curl https://CLUSTERNAME:5080/2/info
197 .. highlight:: python
202 f = urllib2.urlopen('https://CLUSTERNAME:5080/2/info')
209 .. warning:: While it's possible to use JavaScript, it poses several
210 potential problems, including browser blocking request due to
211 non-standard ports or different domain names. Fetching the data on
212 the webserver is easier.
214 .. highlight:: javascript
218 var url = 'https://CLUSTERNAME:5080/2/info';
220 var xmlreq = new XMLHttpRequest();
221 xmlreq.onreadystatechange = function () {
222 if (xmlreq.readyState != 4) return;
223 if (xmlreq.status == 200) {
224 info = eval("(" + xmlreq.responseText + ")");
227 alert('Error fetching cluster info');
231 xmlreq.open('GET', url, true);
237 .. highlight:: javascript
244 It supports the following commands: ``GET``.
249 Shows the list of mapped resources.
251 Returns: a dictionary with 'name' and 'uri' keys for each of them.
256 The ``/2`` resource, the root of the version 2 API.
258 It supports the following commands: ``GET``.
263 Show the list of mapped resources.
265 Returns: a dictionary with ``name`` and ``uri`` keys for each of them.
270 Cluster information resource.
272 It supports the following commands: ``GET``.
277 Returns cluster information.
282 "config_version": 2000000,
284 "software_version": "2.0.0~beta2",
285 "os_api_version": 10,
287 "candidate_pool_size": 10,
288 "enabled_hypervisors": [
294 "default_hypervisor": "fake",
295 "master": "node1.example.com",
300 "protocol_version": 20,
303 "auto_balance": true,
311 ``/2/redistribute-config``
312 ++++++++++++++++++++++++++
314 Redistribute configuration to all nodes.
316 It supports the following commands: ``PUT``.
321 Redistribute configuration to all nodes. The result will be a job id.
330 Returns a list of features supported by the RAPI server. Available
335 rlib2.ALL_FEATURES == set([rlib2._INST_CREATE_REQV1,
336 rlib2._INST_REINSTALL_REQV1,
337 rlib2._NODE_MIGRATE_REQV1,
338 rlib2._NODE_EVAC_RES1])
340 :pyeval:`rlib2._INST_CREATE_REQV1`
341 Instance creation request data version 1 supported.
342 :pyeval:`rlib2._INST_REINSTALL_REQV1`
343 Instance reinstall supports body parameters.
344 :pyeval:`rlib2._NODE_MIGRATE_REQV1`
345 Whether migrating a node (``/2/nodes/[node_name]/migrate``) supports
346 request body parameters.
347 :pyeval:`rlib2._NODE_EVAC_RES1`
348 Whether evacuating a node (``/2/nodes/[node_name]/evacuate``) returns
349 a new-style result (see resource description)
353 ++++++++++++++++++++++++++++++++++++++++
355 Modifies cluster parameters.
357 Supports the following commands: ``PUT``.
366 .. opcode_params:: OP_CLUSTER_SET_PARAMS
374 It supports the following commands: ``GET``, ``POST``.
379 Returns a list of all existing node groups.
386 "uri": "\/2\/groups\/group1"
390 "uri": "\/2\/groups\/group2"
394 If the optional bool *bulk* argument is provided and set to a true value
395 (i.e ``?bulk=1``), the output contains detailed information about node
398 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.G_FIELDS))`
410 "uuid": "0d7d407c-262e-49af-881a-6a430034bf43"
418 "uuid": "f5a277e7-68f9-44d3-a378-4b25ecb5df5c"
425 Creates a node group.
427 If the optional bool *dry-run* argument is provided, the job will not be
428 actually executed, only the pre-execution checks will be done.
430 Returns: a job ID that can be used later for polling.
434 .. opcode_params:: OP_GROUP_ADD
436 Earlier versions used a parameter named ``name`` which, while still
437 supported, has been renamed to ``group_name``.
440 ``/2/groups/[group_name]``
441 ++++++++++++++++++++++++++
443 Returns information about a node group.
445 It supports the following commands: ``GET``, ``DELETE``.
450 Returns information about a node group, similar to the bulk output from
453 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.G_FIELDS))`
458 Deletes a node group.
460 It supports the ``dry-run`` argument.
463 ``/2/groups/[group_name]/modify``
464 +++++++++++++++++++++++++++++++++
466 Modifies the parameters of a node group.
468 Supports the following commands: ``PUT``.
477 .. opcode_params:: OP_GROUP_SET_PARAMS
481 ``/2/groups/[group_name]/rename``
482 +++++++++++++++++++++++++++++++++
484 Renames a node group.
486 Supports the following commands: ``PUT``.
495 .. opcode_params:: OP_GROUP_RENAME
499 ``/2/groups/[group_name]/assign-nodes``
500 +++++++++++++++++++++++++++++++++++++++
502 Assigns nodes to a group.
504 Supports the following commands: ``PUT``.
509 Returns a job ID. It supports the ``dry-run`` and ``force`` arguments.
513 .. opcode_params:: OP_GROUP_ASSIGN_NODES
514 :exclude: group_name, force, dry_run
517 ``/2/groups/[group_name]/tags``
518 +++++++++++++++++++++++++++++++
520 Manages per-nodegroup tags.
522 Supports the following commands: ``GET``, ``PUT``, ``DELETE``.
527 Returns a list of tags.
531 ["tag1", "tag2", "tag3"]
538 The request as a list of strings should be ``PUT`` to this URI. The
539 result will be a job id.
541 It supports the ``dry-run`` argument.
549 In order to delete a set of tags, the DELETE request should be addressed
552 /tags?tag=[tag]&tag=[tag]
554 It supports the ``dry-run`` argument.
560 The instances resource.
562 It supports the following commands: ``GET``, ``POST``.
567 Returns a list of all available instances.
573 "name": "web.example.com",
574 "uri": "\/instances\/web.example.com"
577 "name": "mail.example.com",
578 "uri": "\/instances\/mail.example.com"
582 If the optional bool *bulk* argument is provided and set to a true value
583 (i.e ``?bulk=1``), the output contains detailed information about
586 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.I_FIELDS))`
597 "name": "web.example.com",
598 "tags": ["tag1", "tag2"],
606 "pnode": "node1.example.com",
607 "nic.macs": ["01:23:45:67:89:01"],
608 "snodes": ["node2.example.com"],
609 "disk_template": "drbd",
623 If the optional bool *dry-run* argument is provided, the job will not be
624 actually executed, only the pre-execution checks will be done. Query-ing
625 the job result will return, in both dry-run and normal case, the list of
626 nodes selected for the instance.
628 Returns: a job ID that can be used later for polling.
632 ``__version__`` (int, required)
633 Must be ``1`` (older Ganeti versions used a different format for
634 instance creation requests, version ``0``, but that format is no
637 .. opcode_params:: OP_INSTANCE_CREATE
639 Earlier versions used parameters named ``name`` and ``os``. These have
640 been replaced by ``instance_name`` and ``os_type`` to match the
641 underlying opcode. The old names can still be used.
644 ``/2/instances/[instance_name]``
645 ++++++++++++++++++++++++++++++++
647 Instance-specific resource.
649 It supports the following commands: ``GET``, ``DELETE``.
654 Returns information about an instance, similar to the bulk output from
657 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.I_FIELDS))`
664 It supports the ``dry-run`` argument.
667 ``/2/instances/[instance_name]/info``
668 +++++++++++++++++++++++++++++++++++++++
670 It supports the following commands: ``GET``.
675 Requests detailed information about the instance. An optional parameter,
676 ``static`` (bool), can be set to return only static information from the
677 configuration without querying the instance's nodes. The result will be
681 ``/2/instances/[instance_name]/reboot``
682 +++++++++++++++++++++++++++++++++++++++
684 Reboots URI for an instance.
686 It supports the following commands: ``POST``.
691 Reboots the instance.
693 The URI takes optional ``type=soft|hard|full`` and
694 ``ignore_secondaries=0|1`` parameters.
696 ``type`` defines the reboot type. ``soft`` is just a normal reboot,
697 without terminating the hypervisor. ``hard`` means full shutdown
698 (including terminating the hypervisor process) and startup again.
699 ``full`` is like ``hard`` but also recreates the configuration from
700 ground up as if you would have done a ``gnt-instance shutdown`` and
701 ``gnt-instance start`` on it.
703 ``ignore_secondaries`` is a bool argument indicating if we start the
704 instance even if secondary disks are failing.
706 It supports the ``dry-run`` argument.
709 ``/2/instances/[instance_name]/shutdown``
710 +++++++++++++++++++++++++++++++++++++++++
712 Instance shutdown URI.
714 It supports the following commands: ``PUT``.
719 Shutdowns an instance.
721 It supports the ``dry-run`` argument.
723 .. opcode_params:: OP_INSTANCE_SHUTDOWN
724 :exclude: instance_name, dry_run
727 ``/2/instances/[instance_name]/startup``
728 ++++++++++++++++++++++++++++++++++++++++
730 Instance startup URI.
732 It supports the following commands: ``PUT``.
739 The URI takes an optional ``force=1|0`` parameter to start the
740 instance even if secondary disks are failing.
742 It supports the ``dry-run`` argument.
744 ``/2/instances/[instance_name]/reinstall``
745 ++++++++++++++++++++++++++++++++++++++++++++++
747 Installs the operating system again.
749 It supports the following commands: ``POST``.
758 ``os`` (string, required)
759 Instance operating system.
760 ``start`` (bool, defaults to true)
761 Whether to start instance after reinstallation.
763 Dictionary with (temporary) OS parameters.
765 For backwards compatbility, this resource also takes the query
766 parameters ``os`` (OS template name) and ``nostartup`` (bool). New
767 clients should use the body parameters.
770 ``/2/instances/[instance_name]/replace-disks``
771 ++++++++++++++++++++++++++++++++++++++++++++++
773 Replaces disks on an instance.
775 It supports the following commands: ``POST``.
780 Takes the parameters ``mode`` (one of ``replace_on_primary``,
781 ``replace_on_secondary``, ``replace_new_secondary`` or
782 ``replace_auto``), ``disks`` (comma separated list of disk indexes),
783 ``remote_node`` and ``iallocator``.
785 Either ``remote_node`` or ``iallocator`` needs to be defined when using
786 ``mode=replace_new_secondary``.
788 ``mode`` is a mandatory parameter. ``replace_auto`` tries to determine
789 the broken disk(s) on its own and replacing it.
792 ``/2/instances/[instance_name]/activate-disks``
793 +++++++++++++++++++++++++++++++++++++++++++++++
795 Activate disks on an instance.
797 It supports the following commands: ``PUT``.
802 Takes the bool parameter ``ignore_size``. When set ignore the recorded
803 size (useful for forcing activation when recorded size is wrong).
806 ``/2/instances/[instance_name]/deactivate-disks``
807 +++++++++++++++++++++++++++++++++++++++++++++++++
809 Deactivate disks on an instance.
811 It supports the following commands: ``PUT``.
819 ``/2/instances/[instance_name]/disk/[disk_index]/grow``
820 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
822 Grows one disk of an instance.
824 Supports the following commands: ``POST``.
833 .. opcode_params:: OP_INSTANCE_GROW_DISK
834 :exclude: instance_name, disk
837 ``/2/instances/[instance_name]/prepare-export``
838 +++++++++++++++++++++++++++++++++++++++++++++++++
840 Prepares an export of an instance.
842 It supports the following commands: ``PUT``.
847 Takes one parameter, ``mode``, for the export mode. Returns a job ID.
850 ``/2/instances/[instance_name]/export``
851 +++++++++++++++++++++++++++++++++++++++++++++++++
855 It supports the following commands: ``PUT``.
864 .. opcode_params:: OP_BACKUP_EXPORT
865 :exclude: instance_name
866 :alias: target_node=destination
869 ``/2/instances/[instance_name]/migrate``
870 ++++++++++++++++++++++++++++++++++++++++
872 Migrates an instance.
874 Supports the following commands: ``PUT``.
883 .. opcode_params:: OP_INSTANCE_MIGRATE
884 :exclude: instance_name, live
887 ``/2/instances/[instance_name]/failover``
888 +++++++++++++++++++++++++++++++++++++++++
890 Does a failover of an instance.
892 Supports the following commands: ``PUT``.
901 .. opcode_params:: OP_INSTANCE_FAILOVER
902 :exclude: instance_name
905 ``/2/instances/[instance_name]/rename``
906 ++++++++++++++++++++++++++++++++++++++++
910 Supports the following commands: ``PUT``.
919 .. opcode_params:: OP_INSTANCE_RENAME
920 :exclude: instance_name
923 ``/2/instances/[instance_name]/modify``
924 ++++++++++++++++++++++++++++++++++++++++
926 Modifies an instance.
928 Supports the following commands: ``PUT``.
937 .. opcode_params:: OP_INSTANCE_SET_PARAMS
938 :exclude: instance_name
941 ``/2/instances/[instance_name]/console``
942 ++++++++++++++++++++++++++++++++++++++++
944 Request information for connecting to instance's console.
946 Supports the following commands: ``GET``.
951 Returns a dictionary containing information about the instance's
952 console. Contained keys:
956 constants.CONS_ALL == frozenset([
957 constants.CONS_MESSAGE,
965 Console type, one of :pyeval:`constants.CONS_SSH`,
966 :pyeval:`constants.CONS_VNC` or :pyeval:`constants.CONS_MESSAGE`.
968 Message to display (:pyeval:`constants.CONS_MESSAGE` type only).
970 Host to connect to (:pyeval:`constants.CONS_SSH` and
971 :pyeval:`constants.CONS_VNC` only).
973 TCP port to connect to (:pyeval:`constants.CONS_VNC` only).
975 Username to use (:pyeval:`constants.CONS_SSH` only).
977 Command to execute on machine (:pyeval:`constants.CONS_SSH` only)
979 VNC display number (:pyeval:`constants.CONS_VNC` only).
982 ``/2/instances/[instance_name]/tags``
983 +++++++++++++++++++++++++++++++++++++
985 Manages per-instance tags.
987 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
992 Returns a list of tags.
996 ["tag1", "tag2", "tag3"]
1003 The request as a list of strings should be ``PUT`` to this URI. The
1004 result will be a job id.
1006 It supports the ``dry-run`` argument.
1014 In order to delete a set of tags, the DELETE request should be addressed
1017 /tags?tag=[tag]&tag=[tag]
1019 It supports the ``dry-run`` argument.
1025 The ``/2/jobs`` resource.
1027 It supports the following commands: ``GET``.
1032 Returns a dictionary of jobs.
1034 Returns: a dictionary with jobs id and uri.
1036 If the optional bool *bulk* argument is provided and set to a true value
1037 (i.e. ``?bulk=1``), the output contains detailed information about jobs
1040 Returned fields for bulk requests (unlike other bulk requests, these
1041 fields are not the same as for per-job requests):
1042 :pyeval:`utils.CommaJoin(sorted(rlib2.J_FIELDS_BULK))`
1044 ``/2/jobs/[job_id]``
1045 ++++++++++++++++++++
1050 It supports the following commands: ``GET``, ``DELETE``.
1055 Returns a dictionary with job parameters, containing the fields
1056 :pyeval:`utils.CommaJoin(sorted(rlib2.J_FIELDS))`.
1058 The result includes:
1060 - id: job ID as a number
1061 - status: current job status as a string
1062 - ops: involved OpCodes as a list of dictionaries for each opcodes in
1064 - opstatus: OpCodes status as a list
1065 - opresult: OpCodes results as a list
1067 For a successful opcode, the ``opresult`` field corresponding to it will
1068 contain the raw result from its :term:`LogicalUnit`. In case an opcode
1069 has failed, its element in the opresult list will be a list of two
1072 - first element the error type (the Ganeti internal error name)
1073 - second element a list of either one or two elements:
1075 - the first element is the textual error description
1076 - the second element, if any, will hold an error classification
1078 The error classification is most useful for the ``OpPrereqError``
1079 error type - these errors happen before the OpCode has started
1080 executing, so it's possible to retry the OpCode without side
1081 effects. But whether it make sense to retry depends on the error
1086 errors.ECODE_ALL == set([errors.ECODE_RESOLVER, errors.ECODE_NORES,
1087 errors.ECODE_INVAL, errors.ECODE_STATE, errors.ECODE_NOENT,
1088 errors.ECODE_EXISTS, errors.ECODE_NOTUNIQUE, errors.ECODE_FAULT,
1089 errors.ECODE_ENVIRON])
1091 :pyeval:`errors.ECODE_RESOLVER`
1092 Resolver errors. This usually means that a name doesn't exist in DNS,
1093 so if it's a case of slow DNS propagation the operation can be retried
1096 :pyeval:`errors.ECODE_NORES`
1097 Not enough resources (iallocator failure, disk space, memory,
1098 etc.). If the resources on the cluster increase, the operation might
1101 :pyeval:`errors.ECODE_INVAL`
1102 Wrong arguments (at syntax level). The operation will not ever be
1103 accepted unless the arguments change.
1105 :pyeval:`errors.ECODE_STATE`
1106 Wrong entity state. For example, live migration has been requested for
1107 a down instance, or instance creation on an offline node. The
1108 operation can be retried once the resource has changed state.
1110 :pyeval:`errors.ECODE_NOENT`
1111 Entity not found. For example, information has been requested for an
1114 :pyeval:`errors.ECODE_EXISTS`
1115 Entity already exists. For example, instance creation has been
1116 requested for an already-existing instance.
1118 :pyeval:`errors.ECODE_NOTUNIQUE`
1119 Resource not unique (e.g. MAC or IP duplication).
1121 :pyeval:`errors.ECODE_FAULT`
1122 Internal cluster error. For example, a node is unreachable but not set
1123 offline, or the ganeti node daemons are not working, etc. A
1124 ``gnt-cluster verify`` should be run.
1126 :pyeval:`errors.ECODE_ENVIRON`
1127 Environment error (e.g. node disk error). A ``gnt-cluster verify``
1130 Note that in the above list, by entity we refer to a node or instance,
1131 while by a resource we refer to an instance's disk, or NIC, etc.
1137 Cancel a not-yet-started job.
1140 ``/2/jobs/[job_id]/wait``
1141 +++++++++++++++++++++++++
1146 Waits for changes on a job. Takes the following body parameters in a
1150 The job fields on which to watch for changes.
1152 ``previous_job_info``
1153 Previously received field values or None if not yet available.
1155 ``previous_log_serial``
1156 Highest log serial number received so far or None if not yet
1159 Returns None if no changes have been detected and a dict with two keys,
1160 ``job_info`` and ``log_entries`` otherwise.
1168 It supports the following commands: ``GET``.
1173 Returns a list of all nodes.
1179 "id": "node1.example.com",
1180 "uri": "\/nodes\/node1.example.com"
1183 "id": "node2.example.com",
1184 "uri": "\/nodes\/node2.example.com"
1188 If the optional bool *bulk* argument is provided and set to a true value
1189 (i.e ``?bulk=1``), the output contains detailed information about nodes
1192 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.N_FIELDS))`
1201 "name": "www.example.com",
1212 ``/2/nodes/[node_name]``
1213 +++++++++++++++++++++++++++++++++
1215 Returns information about a node.
1217 It supports the following commands: ``GET``.
1219 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.N_FIELDS))`
1221 ``/2/nodes/[node_name]/evacuate``
1222 +++++++++++++++++++++++++++++++++
1224 Evacuates instances off a node.
1226 It supports the following commands: ``POST``.
1231 Returns a job ID. The result of the job will contain the IDs of the
1232 individual jobs submitted to evacuate the node.
1236 .. opcode_params:: OP_NODE_EVACUATE
1239 Up to and including Ganeti 2.4 query arguments were used. Those are no
1240 longer supported. The new request can be detected by the presence of the
1241 :pyeval:`rlib2._NODE_EVAC_RES1` feature string.
1244 ``/2/nodes/[node_name]/migrate``
1245 +++++++++++++++++++++++++++++++++
1247 Migrates all primary instances from a node.
1249 It supports the following commands: ``POST``.
1254 If no mode is explicitly specified, each instances' hypervisor default
1255 migration mode will be used. Body parameters:
1257 .. opcode_params:: OP_NODE_MIGRATE
1260 The query arguments used up to and including Ganeti 2.4 are deprecated
1261 and should no longer be used. The new request format can be detected by
1262 the presence of the :pyeval:`rlib2._NODE_MIGRATE_REQV1` feature string.
1265 ``/2/nodes/[node_name]/role``
1266 +++++++++++++++++++++++++++++
1270 It supports the following commands: ``GET``, ``PUT``.
1272 The role is always one of the following:
1279 Note that the 'master' role is a special, and currently it can't be
1280 modified via RAPI, only via the command line (``gnt-cluster
1286 Returns the current node role.
1295 Change the node role.
1297 The request is a string which should be PUT to this URI. The result will
1300 It supports the bool ``force`` argument.
1302 ``/2/nodes/[node_name]/storage``
1303 ++++++++++++++++++++++++++++++++
1305 Manages storage units on the node.
1312 constants.VALID_STORAGE_TYPES == set([constants.ST_FILE,
1313 constants.ST_LVM_PV,
1314 constants.ST_LVM_VG])
1316 Requests a list of storage units on a node. Requires the parameters
1317 ``storage_type`` (one of :pyeval:`constants.ST_FILE`,
1318 :pyeval:`constants.ST_LVM_PV` or :pyeval:`constants.ST_LVM_VG`) and
1319 ``output_fields``. The result will be a job id, using which the result
1322 ``/2/nodes/[node_name]/storage/modify``
1323 +++++++++++++++++++++++++++++++++++++++
1325 Modifies storage units on the node.
1330 Modifies parameters of storage units on the node. Requires the
1331 parameters ``storage_type`` (one of :pyeval:`constants.ST_FILE`,
1332 :pyeval:`constants.ST_LVM_PV` or :pyeval:`constants.ST_LVM_VG`)
1333 and ``name`` (name of the storage unit). Parameters can be passed
1334 additionally. Currently only :pyeval:`constants.SF_ALLOCATABLE` (bool)
1335 is supported. The result will be a job id.
1337 ``/2/nodes/[node_name]/storage/repair``
1338 +++++++++++++++++++++++++++++++++++++++
1340 Repairs a storage unit on the node.
1347 constants.VALID_STORAGE_OPERATIONS == {
1348 constants.ST_LVM_VG: set([constants.SO_FIX_CONSISTENCY]),
1351 Repairs a storage unit on the node. Requires the parameters
1352 ``storage_type`` (currently only :pyeval:`constants.ST_LVM_VG` can be
1353 repaired) and ``name`` (name of the storage unit). The result will be a
1356 ``/2/nodes/[node_name]/tags``
1357 +++++++++++++++++++++++++++++
1359 Manages per-node tags.
1361 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1366 Returns a list of tags.
1370 ["tag1", "tag2", "tag3"]
1377 The request as a list of strings should be PUT to this URI. The result
1380 It supports the ``dry-run`` argument.
1387 In order to delete a set of tags, the DELETE request should be addressed
1390 /tags?tag=[tag]&tag=[tag]
1392 It supports the ``dry-run`` argument.
1395 ``/2/query/[resource]``
1396 +++++++++++++++++++++++
1398 Requests resource information. Available fields can be found in man
1399 pages and using ``/2/query/[resource]/fields``. The resource is one of
1400 :pyeval:`utils.CommaJoin(constants.QR_VIA_RAPI)`. See the :doc:`query2
1401 design document <design-query2>` for more details.
1403 Supports the following commands: ``GET``, ``PUT``.
1408 Returns list of included fields and actual data. Takes a query parameter
1409 named "fields", containing a comma-separated list of field names. Does
1410 not support filtering.
1415 Returns list of included fields and actual data. The list of requested
1416 fields can either be given as the query parameter "fields" or as a body
1417 parameter with the same name. The optional body parameter "filter" can
1418 be given and must be either ``null`` or a list containing filter
1422 ``/2/query/[resource]/fields``
1423 ++++++++++++++++++++++++++++++
1425 Request list of available fields for a resource. The resource is one of
1426 :pyeval:`utils.CommaJoin(constants.QR_VIA_RAPI)`. See the
1427 :doc:`query2 design document <design-query2>` for more details.
1429 Supports the following commands: ``GET``.
1434 Returns a list of field descriptions for available fields. Takes an
1435 optional query parameter named "fields", containing a comma-separated
1436 list of field names.
1444 It supports the following commands: ``GET``.
1449 Return a list of all OSes.
1451 Can return error 500 in case of a problem. Since this is a costly
1452 operation for Ganeti 2.0, it is not recommended to execute it too often.
1461 Manages cluster tags.
1463 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1468 Returns the cluster tags.
1472 ["tag1", "tag2", "tag3"]
1479 The request as a list of strings should be PUT to this URI. The result
1482 It supports the ``dry-run`` argument.
1490 In order to delete a set of tags, the DELETE request should be addressed
1493 /tags?tag=[tag]&tag=[tag]
1495 It supports the ``dry-run`` argument.
1501 The version resource.
1503 This resource should be used to determine the remote API version and to
1504 adapt clients accordingly.
1506 It supports the following commands: ``GET``.
1511 Returns the remote API version. Ganeti 1.2 returned ``1`` and Ganeti 2.0
1514 .. vim: set textwidth=72 :