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
74 A note on JSON as used by RAPI
75 ++++++++++++++++++++++++++++++
77 JSON_ as used by Ganeti RAPI does not conform to the specification in
78 :rfc:`4627`. Section 2 defines a JSON text to be either an object
79 (``{"key": "value", …}``) or an array (``[1, 2, 3, …]``). In violation
80 of this RAPI uses plain strings (``"master-candidate"``, ``"1234"``) for
81 some requests or responses. Changing this now would likely break
82 existing clients and cause a lot of trouble.
86 Unlike Python's `JSON encoder and decoder
87 <http://docs.python.org/library/json.html>`_, other programming
88 languages or libraries may only provide a strict implementation, not
89 allowing plain values. For those, responses can usually be wrapped in an
90 array whose first element is then used, e.g. the response ``"1234"``
91 becomes ``["1234"]``. This works equally well for more complex values.
96 # Insert code to get response here
99 decoded = JSON.parse("[#{response}]").first
101 Short of modifying the encoder to allow encoding to a less strict
102 format, requests will have to be formatted by hand. Newer RAPI requests
103 already use a dictionary as their input data and shouldn't cause any
110 According to :rfc:`2616` the main difference between PUT and POST is
111 that POST can create new resources but PUT can only create the resource
112 the URI was pointing to on the PUT request.
114 Unfortunately, due to historic reasons, the Ganeti RAPI library is not
115 consistent with this usage, so just use the methods as documented below
118 For more details have a look in the source code at
119 ``lib/rapi/rlib2.py``.
122 Generic parameter types
123 -----------------------
125 A few generic refered parameter types and the values they allow.
130 A boolean option will accept ``1`` or ``0`` as numbers but not
131 i.e. ``True`` or ``False``.
136 A few parameter mean the same thing across all resources which implement
142 Bulk-mode means that for the resources which usually return just a list
143 of child resources (e.g. ``/2/instances`` which returns just instance
144 names), the output will instead contain detailed data for all these
145 subresources. This is more efficient than query-ing the sub-resources
151 The boolean *dry-run* argument, if provided and set, signals to Ganeti
152 that the job should not be executed, only the pre-execution checks will
155 This is useful in trying to determine (without guarantees though, as in
156 the meantime the cluster state could have changed) if the operation is
157 likely to succeed or at least start executing.
162 Force operation to continue even if it will cause the cluster to become
163 inconsistent (e.g. because there are not enough master candidates).
168 You can access the API using your favorite programming language as long
169 as it supports network connections.
174 Ganeti includes a standalone RAPI client, ``lib/rapi/client.py``.
183 wget -q -O - https://CLUSTERNAME:5080/2/info
187 curl https://CLUSTERNAME:5080/2/info
193 .. highlight:: python
198 f = urllib2.urlopen('https://CLUSTERNAME:5080/2/info')
205 .. warning:: While it's possible to use JavaScript, it poses several
206 potential problems, including browser blocking request due to
207 non-standard ports or different domain names. Fetching the data on
208 the webserver is easier.
210 .. highlight:: javascript
214 var url = 'https://CLUSTERNAME:5080/2/info';
216 var xmlreq = new XMLHttpRequest();
217 xmlreq.onreadystatechange = function () {
218 if (xmlreq.readyState != 4) return;
219 if (xmlreq.status == 200) {
220 info = eval("(" + xmlreq.responseText + ")");
223 alert('Error fetching cluster info');
227 xmlreq.open('GET', url, true);
233 .. highlight:: javascript
240 It supports the following commands: ``GET``.
245 Shows the list of mapped resources.
247 Returns: a dictionary with 'name' and 'uri' keys for each of them.
252 The ``/2`` resource, the root of the version 2 API.
254 It supports the following commands: ``GET``.
259 Show the list of mapped resources.
261 Returns: a dictionary with ``name`` and ``uri`` keys for each of them.
266 Cluster information resource.
268 It supports the following commands: ``GET``.
273 Returns cluster information.
278 "config_version": 2000000,
280 "software_version": "2.0.0~beta2",
281 "os_api_version": 10,
283 "candidate_pool_size": 10,
284 "enabled_hypervisors": [
290 "default_hypervisor": "fake",
291 "master": "node1.example.com",
296 "protocol_version": 20,
299 "auto_balance": true,
307 ``/2/redistribute-config``
308 ++++++++++++++++++++++++++
310 Redistribute configuration to all nodes.
312 It supports the following commands: ``PUT``.
317 Redistribute configuration to all nodes. The result will be a job id.
326 Returns a list of features supported by the RAPI server. Available
329 ``instance-create-reqv1``
330 Instance creation request data version 1 supported.
331 ``instance-reinstall-reqv1``
332 Instance reinstall supports body parameters.
340 It supports the following commands: ``GET``.
345 Returns a list of all existing node groups.
352 "uri": "\/2\/groups\/group1"
356 "uri": "\/2\/groups\/group2"
360 If the optional bool *bulk* argument is provided and set to a true value
361 (i.e ``?bulk=1``), the output contains detailed information about node
374 "uuid": "0d7d407c-262e-49af-881a-6a430034bf43"
382 "uuid": "f5a277e7-68f9-44d3-a378-4b25ecb5df5c"
386 ``/2/groups/[group_name]``
387 +++++++++++++++++++++++++++++++++
389 Returns information about a node group.
391 It supports the following commands: ``GET``.
397 The instances resource.
399 It supports the following commands: ``GET``, ``POST``.
404 Returns a list of all available instances.
410 "name": "web.example.com",
411 "uri": "\/instances\/web.example.com"
414 "name": "mail.example.com",
415 "uri": "\/instances\/mail.example.com"
419 If the optional bool *bulk* argument is provided and set to a true value
420 (i.e ``?bulk=1``), the output contains detailed information about
432 "name": "web.example.com",
433 "tags": ["tag1", "tag2"],
441 "pnode": "node1.example.com",
442 "nic.macs": ["01:23:45:67:89:01"],
443 "snodes": ["node2.example.com"],
444 "disk_template": "drbd",
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. Query-ing
460 the job result will return, in both dry-run and normal case, the list of
461 nodes selected for the instance.
463 Returns: a job ID that can be used later for polling.
467 ``__version__`` (int, required)
468 Must be ``1`` (older Ganeti versions used a different format for
469 instance creation requests, version ``0``, but that format is not
471 ``mode`` (string, required)
472 Instance creation mode.
473 ``name`` (string, required)
475 ``disk_template`` (string, required)
476 Disk template for instance.
477 ``disks`` (list, required)
478 List of disk definitions. Example: ``[{"size": 100}, {"size": 5}]``.
479 Each disk definition must contain a ``size`` value and can contain an
480 optional ``mode`` value denoting the disk access mode (``ro`` or
482 ``nics`` (list, required)
483 List of NIC (network interface) definitions. Example: ``[{}, {},
484 {"ip": "198.51.100.4"}]``. Each NIC definition can contain the
485 optional values ``ip``, ``mode``, ``link`` and ``bridge``.
486 ``os`` (string, required)
487 Instance operating system.
488 ``osparams`` (dictionary)
489 Dictionary with OS parameters. If not valid for the given OS, the job
491 ``force_variant`` (bool)
492 Whether to force an unknown variant.
493 ``no_install`` (bool)
494 Do not install the OS (will enable no-start)
499 ``src_node`` (string)
500 Source node for import.
501 ``src_path`` (string)
502 Source directory for import.
504 Whether to start instance after creation.
506 Whether to ensure instance's IP address is inactive.
507 ``name_check`` (bool)
508 Whether to ensure instance's name is resolvable.
509 ``file_storage_dir`` (string)
510 File storage directory.
511 ``file_driver`` (string)
513 ``iallocator`` (string)
514 Instance allocator name.
515 ``source_handshake`` (list)
516 Signed handshake from source (remote import only).
517 ``source_x509_ca`` (string)
518 Source X509 CA in PEM format (remote import only).
519 ``source_instance_name`` (string)
520 Source instance name (remote import only).
521 ``hypervisor`` (string)
524 Hypervisor parameters, hypervisor-dependent.
529 ``/2/instances/[instance_name]``
530 ++++++++++++++++++++++++++++++++
532 Instance-specific resource.
534 It supports the following commands: ``GET``, ``DELETE``.
539 Returns information about an instance, similar to the bulk output from
547 It supports the ``dry-run`` argument.
550 ``/2/instances/[instance_name]/info``
551 +++++++++++++++++++++++++++++++++++++++
553 It supports the following commands: ``GET``.
558 Requests detailed information about the instance. An optional parameter,
559 ``static`` (bool), can be set to return only static information from the
560 configuration without querying the instance's nodes. The result will be
564 ``/2/instances/[instance_name]/reboot``
565 +++++++++++++++++++++++++++++++++++++++
567 Reboots URI for an instance.
569 It supports the following commands: ``POST``.
574 Reboots the instance.
576 The URI takes optional ``type=soft|hard|full`` and
577 ``ignore_secondaries=0|1`` parameters.
579 ``type`` defines the reboot type. ``soft`` is just a normal reboot,
580 without terminating the hypervisor. ``hard`` means full shutdown
581 (including terminating the hypervisor process) and startup again.
582 ``full`` is like ``hard`` but also recreates the configuration from
583 ground up as if you would have done a ``gnt-instance shutdown`` and
584 ``gnt-instance start`` on it.
586 ``ignore_secondaries`` is a bool argument indicating if we start the
587 instance even if secondary disks are failing.
589 It supports the ``dry-run`` argument.
592 ``/2/instances/[instance_name]/shutdown``
593 +++++++++++++++++++++++++++++++++++++++++
595 Instance shutdown URI.
597 It supports the following commands: ``PUT``.
602 Shutdowns an instance.
604 It supports the ``dry-run`` argument.
607 ``/2/instances/[instance_name]/startup``
608 ++++++++++++++++++++++++++++++++++++++++
610 Instance startup URI.
612 It supports the following commands: ``PUT``.
619 The URI takes an optional ``force=1|0`` parameter to start the
620 instance even if secondary disks are failing.
622 It supports the ``dry-run`` argument.
624 ``/2/instances/[instance_name]/reinstall``
625 ++++++++++++++++++++++++++++++++++++++++++++++
627 Installs the operating system again.
629 It supports the following commands: ``POST``.
638 ``os`` (string, required)
639 Instance operating system.
640 ``start`` (bool, defaults to true)
641 Whether to start instance after reinstallation.
643 Dictionary with (temporary) OS parameters.
645 For backwards compatbility, this resource also takes the query
646 parameters ``os`` (OS template name) and ``nostartup`` (bool). New
647 clients should use the body parameters.
650 ``/2/instances/[instance_name]/replace-disks``
651 ++++++++++++++++++++++++++++++++++++++++++++++
653 Replaces disks on an instance.
655 It supports the following commands: ``POST``.
660 Takes the parameters ``mode`` (one of ``replace_on_primary``,
661 ``replace_on_secondary``, ``replace_new_secondary`` or
662 ``replace_auto``), ``disks`` (comma separated list of disk indexes),
663 ``remote_node`` and ``iallocator``.
665 Either ``remote_node`` or ``iallocator`` needs to be defined when using
666 ``mode=replace_new_secondary``.
668 ``mode`` is a mandatory parameter. ``replace_auto`` tries to determine
669 the broken disk(s) on its own and replacing it.
672 ``/2/instances/[instance_name]/activate-disks``
673 +++++++++++++++++++++++++++++++++++++++++++++++
675 Activate disks on an instance.
677 It supports the following commands: ``PUT``.
682 Takes the bool parameter ``ignore_size``. When set ignore the recorded
683 size (useful for forcing activation when recorded size is wrong).
686 ``/2/instances/[instance_name]/deactivate-disks``
687 +++++++++++++++++++++++++++++++++++++++++++++++++
689 Deactivate disks on an instance.
691 It supports the following commands: ``PUT``.
699 ``/2/instances/[instance_name]/prepare-export``
700 +++++++++++++++++++++++++++++++++++++++++++++++++
702 Prepares an export of an instance.
704 It supports the following commands: ``PUT``.
709 Takes one parameter, ``mode``, for the export mode. Returns a job ID.
712 ``/2/instances/[instance_name]/export``
713 +++++++++++++++++++++++++++++++++++++++++++++++++
717 It supports the following commands: ``PUT``.
728 ``destination`` (required)
729 Destination information, depends on export mode.
730 ``shutdown`` (bool, required)
731 Whether to shutdown instance before export.
732 ``remove_instance`` (bool)
733 Whether to remove instance after export.
735 Name of X509 key (remote export only).
736 ``destination_x509_ca``
737 Destination X509 CA (remote export only).
740 ``/2/instances/[instance_name]/migrate``
741 ++++++++++++++++++++++++++++++++++++++++
743 Migrates an instance.
745 Supports the following commands: ``PUT``.
757 Whether a previously failed migration should be cleaned up.
760 ``/2/instances/[instance_name]/rename``
761 ++++++++++++++++++++++++++++++++++++++++
765 Supports the following commands: ``PUT``.
774 ``new_name`` (string, required)
777 Whether to ensure instance's IP address is inactive.
778 ``name_check`` (bool)
779 Whether to ensure instance's name is resolvable.
782 ``/2/instances/[instance_name]/modify``
783 ++++++++++++++++++++++++++++++++++++++++
785 Modifies an instance.
787 Supports the following commands: ``PUT``.
797 Dictionary with OS parameters.
799 Hypervisor parameters, hypervisor-dependent.
803 Whether to force the operation.
805 List of NIC changes. Each item is of the form ``(op, settings)``.
806 ``op`` can be ``add`` to add a new NIC with the specified settings,
807 ``remove`` to remove the last NIC or a number to modify the settings
808 of the NIC with that index.
810 List of disk changes. See ``nics``.
811 ``disk_template`` (string)
812 Disk template for instance.
813 ``remote_node`` (string)
814 Secondary node (used when changing disk template).
816 Change instance's OS name. Does not reinstall the instance.
817 ``force_variant`` (bool)
818 Whether to force an unknown variant.
821 ``/2/instances/[instance_name]/tags``
822 +++++++++++++++++++++++++++++++++++++
824 Manages per-instance tags.
826 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
831 Returns a list of tags.
835 ["tag1", "tag2", "tag3"]
842 The request as a list of strings should be ``PUT`` to this URI. The
843 result will be a job id.
845 It supports the ``dry-run`` argument.
853 In order to delete a set of tags, the DELETE request should be addressed
856 /tags?tag=[tag]&tag=[tag]
858 It supports the ``dry-run`` argument.
864 The ``/2/jobs`` resource.
866 It supports the following commands: ``GET``.
871 Returns a dictionary of jobs.
873 Returns: a dictionary with jobs id and uri.
881 It supports the following commands: ``GET``, ``DELETE``.
886 Returns a job status.
888 Returns: a dictionary with job parameters.
892 - id: job ID as a number
893 - status: current job status as a string
894 - ops: involved OpCodes as a list of dictionaries for each opcodes in
896 - opstatus: OpCodes status as a list
897 - opresult: OpCodes results as a list
899 For a successful opcode, the ``opresult`` field corresponding to it will
900 contain the raw result from its :term:`LogicalUnit`. In case an opcode
901 has failed, its element in the opresult list will be a list of two
904 - first element the error type (the Ganeti internal error name)
905 - second element a list of either one or two elements:
907 - the first element is the textual error description
908 - the second element, if any, will hold an error classification
910 The error classification is most useful for the ``OpPrereqError``
911 error type - these errors happen before the OpCode has started
912 executing, so it's possible to retry the OpCode without side
913 effects. But whether it make sense to retry depends on the error
917 Resolver errors. This usually means that a name doesn't exist in DNS,
918 so if it's a case of slow DNS propagation the operation can be retried
921 ``insufficient_resources``
922 Not enough resources (iallocator failure, disk space, memory,
923 etc.). If the resources on the cluster increase, the operation might
927 Wrong arguments (at syntax level). The operation will not ever be
928 accepted unless the arguments change.
931 Wrong entity state. For example, live migration has been requested for
932 a down instance, or instance creation on an offline node. The
933 operation can be retried once the resource has changed state.
936 Entity not found. For example, information has been requested for an
940 Entity already exists. For example, instance creation has been
941 requested for an already-existing instance.
943 ``resource_not_unique``
944 Resource not unique (e.g. MAC or IP duplication).
947 Internal cluster error. For example, a node is unreachable but not set
948 offline, or the ganeti node daemons are not working, etc. A
949 ``gnt-cluster verify`` should be run.
951 ``environment_error``
952 Environment error (e.g. node disk error). A ``gnt-cluster verify``
955 Note that in the above list, by entity we refer to a node or instance,
956 while by a resource we refer to an instance's disk, or NIC, etc.
962 Cancel a not-yet-started job.
965 ``/2/jobs/[job_id]/wait``
966 +++++++++++++++++++++++++
971 Waits for changes on a job. Takes the following body parameters in a
975 The job fields on which to watch for changes.
977 ``previous_job_info``
978 Previously received field values or None if not yet available.
980 ``previous_log_serial``
981 Highest log serial number received so far or None if not yet
984 Returns None if no changes have been detected and a dict with two keys,
985 ``job_info`` and ``log_entries`` otherwise.
993 It supports the following commands: ``GET``.
998 Returns a list of all nodes.
1004 "id": "node1.example.com",
1005 "uri": "\/nodes\/node1.example.com"
1008 "id": "node2.example.com",
1009 "uri": "\/nodes\/node2.example.com"
1013 If the optional 'bulk' argument is provided and set to 'true' value (i.e
1014 '?bulk=1'), the output contains detailed information about nodes as a
1024 "name": "www.example.com",
1035 ``/2/nodes/[node_name]``
1036 +++++++++++++++++++++++++++++++++
1038 Returns information about a node.
1040 It supports the following commands: ``GET``.
1042 ``/2/nodes/[node_name]/evacuate``
1043 +++++++++++++++++++++++++++++++++
1045 Evacuates all secondary instances off a node.
1047 It supports the following commands: ``POST``.
1052 To evacuate a node, either one of the ``iallocator`` or ``remote_node``
1053 parameters must be passed::
1055 evacuate?iallocator=[iallocator]
1056 evacuate?remote_node=[nodeX.example.com]
1058 The result value will be a list, each element being a triple of the job
1059 id (for this specific evacuation), the instance which is being evacuated
1060 by this job, and the node to which it is being relocated. In case the
1061 node is already empty, the result will be an empty list (without any
1062 jobs being submitted).
1064 And additional parameter ``early_release`` signifies whether to try to
1065 parallelize the evacuations, at the risk of increasing I/O contention
1066 and increasing the chances of data loss, if the primary node of any of
1067 the instances being evacuated is not fully healthy.
1069 If the dry-run parameter was specified, then the evacuation jobs were
1070 not actually submitted, and the job IDs will be null.
1073 ``/2/nodes/[node_name]/migrate``
1074 +++++++++++++++++++++++++++++++++
1076 Migrates all primary instances from a node.
1078 It supports the following commands: ``POST``.
1083 If no mode is explicitly specified, each instances' hypervisor default
1084 migration mode will be used. Query parameters:
1087 If set, use live migration if available.
1089 Sets migration mode, ``live`` for live migration and ``non-live`` for
1090 non-live migration. Supported by Ganeti 2.2 and above.
1093 ``/2/nodes/[node_name]/role``
1094 +++++++++++++++++++++++++++++
1098 It supports the following commands: ``GET``, ``PUT``.
1100 The role is always one of the following:
1111 Returns the current node role.
1120 Change the node role.
1122 The request is a string which should be PUT to this URI. The result will
1125 It supports the bool ``force`` argument.
1127 ``/2/nodes/[node_name]/storage``
1128 ++++++++++++++++++++++++++++++++
1130 Manages storage units on the node.
1135 Requests a list of storage units on a node. Requires the parameters
1136 ``storage_type`` (one of ``file``, ``lvm-pv`` or ``lvm-vg``) and
1137 ``output_fields``. The result will be a job id, using which the result
1140 ``/2/nodes/[node_name]/storage/modify``
1141 +++++++++++++++++++++++++++++++++++++++
1143 Modifies storage units on the node.
1148 Modifies parameters of storage units on the node. Requires the
1149 parameters ``storage_type`` (one of ``file``, ``lvm-pv`` or ``lvm-vg``)
1150 and ``name`` (name of the storage unit). Parameters can be passed
1151 additionally. Currently only ``allocatable`` (bool) is supported. The
1152 result will be a job id.
1154 ``/2/nodes/[node_name]/storage/repair``
1155 +++++++++++++++++++++++++++++++++++++++
1157 Repairs a storage unit on the node.
1162 Repairs a storage unit on the node. Requires the parameters
1163 ``storage_type`` (currently only ``lvm-vg`` can be repaired) and
1164 ``name`` (name of the storage unit). The result will be a job id.
1166 ``/2/nodes/[node_name]/tags``
1167 +++++++++++++++++++++++++++++
1169 Manages per-node tags.
1171 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1176 Returns a list of tags.
1180 ["tag1", "tag2", "tag3"]
1187 The request as a list of strings should be PUT to this URI. The result
1190 It supports the ``dry-run`` argument.
1197 In order to delete a set of tags, the DELETE request should be addressed
1200 /tags?tag=[tag]&tag=[tag]
1202 It supports the ``dry-run`` argument.
1210 It supports the following commands: ``GET``.
1215 Return a list of all OSes.
1217 Can return error 500 in case of a problem. Since this is a costly
1218 operation for Ganeti 2.0, it is not recommended to execute it too often.
1227 Manages cluster tags.
1229 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1234 Returns the cluster tags.
1238 ["tag1", "tag2", "tag3"]
1245 The request as a list of strings should be PUT to this URI. The result
1248 It supports the ``dry-run`` argument.
1256 In order to delete a set of tags, the DELETE request should be addressed
1259 /tags?tag=[tag]&tag=[tag]
1261 It supports the ``dry-run`` argument.
1267 The version resource.
1269 This resource should be used to determine the remote API version and to
1270 adapt clients accordingly.
1272 It supports the following commands: ``GET``.
1277 Returns the remote API version. Ganeti 1.2 returned ``1`` and Ganeti 2.0
1280 .. vim: set textwidth=72 :