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
24 ``ganeti-rapi`` reads users and passwords from a file (usually
25 ``/var/lib/ganeti/rapi/users``) on startup. Changes to the file will be
28 Lines starting with the hash sign (``#``) are treated as comments. Each
29 line consists of two or three fields separated by whitespace. The first
30 two fields are for username and password. The third field is optional
31 and can be used to specify per-user options (separated by comma without
32 spaces). Available options:
36 rapi.RAPI_ACCESS_ALL == set([
37 rapi.RAPI_ACCESS_WRITE,
38 rapi.RAPI_ACCESS_READ,
41 :pyeval:`rapi.RAPI_ACCESS_WRITE`
42 Enables the user to execute operations modifying the cluster. Implies
43 :pyeval:`rapi.RAPI_ACCESS_READ` access.
44 :pyeval:`rapi.RAPI_ACCESS_READ`
45 Allow access to operations querying for information.
47 Passwords can either be written in clear text or as a hash. Clear text
48 passwords may not start with an opening brace (``{``) or they must be
49 prefixed with ``{cleartext}``. To use the hashed form, get the MD5 hash
50 of the string ``$username:Ganeti Remote API:$password`` (e.g. ``echo -n
51 'jack:Ganeti Remote API:abc123' | openssl md5``) [#pwhash]_ and prefix
52 it with ``{ha1}``. Using the scheme prefix for all passwords is
53 recommended. Scheme prefixes are not case sensitive.
57 # Give Jack and Fred read-only access
59 fred {cleartext}foo555
61 # Give write access to an imaginary instance creation script
62 autocreator xyz789 write
64 # Hashed password for Jessica
65 jessica {HA1}7046452df2cbb530877058712cf17bd4 write
67 # Monitoring can query for values
68 monitoring {HA1}ec018ffe72b8e75bb4d508ed5b6d079c read
70 # A user who can read and write (the former is implied by granting
72 superuser {HA1}ec018ffe72b8e75bb4d508ed5b6d079c read,write
75 .. [#pwhash] Using the MD5 hash of username, realm and password is
76 described in :rfc:`2617` ("HTTP Authentication"), sections 3.2.2.2
77 and 3.3. The reason for using it over another algorithm is forward
78 compatibility. If ``ganeti-rapi`` were to implement HTTP Digest
79 authentication in the future, the same hash could be used.
80 In the current version ``ganeti-rapi``'s realm, ``Ganeti Remote
81 API``, can only be changed by modifying the source code.
87 The protocol used is JSON_ over HTTP designed after the REST_ principle.
88 HTTP Basic authentication as per :rfc:`2617` is supported.
90 .. _JSON: http://www.json.org/
91 .. _REST: http://en.wikipedia.org/wiki/Representational_State_Transfer
93 HTTP requests with a body (e.g. ``PUT`` or ``POST``) require the request
94 header ``Content-type`` be set to ``application/json`` (see :rfc:`2616`
95 (HTTP/1.1), section 7.2.1).
98 A note on JSON as used by RAPI
99 ++++++++++++++++++++++++++++++
101 JSON_ as used by Ganeti RAPI does not conform to the specification in
102 :rfc:`4627`. Section 2 defines a JSON text to be either an object
103 (``{"key": "value", …}``) or an array (``[1, 2, 3, …]``). In violation
104 of this RAPI uses plain strings (``"master-candidate"``, ``"1234"``) for
105 some requests or responses. Changing this now would likely break
106 existing clients and cause a lot of trouble.
110 Unlike Python's `JSON encoder and decoder
111 <http://docs.python.org/library/json.html>`_, other programming
112 languages or libraries may only provide a strict implementation, not
113 allowing plain values. For those, responses can usually be wrapped in an
114 array whose first element is then used, e.g. the response ``"1234"``
115 becomes ``["1234"]``. This works equally well for more complex values.
120 # Insert code to get response here
121 response = "\"1234\""
123 decoded = JSON.parse("[#{response}]").first
125 Short of modifying the encoder to allow encoding to a less strict
126 format, requests will have to be formatted by hand. Newer RAPI requests
127 already use a dictionary as their input data and shouldn't cause any
134 According to :rfc:`2616` the main difference between PUT and POST is
135 that POST can create new resources but PUT can only create the resource
136 the URI was pointing to on the PUT request.
138 Unfortunately, due to historic reasons, the Ganeti RAPI library is not
139 consistent with this usage, so just use the methods as documented below
142 For more details have a look in the source code at
143 ``lib/rapi/rlib2.py``.
146 Generic parameter types
147 -----------------------
149 A few generic refered parameter types and the values they allow.
154 A boolean option will accept ``1`` or ``0`` as numbers but not
155 i.e. ``True`` or ``False``.
160 A few parameter mean the same thing across all resources which implement
166 Bulk-mode means that for the resources which usually return just a list
167 of child resources (e.g. ``/2/instances`` which returns just instance
168 names), the output will instead contain detailed data for all these
169 subresources. This is more efficient than query-ing the sub-resources
175 The boolean *dry-run* argument, if provided and set, signals to Ganeti
176 that the job should not be executed, only the pre-execution checks will
179 This is useful in trying to determine (without guarantees though, as in
180 the meantime the cluster state could have changed) if the operation is
181 likely to succeed or at least start executing.
186 Force operation to continue even if it will cause the cluster to become
187 inconsistent (e.g. because there are not enough master candidates).
192 Some parameters are not straight forward, so we describe them in details
200 The instance policy specification is a dict with the following fields:
204 constants.IPOLICY_ALL_KEYS == set([constants.ISPECS_MIN,
205 constants.ISPECS_MAX,
206 constants.ISPECS_STD,
207 constants.IPOLICY_DTS,
208 constants.IPOLICY_VCPU_RATIO,
209 constants.IPOLICY_SPINDLE_RATIO])
214 (set(constants.ISPECS_PARAMETER_TYPES.keys()) ==
215 set([constants.ISPEC_MEM_SIZE,
216 constants.ISPEC_DISK_SIZE,
217 constants.ISPEC_DISK_COUNT,
218 constants.ISPEC_CPU_COUNT,
219 constants.ISPEC_NIC_COUNT,
220 constants.ISPEC_SPINDLE_USE]))
222 .. |ispec-min| replace:: :pyeval:`constants.ISPECS_MIN`
223 .. |ispec-max| replace:: :pyeval:`constants.ISPECS_MAX`
224 .. |ispec-std| replace:: :pyeval:`constants.ISPECS_STD`
227 |ispec-min|, |ispec-max|, |ispec-std|
228 A sub- `dict` with the following fields, which sets the limit and standard
229 values of the instances:
231 :pyeval:`constants.ISPEC_MEM_SIZE`
232 The size in MiB of the memory used
233 :pyeval:`constants.ISPEC_DISK_SIZE`
234 The size in MiB of the disk used
235 :pyeval:`constants.ISPEC_DISK_COUNT`
236 The numbers of disks used
237 :pyeval:`constants.ISPEC_CPU_COUNT`
238 The numbers of cpus used
239 :pyeval:`constants.ISPEC_NIC_COUNT`
240 The numbers of nics used
241 :pyeval:`constants.ISPEC_SPINDLE_USE`
242 The numbers of virtual disk spindles used by this instance. They are
243 not real in the sense of actual HDD spindles, but useful for
244 accounting the spindle usage on the residing node
245 :pyeval:`constants.IPOLICY_DTS`
246 A `list` of disk templates allowed for instances using this policy
247 :pyeval:`constants.IPOLICY_VCPU_RATIO`
248 Maximum ratio of virtual to physical CPUs (`float`)
249 :pyeval:`constants.IPOLICY_SPINDLE_RATIO`
250 Maximum ratio of instances to their node's ``spindle_count`` (`float`)
255 You can access the API using your favorite programming language as long
256 as it supports network connections.
261 Ganeti includes a standalone RAPI client, ``lib/rapi/client.py``.
266 .. highlight:: shell-example
270 $ wget -q -O - https://%CLUSTERNAME%:5080/2/info
274 $ curl https://%CLUSTERNAME%:5080/2/info
280 .. highlight:: python
285 f = urllib2.urlopen('https://CLUSTERNAME:5080/2/info')
292 .. warning:: While it's possible to use JavaScript, it poses several
293 potential problems, including browser blocking request due to
294 non-standard ports or different domain names. Fetching the data on
295 the webserver is easier.
297 .. highlight:: javascript
301 var url = 'https://CLUSTERNAME:5080/2/info';
303 var xmlreq = new XMLHttpRequest();
304 xmlreq.onreadystatechange = function () {
305 if (xmlreq.readyState != 4) return;
306 if (xmlreq.status == 200) {
307 info = eval("(" + xmlreq.responseText + ")");
310 alert('Error fetching cluster info');
314 xmlreq.open('GET', url, true);
320 .. highlight:: javascript
325 The root resource. Has no function, but for legacy reasons the ``GET``
331 Has no function, but for legacy reasons the ``GET`` method is supported.
336 Cluster information resource.
338 It supports the following commands: ``GET``.
343 Returns cluster information.
348 "config_version": 2000000,
350 "software_version": "2.0.0~beta2",
351 "os_api_version": 10,
353 "candidate_pool_size": 10,
354 "enabled_hypervisors": [
360 "default_hypervisor": "fake",
361 "master": "node1.example.com",
366 "protocol_version": 20,
369 "auto_balance": true,
378 ``/2/redistribute-config``
379 ++++++++++++++++++++++++++
381 Redistribute configuration to all nodes.
383 It supports the following commands: ``PUT``.
388 Redistribute configuration to all nodes. The result will be a job id.
392 .. opcode_result:: OP_CLUSTER_REDIST_CONF
401 Returns a list of features supported by the RAPI server. Available
406 rlib2.ALL_FEATURES == set([rlib2._INST_CREATE_REQV1,
407 rlib2._INST_REINSTALL_REQV1,
408 rlib2._NODE_MIGRATE_REQV1,
409 rlib2._NODE_EVAC_RES1])
411 :pyeval:`rlib2._INST_CREATE_REQV1`
412 Instance creation request data version 1 supported
413 :pyeval:`rlib2._INST_REINSTALL_REQV1`
414 Instance reinstall supports body parameters
415 :pyeval:`rlib2._NODE_MIGRATE_REQV1`
416 Whether migrating a node (``/2/nodes/[node_name]/migrate``) supports
417 request body parameters
418 :pyeval:`rlib2._NODE_EVAC_RES1`
419 Whether evacuating a node (``/2/nodes/[node_name]/evacuate``) returns
420 a new-style result (see resource description)
424 ++++++++++++++++++++++++++++++++++++++++
426 Modifies cluster parameters.
428 Supports the following commands: ``PUT``.
437 .. opcode_params:: OP_CLUSTER_SET_PARAMS
441 .. opcode_result:: OP_CLUSTER_SET_PARAMS
449 It supports the following commands: ``GET``, ``POST``.
454 Returns a list of all existing node groups.
461 "uri": "\/2\/groups\/group1"
465 "uri": "\/2\/groups\/group2"
469 If the optional bool *bulk* argument is provided and set to a true value
470 (i.e ``?bulk=1``), the output contains detailed information about node
473 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.G_FIELDS))`.
485 "uuid": "0d7d407c-262e-49af-881a-6a430034bf43",
494 "uuid": "f5a277e7-68f9-44d3-a378-4b25ecb5df5c",
503 Creates a node group.
505 If the optional bool *dry-run* argument is provided, the job will not be
506 actually executed, only the pre-execution checks will be done.
508 Returns: a job ID that can be used later for polling.
512 .. opcode_params:: OP_GROUP_ADD
514 Earlier versions used a parameter named ``name`` which, while still
515 supported, has been renamed to ``group_name``.
519 .. opcode_result:: OP_GROUP_ADD
522 ``/2/groups/[group_name]``
523 ++++++++++++++++++++++++++
525 Returns information about a node group.
527 It supports the following commands: ``GET``, ``DELETE``.
532 Returns information about a node group, similar to the bulk output from
535 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.G_FIELDS))`.
540 Deletes a node group.
542 It supports the ``dry-run`` argument.
546 .. opcode_result:: OP_GROUP_REMOVE
549 ``/2/groups/[group_name]/modify``
550 +++++++++++++++++++++++++++++++++
552 Modifies the parameters of a node group.
554 Supports the following commands: ``PUT``.
563 .. opcode_params:: OP_GROUP_SET_PARAMS
568 .. opcode_result:: OP_GROUP_SET_PARAMS
571 ``/2/groups/[group_name]/rename``
572 +++++++++++++++++++++++++++++++++
574 Renames a node group.
576 Supports the following commands: ``PUT``.
585 .. opcode_params:: OP_GROUP_RENAME
590 .. opcode_result:: OP_GROUP_RENAME
593 ``/2/groups/[group_name]/assign-nodes``
594 +++++++++++++++++++++++++++++++++++++++
596 Assigns nodes to a group.
598 Supports the following commands: ``PUT``.
603 Returns a job ID. It supports the ``dry-run`` and ``force`` arguments.
607 .. opcode_params:: OP_GROUP_ASSIGN_NODES
608 :exclude: group_name, force, dry_run
612 .. opcode_result:: OP_GROUP_ASSIGN_NODES
615 ``/2/groups/[group_name]/tags``
616 +++++++++++++++++++++++++++++++
618 Manages per-nodegroup tags.
620 Supports the following commands: ``GET``, ``PUT``, ``DELETE``.
625 Returns a list of tags.
629 ["tag1", "tag2", "tag3"]
636 The request as a list of strings should be ``PUT`` to this URI. The
637 result will be a job id.
639 It supports the ``dry-run`` argument.
647 In order to delete a set of tags, the DELETE request should be addressed
650 /tags?tag=[tag]&tag=[tag]
652 It supports the ``dry-run`` argument.
658 The networks resource.
660 It supports the following commands: ``GET``, ``POST``.
665 Returns a list of all existing networks.
672 "uri": "\/2\/networks\/network1"
676 "uri": "\/2\/networks\/network2"
680 If the optional bool *bulk* argument is provided and set to a true value
681 (i.e ``?bulk=1``), the output contains detailed information about networks
684 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.NET_FIELDS))`.
690 'external_reservations': '10.0.0.0, 10.0.0.1, 10.0.0.15',
692 'gateway': '10.0.0.1',
694 'group_list': ['default(bridged, prv0)'],
697 'map': 'XX.............X',
699 'network': '10.0.0.0/28',
701 'network_type': 'private',
714 If the optional bool *dry-run* argument is provided, the job will not be
715 actually executed, only the pre-execution checks will be done.
717 Returns: a job ID that can be used later for polling.
721 .. opcode_params:: OP_NETWORK_ADD
725 .. opcode_result:: OP_NETWORK_ADD
728 ``/2/networks/[network_name]``
729 ++++++++++++++++++++++++++++++
731 Returns information about a network.
733 It supports the following commands: ``GET``, ``DELETE``.
738 Returns information about a network, similar to the bulk output from
741 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.NET_FIELDS))`.
748 It supports the ``dry-run`` argument.
752 .. opcode_result:: OP_NETWORK_REMOVE
755 ``/2/networks/[network_name]/modify``
756 +++++++++++++++++++++++++++++++++++++
758 Modifies the parameters of a network.
760 Supports the following commands: ``PUT``.
769 .. opcode_params:: OP_NETWORK_SET_PARAMS
773 .. opcode_result:: OP_NETWORK_SET_PARAMS
776 ``/2/networks/[network_name]/connect``
777 ++++++++++++++++++++++++++++++++++++++
779 Connects a network to a nodegroup.
781 Supports the following commands: ``PUT``.
786 Returns a job ID. It supports the ``dry-run`` arguments.
790 .. opcode_params:: OP_NETWORK_CONNECT
794 .. opcode_result:: OP_NETWORK_CONNECT
797 ``/2/networks/[network_name]/disconnect``
798 +++++++++++++++++++++++++++++++++++++++++
800 Disonnects a network from a nodegroup.
802 Supports the following commands: ``PUT``.
807 Returns a job ID. It supports the ``dry-run`` arguments.
811 .. opcode_params:: OP_NETWORK_DISCONNECT
815 .. opcode_result:: OP_NETWORK_DISCONNECT
818 ``/2/networks/[network_name]/tags``
819 +++++++++++++++++++++++++++++++++++
821 Manages per-network tags.
823 Supports the following commands: ``GET``, ``PUT``, ``DELETE``.
828 Returns a list of tags.
832 ["tag1", "tag2", "tag3"]
839 The request as a list of strings should be ``PUT`` to this URI. The
840 result will be a job id.
842 It supports the ``dry-run`` argument.
850 In order to delete a set of tags, the DELETE request should be addressed
853 /tags?tag=[tag]&tag=[tag]
855 It supports the ``dry-run`` argument.
858 ``/2/instances-multi-alloc``
859 ++++++++++++++++++++++++++++
861 Tries to allocate multiple instances.
863 It supports the following commands: ``POST``
870 .. opcode_params:: OP_INSTANCE_MULTI_ALLOC
874 .. opcode_result:: OP_INSTANCE_MULTI_ALLOC
880 The instances resource.
882 It supports the following commands: ``GET``, ``POST``.
887 Returns a list of all available instances.
893 "name": "web.example.com",
894 "uri": "\/instances\/web.example.com"
897 "name": "mail.example.com",
898 "uri": "\/instances\/mail.example.com"
902 If the optional bool *bulk* argument is provided and set to a true value
903 (i.e ``?bulk=1``), the output contains detailed information about
906 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.I_FIELDS))`.
917 "name": "web.example.com",
918 "tags": ["tag1", "tag2"],
926 "pnode": "node1.example.com",
927 "nic.macs": ["01:23:45:67:89:01"],
928 "snodes": ["node2.example.com"],
929 "disk_template": "drbd",
944 If the optional bool *dry-run* argument is provided, the job will not be
945 actually executed, only the pre-execution checks will be done. Query-ing
946 the job result will return, in both dry-run and normal case, the list of
947 nodes selected for the instance.
949 Returns: a job ID that can be used later for polling.
953 ``__version__`` (int, required)
954 Must be ``1`` (older Ganeti versions used a different format for
955 instance creation requests, version ``0``, but that format is no
958 .. opcode_params:: OP_INSTANCE_CREATE
960 Earlier versions used parameters named ``name`` and ``os``. These have
961 been replaced by ``instance_name`` and ``os_type`` to match the
962 underlying opcode. The old names can still be used.
966 .. opcode_result:: OP_INSTANCE_CREATE
969 ``/2/instances/[instance_name]``
970 ++++++++++++++++++++++++++++++++
972 Instance-specific resource.
974 It supports the following commands: ``GET``, ``DELETE``.
979 Returns information about an instance, similar to the bulk output from
982 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.I_FIELDS))`.
989 It supports the ``dry-run`` argument.
993 .. opcode_result:: OP_INSTANCE_REMOVE
996 ``/2/instances/[instance_name]/info``
997 +++++++++++++++++++++++++++++++++++++++
999 It supports the following commands: ``GET``.
1004 Requests detailed information about the instance. An optional parameter,
1005 ``static`` (bool), can be set to return only static information from the
1006 configuration without querying the instance's nodes. The result will be
1011 .. opcode_result:: OP_INSTANCE_QUERY_DATA
1014 ``/2/instances/[instance_name]/reboot``
1015 +++++++++++++++++++++++++++++++++++++++
1017 Reboots URI for an instance.
1019 It supports the following commands: ``POST``.
1024 Reboots the instance.
1026 The URI takes optional ``type=soft|hard|full`` and
1027 ``ignore_secondaries=0|1`` parameters.
1029 ``type`` defines the reboot type. ``soft`` is just a normal reboot,
1030 without terminating the hypervisor. ``hard`` means full shutdown
1031 (including terminating the hypervisor process) and startup again.
1032 ``full`` is like ``hard`` but also recreates the configuration from
1033 ground up as if you would have done a ``gnt-instance shutdown`` and
1034 ``gnt-instance start`` on it.
1036 ``ignore_secondaries`` is a bool argument indicating if we start the
1037 instance even if secondary disks are failing.
1039 It supports the ``dry-run`` argument.
1043 .. opcode_result:: OP_INSTANCE_REBOOT
1046 ``/2/instances/[instance_name]/shutdown``
1047 +++++++++++++++++++++++++++++++++++++++++
1049 Instance shutdown URI.
1051 It supports the following commands: ``PUT``.
1056 Shutdowns an instance.
1058 It supports the ``dry-run`` argument.
1060 .. opcode_params:: OP_INSTANCE_SHUTDOWN
1061 :exclude: instance_name, dry_run
1065 .. opcode_result:: OP_INSTANCE_SHUTDOWN
1068 ``/2/instances/[instance_name]/startup``
1069 ++++++++++++++++++++++++++++++++++++++++
1071 Instance startup URI.
1073 It supports the following commands: ``PUT``.
1078 Startup an instance.
1080 The URI takes an optional ``force=1|0`` parameter to start the
1081 instance even if secondary disks are failing.
1083 It supports the ``dry-run`` argument.
1087 .. opcode_result:: OP_INSTANCE_STARTUP
1090 ``/2/instances/[instance_name]/reinstall``
1091 ++++++++++++++++++++++++++++++++++++++++++++++
1093 Installs the operating system again.
1095 It supports the following commands: ``POST``.
1104 ``os`` (string, required)
1105 Instance operating system.
1106 ``start`` (bool, defaults to true)
1107 Whether to start instance after reinstallation.
1109 Dictionary with (temporary) OS parameters.
1111 For backwards compatbility, this resource also takes the query
1112 parameters ``os`` (OS template name) and ``nostartup`` (bool). New
1113 clients should use the body parameters.
1116 ``/2/instances/[instance_name]/replace-disks``
1117 ++++++++++++++++++++++++++++++++++++++++++++++
1119 Replaces disks on an instance.
1121 It supports the following commands: ``POST``.
1130 .. opcode_params:: OP_INSTANCE_REPLACE_DISKS
1131 :exclude: instance_name
1133 Ganeti 2.4 and below used query parameters. Those are deprecated and
1134 should no longer be used.
1138 .. opcode_result:: OP_INSTANCE_REPLACE_DISKS
1141 ``/2/instances/[instance_name]/activate-disks``
1142 +++++++++++++++++++++++++++++++++++++++++++++++
1144 Activate disks on an instance.
1146 It supports the following commands: ``PUT``.
1151 Takes the bool parameter ``ignore_size``. When set ignore the recorded
1152 size (useful for forcing activation when recorded size is wrong).
1156 .. opcode_result:: OP_INSTANCE_ACTIVATE_DISKS
1159 ``/2/instances/[instance_name]/deactivate-disks``
1160 +++++++++++++++++++++++++++++++++++++++++++++++++
1162 Deactivate disks on an instance.
1164 It supports the following commands: ``PUT``.
1169 Takes no parameters.
1173 .. opcode_result:: OP_INSTANCE_DEACTIVATE_DISKS
1176 ``/2/instances/[instance_name]/recreate-disks``
1177 +++++++++++++++++++++++++++++++++++++++++++++++++
1179 Recreate disks of an instance. Supports the following commands:
1189 .. opcode_params:: OP_INSTANCE_RECREATE_DISKS
1190 :exclude: instance_name
1194 .. opcode_result:: OP_INSTANCE_RECREATE_DISKS
1197 ``/2/instances/[instance_name]/disk/[disk_index]/grow``
1198 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1200 Grows one disk of an instance.
1202 Supports the following commands: ``POST``.
1211 .. opcode_params:: OP_INSTANCE_GROW_DISK
1212 :exclude: instance_name, disk
1216 .. opcode_result:: OP_INSTANCE_GROW_DISK
1219 ``/2/instances/[instance_name]/prepare-export``
1220 +++++++++++++++++++++++++++++++++++++++++++++++++
1222 Prepares an export of an instance.
1224 It supports the following commands: ``PUT``.
1229 Takes one parameter, ``mode``, for the export mode. Returns a job ID.
1233 .. opcode_result:: OP_BACKUP_PREPARE
1236 ``/2/instances/[instance_name]/export``
1237 +++++++++++++++++++++++++++++++++++++++++++++++++
1239 Exports an instance.
1241 It supports the following commands: ``PUT``.
1250 .. opcode_params:: OP_BACKUP_EXPORT
1251 :exclude: instance_name
1252 :alias: target_node=destination
1256 .. opcode_result:: OP_BACKUP_EXPORT
1259 ``/2/instances/[instance_name]/migrate``
1260 ++++++++++++++++++++++++++++++++++++++++
1262 Migrates an instance.
1264 Supports the following commands: ``PUT``.
1273 .. opcode_params:: OP_INSTANCE_MIGRATE
1274 :exclude: instance_name, live
1278 .. opcode_result:: OP_INSTANCE_MIGRATE
1281 ``/2/instances/[instance_name]/failover``
1282 +++++++++++++++++++++++++++++++++++++++++
1284 Does a failover of an instance.
1286 Supports the following commands: ``PUT``.
1295 .. opcode_params:: OP_INSTANCE_FAILOVER
1296 :exclude: instance_name
1300 .. opcode_result:: OP_INSTANCE_FAILOVER
1303 ``/2/instances/[instance_name]/rename``
1304 ++++++++++++++++++++++++++++++++++++++++
1306 Renames an instance.
1308 Supports the following commands: ``PUT``.
1317 .. opcode_params:: OP_INSTANCE_RENAME
1318 :exclude: instance_name
1322 .. opcode_result:: OP_INSTANCE_RENAME
1325 ``/2/instances/[instance_name]/modify``
1326 ++++++++++++++++++++++++++++++++++++++++
1328 Modifies an instance.
1330 Supports the following commands: ``PUT``.
1339 .. opcode_params:: OP_INSTANCE_SET_PARAMS
1340 :exclude: instance_name
1344 .. opcode_result:: OP_INSTANCE_SET_PARAMS
1347 ``/2/instances/[instance_name]/console``
1348 ++++++++++++++++++++++++++++++++++++++++
1350 Request information for connecting to instance's console.
1354 not (hasattr(rlib2.R_2_instances_name_console, "PUT") or
1355 hasattr(rlib2.R_2_instances_name_console, "POST") or
1356 hasattr(rlib2.R_2_instances_name_console, "DELETE"))
1358 Supports the following commands: ``GET``. Requires authentication with
1359 one of the following options:
1360 :pyeval:`utils.CommaJoin(rlib2.R_2_instances_name_console.GET_ACCESS)`.
1365 Returns a dictionary containing information about the instance's
1366 console. Contained keys:
1370 constants.CONS_ALL == frozenset([
1371 constants.CONS_MESSAGE,
1374 constants.CONS_SPICE,
1380 Console type, one of :pyeval:`constants.CONS_SSH`,
1381 :pyeval:`constants.CONS_VNC`, :pyeval:`constants.CONS_SPICE`
1382 or :pyeval:`constants.CONS_MESSAGE`
1384 Message to display (:pyeval:`constants.CONS_MESSAGE` type only)
1386 Host to connect to (:pyeval:`constants.CONS_SSH`,
1387 :pyeval:`constants.CONS_VNC` or :pyeval:`constants.CONS_SPICE` only)
1389 TCP port to connect to (:pyeval:`constants.CONS_VNC` or
1390 :pyeval:`constants.CONS_SPICE` only)
1392 Username to use (:pyeval:`constants.CONS_SSH` only)
1394 Command to execute on machine (:pyeval:`constants.CONS_SSH` only)
1396 VNC display number (:pyeval:`constants.CONS_VNC` only)
1399 ``/2/instances/[instance_name]/tags``
1400 +++++++++++++++++++++++++++++++++++++
1402 Manages per-instance tags.
1404 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1409 Returns a list of tags.
1413 ["tag1", "tag2", "tag3"]
1420 The request as a list of strings should be ``PUT`` to this URI. The
1421 result will be a job id.
1423 It supports the ``dry-run`` argument.
1431 In order to delete a set of tags, the DELETE request should be addressed
1434 /tags?tag=[tag]&tag=[tag]
1436 It supports the ``dry-run`` argument.
1442 The ``/2/jobs`` resource.
1444 It supports the following commands: ``GET``.
1449 Returns a dictionary of jobs.
1451 Returns: a dictionary with jobs id and uri.
1453 If the optional bool *bulk* argument is provided and set to a true value
1454 (i.e. ``?bulk=1``), the output contains detailed information about jobs
1457 Returned fields for bulk requests (unlike other bulk requests, these
1458 fields are not the same as for per-job requests):
1459 :pyeval:`utils.CommaJoin(sorted(rlib2.J_FIELDS_BULK))`.
1461 ``/2/jobs/[job_id]``
1462 ++++++++++++++++++++
1467 It supports the following commands: ``GET``, ``DELETE``.
1472 Returns a dictionary with job parameters, containing the fields
1473 :pyeval:`utils.CommaJoin(sorted(rlib2.J_FIELDS))`.
1475 The result includes:
1477 - id: job ID as a number
1478 - status: current job status as a string
1479 - ops: involved OpCodes as a list of dictionaries for each opcodes in
1481 - opstatus: OpCodes status as a list
1482 - opresult: OpCodes results as a list
1484 For a successful opcode, the ``opresult`` field corresponding to it will
1485 contain the raw result from its :term:`LogicalUnit`. In case an opcode
1486 has failed, its element in the opresult list will be a list of two
1489 - first element the error type (the Ganeti internal error name)
1490 - second element a list of either one or two elements:
1492 - the first element is the textual error description
1493 - the second element, if any, will hold an error classification
1495 The error classification is most useful for the ``OpPrereqError``
1496 error type - these errors happen before the OpCode has started
1497 executing, so it's possible to retry the OpCode without side
1498 effects. But whether it make sense to retry depends on the error
1503 errors.ECODE_ALL == set([errors.ECODE_RESOLVER, errors.ECODE_NORES,
1504 errors.ECODE_INVAL, errors.ECODE_STATE, errors.ECODE_NOENT,
1505 errors.ECODE_EXISTS, errors.ECODE_NOTUNIQUE, errors.ECODE_FAULT,
1506 errors.ECODE_ENVIRON, errors.ECODE_TEMP_NORES])
1508 :pyeval:`errors.ECODE_RESOLVER`
1509 Resolver errors. This usually means that a name doesn't exist in DNS,
1510 so if it's a case of slow DNS propagation the operation can be retried
1513 :pyeval:`errors.ECODE_NORES`
1514 Not enough resources (iallocator failure, disk space, memory,
1515 etc.). If the resources on the cluster increase, the operation might
1518 :pyeval:`errors.ECODE_TEMP_NORES`
1519 Simliar to :pyeval:`errors.ECODE_NORES`, but indicating the operation
1520 should be attempted again after some time.
1522 :pyeval:`errors.ECODE_INVAL`
1523 Wrong arguments (at syntax level). The operation will not ever be
1524 accepted unless the arguments change.
1526 :pyeval:`errors.ECODE_STATE`
1527 Wrong entity state. For example, live migration has been requested for
1528 a down instance, or instance creation on an offline node. The
1529 operation can be retried once the resource has changed state.
1531 :pyeval:`errors.ECODE_NOENT`
1532 Entity not found. For example, information has been requested for an
1535 :pyeval:`errors.ECODE_EXISTS`
1536 Entity already exists. For example, instance creation has been
1537 requested for an already-existing instance.
1539 :pyeval:`errors.ECODE_NOTUNIQUE`
1540 Resource not unique (e.g. MAC or IP duplication).
1542 :pyeval:`errors.ECODE_FAULT`
1543 Internal cluster error. For example, a node is unreachable but not set
1544 offline, or the ganeti node daemons are not working, etc. A
1545 ``gnt-cluster verify`` should be run.
1547 :pyeval:`errors.ECODE_ENVIRON`
1548 Environment error (e.g. node disk error). A ``gnt-cluster verify``
1551 Note that in the above list, by entity we refer to a node or instance,
1552 while by a resource we refer to an instance's disk, or NIC, etc.
1558 Cancel a not-yet-started job.
1561 ``/2/jobs/[job_id]/wait``
1562 +++++++++++++++++++++++++
1567 Waits for changes on a job. Takes the following body parameters in a
1571 The job fields on which to watch for changes
1573 ``previous_job_info``
1574 Previously received field values or None if not yet available
1576 ``previous_log_serial``
1577 Highest log serial number received so far or None if not yet
1580 Returns None if no changes have been detected and a dict with two keys,
1581 ``job_info`` and ``log_entries`` otherwise.
1589 It supports the following commands: ``GET``.
1594 Returns a list of all nodes.
1600 "id": "node1.example.com",
1601 "uri": "\/nodes\/node1.example.com"
1604 "id": "node2.example.com",
1605 "uri": "\/nodes\/node2.example.com"
1609 If the optional bool *bulk* argument is provided and set to a true value
1610 (i.e ``?bulk=1``), the output contains detailed information about nodes
1613 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.N_FIELDS))`.
1622 "name": "www.example.com",
1634 ``/2/nodes/[node_name]``
1635 +++++++++++++++++++++++++++++++++
1637 Returns information about a node.
1639 It supports the following commands: ``GET``.
1641 Returned fields: :pyeval:`utils.CommaJoin(sorted(rlib2.N_FIELDS))`.
1643 ``/2/nodes/[node_name]/powercycle``
1644 +++++++++++++++++++++++++++++++++++
1646 Powercycles a node. Supports the following commands: ``POST``.
1655 .. opcode_result:: OP_NODE_POWERCYCLE
1658 ``/2/nodes/[node_name]/evacuate``
1659 +++++++++++++++++++++++++++++++++
1661 Evacuates instances off a node.
1663 It supports the following commands: ``POST``.
1668 Returns a job ID. The result of the job will contain the IDs of the
1669 individual jobs submitted to evacuate the node.
1673 .. opcode_params:: OP_NODE_EVACUATE
1676 Up to and including Ganeti 2.4 query arguments were used. Those are no
1677 longer supported. The new request can be detected by the presence of the
1678 :pyeval:`rlib2._NODE_EVAC_RES1` feature string.
1682 .. opcode_result:: OP_NODE_EVACUATE
1685 ``/2/nodes/[node_name]/migrate``
1686 +++++++++++++++++++++++++++++++++
1688 Migrates all primary instances from a node.
1690 It supports the following commands: ``POST``.
1695 If no mode is explicitly specified, each instances' hypervisor default
1696 migration mode will be used. Body parameters:
1698 .. opcode_params:: OP_NODE_MIGRATE
1701 The query arguments used up to and including Ganeti 2.4 are deprecated
1702 and should no longer be used. The new request format can be detected by
1703 the presence of the :pyeval:`rlib2._NODE_MIGRATE_REQV1` feature string.
1707 .. opcode_result:: OP_NODE_MIGRATE
1710 ``/2/nodes/[node_name]/role``
1711 +++++++++++++++++++++++++++++
1715 It supports the following commands: ``GET``, ``PUT``.
1717 The role is always one of the following:
1724 Note that the 'master' role is a special, and currently it can't be
1725 modified via RAPI, only via the command line (``gnt-cluster
1731 Returns the current node role.
1740 Change the node role.
1742 The request is a string which should be PUT to this URI. The result will
1745 It supports the bool ``force`` argument.
1749 .. opcode_result:: OP_NODE_SET_PARAMS
1752 ``/2/nodes/[node_name]/modify``
1753 +++++++++++++++++++++++++++++++
1755 Modifies the parameters of a node. Supports the following commands:
1765 .. opcode_params:: OP_NODE_SET_PARAMS
1770 .. opcode_result:: OP_NODE_SET_PARAMS
1773 ``/2/nodes/[node_name]/storage``
1774 ++++++++++++++++++++++++++++++++
1776 Manages storage units on the node.
1783 constants.VALID_STORAGE_TYPES == set([constants.ST_FILE,
1784 constants.ST_LVM_PV,
1785 constants.ST_LVM_VG])
1787 Requests a list of storage units on a node. Requires the parameters
1788 ``storage_type`` (one of :pyeval:`constants.ST_FILE`,
1789 :pyeval:`constants.ST_LVM_PV` or :pyeval:`constants.ST_LVM_VG`) and
1790 ``output_fields``. The result will be a job id, using which the result
1793 ``/2/nodes/[node_name]/storage/modify``
1794 +++++++++++++++++++++++++++++++++++++++
1796 Modifies storage units on the node.
1801 Modifies parameters of storage units on the node. Requires the
1802 parameters ``storage_type`` (one of :pyeval:`constants.ST_FILE`,
1803 :pyeval:`constants.ST_LVM_PV` or :pyeval:`constants.ST_LVM_VG`)
1804 and ``name`` (name of the storage unit). Parameters can be passed
1805 additionally. Currently only :pyeval:`constants.SF_ALLOCATABLE` (bool)
1806 is supported. The result will be a job id.
1810 .. opcode_result:: OP_NODE_MODIFY_STORAGE
1813 ``/2/nodes/[node_name]/storage/repair``
1814 +++++++++++++++++++++++++++++++++++++++
1816 Repairs a storage unit on the node.
1823 constants.VALID_STORAGE_OPERATIONS == {
1824 constants.ST_LVM_VG: set([constants.SO_FIX_CONSISTENCY]),
1827 Repairs a storage unit on the node. Requires the parameters
1828 ``storage_type`` (currently only :pyeval:`constants.ST_LVM_VG` can be
1829 repaired) and ``name`` (name of the storage unit). The result will be a
1834 .. opcode_result:: OP_REPAIR_NODE_STORAGE
1837 ``/2/nodes/[node_name]/tags``
1838 +++++++++++++++++++++++++++++
1840 Manages per-node tags.
1842 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1847 Returns a list of tags.
1851 ["tag1", "tag2", "tag3"]
1858 The request as a list of strings should be PUT to this URI. The result
1861 It supports the ``dry-run`` argument.
1868 In order to delete a set of tags, the DELETE request should be addressed
1871 /tags?tag=[tag]&tag=[tag]
1873 It supports the ``dry-run`` argument.
1876 ``/2/query/[resource]``
1877 +++++++++++++++++++++++
1879 Requests resource information. Available fields can be found in man
1880 pages and using ``/2/query/[resource]/fields``. The resource is one of
1881 :pyeval:`utils.CommaJoin(constants.QR_VIA_RAPI)`. See the :doc:`query2
1882 design document <design-query2>` for more details.
1886 (rlib2.R_2_query.GET_ACCESS == rlib2.R_2_query.PUT_ACCESS and
1887 not (hasattr(rlib2.R_2_query, "POST") or
1888 hasattr(rlib2.R_2_query, "DELETE")))
1890 Supports the following commands: ``GET``, ``PUT``. Requires
1891 authentication with one of the following options:
1892 :pyeval:`utils.CommaJoin(rlib2.R_2_query.GET_ACCESS)`.
1897 Returns list of included fields and actual data. Takes a query parameter
1898 named "fields", containing a comma-separated list of field names. Does
1899 not support filtering.
1904 Returns list of included fields and actual data. The list of requested
1905 fields can either be given as the query parameter "fields" or as a body
1906 parameter with the same name. The optional body parameter "filter" can
1907 be given and must be either ``null`` or a list containing filter
1911 ``/2/query/[resource]/fields``
1912 ++++++++++++++++++++++++++++++
1914 Request list of available fields for a resource. The resource is one of
1915 :pyeval:`utils.CommaJoin(constants.QR_VIA_RAPI)`. See the
1916 :doc:`query2 design document <design-query2>` for more details.
1918 Supports the following commands: ``GET``.
1923 Returns a list of field descriptions for available fields. Takes an
1924 optional query parameter named "fields", containing a comma-separated
1925 list of field names.
1933 It supports the following commands: ``GET``.
1938 Return a list of all OSes.
1940 Can return error 500 in case of a problem. Since this is a costly
1941 operation for Ganeti 2.0, it is not recommended to execute it too often.
1950 Manages cluster tags.
1952 It supports the following commands: ``GET``, ``PUT``, ``DELETE``.
1957 Returns the cluster tags.
1961 ["tag1", "tag2", "tag3"]
1968 The request as a list of strings should be PUT to this URI. The result
1971 It supports the ``dry-run`` argument.
1979 In order to delete a set of tags, the DELETE request should be addressed
1982 /tags?tag=[tag]&tag=[tag]
1984 It supports the ``dry-run`` argument.
1990 The version resource.
1992 This resource should be used to determine the remote API version and to
1993 adapt clients accordingly.
1995 It supports the following commands: ``GET``.
2000 Returns the remote API version. Ganeti 1.2 returned ``1`` and Ganeti 2.0
2003 .. vim: set textwidth=72 :