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
333 ``instance-create-reqv1``
334 Instance creation request data version 1 supported.
335 ``instance-reinstall-reqv1``
336 Instance reinstall supports body parameters.
340 ++++++++++++++++++++++++++++++++++++++++
342 Modifies cluster parameters.
344 Supports the following commands: ``PUT``.
355 ``enabled_hypervisors`` (list)
356 List of enabled hypervisors.
358 Cluster-wide hypervisor parameter defaults, hypervisor-dependent.
360 Cluster-wide backend parameter defaults.
362 Cluster-wide per-OS hypervisor parameter defaults.
364 Dictionary with OS parameters.
365 ``candidate_pool_size`` (int)
366 Master candidate pool size.
368 Set UID pool. Must be list of lists describing UID ranges (two items,
369 start and end inclusive).
371 Extend UID pool. Must be list of lists describing UID ranges (two
372 items, start and end inclusive) to be added.
374 Shrink UID pool. Must be list of lists describing UID ranges (two
375 items, start and end inclusive) to be removed.
376 ``maintain_node_health`` (bool)
377 Whether to automatically maintain node health.
378 ``prealloc_wipe_disks`` (bool)
379 Whether to wipe disks before allocating them to instances.
381 Cluster-wide NIC parameter defaults.
383 Cluster-wide node parameter defaults.
384 ``drbd_helper`` (string)
386 ``default_iallocator`` (string)
387 Default iallocator for cluster.
388 ``master_netdev`` (string)
389 Master network device.
390 ``reserved_lvs`` (list)
391 List of reserved LVs (strings).
393 List of modifications as lists. Each modification must have two items,
394 the operation and the OS name. The operation can be ``add`` or
396 ``blacklisted_os`` (list)
397 List of modifications as lists. Each modification must have two items,
398 the operation and the OS name. The operation can be ``add`` or
407 It supports the following commands: ``GET``, ``POST``.
412 Returns a list of all existing node groups.
419 "uri": "\/2\/groups\/group1"
423 "uri": "\/2\/groups\/group2"
427 If the optional bool *bulk* argument is provided and set to a true value
428 (i.e ``?bulk=1``), the output contains detailed information about node
441 "uuid": "0d7d407c-262e-49af-881a-6a430034bf43"
449 "uuid": "f5a277e7-68f9-44d3-a378-4b25ecb5df5c"
456 Creates a node group.
458 If the optional bool *dry-run* argument is provided, the job will not be
459 actually executed, only the pre-execution checks will be done.
461 Returns: a job ID that can be used later for polling.
465 ``name`` (string, required)
469 ``/2/groups/[group_name]``
470 ++++++++++++++++++++++++++
472 Returns information about a node group.
474 It supports the following commands: ``GET``, ``DELETE``.
479 Returns information about a node group, similar to the bulk output from
485 Deletes a node group.
487 It supports the ``dry-run`` argument.
490 ``/2/groups/[group_name]/modify``
491 +++++++++++++++++++++++++++++++++
493 Modifies the parameters of a node group.
495 Supports the following commands: ``PUT``.
504 ``alloc_policy`` (string)
505 If present, the new allocation policy for the node group.
508 ``/2/groups/[group_name]/rename``
509 +++++++++++++++++++++++++++++++++
511 Renames a node group.
513 Supports the following commands: ``PUT``.
522 ``new_name`` (string, required)
526 ``/2/groups/[group_name]/assign-nodes``
527 +++++++++++++++++++++++++++++++++++++++
529 Assigns nodes to a group.
531 Supports the following commands: ``PUT``.
536 Returns a job ID. It supports the ``dry-run`` and ``force`` arguments.
540 ``nodes`` (list, required)
541 One or more nodes to assign to the group.
547 The instances resource.
549 It supports the following commands: ``GET``, ``POST``.
554 Returns a list of all available instances.
560 "name": "web.example.com",
561 "uri": "\/instances\/web.example.com"
564 "name": "mail.example.com",
565 "uri": "\/instances\/mail.example.com"
569 If the optional bool *bulk* argument is provided and set to a true value
570 (i.e ``?bulk=1``), the output contains detailed information about
582 "name": "web.example.com",
583 "tags": ["tag1", "tag2"],
591 "pnode": "node1.example.com",
592 "nic.macs": ["01:23:45:67:89:01"],
593 "snodes": ["node2.example.com"],
594 "disk_template": "drbd",
608 If the optional bool *dry-run* argument is provided, the job will not be
609 actually executed, only the pre-execution checks will be done. Query-ing
610 the job result will return, in both dry-run and normal case, the list of
611 nodes selected for the instance.
613 Returns: a job ID that can be used later for polling.
617 ``__version__`` (int, required)
618 Must be ``1`` (older Ganeti versions used a different format for
619 instance creation requests, version ``0``, but that format is not
621 ``mode`` (string, required)
622 Instance creation mode.
623 ``name`` (string, required)
625 ``disk_template`` (string, required)
626 Disk template for instance.
627 ``disks`` (list, required)
628 List of disk definitions. Example: ``[{"size": 100}, {"size": 5}]``.
629 Each disk definition must contain a ``size`` value and can contain an
630 optional ``mode`` value denoting the disk access mode (``ro`` or
632 ``nics`` (list, required)
633 List of NIC (network interface) definitions. Example: ``[{}, {},
634 {"ip": "198.51.100.4"}]``. Each NIC definition can contain the
635 optional values ``ip``, ``mode``, ``link`` and ``bridge``.
636 ``os`` (string, required)
637 Instance operating system.
638 ``osparams`` (dictionary)
639 Dictionary with OS parameters. If not valid for the given OS, the job
641 ``force_variant`` (bool)
642 Whether to force an unknown variant.
643 ``no_install`` (bool)
644 Do not install the OS (will enable no-start)
649 ``src_node`` (string)
650 Source node for import.
651 ``src_path`` (string)
652 Source directory for import.
654 Whether to start instance after creation.
656 Whether to ensure instance's IP address is inactive.
657 ``name_check`` (bool)
658 Whether to ensure instance's name is resolvable.
659 ``file_storage_dir`` (string)
660 File storage directory.
661 ``file_driver`` (string)
663 ``iallocator`` (string)
664 Instance allocator name.
665 ``source_handshake`` (list)
666 Signed handshake from source (remote import only).
667 ``source_x509_ca`` (string)
668 Source X509 CA in PEM format (remote import only).
669 ``source_instance_name`` (string)
670 Source instance name (remote import only).
671 ``hypervisor`` (string)
674 Hypervisor parameters, hypervisor-dependent.
679 ``/2/instances/[instance_name]``
680 ++++++++++++++++++++++++++++++++
682 Instance-specific resource.
684 It supports the following commands: ``GET``, ``DELETE``.
689 Returns information about an instance, similar to the bulk output from
697 It supports the ``dry-run`` argument.
700 ``/2/instances/[instance_name]/info``
701 +++++++++++++++++++++++++++++++++++++++
703 It supports the following commands: ``GET``.
708 Requests detailed information about the instance. An optional parameter,
709 ``static`` (bool), can be set to return only static information from the
710 configuration without querying the instance's nodes. The result will be
714 ``/2/instances/[instance_name]/reboot``
715 +++++++++++++++++++++++++++++++++++++++
717 Reboots URI for an instance.
719 It supports the following commands: ``POST``.
724 Reboots the instance.
726 The URI takes optional ``type=soft|hard|full`` and
727 ``ignore_secondaries=0|1`` parameters.
729 ``type`` defines the reboot type. ``soft`` is just a normal reboot,
730 without terminating the hypervisor. ``hard`` means full shutdown
731 (including terminating the hypervisor process) and startup again.
732 ``full`` is like ``hard`` but also recreates the configuration from
733 ground up as if you would have done a ``gnt-instance shutdown`` and
734 ``gnt-instance start`` on it.
736 ``ignore_secondaries`` is a bool argument indicating if we start the
737 instance even if secondary disks are failing.
739 It supports the ``dry-run`` argument.
742 ``/2/instances/[instance_name]/shutdown``
743 +++++++++++++++++++++++++++++++++++++++++
745 Instance shutdown URI.
747 It supports the following commands: ``PUT``.
752 Shutdowns an instance.
754 It supports the ``dry-run`` argument.
757 ``/2/instances/[instance_name]/startup``
758 ++++++++++++++++++++++++++++++++++++++++
760 Instance startup URI.
762 It supports the following commands: ``PUT``.
769 The URI takes an optional ``force=1|0`` parameter to start the
770 instance even if secondary disks are failing.
772 It supports the ``dry-run`` argument.
774 ``/2/instances/[instance_name]/reinstall``
775 ++++++++++++++++++++++++++++++++++++++++++++++
777 Installs the operating system again.
779 It supports the following commands: ``POST``.
788 ``os`` (string, required)
789 Instance operating system.
790 ``start`` (bool, defaults to true)
791 Whether to start instance after reinstallation.
793 Dictionary with (temporary) OS parameters.
795 For backwards compatbility, this resource also takes the query
796 parameters ``os`` (OS template name) and ``nostartup`` (bool). New
797 clients should use the body parameters.
800 ``/2/instances/[instance_name]/replace-disks``
801 ++++++++++++++++++++++++++++++++++++++++++++++
803 Replaces disks on an instance.
805 It supports the following commands: ``POST``.
810 Takes the parameters ``mode`` (one of ``replace_on_primary``,
811 ``replace_on_secondary``, ``replace_new_secondary`` or
812 ``replace_auto``), ``disks`` (comma separated list of disk indexes),
813 ``remote_node`` and ``iallocator``.
815 Either ``remote_node`` or ``iallocator`` needs to be defined when using
816 ``mode=replace_new_secondary``.
818 ``mode`` is a mandatory parameter. ``replace_auto`` tries to determine
819 the broken disk(s) on its own and replacing it.
822 ``/2/instances/[instance_name]/activate-disks``
823 +++++++++++++++++++++++++++++++++++++++++++++++
825 Activate disks on an instance.
827 It supports the following commands: ``PUT``.
832 Takes the bool parameter ``ignore_size``. When set ignore the recorded
833 size (useful for forcing activation when recorded size is wrong).
836 ``/2/instances/[instance_name]/deactivate-disks``
837 +++++++++++++++++++++++++++++++++++++++++++++++++
839 Deactivate disks on an instance.
841 It supports the following commands: ``PUT``.
849 ``/2/instances/[instance_name]/disk/[disk_index]/grow``
850 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
852 Grows one disk of an instance.
854 Supports the following commands: ``POST``.
863 ``amount`` (int, required)
864 Amount of disk space to add.
865 ``wait_for_sync`` (bool)
866 Whether to wait for the disk to synchronize.
869 ``/2/instances/[instance_name]/prepare-export``
870 +++++++++++++++++++++++++++++++++++++++++++++++++
872 Prepares an export of an instance.
874 It supports the following commands: ``PUT``.
879 Takes one parameter, ``mode``, for the export mode. Returns a job ID.
882 ``/2/instances/[instance_name]/export``
883 +++++++++++++++++++++++++++++++++++++++++++++++++
887 It supports the following commands: ``PUT``.
898 ``destination`` (required)
899 Destination information, depends on export mode.
900 ``shutdown`` (bool, required)
901 Whether to shutdown instance before export.
902 ``remove_instance`` (bool)
903 Whether to remove instance after export.
905 Name of X509 key (remote export only).
906 ``destination_x509_ca``
907 Destination X509 CA (remote export only).
910 ``/2/instances/[instance_name]/migrate``
911 ++++++++++++++++++++++++++++++++++++++++
913 Migrates an instance.
915 Supports the following commands: ``PUT``.
927 Whether a previously failed migration should be cleaned up.
930 ``/2/instances/[instance_name]/rename``
931 ++++++++++++++++++++++++++++++++++++++++
935 Supports the following commands: ``PUT``.
944 ``new_name`` (string, required)
947 Whether to ensure instance's IP address is inactive.
948 ``name_check`` (bool)
949 Whether to ensure instance's name is resolvable.
952 ``/2/instances/[instance_name]/modify``
953 ++++++++++++++++++++++++++++++++++++++++
955 Modifies an instance.
957 Supports the following commands: ``PUT``.
967 Dictionary with OS parameters.
969 Hypervisor parameters, hypervisor-dependent.
973 Whether to force the operation.
975 List of NIC changes. Each item is of the form ``(op, settings)``.
976 ``op`` can be ``add`` to add a new NIC with the specified settings,
977 ``remove`` to remove the last NIC or a number to modify the settings
978 of the NIC with that index.
980 List of disk changes. See ``nics``.
981 ``disk_template`` (string)
982 Disk template for instance.
983 ``remote_node`` (string)
984 Secondary node (used when changing disk template).
986 Change instance's OS name. Does not reinstall the instance.
987 ``force_variant`` (bool)
988 Whether to force an unknown variant.
991 ``/2/instances/[instance_name]/console``
992 ++++++++++++++++++++++++++++++++++++++++
994 Request information for connecting to instance's console.
996 Supports the following commands: ``GET``.
1001 Returns a dictionary containing information about the instance's
1002 console. Contained keys:
1007 Console type, one of ``ssh``, ``vnc`` or ``msg``.
1009 Message to display (``msg`` type only).
1011 Host to connect to (``ssh`` and ``vnc`` only).
1013 TCP port to connect to (``vnc`` only).
1015 Username to use (``ssh`` only).
1017 Command to execute on machine (``ssh`` only)
1019 VNC display number (``vnc`` only).
1022 ``/2/instances/[instance_name]/tags``
1023 +++++++++++++++++++++++++++++++++++++
1025 Manages per-instance tags.
1027 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1032 Returns a list of tags.
1036 ["tag1", "tag2", "tag3"]
1043 The request as a list of strings should be ``PUT`` to this URI. The
1044 result will be a job id.
1046 It supports the ``dry-run`` argument.
1054 In order to delete a set of tags, the DELETE request should be addressed
1057 /tags?tag=[tag]&tag=[tag]
1059 It supports the ``dry-run`` argument.
1065 The ``/2/jobs`` resource.
1067 It supports the following commands: ``GET``.
1072 Returns a dictionary of jobs.
1074 Returns: a dictionary with jobs id and uri.
1076 ``/2/jobs/[job_id]``
1077 ++++++++++++++++++++
1082 It supports the following commands: ``GET``, ``DELETE``.
1087 Returns a job status.
1089 Returns: a dictionary with job parameters.
1091 The result includes:
1093 - id: job ID as a number
1094 - status: current job status as a string
1095 - ops: involved OpCodes as a list of dictionaries for each opcodes in
1097 - opstatus: OpCodes status as a list
1098 - opresult: OpCodes results as a list
1100 For a successful opcode, the ``opresult`` field corresponding to it will
1101 contain the raw result from its :term:`LogicalUnit`. In case an opcode
1102 has failed, its element in the opresult list will be a list of two
1105 - first element the error type (the Ganeti internal error name)
1106 - second element a list of either one or two elements:
1108 - the first element is the textual error description
1109 - the second element, if any, will hold an error classification
1111 The error classification is most useful for the ``OpPrereqError``
1112 error type - these errors happen before the OpCode has started
1113 executing, so it's possible to retry the OpCode without side
1114 effects. But whether it make sense to retry depends on the error
1118 Resolver errors. This usually means that a name doesn't exist in DNS,
1119 so if it's a case of slow DNS propagation the operation can be retried
1122 ``insufficient_resources``
1123 Not enough resources (iallocator failure, disk space, memory,
1124 etc.). If the resources on the cluster increase, the operation might
1128 Wrong arguments (at syntax level). The operation will not ever be
1129 accepted unless the arguments change.
1132 Wrong entity state. For example, live migration has been requested for
1133 a down instance, or instance creation on an offline node. The
1134 operation can be retried once the resource has changed state.
1137 Entity not found. For example, information has been requested for an
1141 Entity already exists. For example, instance creation has been
1142 requested for an already-existing instance.
1144 ``resource_not_unique``
1145 Resource not unique (e.g. MAC or IP duplication).
1148 Internal cluster error. For example, a node is unreachable but not set
1149 offline, or the ganeti node daemons are not working, etc. A
1150 ``gnt-cluster verify`` should be run.
1152 ``environment_error``
1153 Environment error (e.g. node disk error). A ``gnt-cluster verify``
1156 Note that in the above list, by entity we refer to a node or instance,
1157 while by a resource we refer to an instance's disk, or NIC, etc.
1163 Cancel a not-yet-started job.
1166 ``/2/jobs/[job_id]/wait``
1167 +++++++++++++++++++++++++
1172 Waits for changes on a job. Takes the following body parameters in a
1176 The job fields on which to watch for changes.
1178 ``previous_job_info``
1179 Previously received field values or None if not yet available.
1181 ``previous_log_serial``
1182 Highest log serial number received so far or None if not yet
1185 Returns None if no changes have been detected and a dict with two keys,
1186 ``job_info`` and ``log_entries`` otherwise.
1194 It supports the following commands: ``GET``.
1199 Returns a list of all nodes.
1205 "id": "node1.example.com",
1206 "uri": "\/nodes\/node1.example.com"
1209 "id": "node2.example.com",
1210 "uri": "\/nodes\/node2.example.com"
1214 If the optional 'bulk' argument is provided and set to 'true' value (i.e
1215 '?bulk=1'), the output contains detailed information about nodes as a
1225 "name": "www.example.com",
1236 ``/2/nodes/[node_name]``
1237 +++++++++++++++++++++++++++++++++
1239 Returns information about a node.
1241 It supports the following commands: ``GET``.
1243 ``/2/nodes/[node_name]/evacuate``
1244 +++++++++++++++++++++++++++++++++
1246 Evacuates all secondary instances off a node.
1248 It supports the following commands: ``POST``.
1253 To evacuate a node, either one of the ``iallocator`` or ``remote_node``
1254 parameters must be passed::
1256 evacuate?iallocator=[iallocator]
1257 evacuate?remote_node=[nodeX.example.com]
1259 The result value will be a list, each element being a triple of the job
1260 id (for this specific evacuation), the instance which is being evacuated
1261 by this job, and the node to which it is being relocated. In case the
1262 node is already empty, the result will be an empty list (without any
1263 jobs being submitted).
1265 And additional parameter ``early_release`` signifies whether to try to
1266 parallelize the evacuations, at the risk of increasing I/O contention
1267 and increasing the chances of data loss, if the primary node of any of
1268 the instances being evacuated is not fully healthy.
1270 If the dry-run parameter was specified, then the evacuation jobs were
1271 not actually submitted, and the job IDs will be null.
1274 ``/2/nodes/[node_name]/migrate``
1275 +++++++++++++++++++++++++++++++++
1277 Migrates all primary instances from a node.
1279 It supports the following commands: ``POST``.
1284 If no mode is explicitly specified, each instances' hypervisor default
1285 migration mode will be used. Query parameters:
1288 If set, use live migration if available.
1290 Sets migration mode, ``live`` for live migration and ``non-live`` for
1291 non-live migration. Supported by Ganeti 2.2 and above.
1294 ``/2/nodes/[node_name]/role``
1295 +++++++++++++++++++++++++++++
1299 It supports the following commands: ``GET``, ``PUT``.
1301 The role is always one of the following:
1308 Note that the 'master' role is a special, and currently it can't be
1309 modified via RAPI, only via the command line (``gnt-cluster
1315 Returns the current node role.
1324 Change the node role.
1326 The request is a string which should be PUT to this URI. The result will
1329 It supports the bool ``force`` argument.
1331 ``/2/nodes/[node_name]/storage``
1332 ++++++++++++++++++++++++++++++++
1334 Manages storage units on the node.
1339 Requests a list of storage units on a node. Requires the parameters
1340 ``storage_type`` (one of ``file``, ``lvm-pv`` or ``lvm-vg``) and
1341 ``output_fields``. The result will be a job id, using which the result
1344 ``/2/nodes/[node_name]/storage/modify``
1345 +++++++++++++++++++++++++++++++++++++++
1347 Modifies storage units on the node.
1352 Modifies parameters of storage units on the node. Requires the
1353 parameters ``storage_type`` (one of ``file``, ``lvm-pv`` or ``lvm-vg``)
1354 and ``name`` (name of the storage unit). Parameters can be passed
1355 additionally. Currently only ``allocatable`` (bool) is supported. The
1356 result will be a job id.
1358 ``/2/nodes/[node_name]/storage/repair``
1359 +++++++++++++++++++++++++++++++++++++++
1361 Repairs a storage unit on the node.
1366 Repairs a storage unit on the node. Requires the parameters
1367 ``storage_type`` (currently only ``lvm-vg`` can be repaired) and
1368 ``name`` (name of the storage unit). The result will be a job id.
1370 ``/2/nodes/[node_name]/tags``
1371 +++++++++++++++++++++++++++++
1373 Manages per-node tags.
1375 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1380 Returns a list of tags.
1384 ["tag1", "tag2", "tag3"]
1391 The request as a list of strings should be PUT to this URI. The result
1394 It supports the ``dry-run`` argument.
1401 In order to delete a set of tags, the DELETE request should be addressed
1404 /tags?tag=[tag]&tag=[tag]
1406 It supports the ``dry-run`` argument.
1414 It supports the following commands: ``GET``.
1419 Return a list of all OSes.
1421 Can return error 500 in case of a problem. Since this is a costly
1422 operation for Ganeti 2.0, it is not recommended to execute it too often.
1431 Manages cluster tags.
1433 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1438 Returns the cluster tags.
1442 ["tag1", "tag2", "tag3"]
1449 The request as a list of strings should be PUT to this URI. The result
1452 It supports the ``dry-run`` argument.
1460 In order to delete a set of tags, the DELETE request should be addressed
1463 /tags?tag=[tag]&tag=[tag]
1465 It supports the ``dry-run`` argument.
1471 The version resource.
1473 This resource should be used to determine the remote API version and to
1474 adapt clients accordingly.
1476 It supports the following commands: ``GET``.
1481 Returns the remote API version. Ganeti 1.2 returned ``1`` and Ganeti 2.0
1484 .. vim: set textwidth=72 :