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
57 and 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
482 .. opcode_result:: OP_GROUP_SET_PARAMS
485 ``/2/groups/[group_name]/rename``
486 +++++++++++++++++++++++++++++++++
488 Renames a node group.
490 Supports the following commands: ``PUT``.
499 .. opcode_params:: OP_GROUP_RENAME
504 .. opcode_result:: OP_GROUP_RENAME
507 ``/2/groups/[group_name]/assign-nodes``
508 +++++++++++++++++++++++++++++++++++++++
510 Assigns nodes to a group.
512 Supports the following commands: ``PUT``.
517 Returns a job ID. It supports the ``dry-run`` and ``force`` arguments.
521 .. opcode_params:: OP_GROUP_ASSIGN_NODES
522 :exclude: group_name, force, dry_run
525 ``/2/groups/[group_name]/tags``
526 +++++++++++++++++++++++++++++++
528 Manages per-nodegroup tags.
530 Supports the following commands: ``GET``, ``PUT``, ``DELETE``.
535 Returns a list of tags.
539 ["tag1", "tag2", "tag3"]
546 The request as a list of strings should be ``PUT`` to this URI. The
547 result will be a job id.
549 It supports the ``dry-run`` argument.
557 In order to delete a set of tags, the DELETE request should be addressed
560 /tags?tag=[tag]&tag=[tag]
562 It supports the ``dry-run`` argument.
568 The instances resource.
570 It supports the following commands: ``GET``, ``POST``.
575 Returns a list of all available instances.
581 "name": "web.example.com",
582 "uri": "\/instances\/web.example.com"
585 "name": "mail.example.com",
586 "uri": "\/instances\/mail.example.com"
590 If the optional bool *bulk* argument is provided and set to a true value
591 (i.e ``?bulk=1``), the output contains detailed information about
594 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.I_FIELDS))`
605 "name": "web.example.com",
606 "tags": ["tag1", "tag2"],
614 "pnode": "node1.example.com",
615 "nic.macs": ["01:23:45:67:89:01"],
616 "snodes": ["node2.example.com"],
617 "disk_template": "drbd",
631 If the optional bool *dry-run* argument is provided, the job will not be
632 actually executed, only the pre-execution checks will be done. Query-ing
633 the job result will return, in both dry-run and normal case, the list of
634 nodes selected for the instance.
636 Returns: a job ID that can be used later for polling.
640 ``__version__`` (int, required)
641 Must be ``1`` (older Ganeti versions used a different format for
642 instance creation requests, version ``0``, but that format is no
645 .. opcode_params:: OP_INSTANCE_CREATE
647 Earlier versions used parameters named ``name`` and ``os``. These have
648 been replaced by ``instance_name`` and ``os_type`` to match the
649 underlying opcode. The old names can still be used.
653 .. opcode_result:: OP_INSTANCE_CREATE
656 ``/2/instances/[instance_name]``
657 ++++++++++++++++++++++++++++++++
659 Instance-specific resource.
661 It supports the following commands: ``GET``, ``DELETE``.
666 Returns information about an instance, similar to the bulk output from
669 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.I_FIELDS))`
676 It supports the ``dry-run`` argument.
679 ``/2/instances/[instance_name]/info``
680 +++++++++++++++++++++++++++++++++++++++
682 It supports the following commands: ``GET``.
687 Requests detailed information about the instance. An optional parameter,
688 ``static`` (bool), can be set to return only static information from the
689 configuration without querying the instance's nodes. The result will be
693 ``/2/instances/[instance_name]/reboot``
694 +++++++++++++++++++++++++++++++++++++++
696 Reboots URI for an instance.
698 It supports the following commands: ``POST``.
703 Reboots the instance.
705 The URI takes optional ``type=soft|hard|full`` and
706 ``ignore_secondaries=0|1`` parameters.
708 ``type`` defines the reboot type. ``soft`` is just a normal reboot,
709 without terminating the hypervisor. ``hard`` means full shutdown
710 (including terminating the hypervisor process) and startup again.
711 ``full`` is like ``hard`` but also recreates the configuration from
712 ground up as if you would have done a ``gnt-instance shutdown`` and
713 ``gnt-instance start`` on it.
715 ``ignore_secondaries`` is a bool argument indicating if we start the
716 instance even if secondary disks are failing.
718 It supports the ``dry-run`` argument.
721 ``/2/instances/[instance_name]/shutdown``
722 +++++++++++++++++++++++++++++++++++++++++
724 Instance shutdown URI.
726 It supports the following commands: ``PUT``.
731 Shutdowns an instance.
733 It supports the ``dry-run`` argument.
735 .. opcode_params:: OP_INSTANCE_SHUTDOWN
736 :exclude: instance_name, dry_run
739 ``/2/instances/[instance_name]/startup``
740 ++++++++++++++++++++++++++++++++++++++++
742 Instance startup URI.
744 It supports the following commands: ``PUT``.
751 The URI takes an optional ``force=1|0`` parameter to start the
752 instance even if secondary disks are failing.
754 It supports the ``dry-run`` argument.
756 ``/2/instances/[instance_name]/reinstall``
757 ++++++++++++++++++++++++++++++++++++++++++++++
759 Installs the operating system again.
761 It supports the following commands: ``POST``.
770 ``os`` (string, required)
771 Instance operating system.
772 ``start`` (bool, defaults to true)
773 Whether to start instance after reinstallation.
775 Dictionary with (temporary) OS parameters.
777 For backwards compatbility, this resource also takes the query
778 parameters ``os`` (OS template name) and ``nostartup`` (bool). New
779 clients should use the body parameters.
782 ``/2/instances/[instance_name]/replace-disks``
783 ++++++++++++++++++++++++++++++++++++++++++++++
785 Replaces disks on an instance.
787 It supports the following commands: ``POST``.
792 Takes the parameters ``mode`` (one of ``replace_on_primary``,
793 ``replace_on_secondary``, ``replace_new_secondary`` or
794 ``replace_auto``), ``disks`` (comma separated list of disk indexes),
795 ``remote_node`` and ``iallocator``.
797 Either ``remote_node`` or ``iallocator`` needs to be defined when using
798 ``mode=replace_new_secondary``.
800 ``mode`` is a mandatory parameter. ``replace_auto`` tries to determine
801 the broken disk(s) on its own and replacing it.
804 ``/2/instances/[instance_name]/activate-disks``
805 +++++++++++++++++++++++++++++++++++++++++++++++
807 Activate disks on an instance.
809 It supports the following commands: ``PUT``.
814 Takes the bool parameter ``ignore_size``. When set ignore the recorded
815 size (useful for forcing activation when recorded size is wrong).
818 ``/2/instances/[instance_name]/deactivate-disks``
819 +++++++++++++++++++++++++++++++++++++++++++++++++
821 Deactivate disks on an instance.
823 It supports the following commands: ``PUT``.
831 ``/2/instances/[instance_name]/disk/[disk_index]/grow``
832 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
834 Grows one disk of an instance.
836 Supports the following commands: ``POST``.
845 .. opcode_params:: OP_INSTANCE_GROW_DISK
846 :exclude: instance_name, disk
849 ``/2/instances/[instance_name]/prepare-export``
850 +++++++++++++++++++++++++++++++++++++++++++++++++
852 Prepares an export of an instance.
854 It supports the following commands: ``PUT``.
859 Takes one parameter, ``mode``, for the export mode. Returns a job ID.
862 ``/2/instances/[instance_name]/export``
863 +++++++++++++++++++++++++++++++++++++++++++++++++
867 It supports the following commands: ``PUT``.
876 .. opcode_params:: OP_BACKUP_EXPORT
877 :exclude: instance_name
878 :alias: target_node=destination
881 ``/2/instances/[instance_name]/migrate``
882 ++++++++++++++++++++++++++++++++++++++++
884 Migrates an instance.
886 Supports the following commands: ``PUT``.
895 .. opcode_params:: OP_INSTANCE_MIGRATE
896 :exclude: instance_name, live
899 ``/2/instances/[instance_name]/failover``
900 +++++++++++++++++++++++++++++++++++++++++
902 Does a failover of an instance.
904 Supports the following commands: ``PUT``.
913 .. opcode_params:: OP_INSTANCE_FAILOVER
914 :exclude: instance_name
917 ``/2/instances/[instance_name]/rename``
918 ++++++++++++++++++++++++++++++++++++++++
922 Supports the following commands: ``PUT``.
931 .. opcode_params:: OP_INSTANCE_RENAME
932 :exclude: instance_name
936 .. opcode_result:: OP_INSTANCE_RENAME
939 ``/2/instances/[instance_name]/modify``
940 ++++++++++++++++++++++++++++++++++++++++
942 Modifies an instance.
944 Supports the following commands: ``PUT``.
953 .. opcode_params:: OP_INSTANCE_SET_PARAMS
954 :exclude: instance_name
958 .. opcode_result:: OP_INSTANCE_SET_PARAMS
961 ``/2/instances/[instance_name]/console``
962 ++++++++++++++++++++++++++++++++++++++++
964 Request information for connecting to instance's console.
966 Supports the following commands: ``GET``.
971 Returns a dictionary containing information about the instance's
972 console. Contained keys:
976 constants.CONS_ALL == frozenset([
977 constants.CONS_MESSAGE,
985 Console type, one of :pyeval:`constants.CONS_SSH`,
986 :pyeval:`constants.CONS_VNC` or :pyeval:`constants.CONS_MESSAGE`.
988 Message to display (:pyeval:`constants.CONS_MESSAGE` type only).
990 Host to connect to (:pyeval:`constants.CONS_SSH` and
991 :pyeval:`constants.CONS_VNC` only).
993 TCP port to connect to (:pyeval:`constants.CONS_VNC` only).
995 Username to use (:pyeval:`constants.CONS_SSH` only).
997 Command to execute on machine (:pyeval:`constants.CONS_SSH` only)
999 VNC display number (:pyeval:`constants.CONS_VNC` only).
1002 ``/2/instances/[instance_name]/tags``
1003 +++++++++++++++++++++++++++++++++++++
1005 Manages per-instance tags.
1007 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1012 Returns a list of tags.
1016 ["tag1", "tag2", "tag3"]
1023 The request as a list of strings should be ``PUT`` to this URI. The
1024 result will be a job id.
1026 It supports the ``dry-run`` argument.
1034 In order to delete a set of tags, the DELETE request should be addressed
1037 /tags?tag=[tag]&tag=[tag]
1039 It supports the ``dry-run`` argument.
1045 The ``/2/jobs`` resource.
1047 It supports the following commands: ``GET``.
1052 Returns a dictionary of jobs.
1054 Returns: a dictionary with jobs id and uri.
1056 If the optional bool *bulk* argument is provided and set to a true value
1057 (i.e. ``?bulk=1``), the output contains detailed information about jobs
1060 Returned fields for bulk requests (unlike other bulk requests, these
1061 fields are not the same as for per-job requests):
1062 :pyeval:`utils.CommaJoin(sorted(rlib2.J_FIELDS_BULK))`
1064 ``/2/jobs/[job_id]``
1065 ++++++++++++++++++++
1070 It supports the following commands: ``GET``, ``DELETE``.
1075 Returns a dictionary with job parameters, containing the fields
1076 :pyeval:`utils.CommaJoin(sorted(rlib2.J_FIELDS))`.
1078 The result includes:
1080 - id: job ID as a number
1081 - status: current job status as a string
1082 - ops: involved OpCodes as a list of dictionaries for each opcodes in
1084 - opstatus: OpCodes status as a list
1085 - opresult: OpCodes results as a list
1087 For a successful opcode, the ``opresult`` field corresponding to it will
1088 contain the raw result from its :term:`LogicalUnit`. In case an opcode
1089 has failed, its element in the opresult list will be a list of two
1092 - first element the error type (the Ganeti internal error name)
1093 - second element a list of either one or two elements:
1095 - the first element is the textual error description
1096 - the second element, if any, will hold an error classification
1098 The error classification is most useful for the ``OpPrereqError``
1099 error type - these errors happen before the OpCode has started
1100 executing, so it's possible to retry the OpCode without side
1101 effects. But whether it make sense to retry depends on the error
1106 errors.ECODE_ALL == set([errors.ECODE_RESOLVER, errors.ECODE_NORES,
1107 errors.ECODE_INVAL, errors.ECODE_STATE, errors.ECODE_NOENT,
1108 errors.ECODE_EXISTS, errors.ECODE_NOTUNIQUE, errors.ECODE_FAULT,
1109 errors.ECODE_ENVIRON])
1111 :pyeval:`errors.ECODE_RESOLVER`
1112 Resolver errors. This usually means that a name doesn't exist in DNS,
1113 so if it's a case of slow DNS propagation the operation can be retried
1116 :pyeval:`errors.ECODE_NORES`
1117 Not enough resources (iallocator failure, disk space, memory,
1118 etc.). If the resources on the cluster increase, the operation might
1121 :pyeval:`errors.ECODE_INVAL`
1122 Wrong arguments (at syntax level). The operation will not ever be
1123 accepted unless the arguments change.
1125 :pyeval:`errors.ECODE_STATE`
1126 Wrong entity state. For example, live migration has been requested for
1127 a down instance, or instance creation on an offline node. The
1128 operation can be retried once the resource has changed state.
1130 :pyeval:`errors.ECODE_NOENT`
1131 Entity not found. For example, information has been requested for an
1134 :pyeval:`errors.ECODE_EXISTS`
1135 Entity already exists. For example, instance creation has been
1136 requested for an already-existing instance.
1138 :pyeval:`errors.ECODE_NOTUNIQUE`
1139 Resource not unique (e.g. MAC or IP duplication).
1141 :pyeval:`errors.ECODE_FAULT`
1142 Internal cluster error. For example, a node is unreachable but not set
1143 offline, or the ganeti node daemons are not working, etc. A
1144 ``gnt-cluster verify`` should be run.
1146 :pyeval:`errors.ECODE_ENVIRON`
1147 Environment error (e.g. node disk error). A ``gnt-cluster verify``
1150 Note that in the above list, by entity we refer to a node or instance,
1151 while by a resource we refer to an instance's disk, or NIC, etc.
1157 Cancel a not-yet-started job.
1160 ``/2/jobs/[job_id]/wait``
1161 +++++++++++++++++++++++++
1166 Waits for changes on a job. Takes the following body parameters in a
1170 The job fields on which to watch for changes.
1172 ``previous_job_info``
1173 Previously received field values or None if not yet available.
1175 ``previous_log_serial``
1176 Highest log serial number received so far or None if not yet
1179 Returns None if no changes have been detected and a dict with two keys,
1180 ``job_info`` and ``log_entries`` otherwise.
1188 It supports the following commands: ``GET``.
1193 Returns a list of all nodes.
1199 "id": "node1.example.com",
1200 "uri": "\/nodes\/node1.example.com"
1203 "id": "node2.example.com",
1204 "uri": "\/nodes\/node2.example.com"
1208 If the optional bool *bulk* argument is provided and set to a true value
1209 (i.e ``?bulk=1``), the output contains detailed information about nodes
1212 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.N_FIELDS))`
1221 "name": "www.example.com",
1232 ``/2/nodes/[node_name]``
1233 +++++++++++++++++++++++++++++++++
1235 Returns information about a node.
1237 It supports the following commands: ``GET``.
1239 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.N_FIELDS))`
1241 ``/2/nodes/[node_name]/evacuate``
1242 +++++++++++++++++++++++++++++++++
1244 Evacuates instances off a node.
1246 It supports the following commands: ``POST``.
1251 Returns a job ID. The result of the job will contain the IDs of the
1252 individual jobs submitted to evacuate the node.
1256 .. opcode_params:: OP_NODE_EVACUATE
1259 Up to and including Ganeti 2.4 query arguments were used. Those are no
1260 longer supported. The new request can be detected by the presence of the
1261 :pyeval:`rlib2._NODE_EVAC_RES1` feature string.
1265 .. opcode_result:: OP_NODE_EVACUATE
1268 ``/2/nodes/[node_name]/migrate``
1269 +++++++++++++++++++++++++++++++++
1271 Migrates all primary instances from a node.
1273 It supports the following commands: ``POST``.
1278 If no mode is explicitly specified, each instances' hypervisor default
1279 migration mode will be used. Body parameters:
1281 .. opcode_params:: OP_NODE_MIGRATE
1284 The query arguments used up to and including Ganeti 2.4 are deprecated
1285 and should no longer be used. The new request format can be detected by
1286 the presence of the :pyeval:`rlib2._NODE_MIGRATE_REQV1` feature string.
1289 ``/2/nodes/[node_name]/role``
1290 +++++++++++++++++++++++++++++
1294 It supports the following commands: ``GET``, ``PUT``.
1296 The role is always one of the following:
1303 Note that the 'master' role is a special, and currently it can't be
1304 modified via RAPI, only via the command line (``gnt-cluster
1310 Returns the current node role.
1319 Change the node role.
1321 The request is a string which should be PUT to this URI. The result will
1324 It supports the bool ``force`` argument.
1326 ``/2/nodes/[node_name]/storage``
1327 ++++++++++++++++++++++++++++++++
1329 Manages storage units on the node.
1336 constants.VALID_STORAGE_TYPES == set([constants.ST_FILE,
1337 constants.ST_LVM_PV,
1338 constants.ST_LVM_VG])
1340 Requests a list of storage units on a node. Requires the parameters
1341 ``storage_type`` (one of :pyeval:`constants.ST_FILE`,
1342 :pyeval:`constants.ST_LVM_PV` or :pyeval:`constants.ST_LVM_VG`) and
1343 ``output_fields``. The result will be a job id, using which the result
1346 ``/2/nodes/[node_name]/storage/modify``
1347 +++++++++++++++++++++++++++++++++++++++
1349 Modifies storage units on the node.
1354 Modifies parameters of storage units on the node. Requires the
1355 parameters ``storage_type`` (one of :pyeval:`constants.ST_FILE`,
1356 :pyeval:`constants.ST_LVM_PV` or :pyeval:`constants.ST_LVM_VG`)
1357 and ``name`` (name of the storage unit). Parameters can be passed
1358 additionally. Currently only :pyeval:`constants.SF_ALLOCATABLE` (bool)
1359 is supported. The result will be a job id.
1361 ``/2/nodes/[node_name]/storage/repair``
1362 +++++++++++++++++++++++++++++++++++++++
1364 Repairs a storage unit on the node.
1371 constants.VALID_STORAGE_OPERATIONS == {
1372 constants.ST_LVM_VG: set([constants.SO_FIX_CONSISTENCY]),
1375 Repairs a storage unit on the node. Requires the parameters
1376 ``storage_type`` (currently only :pyeval:`constants.ST_LVM_VG` can be
1377 repaired) and ``name`` (name of the storage unit). The result will be a
1380 ``/2/nodes/[node_name]/tags``
1381 +++++++++++++++++++++++++++++
1383 Manages per-node tags.
1385 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1390 Returns a list of tags.
1394 ["tag1", "tag2", "tag3"]
1401 The request as a list of strings should be PUT to this URI. The result
1404 It supports the ``dry-run`` argument.
1411 In order to delete a set of tags, the DELETE request should be addressed
1414 /tags?tag=[tag]&tag=[tag]
1416 It supports the ``dry-run`` argument.
1419 ``/2/query/[resource]``
1420 +++++++++++++++++++++++
1422 Requests resource information. Available fields can be found in man
1423 pages and using ``/2/query/[resource]/fields``. The resource is one of
1424 :pyeval:`utils.CommaJoin(constants.QR_VIA_RAPI)`. See the :doc:`query2
1425 design document <design-query2>` for more details.
1427 Supports the following commands: ``GET``, ``PUT``.
1432 Returns list of included fields and actual data. Takes a query parameter
1433 named "fields", containing a comma-separated list of field names. Does
1434 not support filtering.
1439 Returns list of included fields and actual data. The list of requested
1440 fields can either be given as the query parameter "fields" or as a body
1441 parameter with the same name. The optional body parameter "filter" can
1442 be given and must be either ``null`` or a list containing filter
1446 ``/2/query/[resource]/fields``
1447 ++++++++++++++++++++++++++++++
1449 Request list of available fields for a resource. The resource is one of
1450 :pyeval:`utils.CommaJoin(constants.QR_VIA_RAPI)`. See the
1451 :doc:`query2 design document <design-query2>` for more details.
1453 Supports the following commands: ``GET``.
1458 Returns a list of field descriptions for available fields. Takes an
1459 optional query parameter named "fields", containing a comma-separated
1460 list of field names.
1468 It supports the following commands: ``GET``.
1473 Return a list of all OSes.
1475 Can return error 500 in case of a problem. Since this is a costly
1476 operation for Ganeti 2.0, it is not recommended to execute it too often.
1485 Manages cluster tags.
1487 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1492 Returns the cluster tags.
1496 ["tag1", "tag2", "tag3"]
1503 The request as a list of strings should be PUT to this URI. The result
1506 It supports the ``dry-run`` argument.
1514 In order to delete a set of tags, the DELETE request should be addressed
1517 /tags?tag=[tag]&tag=[tag]
1519 It supports the ``dry-run`` argument.
1525 The version resource.
1527 This resource should be used to determine the remote API version and to
1528 adapt clients accordingly.
1530 It supports the following commands: ``GET``.
1535 Returns the remote API version. Ganeti 1.2 returned ``1`` and Ganeti 2.0
1538 .. vim: set textwidth=72 :