REST API Guide
Using the Red Hat Virtualization REST Application Programming Interface
Abstract
ovirt-engine-api-model code, and is currently partially complete. Updated versions of this documentation will be published as new content becomes available.
Chapter 1. Introduction Copy linkLink copied to clipboard!
The Red Hat Virtualization Manager provides a Representational State Transfer (REST) API. The API provides software developers and system administrators with control over their Red Hat Virtualization environment outside of the standard web interface. The API is useful for developers and administrators to integrate the functionality of a Red Hat Virtualization environment with custom scripts or external applications that access the API via the standard Hypertext Transfer Protocol (HTTP).
The benefits of the API are:
- Broad client support - Any programming language, framework, or system with support for HTTP protocol can use the API.
- Self descriptive - Client applications require minimal knowledge of the virtualization infrastructure, as many details are discovered at runtime.
- Resource-based model - The resource-based REST model provides a natural way to manage a virtualization platform.
This provides developers and administrators with the ability to:
- Integrate with enterprise IT systems.
- Integrate with third-party virtualization software.
- Perform automated maintenance or error-checking tasks.
- Automate repetitive tasks in a Red Hat Virtualization environment with scripts.
This documentation acts as a reference for the Red Hat Virtualization API. It aims to provide developers and administrators with instructions and examples to help harness the functionality of their Red Hat Virtualization environment through the API, either directly or using the provided SDKs.
1.1. Representational State Transfer Copy linkLink copied to clipboard!
Representational State Transfer (REST) is a design architecture that focuses on resources for a specific service and their representations. A resource representation is a key abstraction of information that corresponds to one specific managed element on a server. A client sends a request to a server element located at a Uniform Resource Identifier (URI) and performs operations with standard HTTP methods, such as GET, POST, PUT, and DELETE. This provides a stateless communication between the client and server where each request acts independently of any other request, and contains all the information necessary to complete the request.
1.1.1. API Prerequisites Copy linkLink copied to clipboard!
Prerequisites for using the Red Hat Virtualization API:
- A networked installation of Red Hat Virtualization Manager, which includes the API.
A client or programming library that initiates and receives HTTP requests from the API server, for example:
- The oVirt Python SDK.
- The oVirt Java SDK.
- The cURL command line tool.
- RESTClient, a debugger for RESTful web services.
- Knowledge of Hypertext Transfer Protocol (HTTP), the protocol used for REST API interactions. See RFC 2616: HTTP/1.1.
- Knowledge of Extensible Markup Language (XML) or JavaScript Object Notation (JSON), which the API uses to construct resource representations. See W3C Extensible Markup Language (XML) 1.0 and ECMA-404: JSON data interchange syntax.
Chapter 2. Authentication and Security Copy linkLink copied to clipboard!
2.1. TLS/SSL Certification Copy linkLink copied to clipboard!
The Red Hat Virtualization API requires Hypertext Transfer Protocol Secure (HTTPS) footnote:[See RFC 2818: HTTP Over TLS for secure interaction with client software, such as the SDK and CLI components. This involves obtaining the CA certificate used by the server and importing it into the certificate store of your client.
2.1.1. Obtaining the CA Certificate Copy linkLink copied to clipboard!
You can obtain the CA certificate from the Red Hat Virtualization Manager and transfer it to the client machine using one of these methods:
- Method 1
The preferred method for obtaining the CA certificate is to use the
openssl s_clientcommand line tool to perform a real TLS handshake with the server, and then extract the certificates that it presents.Run the
openssl s_clientcommand as in the following example:openssl s_client \ -connect myengine.example.com:443 \ -showcerts \ < /dev/null
$ openssl s_client \ -connect myengine.example.com:443 \ -showcerts \ < /dev/nullCopy to Clipboard Copied! Toggle word wrap Toggle overflow Example output
Copy to Clipboard Copied! Toggle word wrap Toggle overflow The text between the
-----BEGIN CERTIFICATE-----and-----END CERTIFICATE-----lines shows the certificates presented by the server.The first certificate is the certificate of the server itself. The second certificate is the certificate of the CA.
Copy the CA certificate, including the
-----BEGIN CERTIFICATE-----and-----END CERTIFICATE-----lines, to theca.crtfile as in the following example:-----BEGIN CERTIFICATE----- MIIDxjCCAq6gAwIBAgICEAAwDQYJKoZIhvcNAQEFBQAwSTELMAkGA1UEBhMCVVMx FTATBgNVBAoTDEV4YW1wbGUgSW5jLjEjMCEGA1UEAxMaZW5naW5lNDEuZXhhbXBs Pkyg1rQHR6ebGQ== -----END CERTIFICATE-----
-----BEGIN CERTIFICATE----- MIIDxjCCAq6gAwIBAgICEAAwDQYJKoZIhvcNAQEFBQAwSTELMAkGA1UEBhMCVVMx FTATBgNVBAoTDEV4YW1wbGUgSW5jLjEjMCEGA1UEAxMaZW5naW5lNDEuZXhhbXBs Pkyg1rQHR6ebGQ== -----END CERTIFICATE-----Copy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantThis is the most reliable method to obtain the CA certificate used by the server. The rest of the methods described here will work in most cases, but they will not obtain the correct CA certificate if the certificate has been manually replaced by the server administrator.
- Method 2
If you cannot use
openssl s_clientto obtain the certificate, you can use a command line tool, for examplecurlorwget, to download the CA certificate from the Red Hat Virtualization Manager.curlandwgetare available on multiple platforms.If using
curl:curl \ --output ca.crt \ 'http://myengine.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA'
$ curl \ --output ca.crt \ 'http://myengine.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA'Copy to Clipboard Copied! Toggle word wrap Toggle overflow If using
wget:wget \ --output-document ca.crt \ 'http://myengine.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA'
$ wget \ --output-document ca.crt \ 'http://myengine.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA'Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- Method 3
Use a web browser to navigate to the certificate located at `https://myengine.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA`.
Depending on the chosen browser, the certificate is downloaded or imported into the browser’s keystore:
-
If the browser downloads the certificate, save the file as
ca.crt. -
If the browser imports the certificate, export it using the browser’s certificate management options and save it as
ca.crt.
-
If the browser downloads the certificate, save the file as
- Method 4
Log in to the Red Hat Virtualization Manager, export the certificate from the truststore, and copy it to your client machine.
-
Log in to the Red Hat Virtualization Manager machine as
root. Export the certificate from the truststore using the Java
keytoolmanagement utility:Copy to Clipboard Copied! Toggle word wrap Toggle overflow This creates a certificate file called
ca.crt.Copy the certificate to the client machine using the
scpcommand:scp ca.crt myuser@myclient.example.com:/home/myuser/.
$ scp ca.crt myuser@myclient.example.com:/home/myuser/.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Each of these methods results in a certificate file named
ca.crton your client machine. You must then import this file into the certificate store of the client.
-
Log in to the Red Hat Virtualization Manager machine as
2.1.2. Importing a Certificate to a Client Copy linkLink copied to clipboard!
Importing a certificate to a client relies on how the client stores and interprets certificates. See your client documentation for more information on importing a certificate.
2.2. Authentication Copy linkLink copied to clipboard!
Any user with a Red Hat Virtualization Manager account has access to the API. All requests must be authenticated using either OAuth or basic authentication, as described below.
2.2.1. OAuth Authentication Copy linkLink copied to clipboard!
Since version 4.0 of Red Hat Virtualization the preferred authentication mechanism is OAuth 2.0, as described in RFC 6749.
OAuth is a sophisticated protocol, with several mechanisms for obtaining authorization and access tokens. For use with the Red Hat Virtualization API, the only supported one is the Resource Owner Password Credentials Grant, as described in RFC 6749.
You must first obtain a token, sending the user name and password to the Red Hat Virtualization Manager single sign-on service:
POST /ovirt-engine/sso/oauth/token HTTP/1.1 Host: myengine.example.com Content-Type: application/x-www-form-urlencoded Accept: application/json
POST /ovirt-engine/sso/oauth/token HTTP/1.1
Host: myengine.example.com
Content-Type: application/x-www-form-urlencoded
Accept: application/json
The request body must contain the grant_type, scope, username, and password parameters:
| Name | Value |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
These parameters must be URL-encoded. For example, the @ character in the user name needs to be encoded as %40. The resulting request body will be something like this:
grant_type=password&scope=ovirt-app-api&username=admin%40internal&password=mypassword
grant_type=password&scope=ovirt-app-api&username=admin%40internal&password=mypassword
The scope parameter is described as optional in the OAuth RFC, but when using it with the Red Hat Virtualization API it is mandatory, and its value must be ovirt-app-api.
If the user name and password are valid, the Red Hat Virtualization Manager single sign-on service will respond with a JSON document similar to this one:
For API authentication purposes, the only relevant name/value pair is the access_token. Do not manipulate this in any way; use it exactly as provided by the SSO service.
Once the token has been obtained, it can be used to perform requests to the API by including it in the HTTP Authorization header, and using the Bearer scheme. For example, to get the list of virtual machines, send a request like this:
GET /ovirt-engine/api/vms HTTP/1.1 Host: myengine.example.com Accept: application/xml Authorization: Bearer fqbR1ftzh8wBCviLxJcYuV5oSDI=
GET /ovirt-engine/api/vms HTTP/1.1
Host: myengine.example.com
Accept: application/xml
Authorization: Bearer fqbR1ftzh8wBCviLxJcYuV5oSDI=
The token can be used multiple times, for multiple requests, but it will eventually expire. When it expires, the server will reject the request with the 401 HTTP response code:
HTTP/1.1 401 Unauthorized
HTTP/1.1 401 Unauthorized
When this happens, a new token is needed, as the Red Hat Virtualization Manager single sign-on service does not currently support refreshing tokens. A new token can be requested using the same method described above.
2.2.2. Basic Authentication Copy linkLink copied to clipboard!
Basic authentication is supported only for backwards compatibility; it is deprecated since version 4.0 of Red Hat Virtualization, and will be removed in the future.
Each request uses HTTP Basic Authentication [1] to encode the credentials. If a request does not include an appropriate Authorization header, the server sends a 401 Authorization Required response:
HEAD /ovirt-engine/api HTTP/1.1 Host: myengine.example.com HTTP/1.1 401 Authorization Required
HEAD /ovirt-engine/api HTTP/1.1
Host: myengine.example.com
HTTP/1.1 401 Authorization Required
Request are issued with an Authorization header for the specified realm. Encode an appropriate Red Hat Virtualization Manager domain and user in the supplied credentials with the username@domain:password convention.
The following table shows the process for encoding credentials in Base64.
| Item | Value |
|---|---|
| User name |
|
| Domain |
|
| Password |
|
| Unencoded credentials |
|
| Base64 encoded credentials |
|
Provide the Base64-encoded credentials as shown:
HEAD /ovirt-engine/api HTTP/1.1 Host: myengine.example.com Authorization: Basic YWRtaW5AaW50ZXJuYWw6bXlwYXNzd29yZA== HTTP/1.1 200 OK
HEAD /ovirt-engine/api HTTP/1.1
Host: myengine.example.com
Authorization: Basic YWRtaW5AaW50ZXJuYWw6bXlwYXNzd29yZA==
HTTP/1.1 200 OK
Basic authentication involves potentially sensitive information, such as passwords, sent as plain text. The API requires Hypertext Transfer Protocol Secure (HTTPS) for transport-level encryption of plain-text requests.
Some Base64 libraries break the result into multiple lines and terminate each line with a newline character. This breaks the header and causes a faulty request. The Authorization header requires the encoded credentials on a single line within the header.
2.2.3. Authentication Sessions Copy linkLink copied to clipboard!
The API also provides authentication session support. Send an initial request with authentication details, then send all subsequent requests using a session cookie to authenticate.
2.2.3.1. Requesting an Authenticated Session Copy linkLink copied to clipboard!
Send a request with the
AuthorizationandPrefer: persistent-authheaders:Copy to Clipboard Copied! Toggle word wrap Toggle overflow This returns a response with the following header:
Set-Cookie: JSESSIONID=5dQja5ubr4yvI2MM2z+LZxrK; Path=/ovirt-engine/api; Secure
Set-Cookie: JSESSIONID=5dQja5ubr4yvI2MM2z+LZxrK; Path=/ovirt-engine/api; SecureCopy to Clipboard Copied! Toggle word wrap Toggle overflow Take note of the
JSESSIONID=value. In this example the value is5dQja5ubr4yvI2MM2z+LZxrK.Send all subsequent requests with the
Prefer: persistent-authandCookieheaders with theJSESSIONID=value. TheAuthorizationheader is no longer needed when using an authenticated session.Copy to Clipboard Copied! Toggle word wrap Toggle overflow When the session is no longer required, perform a request to the sever without the
Prefer: persistent-authheader.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 3. Common concepts Copy linkLink copied to clipboard!
3.1. Types Copy linkLink copied to clipboard!
The API uses the type concept to describe the different kinds of objects accepted and returned.
There are three relevant kinds of types:
3.2. Identified types Copy linkLink copied to clipboard!
Many of the types used by the API represent identified objects, objects that have an unique identifier and exist independently of other objects. The types used to describe those objects extend the Identified type, which contains the following set of common attributes:
| Attribute | Type | Description |
|---|---|---|
|
|
Each object in the virtualization infrastructure contains an | |
|
| The canonical location of the object as an absolute path. | |
|
|
A user-supplied human readable name for the object. The | |
|
| A free-form user-supplied human readable description of the object. |
Currently for most types of objects the id attribute is actually a randomly generated UUID, but this is an implementation detail, and users should not rely on that, as it may change in the future. Instead users should assume that these identifiers are just strings.
3.3. Objects Copy linkLink copied to clipboard!
Objects are the individual instances of the types supported by the API. For example, the virtual machine with identifier 123 is an object of the Vm type.
3.4. Collections Copy linkLink copied to clipboard!
A collection is a set of objects of the same type.
3.5. Representations Copy linkLink copied to clipboard!
The state of objects needs to be represented when it is transferred beetween the client and the server. The API supports XML and JSON as the representation of the state of objects, both for input and output.
3.5.1. XML representation Copy linkLink copied to clipboard!
The XML representation of an object consists of an XML element corresponding to the type of the object, XML attributes for the id and href attributes, and nested XML elements for the rest of the attributes. For example, the XML representation for a virtual machine appears as follows:
The XML representation of a collection of objects consists of an XML element, named after the type of the objects, in plural. This contains the representations of the objects of the collection. For example, the XML respresentation for a collection of virtual machines appears as follows:
In the XML representation of objects the id and href attributes are the only ones that are represented as XML attributes, the rest are represented as nested XML elements.
3.5.2. JSON representation Copy linkLink copied to clipboard!
The JSON representation of an object consists of a JSON document containing a name/value pair for each attribute (including id and href). For example, the JSON representation of a virtual machine appears as follows:
The JSON representation of a collection of objects consists of a JSON document containg a name/value pair (named ater the type of the objects, in singular) which in turn contains an array with the representations of the objects of the collection. For example, the JSON respresentation for a collection of virtual machines appears as follows:
3.6. Services Copy linkLink copied to clipboard!
Services are the parts of the server responsible for retrieving, adding updating, removing and executing actions on the objects supported by the API.
There are two relevant kinds of services:
- Services that manage a collection of objects
- These services are reponsible for listing existing objects and adding new objects. For example, the Vms service is responsible for managing the collection of virtual machines available in the system.
- Services that manage a specific object
- These services are responsible for retrieving, updating, deleting and executing actions in specific objects. For example, the Vm service is responsible for managing a specific virtual machine.
Each service is accessible via a particular path within the server. For example, the service that manages the collection of virtual machines available in the system is available in the via the path /vms, and the service that manages the virtual machine 123 is available via the path /vms/123.
All kinds of services have a set of methods that represent the operations that they can perform. The services that manage collections of objects usually have the list and add methods. The services that manage specific objects usually have the get, update and remove methods. In addition, services may also have action methods, that represent less common operations. For example, the Vm service has a start method that is used to start a virtual machine.
For the more usual methods there is a direct mapping between the name of the method and the name of the HTTP method:
| Method name | HTTP method |
|---|---|
|
| POST |
|
| GET |
|
| GET |
|
| PUT |
|
| DELETE |
The path used in the HTTP request is the path of the service, with the /ovirt-engine/api prefix.
For example, the request to list the virtual machines should be like this, using the HTTP GET method and the path /vms:
GET /ovirt-engine/api/vms
GET /ovirt-engine/api/vms
For action methods the HTTP method is always POST, and the name of the method is added as a suffix to the path. For example, the request to start virtual machine 123 should look like this, using the HTTP POST method and the path /vms/123/start:
POST /ovirt-engine/api/vms/123/start
POST /ovirt-engine/api/vms/123/start
Each method has a set of parameters.
Parameters are classified into two categories:
- Main parameter
-
The main parameter corresponds the object or collection that is retrieved, added or updated. This only applies to the
add,get,listandupdatemethods, and there will be exactly one such main parameter per method. - Secondary parameters
- The rest of the parameters.
For example, the operation that adds a virtual machine (see here) has three parameters: vm, clone and clone_permissions. The main parameter is vm, as it describes the object that is added. The clone and clone_permissions parameters are secondary parameters.
The main parameter, when used for input, must be included in the body of the HTTP request. For example, when adding a virtual machine, the vm parameter, of type Vm must be included in the request body. So the complete request to add a virtual machine, including all the HTTP details, must look like this:
When used for output, the main parameters are included in the response body. For example, when adding a virtual machine, the vm parameter will be included in the response body. So the complete response body will look like this:
Secondary parameters are only allowed for input (except for action methods, which are described later), and they must be included as query parameters. For example, when adding a virtual machine with the clone parameter set to true, the complete request must look like this:
Action methods only have secondary parameters. They can be used for input and output, and they should be included in the request body, wrapped with an action element. For example, the action method used to start a virtual machine (see here) has a vm parameter to describe how the virtual machine should be started, and a use_cloud_init parameter to specify if cloud-init should be used to configure the guest operating system. So the complete request to start virtual machine 123 using cloud-init will look like this when using XML:
3.7. Searching Copy linkLink copied to clipboard!
The list method of some services has a search parameter that can be used to specify search criteria. When used, the server will only return objects within the collection that satisfy those criteria. For example, the following request will return only the virtual machine named myvm:
GET /ovirt-engine/api/vms?search=name%3Dmyvm
GET /ovirt-engine/api/vms?search=name%3Dmyvm
3.7.1. Maximum results parameter Copy linkLink copied to clipboard!
Use the max parameter to limit the number of objects returned. For example, the following request will only return one virtual machine, regardless of how many are available in the system:
GET /ovirt-engine/api/vms?max=1
GET /ovirt-engine/api/vms?max=1
A search request without the max parameter will return all the objects. Specifying the max parameter is recommended to reduce the impact of requests in the overall performance of the system.
3.7.2. Case sensitivity Copy linkLink copied to clipboard!
By default queries are not case sensitive. For example, the following request will return the virtual machines named myvm, MyVM and MYVM:
GET /ovirt-engine/api/vms?search=name%3Dmyvm
GET /ovirt-engine/api/vms?search=name%3Dmyvm
The optional case_sensitive boolean parameter can be used to change this behaviour. For example, to get exactly the virtual machine named myhost, and not MyHost or MYHOST, send a request like this:
GET /ovirt-engine/api/vms?search=name%3D=myvm&case_sensitive=true
GET /ovirt-engine/api/vms?search=name%3D=myvm&case_sensitive=true
3.7.3. Search syntax Copy linkLink copied to clipboard!
The search parameters use the same syntax as the Red Hat Virtualization query language:
(criteria) [sortby (element) asc|desc]
(criteria) [sortby (element) asc|desc]
The sortby clause is optional and only needed when ordering results.
Example search queries:
| Collection | Criteria | Result |
|---|---|---|
|
|
|
Returns a list of all hosts running virtual machines that are |
|
|
| Returns a list of all virtual machines running on the specified domain. |
|
|
|
Returns a list of all virtual machines belonging to users with the user name |
|
|
|
Returns a list of all events with severity higher than |
|
|
|
Returns a list of all events with severity higher than |
The value of the search parameter must be URL-encoded to translate reserved characters, such as operators and spaces. For example, the equal sign should be encoded as %3D:
GET /ovirt-engine/api/vms?search=name%3Dmyvm
GET /ovirt-engine/api/vms?search=name%3Dmyvm
3.7.4. Wildcards Copy linkLink copied to clipboard!
The asterisk can be used as part of a value, to indicate that any string matches, including the emtpy string. For example, the following request will return all the virtual machines with names beginning with myvm, such as myvm, myvm2, myvma or myvm-webserver:
GET /ovirt-engine/api/vms?search=name%3Dmyvm*
GET /ovirt-engine/api/vms?search=name%3Dmyvm*
3.7.5. Pagination Copy linkLink copied to clipboard!
Some Red Hat Virtualization environments contain large collections of objects. Retrieving all of them with one request isn’t practical, and hurts performace. To allow retrieving them page by page the search parameter supports an optional page clause. This, combined with the max parameter, is the basis for paging. For example, to get the first page of virtual machines, with a page size of 10 virtual machines, send request like this:
GET /ovirt-engine/api/vms?search=page%201&max=10
GET /ovirt-engine/api/vms?search=page%201&max=10
The search parameter is URL-encoded, the actual value of the search parameter, before encoding, is page 1, so this is actually requesting the first page.
Increase the page value to retrieve the next page:
GET /ovirt-engine/api/vms?search=page%202&max=10
GET /ovirt-engine/api/vms?search=page%202&max=10
The page clause can be used in conjunction with other clauses inside the search parameter. For example, the following request will return the second page of virtual machines, but sorting by name:
GET /ovirt-engine/api/vms?search=sortby%20name%20page%202&max=10
GET /ovirt-engine/api/vms?search=sortby%20name%20page%202&max=10
The API is stateless; it is not possible to retain a state between different requests since all requests are independent from each other. As a result, if a status change occurs between your requests, then the page results may be inconsistent.
For example, if you request a specific page from a list of virtual machines, and virtual machines are created or removed before you request the next page, then your results may be missing some of them, or contain duplicates.
3.8. Following links Copy linkLink copied to clipboard!
The API returns references to related objects as links. For example, when a virtual machine is retrieved it contains links to its disk attachments and network interface cards:
The complete description of those linked objects can be retrieved by sending separate requests:
GET /ovirt-engine/api/vms/123/diskattachments GET /ovirt-engine/api/vms/123/nics
GET /ovirt-engine/api/vms/123/diskattachments
GET /ovirt-engine/api/vms/123/nics
However, in some situations it is more convenient for the application using the API to retrieve the linked information in the same request. This is useful, for example, when the additional network round trips introduce an unacceptable overhead, or when the multiple requests complicate the code of the application in an unacceptable way. For those use cases the API provides a follow parameter that allows the application to retrieve the linked information using only one request.
The value of the follow parameter is a list of strings, separated by commas. Each of those strings is the path of the linked object. For example, to retrieve the disk attachments and the NICs in the example above the request should be like this:
GET /ovirt-engine/api/vms/123?follow=disk_attachments,nics
GET /ovirt-engine/api/vms/123?follow=disk_attachments,nics
That will return an response like this:
The path to the linked object can be a single word, as in the previous example, or it can be a sequence of words, separated by dots, to request nested data. For example, the previous example used disk_attachments in order to retrieve the complete description of the disk attachments, but each disk attachment contains a link to the disk, which wasn’t followed. In order to also follow the links to the disks, the following request can be used:
GET /ovirt-engine/api/vms/123?follow=disk_attachments.disk
GET /ovirt-engine/api/vms/123?follow=disk_attachments.disk
That will result in the following response:
The path can be made as deep as needed. For example, to also get the statistics of the disks:
GET /ovirt-engine/api/vms/123?follow=disk_attachments.disk.statistics
GET /ovirt-engine/api/vms/123?follow=disk_attachments.disk.statistics
Multiple path elements and multiple paths can be combined. For example, to get the disk attachments and the network interface cards, both with their statistics:
GET /ovirt-engine/api/vms/123?follow=disk_attachments.disk.statistics,nics.statistics
GET /ovirt-engine/api/vms/123?follow=disk_attachments.disk.statistics,nics.statistics
Almost all the operations that retrieve objects support the follow parameter, but make sure to explicitly check the reference documentation, as some operations may not support it, or may provide advice on how to use it to get the best performance.
Using the follow parameter moves the overhead from the client side to the server side. When you request additional data, the server must fetch and merge it with the basic data. That consumes CPU and memory in the server side, and will in most cases require additional database queries. That may adversely affect the performance of the server, especially in large scale environments. Make sure to test your application in a realistic environment, and use the follow parameter only when justified.
3.9. Permissions Copy linkLink copied to clipboard!
Many of the services that manage a single object provide a reference to a permissions service that manages the permissions assigned to that object. Each permission contains links to the user or group, the role and the object. For example, the permissions assigned to a specific virtual machine can be retrieved sending a request like this:
GET /ovirt-engine/api/vms/123/permissions
GET /ovirt-engine/api/vms/123/permissions
The response body will look like this:
A permission is added to an object sending a POST request with a permission representation to this service. Each new permission requires a role and a user.
3.10. Handling errors Copy linkLink copied to clipboard!
Some errors require further explanation beyond a standard HTTP status code. For example, the API reports an unsuccessful object state update or action with a fault in the response body. The fault contains the reason and detail attributes. For example, when the server receives a request to create a virtual machine without the mandatory name attribute it will respond with the following HTTP response line:
HTTP/1.1 400 Bad Request
HTTP/1.1 400 Bad Request
And the following response body:
<fault> <reason>Incomplete parameters</reason> <detail>Vm [name] required for add</detail> </fault>
<fault>
<reason>Incomplete parameters</reason>
<detail>Vm [name] required for add</detail>
</fault>
Chapter 4. Quick Start Examples Copy linkLink copied to clipboard!
The examples in this section show you how to use the REST API to set up a basic Red Hat Virtualization environment and to create a virtual machine. In addition to the standard prerequisites, these examples require the following:
- A networked and configured Red Hat Virtualization installation.
- An ISO file containing the virtual machine operating system you want to install. This chapter uses CentOS 7 for the installation ISO example.
The API examples use curl to demonstrate API requests with a client application. You can use any application that sends HTTP requests.
The HTTP request headers in this example omit the Host and Authorization headers. However, these fields are mandatory and require data specific to your installation of Red Hat Virtualization.
The curl examples use admin@internal for the user name, mypassword for the password, /etc/pki/ovirt-engine/ca.pem for the certificate location, and myengine.example.com for the host name. You must replace them with the correct values for your environment.
Red Hat Virtualization generates a unique identifier for the id attribute for each resource. Identifier codes in this example will differ from the identifier codes in your Red Hat Virtualization environment.
In many examples, some attributes of the results returned by the API have been omitted, for brevity. See, for example, the Cluster reference for a complete list of attributes.
4.1. Access API entry point Copy linkLink copied to clipboard!
The following request retrieves a representation of the main entry point for version 4 of the API:
GET /ovirt-engine/api HTTP/1.1 Version: 4 Accept: application/xml
GET /ovirt-engine/api HTTP/1.1
Version: 4
Accept: application/xml
The same request, but using the /v4 URL prefix instead of the Version header:
GET /ovirt-engine/api/v4 HTTP/1.1 Accept: application/xml
GET /ovirt-engine/api/v4 HTTP/1.1
Accept: application/xml
The same request, using the curl command:
The result is an object of type Api:
When neither the header nor the URL prefix are used, the server will automatically select a version. The default is version 4. You can change the default version using the ENGINE_API_DEFAULT_VERSION configuration parameter:
echo "ENGINE_API_DEFAULT_VERSION=3" > \ /etc/ovirt-engine/engine.conf.d/99-set-default-version.conf systemctl restart ovirt-engine
# echo "ENGINE_API_DEFAULT_VERSION=3" > \
/etc/ovirt-engine/engine.conf.d/99-set-default-version.conf
# systemctl restart ovirt-engine
Changing this parameter affects all users of the API that do not specify the version explicitly.
The entry point provides a user with links to the collections in a virtualization environment. The rel attribute of each collection link provides a reference point for each link. The next step in this example examines the data center collection, which is available through the datacenters link.
The entry point also contains other data such as product_info, special_objects and summary. This data is covered in chapters outside this example.
4.2. List data centers Copy linkLink copied to clipboard!
Red Hat Virtualization creates a Default data center on installation. This example uses the Default data center as the basis for the virtual environment.
The following request retrieves a representation of the data centers:
GET /ovirt-engine/api/datacenters HTTP/1.1 Accept: application/xml
GET /ovirt-engine/api/datacenters HTTP/1.1
Accept: application/xml
The same request, using the curl command:
The result will be a list of objects of type DataCenter:
Note the id of your Default data center. It identifies this data center in relation to other resources of your virtual environment.
The data center also contains a link to the service that manages the storage domains attached to the data center:
<link href="/ovirt-engine/api/datacenters/001/storagedomains" rel="storagedomains"/>
<link href="/ovirt-engine/api/datacenters/001/storagedomains" rel="storagedomains"/>
That service is used to attach storage domains from the main storagedomains collection, which this example covers later.
4.3. List host clusters Copy linkLink copied to clipboard!
Red Hat Virtualization creates a Default hosts cluster on installation. This example uses the Default cluster to group resources in your Red Hat Virtualization environment.
The following request retrieves a representation of the cluster collection:
GET /ovirt-engine/api/clusters HTTP/1.1 Accept: application/xml
GET /ovirt-engine/api/clusters HTTP/1.1
Accept: application/xml
The same request, using the curl command:
The result will be a list of objects of type Cluster:
Note the id of your Default host cluster. It identifies this host cluster in relation to other resources of your virtual environment.
The Default cluster is associated with the Default data center through a relationship using the id and href attributes of the data_center link:
<data_center href="/ovirt-engine/api/datacenters/001" id="001"/>
<data_center href="/ovirt-engine/api/datacenters/001" id="001"/>
The networks link is a reference to the service that manages the networks associated to this cluster. The next section examines the networks collection in more detail.
4.4. List logical networks Copy linkLink copied to clipboard!
Red Hat Virtualization creates a default ovirtmgmt network on installation. This network acts as the management network for Red Hat Virtualization Manager to access hosts.
This network is associated with the Default cluster and is a member of the Default data center. This example uses the ovirtmgmt network to connect the virtual machines.
The following request retrieves the list of logical networks:
GET /ovirt-engine/api/networks HTTP/1.1 Accept: application/xml
GET /ovirt-engine/api/networks HTTP/1.1
Accept: application/xml
The same request, using the curl command:
The result will be a list of objects of type Network:
The ovirtmgmt network is attached to the Default data center through a relationship using the data center’s id.
The ovirtmgmt network is also attached to the Default cluster through a relationship in the cluster’s network sub-collection.
4.5. List hosts Copy linkLink copied to clipboard!
This example retrieves the list of hosts and shows a host named myhost registered with the virtualization environment:
GET /ovirt-engine/api/hosts HTTP/1.1 Accept: application/xml
GET /ovirt-engine/api/hosts HTTP/1.1
Accept: application/xml
The same request, using the curl command:
The result will be a list of objects of type Host:
Note the id of your host. It identifies this host in relation to other resources of your virtual environment.
This host is a member of the Default cluster and accessing the nics sub-collection shows this host has a connection to the ovirtmgmt network.
4.6. Create NFS data storage Copy linkLink copied to clipboard!
An NFS data storage domain is an exported NFS share attached to a data center and provides storage for virtualized guest images. Creation of a new storage domain requires a POST request, with the storage domain representation included, sent to the URL of the storage domain collection.
You can enable the wipe after delete option by default on the storage domain. To configure this specify wipe_after_delete in the POST request. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
The request should be like this:
POST /ovirt-engine/api/storagedomains HTTP/1.1 Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/storagedomains HTTP/1.1
Accept: application/xml
Content-type: application/xml
And the request body should be like this:
The same request, using the curl command:
The server uses host myhost to create a NFS data storage domain called mydata with an export path of mynfs.example.com:/exports/mydata. The API also returns the following representation of the newly created storage domain resource (of type StorageDomain):
4.7. Create NFS ISO storage Copy linkLink copied to clipboard!
An NFS ISO storage domain is a mounted NFS share attached to a data center and provides storage for DVD/CD-ROM ISO and virtual floppy disk (VFD) image files. Creation of a new storage domain requires a POST request, with the storage domain representation included, sent to the URL of the storage domain collection:
The request should be like this:
POST /ovirt-engine/api/storagedomains HTTP/1.1 Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/storagedomains HTTP/1.1
Accept: application/xml
Content-type: application/xml
And the request body should be like this:
The same request, using the curl command:
The server uses host myhost to create a NFS ISO storage domain called myisos with an export path of mynfs.example.com:/exports/myisos. The API also returns the following representation of the newly created storage domain resource (of type StorageDomain):
4.8. Attach storage domains to data center Copy linkLink copied to clipboard!
The following example attaches the mydata and myisos storage domains to the Default data center.
To attach the mydata storage domain, send a request like this:
POST /ovirt-engine/api/datacenters/001/storagedomains HTTP/1.1 Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/datacenters/001/storagedomains HTTP/1.1
Accept: application/xml
Content-type: application/xml
With a request body like this:
<storage_domain> <name>mydata</name> </storage_domain>
<storage_domain>
<name>mydata</name>
</storage_domain>
The same request, using the curl command:
To attach the myisos storage domain, send a request like this:
POST /ovirt-engine/api/datacenters/001/storagedomains HTTP/1.1 Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/datacenters/001/storagedomains HTTP/1.1
Accept: application/xml
Content-type: application/xml
With a request body like this:
<storage_domain> <name>myisos</name> </storage_domain>
<storage_domain>
<name>myisos</name>
</storage_domain>
The same request, using the curl command:
4.9. Create virtual machine Copy linkLink copied to clipboard!
The following example creates a virtual machine called myvm on the Default cluster using the virtualization environment’s Blank template as a basis. The request also defines the virtual machine’s memory as 512 MiB and sets the boot device to a virtual hard disk.
The request should be contain an object of type Vm describing the virtual machine to create:
POST /ovirt-engine/api/vms HTTP/1.1 Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/vms HTTP/1.1
Accept: application/xml
Content-type: application/xml
And the request body should be like this:
The same request, using the curl command:
The response body will be an object of the Vm type:
4.10. Create a virtual machine NIC Copy linkLink copied to clipboard!
The following example creates a virtual network interface to connect the example virtual machine to the ovirtmgmt network.
The request should be like this:
POST /ovirt-engine/api/vms/007/nics HTTP/1.1 Content-Type: application/xml Accept: application/xml
POST /ovirt-engine/api/vms/007/nics HTTP/1.1
Content-Type: application/xml
Accept: application/xml
The request body should contain an object of type Nic describing the NIC to be created:
<nic> <name>mynic</name> <description>My network interface card</description> </nic>
<nic>
<name>mynic</name>
<description>My network interface card</description>
</nic>
The same request, using the curl command:
4.11. Create virtual machine disk Copy linkLink copied to clipboard!
The following example creates an 8 GiB copy-on-write disk for the example virtual machine.
The request should be like this:
POST /ovirt-engine/api/vms/007/diskattachments HTTP/1.1 Content-Type: application/xml Accept: application/xml
POST /ovirt-engine/api/vms/007/diskattachments HTTP/1.1
Content-Type: application/xml
Accept: application/xml
The request body should be an object of type DiskAttachment describing the disk and how it will be attached to the virtual machine:
The same request, using the curl command:
The storage_domains attribute tells the API to store the disk on the mydata storage domain.
4.12. Attach ISO image to virtual machine Copy linkLink copied to clipboard!
The boot media for the following virtual machine example requires a CD-ROM or DVD ISO image for an operating system installation. This example uses a CentOS 7 image.
ISO images must be available in the myisos ISO domain for the virtual machines to use. You can use ImageTransfer to create an image transfer and ImageTransfers to upload the ISO image.
Once the ISO image is uploaded, an API can be used to request the list of files from the ISO storage domain:
GET /ovirt-engine/api/storagedomains/006/files HTTP/1.1 Accept: application/xml
GET /ovirt-engine/api/storagedomains/006/files HTTP/1.1
Accept: application/xml
The same request, using the curl command:
The server returns the following list of objects of type File, one for each available ISO (or floppy) image:
An API user attaches the CentOS-7-x86_64-Minimal.iso to the example virtual machine. Attaching an ISO image is equivalent to using the Change CD button in the administration or user portal applications.
The request should be like this:
PUT /ovirt-engine/api/vms/007/cdroms/00000000-0000-0000-0000-000000000000 HTTP/1.1 Accept: application/xml Content-type: application/xml
PUT /ovirt-engine/api/vms/007/cdroms/00000000-0000-0000-0000-000000000000 HTTP/1.1
Accept: application/xml
Content-type: application/xml
The request body should be an object of type Cdrom containing an inner file attribute to indicate the identifier of the ISO (or floppy) image:
<cdrom> <file id="CentOS-7-x86_64-Minimal.iso"/> </cdrom>
<cdrom>
<file id="CentOS-7-x86_64-Minimal.iso"/>
</cdrom>
The same request, using the curl command:
For more details see the documentation of the service that manages virtual machine CD-ROMS.
4.13. Start the virtual machine Copy linkLink copied to clipboard!
The virtual environment is complete and the virtual machine contains all necessary components to function. This example starts the virtual machine using the start method.
The request should be like this:
POST /ovirt-engine/api/vms/007/start HTTP/1.1 Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/vms/007/start HTTP/1.1
Accept: application/xml
Content-type: application/xml
The request body should be like this:
The same request, using the curl command:
The additional request body sets the virtual machine’s boot device to CD-ROM for this boot only. This enables the virtual machine to install the operating system from the attached ISO image. The boot device reverts back to disk for all future boots.
Chapter 5. Requests Copy linkLink copied to clipboard!
This section enumerates all the requests that are available in the API.
- POST /affinitylabels
- GET /affinitylabels
- GET /affinitylabels/{label:id}
- PUT /affinitylabels/{label:id}
- DELETE /affinitylabels/{label:id}
- POST /affinitylabels/{label:id}/hosts
- GET /affinitylabels/{label:id}/hosts
- DELETE /affinitylabels/{label:id}/hosts/{host:id}
- GET /affinitylabels/{label:id}/hosts/{host:id}
- POST /affinitylabels/{label:id}/vms
- GET /affinitylabels/{label:id}/vms
- DELETE /affinitylabels/{label:id}/vms/{vm:id}
- GET /affinitylabels/{label:id}/vms/{vm:id}
- POST /bookmarks
- GET /bookmarks
- GET /bookmarks/{bookmark:id}
- PUT /bookmarks/{bookmark:id}
- DELETE /bookmarks/{bookmark:id}
- GET /clusterlevels
- GET /clusterlevels/{level:id}
- GET /clusterlevels/{level:id}/clusterfeatures
- GET /clusterlevels/{level:id}/clusterfeatures/{feature:id}
- POST /clusters
- GET /clusters
- GET /clusters/{cluster:id}
- PUT /clusters/{cluster:id}
- DELETE /clusters/{cluster:id}
- POST /clusters/{cluster:id}/affinitygroups
- GET /clusters/{cluster:id}/affinitygroups
- GET /clusters/{cluster:id}/affinitygroups/{group:id}
- PUT /clusters/{cluster:id}/affinitygroups/{group:id}
- DELETE /clusters/{cluster:id}/affinitygroups/{group:id}
- POST /clusters/{cluster:id}/affinitygroups/{group:id}/hostlabels
- GET /clusters/{cluster:id}/affinitygroups/{group:id}/hostlabels
- DELETE /clusters/{cluster:id}/affinitygroups/{group:id}/hostlabels/{label:id}
- POST /clusters/{cluster:id}/affinitygroups/{group:id}/hosts
- GET /clusters/{cluster:id}/affinitygroups/{group:id}/hosts
- DELETE /clusters/{cluster:id}/affinitygroups/{group:id}/hosts/{host:idorname}
- POST /clusters/{cluster:id}/affinitygroups/{group:id}/vmlabels
- GET /clusters/{cluster:id}/affinitygroups/{group:id}/vmlabels
- DELETE /clusters/{cluster:id}/affinitygroups/{group:id}/vmlabels/{label:id}
- POST /clusters/{cluster:id}/affinitygroups/{group:id}/vms
- GET /clusters/{cluster:id}/affinitygroups/{group:id}/vms
- DELETE /clusters/{cluster:id}/affinitygroups/{group:id}/vms/{vm:id}
- POST /clusters/{cluster:id}/cpuprofiles
- GET /clusters/{cluster:id}/cpuprofiles
- GET /clusters/{cluster:id}/cpuprofiles/{profile:id}
- DELETE /clusters/{cluster:id}/cpuprofiles/{profile:id}
- GET /clusters/{cluster:id}/enabledfeatures
- POST /clusters/{cluster:id}/enabledfeatures
- GET /clusters/{cluster:id}/enabledfeatures/{feature:id}
- DELETE /clusters/{cluster:id}/enabledfeatures/{feature:id}
- GET /clusters/{cluster:id}/externalnetworkproviders
- GET /clusters/{cluster:id}/glusterhooks
- GET /clusters/{cluster:id}/glusterhooks/{hook:id}
- DELETE /clusters/{cluster:id}/glusterhooks/{hook:id}
- POST /clusters/{cluster:id}/glusterhooks/{hook:id}/disable
- POST /clusters/{cluster:id}/glusterhooks/{hook:id}/enable
- POST /clusters/{cluster:id}/glusterhooks/{hook:id}/resolve
- POST /clusters/{cluster:id}/glustervolumes
- GET /clusters/{cluster:id}/glustervolumes
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}
- DELETE /clusters/{cluster:id}/glustervolumes/{volume:id}
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/getprofilestatistics
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks
- DELETE /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/activate
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/migrate
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/stopmigrate
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}
- DELETE /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}/replace
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}/statistics
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}/statistics/{statistic:id}
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/rebalance
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/resetalloptions
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/resetoption
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/setoption
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/start
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/startprofile
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}/statistics
- GET /clusters/{cluster:id}/glustervolumes/{volume:id}/statistics/{statistic:id}
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/stop
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/stopprofile
- POST /clusters/{cluster:id}/glustervolumes/{volume:id}/stoprebalance
- GET /clusters/{cluster:id}/networkfilters
- GET /clusters/{cluster:id}/networkfilters/{networkfilter:id}
- POST /clusters/{cluster:id}/networks
- GET /clusters/{cluster:id}/networks
- GET /clusters/{cluster:id}/networks/{network:id}
- DELETE /clusters/{cluster:id}/networks/{network:id}
- PUT /clusters/{cluster:id}/networks/{network:id}
- POST /clusters/{cluster:id}/permissions
- GET /clusters/{cluster:id}/permissions
- GET /clusters/{cluster:id}/permissions/{permission:id}
- DELETE /clusters/{cluster:id}/permissions/{permission:id}
- POST /clusters/{cluster:id}/refreshglusterhealstatus
- POST /clusters/{cluster:id}/resetemulatedmachine
- POST /clusters/{cluster:id}/syncallnetworks
- POST /clusters/{cluster:id}/upgrade
- POST /cpuprofiles
- GET /cpuprofiles
- GET /cpuprofiles/{profile:id}
- PUT /cpuprofiles/{profile:id}
- DELETE /cpuprofiles/{profile:id}
- POST /cpuprofiles/{profile:id}/permissions
- GET /cpuprofiles/{profile:id}/permissions
- GET /cpuprofiles/{profile:id}/permissions/{permission:id}
- DELETE /cpuprofiles/{profile:id}/permissions/{permission:id}
- POST /datacenters
- GET /datacenters
- GET /datacenters/{datacenter:id}
- PUT /datacenters/{datacenter:id}
- DELETE /datacenters/{datacenter:id}
- POST /datacenters/{datacenter:id}/cleanfinishedtasks
- POST /datacenters/{datacenter:id}/clusters
- GET /datacenters/{datacenter:id}/clusters
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}
- PUT /datacenters/{datacenter:id}/clusters/{cluster:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}
- PUT /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/hostlabels
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/hostlabels
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/hostlabels/{label:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/hosts
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/hosts
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/hosts/{host:idorname}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/vmlabels
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/vmlabels
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/vmlabels/{label:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/vms
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/vms
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/affinitygroups/{group:id}/vms/{vm:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/cpuprofiles
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/cpuprofiles
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/cpuprofiles/{profile:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/cpuprofiles/{profile:id}
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/enabledfeatures
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/enabledfeatures
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/enabledfeatures/{feature:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/enabledfeatures/{feature:id}
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/externalnetworkproviders
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glusterhooks
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glusterhooks/{hook:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/glusterhooks/{hook:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glusterhooks/{hook:id}/disable
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glusterhooks/{hook:id}/enable
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glusterhooks/{hook:id}/resolve
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/getprofilestatistics
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/activate
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/migrate
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/stopmigrate
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}/replace
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}/statistics
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/glusterbricks/{brick:id}/statistics/{statistic:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/rebalance
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/resetalloptions
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/resetoption
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/setoption
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/start
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/startprofile
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/statistics
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/statistics/{statistic:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/stop
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/stopprofile
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/glustervolumes/{volume:id}/stoprebalance
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/networkfilters
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/networkfilters/{networkfilter:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/networks
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/networks
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/networks/{network:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/networks/{network:id}
- PUT /datacenters/{datacenter:id}/clusters/{cluster:id}/networks/{network:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/permissions
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/permissions
- GET /datacenters/{datacenter:id}/clusters/{cluster:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/clusters/{cluster:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/refreshglusterhealstatus
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/resetemulatedmachine
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/syncallnetworks
- POST /datacenters/{datacenter:id}/clusters/{cluster:id}/upgrade
- POST /datacenters/{datacenter:id}/iscsibonds
- GET /datacenters/{datacenter:id}/iscsibonds
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}
- PUT /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}
- POST /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}
- PUT /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}
- POST /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/networklabels
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/networklabels
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/networklabels/{label:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/networklabels/{label:id}
- POST /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/permissions
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/permissions
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles/{profile:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles/{profile:id}
- POST /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/storageserverconnections
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/storageserverconnections
- GET /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/storageserverconnections/{storageconnection:id}
- PUT /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/storageserverconnections/{storageconnection:id}
- DELETE /datacenters/{datacenter:id}/iscsibonds/{iscsibond:id}/storageserverconnections/{storageconnection:id}
- POST /datacenters/{datacenter:id}/networks
- GET /datacenters/{datacenter:id}/networks
- GET /datacenters/{datacenter:id}/networks/{network:id}
- DELETE /datacenters/{datacenter:id}/networks/{network:id}
- PUT /datacenters/{datacenter:id}/networks/{network:id}
- POST /datacenters/{datacenter:id}/permissions
- GET /datacenters/{datacenter:id}/permissions
- GET /datacenters/{datacenter:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/qoss
- GET /datacenters/{datacenter:id}/qoss
- GET /datacenters/{datacenter:id}/qoss/{qos:id}
- PUT /datacenters/{datacenter:id}/qoss/{qos:id}
- DELETE /datacenters/{datacenter:id}/qoss/{qos:id}
- POST /datacenters/{datacenter:id}/quotas
- GET /datacenters/{datacenter:id}/quotas
- GET /datacenters/{datacenter:id}/quotas/{quota:id}
- PUT /datacenters/{datacenter:id}/quotas/{quota:id}
- DELETE /datacenters/{datacenter:id}/quotas/{quota:id}
- POST /datacenters/{datacenter:id}/quotas/{quota:id}/permissions
- GET /datacenters/{datacenter:id}/quotas/{quota:id}/permissions
- GET /datacenters/{datacenter:id}/quotas/{quota:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/quotas/{quota:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/quotas/{quota:id}/quotaclusterlimits
- GET /datacenters/{datacenter:id}/quotas/{quota:id}/quotaclusterlimits
- GET /datacenters/{datacenter:id}/quotas/{quota:id}/quotaclusterlimits/{limit:id}
- DELETE /datacenters/{datacenter:id}/quotas/{quota:id}/quotaclusterlimits/{limit:id}
- POST /datacenters/{datacenter:id}/quotas/{quota:id}/quotastoragelimits
- GET /datacenters/{datacenter:id}/quotas/{quota:id}/quotastoragelimits
- GET /datacenters/{datacenter:id}/quotas/{quota:id}/quotastoragelimits/{limit:id}
- DELETE /datacenters/{datacenter:id}/quotas/{quota:id}/quotastoragelimits/{limit:id}
- POST /datacenters/{datacenter:id}/setmaster
- POST /datacenters/{datacenter:id}/storagedomains
- GET /datacenters/{datacenter:id}/storagedomains
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}
- DELETE /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/activate
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/deactivate
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks
- PUT /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}
- DELETE /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/copy
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/export
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/move
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/permissions
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/permissions
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/register
- POST /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/sparsify
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/statistics
- GET /datacenters/{datacenter:id}/storagedomains/{storagedomain:id}/disks/{disk:id}/statistics/{statistic:id}
- POST /diskprofiles
- GET /diskprofiles
- GET /diskprofiles/{diskprofile:id}
- PUT /diskprofiles/{diskprofile:id}
- DELETE /diskprofiles/{diskprofile:id}
- POST /diskprofiles/{diskprofile:id}/permissions
- GET /diskprofiles/{diskprofile:id}/permissions
- GET /diskprofiles/{diskprofile:id}/permissions/{permission:id}
- DELETE /diskprofiles/{diskprofile:id}/permissions/{permission:id}
- POST /disks
- GET /disks
- PUT /disks/{disk:id}
- GET /disks/{disk:id}
- DELETE /disks/{disk:id}
- POST /disks/{disk:id}/convert
- POST /disks/{disk:id}/copy
- GET /disks/{disk:id}/disksnapshots
- GET /disks/{disk:id}/disksnapshots/{snapshot:id}
- DELETE /disks/{disk:id}/disksnapshots/{snapshot:id}
- POST /disks/{disk:id}/export
- POST /disks/{disk:id}/move
- POST /disks/{disk:id}/permissions
- GET /disks/{disk:id}/permissions
- GET /disks/{disk:id}/permissions/{permission:id}
- DELETE /disks/{disk:id}/permissions/{permission:id}
- POST /disks/{disk:id}/reduce
- POST /disks/{disk:id}/refreshlun
- POST /disks/{disk:id}/sparsify
- GET /disks/{disk:id}/statistics
- GET /disks/{disk:id}/statistics/{statistic:id}
- GET /domains
- GET /domains/{domain:id}
- GET /domains/{domain:id}/groups
- GET /domains/{domain:id}/groups/{group:id}
- GET /domains/{domain:id}/users
- GET /domains/{domain:id}/users/{user:id}
- POST /events
- GET /events
- POST /events/undelete
- GET /events/{event:id}
- DELETE /events/{event:id}
- POST /externalhostproviders
- GET /externalhostproviders
- GET /externalhostproviders/{provider:id}
- PUT /externalhostproviders/{provider:id}
- DELETE /externalhostproviders/{provider:id}
- GET /externalhostproviders/{provider:id}/certificates
- GET /externalhostproviders/{provider:id}/certificates/{certificate:id}
- GET /externalhostproviders/{provider:id}/computeresources
- GET /externalhostproviders/{provider:id}/computeresources/{resource:id}
- GET /externalhostproviders/{provider:id}/discoveredhosts
- GET /externalhostproviders/{provider:id}/discoveredhosts/{host:id}
- GET /externalhostproviders/{provider:id}/hostgroups
- GET /externalhostproviders/{provider:id}/hostgroups/{group:id}
- GET /externalhostproviders/{provider:id}/hosts
- GET /externalhostproviders/{provider:id}/hosts/{host:id}
- POST /externalhostproviders/{provider:id}/importcertificates
- POST /externalhostproviders/{provider:id}/testconnectivity
- POST /externaltemplateimports
- POST /externalvmimports
- POST /groups
- GET /groups
- GET /groups/{group:id}
- DELETE /groups/{group:id}
- POST /groups/{group:id}/permissions
- GET /groups/{group:id}/permissions
- GET /groups/{group:id}/permissions/{permission:id}
- DELETE /groups/{group:id}/permissions/{permission:id}
- GET /groups/{group:id}/roles
- GET /groups/{group:id}/roles/{role:id}
- DELETE /groups/{group:id}/roles/{role:id}
- PUT /groups/{group:id}/roles/{role:id}
- POST /groups/{group:id}/roles/{role:id}/permits
- GET /groups/{group:id}/roles/{role:id}/permits
- GET /groups/{group:id}/roles/{role:id}/permits/{permit:id}
- DELETE /groups/{group:id}/roles/{role:id}/permits/{permit:id}
- POST /groups/{group:id}/tags
- GET /groups/{group:id}/tags
- GET /groups/{group:id}/tags/{tag:id}
- DELETE /groups/{group:id}/tags/{tag:id}
- POST /hosts
- GET /hosts
- GET /hosts/{host:id}
- PUT /hosts/{host:id}
- DELETE /hosts/{host:id}
- POST /hosts/{host:id}/activate
- POST /hosts/{host:id}/affinitylabels
- GET /hosts/{host:id}/affinitylabels
- GET /hosts/{host:id}/affinitylabels/{label:id}
- DELETE /hosts/{host:id}/affinitylabels/{label:id}
- POST /hosts/{host:id}/approve
- POST /hosts/{host:id}/commitnetconfig
- POST /hosts/{host:id}/copyhostnetworks
- GET /hosts/{host:id}/cpuunits
- POST /hosts/{host:id}/deactivate
- GET /hosts/{host:id}/devices
- GET /hosts/{host:id}/devices/{device:id}
- POST /hosts/{host:id}/discoveriscsi
- POST /hosts/{host:id}/enrollcertificate
- GET /hosts/{host:id}/externalnetworkproviderconfigurations
- GET /hosts/{host:id}/externalnetworkproviderconfigurations/{configuration:id}
- POST /hosts/{host:id}/fence
- POST /hosts/{host:id}/fenceagents
- GET /hosts/{host:id}/fenceagents
- GET /hosts/{host:id}/fenceagents/{agent:id}
- PUT /hosts/{host:id}/fenceagents/{agent:id}
- DELETE /hosts/{host:id}/fenceagents/{agent:id}
- POST /hosts/{host:id}/forceselectspm
- GET /hosts/{host:id}/hooks
- GET /hosts/{host:id}/hooks/{hook:id}
- POST /hosts/{host:id}/install
- POST /hosts/{host:id}/iscsidiscover
- POST /hosts/{host:id}/iscsilogin
- GET /hosts/{host:id}/katelloerrata
- GET /hosts/{host:id}/katelloerrata/{katelloerratum:id}
- POST /hosts/{host:id}/networkattachments
- GET /hosts/{host:id}/networkattachments
- GET /hosts/{host:id}/networkattachments/{attachment:id}
- PUT /hosts/{host:id}/networkattachments/{attachment:id}
- DELETE /hosts/{host:id}/networkattachments/{attachment:id}
- GET /hosts/{host:id}/nics
- GET /hosts/{host:id}/nics/{nic:id}
- GET /hosts/{host:id}/nics/{nic:id}/linklayerdiscoveryprotocolelements
- POST /hosts/{host:id}/nics/{nic:id}/networkattachments
- GET /hosts/{host:id}/nics/{nic:id}/networkattachments
- GET /hosts/{host:id}/nics/{nic:id}/networkattachments/{attachment:id}
- PUT /hosts/{host:id}/nics/{nic:id}/networkattachments/{attachment:id}
- DELETE /hosts/{host:id}/nics/{nic:id}/networkattachments/{attachment:id}
- POST /hosts/{host:id}/nics/{nic:id}/networklabels
- GET /hosts/{host:id}/nics/{nic:id}/networklabels
- GET /hosts/{host:id}/nics/{nic:id}/networklabels/{label:id}
- DELETE /hosts/{host:id}/nics/{nic:id}/networklabels/{label:id}
- GET /hosts/{host:id}/nics/{nic:id}/statistics
- GET /hosts/{host:id}/nics/{nic:id}/statistics/{statistic:id}
- POST /hosts/{host:id}/nics/{nic:id}/updatevirtualfunctionsconfiguration
- POST /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowedlabels
- GET /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowedlabels
- GET /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowedlabels/{label:id}
- DELETE /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowedlabels/{label:id}
- POST /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowednetworks
- GET /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowednetworks
- GET /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowednetworks/{network:id}
- DELETE /hosts/{host:id}/nics/{nic:id}/virtualfunctionallowednetworks/{network:id}
- GET /hosts/{host:id}/numanodes
- GET /hosts/{host:id}/numanodes/{node:id}
- GET /hosts/{host:id}/numanodes/{node:id}/statistics
- GET /hosts/{host:id}/numanodes/{node:id}/statistics/{statistic:id}
- POST /hosts/{host:id}/permissions
- GET /hosts/{host:id}/permissions
- GET /hosts/{host:id}/permissions/{permission:id}
- DELETE /hosts/{host:id}/permissions/{permission:id}
- POST /hosts/{host:id}/refresh
- POST /hosts/{host:id}/setupnetworks
- GET /hosts/{host:id}/statistics
- GET /hosts/{host:id}/statistics/{statistic:id}
- GET /hosts/{host:id}/storage
- GET /hosts/{host:id}/storage/{storage:id}
- POST /hosts/{host:id}/storageconnectionextensions
- GET /hosts/{host:id}/storageconnectionextensions
- GET /hosts/{host:id}/storageconnectionextensions/{storageconnectionextension:id}
- PUT /hosts/{host:id}/storageconnectionextensions/{storageconnectionextension:id}
- DELETE /hosts/{host:id}/storageconnectionextensions/{storageconnectionextension:id}
- POST /hosts/{host:id}/syncallnetworks
- POST /hosts/{host:id}/tags
- GET /hosts/{host:id}/tags
- GET /hosts/{host:id}/tags/{tag:id}
- DELETE /hosts/{host:id}/tags/{tag:id}
- GET /hosts/{host:id}/unmanagednetworks
- GET /hosts/{host:id}/unmanagednetworks/{unmanagednetwork:id}
- DELETE /hosts/{host:id}/unmanagednetworks/{unmanagednetwork:id}
- POST /hosts/{host:id}/unregisteredstoragedomainsdiscover
- POST /hosts/{host:id}/upgrade
- POST /hosts/{host:id}/upgradecheck
- GET /icons
- GET /icons/{icon:id}
- POST /imagetransfers
- GET /imagetransfers
- GET /imagetransfers/{imagetransfer:id}
- POST /imagetransfers/{imagetransfer:id}/cancel
- POST /imagetransfers/{imagetransfer:id}/extend
- POST /imagetransfers/{imagetransfer:id}/finalize
- POST /imagetransfers/{imagetransfer:id}/pause
- POST /imagetransfers/{imagetransfer:id}/resume
- POST /instancetypes
- GET /instancetypes
- GET /instancetypes/{instancetype:id}
- PUT /instancetypes/{instancetype:id}
- DELETE /instancetypes/{instancetype:id}
- POST /instancetypes/{instancetype:id}/graphicsconsoles
- GET /instancetypes/{instancetype:id}/graphicsconsoles
- GET /instancetypes/{instancetype:id}/graphicsconsoles/{console:id}
- DELETE /instancetypes/{instancetype:id}/graphicsconsoles/{console:id}
- POST /instancetypes/{instancetype:id}/nics
- GET /instancetypes/{instancetype:id}/nics
- GET /instancetypes/{instancetype:id}/nics/{nic:id}
- PUT /instancetypes/{instancetype:id}/nics/{nic:id}
- DELETE /instancetypes/{instancetype:id}/nics/{nic:id}
- POST /instancetypes/{instancetype:id}/watchdogs
- GET /instancetypes/{instancetype:id}/watchdogs
- GET /instancetypes/{instancetype:id}/watchdogs/{watchdog:id}
- PUT /instancetypes/{instancetype:id}/watchdogs/{watchdog:id}
- DELETE /instancetypes/{instancetype:id}/watchdogs/{watchdog:id}
- POST /jobs
- GET /jobs
- GET /jobs/{job:id}
- POST /jobs/{job:id}/clear
- POST /jobs/{job:id}/end
- POST /jobs/{job:id}/steps
- GET /jobs/{job:id}/steps
- GET /jobs/{job:id}/steps/{step:id}
- POST /jobs/{job:id}/steps/{step:id}/end
- GET /jobs/{job:id}/steps/{step:id}/statistics
- GET /jobs/{job:id}/steps/{step:id}/statistics/{statistic:id}
- GET /katelloerrata
- GET /katelloerrata/{katelloerratum:id}
- POST /macpools
- GET /macpools
- GET /macpools/{macpool:id}
- PUT /macpools/{macpool:id}
- DELETE /macpools/{macpool:id}
- POST /macpools/{macpool:id}/permissions
- GET /macpools/{macpool:id}/permissions
- GET /macpools/{macpool:id}/permissions/{permission:id}
- DELETE /macpools/{macpool:id}/permissions/{permission:id}
- GET /networkfilters
- GET /networkfilters/{networkfilter:id}
- POST /networks
- GET /networks
- GET /networks/{network:id}
- PUT /networks/{network:id}
- DELETE /networks/{network:id}
- POST /networks/{network:id}/networklabels
- GET /networks/{network:id}/networklabels
- GET /networks/{network:id}/networklabels/{label:id}
- DELETE /networks/{network:id}/networklabels/{label:id}
- POST /networks/{network:id}/permissions
- GET /networks/{network:id}/permissions
- GET /networks/{network:id}/permissions/{permission:id}
- DELETE /networks/{network:id}/permissions/{permission:id}
- POST /networks/{network:id}/vnicprofiles
- GET /networks/{network:id}/vnicprofiles
- GET /networks/{network:id}/vnicprofiles/{profile:id}
- DELETE /networks/{network:id}/vnicprofiles/{profile:id}
- POST /networks/{network:id}/vnicprofiles/{profile:id}/permissions
- GET /networks/{network:id}/vnicprofiles/{profile:id}/permissions
- GET /networks/{network:id}/vnicprofiles/{profile:id}/permissions/{permission:id}
- DELETE /networks/{network:id}/vnicprofiles/{profile:id}/permissions/{permission:id}
- POST /openstackimageproviders
- GET /openstackimageproviders
- GET /openstackimageproviders/{provider:id}
- PUT /openstackimageproviders/{provider:id}
- DELETE /openstackimageproviders/{provider:id}
- GET /openstackimageproviders/{provider:id}/certificates
- GET /openstackimageproviders/{provider:id}/certificates/{certificate:id}
- GET /openstackimageproviders/{provider:id}/images
- GET /openstackimageproviders/{provider:id}/images/\{image\:id}
- POST /openstackimageproviders/{provider:id}/images/\{image\:id}/import
- POST /openstackimageproviders/{provider:id}/importcertificates
- POST /openstackimageproviders/{provider:id}/testconnectivity
- POST /openstacknetworkproviders
- GET /openstacknetworkproviders
- GET /openstacknetworkproviders/{provider:id}
- PUT /openstacknetworkproviders/{provider:id}
- DELETE /openstacknetworkproviders/{provider:id}
- GET /openstacknetworkproviders/{provider:id}/certificates
- GET /openstacknetworkproviders/{provider:id}/certificates/{certificate:id}
- POST /openstacknetworkproviders/{provider:id}/importcertificates
- GET /openstacknetworkproviders/{provider:id}/networks
- GET /openstacknetworkproviders/{provider:id}/networks/{network:id}
- POST /openstacknetworkproviders/{provider:id}/networks/{network:id}/import
- POST /openstacknetworkproviders/{provider:id}/networks/{network:id}/subnets
- GET /openstacknetworkproviders/{provider:id}/networks/{network:id}/subnets
- GET /openstacknetworkproviders/{provider:id}/networks/{network:id}/subnets/{subnet:id}
- DELETE /openstacknetworkproviders/{provider:id}/networks/{network:id}/subnets/{subnet:id}
- POST /openstacknetworkproviders/{provider:id}/testconnectivity
- POST /openstackvolumeproviders
- GET /openstackvolumeproviders
- GET /openstackvolumeproviders/{provider:id}
- PUT /openstackvolumeproviders/{provider:id}
- DELETE /openstackvolumeproviders/{provider:id}
- POST /openstackvolumeproviders/{provider:id}/authenticationkeys
- GET /openstackvolumeproviders/{provider:id}/authenticationkeys
- GET /openstackvolumeproviders/{provider:id}/authenticationkeys/{key:id}
- PUT /openstackvolumeproviders/{provider:id}/authenticationkeys/{key:id}
- DELETE /openstackvolumeproviders/{provider:id}/authenticationkeys/{key:id}
- GET /openstackvolumeproviders/{provider:id}/certificates
- GET /openstackvolumeproviders/{provider:id}/certificates/{certificate:id}
- POST /openstackvolumeproviders/{provider:id}/importcertificates
- POST /openstackvolumeproviders/{provider:id}/testconnectivity
- GET /openstackvolumeproviders/{provider:id}/volumetypes
- GET /openstackvolumeproviders/{provider:id}/volumetypes/{type:id}
- GET /operatingsystems
- GET /operatingsystems/{operatingsystem:id}
- GET /options/{option:id}
- POST /permissions
- GET /permissions
- GET /permissions/{permission:id}
- DELETE /permissions/{permission:id}
- POST /roles
- GET /roles
- GET /roles/{role:id}
- DELETE /roles/{role:id}
- PUT /roles/{role:id}
- POST /roles/{role:id}/permits
- GET /roles/{role:id}/permits
- GET /roles/{role:id}/permits/{permit:id}
- DELETE /roles/{role:id}/permits/{permit:id}
- POST /schedulingpolicies
- GET /schedulingpolicies
- GET /schedulingpolicies/{policy:id}
- PUT /schedulingpolicies/{policy:id}
- DELETE /schedulingpolicies/{policy:id}
- POST /schedulingpolicies/{policy:id}/balances
- GET /schedulingpolicies/{policy:id}/balances
- GET /schedulingpolicies/{policy:id}/balances/{balance:id}
- DELETE /schedulingpolicies/{policy:id}/balances/{balance:id}
- POST /schedulingpolicies/{policy:id}/filters
- GET /schedulingpolicies/{policy:id}/filters
- GET /schedulingpolicies/{policy:id}/filters/{filter:id}
- DELETE /schedulingpolicies/{policy:id}/filters/{filter:id}
- POST /schedulingpolicies/{policy:id}/weights
- GET /schedulingpolicies/{policy:id}/weights
- GET /schedulingpolicies/{policy:id}/weights/{weight:id}
- DELETE /schedulingpolicies/{policy:id}/weights/{weight:id}
- GET /schedulingpolicyunits
- GET /schedulingpolicyunits/{unit:id}
- DELETE /schedulingpolicyunits/{unit:id}
- POST /storageconnections
- GET /storageconnections
- GET /storageconnections/{storageconnection:id}
- PUT /storageconnections/{storageconnection:id}
- DELETE /storageconnections/{storageconnection:id}
- POST /storagedomains
- GET /storagedomains
- GET /storagedomains/{storagedomain:id}
- PUT /storagedomains/{storagedomain:id}
- DELETE /storagedomains/{storagedomain:id}
- POST /storagedomains/{storagedomain:id}/diskprofiles
- GET /storagedomains/{storagedomain:id}/diskprofiles
- GET /storagedomains/{storagedomain:id}/diskprofiles/{profile:id}
- DELETE /storagedomains/{storagedomain:id}/diskprofiles/{profile:id}
- POST /storagedomains/{storagedomain:id}/disks
- GET /storagedomains/{storagedomain:id}/disks
- PUT /storagedomains/{storagedomain:id}/disks/{disk:id}
- GET /storagedomains/{storagedomain:id}/disks/{disk:id}
- DELETE /storagedomains/{storagedomain:id}/disks/{disk:id}
- POST /storagedomains/{storagedomain:id}/disks/{disk:id}/copy
- POST /storagedomains/{storagedomain:id}/disks/{disk:id}/export
- POST /storagedomains/{storagedomain:id}/disks/{disk:id}/move
- POST /storagedomains/{storagedomain:id}/disks/{disk:id}/permissions
- GET /storagedomains/{storagedomain:id}/disks/{disk:id}/permissions
- GET /storagedomains/{storagedomain:id}/disks/{disk:id}/permissions/{permission:id}
- DELETE /storagedomains/{storagedomain:id}/disks/{disk:id}/permissions/{permission:id}
- POST /storagedomains/{storagedomain:id}/disks/{disk:id}/reduce
- POST /storagedomains/{storagedomain:id}/disks/{disk:id}/sparsify
- GET /storagedomains/{storagedomain:id}/disks/{disk:id}/statistics
- GET /storagedomains/{storagedomain:id}/disks/{disk:id}/statistics/{statistic:id}
- GET /storagedomains/{storagedomain:id}/disksnapshots
- GET /storagedomains/{storagedomain:id}/disksnapshots/{snapshot:id}
- DELETE /storagedomains/{storagedomain:id}/disksnapshots/{snapshot:id}
- GET /storagedomains/{storagedomain:id}/files
- GET /storagedomains/{storagedomain:id}/files/{file:id}
- GET /storagedomains/{storagedomain:id}/images
- GET /storagedomains/{storagedomain:id}/images/\{image\:id}
- POST /storagedomains/{storagedomain:id}/images/\{image\:id}/import
- POST /storagedomains/{storagedomain:id}/isattached
- POST /storagedomains/{storagedomain:id}/permissions
- GET /storagedomains/{storagedomain:id}/permissions
- GET /storagedomains/{storagedomain:id}/permissions/{permission:id}
- DELETE /storagedomains/{storagedomain:id}/permissions/{permission:id}
- POST /storagedomains/{storagedomain:id}/reduceluns
- POST /storagedomains/{storagedomain:id}/refreshluns
- POST /storagedomains/{storagedomain:id}/storageconnections
- GET /storagedomains/{storagedomain:id}/storageconnections
- GET /storagedomains/{storagedomain:id}/storageconnections/{connection:id}
- DELETE /storagedomains/{storagedomain:id}/storageconnections/{connection:id}
- GET /storagedomains/{storagedomain:id}/templates
- GET /storagedomains/{storagedomain:id}/templates/{template:id}
- DELETE /storagedomains/{storagedomain:id}/templates/{template:id}
- GET /storagedomains/{storagedomain:id}/templates/{template:id}/disks
- GET /storagedomains/{storagedomain:id}/templates/{template:id}/disks/{disk:id}
- POST /storagedomains/{storagedomain:id}/templates/{template:id}/import
- POST /storagedomains/{storagedomain:id}/templates/{template:id}/register
- POST /storagedomains/{storagedomain:id}/updateovfstore
- GET /storagedomains/{storagedomain:id}/vms
- GET /storagedomains/{storagedomain:id}/vms/{vm:id}
- DELETE /storagedomains/{storagedomain:id}/vms/{vm:id}
- GET /storagedomains/{storagedomain:id}/vms/{vm:id}/diskattachments
- GET /storagedomains/{storagedomain:id}/vms/{vm:id}/diskattachments/{attachment:id}
- GET /storagedomains/{storagedomain:id}/vms/{vm:id}/disks
- GET /storagedomains/{storagedomain:id}/vms/{vm:id}/disks/{disk:id}
- POST /storagedomains/{storagedomain:id}/vms/{vm:id}/import
- POST /storagedomains/{storagedomain:id}/vms/{vm:id}/register
- POST /tags
- GET /tags
- GET /tags/{tag:id}
- PUT /tags/{tag:id}
- DELETE /tags/{tag:id}
- POST /templates
- GET /templates
- GET /templates/{template:id}
- PUT /templates/{template:id}
- DELETE /templates/{template:id}
- GET /templates/{template:id}/cdroms
- GET /templates/{template:id}/cdroms/{cdrom:id}
- GET /templates/{template:id}/diskattachments
- GET /templates/{template:id}/diskattachments/{attachment:id}
- DELETE /templates/{template:id}/diskattachments/{attachment:id}
- POST /templates/{template:id}/export
- POST /templates/{template:id}/graphicsconsoles
- GET /templates/{template:id}/graphicsconsoles
- GET /templates/{template:id}/graphicsconsoles/{console:id}
- DELETE /templates/{template:id}/graphicsconsoles/{console:id}
- POST /templates/{template:id}/mediateddevices
- GET /templates/{template:id}/mediateddevices
- GET /templates/{template:id}/mediateddevices/{device:id}
- PUT /templates/{template:id}/mediateddevices/{device:id}
- DELETE /templates/{template:id}/mediateddevices/{device:id}
- POST /templates/{template:id}/nics
- GET /templates/{template:id}/nics
- GET /templates/{template:id}/nics/{nic:id}
- PUT /templates/{template:id}/nics/{nic:id}
- DELETE /templates/{template:id}/nics/{nic:id}
- POST /templates/{template:id}/permissions
- GET /templates/{template:id}/permissions
- GET /templates/{template:id}/permissions/{permission:id}
- DELETE /templates/{template:id}/permissions/{permission:id}
- POST /templates/{template:id}/tags
- GET /templates/{template:id}/tags
- GET /templates/{template:id}/tags/{tag:id}
- DELETE /templates/{template:id}/tags/{tag:id}
- POST /templates/{template:id}/watchdogs
- GET /templates/{template:id}/watchdogs
- GET /templates/{template:id}/watchdogs/{watchdog:id}
- PUT /templates/{template:id}/watchdogs/{watchdog:id}
- DELETE /templates/{template:id}/watchdogs/{watchdog:id}
- POST /users
- GET /users
- GET /users/{user:id}
- PUT /users/{user:id}
- DELETE /users/{user:id}
- POST /users/{user:id}/eventsubscriptions
- GET /users/{user:id}/eventsubscriptions
- GET /users/{user:id}/eventsubscriptions/{eventsubscription:id}
- DELETE /users/{user:id}/eventsubscriptions/{eventsubscription:id}
- GET /users/{user:id}/groups
- POST /users/{user:id}/options
- GET /users/{user:id}/options
- GET /users/{user:id}/options/{option:id}
- DELETE /users/{user:id}/options/{option:id}
- POST /users/{user:id}/permissions
- GET /users/{user:id}/permissions
- GET /users/{user:id}/permissions/{permission:id}
- DELETE /users/{user:id}/permissions/{permission:id}
- GET /users/{user:id}/roles
- GET /users/{user:id}/roles/{role:id}
- DELETE /users/{user:id}/roles/{role:id}
- PUT /users/{user:id}/roles/{role:id}
- POST /users/{user:id}/roles/{role:id}/permits
- GET /users/{user:id}/roles/{role:id}/permits
- GET /users/{user:id}/roles/{role:id}/permits/{permit:id}
- DELETE /users/{user:id}/roles/{role:id}/permits/{permit:id}
- POST /users/{user:id}/sshpublickeys
- GET /users/{user:id}/sshpublickeys
- GET /users/{user:id}/sshpublickeys/{key:id}
- PUT /users/{user:id}/sshpublickeys/{key:id}
- DELETE /users/{user:id}/sshpublickeys/{key:id}
- POST /users/{user:id}/tags
- GET /users/{user:id}/tags
- GET /users/{user:id}/tags/{tag:id}
- DELETE /users/{user:id}/tags/{tag:id}
- POST /vmpools
- GET /vmpools
- GET /vmpools/{pool:id}
- PUT /vmpools/{pool:id}
- DELETE /vmpools/{pool:id}
- POST /vmpools/{pool:id}/allocatevm
- POST /vmpools/{pool:id}/permissions
- GET /vmpools/{pool:id}/permissions
- GET /vmpools/{pool:id}/permissions/{permission:id}
- DELETE /vmpools/{pool:id}/permissions/{permission:id}
- POST /vms
- GET /vms
- GET /vms/{vm:id}
- PUT /vms/{vm:id}
- DELETE /vms/{vm:id}
- POST /vms/{vm:id}/affinitylabels
- GET /vms/{vm:id}/affinitylabels
- GET /vms/{vm:id}/affinitylabels/{label:id}
- DELETE /vms/{vm:id}/affinitylabels/{label:id}
- GET /vms/{vm:id}/applications
- GET /vms/{vm:id}/applications/{application:id}
- POST /vms/{vm:id}/autopincpuandnumanodes
- POST /vms/{vm:id}/backups
- GET /vms/{vm:id}/backups
- GET /vms/{vm:id}/backups/{backup:id}
- GET /vms/{vm:id}/backups/{backup:id}/disks
- GET /vms/{vm:id}/backups/{backup:id}/disks/{disk:id}
- POST /vms/{vm:id}/backups/{backup:id}/finalize
- POST /vms/{vm:id}/cancelmigration
- POST /vms/{vm:id}/cdroms
- GET /vms/{vm:id}/cdroms
- GET /vms/{vm:id}/cdroms/{cdrom:id}
- PUT /vms/{vm:id}/cdroms/{cdrom:id}
- GET /vms/{vm:id}/checkpoints
- GET /vms/{vm:id}/checkpoints/{checkpoint:id}
- DELETE /vms/{vm:id}/checkpoints/{checkpoint:id}
- GET /vms/{vm:id}/checkpoints/{checkpoint:id}/disks
- GET /vms/{vm:id}/checkpoints/{checkpoint:id}/disks/{disk:id}
- POST /vms/{vm:id}/clone
- POST /vms/{vm:id}/commitsnapshot
- POST /vms/{vm:id}/detach
- POST /vms/{vm:id}/diskattachments
- GET /vms/{vm:id}/diskattachments
- GET /vms/{vm:id}/diskattachments/{attachment:id}
- DELETE /vms/{vm:id}/diskattachments/{attachment:id}
- PUT /vms/{vm:id}/diskattachments/{attachment:id}
- POST /vms/{vm:id}/export
- POST /vms/{vm:id}/freezefilesystems
- POST /vms/{vm:id}/graphicsconsoles
- GET /vms/{vm:id}/graphicsconsoles
- GET /vms/{vm:id}/graphicsconsoles/{console:id}
- DELETE /vms/{vm:id}/graphicsconsoles/{console:id}
- POST /vms/{vm:id}/graphicsconsoles/{console:id}/proxyticket
- POST /vms/{vm:id}/graphicsconsoles/{console:id}/remoteviewerconnectionfile
- POST /vms/{vm:id}/graphicsconsoles/{console:id}/ticket
- POST /vms/{vm:id}/hostdevices
- GET /vms/{vm:id}/hostdevices
- GET /vms/{vm:id}/hostdevices/{device:id}
- DELETE /vms/{vm:id}/hostdevices/{device:id}
- GET /vms/{vm:id}/katelloerrata
- GET /vms/{vm:id}/katelloerrata/{katelloerratum:id}
- POST /vms/{vm:id}/logon
- POST /vms/{vm:id}/maintenance
- POST /vms/{vm:id}/mediateddevices
- GET /vms/{vm:id}/mediateddevices
- GET /vms/{vm:id}/mediateddevices/{device:id}
- PUT /vms/{vm:id}/mediateddevices/{device:id}
- DELETE /vms/{vm:id}/mediateddevices/{device:id}
- POST /vms/{vm:id}/migrate
- POST /vms/{vm:id}/nics
- GET /vms/{vm:id}/nics
- GET /vms/{vm:id}/nics/{nic:id}
- PUT /vms/{vm:id}/nics/{nic:id}
- DELETE /vms/{vm:id}/nics/{nic:id}
- POST /vms/{vm:id}/nics/{nic:id}/activate
- POST /vms/{vm:id}/nics/{nic:id}/deactivate
- GET /vms/{vm:id}/nics/{nic:id}/networkfilterparameters
- POST /vms/{vm:id}/nics/{nic:id}/networkfilterparameters
- GET /vms/{vm:id}/nics/{nic:id}/networkfilterparameters/{parameter:id}
- PUT /vms/{vm:id}/nics/{nic:id}/networkfilterparameters/{parameter:id}
- DELETE /vms/{vm:id}/nics/{nic:id}/networkfilterparameters/{parameter:id}
- GET /vms/{vm:id}/nics/{nic:id}/reporteddevices
- GET /vms/{vm:id}/nics/{nic:id}/reporteddevices/{reporteddevice:id}
- GET /vms/{vm:id}/nics/{nic:id}/statistics
- GET /vms/{vm:id}/nics/{nic:id}/statistics/{statistic:id}
- POST /vms/{vm:id}/numanodes
- GET /vms/{vm:id}/numanodes
- GET /vms/{vm:id}/numanodes/{node:id}
- PUT /vms/{vm:id}/numanodes/{node:id}
- DELETE /vms/{vm:id}/numanodes/{node:id}
- POST /vms/{vm:id}/permissions
- GET /vms/{vm:id}/permissions
- GET /vms/{vm:id}/permissions/{permission:id}
- DELETE /vms/{vm:id}/permissions/{permission:id}
- POST /vms/{vm:id}/previewsnapshot
- POST /vms/{vm:id}/reboot
- POST /vms/{vm:id}/reordermacaddresses
- GET /vms/{vm:id}/reporteddevices
- GET /vms/{vm:id}/reporteddevices/{reporteddevice:id}
- POST /vms/{vm:id}/reset
- POST /vms/{vm:id}/screenshot
- GET /vms/{vm:id}/sessions
- GET /vms/{vm:id}/sessions/{session:id}
- POST /vms/{vm:id}/shutdown
- POST /vms/{vm:id}/snapshots
- GET /vms/{vm:id}/snapshots
- GET /vms/{vm:id}/snapshots/{snapshot:id}
- DELETE /vms/{vm:id}/snapshots/{snapshot:id}
- GET /vms/{vm:id}/snapshots/{snapshot:id}/cdroms
- GET /vms/{vm:id}/snapshots/{snapshot:id}/cdroms/{cdrom:id}
- GET /vms/{vm:id}/snapshots/{snapshot:id}/disks
- GET /vms/{vm:id}/snapshots/{snapshot:id}/disks/{disk:id}
- GET /vms/{vm:id}/snapshots/{snapshot:id}/nics
- GET /vms/{vm:id}/snapshots/{snapshot:id}/nics/{nic:id}
- POST /vms/{vm:id}/snapshots/{snapshot:id}/restore
- POST /vms/{vm:id}/start
- GET /vms/{vm:id}/statistics
- GET /vms/{vm:id}/statistics/{statistic:id}
- POST /vms/{vm:id}/stop
- POST /vms/{vm:id}/suspend
- POST /vms/{vm:id}/tags
- GET /vms/{vm:id}/tags
- GET /vms/{vm:id}/tags/{tag:id}
- DELETE /vms/{vm:id}/tags/{tag:id}
- POST /vms/{vm:id}/thawfilesystems
- POST /vms/{vm:id}/ticket
- POST /vms/{vm:id}/undosnapshot
- POST /vms/{vm:id}/watchdogs
- GET /vms/{vm:id}/watchdogs
- GET /vms/{vm:id}/watchdogs/{watchdog:id}
- PUT /vms/{vm:id}/watchdogs/{watchdog:id}
- DELETE /vms/{vm:id}/watchdogs/{watchdog:id}
- POST /vnicprofiles
- GET /vnicprofiles
- GET /vnicprofiles/{profile:id}
- PUT /vnicprofiles/{profile:id}
- DELETE /vnicprofiles/{profile:id}
- POST /vnicprofiles/{profile:id}/permissions
- GET /vnicprofiles/{profile:id}/permissions
- GET /vnicprofiles/{profile:id}/permissions/{permission:id}
- DELETE /vnicprofiles/{profile:id}/permissions/{permission:id}
Chapter 6. Services Copy linkLink copied to clipboard!
This section enumerates all the services that are available in the API.
6.1. AffinityGroup Copy linkLink copied to clipboard!
This service manages a single affinity group.
| Name | Summary |
|---|---|
|
| Retrieve the affinity group details. |
|
| Remove the affinity group. |
|
| Update the affinity group. |
6.1.1. get GET Copy linkLink copied to clipboard!
Retrieve the affinity group details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The affinity group. |
6.1.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.1.2. remove DELETE Copy linkLink copied to clipboard!
Remove the affinity group.
DELETE /ovirt-engine/api/clusters/000-000/affinitygroups/123-456
DELETE /ovirt-engine/api/clusters/000-000/affinitygroups/123-456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.1.3. update PUT Copy linkLink copied to clipboard!
Update the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The affinity group. |
6.2. AffinityGroupHost Copy linkLink copied to clipboard!
This service manages a single host to affinity group assignment.
| Name | Summary |
|---|---|
|
| Remove host from the affinity group. |
6.2.1. remove DELETE Copy linkLink copied to clipboard!
Remove host from the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.3. AffinityGroupHostLabel Copy linkLink copied to clipboard!
This service manages a single host label assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Remove this label from the affinity group. |
6.3.1. remove DELETE Copy linkLink copied to clipboard!
Remove this label from the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.4. AffinityGroupHostLabels Copy linkLink copied to clipboard!
This service manages a collection of all host labels assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Adds a host label to the affinity group. |
|
| List all host labels assigned to this affinity group. |
6.4.1. add POST Copy linkLink copied to clipboard!
Adds a host label to the affinity group.
For example, to add the label 789 to the affinity group 456 of cluster 123, send a request like this:
POST /ovirt-engine/api/clusters/123/affinitygroups/456/hostlabels
POST /ovirt-engine/api/clusters/123/affinitygroups/456/hostlabels
With the following body:
<affinity_label id="789"/>
<affinity_label id="789"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The AffinityLabel object to add to the affinity group. |
6.4.2. list GET Copy linkLink copied to clipboard!
List all host labels assigned to this affinity group.
The order of the returned labels isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Host labels assigned to the affinity group. | |
|
| In | Sets the maximum number of host labels to return. |
6.4.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.4.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of host labels to return. If not specified, all the labels are returned.
6.5. AffinityGroupHosts Copy linkLink copied to clipboard!
This service manages a collection of all hosts assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Adds a host to the affinity group. |
|
| List all hosts assigned to this affinity group. |
6.5.1. add POST Copy linkLink copied to clipboard!
Adds a host to the affinity group.
For example, to add the host 789 to the affinity group 456 of cluster 123, send a request like this:
POST /ovirt-engine/api/clusters/123/affinitygroups/456/hosts
POST /ovirt-engine/api/clusters/123/affinitygroups/456/hosts
With the following body:
<host id="789"/>
<host id="789"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The host to be added to the affinity group. |
6.5.2. list GET Copy linkLink copied to clipboard!
List all hosts assigned to this affinity group.
The order of the returned hosts isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of hosts assigned to this affinity group. | |
|
| In | Sets the maximum number of hosts to return. |
6.5.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.5.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified, all the hosts are returned.
6.6. AffinityGroupVm Copy linkLink copied to clipboard!
This service manages a single virtual machine to affinity group assignment.
| Name | Summary |
|---|---|
|
| Remove this virtual machine from the affinity group. |
6.6.1. remove DELETE Copy linkLink copied to clipboard!
Remove this virtual machine from the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.7. AffinityGroupVmLabel Copy linkLink copied to clipboard!
This service manages a single virtual machine label assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Remove this label from the affinity group. |
6.7.1. remove DELETE Copy linkLink copied to clipboard!
Remove this label from the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.8. AffinityGroupVmLabels Copy linkLink copied to clipboard!
This service manages a collection of all virtual machine labels assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Adds a virtual machine label to the affinity group. |
|
| List all virtual machine labels assigned to this affinity group. |
6.8.1. add POST Copy linkLink copied to clipboard!
Adds a virtual machine label to the affinity group.
For example, to add the label 789 to the affinity group 456 of cluster 123, send a request like this:
POST /ovirt-engine/api/clusters/123/affinitygroups/456/vmlabels
POST /ovirt-engine/api/clusters/123/affinitygroups/456/vmlabels
With the following body:
<affinity_label id="789"/>
<affinity_label id="789"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The AffinityLabel object to add to the affinity group. |
6.8.2. list GET Copy linkLink copied to clipboard!
List all virtual machine labels assigned to this affinity group.
The order of the returned labels isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Virtual machine labels assigned to the affinity group. | |
|
| In | Sets the maximum number of virtual machine labels to return. |
6.8.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.8.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machine labels to return. If not specified, all the labels are returned.
6.9. AffinityGroupVms Copy linkLink copied to clipboard!
This service manages a collection of all the virtual machines assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Adds a virtual machine to the affinity group. |
|
| List all virtual machines assigned to this affinity group. |
6.9.1. add POST Copy linkLink copied to clipboard!
Adds a virtual machine to the affinity group.
For example, to add the virtual machine 789 to the affinity group 456 of cluster 123, send a request like this:
POST /ovirt-engine/api/clusters/123/affinitygroups/456/vms
POST /ovirt-engine/api/clusters/123/affinitygroups/456/vms
With the following body:
<vm id="789"/>
<vm id="789"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.9.2. list GET Copy linkLink copied to clipboard!
List all virtual machines assigned to this affinity group.
The order of the returned virtual machines isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of virtual machines to return. | |
|
| Vm[] | Out |
6.9.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.9.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machines to return. If not specified, all the virtual machines are returned.
6.10. AffinityGroups Copy linkLink copied to clipboard!
The affinity groups service manages virtual machine relationships and dependencies.
| Name | Summary |
|---|---|
|
| Create a new affinity group. |
|
| List existing affinity groups. |
6.10.1. add POST Copy linkLink copied to clipboard!
Create a new affinity group.
Post a request like in the example below to create a new affinity group:
POST /ovirt-engine/api/clusters/000-000/affinitygroups
POST /ovirt-engine/api/clusters/000-000/affinitygroups
And use the following example in its body:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The affinity group object to create. |
6.10.2. list GET Copy linkLink copied to clipboard!
List existing affinity groups.
The order of the affinity groups results isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of existing affinity groups. | |
|
| In | Sets the maximum number of affinity groups to return. |
6.10.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.10.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of affinity groups to return. If not specified all the affinity groups are returned.
6.11. AffinityLabel Copy linkLink copied to clipboard!
The details of a single affinity label.
| Name | Summary |
|---|---|
|
| Retrieves the details of a label. |
|
| Removes a label from the system and clears all assignments of the removed label. |
|
| Updates a label. |
6.11.1. get GET Copy linkLink copied to clipboard!
Retrieves the details of a label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.11.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.11.2. remove DELETE Copy linkLink copied to clipboard!
Removes a label from the system and clears all assignments of the removed label.
6.11.3. update PUT Copy linkLink copied to clipboard!
Updates a label. This call will update all metadata, such as the name or description.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.12. AffinityLabelHost Copy linkLink copied to clipboard!
This service represents a host that has a specific label when accessed through the affinitylabels/hosts subcollection.
| Name | Summary |
|---|---|
|
| Retrieves details about a host that has this label assigned. |
|
| Remove a label from a host. |
6.12.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a host that has this label assigned.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.12.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.12.2. remove DELETE Copy linkLink copied to clipboard!
Remove a label from a host.
6.13. AffinityLabelHosts Copy linkLink copied to clipboard!
This service represents list of hosts that have a specific label when accessed through the affinitylabels/hosts subcollection.
| Name | Summary |
|---|---|
|
| Add a label to a host. |
|
| List all hosts with the label. |
6.13.1. add POST Copy linkLink copied to clipboard!
Add a label to a host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.13.2. list GET Copy linkLink copied to clipboard!
List all hosts with the label.
The order of the returned hosts isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.13.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.14. AffinityLabelVm Copy linkLink copied to clipboard!
This service represents a vm that has a specific label when accessed through the affinitylabels/vms subcollection.
| Name | Summary |
|---|---|
|
| Retrieves details about a vm that has this label assigned. |
|
| Remove a label from a vm. |
6.14.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a vm that has this label assigned.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.14.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.14.2. remove DELETE Copy linkLink copied to clipboard!
Remove a label from a vm.
6.15. AffinityLabelVms Copy linkLink copied to clipboard!
This service represents list of vms that have a specific label when accessed through the affinitylabels/vms subcollection.
| Name | Summary |
|---|---|
|
| Add a label to a vm. |
|
| List all virtual machines with the label. |
6.15.1. add POST Copy linkLink copied to clipboard!
Add a label to a vm.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.15.2. list GET Copy linkLink copied to clipboard!
List all virtual machines with the label.
The order of the returned virtual machines isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Vm[] | Out |
6.15.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.16. AffinityLabels Copy linkLink copied to clipboard!
Manages the affinity labels available in the system.
| Name | Summary |
|---|---|
|
| Creates a new label. |
|
| Lists all labels present in the system. |
6.16.1. add POST Copy linkLink copied to clipboard!
Creates a new label. The label is automatically attached to all entities mentioned in the vms or hosts lists.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.16.2. list GET Copy linkLink copied to clipboard!
Lists all labels present in the system.
The order of the returned labels isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of labels to return. |
6.16.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.16.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of labels to return. If not specified all the labels are returned.
6.17. Area Copy linkLink copied to clipboard!
This annotation is intended to specify what oVirt area is the annotated concept related to. Currently the following areas are in use, and they are closely related to the oVirt teams, but not necessarily the same:
- Infrastructure
- Network
- SLA
- Storage
- Virtualization
A concept may be associated to more than one area, or to no area.
The value of this annotation is intended for reporting only, and it doesn’t affect at all the generated code or the validity of the model
6.18. AssignedAffinityLabel Copy linkLink copied to clipboard!
This service represents one label to entity assignment when accessed using the entities/affinitylabels subcollection.
| Name | Summary |
|---|---|
|
| Retrieves details about the attached label. |
|
| Removes the label from an entity. |
6.18.1. get GET Copy linkLink copied to clipboard!
Retrieves details about the attached label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.18.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.18.2. remove DELETE Copy linkLink copied to clipboard!
Removes the label from an entity. Does not touch the label itself.
6.19. AssignedAffinityLabels Copy linkLink copied to clipboard!
This service is used to list and manipulate affinity labels that are assigned to supported entities when accessed using entities/affinitylabels.
| Name | Summary |
|---|---|
|
| Attaches a label to an entity. |
|
| Lists all labels that are attached to an entity. |
6.19.1. add POST Copy linkLink copied to clipboard!
Attaches a label to an entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.19.2. list GET Copy linkLink copied to clipboard!
Lists all labels that are attached to an entity.
The order of the returned entities isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.19.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.20. AssignedCpuProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.20.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.20.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.20.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.21. AssignedCpuProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new cpu profile for the cluster. |
|
| List the CPU profiles assigned to the cluster. |
6.21.1. add POST Copy linkLink copied to clipboard!
Add a new cpu profile for the cluster.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.21.2. list GET Copy linkLink copied to clipboard!
List the CPU profiles assigned to the cluster.
The order of the returned CPU profiles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.21.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.21.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.22. AssignedDiskProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.22.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.22.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.22.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.23. AssignedDiskProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new disk profile for the storage domain. |
|
| Returns the list of disk profiles assigned to the storage domain. |
6.23.1. add POST Copy linkLink copied to clipboard!
Add a new disk profile for the storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.23.2. list GET Copy linkLink copied to clipboard!
Returns the list of disk profiles assigned to the storage domain.
The order of the returned disk profiles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.23.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.23.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.24. AssignedPermissions Copy linkLink copied to clipboard!
Represents a permission sub-collection, scoped by user, group or some entity type.
| Name | Summary |
|---|---|
|
| Assign a new permission to a user or group for specific entity. |
|
| List all the permissions of the specific entity. |
6.24.1. add POST Copy linkLink copied to clipboard!
Assign a new permission to a user or group for specific entity.
For example, to assign the UserVmManager role to the virtual machine with id 123 to the user with id 456 send a request like this:
POST /ovirt-engine/api/vms/123/permissions
POST /ovirt-engine/api/vms/123/permissions
With a request body like this:
To assign the SuperUser role to the system to the user with id 456 send a request like this:
POST /ovirt-engine/api/permissions
POST /ovirt-engine/api/permissions
With a request body like this:
If you want to assign permission to the group instead of the user please replace the user element with the group element with proper id of the group. For example to assign the UserRole role to the cluster with id 123 to the group with id 789 send a request like this:
POST /ovirt-engine/api/clusters/123/permissions
POST /ovirt-engine/api/clusters/123/permissions
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The permission. |
6.24.2. list GET Copy linkLink copied to clipboard!
List all the permissions of the specific entity.
For example to list all the permissions of the cluster with id 123 send a request like this:
GET /ovirt-engine/api/clusters/123/permissions
GET /ovirt-engine/api/clusters/123/permissions
The order of the returned permissions isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of permissions. |
6.24.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.25. AssignedRoles Copy linkLink copied to clipboard!
Represents a roles sub-collection, for example scoped by user.
| Name | Summary |
|---|---|
|
| Returns the roles assigned to the permission. |
6.25.1. list GET Copy linkLink copied to clipboard!
Returns the roles assigned to the permission.
The order of the returned roles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of roles to return. | |
|
| Out |
6.25.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.25.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of roles to return. If not specified all the roles are returned.
6.26. AssignedTag Copy linkLink copied to clipboard!
A service to manage assignment of specific tag to specific entities in system.
| Name | Summary |
|---|---|
|
| Gets the information about the assigned tag. |
|
| Unassign tag from specific entity in the system. |
6.26.1. get GET Copy linkLink copied to clipboard!
Gets the information about the assigned tag.
For example to retrieve the information about the tag with the id 456 which is assigned to virtual machine with id 123 send a request like this:
GET /ovirt-engine/api/vms/123/tags/456
GET /ovirt-engine/api/vms/123/tags/456
<tag href="/ovirt-engine/api/tags/456" id="456"> <name>root</name> <description>root</description> <vm href="/ovirt-engine/api/vms/123" id="123"/> </tag>
<tag href="/ovirt-engine/api/tags/456" id="456">
<name>root</name>
<description>root</description>
<vm href="/ovirt-engine/api/vms/123" id="123"/>
</tag>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The assigned tag. |
6.26.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.26.2. remove DELETE Copy linkLink copied to clipboard!
Unassign tag from specific entity in the system.
For example to unassign the tag with id 456 from virtual machine with id 123 send a request like this:
DELETE /ovirt-engine/api/vms/123/tags/456
DELETE /ovirt-engine/api/vms/123/tags/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.27. AssignedTags Copy linkLink copied to clipboard!
A service to manage collection of assignment of tags to specific entities in system.
| Name | Summary |
|---|---|
|
| Assign tag to specific entity in the system. |
|
| List all tags assigned to the specific entity. |
6.27.1. add POST Copy linkLink copied to clipboard!
Assign tag to specific entity in the system.
For example to assign tag mytag to virtual machine with the id 123 send a request like this:
POST /ovirt-engine/api/vms/123/tags
POST /ovirt-engine/api/vms/123/tags
With a request body like this:
<tag> <name>mytag</name> </tag>
<tag>
<name>mytag</name>
</tag>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The assigned tag. |
6.27.2. list GET Copy linkLink copied to clipboard!
List all tags assigned to the specific entity.
For example to list all the tags of the virtual machine with id 123 send a request like this:
GET /ovirt-engine/api/vms/123/tags
GET /ovirt-engine/api/vms/123/tags
The order of the returned tags isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of tags to return. | |
|
| Tag[] | Out | The list of assigned tags. |
6.27.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.27.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of tags to return. If not specified all the tags are returned.
6.28. AssignedVnicProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.28.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.28.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.28.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.29. AssignedVnicProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new virtual network interface card profile for the network. |
|
| Returns the list of VNIC profiles assifned to the network. |
6.29.1. add POST Copy linkLink copied to clipboard!
Add a new virtual network interface card profile for the network.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.29.2. list GET Copy linkLink copied to clipboard!
Returns the list of VNIC profiles assifned to the network.
The order of the returned VNIC profiles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.29.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.29.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.30. AttachedStorageDomain Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| This operation activates an attached storage domain. |
|
| This operation deactivates an attached storage domain. |
|
| |
|
|
6.30.1. activate POST Copy linkLink copied to clipboard!
This operation activates an attached storage domain. Once the storage domain is activated it is ready for use with the data center.
POST /ovirt-engine/api/datacenters/123/storagedomains/456/activate
POST /ovirt-engine/api/datacenters/123/storagedomains/456/activate
The activate action does not take any action specific parameters, so the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.30.2. deactivate POST Copy linkLink copied to clipboard!
This operation deactivates an attached storage domain. Once the storage domain is deactivated it will not be used with the data center. For example, to deactivate storage domain 456, send the following request:
POST /ovirt-engine/api/datacenters/123/storagedomains/456/deactivate
POST /ovirt-engine/api/datacenters/123/storagedomains/456/deactivate
With a request body like this:
<action/>
<action/>
If the force parameter is true then the operation will succeed, even if the OVF update which takes place before the deactivation of the storage domain failed. If the force parameter is false and the OVF update failed, the deactivation of the storage domain will also fail.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. | |
|
| In | Indicates if the operation should succeed and the storage domain should be moved to a deactivated state, even if the OVF update for the storage domain failed. |
6.30.2.1. force Copy linkLink copied to clipboard!
Indicates if the operation should succeed and the storage domain should be moved to a deactivated state, even if the OVF update for the storage domain failed. For example, to deactivate storage domain 456 using force flag, send the following request:
POST /ovirt-engine/api/datacenters/123/storagedomains/456/deactivate
POST /ovirt-engine/api/datacenters/123/storagedomains/456/deactivate
With a request body like this:
<action> <force>true</force> <action>
<action>
<force>true</force>
<action>
This parameter is optional, and the default value is false.
6.30.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.30.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.30.4. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.31. AttachedStorageDomainDisk Copy linkLink copied to clipboard!
Manages a single disk available in a storage domain attached to a data center.
Since version 4.2 of the engine this service is intended only to list disks available in the storage domain, and to register unregistered disks. All the other operations, like copying a disk, moving a disk, etc, have been deprecated and will be removed in the future. To perform those operations use the service that manages all the disks of the system or the service that manages a specific disk.
| Name | Summary |
|---|---|
|
| Copies a disk to the specified storage domain. |
|
| Exports a disk to an export storage domain. |
|
| Retrieves the description of the disk. |
|
| Moves a disk to another storage domain. |
|
| Registers an unregistered disk. |
|
| Removes a disk. |
|
| Sparsify the disk. |
|
| Updates the disk. |
6.31.1. copy POST Copy linkLink copied to clipboard!
Copies a disk to the specified storage domain.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To copy a disk use the copy operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Description of the resulting disk. | |
|
| In | The storage domain where the new disk will be created. |
6.31.2. export POST Copy linkLink copied to clipboard!
Exports a disk to an export storage domain.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To export a disk use the export operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | The export storage domain where the disk should be exported to. |
6.31.3. get GET Copy linkLink copied to clipboard!
Retrieves the description of the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The description of the disk. | |
|
| In | Indicates which inner links should be followed. |
6.31.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.31.4. move POST Copy linkLink copied to clipboard!
Moves a disk to another storage domain.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To move a disk use the move operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the move should be performed asynchronously. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | The storage domain where the disk will be moved to. |
6.31.5. register POST Copy linkLink copied to clipboard!
Registers an unregistered disk.
6.31.6. remove DELETE Copy linkLink copied to clipboard!
Removes a disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To remove a disk use the remove operation of the service that manages that disk.
6.31.7. sparsify POST Copy linkLink copied to clipboard!
Sparsify the disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To remove a disk use the remove operation of the service that manages that disk.
6.31.8. update PUT Copy linkLink copied to clipboard!
Updates the disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To update a disk use the update operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The update to apply to the disk. |
6.32. AttachedStorageDomainDisks Copy linkLink copied to clipboard!
Manages the collection of disks available inside an storage domain that is attached to a data center.
| Name | Summary |
|---|---|
|
| Adds or registers a disk. |
|
| Retrieve the list of disks that are available in the storage domain. |
6.32.1. add POST Copy linkLink copied to clipboard!
Adds or registers a disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To add a new disk use the add operation of the service that manages the disks of the system. To register an unregistered disk use the register operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The disk to add or register. | |
|
| In | Indicates if a new disk should be added or if an existing unregistered disk should be registered. |
6.32.1.1. unregistered Copy linkLink copied to clipboard!
Indicates if a new disk should be added or if an existing unregistered disk should be registered. If the value is true then the identifier of the disk to register needs to be provided. For example, to register the disk with id 456 send a request like this:
POST /ovirt-engine/api/storagedomains/123/disks?unregistered=true
POST /ovirt-engine/api/storagedomains/123/disks?unregistered=true
With a request body like this:
<disk id="456"/>
<disk id="456"/>
If the value is false then a new disk will be created in the storage domain. In that case the provisioned_size, format and name attributes are mandatory. For example, to create a new copy on write disk of 1 GiB, send a request like this:
POST /ovirt-engine/api/storagedomains/123/disks
POST /ovirt-engine/api/storagedomains/123/disks
With a request body like this:
<disk> <name>mydisk</name> <format>cow</format> <provisioned_size>1073741824</provisioned_size> </disk>
<disk>
<name>mydisk</name>
<format>cow</format>
<provisioned_size>1073741824</provisioned_size>
</disk>
The default value is false.
6.32.2. list GET Copy linkLink copied to clipboard!
Retrieve the list of disks that are available in the storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | List of retrieved disks. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. |
6.32.2.1. disks Copy linkLink copied to clipboard!
List of retrieved disks.
The order of the returned disks isn’t guaranteed.
6.32.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.32.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.33. AttachedStorageDomains Copy linkLink copied to clipboard!
Manages the storage domains attached to a data center.
| Name | Summary |
|---|---|
|
| Attaches an existing storage domain to the data center. |
|
| Returns the list of storage domains attached to the data center. |
6.33.1. add POST Copy linkLink copied to clipboard!
Attaches an existing storage domain to the data center.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The storage domain to attach to the data center. |
6.33.2. list GET Copy linkLink copied to clipboard!
Returns the list of storage domains attached to the data center.
The order of the returned storage domains isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of storage domains to return. | |
|
| Out | A list of storage domains that are attached to the data center. |
6.33.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.33.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of storage domains to return. If not specified all the storage domains are returned.
6.34. Balance Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.34.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. |
6.34.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.34.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.35. Balances Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a balance module to a specified user defined scheduling policy. |
|
| Returns the list of balance modules used by the scheduling policy. |
6.35.1. add POST Copy linkLink copied to clipboard!
Add a balance module to a specified user defined scheduling policy.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.35.2. list GET Copy linkLink copied to clipboard!
Returns the list of balance modules used by the scheduling policy.
The order of the returned balance modules isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of balances to return. |
6.35.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.35.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of balances to return. If not specified all the balances are returned.
6.36. Bookmark Copy linkLink copied to clipboard!
A service to manage a bookmark.
| Name | Summary |
|---|---|
|
| Get a bookmark. |
|
| Remove a bookmark. |
|
| Update a bookmark. |
6.36.1. get GET Copy linkLink copied to clipboard!
Get a bookmark.
An example for getting a bookmark:
GET /ovirt-engine/api/bookmarks/123
GET /ovirt-engine/api/bookmarks/123
<bookmark href="/ovirt-engine/api/bookmarks/123" id="123"> <name>example_vm</name> <value>vm: name=example*</value> </bookmark>
<bookmark href="/ovirt-engine/api/bookmarks/123" id="123">
<name>example_vm</name>
<value>vm: name=example*</value>
</bookmark>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The requested bookmark. | |
|
| In | Indicates which inner links should be followed. |
6.36.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.36.2. remove DELETE Copy linkLink copied to clipboard!
Remove a bookmark.
An example for removing a bookmark:
DELETE /ovirt-engine/api/bookmarks/123
DELETE /ovirt-engine/api/bookmarks/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.36.3. update PUT Copy linkLink copied to clipboard!
Update a bookmark.
An example for updating a bookmark:
PUT /ovirt-engine/api/bookmarks/123
PUT /ovirt-engine/api/bookmarks/123
With the request body:
<bookmark> <name>new_example_vm</name> <value>vm: name=new_example*</value> </bookmark>
<bookmark>
<name>new_example_vm</name>
<value>vm: name=new_example*</value>
</bookmark>
6.37. Bookmarks Copy linkLink copied to clipboard!
A service to manage bookmarks.
| Name | Summary |
|---|---|
|
| Adding a new bookmark. |
|
| Listing all the available bookmarks. |
6.37.1. add POST Copy linkLink copied to clipboard!
Adding a new bookmark.
Example of adding a bookmark:
POST /ovirt-engine/api/bookmarks
POST /ovirt-engine/api/bookmarks
<bookmark> <name>new_example_vm</name> <value>vm: name=new_example*</value> </bookmark>
<bookmark>
<name>new_example_vm</name>
<value>vm: name=new_example*</value>
</bookmark>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The added bookmark. |
6.37.2. list GET Copy linkLink copied to clipboard!
Listing all the available bookmarks.
Example of listing bookmarks:
GET /ovirt-engine/api/bookmarks
GET /ovirt-engine/api/bookmarks
The order of the returned bookmarks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of available bookmarks. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of bookmarks to return. |
6.37.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.37.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of bookmarks to return. If not specified all the bookmarks are returned.
6.38. Cluster Copy linkLink copied to clipboard!
A service to manage a specific cluster.
| Name | Summary |
|---|---|
|
| Gets information about the cluster. |
|
| Refresh the Gluster heal info for all volumes in cluster. |
|
| Removes the cluster from the system. |
|
| |
|
| Synchronizes all networks on the cluster. |
|
| Updates information about the cluster. |
|
| Start, update or finish upgrade process for the cluster based on the action value. |
6.38.1. get GET Copy linkLink copied to clipboard!
Gets information about the cluster.
An example of getting a cluster:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. |
6.38.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.38.2. refreshglusterhealstatus POST Copy linkLink copied to clipboard!
Refresh the Gluster heal info for all volumes in cluster.
For example, Cluster 123, send a request like this:
POST /ovirt-engine/api/clusters/123/refreshglusterhealstatus
POST /ovirt-engine/api/clusters/123/refreshglusterhealstatus
6.38.3. remove DELETE Copy linkLink copied to clipboard!
Removes the cluster from the system.
DELETE /ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000
DELETE /ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.38.4. resetemulatedmachine POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reset should be performed asynchronously. |
6.38.5. syncallnetworks POST Copy linkLink copied to clipboard!
Synchronizes all networks on the cluster.
POST /ovirt-engine/api/clusters/123/syncallnetworks
POST /ovirt-engine/api/clusters/123/syncallnetworks
With a request body like this:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.38.6. update PUT Copy linkLink copied to clipboard!
Updates information about the cluster.
Only the specified fields are updated; others remain unchanged.
For example, to update the cluster’s CPU:
PUT /ovirt-engine/api/clusters/123
PUT /ovirt-engine/api/clusters/123
With a request body like this:
<cluster>
<cpu>
<type>Intel Haswell-noTSX Family</type>
</cpu>
</cluster>
<cluster>
<cpu>
<type>Intel Haswell-noTSX Family</type>
</cpu>
</cluster>
6.38.7. upgrade POST Copy linkLink copied to clipboard!
Start, update or finish upgrade process for the cluster based on the action value. This action marks the cluster for upgrade, updates the progress, or clears the upgrade running flag on the cluster based on the action value which takes values of start, stop or update_progress.
POST /ovirt-engine/api/clusters/123/upgrade
POST /ovirt-engine/api/clusters/123/upgrade
With a request body like this to mark the cluster for upgrade:
<action>
<upgrade_action>
start
</upgrade_action>
</action>
<action>
<upgrade_action>
start
</upgrade_action>
</action>
After starting the upgrade, use a request body like this to update the progress to 15%:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Explicitly set the upgrade correlation identifier. | |
|
| In | The action to be performed. | |
|
| In | Update the upgrade’s progress as a percent complete of the total process. |
6.38.7.1. correlation_id Copy linkLink copied to clipboard!
Explicitly set the upgrade correlation identifier. Use to correlate events detailing the cluster upgrade to the upgrade itself. If not specificed, the correlation id from Correlation-Id http header will be used.
6.39. ClusterEnabledFeature Copy linkLink copied to clipboard!
Represents a feature enabled for the cluster.
| Name | Summary |
|---|---|
|
| Provides the information about the cluster feature enabled. |
|
| Disables a cluster feature. |
6.39.1. get GET Copy linkLink copied to clipboard!
Provides the information about the cluster feature enabled.
For example, to find details of the enabled feature 456 for cluster 123, send a request like this:
GET /ovirt-engine/api/clusters/123/enabledfeatures/456
GET /ovirt-engine/api/clusters/123/enabledfeatures/456
That will return a ClusterFeature object containing the name:
<cluster_feature id="456"> <name>libgfapi_supported</name> </cluster_feature>
<cluster_feature id="456">
<name>libgfapi_supported</name>
</cluster_feature>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved cluster feature that’s enabled. | |
|
| In | Indicates which inner links should be followed. |
6.39.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.39.2. remove DELETE Copy linkLink copied to clipboard!
Disables a cluster feature.
For example, to disable the feature 456 of cluster 123 send a request like this:
DELETE /ovirt-engine/api/clusters/123/enabledfeatures/456
DELETE /ovirt-engine/api/clusters/123/enabledfeatures/456
6.40. ClusterEnabledFeatures Copy linkLink copied to clipboard!
Provides information about the additional features that are enabled for this cluster. The features that are enabled are the available features for the cluster level
| Name | Summary |
|---|---|
|
| Enable an additional feature for a cluster. |
|
| Lists the additional features enabled for the cluster. |
6.40.1. add POST Copy linkLink copied to clipboard!
Enable an additional feature for a cluster.
For example, to enable a feature 456 on cluster 123, send a request like this:
POST /ovirt-engine/api/clusters/123/enabledfeatures
POST /ovirt-engine/api/clusters/123/enabledfeatures
The request body should look like this:
<cluster_feature id="456"/>
<cluster_feature id="456"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.40.2. list GET Copy linkLink copied to clipboard!
Lists the additional features enabled for the cluster.
For example, to get the features enabled for cluster 123 send a request like this:
GET /ovirt-engine/api/clusters/123/enabledfeatures
GET /ovirt-engine/api/clusters/123/enabledfeatures
This will return a list of features:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved features. | |
|
| In | Indicates which inner links should be followed. |
6.40.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.41. ClusterExternalProviders Copy linkLink copied to clipboard!
This service lists external providers.
| Name | Summary |
|---|---|
|
| Returns the list of external providers. |
6.41.1. list GET Copy linkLink copied to clipboard!
Returns the list of external providers.
The order of the returned list of providers is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.41.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.42. ClusterFeature Copy linkLink copied to clipboard!
Represents a feature enabled for the cluster level
| Name | Summary |
|---|---|
|
| Provides the information about the a cluster feature supported by a cluster level. |
6.42.1. get GET Copy linkLink copied to clipboard!
Provides the information about the a cluster feature supported by a cluster level.
For example, to find details of the cluster feature 456 for cluster level 4.1, send a request like this:
GET /ovirt-engine/api/clusterlevels/4.1/clusterfeatures/456
GET /ovirt-engine/api/clusterlevels/4.1/clusterfeatures/456
That will return a ClusterFeature object containing the name:
<cluster_feature id="456"> <name>libgfapi_supported</name> </cluster_feature>
<cluster_feature id="456">
<name>libgfapi_supported</name>
</cluster_feature>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved cluster feature. | |
|
| In | Indicates which inner links should be followed. |
6.42.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.43. ClusterFeatures Copy linkLink copied to clipboard!
Provides information about the cluster features that are supported by a cluster level.
| Name | Summary |
|---|---|
|
| Lists the cluster features supported by the cluster level. |
6.43.1. list GET Copy linkLink copied to clipboard!
Lists the cluster features supported by the cluster level.
GET /ovirt-engine/api/clusterlevels/4.1/clusterfeatures
GET /ovirt-engine/api/clusterlevels/4.1/clusterfeatures
This will return a list of cluster features supported by the cluster level:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved features. | |
|
| In | Indicates which inner links should be followed. |
6.43.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.44. ClusterLevel Copy linkLink copied to clipboard!
Provides information about a specific cluster level. See the ClusterLevels service for more information.
| Name | Summary |
|---|---|
|
| Provides the information about the capabilities of the specific cluster level managed by this service. |
6.44.1. get GET Copy linkLink copied to clipboard!
Provides the information about the capabilities of the specific cluster level managed by this service.
For example, to find what CPU types are supported by level 3.6 you can send a request like this:
GET /ovirt-engine/api/clusterlevels/3.6
GET /ovirt-engine/api/clusterlevels/3.6
That will return a ClusterLevel object containing the supported CPU types, and other information which describes the cluster level:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retreived cluster level. |
6.44.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.45. ClusterLevels Copy linkLink copied to clipboard!
Provides information about the capabilities of different cluster levels supported by the engine. Version 4.0 of the engine supports levels 4.0 and 3.6. Each of these levels support different sets of CPU types, for example. This service provides that information.
| Name | Summary |
|---|---|
|
| Lists the cluster levels supported by the system. |
6.45.1. list GET Copy linkLink copied to clipboard!
Lists the cluster levels supported by the system.
GET /ovirt-engine/api/clusterlevels
GET /ovirt-engine/api/clusterlevels
This will return a list of available cluster levels.
The order of the returned cluster levels isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieved cluster levels. |
6.45.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.46. ClusterNetwork Copy linkLink copied to clipboard!
A service to manage a specific cluster network.
| Name | Summary |
|---|---|
|
| Retrieves the cluster network details. |
|
| Unassigns the network from a cluster. |
|
| Updates the network in the cluster. |
6.46.1. get GET Copy linkLink copied to clipboard!
Retrieves the cluster network details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The cluster network. |
6.46.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.46.2. remove DELETE Copy linkLink copied to clipboard!
Unassigns the network from a cluster.
6.46.3. update PUT Copy linkLink copied to clipboard!
Updates the network in the cluster.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The cluster network. |
6.47. ClusterNetworks Copy linkLink copied to clipboard!
A service to manage cluster networks.
| Name | Summary |
|---|---|
|
| Assigns the network to a cluster. |
|
| Lists the networks that are assigned to the cluster. |
6.47.1. add POST Copy linkLink copied to clipboard!
Assigns the network to a cluster.
Post a request like in the example below to assign the network to a cluster:
POST /ovirt-engine/api/clusters/123/networks
POST /ovirt-engine/api/clusters/123/networks
Use the following example in its body:
<network id="123" />
<network id="123" />
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The network object to be assigned to the cluster. |
6.47.2. list GET Copy linkLink copied to clipboard!
Lists the networks that are assigned to the cluster.
The order of the returned clusters isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out | The list of networks that are assigned to the cluster. |
6.47.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.47.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified, all the networks are returned.
6.48. Clusters Copy linkLink copied to clipboard!
A service to manage clusters.
| Name | Summary |
|---|---|
|
| Creates a new cluster. |
|
| Returns the list of clusters of the system. |
6.48.1. add POST Copy linkLink copied to clipboard!
Creates a new cluster.
This requires the name, cpu.type, and data_center attributes. Identify the data center with either the id or name attribute.
POST /ovirt-engine/api/clusters
POST /ovirt-engine/api/clusters
With a request body like this:
To create a cluster with an external network provider to be deployed on every host that is added to the cluster, send a request like this:
POST /ovirt-engine/api/clusters
POST /ovirt-engine/api/clusters
With a request body containing a reference to the desired provider:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.48.2. list GET Copy linkLink copied to clipboard!
Returns the list of clusters of the system.
The order of the returned clusters is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the search should be performed taking case into account. | |
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of clusters to return. | |
|
| In | A query string used to restrict the returned clusters. |
6.48.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search should be performed taking case into account. The default value is true, which means that case is taken into account. To search ignoring case, set it to false.
6.48.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.48.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of clusters to return. If not specified, all the clusters are returned.
6.49. Copyable Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.49.1. copy POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the copy should be performed asynchronously. |
6.50. CpuProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the specified cpu profile in the system. |
6.50.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.50.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.50.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.50.3. update PUT Copy linkLink copied to clipboard!
Update the specified cpu profile in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.51. CpuProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new cpu profile to the system. |
|
| Returns the list of CPU profiles of the system. |
6.51.1. add POST Copy linkLink copied to clipboard!
Add a new cpu profile to the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.51.2. list GET Copy linkLink copied to clipboard!
Returns the list of CPU profiles of the system.
The order of the returned list of CPU profiles is random.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.51.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.51.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified, all the profiles are returned.
6.52. DataCenter Copy linkLink copied to clipboard!
A service to manage a data center.
| Name | Summary |
|---|---|
|
| Currently, the storage pool manager (SPM) fails to switch to another host if the SPM has uncleared tasks. |
|
| Get a data center. |
|
| Removes the data center. |
|
| Used for manually setting a storage domain in the data center as a master. |
|
| Updates the data center. |
6.52.1. cleanfinishedtasks POST Copy linkLink copied to clipboard!
Currently, the storage pool manager (SPM) fails to switch to another host if the SPM has uncleared tasks. Clearing all finished tasks enables the SPM switching.
For example, to clean all the finished tasks on a data center with ID 123 send a request like this:
POST /ovirt-engine/api/datacenters/123/cleanfinishedtasks
POST /ovirt-engine/api/datacenters/123/cleanfinishedtasks
With a request body like this:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.52.2. get GET Copy linkLink copied to clipboard!
Get a data center.
An example of getting a data center:
GET /ovirt-engine/api/datacenters/123
GET /ovirt-engine/api/datacenters/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. |
6.52.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.52.3. remove DELETE Copy linkLink copied to clipboard!
Removes the data center.
DELETE /ovirt-engine/api/datacenters/123
DELETE /ovirt-engine/api/datacenters/123
Without any special parameters, the storage domains attached to the data center are detached and then removed from the storage. If something fails when performing this operation, for example if there is no host available to remove the storage domains from the storage, the complete operation will fail.
If the force parameter is true then the operation will always succeed, even if something fails while removing one storage domain, for example. The failure is just ignored and the data center is removed from the database anyway.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates if the operation should succeed, and the storage domain removed from the database, even if something fails during the operation. |
6.52.3.1. force Copy linkLink copied to clipboard!
Indicates if the operation should succeed, and the storage domain removed from the database, even if something fails during the operation.
This parameter is optional, and the default value is false.
6.52.4. setmaster POST Copy linkLink copied to clipboard!
Used for manually setting a storage domain in the data center as a master. For example, for setting a storage domain with ID '456' as a master on a data center with ID '123', send a request like this:
POST /ovirt-engine/api/datacenters/123/setmaster
POST /ovirt-engine/api/datacenters/123/setmaster
With a request body like this:
<action> <storage_domain id="456"/> </action>
<action>
<storage_domain id="456"/>
</action>
The new master storage domain can be also specified by its name.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | The new master storage domain for the data center. |
6.52.5. update PUT Copy linkLink copied to clipboard!
Updates the data center.
The name, description, storage_type, version, storage_format and mac_pool elements are updatable post-creation. For example, to change the name and description of data center 123 send a request like this:
PUT /ovirt-engine/api/datacenters/123
PUT /ovirt-engine/api/datacenters/123
With a request body like this:
<data_center> <name>myupdatedname</name> <description>An updated description for the data center</description> </data_center>
<data_center>
<name>myupdatedname</name>
<description>An updated description for the data center</description>
</data_center>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The data center that is being updated. |
6.53. DataCenterNetwork Copy linkLink copied to clipboard!
A service to manage a specific data center network.
| Name | Summary |
|---|---|
|
| Retrieves the data center network details. |
|
| Removes the network. |
|
| Updates the network in the data center. |
6.53.1. get GET Copy linkLink copied to clipboard!
Retrieves the data center network details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The data center network. |
6.53.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.53.2. remove DELETE Copy linkLink copied to clipboard!
Removes the network.
6.53.3. update PUT Copy linkLink copied to clipboard!
Updates the network in the data center.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The data center network. |
6.54. DataCenterNetworks Copy linkLink copied to clipboard!
A service to manage data center networks.
| Name | Summary |
|---|---|
|
| Create a new network in a data center. |
|
| Lists networks in the data center. |
6.54.1. add POST Copy linkLink copied to clipboard!
Create a new network in a data center.
Post a request like in the example below to create a new network in a data center with an ID of 123.
POST /ovirt-engine/api/datacenters/123/networks
POST /ovirt-engine/api/datacenters/123/networks
Use the following example in its body:
<network> <name>mynetwork</name> </network>
<network>
<name>mynetwork</name>
</network>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The network object to be created in the data center. |
6.54.2. list GET Copy linkLink copied to clipboard!
Lists networks in the data center.
The order of the returned list of networks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out | The list of networks which are in the data center. |
6.54.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.54.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified, all the networks are returned.
6.55. DataCenters Copy linkLink copied to clipboard!
A service to manage data centers.
| Name | Summary |
|---|---|
|
| Creates a new data center. |
|
| Lists the data centers. |
6.55.1. add POST Copy linkLink copied to clipboard!
Creates a new data center.
Creation of a new data center requires the name and local elements. For example, to create a data center named mydc that uses shared storage (NFS, iSCSI or fibre channel) send a request like this:
POST /ovirt-engine/api/datacenters
POST /ovirt-engine/api/datacenters
With a request body like this:
<data_center> <name>mydc</name> <local>false</local> </data_center>
<data_center>
<name>mydc</name>
<local>false</local>
</data_center>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The data center that is being added. |
6.55.2. list GET Copy linkLink copied to clipboard!
Lists the data centers.
The following request retrieves a representation of the data centers:
GET /ovirt-engine/api/datacenters
GET /ovirt-engine/api/datacenters
The above request performed with curl:
This is what an example response could look like:
Note the id code of your Default data center. This code identifies this data center in relation to other resources of your virtual environment.
The data center also contains a link to the storage domains collection. The data center uses this collection to attach storage domains from the storage domains main collection.
The order of the returned list of data centers is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of data centers to return. | |
|
| In | A query string used to restrict the returned data centers. |
6.55.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.55.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.55.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of data centers to return. If not specified all the data centers are returned.
6.56. Disk Copy linkLink copied to clipboard!
Manages a single disk.
| Name | Summary |
|---|---|
|
| Converts disk format and/or preallocation mode. |
|
| This operation copies a disk to the specified storage domain. |
|
| Exports a disk to an export storage domain. |
|
| Retrieves the description of the disk. |
|
| Moves a disk to another storage domain. |
|
| Reduces the size of the disk image. |
|
| Refreshes a direct LUN disk with up-to-date information from the storage. |
|
| Removes a disk. |
|
| Sparsify the disk. |
|
| Updates the parameters of the specified disk. |
6.56.1. convert POST Copy linkLink copied to clipboard!
Converts disk format and/or preallocation mode.
For example, to convert the disk format from preallocated-cow to a sparse-raw image, send a request like the following:
POST /ovirt-engine/api/disks/123/convert
POST /ovirt-engine/api/disks/123/convert
With the following request body:
Note: In order to sparsify a disk, two conversions might be needed if the disk is on a Block Storage Domain. For example: If a disk is RAW, converting it to QCOW will result in a larger disk. In order to reduce the size, it is possible to convert the disk again to QCOW and keep the same allocation policy.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | The description of the disk. | |
|
| In | Indicates which inner links should be followed. |
6.56.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.56.2. copy POST Copy linkLink copied to clipboard!
This operation copies a disk to the specified storage domain.
For example, a disk can be copied using the following request:
POST /ovirt-engine/api/disks/123/copy
POST /ovirt-engine/api/disks/123/copy
With a request body like this:
If the disk profile or the quota currently used by the disk are not defined for the new storage domain, they can be explicitly specified. If they are not specified, the first available disk profile and the default quota are used.
For example, to specify disk profile 987 and quota 753, send a request body like this:
<action> <storage_domain id="456"/> <disk_profile id="987"/> <quota id="753"/> </action>
<action>
<storage_domain id="456"/>
<disk_profile id="987"/>
<quota id="753"/>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the copy should be performed asynchronously. | |
|
| In | ||
|
| In | Disk profile for the disk in the new storage domain. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Quota for the disk in the new storage domain. | |
|
| In | The storage domain where the new disk is created. |
6.56.2.1. disk_profile Copy linkLink copied to clipboard!
Disk profile for the disk in the new storage domain.
Disk profiles are defined for storage domains, so the old disk profile will not exist in the new storage domain. If this parameter is not used, the first disk profile from the new storage domain to which the user has permissions will be assigned to the disk.
6.56.2.2. quota Copy linkLink copied to clipboard!
Quota for the disk in the new storage domain.
This optional parameter can be used to specify new quota for the disk, because the current quota may not be defined for the new storage domain. If this parameter is not used and the old quota is not defined for the new storage domain, the default (unlimited) quota will be assigned to the disk.
6.56.2.3. storage_domain Copy linkLink copied to clipboard!
The storage domain where the new disk is created. This can be specified using the id or name attributes. For example, to copy a disk to the storage domain called mydata, send a request like this:
POST /ovirt-engine/api/storagedomains/123/disks/789
POST /ovirt-engine/api/storagedomains/123/disks/789
With a request body like this:
<action>
<storage_domain>
<name>mydata</name>
</storage_domain>
</action>
<action>
<storage_domain>
<name>mydata</name>
</storage_domain>
</action>
6.56.3. export POST Copy linkLink copied to clipboard!
Exports a disk to an export storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the export should be performed asynchronously. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | The export storage domain where the disk will be exported to. |
6.56.4. get GET Copy linkLink copied to clipboard!
Retrieves the description of the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the disk should be included in the response. | |
|
| Out | The description of the disk. | |
|
| In | Indicates which inner links should be followed. |
6.56.4.1. all_content Copy linkLink copied to clipboard!
Indicates if all of the attributes of the disk should be included in the response.
By default the following disk attributes are excluded:
-
vms
For example, to retrieve the complete representation of disk '123':
GET /ovirt-engine/api/disks/123?all_content=true
GET /ovirt-engine/api/disks/123?all_content=true
6.56.4.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.56.5. move POST Copy linkLink copied to clipboard!
Moves a disk to another storage domain.
For example, to move the disk with identifier 123 to a storage domain with identifier 456 send the following request:
POST /ovirt-engine/api/disks/123/move
POST /ovirt-engine/api/disks/123/move
With the following request body:
<action> <storage_domain id="456"/> </action>
<action>
<storage_domain id="456"/>
</action>
If the disk profile or the quota used currently by the disk aren’t defined for the new storage domain, then they can be explicitly specified. If they aren’t then the first available disk profile and the default quota are used.
For example, to explicitly use disk profile 987 and quota 753 send a request body like this:
<action> <storage_domain id="456"/> <disk_profile id="987"/> <quota id="753"/> </action>
<action>
<storage_domain id="456"/>
<disk_profile id="987"/>
<quota id="753"/>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the move should be performed asynchronously. | |
|
| In | Disk profile for the disk in the new storage domain. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Quota for the disk in the new storage domain. | |
|
| In | The storage domain where the disk will be moved to. |
6.56.5.1. disk_profile Copy linkLink copied to clipboard!
Disk profile for the disk in the new storage domain.
Disk profiles are defined for storage domains, so the old disk profile will not exist in the new storage domain. If this parameter is not used, the first disk profile from the new storage domain to which the user has permissions will be assigned to the disk.
6.56.5.2. quota Copy linkLink copied to clipboard!
Quota for the disk in the new storage domain.
This optional parameter can be used to specify new quota for the disk, because the current quota may not be defined for the new storage domain. If this parameter is not used and the old quota is not defined for the new storage domain, the default (unlimited) quota will be assigned to the disk.
6.56.6. reduce POST Copy linkLink copied to clipboard!
Reduces the size of the disk image.
Invokes reduce on the logical volume (i.e. this is only applicable for block storage domains). This is applicable for floating disks and disks attached to non-running virtual machines. There is no need to specify the size as the optimal size is calculated automatically.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.56.7. refreshlun POST Copy linkLink copied to clipboard!
Refreshes a direct LUN disk with up-to-date information from the storage.
Refreshing a direct LUN disk is useful when:
- The LUN was added using the API without the host parameter, and therefore does not contain any information from the storage (see DisksService::add).
- New information about the LUN is available on the storage and you want to update the LUN with it.
To refresh direct LUN disk 123 using host 456, send the following request:
POST /ovirt-engine/api/disks/123/refreshlun
POST /ovirt-engine/api/disks/123/refreshlun
With the following request body:
<action> <host id='456'/> </action>
<action>
<host id='456'/>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | The host that will be used to refresh the direct LUN disk. |
6.56.8. remove DELETE Copy linkLink copied to clipboard!
Removes a disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.56.9. sparsify POST Copy linkLink copied to clipboard!
Sparsify the disk.
Sparsification frees space in the disk image that is not used by its filesystem. As a result, the image will occupy less space on the storage.
Currently sparsification works only on disks without snapshots. Disks having derived disks are also not allowed.
6.56.10. update PUT Copy linkLink copied to clipboard!
Updates the parameters of the specified disk.
This operation allows updating the following floating disk properties:
-
For Image disks:
provisioned_size,alias,description,wipe_after_delete,shareable,backupanddisk_profile. -
For LUN disks:
alias,descriptionandshareable. - Cinder integration has been replaced by Managed Block Storage.
-
For Managed Block disks:
provisioned_size,aliasanddescription. -
For VM attached disks, the
qcow_versioncan also be updated.
For example, a disk’s update can be done by using the following request:
PUT /ovirt-engine/api/disks/123
PUT /ovirt-engine/api/disks/123
With a request body like this:
<disk> <qcow_version>qcow2_v3</qcow_version> <alias>new-alias</alias> <description>new-desc</description> </disk>
<disk>
<qcow_version>qcow2_v3</qcow_version>
<alias>new-alias</alias>
<description>new-desc</description>
</disk>
Since the backend operation is asynchronous, the disk element that is returned to the user might not be synced with the changed properties.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The update to apply to the disk. |
6.57. DiskAttachment Copy linkLink copied to clipboard!
This service manages the attachment of a disk to a virtual machine.
| Name | Summary |
|---|---|
|
| Returns the details of the attachment, including the bootable flag and link to the disk. |
|
| Removes the disk attachment. |
|
| Update the disk attachment and the disk properties within it. |
6.57.1. get GET Copy linkLink copied to clipboard!
Returns the details of the attachment, including the bootable flag and link to the disk.
An example of getting a disk attachment:
GET /ovirt-engine/api/vms/123/diskattachments/456
GET /ovirt-engine/api/vms/123/diskattachments/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.57.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.57.2. remove DELETE Copy linkLink copied to clipboard!
Removes the disk attachment.
This will only detach the disk from the virtual machine, but won’t remove it from the system, unless the detach_only parameter is false.
An example of removing a disk attachment:
DELETE /ovirt-engine/api/vms/123/diskattachments/456?detach_only=true
DELETE /ovirt-engine/api/vms/123/diskattachments/456?detach_only=true
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the disk should only be detached from the virtual machine, but not removed from the system. |
6.57.2.1. detach_only Copy linkLink copied to clipboard!
Indicates if the disk should only be detached from the virtual machine, but not removed from the system. The default value is true, which won’t remove the disk from the system.
6.57.3. update PUT Copy linkLink copied to clipboard!
Update the disk attachment and the disk properties within it.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.58. DiskAttachments Copy linkLink copied to clipboard!
This service manages the set of disks attached to a virtual machine. Each attached disk is represented by a DiskAttachment, containing the bootable flag, the disk interface and the reference to the disk.
| Name | Summary |
|---|---|
|
| Adds a new disk attachment to the virtual machine. |
|
| List the disk that are attached to the virtual machine. |
6.58.1. add POST Copy linkLink copied to clipboard!
Adds a new disk attachment to the virtual machine. The attachment parameter can contain just a reference, if the disk already exists:
Or it can contain the complete representation of the disk, if the disk doesn’t exist yet:
In this case the disk will be created and then attached to the virtual machine.
In both cases, use the following URL for a virtual machine with an id 345:
POST /ovirt-engine/api/vms/345/diskattachments
POST /ovirt-engine/api/vms/345/diskattachments
The server accepts requests that do not contain the active attribute, but the effect is undefined. In some cases the disk will be automatically activated and in other cases it won’t. To avoid issues it is strongly recommended to always include the active attribute with the desired value.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The disk attachment to add to the virtual machine. |
6.58.2. list GET Copy linkLink copied to clipboard!
List the disk that are attached to the virtual machine.
The order of the returned list of disks attachments isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A list of disk attachments that are attached to the virtual machine. | |
|
| In | Indicates which inner links should be followed. |
6.58.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.59. DiskProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the specified disk profile in the system. |
6.59.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.59.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.59.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.59.3. update PUT Copy linkLink copied to clipboard!
Update the specified disk profile in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.60. DiskProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new disk profile to the system. |
|
| Returns the list of disk profiles of the system. |
6.60.1. add POST Copy linkLink copied to clipboard!
Add a new disk profile to the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.60.2. list GET Copy linkLink copied to clipboard!
Returns the list of disk profiles of the system.
The order of the returned list of disk profiles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.60.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.60.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.61. DiskSnapshot Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.61.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.61.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.61.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.62. DiskSnapshots Copy linkLink copied to clipboard!
Manages the collection of disk snapshots available in an storage domain.
| Name | Summary |
|---|---|
|
| Returns the list of disk snapshots of the storage domain. |
6.62.1. list GET Copy linkLink copied to clipboard!
Returns the list of disk snapshots of the storage domain.
The order of the returned list of disk snapshots isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | If true return also active snapshots. | |
|
| In | If true return also template snapshots. | |
|
| In | Sets the maximum number of snapshots to return. | |
|
| Out |
6.62.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.62.1.2. include_active Copy linkLink copied to clipboard!
If true return also active snapshots. If not specified active snapshots are not returned.
6.62.1.3. include_template Copy linkLink copied to clipboard!
If true return also template snapshots. If not specified template snapshots are not returned.
6.62.1.4. max Copy linkLink copied to clipboard!
Sets the maximum number of snapshots to return. If not specified all the snapshots are returned.
6.63. Disks Copy linkLink copied to clipboard!
Manages the collection of disks available in the system.
| Name | Summary |
|---|---|
|
| Adds a new floating disk. |
|
| Get list of disks. |
6.63.1. add POST Copy linkLink copied to clipboard!
Adds a new floating disk.
There are three types of disks that can be added - disk image, direct LUN and Managed Block disk. Cinder integration has been replaced by Managed Block Storage.
Adding a new image disk:
When creating a new floating image Disk, the API requires the storage_domain, provisioned_size and format attributes.
Note that block storage domains (i.e. storage domains with the storage type of iSCSI or FCP) do not support the combination of the raw format with sparse=true, so sparse=false must be stated explicitly.
To create a new floating image disk with specified provisioned_size, format and name on a storage domain with an id 123 and enabled for incremental backup, send a request as follows:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disks
With a request body as follows:
Adding a new direct LUN disk:
When adding a new floating direct LUN via the API, there are two flavors that can be used:
-
With a
hostelement - in this case, the host is used for sanity checks (e.g., that the LUN is visible) and to retrieve basic information about the LUN (e.g., size and serial). -
Without a
hostelement - in this case, the operation is a database-only operation, and the storage is never accessed.
To create a new floating direct LUN disk with a host element with an id 123, specified alias, type and logical_unit with an id 456 (that has the attributes address, port and target), send a request as follows:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disks
With a request body as follows:
To create a new floating direct LUN disk without using a host, remove the host element.
Adding a new Cinder disk:
Cinder integration has been replaced by Managed Block Storage.
Adding a floating disks in order to upload disk snapshots:
Since version 4.2 of the engine it is possible to upload disks with snapshots. This request should be used to create the base image of the images chain (The consecutive disk snapshots (images), should be created using disk-attachments element when creating a snapshot).
The disk has to be created with the same disk identifier and image identifier of the uploaded image. I.e. the identifiers should be saved as part of the backup process. The image identifier can be also fetched using the qemu-img info command. For example, if the disk image is stored into a file named b7a4c6c5-443b-47c5-967f-6abc79675e8b/myimage.img:
To create a disk with with the disk identifier and image identifier obtained with the qemu-img info command shown above, send a request like this:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disks
With a request body as follows:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The disk. |
6.63.2. list GET Copy linkLink copied to clipboard!
Get list of disks.
GET /ovirt-engine/api/disks
GET /ovirt-engine/api/disks
You will get a XML response which will look like this one:
The order of the returned list of disks is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | List of retrieved disks. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. | |
|
| In | A query string used to restrict the returned disks. |
6.63.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.63.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.63.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.64. Domain Copy linkLink copied to clipboard!
A service to view details of an authentication domain in the system.
| Name | Summary |
|---|---|
|
| Gets the authentication domain information. |
6.64.1. get GET Copy linkLink copied to clipboard!
Gets the authentication domain information.
Usage:
GET /ovirt-engine/api/domains/5678
GET /ovirt-engine/api/domains/5678
Will return the domain information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The authentication domain. | |
|
| In | Indicates which inner links should be followed. |
6.64.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.65. DomainGroup Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.65.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.65.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.66. DomainGroups Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of groups. |
6.66.1. list GET Copy linkLink copied to clipboard!
Returns the list of groups.
The order of the returned list of groups isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of groups to return. | |
|
| In | A query string used to restrict the returned groups. |
6.66.1.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.66.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.66.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of groups to return. If not specified all the groups are returned.
6.67. DomainUser Copy linkLink copied to clipboard!
A service to view a domain user in the system.
| Name | Summary |
|---|---|
|
| Gets the domain user information. |
6.67.1. get GET Copy linkLink copied to clipboard!
Gets the domain user information.
Usage:
GET /ovirt-engine/api/domains/5678/users/1234
GET /ovirt-engine/api/domains/5678/users/1234
Will return the domain user information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The domain user. |
6.67.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.68. DomainUserGroups Copy linkLink copied to clipboard!
A service that shows a user’s group membership in the AAA extension.
| Name | Summary |
|---|---|
|
| Returns the list of groups that the user is a member of. |
6.68.1. list GET Copy linkLink copied to clipboard!
Returns the list of groups that the user is a member of.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of groups that the user is a member of. |
6.68.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.69. DomainUsers Copy linkLink copied to clipboard!
A service to list all domain users in the system.
| Name | Summary |
|---|---|
|
| List all the users in the domain. |
6.69.1. list GET Copy linkLink copied to clipboard!
List all the users in the domain.
Usage:
GET /ovirt-engine/api/domains/5678/users
GET /ovirt-engine/api/domains/5678/users
Will return the list of users in the domain:
The order of the returned list of users isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of users to return. | |
|
| In | A query string used to restrict the returned users. | |
|
| Out | The list of users in the domain. |
6.69.1.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.69.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.69.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of users to return. If not specified all the users are returned.
6.70. Domains Copy linkLink copied to clipboard!
A service to list all authentication domains in the system.
| Name | Summary |
|---|---|
|
| List all the authentication domains in the system. |
6.70.1. list GET Copy linkLink copied to clipboard!
List all the authentication domains in the system.
Usage:
GET /ovirt-engine/api/domains
GET /ovirt-engine/api/domains
Will return the list of domains:
The order of the returned list of domains isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of domains. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of domains to return. |
6.70.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.70.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of domains to return. If not specified all the domains are returned.
6.71. EngineKatelloErrata Copy linkLink copied to clipboard!
A service to manage Katello errata assigned to the engine. The information is retrieved from Katello.
| Name | Summary |
|---|---|
|
| Retrieves the representation of the Katello errata. |
6.71.1. list GET Copy linkLink copied to clipboard!
Retrieves the representation of the Katello errata.
GET /ovirt-engine/api/katelloerrata
GET /ovirt-engine/api/katelloerrata
You will receive response in XML like this one:
The order of the returned list of erratum isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A representation of Katello errata. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of errata to return. |
6.71.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.71.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of errata to return. If not specified all the errata are returned.
6.72. Event Copy linkLink copied to clipboard!
A service to manage an event in the system.
| Name | Summary |
|---|---|
|
| Get an event. |
|
| Removes an event from internal audit log. |
6.72.1. get GET Copy linkLink copied to clipboard!
Get an event.
An example of getting an event:
GET /ovirt-engine/api/events/123
GET /ovirt-engine/api/events/123
Note that the number of fields changes according to the information that resides on the event. For example, for storage domain related events you will get the storage domain reference, as well as the reference for the data center this storage domain resides in.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.72.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.72.2. remove DELETE Copy linkLink copied to clipboard!
Removes an event from internal audit log.
An event can be removed by sending following request
DELETE /ovirt-engine/api/events/123
DELETE /ovirt-engine/api/events/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.73. EventSubscription Copy linkLink copied to clipboard!
A service to manage a specific event-subscription in the system.
| Name | Summary |
|---|---|
|
| Gets the information about the event-subscription. |
|
| Removes the event-subscription from the system. |
6.73.1. get GET Copy linkLink copied to clipboard!
Gets the information about the event-subscription.
For example to retrieve the information about the subscription of user '123' to the event 'vm_console_detected':
GET /ovirt-engine/api/users/123/vm_console_detected
GET /ovirt-engine/api/users/123/vm_console_detected
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The event-subscription. |
6.73.2. remove DELETE Copy linkLink copied to clipboard!
Removes the event-subscription from the system.
For example to remove user 123’s subscription to vm_console_detected event:
DELETE /ovirt-engine/api/users/123/vm_console_detected
DELETE /ovirt-engine/api/users/123/vm_console_detected
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.74. EventSubscriptions Copy linkLink copied to clipboard!
Represents a service to manage collection of event-subscription of a user.
| Name | Summary |
|---|---|
|
| Add a new event-subscription to the system. |
|
| List the event-subscriptions for the provided user. |
6.74.1. add POST Copy linkLink copied to clipboard!
Add a new event-subscription to the system.
An event-subscription is always added in the context of a user. For example, to add new event-subscription for host_high_cpu_use for user 123, and have the notification sent to the e-mail address: a@b.com, send a request like this:
POST /ovirt-engine/api/users/123/eventsubscriptions
POST /ovirt-engine/api/users/123/eventsubscriptions
With a request body like this:
<event_subscription>
<event>host_high_cpu_use</event>
<address>a@b.com</address>
</event_subscription>
<event_subscription>
<event>host_high_cpu_use</event>
<address>a@b.com</address>
</event_subscription>
The event name will become the ID of the new event-subscription entity: GET …/api/users/123/eventsubscriptions/host_high_cpu_use
Note that no user id is provided in the request body. This is because the user-id (in this case 123) is already known to the API from the context. Note also that event-subscription entity contains notification-method field, but it is not provided either in the request body. This is because currently it’s always set to SMTP as SNMP notifications are still unsupported by the API layer.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The added event-subscription. |
6.74.2. list GET Copy linkLink copied to clipboard!
List the event-subscriptions for the provided user.
For example to list event-subscriptions for user 123:
GET /ovirt-engine/api/users/123/event-subscriptions
GET /ovirt-engine/api/users/123/event-subscriptions
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | List of the event-subscriptions for the specified user | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of event-subscriptions to return. |
6.74.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.74.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of event-subscriptions to return. If not specified all the event-subscriptions are returned.
6.75. Events Copy linkLink copied to clipboard!
A service to manage events in the system.
| Name | Summary |
|---|---|
|
| Adds an external event to the internal audit log. |
|
| Get list of events. |
|
|
6.75.1. add POST Copy linkLink copied to clipboard!
Adds an external event to the internal audit log.
This is intended for integration with external systems that detect or produce events relevant for the administrator of the system. For example, an external monitoring tool may be able to detect that a file system is full inside the guest operating system of a virtual machine. This event can be added to the internal audit log sending a request like this:
Events can also be linked to specific objects. For example, the above event could be linked to the specific virtual machine where it happened, using the vm link:
When using links, like the vm in the previous example, only the id attribute is accepted. The name attribute, if provided, is simply ignored.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.75.2. list GET Copy linkLink copied to clipboard!
Get list of events.
GET /ovirt-engine/api/events
GET /ovirt-engine/api/events
To the above request we get following response:
The following events occur:
- id="1" - The API logs in the admin user account.
- id="2" - The API logs out of the admin user account.
The order of the returned list of events is always garanteed. If the sortby clause is included in the search parameter, then the events will be ordered according to that clause. If the sortby clause isn’t included, then the events will be sorted by the numeric value of the id attribute, starting with the highest value. This, combined with the max parameter, simplifies obtaining the most recent event:
GET /ovirt-engine/api/events?max=1
GET /ovirt-engine/api/events?max=1
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Indicates the event index after which events should be returned. | |
|
| In | Sets the maximum number of events to return. | |
|
| In | The events service provides search queries similar to other resource services. |
6.75.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.75.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.75.2.3. from Copy linkLink copied to clipboard!
Indicates the event index after which events should be returned. The indexes of events are strictly increasing, so when this parameter is used only the events with greater indexes will be returned. For example, the following request will return only the events with indexes greater than 123:
GET /ovirt-engine/api/events?from=123
GET /ovirt-engine/api/events?from=123
This parameter is optional, and if not specified then the first event returned will be most recently generated.
6.75.2.4. max Copy linkLink copied to clipboard!
Sets the maximum number of events to return. If not specified all the events are returned.
6.75.2.5. search Copy linkLink copied to clipboard!
The events service provides search queries similar to other resource services.
We can search by providing specific severity.
GET /ovirt-engine/api/events?search=severity%3Dnormal
GET /ovirt-engine/api/events?search=severity%3Dnormal
To the above request we get a list of events which severity is equal to normal:
A virtualization environment generates a large amount of events after a period of time. However, the API only displays a default number of events for one search query. To display more than the default, the API separates results into pages with the page command in a search query. The following search query tells the API to paginate results using a page value in combination with the sortby clause:
sortby time asc page 1
sortby time asc page 1
Below example paginates event resources. The URL-encoded request is:
GET /ovirt-engine/api/events?search=sortby%20time%20asc%20page%201
GET /ovirt-engine/api/events?search=sortby%20time%20asc%20page%201
Increase the page value to view the next page of results.
GET /ovirt-engine/api/events?search=sortby%20time%20asc%20page%202
GET /ovirt-engine/api/events?search=sortby%20time%20asc%20page%202
6.75.3. undelete POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the un-delete should be performed asynchronously. |
6.76. ExternalComputeResource Copy linkLink copied to clipboard!
Manages a single external compute resource.
Compute resource is a term of host external provider. The external provider also needs to know to where the provisioned host needs to register. The login details of the engine are saved as a compute resource in the external provider side.
| Name | Summary |
|---|---|
|
| Retrieves external compute resource details. |
6.76.1. get GET Copy linkLink copied to clipboard!
Retrieves external compute resource details.
For example, to get the details of compute resource 234 of provider 123, send a request like this:
GET /ovirt-engine/api/externalhostproviders/123/computeresources/234
GET /ovirt-engine/api/externalhostproviders/123/computeresources/234
It will return a response like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | External compute resource information |
6.76.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.77. ExternalComputeResources Copy linkLink copied to clipboard!
Manages a collection of external compute resources.
Compute resource is a term of host external provider. The external provider also needs to know to where the provisioned host needs to register. The login details of the engine is saved as a compute resource in the external provider side.
| Name | Summary |
|---|---|
|
| Retrieves a list of external compute resources. |
6.77.1. list GET Copy linkLink copied to clipboard!
Retrieves a list of external compute resources.
For example, to retrieve the compute resources of external host provider 123, send a request like this:
GET /ovirt-engine/api/externalhostproviders/123/computeresources
GET /ovirt-engine/api/externalhostproviders/123/computeresources
It will return a response like this:
The order of the returned list of compute resources isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of resources to return. | |
|
| Out | List of external computer resources. |
6.77.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.77.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of resources to return. If not specified all the resources are returned.
6.78. ExternalDiscoveredHost Copy linkLink copied to clipboard!
This service manages a single discovered host.
| Name | Summary |
|---|---|
|
| Get discovered host info. |
6.78.1. get GET Copy linkLink copied to clipboard!
Get discovered host info.
Retrieves information about an host that is managed in external provider management system, such as Foreman. The information includes hostname, address, subnet, base image and more.
For example, to get the details of host 234 from provider 123, send a request like this:
GET /ovirt-engine/api/externalhostproviders/123/discoveredhosts/234
GET /ovirt-engine/api/externalhostproviders/123/discoveredhosts/234
The result will be like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Host’s hardware and config information. |
6.78.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.79. ExternalDiscoveredHosts Copy linkLink copied to clipboard!
This service manages external discovered hosts.
| Name | Summary |
|---|---|
|
| Get list of discovered hosts' information. |
6.79.1. list GET Copy linkLink copied to clipboard!
Get list of discovered hosts' information.
Discovered hosts are fetched from third-party providers such as Foreman.
To list all discovered hosts for provider 123 send the following:
GET /ovirt-engine/api/externalhostproviders/123/discoveredhost
GET /ovirt-engine/api/externalhostproviders/123/discoveredhost
The order of the returned list of hosts isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | List of discovered hosts | |
|
| In | Sets the maximum number of hosts to return. |
6.79.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.79.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
6.80. ExternalHost Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.80.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.80.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.81. ExternalHostGroup Copy linkLink copied to clipboard!
This service manages a single host group information.
Host group is a term of host provider - the host group includes provision details that are applied to new discovered host. Information such as subnet, operating system, domain, etc.
| Name | Summary |
|---|---|
|
| Get host group information. |
6.81.1. get GET Copy linkLink copied to clipboard!
Get host group information.
For example, to get the details of hostgroup 234 of provider 123, send a request like this:
GET /ovirt-engine/api/externalhostproviders/123/hostgroups/234
GET /ovirt-engine/api/externalhostproviders/123/hostgroups/234
It will return a response like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Host group information. |
6.81.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.82. ExternalHostGroups Copy linkLink copied to clipboard!
This service manages hostgroups.
| Name | Summary |
|---|---|
|
| Get host groups list from external host provider. |
6.82.1. list GET Copy linkLink copied to clipboard!
Get host groups list from external host provider.
Host group is a term of host providers - the host group includes provision details. This API returns all possible hostgroups exposed by the external provider.
For example, to get the details of all host groups of provider 123, send a request like this:
GET /ovirt-engine/api/externalhostproviders/123/hostgroups
GET /ovirt-engine/api/externalhostproviders/123/hostgroups
The response will be like this:
The order of the returned list of host groups isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | List of all hostgroups available for external host provider | |
|
| In | Sets the maximum number of groups to return. |
6.82.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.82.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of groups to return. If not specified all the groups are returned.
6.83. ExternalHostProvider Copy linkLink copied to clipboard!
Represents an external host provider, such as Foreman or Satellite.
See Foreman documentation for details. See Satellite documentation for details.
| Name | Summary |
|---|---|
|
| Get external host provider information Host provider, Foreman or Satellite, can be set as an external provider in ovirt. |
|
| Import the SSL certificates of the external host provider. |
|
| |
|
| In order to test connectivity for external provider we need to run following request where 123 is an id of a provider. |
|
| Update the specified external host provider in the system. |
6.83.1. get GET Copy linkLink copied to clipboard!
Get external host provider information
Host provider, Foreman or Satellite, can be set as an external provider in ovirt. To see details about specific host providers attached to ovirt use this API.
For example, to get the details of host provider 123, send a request like this:
GET /ovirt-engine/api/externalhostproviders/123
GET /ovirt-engine/api/externalhostproviders/123
The response will be like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.83.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.83.2. importcertificates POST Copy linkLink copied to clipboard!
Import the SSL certificates of the external host provider.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.83.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.83.4. testconnectivity POST Copy linkLink copied to clipboard!
In order to test connectivity for external provider we need to run following request where 123 is an id of a provider.
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.83.5. update PUT Copy linkLink copied to clipboard!
Update the specified external host provider in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.84. ExternalHostProviders Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new external host provider to the system. |
|
| Returns the list of external host providers. |
6.84.1. add POST Copy linkLink copied to clipboard!
Add a new external host provider to the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.84.2. list GET Copy linkLink copied to clipboard!
Returns the list of external host providers.
The order of the returned list of host providers isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of providers to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned external host providers. |
6.84.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.84.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.85. ExternalHosts Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Return the list of external hosts. |
6.85.1. list GET Copy linkLink copied to clipboard!
Return the list of external hosts.
The order of the returned list of hosts isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. |
6.85.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.85.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
6.86. ExternalNetworkProviderConfiguration Copy linkLink copied to clipboard!
Describes how an external network provider is provisioned by the system on the host.
| Name | Summary |
|---|---|
|
| Returns the information about an external network provider on the host. |
6.86.1. get GET Copy linkLink copied to clipboard!
Returns the information about an external network provider on the host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.86.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.87. ExternalNetworkProviderConfigurations Copy linkLink copied to clipboard!
A service to list all external network providers provisioned by the system on the host.
| Name | Summary |
|---|---|
|
| Returns the list of all external network providers on the host. |
6.87.1. list GET Copy linkLink copied to clipboard!
Returns the list of all external network providers on the host.
The order of the returned list of networks is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.87.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.88. ExternalProvider Copy linkLink copied to clipboard!
Provides capability to manage external providers.
| Name | Summary |
|---|---|
|
| Import the SSL certificates of the external host provider. |
|
| In order to test connectivity for external provider we need to run following request where 123 is an id of a provider. |
6.88.1. importcertificates POST Copy linkLink copied to clipboard!
Import the SSL certificates of the external host provider.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.88.2. testconnectivity POST Copy linkLink copied to clipboard!
In order to test connectivity for external provider we need to run following request where 123 is an id of a provider.
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.89. ExternalProviderCertificate Copy linkLink copied to clipboard!
A service to view specific certificate for external provider.
| Name | Summary |
|---|---|
|
| Get specific certificate. |
6.89.1. get GET Copy linkLink copied to clipboard!
Get specific certificate.
GET /ovirt-engine/api/externalhostproviders/123/certificate/0
GET /ovirt-engine/api/externalhostproviders/123/certificate/0
And here is sample response:
<certificate id="0"> <organization>provider.example.com</organization> <subject>CN=provider.example.com</subject> <content>...</content> </certificate>
<certificate id="0">
<organization>provider.example.com</organization>
<subject>CN=provider.example.com</subject>
<content>...</content>
</certificate>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The details of the certificate. | |
|
| In | Indicates which inner links should be followed. |
6.89.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.90. ExternalProviderCertificates Copy linkLink copied to clipboard!
A service to view certificates for external provider.
| Name | Summary |
|---|---|
|
| Returns the chain of certificates presented by the external provider. |
6.90.1. list GET Copy linkLink copied to clipboard!
Returns the chain of certificates presented by the external provider.
GET /ovirt-engine/api/externalhostproviders/123/certificates
GET /ovirt-engine/api/externalhostproviders/123/certificates
And here is sample response:
<certificates> <certificate id="789">...</certificate> ... </certificates>
<certificates>
<certificate id="789">...</certificate>
...
</certificates>
The order of the returned certificates is always guaranteed to be the sign order: the first is the certificate of the server itself, the second the certificate of the CA that signs the first, so on.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | List containing certificate details. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of certificates to return. |
6.90.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.90.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of certificates to return. If not specified all the certificates are returned.
6.91. ExternalTemplateImports Copy linkLink copied to clipboard!
Provides capability to import external templates. Currently supports OVA only.
| Name | Summary |
|---|---|
|
| This operation is used to import a template from external hypervisor. |
6.91.1. add POST Copy linkLink copied to clipboard!
This operation is used to import a template from external hypervisor.
For example import of a template OVA can be facilitated using the following request:
POST /externaltemplateimports
POST /externaltemplateimports
With request body of type ExternalTemplateImport, for example:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.92. ExternalVmImports Copy linkLink copied to clipboard!
Provides capability to import external virtual machines.
| Name | Summary |
|---|---|
|
| This operation is used to import a virtual machine from external hypervisor, such as KVM, XEN or VMware. |
6.92.1. add POST Copy linkLink copied to clipboard!
This operation is used to import a virtual machine from external hypervisor, such as KVM, XEN or VMware.
For example import of a virtual machine from VMware can be facilitated using the following request:
POST /externalvmimports
POST /externalvmimports
With request body of type ExternalVmImport, for example:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.93. FenceAgent Copy linkLink copied to clipboard!
A service to manage fence agent for a specific host.
| Name | Summary |
|---|---|
|
| Gets details of this fence agent. |
|
| Removes a fence agent for a specific host. |
|
| Update a fencing-agent. |
6.93.1. get GET Copy linkLink copied to clipboard!
Gets details of this fence agent.
GET /ovirt-engine/api/hosts/123/fenceagents/0
GET /ovirt-engine/api/hosts/123/fenceagents/0
And here is sample response:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Fence agent details. | |
|
| In | Indicates which inner links should be followed. |
6.93.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.93.2. remove DELETE Copy linkLink copied to clipboard!
Removes a fence agent for a specific host.
DELETE /ovirt-engine/api/hosts/123/fenceagents/0
DELETE /ovirt-engine/api/hosts/123/fenceagents/0
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.93.3. update PUT Copy linkLink copied to clipboard!
Update a fencing-agent.
6.94. FenceAgents Copy linkLink copied to clipboard!
A service to manage fence agents for a specific host.
| Name | Summary |
|---|---|
|
| Add a new fencing-agent to the host. |
|
| Returns the list of fencing agents configured for the host. |
6.94.1. add POST Copy linkLink copied to clipboard!
Add a new fencing-agent to the host.
apc, bladecenter, wti fencing agent/s sample request:
apc_snmp, hpblade, ilo, ilo2, ilo_ssh, redfish, rsa fencing agent/s sample request:
cisco_ucs, drac5, eps fencing agent/s sample request:
drac7, ilo3, ilo4, ipmilan, rsb fencing agent/s sample request:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.94.2. list GET Copy linkLink copied to clipboard!
Returns the list of fencing agents configured for the host.
GET /ovirt-engine/api/hosts/123/fenceagents
GET /ovirt-engine/api/hosts/123/fenceagents
And here is sample response:
The order of the returned list of fencing agents isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | List of fence agent details. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of agents to return. |
6.94.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.94.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of agents to return. If not specified all the agents are returned.
6.95. File Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.95.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.95.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.96. Files Copy linkLink copied to clipboard!
Provides a way for clients to list available files.
This service is specifically targeted to ISO storage domains, which contain ISO images and virtual floppy disks (VFDs) that an administrator uploads.
The addition of a CD-ROM device to a virtual machine requires an ISO image from the files of an ISO storage domain.
| Name | Summary |
|---|---|
|
| Returns the list of ISO images and virtual floppy disks available in the storage domain. |
6.96.1. list GET Copy linkLink copied to clipboard!
Returns the list of ISO images and virtual floppy disks available in the storage domain. The order of the returned list is not guaranteed.
If the refresh parameter is false, the returned list may not reflect recent changes to the storage domain; for example, it may not contain a new ISO file that was recently added. This is because the server caches the list of files to improve performance. To get the very latest results, set the refresh parameter to true.
The default value of the refresh parameter is true, but it can be changed using the configuration value ForceRefreshDomainFilesByDefault:
engine-config -s ForceRefreshDomainFilesByDefault=false
# engine-config -s ForceRefreshDomainFilesByDefault=false
Setting the value of the refresh parameter to true has an impact on the performance of the server. Use it only if necessary.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of files to return. | |
|
| In | Indicates whether the list of files should be refreshed from the storage domain, rather than showing cached results that are updated at certain intervals. | |
|
| In | A query string used to restrict the returned files. |
6.96.1.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should take case into account. The default value is true.
6.96.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.96.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of files to return. If not specified, all the files are returned.
6.97. Filter Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.97.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.97.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.97.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.98. Filters Copy linkLink copied to clipboard!
Manages the filters used by an scheduling policy.
| Name | Summary |
|---|---|
|
| Add a filter to a specified user defined scheduling policy. |
|
| Returns the list of filters used by the scheduling policy. |
6.98.1. add POST Copy linkLink copied to clipboard!
Add a filter to a specified user defined scheduling policy.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.98.2. list GET Copy linkLink copied to clipboard!
Returns the list of filters used by the scheduling policy.
The order of the returned list of filters isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of filters to return. |
6.98.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.98.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of filters to return. If not specified all the filters are returned.
6.99. Follow Copy linkLink copied to clipboard!
6.100. GlusterBrick Copy linkLink copied to clipboard!
This service manages a single gluster brick.
| Name | Summary |
|---|---|
|
| Get details of a brick. |
|
| Removes a brick. |
|
| Replaces this brick with a new one. |
6.100.1. get GET Copy linkLink copied to clipboard!
Get details of a brick.
Retrieves status details of brick from underlying gluster volume with header All-Content set to true. This is the equivalent of running gluster volume status <volumename> <brickname> detail.
For example, to get the details of brick 234 of gluster volume 123, send a request like this:
GET /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/234
GET /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/234
Which will return a response body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.100.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.100.2. remove DELETE Copy linkLink copied to clipboard!
Removes a brick.
Removes a brick from the underlying gluster volume and deletes entries from database. This can be used only when removing a single brick without data migration. To remove multiple bricks and with data migration, use migrate instead.
For example, to delete brick 234 from gluster volume 123, send a request like this:
DELETE /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/234
DELETE /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/234
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.100.3. replace POST Copy linkLink copied to clipboard!
Replaces this brick with a new one.
This operation has been deprecated since version 3.5 of the engine and will be removed in the future. Use add brick(s) and migrate brick(s) instead.
6.101. GlusterBricks Copy linkLink copied to clipboard!
This service manages the gluster bricks in a gluster volume
| Name | Summary |
|---|---|
|
| Activate the bricks post data migration of remove brick operation. |
|
| Adds a list of bricks to gluster volume. |
|
| Lists the bricks of a gluster volume. |
|
| Start migration of data prior to removing bricks. |
|
| Removes bricks from gluster volume. |
|
| Stops migration of data from bricks for a remove brick operation. |
6.101.1. activate POST Copy linkLink copied to clipboard!
Activate the bricks post data migration of remove brick operation.
Used to activate brick(s) once the data migration from bricks is complete but user no longer wishes to remove bricks. The bricks that were previously marked for removal will now be used as normal bricks.
For example, to retain the bricks that on glustervolume 123 from which data was migrated, send a request like this:
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/activate
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/activate
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. | |
|
| In | The list of bricks that need to be re-activated. |
6.101.2. add POST Copy linkLink copied to clipboard!
Adds a list of bricks to gluster volume.
Used to expand a gluster volume by adding bricks. For replicated volume types, the parameter replica_count needs to be passed. In case the replica count is being increased, then the number of bricks needs to be equivalent to the number of replica sets.
For example, to add bricks to gluster volume 123, send a request like this:
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The list of bricks to be added to the volume | |
|
| In | Replica count of volume post add operation. | |
|
| In | Stripe count of volume post add operation. |
6.101.3. list GET Copy linkLink copied to clipboard!
Lists the bricks of a gluster volume.
For example, to list bricks of gluster volume 123, send a request like this:
GET /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks
GET /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks
Provides an output as below:
The order of the returned list is based on the brick order provided at gluster volume creation.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of bricks to return. |
6.101.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.101.3.2. max Copy linkLink copied to clipboard!
Sets the maximum number of bricks to return. If not specified all the bricks are returned.
6.101.4. migrate POST Copy linkLink copied to clipboard!
Start migration of data prior to removing bricks.
Removing bricks is a two-step process, where the data on bricks to be removed, is first migrated to remaining bricks. Once migration is completed the removal of bricks is confirmed via the API remove. If at any point, the action needs to be cancelled stopmigrate has to be called.
For instance, to delete a brick from a gluster volume with id 123, send a request:
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/migrate
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/migrate
With a request body like this:
The migration process can be tracked from the job id returned from the API using job and steps in job using step
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should be performed asynchronously. | |
|
| In | List of bricks for which data migration needs to be started. |
6.101.5. remove DELETE Copy linkLink copied to clipboard!
Removes bricks from gluster volume.
The recommended way to remove bricks without data loss is to first migrate the data using stopmigrate and then removing them. If migrate was not called on bricks prior to remove, the bricks are removed without data migration which may lead to data loss.
For example, to delete the bricks from gluster volume 123, send a request like this:
DELETE /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks
DELETE /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks
With a request body like this:
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | The list of bricks to be removed | |
|
| In | Replica count of volume post add operation. |
6.101.6. stopmigrate POST Copy linkLink copied to clipboard!
Stops migration of data from bricks for a remove brick operation.
To cancel data migration that was started as part of the 2-step remove brick process in case the user wishes to continue using the bricks. The bricks that were marked for removal will function as normal bricks post this operation.
For example, to stop migration of data from the bricks of gluster volume 123, send a request like this:
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/stopmigrate
POST /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/stopmigrate
With a request body like this:
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | List of bricks for which data migration needs to be stopped. |
6.101.6.1. bricks Copy linkLink copied to clipboard!
List of bricks for which data migration needs to be stopped. This list should match the arguments passed to migrate.
6.102. GlusterHook Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. |
|
| Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. |
|
| |
|
| Removes the this Gluster hook from all servers in cluster and deletes it from the database. |
|
| Resolves missing hook conflict depending on the resolution type. |
6.102.1. disable POST Copy linkLink copied to clipboard!
Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. This updates the hook status to DISABLED in database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.102.2. enable POST Copy linkLink copied to clipboard!
Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. This updates the hook status to DISABLED in database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.102.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.102.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.102.4. remove DELETE Copy linkLink copied to clipboard!
Removes the this Gluster hook from all servers in cluster and deletes it from the database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.102.5. resolve POST Copy linkLink copied to clipboard!
Resolves missing hook conflict depending on the resolution type.
For ADD resolves by copying hook stored in engine database to all servers where the hook is missing. The engine maintains a list of all servers where hook is missing.
For COPY resolves conflict in hook content by copying hook stored in engine database to all servers where the hook is missing. The engine maintains a list of all servers where the content is conflicting. If a host id is passed as parameter, the hook content from the server is used as the master to copy to other servers in cluster.
6.103. GlusterHooks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of hooks. |
6.103.1. list GET Copy linkLink copied to clipboard!
Returns the list of hooks.
The order of the returned list of hooks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of hooks to return. |
6.103.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.103.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of hooks to return. If not specified all the hooks are returned.
6.104. GlusterVolume Copy linkLink copied to clipboard!
This service manages a single gluster volume.
| Name | Summary |
|---|---|
|
| Get the gluster volume details. |
|
| Get gluster volume profile statistics. |
|
| Rebalance the gluster volume. |
|
| Removes the gluster volume. |
|
| Resets all the options set in the gluster volume. |
|
| Resets a particular option in the gluster volume. |
|
| Sets a particular option in the gluster volume. |
|
| Starts the gluster volume. |
|
| Start profiling the gluster volume. |
|
| Stops the gluster volume. |
|
| Stop profiling the gluster volume. |
|
| Stop rebalancing the gluster volume. |
6.104.1. get GET Copy linkLink copied to clipboard!
Get the gluster volume details.
For example, to get details of a gluster volume with identifier 123 in cluster 456, send a request like this:
GET /ovirt-engine/api/clusters/456/glustervolumes/123
GET /ovirt-engine/api/clusters/456/glustervolumes/123
This GET request will return the following output:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Representation of the gluster volume. |
6.104.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.104.2. getprofilestatistics POST Copy linkLink copied to clipboard!
Get gluster volume profile statistics.
For example, to get profile statistics for a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/getprofilestatistics
POST /ovirt-engine/api/clusters/456/glustervolumes/123/getprofilestatistics
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Gluster volume profiling information returned from the action. |
6.104.3. rebalance POST Copy linkLink copied to clipboard!
Rebalance the gluster volume.
Rebalancing a gluster volume helps to distribute the data evenly across all the bricks. After expanding or shrinking a gluster volume (without migrating data), we need to rebalance the data among the bricks. In a non-replicated volume, all bricks should be online to perform the rebalance operation. In a replicated volume, at least one of the bricks in the replica should be online.
For example, to rebalance a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/rebalance
POST /ovirt-engine/api/clusters/456/glustervolumes/123/rebalance
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the rebalance should be performed asynchronously. | |
|
| In | If set to true, rebalance will only fix the layout so that new data added to the volume is distributed across all the hosts. | |
|
| In | Indicates if the rebalance should be force started. |
6.104.3.1. fix_layout Copy linkLink copied to clipboard!
If set to true, rebalance will only fix the layout so that new data added to the volume is distributed across all the hosts. But it will not migrate/rebalance the existing data. Default is false.
6.104.3.2. force Copy linkLink copied to clipboard!
Indicates if the rebalance should be force started. The rebalance command can be executed with the force option even when the older clients are connected to the cluster. However, this could lead to a data loss situation. Default is false.
6.104.4. remove DELETE Copy linkLink copied to clipboard!
Removes the gluster volume.
For example, to remove a volume with identifier 123 in cluster 456, send a request like this:
DELETE /ovirt-engine/api/clusters/456/glustervolumes/123
DELETE /ovirt-engine/api/clusters/456/glustervolumes/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.104.5. resetalloptions POST Copy linkLink copied to clipboard!
Resets all the options set in the gluster volume.
For example, to reset all options in a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/resetalloptions
POST /ovirt-engine/api/clusters/456/glustervolumes/123/resetalloptions
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reset should be performed asynchronously. |
6.104.6. resetoption POST Copy linkLink copied to clipboard!
Resets a particular option in the gluster volume.
For example, to reset a particular option option1 in a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/resetoption
POST /ovirt-engine/api/clusters/456/glustervolumes/123/resetoption
With the following request body:
<action> <option name="option1"/> </action>
<action>
<option name="option1"/>
</action>
6.104.7. setoption POST Copy linkLink copied to clipboard!
Sets a particular option in the gluster volume.
For example, to set option1 with value value1 in a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/setoption
POST /ovirt-engine/api/clusters/456/glustervolumes/123/setoption
With the following request body:
<action> <option name="option1" value="value1"/> </action>
<action>
<option name="option1" value="value1"/>
</action>
6.104.8. start POST Copy linkLink copied to clipboard!
Starts the gluster volume.
A Gluster Volume should be started to read/write data. For example, to start a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/start
POST /ovirt-engine/api/clusters/456/glustervolumes/123/start
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Indicates if the volume should be force started. |
6.104.8.1. force Copy linkLink copied to clipboard!
Indicates if the volume should be force started. If a gluster volume is started already but few/all bricks are down then force start can be used to bring all the bricks up. Default is false.
6.104.9. startprofile POST Copy linkLink copied to clipboard!
Start profiling the gluster volume.
For example, to start profiling a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/startprofile
POST /ovirt-engine/api/clusters/456/glustervolumes/123/startprofile
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.104.10. stop POST Copy linkLink copied to clipboard!
Stops the gluster volume.
Stopping a volume will make its data inaccessible.
For example, to stop a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stop
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stop
6.104.11. stopprofile POST Copy linkLink copied to clipboard!
Stop profiling the gluster volume.
For example, to stop profiling a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stopprofile
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stopprofile
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.104.12. stoprebalance POST Copy linkLink copied to clipboard!
Stop rebalancing the gluster volume.
For example, to stop rebalancing a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stoprebalance
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stoprebalance
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.105. GlusterVolumes Copy linkLink copied to clipboard!
This service manages a collection of gluster volumes available in a cluster.
| Name | Summary |
|---|---|
|
| Creates a new gluster volume. |
|
| Lists all gluster volumes in the cluster. |
6.105.1. add POST Copy linkLink copied to clipboard!
Creates a new gluster volume.
The volume is created based on properties of the volume parameter. The properties name, volume_type and bricks are required.
For example, to add a volume with name myvolume to the cluster 123, send the following request:
POST /ovirt-engine/api/clusters/123/glustervolumes
POST /ovirt-engine/api/clusters/123/glustervolumes
With the following request body:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The gluster volume definition from which to create the volume is passed as input and the newly created volume is returned. |
6.105.2. list GET Copy linkLink copied to clipboard!
Lists all gluster volumes in the cluster.
For example, to list all Gluster Volumes in cluster 456, send a request like this:
GET /ovirt-engine/api/clusters/456/glustervolumes
GET /ovirt-engine/api/clusters/456/glustervolumes
The order of the returned list of volumes isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of volumes to return. | |
|
| In | A query string used to restrict the returned volumes. | |
|
| Out |
6.105.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.105.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.105.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of volumes to return. If not specified all the volumes are returned.
6.106. Group Copy linkLink copied to clipboard!
Manages a group of users. Use this service to either get groups details or remove groups. In order to add new groups please use service that manages the collection of groups.
| Name | Summary |
|---|---|
|
| Gets the system group information. |
|
| Removes the system group. |
6.106.1. get GET Copy linkLink copied to clipboard!
Gets the system group information.
Usage:
GET /ovirt-engine/api/groups/123
GET /ovirt-engine/api/groups/123
Will return the group information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The system group. |
6.106.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.106.2. remove DELETE Copy linkLink copied to clipboard!
Removes the system group.
Usage:
DELETE /ovirt-engine/api/groups/123
DELETE /ovirt-engine/api/groups/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.107. Groups Copy linkLink copied to clipboard!
Manages the collection of groups of users.
| Name | Summary |
|---|---|
|
| Add group from a directory service. |
|
| List all the groups in the system. |
6.107.1. add POST Copy linkLink copied to clipboard!
Add group from a directory service. Please note that domain name is name of the authorization provider.
For example, to add the Developers group from the internal-authz authorization provider send a request like this:
POST /ovirt-engine/api/groups
POST /ovirt-engine/api/groups
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The group to be added. |
6.107.2. list GET Copy linkLink copied to clipboard!
List all the groups in the system.
Usage:
GET /ovirt-engine/api/groups
GET /ovirt-engine/api/groups
Will return the list of groups:
The order of the returned list of groups isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of groups. | |
|
| In | Sets the maximum number of groups to return. | |
|
| In | A query string used to restrict the returned groups. |
6.107.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.107.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.107.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of groups to return. If not specified all the groups are returned.
6.108. Host Copy linkLink copied to clipboard!
A service to manage a host.
| Name | Summary |
|---|---|
|
| Activates the host for use, for example to run virtual machines. |
|
| Approve a pre-installed Hypervisor host for usage in the virtualization environment. |
|
| Marks the network configuration as good and persists it inside the host. |
|
| Copy the network configuration of the specified host to current host. |
|
| Deactivates the host to perform maintenance tasks. |
|
| Discovers iSCSI targets on the host, using the initiator details. |
|
| Enrolls the certificate of the host. |
|
| Controls the host’s power management device. |
|
| To manually set a host as the storage pool manager (SPM). |
|
| Gets the host details. |
|
| Installs the latest version of VDSM and related software on the host. |
|
| This method has been deprecated since Engine version 4. |
|
| Login to iSCSI targets on the host, using the target details. |
|
| Refresh the host devices and capabilities. |
|
| Remove the host from the system. |
|
| This method is used to change the configuration of the network interfaces of a host. |
|
| To synchronize all networks on the host, send a request like this: [source] ---- POST /ovirt-engine/api/hosts/123/syncallnetworks ---- With a request body like this: [source,xml] ---- <action/> ---- |
|
| Discovers the block Storage Domains which are candidates to be imported to the setup. |
|
| Update the host properties. |
|
| Upgrades VDSM and selected software on the host. |
|
| Check if there are upgrades available for the host. |
6.108.1. activate POST Copy linkLink copied to clipboard!
Activates the host for use, for example to run virtual machines.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.108.2. approve POST Copy linkLink copied to clipboard!
Approve a pre-installed Hypervisor host for usage in the virtualization environment.
This action also accepts an optional cluster element to define the target cluster for this host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | When set to 'true', this host will be activated after its approval completes. | |
|
| In | Indicates if the approval should be performed asynchronously. | |
|
| In | The cluster where the host will be added after it is approved. | |
|
| In | The host to approve. | |
|
| In | Indicates if the host should be rebooted after successful installation. |
6.108.2.1. activate Copy linkLink copied to clipboard!
When set to 'true', this host will be activated after its approval completes. When set to 'false' the host will remain in 'maintenance' status after its approval. Absence of this parameter will be interpreted as 'true', since the desired default behavior is activating the host after approval.
6.108.2.2. reboot Copy linkLink copied to clipboard!
Indicates if the host should be rebooted after successful installation. The default value is true.
6.108.3. commitnetconfig POST Copy linkLink copied to clipboard!
Marks the network configuration as good and persists it inside the host.
An API user commits the network configuration to persist a host network interface attachment or detachment, or persist the creation and deletion of a bonded interface.
Networking configuration is only committed after the engine has established that host connectivity is not lost as a result of the configuration changes. If host connectivity is lost, the host requires a reboot and automatically reverts to the previous networking configuration.
For example, to commit the network configuration of host with id 123 send a request like this:
POST /ovirt-engine/api/hosts/123/commitnetconfig
POST /ovirt-engine/api/hosts/123/commitnetconfig
With a request body like this:
<action/>
<action/>
Since Red Hat Virtualization Manager 4.3, it is possible to also specify commit_on_success in the setupnetworks request, in which case the new configuration is automatically saved in the {hypervisor-name} upon completing the setup and re-establishing connectivity between the {hypervisor-name} and Red Hat Virtualization Manager, and without waiting for a separate commitnetconfig request.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.108.4. copyhostnetworks POST Copy linkLink copied to clipboard!
Copy the network configuration of the specified host to current host.
Any network attachments that are not present on the source host will be erased from the target host by the copy operation.
To copy networks from another host, send a request like this:
POST /ovirt-engine/api/hosts/123/copyhostnetworks
POST /ovirt-engine/api/hosts/123/copyhostnetworks
With a request body like this:
<action> <source_host id="456"/> </action>
<action>
<source_host id="456"/>
</action>
6.108.5. deactivate POST Copy linkLink copied to clipboard!
Deactivates the host to perform maintenance tasks.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. | |
|
| In | ||
|
| In | Indicates if the gluster service should be stopped as part of deactivating the host. |
6.108.5.1. stop_gluster_service Copy linkLink copied to clipboard!
Indicates if the gluster service should be stopped as part of deactivating the host. It can be used while performing maintenance operations on the gluster host. Default value for this variable is false.
6.108.6. discoveriscsi POST Copy linkLink copied to clipboard!
Discovers iSCSI targets on the host, using the initiator details. Returns a list of IscsiDetails objects containing the discovered data.
For example, to discover iSCSI targets available in myiscsi.example.com, from host 123, send a request like this:
POST /ovirt-engine/api/hosts/123/discoveriscsi
POST /ovirt-engine/api/hosts/123/discoveriscsi
With a request body like this:
<action>
<iscsi>
<address>myiscsi.example.com</address>
</iscsi>
</action>
<action>
<iscsi>
<address>myiscsi.example.com</address>
</iscsi>
</action>
The result will be like this:
When using this method to discover iscsi targets, you can use an FQDN or an IP address, but you must use the iscsi details from the discovered targets results to log in using the iscsilogin method.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the discovery should be performed asynchronously. | |
|
| Out | The discovered targets including all connection information. | |
|
| In | The target iSCSI device. |
6.108.7. enrollcertificate POST Copy linkLink copied to clipboard!
Enrolls the certificate of the host. Useful in case you get a warning that it is about to expire or has already expired.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the enrollment should be performed asynchronously. |
6.108.8. fence POST Copy linkLink copied to clipboard!
Controls the host’s power management device.
For example, to start the host. This can be done via:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the fencing should be performed asynchronously. | |
|
| In | ||
|
| In | Indicates if host should be put into maintenance after restart. | |
|
| Out |
6.108.9. forceselectspm POST Copy linkLink copied to clipboard!
To manually set a host as the storage pool manager (SPM).
POST /ovirt-engine/api/hosts/123/forceselectspm
POST /ovirt-engine/api/hosts/123/forceselectspm
With a request body like this:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.108.10. get GET Copy linkLink copied to clipboard!
Gets the host details.
GET /ovirt-engine/api/hosts/123
GET /ovirt-engine/api/hosts/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the host should be included in the response. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | The queried host. |
6.108.10.1. all_content Copy linkLink copied to clipboard!
Indicates if all of the attributes of the host should be included in the response.
By default the following attributes are excluded:
-
hosted_engine
For example, to retrieve the complete representation of host '123':
GET /ovirt-engine/api/hosts/123?all_content=true
GET /ovirt-engine/api/hosts/123?all_content=true
These attributes are not included by default because retrieving them impacts performance. They are seldom used and require additional queries to the database. Use this parameter with caution and only when specifically required.
6.108.10.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.108.11. install POST Copy linkLink copied to clipboard!
Installs the latest version of VDSM and related software on the host.
The action also performs every configuration steps on the host which is done during adding host to the engine: kdump configuration, hosted-engine deploy, kernel options changes, etc.
The host type defines additional parameters for the action.
Example of installing a host, using curl and JSON, plain:
Example of installing a host using curl and JSON with hosted engine components:
Since version 4.1.2 of the engine, when a host is reinstalled we override the host firewall definitions by default.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | When set to 'true', this host will be activated after its installation completes. | |
|
| In | Indicates if the installation should be performed asynchronously. | |
|
| In |
When set to | |
|
| In |
The | |
|
| In | When installing {hypervisor-name}, an ISO image file is required. | |
|
| In | Indicates if the host should be rebooted after successful installation. | |
|
| In |
The password of the | |
|
| In | The SSH details used to connect to the host. | |
|
| In |
When set to |
6.108.11.1. activate Copy linkLink copied to clipboard!
When set to 'true', this host will be activated after its installation completes. When set to 'false' the host will remain in 'maintenance' status after its installation. Absence of this parameter will be interpreted as 'true', since the desired default behavior is activating the host after install.
6.108.11.2. deploy_hosted_engine Copy linkLink copied to clipboard!
When set to true this host will also deploy the self-hosted engine components. A missing value is treated as true i.e deploy. Omitting this parameter means false and will not perform any operation in the self-hosted engine area.
6.108.11.3. reboot Copy linkLink copied to clipboard!
Indicates if the host should be rebooted after successful installation. The default value is true.
6.108.11.4. undeploy_hosted_engine Copy linkLink copied to clipboard!
When set to true this host will un-deploy the self-hosted engine components, and this host will not function as part of the High Availability cluster. A missing value is treated as true i.e un-deploy. Omitting this parameter means false and will not perform any operation in the self-hosted engine area.
6.108.12. iscsidiscover POST Copy linkLink copied to clipboard!
This method has been deprecated since Engine version 4.4.6. DiscoverIscsi should be used instead.
Discovers iSCSI targets on the host, using the initiator details. Returns an array of strings containing the discovered data.
For example, to discover iSCSI targets available in myiscsi.example.com, from host 123, send a request like this:
POST /ovirt-engine/api/hosts/123/iscsidiscover
POST /ovirt-engine/api/hosts/123/iscsidiscover
With a request body like this:
<action>
<iscsi>
<address>myiscsi.example.com</address>
</iscsi>
</action>
<action>
<iscsi>
<address>myiscsi.example.com</address>
</iscsi>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the discovery should be performed asynchronously. | |
|
| In | The target iSCSI device. | |
|
| Out | The iSCSI targets. |
6.108.12.1. iscsi_targets Copy linkLink copied to clipboard!
The iSCSI targets. *
6.108.13. iscsilogin POST Copy linkLink copied to clipboard!
Login to iSCSI targets on the host, using the target details.
When using this method to log in, you must use the iscsi details from the discovered targets results in the discoveriscsi method.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the login should be performed asynchronously. | |
|
| In | The target iSCSI device. |
6.108.14. refresh POST Copy linkLink copied to clipboard!
Refresh the host devices and capabilities.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the refresh should be performed asynchronously. |
6.108.15. remove DELETE Copy linkLink copied to clipboard!
Remove the host from the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates that the host should be removed even if it is non-responsive, or if it is part of a Gluster Storage cluster and has volume bricks on it. |
6.108.16. setupnetworks POST Copy linkLink copied to clipboard!
This method is used to change the configuration of the network interfaces of a host.
For example, if you have a host with three network interfaces eth0, eth1 and eth2 and you want to configure a new bond using eth0 and eth1, and put a VLAN on top of it. Using a simple shell script and the curl command line HTTP client that can be done as follows:
This is valid for version 4 of the API. In previous versions some elements were represented as XML attributes instead of XML elements. In particular the options and ip elements were represented as follows:
<options name="mode" value="4"/> <options name="miimon" value="100"/> <ip address="192.168.122.10" netmask="255.255.255.0"/>
<options name="mode" value="4"/>
<options name="miimon" value="100"/>
<ip address="192.168.122.10" netmask="255.255.255.0"/>
The same thing can be done using the Python SDK with the following code:
To make sure that the network configuration has been saved in the host, and that it will be applied when the host is rebooted, remember to call commitnetconfig.
Since Red Hat Virtualization Manager 4.3, it is possible to also specify commit_on_success in the setupnetworks request, in which case the new configuration is automatically saved in the {hypervisor-name} upon completing the setup and re-establishing connectivity between the {hypervisor-name} and Red Hat Virtualization Manager, and without waiting for a separate commitnetconfig request.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | ||
|
| In | Specifies whether to automatically save the configuration in the {hypervisor-name} upon completing the setup and re-establishing connectivity between the {hypervisor-name} and Red Hat Virtualization Manager, and without waiting for a separate commitnetconfig request. | |
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | A list of network attachments that will be synchronized. |
6.108.16.1. commit_on_success Copy linkLink copied to clipboard!
Specifies whether to automatically save the configuration in the {hypervisor-name} upon completing the setup and re-establishing connectivity between the {hypervisor-name} and Red Hat Virtualization Manager, and without waiting for a separate commitnetconfig request. The default value is false, which means that the configuration will not be saved automatically.
6.108.17. syncallnetworks POST Copy linkLink copied to clipboard!
To synchronize all networks on the host, send a request like this:
POST /ovirt-engine/api/hosts/123/syncallnetworks
POST /ovirt-engine/api/hosts/123/syncallnetworks
With a request body like this:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.108.18. unregisteredstoragedomainsdiscover POST Copy linkLink copied to clipboard!
Discovers the block Storage Domains which are candidates to be imported to the setup. For FCP no arguments are required.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the discovery should be performed asynchronously. | |
|
| In | ||
|
| Out |
6.108.19. update PUT Copy linkLink copied to clipboard!
Update the host properties.
For example, to update a the kernel command line of a host send a request like this:
PUT /ovirt-engine/api/hosts/123
PUT /ovirt-engine/api/hosts/123
With request body like this:
<host>
<os>
<custom_kernel_cmdline>vfio_iommu_type1.allow_unsafe_interrupts=1</custom_kernel_cmdline>
</os>
</host>
<host>
<os>
<custom_kernel_cmdline>vfio_iommu_type1.allow_unsafe_interrupts=1</custom_kernel_cmdline>
</os>
</host>
6.108.20. upgrade POST Copy linkLink copied to clipboard!
Upgrades VDSM and selected software on the host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the upgrade should be performed asynchronously. | |
|
| In | This property is no longer relevant, since Vintage Node is no longer supported, and has been deprecated. | |
|
| In | Indicates if the host should be rebooted after the upgrade. | |
|
| In | Upgrade timeout. |
6.108.20.1. reboot Copy linkLink copied to clipboard!
Indicates if the host should be rebooted after the upgrade. By default the host is rebooted.
This parameter is ignored for {hypervisor-name}, which is always rebooted after the upgrade.
6.108.20.2. timeout Copy linkLink copied to clipboard!
Upgrade timeout.
The maximum time to wait for upgrade to finish in minutes. Default value is specified by ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT configration option.
6.108.21. upgradecheck POST Copy linkLink copied to clipboard!
Check if there are upgrades available for the host. If there are upgrades available an icon will be displayed next to host status icon in the Administration Portal. Audit log messages are also added to indicate the availability of upgrades. The upgrade can be started from the webadmin or by using the upgrade host action.
6.109. HostCpuUnits Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the List of all host’s CPUs with detailed information about the topology (socket, core) and with information about the current CPU pinning. |
6.109.1. list GET Copy linkLink copied to clipboard!
Returns the List of all host’s CPUs with detailed information about the topology (socket, core) and with information about the current CPU pinning.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.109.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.110. HostDevice Copy linkLink copied to clipboard!
A service to access a particular device of a host.
| Name | Summary |
|---|---|
|
| Retrieve information about a particular host’s device. |
6.110.1. get GET Copy linkLink copied to clipboard!
Retrieve information about a particular host’s device.
An example of getting a host device:
GET /ovirt-engine/api/hosts/123/devices/456
GET /ovirt-engine/api/hosts/123/devices/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.110.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.111. HostDevices Copy linkLink copied to clipboard!
A service to access host devices.
| Name | Summary |
|---|---|
|
| List the devices of a host. |
6.111.1. list GET Copy linkLink copied to clipboard!
List the devices of a host.
The order of the returned list of devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of devices to return. |
6.111.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.111.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of devices to return. If not specified all the devices are returned.
6.112. HostHook Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.112.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.112.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.113. HostHooks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of hooks configured for the host. |
6.113.1. list GET Copy linkLink copied to clipboard!
Returns the list of hooks configured for the host.
The order of the returned list of hooks is random.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of hooks to return. |
6.113.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.113.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of hooks to return. If not specified, all the hooks are returned.
6.114. HostNic Copy linkLink copied to clipboard!
A service to manage a network interface of a host.
| Name | Summary |
|---|---|
|
| |
|
| The action updates virtual function configuration in case the current resource represents an SR-IOV enabled NIC. |
6.114.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the host network interface should be included in the response. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.114.1.1. all_content Copy linkLink copied to clipboard!
Indicates if all of the attributes of the host network interface should be included in the response.
By default the following attributes are excluded:
-
virtual_functions_configuration
For example, to retrieve the complete representation network interface '456' of host '123':
GET /ovirt-engine/api/hosts/123/nics/456?all_content=true
GET /ovirt-engine/api/hosts/123/nics/456?all_content=true
These attributes are not included by default because retrieving them impacts performance. They are seldom used and require additional queries to the database. Use this parameter with caution and only when specifically required.
6.114.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.114.2. updatevirtualfunctionsconfiguration POST Copy linkLink copied to clipboard!
The action updates virtual function configuration in case the current resource represents an SR-IOV enabled NIC. The input should be consisted of at least one of the following properties:
-
allNetworksAllowed -
numberOfVirtualFunctions
Please see the HostNicVirtualFunctionsConfiguration type for the meaning of the properties.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In |
6.115. HostNics Copy linkLink copied to clipboard!
A service to manage the network interfaces of a host.
| Name | Summary |
|---|---|
|
| Returns the list of network interfaces of the host. |
6.115.1. list GET Copy linkLink copied to clipboard!
Returns the list of network interfaces of the host.
The order of the returned list of network interfaces isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the host network interface should be included in the response. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
6.115.1.1. all_content Copy linkLink copied to clipboard!
Indicates if all of the attributes of the host network interface should be included in the response.
By default the following attributes are excluded:
-
virtual_functions_configuration
For example, to retrieve the complete representation of network interface '456' of host '123':
GET /ovirt-engine/api/hosts/123/nics?all_content=true
GET /ovirt-engine/api/hosts/123/nics?all_content=true
These attributes are not included by default because retrieving them impacts performance. They are seldom used and require additional queries to the database. Use this parameter with caution and only when specifically required.
6.115.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.115.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.116. HostNumaNode Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.116.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.116.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.117. HostNumaNodes Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of NUMA nodes of the host. |
6.117.1. list GET Copy linkLink copied to clipboard!
Returns the list of NUMA nodes of the host.
The order of the returned list of NUMA nodes isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of nodes to return. | |
|
| Out |
6.117.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.117.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of nodes to return. If not specified all the nodes are returned.
6.118. HostStorage Copy linkLink copied to clipboard!
A service to manage host storages.
| Name | Summary |
|---|---|
|
| Get list of storages. |
6.118.1. list GET Copy linkLink copied to clipboard!
Get list of storages.
GET /ovirt-engine/api/hosts/123/storage
GET /ovirt-engine/api/hosts/123/storage
The XML response you get will be like this one:
The order of the returned list of storages isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Indicates if the status of the LUNs in the storage should be checked. | |
|
| Out | Retrieved list of storages. |
6.118.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.118.1.2. report_status Copy linkLink copied to clipboard!
Indicates if the status of the LUNs in the storage should be checked. Checking the status of the LUN is an heavy weight operation and this data is not always needed by the user. This parameter will give the option to not perform the status check of the LUNs.
The default is true for backward compatibility.
Here an example with the LUN status :
Here an example without the LUN status :
6.119. Hosts Copy linkLink copied to clipboard!
A service that manages hosts.
| Name | Summary |
|---|---|
|
| Creates a new host. |
|
| Get a list of all available hosts. |
6.119.1. add POST Copy linkLink copied to clipboard!
Creates a new host.
The host is created based on the attributes of the host parameter. The name, address, and root_password properties are required.
For example, to add a host, send the following request:
POST /ovirt-engine/api/hosts
POST /ovirt-engine/api/hosts
With the following request body:
<host> <name>myhost</name> <address>myhost.example.com</address> <root_password>myrootpassword</root_password> </host>
<host>
<name>myhost</name>
<address>myhost.example.com</address>
<root_password>myrootpassword</root_password>
</host>
The root_password element is only included in the client-provided initial representation and is not exposed in the representations returned from subsequent requests.
Since version 4.1.2 of the engine, when a host is newly added, the host’s firewall definitions are overridden by default.
To add a hosted engine host, use the optional deploy_hosted_engine parameter:
POST /ovirt-engine/api/hosts?deploy_hosted_engine=true
POST /ovirt-engine/api/hosts?deploy_hosted_engine=true
If the cluster has a default external network provider that is supported for automatic deployment, the external network provider is deployed when adding the host. Only external network providers for OVN are supported for the automatic deployment. To deploy an external network provider other than the one defined in the clusters, overwrite the external network provider when adding hosts, by sending the following request:
POST /ovirt-engine/api/hosts
POST /ovirt-engine/api/hosts
With a request body that contains a reference to the desired provider in the external_network_provider_configuration:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
When set to | |
|
| In |
When set to | |
|
| In/Out | The host definition with which the new host is created is passed as a parameter, and the newly created host is returned. | |
|
| In | Indicates if the host should be rebooted after successful installation. | |
|
| In |
When set to |
6.119.1.1. activate Copy linkLink copied to clipboard!
When set to true, this host will be activated after its installation completes. When set to false the host will remain in maintenance status after its installation. Absence of this parameter will be interpreted as true, since the desired default behavior is activating the host after install.
6.119.1.2. deploy_hosted_engine Copy linkLink copied to clipboard!
When set to true, this host deploys the hosted engine components. A missing value is treated as true, i.e., deploy the hosted engine components. Omitting this parameter equals false, and the host performs no operation in the hosted engine area.
6.119.1.3. reboot Copy linkLink copied to clipboard!
Indicates if the host should be rebooted after successful installation. The default value is true.
6.119.1.4. undeploy_hosted_engine Copy linkLink copied to clipboard!
When set to true, this host un-deploys the hosted engine components and does not function as part of the High Availability cluster. A missing value is treated as true, i.e., un-deploy. Omitting this parameter equals false and the host performs no operation in the hosted engine area.
6.119.2. list GET Copy linkLink copied to clipboard!
Get a list of all available hosts.
For example, to list the hosts send the following request:
GET /ovirt-engine/api/hosts
GET /ovirt-engine/api/hosts
The response body will be similar to this:
The order of the returned list of hosts is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the hosts should be included in the response. | |
|
| In |
Indicates if the search performed using the | |
|
| In |
This parameter can be used with | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. | |
|
| In | Accepts a comma-separated list of virtual machine IDs and returns the hosts that these virtual machines can be migrated to. | |
|
| In | A query string used to restrict the returned hosts. |
6.119.2.1. all_content Copy linkLink copied to clipboard!
Indicates if all of the attributes of the hosts should be included in the response.
By default the following host attributes are excluded:
-
hosted_engine
For example, to retrieve the complete representation of the hosts:
GET /ovirt-engine/api/hosts?all_content=true
GET /ovirt-engine/api/hosts?all_content=true
These attributes are not included by default because retrieving them impacts performance. They are seldom used and require additional queries to the database. Use this parameter with caution and only when specifically required.
6.119.2.2. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.119.2.3. check_vms_in_affinity_closure Copy linkLink copied to clipboard!
This parameter can be used with migration_target_of to get valid migration targets for the listed virtual machines and all other virtual machines that are in positive enforcing affinity with the listed virtual machines.
This is useful in case the virtual machines will be migrated together with others in positive affinity groups.
The default value is false.
GET /ovirt-engine/api/hosts?migration_target_of=123,456&check_vms_in_affinity_closure=true
GET /ovirt-engine/api/hosts?migration_target_of=123,456&check_vms_in_affinity_closure=true
6.119.2.4. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.119.2.5. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
6.119.2.6. migration_target_of Copy linkLink copied to clipboard!
Accepts a comma-separated list of virtual machine IDs and returns the hosts that these virtual machines can be migrated to.
For example, to retrieve the list of hosts to which the virtual machine with ID 123 and the virtual machine with ID 456 can be migrated to, send the following request:
GET /ovirt-engine/api/hosts?migration_target_of=123,456
GET /ovirt-engine/api/hosts?migration_target_of=123,456
6.120. Icon Copy linkLink copied to clipboard!
A service to manage an icon (read-only).
| Name | Summary |
|---|---|
|
| Get an icon. |
6.120.1. get GET Copy linkLink copied to clipboard!
Get an icon.
GET /ovirt-engine/api/icons/123
GET /ovirt-engine/api/icons/123
You will get a XML response like this one:
<icon id="123"> <data>Some binary data here</data> <media_type>image/png</media_type> </icon>
<icon id="123">
<data>Some binary data here</data>
<media_type>image/png</media_type>
</icon>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieved icon. |
6.120.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.121. Icons Copy linkLink copied to clipboard!
A service to manage icons.
| Name | Summary |
|---|---|
|
| Get a list of icons. |
6.121.1. list GET Copy linkLink copied to clipboard!
Get a list of icons.
GET /ovirt-engine/api/icons
GET /ovirt-engine/api/icons
You will get a XML response which is similar to this one:
The order of the returned list of icons isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieved list of icons. | |
|
| In | Sets the maximum number of icons to return. |
6.121.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.121.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of icons to return. If not specified all the icons are returned.
6.122. Image Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Imports an image. |
6.122.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.122.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.122.2. import POST Copy linkLink copied to clipboard!
Imports an image.
If the import_as_template parameter is true then the image will be imported as a template, otherwise it will be imported as a disk.
When imported as a template, the name of the template can be specified by the optional template.name parameter. If that parameter is not specified, then the name of the template will be automatically assigned by the engine as GlanceTemplate-x (where x will be seven random hexadecimal characters).
When imported as a disk, the name of the disk can be specified by the optional disk.name parameter. If that parameter is not specified, then the name of the disk will be automatically assigned by the engine as GlanceDisk-x (where x will be the seven hexadecimal characters of the image identifier).
It is recommended to always explicitly specify the template or disk name, to avoid these automatic names generated by the engine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In |
The cluster to which the image should be imported if the | |
|
| In | The disk to import. | |
|
| In | Specifies if a template should be created from the imported disk. | |
|
| In | The storage domain to which the disk should be imported. | |
|
| In |
The name of the template being created if the |
6.123. ImageTransfer Copy linkLink copied to clipboard!
This service provides a mechanism to control an image transfer. The client will have to create a transfer by using add of the image transfers service, stating the image to transfer data to/from.
After doing that, the transfer is managed by this service.
Using oVirt’s Python’s SDK:
Uploading a disk with id 123 (on a random host in the data center):
Uploading a disk with id 123 on host id 456:
If the user wishes to download a disk rather than upload, he/she should specify download as the direction attribute of the transfer. This will grant a read permission from the image, instead of a write permission.
E.g:
Transfers have phases, which govern the flow of the upload/download. A client implementing such a flow should poll/check the transfer’s phase and act accordingly. All the possible phases can be found in ImageTransferPhase.
After adding a new transfer, its phase will be initializing. The client will have to poll on the transfer’s phase until it changes. When the phase becomes transferring, the session is ready to start the transfer.
For example:
transfer_service = transfers_service.image_transfer_service(transfer.id) while transfer.phase == types.ImageTransferPhase.INITIALIZING: time.sleep(3) transfer = transfer_service.get()
transfer_service = transfers_service.image_transfer_service(transfer.id)
while transfer.phase == types.ImageTransferPhase.INITIALIZING:
time.sleep(3)
transfer = transfer_service.get()
At that stage, if the phase of the transfer is paused_system, the session was not successfully established. This can happen if ovirt-imageio is not running in the selected host.
| Name | Summary |
|---|---|
|
| Cancel the image transfer session. |
|
| Extend the image transfer session. |
|
| After finishing to transfer the data, finalize the transfer. |
|
| Get the image transfer entity. |
|
| Pause the image transfer session. |
|
| Resume the image transfer session. |
6.123.1. cancel POST Copy linkLink copied to clipboard!
Cancel the image transfer session. This terminates the transfer operation and removes the partial image.
6.123.2. extend POST Copy linkLink copied to clipboard!
Extend the image transfer session.
6.123.3. finalize POST Copy linkLink copied to clipboard!
After finishing to transfer the data, finalize the transfer.
This will make sure that the data being transferred is valid and fits the image entity that was targeted in the transfer. Specifically, will verify that if the image entity is a QCOW disk, the data uploaded is indeed a QCOW file, and that the image doesn’t have a backing file.
6.123.4. get GET Copy linkLink copied to clipboard!
Get the image transfer entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.123.4.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.123.5. pause POST Copy linkLink copied to clipboard!
Pause the image transfer session.
6.123.6. resume POST Copy linkLink copied to clipboard!
Resume the image transfer session. The client will need to poll the transfer’s phase until it is different than resuming. For example:
6.124. ImageTransfers Copy linkLink copied to clipboard!
This service manages image transfers, for performing Image I/O API in Red Hat Virtualization. Please refer to image transfer for further documentation.
| Name | Summary |
|---|---|
|
| Add a new image transfer. |
|
| Retrieves the list of image transfers that are currently being performed. |
6.124.1. add POST Copy linkLink copied to clipboard!
Add a new image transfer. An image, disk or disk snapshot needs to be specified in order to make a new transfer.
The image attribute is deprecated since version 4.2 of the engine. Use the disk or snapshot attributes instead.
Creating a new image transfer for downloading or uploading a disk:
To create an image transfer to download or upload a disk with id 123, send the following request:
POST /ovirt-engine/api/imagetransfers
POST /ovirt-engine/api/imagetransfers
With a request body like this:
<image_transfer> <disk id="123"/> <direction>upload|download</direction> </image_transfer>
<image_transfer>
<disk id="123"/>
<direction>upload|download</direction>
</image_transfer>
Creating a new image transfer for downloading or uploading a disk_snapshot:
To create an image transfer to download or upload a disk_snapshot with id 456, send the following request:
POST /ovirt-engine/api/imagetransfers
POST /ovirt-engine/api/imagetransfers
With a request body like this:
<image_transfer> <snapshot id="456"/> <direction>download|upload</direction> </image_transfer>
<image_transfer>
<snapshot id="456"/>
<direction>download|upload</direction>
</image_transfer>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The image transfer to add. |
6.124.2. list GET Copy linkLink copied to clipboard!
Retrieves the list of image transfers that are currently being performed.
The order of the returned list of image transfers is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | A list of image transfers that are currently being performed. |
6.124.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.125. Images Copy linkLink copied to clipboard!
Manages the set of images available in an storage domain or in an OpenStack image provider.
| Name | Summary |
|---|---|
|
| Returns the list of images available in the storage domain or provider. |
6.125.1. list GET Copy linkLink copied to clipboard!
Returns the list of images available in the storage domain or provider.
The order of the returned list of images isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of images to return. |
6.125.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.125.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of images to return. If not specified all the images are returned.
6.126. InstanceType Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Get a specific instance type and it’s attributes. |
|
| Removes a specific instance type from the system. |
|
| Update a specific instance type and it’s attributes. |
6.126.1. get GET Copy linkLink copied to clipboard!
Get a specific instance type and it’s attributes.
GET /ovirt-engine/api/instancetypes/123
GET /ovirt-engine/api/instancetypes/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.126.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.126.2. remove DELETE Copy linkLink copied to clipboard!
Removes a specific instance type from the system.
If a virtual machine was created using an instance type X after removal of the instance type the virtual machine’s instance type will be set to custom.
DELETE /ovirt-engine/api/instancetypes/123
DELETE /ovirt-engine/api/instancetypes/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.126.3. update PUT Copy linkLink copied to clipboard!
Update a specific instance type and it’s attributes.
All the attributes are editable after creation. If a virtual machine was created using an instance type X and some configuration in instance type X was updated, the virtual machine’s configuration will be updated automatically by the engine.
PUT /ovirt-engine/api/instancetypes/123
PUT /ovirt-engine/api/instancetypes/123
For example, to update the memory of instance type 123 to 1 GiB and set the cpu topology to 2 sockets and 1 core, send a request like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.127. InstanceTypeGraphicsConsole Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets graphics console configuration of the instance type. |
|
| Remove the graphics console from the instance type. |
6.127.1. get GET Copy linkLink copied to clipboard!
Gets graphics console configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the graphics console of the instance type. | |
|
| In | Indicates which inner links should be followed. |
6.127.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.127.2. remove DELETE Copy linkLink copied to clipboard!
Remove the graphics console from the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.128. InstanceTypeGraphicsConsoles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add new graphics console to the instance type. |
|
| Lists all the configured graphics consoles of the instance type. |
6.128.1. add POST Copy linkLink copied to clipboard!
Add new graphics console to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.128.2. list GET Copy linkLink copied to clipboard!
Lists all the configured graphics consoles of the instance type.
The order of the returned list of graphics consoles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of graphics consoles of the instance type. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of consoles to return. |
6.128.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.128.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
6.129. InstanceTypeNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets network interface configuration of the instance type. |
|
| Remove the network interface from the instance type. |
|
| Updates the network interface configuration of the instance type. |
6.129.1. get GET Copy linkLink copied to clipboard!
Gets network interface configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.129.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.129.2. remove DELETE Copy linkLink copied to clipboard!
Remove the network interface from the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.129.3. update PUT Copy linkLink copied to clipboard!
Updates the network interface configuration of the instance type.
6.130. InstanceTypeNics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add new network interface to the instance type. |
|
| Lists all the configured network interface of the instance type. |
6.130.1. add POST Copy linkLink copied to clipboard!
Add new network interface to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.130.2. list GET Copy linkLink copied to clipboard!
Lists all the configured network interface of the instance type.
The order of the returned list of network interfaces isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of NICs to return. | |
|
| Nic[] | Out | |
|
| In | A query string used to restrict the returned templates. |
6.130.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.130.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.131. InstanceTypeWatchdog Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets watchdog configuration of the instance type. |
|
| Remove a watchdog from the instance type. |
|
| Updates the watchdog configuration of the instance type. |
6.131.1. get GET Copy linkLink copied to clipboard!
Gets watchdog configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.131.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.131.2. remove DELETE Copy linkLink copied to clipboard!
Remove a watchdog from the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.131.3. update PUT Copy linkLink copied to clipboard!
Updates the watchdog configuration of the instance type.
6.132. InstanceTypeWatchdogs Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add new watchdog to the instance type. |
|
| Lists all the configured watchdogs of the instance type. |
6.132.1. add POST Copy linkLink copied to clipboard!
Add new watchdog to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.132.2. list GET Copy linkLink copied to clipboard!
Lists all the configured watchdogs of the instance type.
The order of the returned list of watchdogs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of watchdogs to return. | |
|
| In | A query string used to restrict the returned templates. | |
|
| Out |
6.132.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.132.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
6.133. InstanceTypes Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new instance type. |
|
| Lists all existing instance types in the system. |
6.133.1. add POST Copy linkLink copied to clipboard!
Creates a new instance type.
This requires only a name attribute and can include all hardware configurations of the virtual machine.
POST /ovirt-engine/api/instancetypes
POST /ovirt-engine/api/instancetypes
With a request body like this:
<instance_type> <name>myinstancetype</name> </template>
<instance_type>
<name>myinstancetype</name>
</template>
Creating an instance type with all hardware configurations with a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.133.2. list GET Copy linkLink copied to clipboard!
Lists all existing instance types in the system.
The order of the returned list of instance types isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of instance types to return. | |
|
| In | A query string used to restrict the returned templates. |
6.133.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.133.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.133.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of instance types to return. If not specified all the instance types are returned.
6.134. IscsiBond Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes of an existing iSCSI bond. |
|
| Updates an iSCSI bond. |
6.134.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The iSCSI bond. | |
|
| In | Indicates which inner links should be followed. |
6.134.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.134.2. remove DELETE Copy linkLink copied to clipboard!
Removes of an existing iSCSI bond.
For example, to remove the iSCSI bond 456 send a request like this:
DELETE /ovirt-engine/api/datacenters/123/iscsibonds/456
DELETE /ovirt-engine/api/datacenters/123/iscsibonds/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.134.3. update PUT Copy linkLink copied to clipboard!
Updates an iSCSI bond.
Updating of an iSCSI bond can be done on the name and the description attributes only. For example, to update the iSCSI bond 456 of data center 123, send a request like this:
PUT /ovirt-engine/api/datacenters/123/iscsibonds/1234
PUT /ovirt-engine/api/datacenters/123/iscsibonds/1234
The request body should look like this:
<iscsi_bond> <name>mybond</name> <description>My iSCSI bond</description> </iscsi_bond>
<iscsi_bond>
<name>mybond</name>
<description>My iSCSI bond</description>
</iscsi_bond>
6.135. IscsiBonds Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Create a new iSCSI bond on a data center. |
|
| Returns the list of iSCSI bonds configured in the data center. |
6.135.1. add POST Copy linkLink copied to clipboard!
Create a new iSCSI bond on a data center.
For example, to create a new iSCSI bond on data center 123 using storage connections 456 and 789, send a request like this:
POST /ovirt-engine/api/datacenters/123/iscsibonds
POST /ovirt-engine/api/datacenters/123/iscsibonds
The request body should look like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.135.2. list GET Copy linkLink copied to clipboard!
Returns the list of iSCSI bonds configured in the data center.
The order of the returned list of iSCSI bonds isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of bonds to return. |
6.135.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.135.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of bonds to return. If not specified all the bonds are returned.
6.136. Job Copy linkLink copied to clipboard!
A service to manage a job.
| Name | Summary |
|---|---|
|
| Set an external job execution to be cleared by the system. |
|
| Marks an external job execution as ended. |
|
| Retrieves a job. |
6.136.1. clear POST Copy linkLink copied to clipboard!
Set an external job execution to be cleared by the system.
For example, to set a job with identifier 123 send the following request:
POST /ovirt-engine/api/jobs/clear
POST /ovirt-engine/api/jobs/clear
With the following request body:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.136.2. end POST Copy linkLink copied to clipboard!
Marks an external job execution as ended.
For example, to terminate a job with identifier 123 send the following request:
POST /ovirt-engine/api/jobs/end
POST /ovirt-engine/api/jobs/end
With the following request body:
<action> <force>true</force> <status>finished</status> </action>
<action>
<force>true</force>
<status>finished</status>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Indicates if the job should be forcibly terminated. | |
|
| In | Indicates if the job should be marked as successfully finished or as failed. |
6.136.2.1. succeeded Copy linkLink copied to clipboard!
Indicates if the job should be marked as successfully finished or as failed.
This parameter is optional, and the default value is true.
6.136.3. get GET Copy linkLink copied to clipboard!
Retrieves a job.
GET /ovirt-engine/api/jobs/123
GET /ovirt-engine/api/jobs/123
You will receive response in XML like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieves the representation of the job. |
6.136.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.137. Jobs Copy linkLink copied to clipboard!
A service to manage jobs.
| Name | Summary |
|---|---|
|
| Add an external job. |
|
| Retrieves the representation of the jobs. |
6.137.1. add POST Copy linkLink copied to clipboard!
Add an external job.
For example, to add a job with the following request:
POST /ovirt-engine/api/jobs
POST /ovirt-engine/api/jobs
With the following request body:
<job> <description>Doing some work</description> <auto_cleared>true</auto_cleared> </job>
<job>
<description>Doing some work</description>
<auto_cleared>true</auto_cleared>
</job>
The response should look like:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Job that will be added. |
6.137.2. list GET Copy linkLink copied to clipboard!
Retrieves the representation of the jobs.
GET /ovirt-engine/api/jobs
GET /ovirt-engine/api/jobs
You will receive response in XML like this one:
The order of the returned list of jobs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| Job[] | Out | A representation of jobs. |
|
| In | Sets the maximum number of jobs to return. | |
|
| In | A query string used to restrict the returned jobs. |
6.137.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.137.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.137.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of jobs to return. If not specified all the jobs are returned.
6.138. KatelloErrata Copy linkLink copied to clipboard!
A service to manage Katello errata. The information is retrieved from Katello.
| Name | Summary |
|---|---|
|
| Retrieves the representation of the Katello errata. |
6.138.1. list GET Copy linkLink copied to clipboard!
Retrieves the representation of the Katello errata.
GET /ovirt-engine/api/katelloerrata
GET /ovirt-engine/api/katelloerrata
You will receive response in XML like this one:
The order of the returned list of erratum isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A representation of Katello errata. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of errata to return. |
6.138.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.138.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of errata to return. If not specified all the errata are returned.
6.139. KatelloErratum Copy linkLink copied to clipboard!
A service to manage a Katello erratum.
| Name | Summary |
|---|---|
|
| Retrieves a Katello erratum. |
6.139.1. get GET Copy linkLink copied to clipboard!
Retrieves a Katello erratum.
GET /ovirt-engine/api/katelloerrata/123
GET /ovirt-engine/api/katelloerrata/123
You will receive response in XML like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieves the representation of the Katello erratum. | |
|
| In | Indicates which inner links should be followed. |
6.139.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.140. LinkLayerDiscoveryProtocol Copy linkLink copied to clipboard!
A service to fetch information elements received by Link Layer Discovery Protocol (LLDP).
| Name | Summary |
|---|---|
|
| Fetches information elements received by LLDP. |
6.140.1. list GET Copy linkLink copied to clipboard!
Fetches information elements received by LLDP.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieves a list of information elements received by LLDP. | |
|
| In | Indicates which inner links should be followed. |
6.140.1.1. elements Copy linkLink copied to clipboard!
Retrieves a list of information elements received by LLDP.
For example, to retrieve the information elements received on the NIC 321 on host 123, send a request like this:
GET ovirt-engine/api/hosts/123/nics/321/linklayerdiscoveryprotocolelements
GET ovirt-engine/api/hosts/123/nics/321/linklayerdiscoveryprotocolelements
It will return a response like this:
6.140.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.141. MacPool Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a MAC address pool. |
|
| Updates a MAC address pool. |
6.141.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.141.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.141.2. remove DELETE Copy linkLink copied to clipboard!
Removes a MAC address pool.
For example, to remove the MAC address pool having id 123 send a request like this:
DELETE /ovirt-engine/api/macpools/123
DELETE /ovirt-engine/api/macpools/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.141.3. update PUT Copy linkLink copied to clipboard!
Updates a MAC address pool.
The name, description, allow_duplicates, and ranges attributes can be updated.
For example, to update the MAC address pool of id 123 send a request like this:
PUT /ovirt-engine/api/macpools/123
PUT /ovirt-engine/api/macpools/123
With a request body like this:
6.142. MacPools Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new MAC address pool. |
|
| Return the list of MAC address pools of the system. |
6.142.1. add POST Copy linkLink copied to clipboard!
Creates a new MAC address pool.
Creation of a MAC address pool requires values for the name and ranges attributes.
For example, to create MAC address pool send a request like this:
POST /ovirt-engine/api/macpools
POST /ovirt-engine/api/macpools
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.142.2. list GET Copy linkLink copied to clipboard!
Return the list of MAC address pools of the system.
The returned list of MAC address pools isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of pools to return. | |
|
| Out |
6.142.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.142.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of pools to return. If not specified all the pools are returned.
6.143. Measurable Copy linkLink copied to clipboard!
6.144. Moveable Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.144.1. move POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the move should be performed asynchronously. |
6.145. Network Copy linkLink copied to clipboard!
A service managing a network
| Name | Summary |
|---|---|
|
| Gets a logical network. |
|
| Removes a logical network, or the association of a logical network to a data center. |
|
| Updates a logical network. |
6.145.1. get GET Copy linkLink copied to clipboard!
Gets a logical network.
For example:
GET /ovirt-engine/api/networks/123
GET /ovirt-engine/api/networks/123
Will respond:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.145.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.145.2. remove DELETE Copy linkLink copied to clipboard!
Removes a logical network, or the association of a logical network to a data center.
For example, to remove the logical network 123 send a request like this:
DELETE /ovirt-engine/api/networks/123
DELETE /ovirt-engine/api/networks/123
Each network is bound exactly to one data center. So if we disassociate network with data center it has the same result as if we would just remove that network. However it might be more specific to say we’re removing network 456 of data center 123.
For example, to remove the association of network 456 to data center 123 send a request like this:
DELETE /ovirt-engine/api/datacenters/123/networks/456
DELETE /ovirt-engine/api/datacenters/123/networks/456
To remove an external logical network, the network has to be removed directly from its provider by OpenStack Networking API. The entity representing the external network inside Red Hat Virtualization is removed automatically, if auto_sync is enabled for the provider, otherwise the entity has to be removed using this method.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.145.3. update PUT Copy linkLink copied to clipboard!
Updates a logical network.
The name, description, ip, vlan, stp and display attributes can be updated.
For example, to update the description of the logical network 123 send a request like this:
PUT /ovirt-engine/api/networks/123
PUT /ovirt-engine/api/networks/123
With a request body like this:
<network> <description>My updated description</description> </network>
<network>
<description>My updated description</description>
</network>
The maximum transmission unit of a network is set using a PUT request to specify the integer value of the mtu attribute.
For example, to set the maximum transmission unit send a request like this:
PUT /ovirt-engine/api/datacenters/123/networks/456
PUT /ovirt-engine/api/datacenters/123/networks/456
With a request body like this:
<network> <mtu>1500</mtu> </network>
<network>
<mtu>1500</mtu>
</network>
Updating external networks is not propagated to the provider.
6.146. NetworkAttachment Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the specified network attachment on the host. |
6.146.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.146.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.146.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.146.3. update PUT Copy linkLink copied to clipboard!
Update the specified network attachment on the host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.147. NetworkAttachments Copy linkLink copied to clipboard!
Manages the set of network attachments of a host or host NIC.
| Name | Summary |
|---|---|
|
| Add a new network attachment to the network interface. |
|
| Returns the list of network attachments of the host or host NIC. |
6.147.1. add POST Copy linkLink copied to clipboard!
Add a new network attachment to the network interface.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.147.2. list GET Copy linkLink copied to clipboard!
Returns the list of network attachments of the host or host NIC.
The order of the returned list of network attachments isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of attachments to return. |
6.147.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.147.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of attachments to return. If not specified all the attachments are returned.
6.148. NetworkFilter Copy linkLink copied to clipboard!
Manages a network filter.
Please note that version is referring to the minimal support version for the specific filter.
| Name | Summary |
|---|---|
|
| Retrieves a representation of the network filter. |
6.148.1. get GET Copy linkLink copied to clipboard!
Retrieves a representation of the network filter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.148.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.149. NetworkFilters Copy linkLink copied to clipboard!
Represents a readonly network filters sub-collection.
The network filter enables to filter packets send to/from the VM’s nic according to defined rules. For more information please refer to NetworkFilter service documentation
Network filters are supported in different versions, starting from version 3.0.
A network filter is defined for each vnic profile.
A vnic profile is defined for a specific network.
A network can be assigned to several different clusters. In the future, each network will be defined in cluster level.
Currently, each network is being defined at data center level. Potential network filters for each network are determined by the network’s data center compatibility version V. V must be >= the network filter version in order to configure this network filter for a specific network. Please note, that if a network is assigned to cluster with a version supporting a network filter, the filter may not be available due to the data center version being smaller then the network filter’s version.
Example of listing all of the supported network filters for a specific cluster:
GET http://localhost:8080/ovirt-engine/api/clusters/{cluster:id}/networkfilters
GET http://localhost:8080/ovirt-engine/api/clusters/{cluster:id}/networkfilters
Output:
| Name | Summary |
|---|---|
|
| Retrieves the representations of the network filters. |
6.149.1. list GET Copy linkLink copied to clipboard!
Retrieves the representations of the network filters.
The order of the returned list of network filters isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.149.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.150. NetworkLabel Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a label from a logical network. |
6.150.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.150.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.150.2. remove DELETE Copy linkLink copied to clipboard!
Removes a label from a logical network.
For example, to remove the label exemplary from a logical network having id 123 send the following request:
DELETE /ovirt-engine/api/networks/123/networklabels/exemplary
DELETE /ovirt-engine/api/networks/123/networklabels/exemplary
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.151. NetworkLabels Copy linkLink copied to clipboard!
Manages the ser of labels attached to a network or to a host NIC.
| Name | Summary |
|---|---|
|
| Attaches label to logical network. |
|
| Returns the list of labels attached to the network or host NIC. |
6.151.1. add POST Copy linkLink copied to clipboard!
Attaches label to logical network.
You can attach labels to a logical network to automate the association of that logical network with physical host network interfaces to which the same label has been attached.
For example, to attach the label mylabel to a logical network having id 123 send a request like this:
POST /ovirt-engine/api/networks/123/networklabels
POST /ovirt-engine/api/networks/123/networklabels
With a request body like this:
<network_label id="mylabel"/>
<network_label id="mylabel"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.151.2. list GET Copy linkLink copied to clipboard!
Returns the list of labels attached to the network or host NIC.
The order of the returned list of labels isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of labels to return. |
6.151.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.151.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of labels to return. If not specified all the labels are returned.
6.152. Networks Copy linkLink copied to clipboard!
Manages logical networks.
The engine creates a default ovirtmgmt network on installation. This network acts as the management network for access to hypervisor hosts. This network is associated with the Default cluster and is a member of the Default data center.
| Name | Summary |
|---|---|
|
| Creates a new logical network, or associates an existing network with a data center. |
|
| List logical networks. |
6.152.1. add POST Copy linkLink copied to clipboard!
Creates a new logical network, or associates an existing network with a data center.
Creation of a new network requires the name and data_center elements.
For example, to create a network named mynetwork for data center 123 send a request like this:
POST /ovirt-engine/api/networks
POST /ovirt-engine/api/networks
With a request body like this:
<network> <name>mynetwork</name> <data_center id="123"/> </network>
<network>
<name>mynetwork</name>
<data_center id="123"/>
</network>
To associate the existing network 456 with the data center 123 send a request like this:
POST /ovirt-engine/api/datacenters/123/networks
POST /ovirt-engine/api/datacenters/123/networks
With a request body like this:
<network> <name>ovirtmgmt</name> </network>
<network>
<name>ovirtmgmt</name>
</network>
To create a network named exnetwork on top of an external OpenStack network provider 456 send a request like this:
POST /ovirt-engine/api/networks
POST /ovirt-engine/api/networks
<network> <name>exnetwork</name> <external_provider id="456"/> <data_center id="123"/> </network>
<network>
<name>exnetwork</name>
<external_provider id="456"/>
<data_center id="123"/>
</network>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.152.2. list GET Copy linkLink copied to clipboard!
List logical networks.
For example:
GET /ovirt-engine/api/networks
GET /ovirt-engine/api/networks
Will respond:
The order of the returned list of networks is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned networks. |
6.152.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.152.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.152.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.153. NicNetworkFilterParameter Copy linkLink copied to clipboard!
This service manages a parameter for a network filter.
| Name | Summary |
|---|---|
|
| Retrieves a representation of the network filter parameter. |
|
| Removes the filter parameter. |
|
| Updates the network filter parameter. |
6.153.1. get GET Copy linkLink copied to clipboard!
Retrieves a representation of the network filter parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The representation of the network filter parameter. |
6.153.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.153.2. remove DELETE Copy linkLink copied to clipboard!
Removes the filter parameter.
For example, to remove the filter parameter with id 123 on NIC 456 of virtual machine 789 send a request like this:
DELETE /ovirt-engine/api/vms/789/nics/456/networkfilterparameters/123
DELETE /ovirt-engine/api/vms/789/nics/456/networkfilterparameters/123
6.153.3. update PUT Copy linkLink copied to clipboard!
Updates the network filter parameter.
For example, to update the network filter parameter having with with id 123 on NIC 456 of virtual machine 789 send a request like this:
PUT /ovirt-engine/api/vms/789/nics/456/networkfilterparameters/123
PUT /ovirt-engine/api/vms/789/nics/456/networkfilterparameters/123
With a request body like this:
<network_filter_parameter> <name>updatedName</name> <value>updatedValue</value> </network_filter_parameter>
<network_filter_parameter>
<name>updatedName</name>
<value>updatedValue</value>
</network_filter_parameter>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The network filter parameter that is being updated. |
6.154. NicNetworkFilterParameters Copy linkLink copied to clipboard!
This service manages a collection of parameters for network filters.
| Name | Summary |
|---|---|
|
| Add a network filter parameter. |
|
| Retrieves the representations of the network filter parameters. |
6.154.1. add POST Copy linkLink copied to clipboard!
Add a network filter parameter.
For example, to add the parameter for the network filter on NIC 456 of virtual machine 789 send a request like this:
POST /ovirt-engine/api/vms/789/nics/456/networkfilterparameters
POST /ovirt-engine/api/vms/789/nics/456/networkfilterparameters
With a request body like this:
<network_filter_parameter> <name>IP</name> <value>10.0.1.2</value> </network_filter_parameter>
<network_filter_parameter>
<name>IP</name>
<value>10.0.1.2</value>
</network_filter_parameter>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The network filter parameter that is being added. |
6.154.2. list GET Copy linkLink copied to clipboard!
Retrieves the representations of the network filter parameters.
The order of the returned list of network filters isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of the network filter parameters. |
6.154.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.155. OpenstackImage Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Imports a virtual machine from a Glance image storage domain. |
6.155.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.155.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.155.2. import POST Copy linkLink copied to clipboard!
Imports a virtual machine from a Glance image storage domain.
For example, to import the image with identifier 456 from the storage domain with identifier 123 send a request like this:
POST /ovirt-engine/api/openstackimageproviders/123/images/456/import
POST /ovirt-engine/api/openstackimageproviders/123/images/456/import
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In |
This parameter is mandatory in case of using | |
|
| In | ||
|
| In | Indicates whether the image should be imported as a template. | |
|
| In | ||
|
| In |
6.156. OpenstackImageProvider Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Import the SSL certificates of the external host provider. |
|
| |
|
| In order to test connectivity for external provider we need to run following request where 123 is an id of a provider. |
|
| Update the specified OpenStack image provider in the system. |
6.156.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.156.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.156.2. importcertificates POST Copy linkLink copied to clipboard!
Import the SSL certificates of the external host provider.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.156.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.156.4. testconnectivity POST Copy linkLink copied to clipboard!
In order to test connectivity for external provider we need to run following request where 123 is an id of a provider.
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.156.5. update PUT Copy linkLink copied to clipboard!
Update the specified OpenStack image provider in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.157. OpenstackImageProviders Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new OpenStack image provider to the system. |
|
| Returns the list of providers. |
6.157.1. add POST Copy linkLink copied to clipboard!
Add a new OpenStack image provider to the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.157.2. list GET Copy linkLink copied to clipboard!
Returns the list of providers.
The order of the returned list of providers isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of providers to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned OpenStack image providers. |
6.157.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.157.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.158. OpenstackImages Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Lists the images of a Glance image storage domain. |
6.158.1. list GET Copy linkLink copied to clipboard!
Lists the images of a Glance image storage domain.
The order of the returned list of images isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of images to return. |
6.158.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.158.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of images to return. If not specified all the images are returned.
6.159. OpenstackNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| This operation imports an external network into Red Hat Virtualization. |
6.159.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.159.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.159.2. import POST Copy linkLink copied to clipboard!
This operation imports an external network into Red Hat Virtualization. The network will be added to the specified data center.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In | The data center into which the network is to be imported. |
6.159.2.1. data_center Copy linkLink copied to clipboard!
The data center into which the network is to be imported. Data center is mandatory, and can be specified using the id or name attributes. The rest of the attributes will be ignored.
If auto_sync is enabled for the provider, the network might be imported automatically. To prevent this, automatic import can be disabled by setting the auto_sync to false, and enabling it again after importing the network.
6.160. OpenstackNetworkProvider Copy linkLink copied to clipboard!
This service manages the OpenStack network provider.
| Name | Summary |
|---|---|
|
| Returns the representation of the object managed by this service. |
|
| Import the SSL certificates of the external host provider. |
|
| Removes the provider. |
|
| In order to test connectivity for external provider we need to run following request where 123 is an id of a provider. |
|
| Updates the provider. |
6.160.1. get GET Copy linkLink copied to clipboard!
Returns the representation of the object managed by this service.
For example, to get the OpenStack network provider with identifier 1234, send a request like this:
GET /ovirt-engine/api/openstacknetworkproviders/1234
GET /ovirt-engine/api/openstacknetworkproviders/1234
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.160.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.160.2. importcertificates POST Copy linkLink copied to clipboard!
Import the SSL certificates of the external host provider.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.160.3. remove DELETE Copy linkLink copied to clipboard!
Removes the provider.
For example, to remove the OpenStack network provider with identifier 1234, send a request like this:
DELETE /ovirt-engine/api/openstacknetworkproviders/1234
DELETE /ovirt-engine/api/openstacknetworkproviders/1234
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.160.4. testconnectivity POST Copy linkLink copied to clipboard!
In order to test connectivity for external provider we need to run following request where 123 is an id of a provider.
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.160.5. update PUT Copy linkLink copied to clipboard!
Updates the provider.
For example, to update provider_name, requires_authentication, url, tenant_name and type properties, for the OpenStack network provider with identifier 1234, send a request like this:
PUT /ovirt-engine/api/openstacknetworkproviders/1234
PUT /ovirt-engine/api/openstacknetworkproviders/1234
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The provider to update. |
6.161. OpenstackNetworkProviders Copy linkLink copied to clipboard!
This service manages OpenStack network providers.
| Name | Summary |
|---|---|
|
| The operation adds a new network provider to the system. |
|
| Returns the list of providers. |
6.161.1. add POST Copy linkLink copied to clipboard!
The operation adds a new network provider to the system. If the type property is not present, a default value of NEUTRON will be used.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.161.2. list GET Copy linkLink copied to clipboard!
Returns the list of providers.
The order of the returned list of providers isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of providers to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned OpenStack network providers. |
6.161.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.161.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.162. OpenstackNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of networks. |
6.162.1. list GET Copy linkLink copied to clipboard!
Returns the list of networks.
The order of the returned list of networks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.162.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.162.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.163. OpenstackSubnet Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.163.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.163.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.163.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.164. OpenstackSubnets Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Returns the list of sub-networks. |
6.164.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.164.2. list GET Copy linkLink copied to clipboard!
Returns the list of sub-networks.
The order of the returned list of sub-networks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of sub-networks to return. | |
|
| Out |
6.164.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.164.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of sub-networks to return. If not specified all the sub-networks are returned.
6.165. OpenstackVolumeAuthenticationKey Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the specified authentication key. |
6.165.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.165.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.165.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.165.3. update PUT Copy linkLink copied to clipboard!
Update the specified authentication key.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.166. OpenstackVolumeAuthenticationKeys Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
| Add a new authentication key to the OpenStack volume provider. |
|
| Returns the list of authentication keys. |
6.166.1. add POST Copy linkLink copied to clipboard!
Add a new authentication key to the OpenStack volume provider.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.166.2. list GET Copy linkLink copied to clipboard!
Returns the list of authentication keys.
The order of the returned list of authentication keys isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of keys to return. |
6.166.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.166.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of keys to return. If not specified all the keys are returned.
6.167. OpenstackVolumeProvider Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
| |
|
| Import the SSL certificates of the external host provider. |
|
| |
|
| In order to test connectivity for external provider we need to run following request where 123 is an id of a provider. |
|
| Update the specified OpenStack volume provider in the system. |
6.167.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.167.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.167.2. importcertificates POST Copy linkLink copied to clipboard!
Import the SSL certificates of the external host provider.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.167.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates if the operation should succeed, and the provider removed from the database, even if something fails during the operation. |
6.167.3.1. force Copy linkLink copied to clipboard!
Indicates if the operation should succeed, and the provider removed from the database, even if something fails during the operation.
This parameter is optional, and the default value is false.
6.167.4. testconnectivity POST Copy linkLink copied to clipboard!
In order to test connectivity for external provider we need to run following request where 123 is an id of a provider.
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
POST /ovirt-engine/api/externalhostproviders/123/testconnectivity
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.167.5. update PUT Copy linkLink copied to clipboard!
Update the specified OpenStack volume provider in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.168. OpenstackVolumeProviders Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
| Adds a new volume provider. |
|
| Retrieves the list of volume providers. |
6.168.1. add POST Copy linkLink copied to clipboard!
Adds a new volume provider.
For example:
POST /ovirt-engine/api/openstackvolumeproviders
POST /ovirt-engine/api/openstackvolumeproviders
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.168.2. list GET Copy linkLink copied to clipboard!
Retrieves the list of volume providers.
The order of the returned list of volume providers isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of providers to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned volume providers. |
6.168.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.168.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.169. OpenstackVolumeType Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
|
6.169.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.169.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.170. OpenstackVolumeTypes Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
| Returns the list of volume types. |
6.170.1. list GET Copy linkLink copied to clipboard!
Returns the list of volume types.
The order of the returned list of volume types isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of volume types to return. | |
|
| Out |
6.170.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.170.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of volume types to return. If not specified all the volume types are returned.
6.171. OperatingSystem Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.171.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.171.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.172. OperatingSystems Copy linkLink copied to clipboard!
Manages the set of types of operating systems available in the system.
| Name | Summary |
|---|---|
|
| Returns the list of types of operating system available in the system. |
6.172.1. list GET Copy linkLink copied to clipboard!
Returns the list of types of operating system available in the system.
The order of the returned list of operating systems isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.172.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.172.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.173. Permission Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.173.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.173.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.173.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.174. Permit Copy linkLink copied to clipboard!
A service to manage a specific permit of the role.
| Name | Summary |
|---|---|
|
| Gets the information about the permit of the role. |
|
| Removes the permit from the role. |
6.174.1. get GET Copy linkLink copied to clipboard!
Gets the information about the permit of the role.
For example to retrieve the information about the permit with the id 456 of the role with the id 123 send a request like this:
GET /ovirt-engine/api/roles/123/permits/456
GET /ovirt-engine/api/roles/123/permits/456
<permit href="/ovirt-engine/api/roles/123/permits/456" id="456"> <name>change_vm_cd</name> <administrative>false</administrative> <role href="/ovirt-engine/api/roles/123" id="123"/> </permit>
<permit href="/ovirt-engine/api/roles/123/permits/456" id="456">
<name>change_vm_cd</name>
<administrative>false</administrative>
<role href="/ovirt-engine/api/roles/123" id="123"/>
</permit>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The permit of the role. |
6.174.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.174.2. remove DELETE Copy linkLink copied to clipboard!
Removes the permit from the role.
For example to remove the permit with id 456 from the role with id 123 send a request like this:
DELETE /ovirt-engine/api/roles/123/permits/456
DELETE /ovirt-engine/api/roles/123/permits/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.175. Permits Copy linkLink copied to clipboard!
Represents a permits sub-collection of the specific role.
| Name | Summary |
|---|---|
|
| Adds a permit to the role. |
|
| List the permits of the role. |
6.175.1. add POST Copy linkLink copied to clipboard!
Adds a permit to the role. The permit name can be retrieved from the cluster_levels service.
For example to assign a permit create_vm to the role with id 123 send a request like this:
POST /ovirt-engine/api/roles/123/permits
POST /ovirt-engine/api/roles/123/permits
With a request body like this:
<permit> <name>create_vm</name> </permit>
<permit>
<name>create_vm</name>
</permit>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The permit to add. |
6.175.2. list GET Copy linkLink copied to clipboard!
List the permits of the role.
For example to list the permits of the role with the id 123 send a request like this:
GET /ovirt-engine/api/roles/123/permits
GET /ovirt-engine/api/roles/123/permits
The order of the returned list of permits isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of permits to return. | |
|
| Out | List of permits. |
6.175.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.175.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of permits to return. If not specified all the permits are returned.
6.176. Qos Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Get specified QoS in the data center. |
|
| Remove specified QoS from datacenter. |
|
| Update the specified QoS in the dataCenter. |
6.176.1. get GET Copy linkLink copied to clipboard!
Get specified QoS in the data center.
GET /ovirt-engine/api/datacenters/123/qoss/123
GET /ovirt-engine/api/datacenters/123/qoss/123
You will get response like this one below:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Queried QoS object. |
6.176.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.176.2. remove DELETE Copy linkLink copied to clipboard!
Remove specified QoS from datacenter.
DELETE /ovirt-engine/api/datacenters/123/qoss/123
DELETE /ovirt-engine/api/datacenters/123/qoss/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.176.3. update PUT Copy linkLink copied to clipboard!
Update the specified QoS in the dataCenter.
PUT /ovirt-engine/api/datacenters/123/qoss/123
PUT /ovirt-engine/api/datacenters/123/qoss/123
For example with curl:
curl -u admin@internal:123456 -X PUT -H "content-type: application/xml" -d \ "<qos><name>321</name><description>321</description><max_iops>10</max_iops></qos>" \ https://engine/ovirt-engine/api/datacenters/123/qoss/123
curl -u admin@internal:123456 -X PUT -H "content-type: application/xml" -d \
"<qos><name>321</name><description>321</description><max_iops>10</max_iops></qos>" \
https://engine/ovirt-engine/api/datacenters/123/qoss/123
You will receive response like this:
6.177. Qoss Copy linkLink copied to clipboard!
Manages the set of quality of service configurations available in a data center.
| Name | Summary |
|---|---|
|
| Add a new QoS to the dataCenter. |
|
| Returns the list of quality of service configurations available in the data center. |
6.177.1. add POST Copy linkLink copied to clipboard!
Add a new QoS to the dataCenter.
POST /ovirt-engine/api/datacenters/123/qoss
POST /ovirt-engine/api/datacenters/123/qoss
The response will look as follows:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Added QoS object. |
6.177.2. list GET Copy linkLink copied to clipboard!
Returns the list of quality of service configurations available in the data center.
GET /ovirt-engine/api/datacenter/123/qoss
GET /ovirt-engine/api/datacenter/123/qoss
You will get response which will look like this:
<qoss> <qos href="/ovirt-engine/api/datacenters/123/qoss/1" id="1">...</qos> <qos href="/ovirt-engine/api/datacenters/123/qoss/2" id="2">...</qos> <qos href="/ovirt-engine/api/datacenters/123/qoss/3" id="3">...</qos> </qoss>
<qoss>
<qos href="/ovirt-engine/api/datacenters/123/qoss/1" id="1">...</qos>
<qos href="/ovirt-engine/api/datacenters/123/qoss/2" id="2">...</qos>
<qos href="/ovirt-engine/api/datacenters/123/qoss/3" id="3">...</qos>
</qoss>
The returned list of quality of service configurations isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of QoS descriptors to return. | |
|
| Qos[] | Out | List of queried QoS objects. |
6.177.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.177.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of QoS descriptors to return. If not specified all the descriptors are returned.
6.178. Quota Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves a quota. |
|
| Delete a quota. |
|
| Updates a quota. |
6.178.1. get GET Copy linkLink copied to clipboard!
Retrieves a quota.
An example of retrieving a quota:
GET /ovirt-engine/api/datacenters/123/quotas/456
GET /ovirt-engine/api/datacenters/123/quotas/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.178.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.178.2. remove DELETE Copy linkLink copied to clipboard!
Delete a quota.
An example of deleting a quota:
DELETE /ovirt-engine/api/datacenters/123-456/quotas/654-321 -0472718ab224 HTTP/1.1 Accept: application/xml Content-type: application/xml
DELETE /ovirt-engine/api/datacenters/123-456/quotas/654-321
-0472718ab224 HTTP/1.1
Accept: application/xml
Content-type: application/xml
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.178.3. update PUT Copy linkLink copied to clipboard!
Updates a quota.
An example of updating a quota:
PUT /ovirt-engine/api/datacenters/123/quotas/456
PUT /ovirt-engine/api/datacenters/123/quotas/456
6.179. QuotaClusterLimit Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.179.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.179.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.179.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.180. QuotaClusterLimits Copy linkLink copied to clipboard!
Manages the set of quota limits configured for a cluster.
| Name | Summary |
|---|---|
|
| Add a cluster limit to a specified Quota. |
|
| Returns the set of quota limits configured for the cluster. |
6.180.1. add POST Copy linkLink copied to clipboard!
Add a cluster limit to a specified Quota.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.180.2. list GET Copy linkLink copied to clipboard!
Returns the set of quota limits configured for the cluster.
The returned list of quota limits isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of limits to return. |
6.180.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.180.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of limits to return. If not specified all the limits are returned.
6.181. QuotaStorageLimit Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.181.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.181.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.181.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. |
6.182. QuotaStorageLimits Copy linkLink copied to clipboard!
Manages the set of storage limits configured for a quota.
| Name | Summary |
|---|---|
|
| Adds a storage limit to a specified quota. |
|
| Returns the list of storage limits configured for the quota. |
6.182.1. add POST Copy linkLink copied to clipboard!
Adds a storage limit to a specified quota.
To create a 100GiB storage limit for all storage domains in a data center, send a request like this:
POST /ovirt-engine/api/datacenters/123/quotas/456/quotastoragelimits
POST /ovirt-engine/api/datacenters/123/quotas/456/quotastoragelimits
With a request body like this:
<quota_storage_limit> <limit>100</limit> </quota_storage_limit>
<quota_storage_limit>
<limit>100</limit>
</quota_storage_limit>
To create a 50GiB storage limit for a storage domain with the ID 000, send a request like this:
POST /ovirt-engine/api/datacenters/123/quotas/456/quotastoragelimits
POST /ovirt-engine/api/datacenters/123/quotas/456/quotastoragelimits
With a request body like this:
<quota_storage_limit> <limit>50</limit> <storage_domain id="000"/> </quota_storage_limit>
<quota_storage_limit>
<limit>50</limit>
<storage_domain id="000"/>
</quota_storage_limit>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.182.2. list GET Copy linkLink copied to clipboard!
Returns the list of storage limits configured for the quota.
The order of the returned list of storage limits is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of limits to return. |
6.182.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.182.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of limits to return. If not specified, all the limits are returned.
6.183. Quotas Copy linkLink copied to clipboard!
Manages the set of quotas configured for a data center.
| Name | Summary |
|---|---|
|
| Creates a new quota. |
|
| Lists quotas of a data center. |
6.183.1. add POST Copy linkLink copied to clipboard!
Creates a new quota.
An example of creating a new quota:
POST /ovirt-engine/api/datacenters/123/quotas
POST /ovirt-engine/api/datacenters/123/quotas
<quota> <name>myquota</name> <description>My new quota for virtual machines</description> </quota>
<quota>
<name>myquota</name>
<description>My new quota for virtual machines</description>
</quota>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.183.2. list GET Copy linkLink copied to clipboard!
Lists quotas of a data center.
The order of the returned list of quotas isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of quota descriptors to return. | |
|
| Out |
6.183.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.183.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of quota descriptors to return. If not specified all the descriptors are returned.
6.184. Role Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Get the role. |
|
| Removes the role. |
|
| Updates a role. |
6.184.1. get GET Copy linkLink copied to clipboard!
Get the role.
GET /ovirt-engine/api/roles/123
GET /ovirt-engine/api/roles/123
You will receive XML response like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieved role. |
6.184.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.184.2. remove DELETE Copy linkLink copied to clipboard!
Removes the role.
To remove the role you need to know its id, then send request like this:
DELETE /ovirt-engine/api/roles/{role_id}
DELETE /ovirt-engine/api/roles/{role_id}
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.184.3. update PUT Copy linkLink copied to clipboard!
Updates a role. You are allowed to update name, description and administrative attributes after role is created. Within this endpoint you can’t add or remove roles permits you need to use service that manages permits of role.
For example to update role’s name, description and administrative attributes send a request like this:
PUT /ovirt-engine/api/roles/123
PUT /ovirt-engine/api/roles/123
With a request body like this:
<role> <name>MyNewRoleName</name> <description>My new description of the role</description> <administrative>true</administrative> </group>
<role>
<name>MyNewRoleName</name>
<description>My new description of the role</description>
<administrative>true</administrative>
</group>
6.185. Roles Copy linkLink copied to clipboard!
Provides read-only access to the global set of roles
| Name | Summary |
|---|---|
|
| Create a new role. |
|
| List roles. |
6.185.1. add POST Copy linkLink copied to clipboard!
Create a new role. The role can be administrative or non-administrative and can have different permits.
For example, to add the MyRole non-administrative role with permits to login and create virtual machines send a request like this (note that you have to pass permit id):
POST /ovirt-engine/api/roles
POST /ovirt-engine/api/roles
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Role that will be added. |
6.185.2. list GET Copy linkLink copied to clipboard!
List roles.
GET /ovirt-engine/api/roles
GET /ovirt-engine/api/roles
You will receive response in XML like this one:
The order of the returned list of roles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of roles to return. | |
|
| Out | Retrieved list of roles. |
6.185.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.185.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of roles to return. If not specified all the roles are returned.
6.186. SchedulingPolicies Copy linkLink copied to clipboard!
Manages the set of scheduling policies available in the system.
| Name | Summary |
|---|---|
|
| Add a new scheduling policy to the system. |
|
| Returns the list of scheduling policies available in the system. |
6.186.1. add POST Copy linkLink copied to clipboard!
Add a new scheduling policy to the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.186.2. list GET Copy linkLink copied to clipboard!
Returns the list of scheduling policies available in the system.
The order of the returned list of scheduling policies isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of policies to return. | |
|
| Out |
6.186.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.186.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of policies to return. If not specified all the policies are returned.
6.187. SchedulingPolicy Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the specified user defined scheduling policy in the system. |
6.187.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.187.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.187.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.187.3. update PUT Copy linkLink copied to clipboard!
Update the specified user defined scheduling policy in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.188. SchedulingPolicyUnit Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.188.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.188.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.188.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.189. SchedulingPolicyUnits Copy linkLink copied to clipboard!
Manages the set of scheduling policy units available in the system.
| Name | Summary |
|---|---|
|
| Returns the list of scheduling policy units available in the system. |
6.189.1. list GET Copy linkLink copied to clipboard!
Returns the list of scheduling policy units available in the system.
The order of the returned list of scheduling policy units isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of policy units to return. | |
|
| Out |
6.189.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.189.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of policy units to return. If not specified all the policy units are returned.
6.190. Snapshot Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Restores a virtual machine snapshot. |
6.190.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.190.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.190.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all the attributes of the virtual machine snapshot should be included in the response. | |
|
| In | Indicates if the remove should be performed asynchronously. |
6.190.2.1. all_content Copy linkLink copied to clipboard!
Indicates if all the attributes of the virtual machine snapshot should be included in the response.
By default the attribute initialization.configuration.data is excluded.
For example, to retrieve the complete representation of the snapshot with id 456 of the virtual machine with id 123 send a request like this:
GET /ovirt-engine/api/vms/123/snapshots/456?all_content=true
GET /ovirt-engine/api/vms/123/snapshots/456?all_content=true
6.190.3. restore POST Copy linkLink copied to clipboard!
Restores a virtual machine snapshot.
For example, to restore the snapshot with identifier 456 of virtual machine with identifier 123 send a request like this:
POST /ovirt-engine/api/vms/123/snapshots/456/restore
POST /ovirt-engine/api/vms/123/snapshots/456/restore
With an empty action in the body:
<action/>
<action/>
Confirm that the commit operation is finished and the virtual machine is down before running the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the restore should be performed asynchronously. | |
|
| In | Specify the disks included in the snapshot’s restore. | |
|
| In |
6.190.3.1. disks Copy linkLink copied to clipboard!
Specify the disks included in the snapshot’s restore.
For each disk parameter, it is also required to specify its image_id.
For example, to restore a snapshot with an identifier 456 of a virtual machine with identifier 123, including a disk with identifier 111 and image_id of 222, send a request like this:
POST /ovirt-engine/api/vms/123/snapshots/456/restore
POST /ovirt-engine/api/vms/123/snapshots/456/restore
Request body:
6.191. SnapshotCdrom Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.191.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.191.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.192. SnapshotCdroms Copy linkLink copied to clipboard!
Manages the set of CD-ROM devices of a virtual machine snapshot.
| Name | Summary |
|---|---|
|
| Returns the list of CD-ROM devices of the snapshot. |
6.192.1. list GET Copy linkLink copied to clipboard!
Returns the list of CD-ROM devices of the snapshot.
The order of the returned list of CD-ROM devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of CDROMS to return. |
6.192.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.192.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of CDROMS to return. If not specified all the CDROMS are returned.
6.193. SnapshotDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.193.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.193.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.194. SnapshotDisks Copy linkLink copied to clipboard!
Manages the set of disks of an snapshot.
| Name | Summary |
|---|---|
|
| Returns the list of disks of the snapshot. |
6.194.1. list GET Copy linkLink copied to clipboard!
Returns the list of disks of the snapshot.
The order of the returned list of disks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. |
6.194.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.194.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.195. SnapshotNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.195.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.195.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.196. SnapshotNics Copy linkLink copied to clipboard!
Manages the set of NICs of an snapshot.
| Name | Summary |
|---|---|
|
| Returns the list of NICs of the snapshot. |
6.196.1. list GET Copy linkLink copied to clipboard!
Returns the list of NICs of the snapshot.
The order of the returned list of NICs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of NICs to return. | |
|
| Nic[] | Out |
6.196.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.196.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.197. Snapshots Copy linkLink copied to clipboard!
Manages the set of snapshots of a storage domain or virtual machine.
| Name | Summary |
|---|---|
|
| Creates a virtual machine snapshot. |
|
| Returns the list of snapshots of the storage domain or virtual machine. |
6.197.1. add POST Copy linkLink copied to clipboard!
Creates a virtual machine snapshot.
For example, to create a new snapshot for virtual machine 123 send a request like this:
POST /ovirt-engine/api/vms/123/snapshots
POST /ovirt-engine/api/vms/123/snapshots
With a request body like this:
<snapshot> <description>My snapshot</description> </snapshot>
<snapshot>
<description>My snapshot</description>
</snapshot>
For including only a sub-set of disks in the snapshots, add disk_attachments element to the request body. Note that disks which are not specified in disk_attachments element will not be a part of the snapshot. If an empty disk_attachments element is passed, the snapshot will include only the virtual machine configuration. If no disk_attachments element is passed, then all the disks will be included in the snapshot.
For each disk, image_id element can be specified for setting the new active image id. This is used in order to restore a chain of images from backup. I.e. when restoring a disk with snapshots, the relevant image_id should be specified for each snapshot (so the identifiers of the disk snapshots are identical to the backup).
When a snapshot is created, the default value for the persist_memorystate attribute is true. That means that the content of the memory of the virtual machine will be included in the snapshot, and it also means that the virtual machine will be paused for a longer time. That can negatively affect applications that are very sensitive to timing (NTP servers, for example). In those cases make sure that you set the attribute to false:
<snapshot> <description>My snapshot</description> <persist_memorystate>false</persist_memorystate> </snapshot>
<snapshot>
<description>My snapshot</description>
<persist_memorystate>false</persist_memorystate>
</snapshot>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.197.2. list GET Copy linkLink copied to clipboard!
Returns the list of snapshots of the storage domain or virtual machine.
The order of the returned list of snapshots isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all the attributes of the virtual machine snapshot should be included in the response. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of snapshots to return. | |
|
| Out |
6.197.2.1. all_content Copy linkLink copied to clipboard!
Indicates if all the attributes of the virtual machine snapshot should be included in the response.
By default the attribute initialization.configuration.data is excluded.
For example, to retrieve the complete representation of the virtual machine with id 123 snapshots send a request like this:
GET /ovirt-engine/api/vms/123/snapshots?all_content=true
GET /ovirt-engine/api/vms/123/snapshots?all_content=true
6.197.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.197.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of snapshots to return. If not specified all the snapshots are returned.
6.198. SshPublicKey Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Replaces the key with a new resource. |
6.198.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.198.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.198.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.198.3. update PUT Copy linkLink copied to clipboard!
Replaces the key with a new resource.
Since version 4.4.8 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. Instead please use DELETE followed by add operation.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.199. SshPublicKeys Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Returns a list of SSH public keys of the user. |
6.199.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.199.2. list GET Copy linkLink copied to clipboard!
Returns a list of SSH public keys of the user.
For example, to retrieve the list of SSH keys of user with identifier 123, send a request like this:
GET /ovirt-engine/api/users/123/sshpublickeys
GET /ovirt-engine/api/users/123/sshpublickeys
The result will be the following XML document:
Or the following JSON object
The order of the returned list of keys is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | ||
|
| In | Sets the maximum number of keys to return. |
6.199.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.199.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of keys to return. If not specified all the keys are returned.
6.200. Statistic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.200.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.200.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.201. Statistics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves a list of statistics. |
6.201.1. list GET Copy linkLink copied to clipboard!
Retrieves a list of statistics.
For example, to retrieve the statistics for virtual machine 123 send a request like this:
GET /ovirt-engine/api/vms/123/statistics
GET /ovirt-engine/api/vms/123/statistics
The result will be like this:
Just a single part of the statistics can be retrieved by specifying its id at the end of the URI. That means:
GET /ovirt-engine/api/vms/123/statistics/456
GET /ovirt-engine/api/vms/123/statistics/456
Outputs:
The order of the returned list of statistics isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of statistics to return. | |
|
| Out |
6.201.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.201.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of statistics to return. If not specified all the statistics are returned.
6.202. Step Copy linkLink copied to clipboard!
A service to manage a step.
| Name | Summary |
|---|---|
|
| Marks an external step execution as ended. |
|
| Retrieves a step. |
6.202.1. end POST Copy linkLink copied to clipboard!
Marks an external step execution as ended.
For example, to terminate a step with identifier 456 which belongs to a job with identifier 123 send the following request:
POST /ovirt-engine/api/jobs/123/steps/456/end
POST /ovirt-engine/api/jobs/123/steps/456/end
With the following request body:
<action> <force>true</force> <succeeded>true</succeeded> </action>
<action>
<force>true</force>
<succeeded>true</succeeded>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Indicates if the step should be forcibly terminated. | |
|
| In | Indicates if the step should be marked as successfully finished or as failed. |
6.202.1.1. succeeded Copy linkLink copied to clipboard!
Indicates if the step should be marked as successfully finished or as failed.
This parameter is optional, and the default value is true.
6.202.2. get GET Copy linkLink copied to clipboard!
Retrieves a step.
GET /ovirt-engine/api/jobs/123/steps/456
GET /ovirt-engine/api/jobs/123/steps/456
You will receive response in XML like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieves the representation of the step. |
6.202.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.203. Steps Copy linkLink copied to clipboard!
A service to manage steps.
| Name | Summary |
|---|---|
|
| Add an external step to an existing job or to an existing step. |
|
| Retrieves the representation of the steps. |
6.203.1. add POST Copy linkLink copied to clipboard!
Add an external step to an existing job or to an existing step.
For example, to add a step to job with identifier 123 send the following request:
POST /ovirt-engine/api/jobs/123/steps
POST /ovirt-engine/api/jobs/123/steps
With the following request body:
The response should look like:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Step that will be added. |
6.203.2. list GET Copy linkLink copied to clipboard!
Retrieves the representation of the steps.
GET /ovirt-engine/api/job/123/steps
GET /ovirt-engine/api/job/123/steps
You will receive response in XML like this one:
The order of the returned list of steps isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of steps to return. | |
|
| Out | A representation of steps. |
6.203.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.203.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of steps to return. If not specified all the steps are returned.
6.204. Storage Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.204.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Indicates if the status of the LUNs in the storage should be checked. | |
|
| Out |
6.204.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.204.1.2. report_status Copy linkLink copied to clipboard!
Indicates if the status of the LUNs in the storage should be checked. Checking the status of the LUN is an heavy weight operation and this data is not always needed by the user. This parameter will give the option to not perform the status check of the LUNs.
The default is true for backward compatibility.
Here an example with the LUN status :
Here an example without the LUN status :
6.205. StorageDomain Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves the description of the storage domain. |
|
| Used for querying if the storage domain is already attached to a data center using the is_attached boolean field, which is part of the storage server. |
|
| This operation reduces logical units from the storage domain. |
|
| This operation refreshes the LUN size. |
|
| Removes the storage domain. |
|
| Updates a storage domain. |
|
|
This operation forces the update of the |
6.205.1. get GET Copy linkLink copied to clipboard!
Retrieves the description of the storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | The description of the storage domain. |
6.205.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.205.2. isattached POST Copy linkLink copied to clipboard!
Used for querying if the storage domain is already attached to a data center using the is_attached boolean field, which is part of the storage server. IMPORTANT: Executing this API will cause the host to disconnect from the storage domain.
6.205.3. reduceluns POST Copy linkLink copied to clipboard!
This operation reduces logical units from the storage domain.
In order to do so the data stored on the provided logical units will be moved to other logical units of the storage domain and only then they will be reduced from the storage domain.
For example, in order to reduce two logical units from a storage domain send a request like this:
POST /ovirt-engine/api/storageDomains/123/reduceluns
POST /ovirt-engine/api/storageDomains/123/reduceluns
With a request body like this:
Note that this operation is only applicable to block storage domains (i.e., storage domains with the xref:types-storage_type[storage type] of iSCSI or FCP).
Note that this operation is only applicable to block storage domains (i.e., storage domains with the
xref:types-storage_type[storage type] of iSCSI or FCP).
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | The logical units that need to be reduced from the storage domain. |
6.205.4. refreshluns POST Copy linkLink copied to clipboard!
This operation refreshes the LUN size.
After increasing the size of the underlying LUN on the storage server, the user can refresh the LUN size. This action forces a rescan of the provided LUNs and updates the database with the new size, if required.
For example, in order to refresh the size of two LUNs send a request like this:
POST /ovirt-engine/api/storageDomains/262b056b-aede-40f1-9666-b883eff59d40/refreshluns
POST /ovirt-engine/api/storageDomains/262b056b-aede-40f1-9666-b883eff59d40/refreshluns
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the refresh should be performed asynchronously. | |
|
| In | The LUNs that need to be refreshed. |
6.205.5. remove DELETE Copy linkLink copied to clipboard!
Removes the storage domain.
Without any special parameters, the storage domain is detached from the system and removed from the database. The storage domain can then be imported to the same or to a different setup, with all the data on it. If the storage is not accessible the operation will fail.
If the destroy parameter is true then the operation will always succeed, even if the storage is not accessible, the failure is just ignored and the storage domain is removed from the database anyway.
If the format parameter is true then the actual storage is formatted, and the metadata is removed from the LUN or directory, so it can no longer be imported to the same or to a different setup.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates if the operation should succeed, and the storage domain removed from the database, even if the storage is not accessible. | |
|
| In | Indicates if the actual storage should be formatted, removing all the metadata from the underlying LUN or directory: [source] ---- DELETE /ovirt-engine/api/storageDomains/123?format=true ----
This parameter is optional, and the default value is | |
|
| In | Indicates which host should be used to remove the storage domain. |
6.205.5.1. destroy Copy linkLink copied to clipboard!
Indicates if the operation should succeed, and the storage domain removed from the database, even if the storage is not accessible.
DELETE /ovirt-engine/api/storageDomains/123?destroy=true
DELETE /ovirt-engine/api/storageDomains/123?destroy=true
This parameter is optional, and the default value is false. When the value of destroy is true the host parameter will be ignored.
6.205.5.2. host Copy linkLink copied to clipboard!
Indicates which host should be used to remove the storage domain.
This parameter is mandatory, except if the destroy parameter is included and its value is true, in that case the host parameter will be ignored.
The value should contain the name or the identifier of the host. For example, to use the host named myhost to remove the storage domain with identifier 123 send a request like this:
DELETE /ovirt-engine/api/storageDomains/123?host=myhost
DELETE /ovirt-engine/api/storageDomains/123?host=myhost
6.205.6. update PUT Copy linkLink copied to clipboard!
Updates a storage domain.
Not all of the StorageDomain's attributes are updatable after creation. Those that can be updated are: name, description, comment, warning_low_space_indicator, critical_space_action_blocker and wipe_after_delete. (Note that changing the wipe_after_delete attribute will not change the wipe after delete property of disks that already exist).
To update the name and wipe_after_delete attributes of a storage domain with an identifier 123, send a request as follows:
PUT /ovirt-engine/api/storageDomains/123
PUT /ovirt-engine/api/storageDomains/123
With a request body as follows:
<storage_domain> <name>data2</name> <wipe_after_delete>true</wipe_after_delete> </storage_domain>
<storage_domain>
<name>data2</name>
<wipe_after_delete>true</wipe_after_delete>
</storage_domain>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The updated storage domain. |
6.205.7. updateovfstore POST Copy linkLink copied to clipboard!
This operation forces the update of the OVF_STORE of this storage domain.
The OVF_STORE is a disk image that contains the metadata of virtual machines and disks that reside in the storage domain. This metadata is used in case the domain is imported or exported to or from a different data center or a different installation.
By default the OVF_STORE is updated periodically (set by default to 60 minutes) but users might want to force an update after an important change, or when the they believe the OVF_STORE is corrupt.
When initiated by the user, OVF_STORE update will be performed whether an update is needed or not.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the |
6.206. StorageDomainContentDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.206.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. |
6.206.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.207. StorageDomainContentDisks Copy linkLink copied to clipboard!
Manages the set of disks available in a storage domain.
| Name | Summary |
|---|---|
|
| Returns the list of disks available in the storage domain. |
6.207.1. list GET Copy linkLink copied to clipboard!
Returns the list of disks available in the storage domain.
The order of the returned list of disks is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. | |
|
| In | A query string used to restrict the returned disks. |
6.207.1.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.207.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.207.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.208. StorageDomainDisk Copy linkLink copied to clipboard!
Manages a single disk available in a storage domain.
Since version 4.2 of the engine this service is intended only to list disks available in the storage domain, and to register unregistered disks. All the other operations, like copying a disk, moving a disk, etc, have been deprecated and will be removed in the future. To perform those operations use the service that manages all the disks of the system or the service that manages a specific disk.
| Name | Summary |
|---|---|
|
| Copies a disk to the specified storage domain. |
|
| Exports a disk to an export storage domain. |
|
| Retrieves the description of the disk. |
|
| Moves a disk to another storage domain. |
|
| Reduces the size of the disk image. |
|
| Removes a disk. |
|
| Sparsify the disk. |
|
| Updates the disk. |
6.208.1. copy POST Copy linkLink copied to clipboard!
Copies a disk to the specified storage domain.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To copy a disk use the copy operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Description of the resulting disk. | |
|
| In | The storage domain where the new disk will be created. |
6.208.2. export POST Copy linkLink copied to clipboard!
Exports a disk to an export storage domain.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To export a disk use the export operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | The export storage domain where the disk should be exported to. |
6.208.3. get GET Copy linkLink copied to clipboard!
Retrieves the description of the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The description of the disk. | |
|
| In | Indicates which inner links should be followed. |
6.208.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.208.4. move POST Copy linkLink copied to clipboard!
Moves a disk to another storage domain.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To move a disk use the move operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the move should be performed asynchronously. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | The storage domain where the disk will be moved to. |
6.208.5. reduce POST Copy linkLink copied to clipboard!
Reduces the size of the disk image.
Invokes reduce on the logical volume (i.e. this is only applicable for block storage domains). This is applicable for floating disks and disks attached to non-running virtual machines. There is no need to specify the size as the optimal size is calculated automatically.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.208.6. remove DELETE Copy linkLink copied to clipboard!
Removes a disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To remove a disk use the remove operation of the service that manages that disk.
6.208.7. sparsify POST Copy linkLink copied to clipboard!
Sparsify the disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To remove a disk use the remove operation of the service that manages that disk.
6.208.8. update PUT Copy linkLink copied to clipboard!
Updates the disk.
Since version 4.2 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To update a disk use the update operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The update to apply to the disk. |
6.209. StorageDomainDisks Copy linkLink copied to clipboard!
Manages the collection of disks available inside a specific storage domain.
| Name | Summary |
|---|---|
|
| Adds or registers a disk. |
|
| Retrieves the list of disks that are available in the storage domain. |
6.209.1. add POST Copy linkLink copied to clipboard!
Adds or registers a disk.
Since version 4.2 of the Red Hat Virtualization Manager this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. To add a new disk use the add operation of the service that manages the disks of the system. To register an unregistered disk use the register operation of the service that manages that disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The disk to add or register. | |
|
| In | Indicates if a new disk should be added or if an existing unregistered disk should be registered. |
6.209.1.1. unregistered Copy linkLink copied to clipboard!
Indicates if a new disk should be added or if an existing unregistered disk should be registered. If the value is true then the identifier of the disk to register needs to be provided. For example, to register the disk with ID 456 send a request like this:
POST /ovirt-engine/api/storagedomains/123/disks?unregistered=true
POST /ovirt-engine/api/storagedomains/123/disks?unregistered=true
With a request body like this:
<disk id="456"/>
<disk id="456"/>
If the value is false then a new disk will be created in the storage domain. In that case the provisioned_size, format, and name attributes are mandatory. For example, to create a new copy on write disk of 1 GiB, send a request like this:
POST /ovirt-engine/api/storagedomains/123/disks
POST /ovirt-engine/api/storagedomains/123/disks
With a request body like this:
<disk> <name>mydisk</name> <format>cow</format> <provisioned_size>1073741824</provisioned_size> </disk>
<disk>
<name>mydisk</name>
<format>cow</format>
<provisioned_size>1073741824</provisioned_size>
</disk>
The default value is false.
This parameter has been deprecated since version 4.2 of the Red Hat Virtualization Manager.
6.209.2. list GET Copy linkLink copied to clipboard!
Retrieves the list of disks that are available in the storage domain.
The order of the returned list of disks is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of retrieved disks. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. | |
|
| In | Indicates whether to retrieve a list of registered or unregistered disks in the storage domain. |
6.209.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.209.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified, all the disks are returned.
6.209.2.3. unregistered Copy linkLink copied to clipboard!
Indicates whether to retrieve a list of registered or unregistered disks in the storage domain. To get a list of unregistered disks in the storage domain the call should indicate the unregistered flag. For example, to get a list of unregistered disks the REST API call should look like this:
GET /ovirt-engine/api/storagedomains/123/disks?unregistered=true
GET /ovirt-engine/api/storagedomains/123/disks?unregistered=true
The default value of the unregistered flag is false. The request only applies to storage domains that are attached.
6.210. StorageDomainServerConnection Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Detaches a storage connection from storage. |
6.210.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.210.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.210.2. remove DELETE Copy linkLink copied to clipboard!
Detaches a storage connection from storage.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.211. StorageDomainServerConnections Copy linkLink copied to clipboard!
Manages the set of connections to storage servers that exist in a storage domain.
| Name | Summary |
|---|---|
|
| |
|
| Returns the list of connections to storage servers that existin the storage domain. |
6.211.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.211.2. list GET Copy linkLink copied to clipboard!
Returns the list of connections to storage servers that existin the storage domain.
The order of the returned list of connections isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of connections to return. |
6.211.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.211.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of connections to return. If not specified all the connections are returned.
6.212. StorageDomainTemplate Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Action to import a template from an export storage domain. |
|
| Register the Template means importing the Template from the data domain by inserting the configuration of the Template and disks into the database without the copy process. |
|
|
6.212.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.212.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.212.2. import POST Copy linkLink copied to clipboard!
Action to import a template from an export storage domain.
For example, to import the template 456 from the storage domain 123 send the following request:
POST /ovirt-engine/api/storagedomains/123/templates/456/import
POST /ovirt-engine/api/storagedomains/123/templates/456/import
With the following request body:
If you register an entity without specifying the cluster ID or name, the cluster name from the entity’s OVF will be used (unless the register request also includes the cluster mapping).
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In |
Use the optional | |
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In |
6.212.2.1. clone Copy linkLink copied to clipboard!
Use the optional clone parameter to generate new UUIDs for the imported template and its entities.
You can import a template with the clone parameter set to false when importing a template from an export domain, with templates that were exported by a different Red Hat Virtualization environment.
6.212.3. register POST Copy linkLink copied to clipboard!
Register the Template means importing the Template from the data domain by inserting the configuration of the Template and disks into the database without the copy process.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates whether a template is allowed to be registered with only some of its disks. | |
|
| In | Indicates if the registration should be performed asynchronously. | |
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | This parameter describes how the template should be registered. | |
|
| In | ||
|
| In | Deprecated attribute describing mapping rules for virtual NIC profiles that will be applied during the import\register process. |
6.212.3.1. allow_partial_import Copy linkLink copied to clipboard!
Indicates whether a template is allowed to be registered with only some of its disks.
If this flag is true, the system will not fail in the validation process if an image is not found, but instead it will allow the template to be registered without the missing disks. This is mainly used during registration of a template when some of the storage domains are not available. The default value is false.
6.212.3.2. registration_configuration Copy linkLink copied to clipboard!
This parameter describes how the template should be registered.
This parameter is optional. If the parameter is not specified, the template will be registered with the same configuration that it had in the original environment where it was created.
6.212.3.3. vnic_profile_mappings Copy linkLink copied to clipboard!
Deprecated attribute describing mapping rules for virtual NIC profiles that will be applied during the import\register process.
Please note that this attribute has been deprecated since version 4.2.1 of the engine, and preserved only for backward compatibility. It will be removed in the future. To specify vnic_profile_mappings use the vnic_profile_mappings attribute inside the RegistrationConfiguration type.
6.212.4. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.213. StorageDomainTemplates Copy linkLink copied to clipboard!
Manages the set of templates available in a storage domain.
| Name | Summary |
|---|---|
|
| Returns the list of templates availalbe in the storage domain. |
6.213.1. list GET Copy linkLink copied to clipboard!
Returns the list of templates availalbe in the storage domain.
The order of the returned list of templates isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of templates to return. | |
|
| Out | ||
|
| In | Indicates whether to retrieve a list of registered or unregistered templates which contain disks on the storage domain. |
6.213.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.213.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of templates to return. If not specified all the templates are returned.
6.213.1.3. unregistered Copy linkLink copied to clipboard!
Indicates whether to retrieve a list of registered or unregistered templates which contain disks on the storage domain. To get a list of unregistered templates the call should indicate the unregistered flag. For example, to get a list of unregistered templates the REST API call should look like this:
GET /ovirt-engine/api/storagedomains/123/templates?unregistered=true
GET /ovirt-engine/api/storagedomains/123/templates?unregistered=true
The default value of the unregisterd flag is false. The request only apply to storage domains that are attached.
6.214. StorageDomainVm Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Imports a virtual machine from an export storage domain. |
|
| |
|
| Deletes a virtual machine from an export storage domain. |
6.214.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.214.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.214.2. import POST Copy linkLink copied to clipboard!
Imports a virtual machine from an export storage domain.
For example, send a request like this:
POST /ovirt-engine/api/storagedomains/123/vms/456/import
POST /ovirt-engine/api/storagedomains/123/vms/456/import
With a request body like this:
To import a virtual machine as a new entity add the clone parameter:
Include an optional disks parameter to choose which disks to import. For example, to import the disks of the template that have the identifiers 123 and 456 send the following request body:
If you register an entity without specifying the cluster ID or name, the cluster name from the entity’s OVF will be used (unless the register request also includes the cluster mapping).
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In | Indicates if the identifiers of the imported virtual machine should be regenerated. | |
|
| In | ||
|
| In | Indicates of the snapshots of the virtual machine that is imported should be collapsed, so that the result will be a virtual machine without snapshots. | |
|
| In | ||
|
| In | ||
|
| In |
6.214.2.1. clone Copy linkLink copied to clipboard!
Indicates if the identifiers of the imported virtual machine should be regenerated.
By default when a virtual machine is imported the identifiers are preserved. This means that the same virtual machine can’t be imported multiple times, as that identifiers needs to be unique. To allow importing the same machine multiple times set this parameter to true, as the default is false.
6.214.2.2. collapse_snapshots Copy linkLink copied to clipboard!
Indicates of the snapshots of the virtual machine that is imported should be collapsed, so that the result will be a virtual machine without snapshots.
This parameter is optional, and if it isn’t explicitly specified the default value is false.
6.214.3. register POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates whether a virtual machine is allowed to be registered with only some of its disks. | |
|
| In | Indicates if the registration should be performed asynchronously. | |
|
| In | ||
|
| In | ||
|
| In | Indicates if the problematic MAC addresses should be re-assigned during the import process by the engine. | |
|
| In | This parameter describes how the virtual machine should be registered. | |
|
| In | ||
|
| In | Deprecated attribute describing mapping rules for virtual NIC profiles that will be applied during the import\register process. |
6.214.3.1. allow_partial_import Copy linkLink copied to clipboard!
Indicates whether a virtual machine is allowed to be registered with only some of its disks.
If this flag is true, the engine will not fail in the validation process if an image is not found, but instead it will allow the virtual machine to be registered without the missing disks. This is mainly used during registration of a virtual machine when some of the storage domains are not available. The default value is false.
6.214.3.2. reassign_bad_macs Copy linkLink copied to clipboard!
Indicates if the problematic MAC addresses should be re-assigned during the import process by the engine.
A MAC address would be considered as a problematic one if one of the following is true:
- It conflicts with a MAC address that is already allocated to a virtual machine in the target environment.
- It’s out of the range of the target MAC address pool.
6.214.3.3. registration_configuration Copy linkLink copied to clipboard!
This parameter describes how the virtual machine should be registered.
This parameter is optional. If the parameter is not specified, the virtual machine will be registered with the same configuration that it had in the original environment where it was created.
6.214.3.4. vnic_profile_mappings Copy linkLink copied to clipboard!
Deprecated attribute describing mapping rules for virtual NIC profiles that will be applied during the import\register process.
Please note that this attribute has been deprecated since version 4.2.1 of the engine, and preserved only for backward compatibility. It will be removed in the future. To specify vnic_profile_mappings use the vnic_profile_mappings attribute inside the RegistrationConfiguration type.
6.214.4. remove DELETE Copy linkLink copied to clipboard!
Deletes a virtual machine from an export storage domain.
For example, to delete the virtual machine 456 from the storage domain 123, send a request like this:
DELETE /ovirt-engine/api/storagedomains/123/vms/456
DELETE /ovirt-engine/api/storagedomains/123/vms/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.215. StorageDomainVmDiskAttachment Copy linkLink copied to clipboard!
Returns the details of the disks attached to a virtual machine in the export domain.
| Name | Summary |
|---|---|
|
| Returns the details of the attachment with all its properties and a link to the disk. |
6.215.1. get GET Copy linkLink copied to clipboard!
Returns the details of the attachment with all its properties and a link to the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The disk attachment. | |
|
| In | Indicates which inner links should be followed. |
6.215.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.216. StorageDomainVmDiskAttachments Copy linkLink copied to clipboard!
Returns the details of a disk attached to a virtual machine in the export domain.
| Name | Summary |
|---|---|
|
| List the disks that are attached to the virtual machine. |
6.216.1. list GET Copy linkLink copied to clipboard!
List the disks that are attached to the virtual machine.
The order of the returned list of disk attachments isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.216.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.217. StorageDomainVms Copy linkLink copied to clipboard!
Lists the virtual machines of an export storage domain.
For example, to retrieve the virtual machines that are available in the storage domain with identifier 123 send the following request:
GET /ovirt-engine/api/storagedomains/123/vms
GET /ovirt-engine/api/storagedomains/123/vms
This will return the following response body:
Virtual machines and templates in these collections have a similar representation to their counterparts in the top-level Vm and Template collections, except they also contain a StorageDomain reference and an import action.
| Name | Summary |
|---|---|
|
| Returns the list of virtual machines of the export storage domain. |
6.217.1. list GET Copy linkLink copied to clipboard!
Returns the list of virtual machines of the export storage domain.
The order of the returned list of virtual machines isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of virtual machines to return. | |
|
| In | Indicates whether to retrieve a list of registered or unregistered virtual machines which contain disks on the storage domain. | |
|
| Vm[] | Out |
6.217.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.217.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machines to return. If not specified all the virtual machines are returned.
6.217.1.3. unregistered Copy linkLink copied to clipboard!
Indicates whether to retrieve a list of registered or unregistered virtual machines which contain disks on the storage domain. To get a list of unregistered virtual machines the call should indicate the unregistered flag. For example, to get a list of unregistered virtual machines the REST API call should look like this:
GET /ovirt-engine/api/storagedomains/123/vms?unregistered=true
GET /ovirt-engine/api/storagedomains/123/vms?unregistered=true
The default value of the unregisterd flag is false. The request only apply to storage domains that are attached.
6.218. StorageDomains Copy linkLink copied to clipboard!
Manages the set of storage domains in the system.
| Name | Summary |
|---|---|
|
| Adds a new storage domain. |
|
| Returns the list of storage domains in the system. |
6.218.1. add POST Copy linkLink copied to clipboard!
Adds a new storage domain.
Creation of a new StorageDomain requires the name, type, host, and storage attributes. Identify the host attribute with the id or name attributes. In Red Hat Virtualization 3.6 and later you can enable the wipe after delete option by default on the storage domain. To configure this, specify wipe_after_delete in the POST request. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
To add a new storage domain with specified name, type, storage.type, storage.address, and storage.path, and using a host with an id 123, send a request like this:
POST /ovirt-engine/api/storageDomains
POST /ovirt-engine/api/storageDomains
With a request body like this:
To create a new NFS ISO storage domain send a request like this:
To create a new iSCSI storage domain send a request like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The storage domain to add. |
6.218.2. list GET Copy linkLink copied to clipboard!
Returns the list of storage domains in the system.
The order of the returned list of storage domains is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the search should be performed taking case into account. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of storage domains to return. | |
|
| In | A query string used to restrict the returned storage domains. | |
|
| Out | A list of the storage domains in the system. |
6.218.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case, set it to false.
6.218.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.218.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of storage domains to return. If not specified, all the storage domains are returned.
6.219. StorageServerConnection Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a storage connection. |
|
| Updates the storage connection. |
6.219.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.219.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.219.2. remove DELETE Copy linkLink copied to clipboard!
Removes a storage connection.
A storage connection can only be deleted if neither storage domain nor LUN disks reference it. The host name or id is optional; providing it disconnects (unmounts) the connection from that host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | The name or identifier of the host from which the connection would be unmounted (disconnected). |
6.219.2.1. host Copy linkLink copied to clipboard!
The name or identifier of the host from which the connection would be unmounted (disconnected). If not provided, no host will be disconnected.
For example, to use the host with identifier 456 to delete the storage connection with identifier 123 send a request like this:
DELETE /ovirt-engine/api/storageconnections/123?host=456
DELETE /ovirt-engine/api/storageconnections/123?host=456
6.219.3. update PUT Copy linkLink copied to clipboard!
Updates the storage connection.
For example, to change the address of an NFS storage server, send a request like this:
PUT /ovirt-engine/api/storageconnections/123
PUT /ovirt-engine/api/storageconnections/123
With a request body like this:
<storage_connection> <address>mynewnfs.example.com</address> </storage_connection>
<storage_connection>
<address>mynewnfs.example.com</address>
</storage_connection>
To change the connection of an iSCSI storage server, send a request like this:
PUT /ovirt-engine/api/storageconnections/123
PUT /ovirt-engine/api/storageconnections/123
With a request body like this:
<storage_connection> <port>3260</port> <target>iqn.2017-01.com.myhost:444</target> </storage_connection>
<storage_connection>
<port>3260</port>
<target>iqn.2017-01.com.myhost:444</target>
</storage_connection>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | ||
|
| In | Indicates if the operation should succeed regardless to the relevant storage domain’s status (i. |
6.219.3.1. force Copy linkLink copied to clipboard!
Indicates if the operation should succeed regardless to the relevant storage domain’s status (i.e. updating is also applicable when storage domain’s status is not maintenance).
This parameter is optional, and the default value is false.
6.220. StorageServerConnectionExtension Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update a storage server connection extension for the given host. |
6.220.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.220.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.220.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.220.3. update PUT Copy linkLink copied to clipboard!
Update a storage server connection extension for the given host.
To update the storage connection 456 of host 123 send a request like this:
PUT /ovirt-engine/api/hosts/123/storageconnectionextensions/456
PUT /ovirt-engine/api/hosts/123/storageconnectionextensions/456
With a request body like this:
<storage_connection_extension> <target>iqn.2016-01.com.example:mytarget</target> <username>myuser</username> <password>mypassword</password> </storage_connection_extension>
<storage_connection_extension>
<target>iqn.2016-01.com.example:mytarget</target>
<username>myuser</username>
<password>mypassword</password>
</storage_connection_extension>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.221. StorageServerConnectionExtensions Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new storage server connection extension for the given host. |
|
| Returns the list os storage connection extensions. |
6.221.1. add POST Copy linkLink copied to clipboard!
Creates a new storage server connection extension for the given host.
The extension lets the user define credentials for an iSCSI target for a specific host. For example to use myuser and mypassword as the credentials when connecting to the iSCSI target from host 123 send a request like this:
POST /ovirt-engine/api/hosts/123/storageconnectionextensions
POST /ovirt-engine/api/hosts/123/storageconnectionextensions
With a request body like this:
<storage_connection_extension> <target>iqn.2016-01.com.example:mytarget</target> <username>myuser</username> <password>mypassword</password> </storage_connection_extension>
<storage_connection_extension>
<target>iqn.2016-01.com.example:mytarget</target>
<username>myuser</username>
<password>mypassword</password>
</storage_connection_extension>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.221.2. list GET Copy linkLink copied to clipboard!
Returns the list os storage connection extensions.
The order of the returned list of storage connections isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of extensions to return. |
6.221.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.221.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of extensions to return. If not specified all the extensions are returned.
6.222. StorageServerConnections Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new storage connection. |
|
| Returns the list of storage connections. |
6.222.1. add POST Copy linkLink copied to clipboard!
Creates a new storage connection.
For example, to create a new storage connection for the NFS server mynfs.example.com and NFS share /export/mydata send a request like this:
POST /ovirt-engine/api/storageconnections
POST /ovirt-engine/api/storageconnections
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.222.2. list GET Copy linkLink copied to clipboard!
Returns the list of storage connections.
The order of the returned list of connections isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of connections to return. |
6.222.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.222.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of connections to return. If not specified all the connections are returned.
6.223. System Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns basic information describing the API, like the product name, the version number and a summary of the number of relevant objects. |
|
|
6.223.1. get GET Copy linkLink copied to clipboard!
Returns basic information describing the API, like the product name, the version number and a summary of the number of relevant objects.
GET /ovirt-engine/api
GET /ovirt-engine/api
We get following response:
The entry point provides a user with links to the collections in a virtualization environment. The rel attribute of each collection link provides a reference point for each link.
The entry point also contains other data such as product_info, special_objects and summary.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.223.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.223.2. reloadconfigurations POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reload should be performed asynchronously. |
6.224. SystemOption Copy linkLink copied to clipboard!
A service that provides values of specific configuration option of the system.
| Name | Summary |
|---|---|
|
| Get the values of specific configuration option. |
6.224.1. get GET Copy linkLink copied to clipboard!
Get the values of specific configuration option.
For example to retrieve the values of configuration option MigrationPolicies send a request like this:
GET /ovirt-engine/api/options/MigrationPolicies
GET /ovirt-engine/api/options/MigrationPolicies
The response to that request will be the following:
The appropriate permissions are required to query configuration options. Some options can be queried only by users with administrator permissions.
There is NO backward compatibility and no guarantee about the names or values of the options. Options may be removed and their meaning can be changed at any point.
We strongly discourage the use of this service for applications other than the ones that are released simultaneously with the engine. Usage by other applications is not supported. Therefore there will be no documentation listing accessible configuration options.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The returned configuration option of the system. | |
|
| In | Optional version parameter that specifies that only particular version of the configuration option should be returned. |
6.224.1.1. version Copy linkLink copied to clipboard!
Optional version parameter that specifies that only particular version of the configuration option should be returned. If this parameter isn’t used then all the versions will be returned.
For example, to get the value of the MigrationPolicies option but only for version 4.2 send a request like this:
GET /ovirt-engine/api/options/MigrationPolicies?version=4.2
GET /ovirt-engine/api/options/MigrationPolicies?version=4.2
The response to that request will be like this:
6.225. SystemOptions Copy linkLink copied to clipboard!
Service that provides values of configuration options of the system.
6.226. SystemPermissions Copy linkLink copied to clipboard!
This service doesn’t add any new methods, it is just a placeholder for the annotation that specifies the path of the resource that manages the permissions assigned to the system object.
| Name | Summary |
|---|---|
|
| Assign a new permission to a user or group for specific entity. |
|
| List all the permissions of the specific entity. |
6.226.1. add POST Copy linkLink copied to clipboard!
Assign a new permission to a user or group for specific entity.
For example, to assign the UserVmManager role to the virtual machine with id 123 to the user with id 456 send a request like this:
POST /ovirt-engine/api/vms/123/permissions
POST /ovirt-engine/api/vms/123/permissions
With a request body like this:
To assign the SuperUser role to the system to the user with id 456 send a request like this:
POST /ovirt-engine/api/permissions
POST /ovirt-engine/api/permissions
With a request body like this:
If you want to assign permission to the group instead of the user please replace the user element with the group element with proper id of the group. For example to assign the UserRole role to the cluster with id 123 to the group with id 789 send a request like this:
POST /ovirt-engine/api/clusters/123/permissions
POST /ovirt-engine/api/clusters/123/permissions
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The permission. |
6.226.2. list GET Copy linkLink copied to clipboard!
List all the permissions of the specific entity.
For example to list all the permissions of the cluster with id 123 send a request like this:
GET /ovirt-engine/api/clusters/123/permissions
GET /ovirt-engine/api/clusters/123/permissions
The order of the returned permissions isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The list of permissions. |
6.226.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.227. Tag Copy linkLink copied to clipboard!
A service to manage a specific tag in the system.
| Name | Summary |
|---|---|
|
| Gets the information about the tag. |
|
| Removes the tag from the system. |
|
| Updates the tag entity. |
6.227.1. get GET Copy linkLink copied to clipboard!
Gets the information about the tag.
For example to retrieve the information about the tag with the id 123 send a request like this:
GET /ovirt-engine/api/tags/123
GET /ovirt-engine/api/tags/123
<tag href="/ovirt-engine/api/tags/123" id="123"> <name>root</name> <description>root</description> </tag>
<tag href="/ovirt-engine/api/tags/123" id="123">
<name>root</name>
<description>root</description>
</tag>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The tag. |
6.227.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.227.2. remove DELETE Copy linkLink copied to clipboard!
Removes the tag from the system.
For example to remove the tag with id 123 send a request like this:
DELETE /ovirt-engine/api/tags/123
DELETE /ovirt-engine/api/tags/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.227.3. update PUT Copy linkLink copied to clipboard!
Updates the tag entity.
For example to update parent tag to tag with id 456 of the tag with id 123 send a request like this:
PUT /ovirt-engine/api/tags/123
PUT /ovirt-engine/api/tags/123
With request body like:
<tag> <parent id="456"/> </tag>
<tag>
<parent id="456"/>
</tag>
You may also specify a tag name instead of id. For example to update parent tag to tag with name mytag of the tag with id 123 send a request like this:
<tag>
<parent>
<name>mytag</name>
</parent>
</tag>
<tag>
<parent>
<name>mytag</name>
</parent>
</tag>
6.228. Tags Copy linkLink copied to clipboard!
Represents a service to manage collection of the tags in the system.
| Name | Summary |
|---|---|
|
| Add a new tag to the system. |
|
| List the tags in the system. |
6.228.1. add POST Copy linkLink copied to clipboard!
Add a new tag to the system.
For example, to add new tag with name mytag to the system send a request like this:
POST /ovirt-engine/api/tags
POST /ovirt-engine/api/tags
With a request body like this:
<tag> <name>mytag</name> </tag>
<tag>
<name>mytag</name>
</tag>
The root tag is a special pseudo-tag assumed as the default parent tag if no parent tag is specified. The root tag cannot be deleted nor assigned a parent tag.
To create new tag with specific parent tag send a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The added tag. |
6.228.2. list GET Copy linkLink copied to clipboard!
List the tags in the system.
For example to list the full hierarchy of the tags in the system send a request like this:
GET /ovirt-engine/api/tags
GET /ovirt-engine/api/tags
In the previous XML output you can see the following hierarchy of the tags:
root: (id: 111)
- root2 (id: 222)
- root3 (id: 333)
root: (id: 111)
- root2 (id: 222)
- root3 (id: 333)
The order of the returned list of tags isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of tags to return. | |
|
| Tag[] | Out | List of all tags in the system. |
6.228.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.228.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of tags to return. If not specified all the tags are returned.
6.229. Template Copy linkLink copied to clipboard!
Manages the virtual machine template and template versions.
| Name | Summary |
|---|---|
|
| Exports a template to the data center export domain. |
|
| Returns the information about this template or template version. |
|
| Removes a virtual machine template. |
|
| Updates the template. |
6.229.1. export POST Copy linkLink copied to clipboard!
Exports a template to the data center export domain.
For example, send the following request:
POST /ovirt-engine/api/templates/123/export
POST /ovirt-engine/api/templates/123/export
With a request body like this:
<action> <storage_domain id="456"/> <exclusive>true<exclusive/> </action>
<action>
<storage_domain id="456"/>
<exclusive>true<exclusive/>
</action>
Since version 4.2 of the engine it is also possible to export a template as a virtual appliance (OVA). For example, to export template 123 as an OVA file named myvm.ova that is placed in the directory /home/ovirt/ on host myhost:
POST /ovirt-engine/api/templates/123/export
POST /ovirt-engine/api/templates/123/export
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the existing templates with the same name should be overwritten. | |
|
| In | Specifies the destination export storage domain. |
6.229.1.1. exclusive Copy linkLink copied to clipboard!
Indicates if the existing templates with the same name should be overwritten.
The export action reports a failed action if a template of the same name exists in the destination domain. Set this parameter to true to change this behavior and overwrite any existing template.
6.229.2. get GET Copy linkLink copied to clipboard!
Returns the information about this template or template version.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | The information about the template or template version. |
6.229.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.229.3. remove DELETE Copy linkLink copied to clipboard!
Removes a virtual machine template.
DELETE /ovirt-engine/api/templates/123
DELETE /ovirt-engine/api/templates/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.229.4. update PUT Copy linkLink copied to clipboard!
Updates the template.
The name, description, type, memory, cpu, topology, os, high_availability, display, stateless, usb, and timezone elements can be updated after a template has been created.
For example, to update a template so that it has 1 GiB of memory send a request like this:
PUT /ovirt-engine/api/templates/123
PUT /ovirt-engine/api/templates/123
With the following request body:
<template> <memory>1073741824</memory> </template>
<template>
<memory>1073741824</memory>
</template>
The version_name name attribute is the only one that can be updated within the version attribute used for template versions:
<template>
<version>
<version_name>mytemplate_2</version_name>
</version>
</template>
<template>
<version>
<version_name>mytemplate_2</version_name>
</version>
</template>
6.230. TemplateCdrom Copy linkLink copied to clipboard!
A service managing a CD-ROM device on templates.
| Name | Summary |
|---|---|
|
| Returns the information about this CD-ROM device. |
6.230.1. get GET Copy linkLink copied to clipboard!
Returns the information about this CD-ROM device.
For example, to get information about the CD-ROM device of template 123 send a request like:
GET /ovirt-engine/api/templates/123/cdroms/
GET /ovirt-engine/api/templates/123/cdroms/
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the CD-ROM device. | |
|
| In | Indicates which inner links should be followed. |
6.230.1.1. cdrom Copy linkLink copied to clipboard!
The information about the CD-ROM device.
The information consists of cdrom attribute containing reference to the CD-ROM device, the template, and optionally the inserted disk.
If there is a disk inserted then the file attribute will contain a reference to the ISO image:
<cdrom href="..." id="00000000-0000-0000-0000-000000000000"> <template href="/ovirt-engine/api/templates/123" id="123"/> <file id="mycd.iso"/> </cdrom>
<cdrom href="..." id="00000000-0000-0000-0000-000000000000">
<template href="/ovirt-engine/api/templates/123" id="123"/>
<file id="mycd.iso"/>
</cdrom>
If there is no disk inserted then the file attribute won’t be reported:
<cdrom href="..." id="00000000-0000-0000-0000-000000000000"> <template href="/ovirt-engine/api/templates/123" id="123"/> </cdrom>
<cdrom href="..." id="00000000-0000-0000-0000-000000000000">
<template href="/ovirt-engine/api/templates/123" id="123"/>
</cdrom>
6.230.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.231. TemplateCdroms Copy linkLink copied to clipboard!
Lists the CD-ROM devices of a template.
| Name | Summary |
|---|---|
|
| Returns the list of CD-ROM devices of the template. |
6.231.1. list GET Copy linkLink copied to clipboard!
Returns the list of CD-ROM devices of the template.
The order of the returned list of CD-ROM devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of CD-ROM devices of the template. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of CD-ROMs to return. |
6.231.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.231.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of CD-ROMs to return. If not specified all the CD-ROMs are returned.
6.232. TemplateDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Copy the specified disk attached to the template to a specific storage domain. |
|
| |
|
| |
|
|
6.232.1. copy POST Copy linkLink copied to clipboard!
Copy the specified disk attached to the template to a specific storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the copy should be performed asynchronously. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In |
6.232.2. export POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the export should be performed asynchronously. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In |
6.232.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.232.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.232.4. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.233. TemplateDiskAttachment Copy linkLink copied to clipboard!
This service manages the attachment of a disk to a template.
| Name | Summary |
|---|---|
|
| Returns the details of the attachment. |
|
| Removes the disk from the template. |
6.233.1. get GET Copy linkLink copied to clipboard!
Returns the details of the attachment.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.233.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.233.2. remove DELETE Copy linkLink copied to clipboard!
Removes the disk from the template. The disk will only be removed if there are other existing copies of the disk on other storage domains.
A storage domain has to be specified to determine which of the copies should be removed (template disks can have copies on multiple storage domains).
DELETE /ovirt-engine/api/templates/{template:id}/diskattachments/{attachment:id}?storage_domain=072fbaa1-08f3-4a40-9f34-a5ca22dd1d74
DELETE /ovirt-engine/api/templates/{template:id}/diskattachments/{attachment:id}?storage_domain=072fbaa1-08f3-4a40-9f34-a5ca22dd1d74
6.234. TemplateDiskAttachments Copy linkLink copied to clipboard!
This service manages the set of disks attached to a template. Each attached disk is represented by a DiskAttachment.
| Name | Summary |
|---|---|
|
| List the disks that are attached to the template. |
6.234.1. list GET Copy linkLink copied to clipboard!
List the disks that are attached to the template.
The order of the returned list of attachments isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.234.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.235. TemplateDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of disks of the template. |
6.235.1. list GET Copy linkLink copied to clipboard!
Returns the list of disks of the template.
The order of the returned list of disks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. |
6.235.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.235.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.236. TemplateGraphicsConsole Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets graphics console configuration of the template. |
|
| Remove the graphics console from the template. |
6.236.1. get GET Copy linkLink copied to clipboard!
Gets graphics console configuration of the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the graphics console of the template. | |
|
| In | Indicates which inner links should be followed. |
6.236.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.236.2. remove DELETE Copy linkLink copied to clipboard!
Remove the graphics console from the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.237. TemplateGraphicsConsoles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add new graphics console to the template. |
|
| Lists all the configured graphics consoles of the template. |
6.237.1. add POST Copy linkLink copied to clipboard!
Add new graphics console to the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.237.2. list GET Copy linkLink copied to clipboard!
Lists all the configured graphics consoles of the template.
The order of the returned list of graphics consoles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of graphics consoles of the template. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of consoles to return. |
6.237.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.237.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
6.238. TemplateMediatedDevice Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets mediated device configuration of the template. |
|
| Remove the mediated device from the template. |
|
| Updates the information about the mediated device. |
6.238.1. get GET Copy linkLink copied to clipboard!
Gets mediated device configuration of the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the mediated device of the template. | |
|
| In | Indicates which inner links should be followed. |
6.238.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.238.2. remove DELETE Copy linkLink copied to clipboard!
Remove the mediated device from the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.238.3. update PUT Copy linkLink copied to clipboard!
Updates the information about the mediated device.
You can update the information using specParams element.
For example, to update a mediated device, send a request like this:
with response body:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The information about the mediated device. |
6.238.3.1. devices Copy linkLink copied to clipboard!
The information about the mediated device.
The request data must contain specParams properties. The response data contains complete information about the updated mediated device.
6.239. TemplateMediatedDevices Copy linkLink copied to clipboard!
A service that manages mediated devices of a template.
| Name | Summary |
|---|---|
|
| Add new mediated device to the template. |
|
| Lists all the configured mediated devices of the template. |
6.239.1. add POST Copy linkLink copied to clipboard!
Add new mediated device to the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.239.2. list GET Copy linkLink copied to clipboard!
Lists all the configured mediated devices of the template.
The order of the returned list of mediated devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of mediated devices of the template. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of mediated devices to return. |
6.239.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.239.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of mediated devices to return. If not specified all the mediated devices are returned.
6.240. TemplateNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the specified network interface card attached to the template. |
6.240.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.240.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.240.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.240.3. update PUT Copy linkLink copied to clipboard!
Update the specified network interface card attached to the template.
6.241. TemplateNics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a new network interface card to the template. |
|
| Returns the list of NICs of the template. |
6.241.1. add POST Copy linkLink copied to clipboard!
Add a new network interface card to the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.241.2. list GET Copy linkLink copied to clipboard!
Returns the list of NICs of the template.
The order of the returned list of NICs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of NICs to return. | |
|
| Nic[] | Out |
6.241.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.241.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.242. TemplateWatchdog Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update the watchdog for the template identified by the given id. |
6.242.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.242.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.242.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.242.3. update PUT Copy linkLink copied to clipboard!
Update the watchdog for the template identified by the given id.
6.243. TemplateWatchdogs Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a watchdog to the template identified by the given id. |
|
| Returns the list of watchdogs. |
6.243.1. add POST Copy linkLink copied to clipboard!
Add a watchdog to the template identified by the given id.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.243.2. list GET Copy linkLink copied to clipboard!
Returns the list of watchdogs.
The order of the returned list of watchdogs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of watchdogs to return. | |
|
| Out |
6.243.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.243.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
6.244. Templates Copy linkLink copied to clipboard!
This service manages the virtual machine templates available in the system.
| Name | Summary |
|---|---|
|
| Creates a new template. |
|
| Returns the list of virtual machine templates. |
6.244.1. add POST Copy linkLink copied to clipboard!
Creates a new template.
This requires the name and vm elements. To identify the virtual machine use the vm.id or vm.name attributes. For example, to create a template from a virtual machine with the identifier 123 send a request like this:
POST /ovirt-engine/api/templates
POST /ovirt-engine/api/templates
With a request body like this:
<template> <name>mytemplate</name> <vm id="123"/> </template>
<template>
<name>mytemplate</name>
<vm id="123"/>
</template>
Since version 4.3, in order to create virtual machine template from a snapshot send a request body like this:
The disks of the template can be customized, making some of their characteristics different from the disks of the original virtual machine. To do so use the vm.disk_attachments attribute, specifying the identifier of the disk of the original virtual machine and the characteristics that you want to change. For example, if the original virtual machine has a disk with the identifier 456, and, for that disk, you want to change the name to mydisk the format to Copy On Write and make it sparse, send a request body like this:
The template can be created as a sub-version of an existing template. This requires the name and vm attributes for the new template, and the base_template and version_name attributes for the new template version. The base_template and version_name attributes must be specified within a version section enclosed in the template section. Identify the virtual machine with the id or name attributes.
The destination storage domain of the template can be customized, in one of two ways:
Globally, at the request level. The request must list the desired disk attachments to be created on the storage domain. If the disk attachments are not listed, the global storage domain parameter will be ignored.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Per each disk attachment. Specify the desired storage domain for each disk attachment. Specifying the global storage definition will override the storage domain per disk attachment specification.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Specifies if the permissions of the virtual machine should be copied to the template. | |
|
| In | Seals the template. | |
|
| In/Out | The information about the template or template version. |
6.244.1.1. clone_permissions Copy linkLink copied to clipboard!
Specifies if the permissions of the virtual machine should be copied to the template.
If this optional parameter is provided, and its value is true, then the permissions of the virtual machine (only the direct ones, not the inherited ones) will be copied to the created template. For example, to create a template from the myvm virtual machine copying its permissions, send a request like this:
POST /ovirt-engine/api/templates?clone_permissions=true
POST /ovirt-engine/api/templates?clone_permissions=true
With a request body like this:
6.244.1.2. seal Copy linkLink copied to clipboard!
Seals the template.
If this optional parameter is provided and its value is true, then the template is sealed after creation.
Sealing erases all host-specific configuration from the filesystem: SSH keys, UDEV rules, MAC addresses, system ID, hostname, and so on, thus making it easier to use the template to create multiple virtual machines without manual intervention.
Currently, sealing is supported only for Linux operating systems.
6.244.2. list GET Copy linkLink copied to clipboard!
Returns the list of virtual machine templates.
For example:
GET /ovirt-engine/api/templates
GET /ovirt-engine/api/templates
Will return the list of virtual machines and virtual machine templates.
The order of the returned list of templates is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of templates to return. | |
|
| In | A query string used to restrict the returned templates. | |
|
| Out | The list of virtual machine templates. |
6.244.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.244.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.244.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of templates to return. If not specified, all the templates are returned.
6.245. UnmanagedNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.245.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.245.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.245.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.246. UnmanagedNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of unmanaged networks of the host. |
6.246.1. list GET Copy linkLink copied to clipboard!
Returns the list of unmanaged networks of the host.
The order of the returned list of networks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.246.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.246.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.247. User Copy linkLink copied to clipboard!
A service to manage a user in the system. Use this service to either get users details or remove users. In order to add new users please use users.
| Name | Summary |
|---|---|
|
| Gets the system user information. |
|
| Removes the system user. |
|
| Updates information about the user. |
6.247.1. get GET Copy linkLink copied to clipboard!
Gets the system user information.
Usage:
GET /ovirt-engine/api/users/1234
GET /ovirt-engine/api/users/1234
Will return the user information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The system user. |
6.247.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.247.2. remove DELETE Copy linkLink copied to clipboard!
Removes the system user.
Usage:
DELETE /ovirt-engine/api/users/1234
DELETE /ovirt-engine/api/users/1234
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.247.3. update PUT Copy linkLink copied to clipboard!
Updates information about the user.
Only the user_options field can be updated.
For example, to update user options:
PUT /ovirt-engine/api/users/123
PUT /ovirt-engine/api/users/123
With a request body like this:
Since version 4.4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. Please use the options endpoint instead.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.248. UserOption Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns a user profile property of type JSON. |
|
| Deletes an existing property of type JSON. |
6.248.1. get GET Copy linkLink copied to clipboard!
Returns a user profile property of type JSON.
Example request(for user with identifier 123 and option with identifier 456):
GET /ovirt-engine/api/users/123/options/456
GET /ovirt-engine/api/users/123/options/456
The result will be the following XML document:
<user_option href="/ovirt-engine/api/users/123/options/456" id="456">
<name>SomeName</name>
<content>["any", "JSON"]</content>
<user href="/ovirt-engine/api/users/123" id="123"/>
</user_option>
<user_option href="/ovirt-engine/api/users/123/options/456" id="456">
<name>SomeName</name>
<content>["any", "JSON"]</content>
<user href="/ovirt-engine/api/users/123" id="123"/>
</user_option>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.248.2. remove DELETE Copy linkLink copied to clipboard!
Deletes an existing property of type JSON.
Example request(for user with identifier 123 and option with identifier 456):
DELETE /ovirt-engine/api/users/123/options/456
DELETE /ovirt-engine/api/users/123/options/456
6.249. UserOptions Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Adds a new user profile property of type JSON. |
|
| Returns a list of user profile properties of type JSON. |
6.249.1. add POST Copy linkLink copied to clipboard!
Adds a new user profile property of type JSON.
Example request(for user with identifier 123):
POST /ovirt-engine/api/users/123/options
POST /ovirt-engine/api/users/123/options
Payload:
<user_option>
<name>SomeName</name>
<content>["any", "JSON"]</content>
</user_option>
<user_option>
<name>SomeName</name>
<content>["any", "JSON"]</content>
</user_option>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.249.2. list GET Copy linkLink copied to clipboard!
Returns a list of user profile properties of type JSON.
Example request(for user with identifier 123):
GET /ovirt-engine/api/users/123/options
GET /ovirt-engine/api/users/123/options
The result will be the following XML document:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.250. Users Copy linkLink copied to clipboard!
A service to manage the users in the system.
| Name | Summary |
|---|---|
|
| Add user from a directory service. |
|
| List all the users in the system. |
6.250.1. add POST Copy linkLink copied to clipboard!
Add user from a directory service.
For example, to add the myuser user from the myextension-authz authorization provider send a request like this:
POST /ovirt-engine/api/users
POST /ovirt-engine/api/users
With a request body like this:
In case you are working with Active Directory you have to pass user principal name (UPN) as username, followed by authorization provider name. Due to bug 1147900 you need to provide also principal parameter set to UPN of the user.
For example, to add the user with UPN myuser@mysubdomain.mydomain.com from the myextension-authz authorization provider send a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.250.2. list GET Copy linkLink copied to clipboard!
List all the users in the system.
Usage:
GET /ovirt-engine/api/users
GET /ovirt-engine/api/users
Will return the list of users:
The order of the returned list of users isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of users to return. | |
|
| In | A query string used to restrict the returned users. | |
|
| Out | The list of users. |
6.250.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.250.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.250.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of users to return. If not specified all the users are returned.
6.251. VirtualFunctionAllowedNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.251.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.251.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.251.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.252. VirtualFunctionAllowedNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Returns the list of networks. |
6.252.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.252.2. list GET Copy linkLink copied to clipboard!
Returns the list of networks.
The order of the returned list of networks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.252.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.252.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.253. Vm Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Apply an automatic CPU and NUMA configuration on the VM. |
|
| This operation stops any migration of a virtual machine to another physical host. |
|
| |
|
| Permanently restores the virtual machine to the state of the previewed snapshot. |
|
| Detaches a virtual machine from a pool. |
|
| Exports the virtual machine. |
|
| Freezes virtual machine file systems. |
|
| Retrieves the description of the virtual machine. |
|
| Initiates the automatic user logon to access a virtual machine from an external console. |
|
| Sets the global maintenance mode on the hosted engine virtual machine. |
|
| Migrates a virtual machine to another physical host. |
|
| Temporarily restores the virtual machine to the state of a snapshot. |
|
| Sends a reboot request to a virtual machine. |
|
| Removes the virtual machine, including the virtual disks attached to it. |
|
| |
|
| Sends a reset request to a virtual machine. |
|
| Captures screenshot of the current state of the VM. |
|
| This operation sends a shutdown request to a virtual machine. |
|
| Starts the virtual machine. |
|
| This operation forces a virtual machine to power-off. |
|
| This operation saves the virtual machine state to disk and stops it. |
|
| Thaws virtual machine file systems. |
|
| Generates a time-sensitive authentication token for accessing a virtual machine’s display. |
|
| Restores the virtual machine to the state it had before previewing the snapshot. |
|
| Update the virtual machine in the system for the given virtual machine id. |
6.253.1. autopincpuandnumanodes POST Copy linkLink copied to clipboard!
Apply an automatic CPU and NUMA configuration on the VM.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. Instead please use PUT followed by update operation.
An example for a request:
POST /ovirt-engine/api/vms/123/autopincpuandnumanodes
POST /ovirt-engine/api/vms/123/autopincpuandnumanodes
With a request body like this:
<action> <optimize_cpu_settings>true</optimize_cpu_settings> </action>
<action>
<optimize_cpu_settings>true</optimize_cpu_settings>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the detach action should be performed asynchronously. | |
|
| In | Specifies how the auto CPU and NUMA configuration is applied. |
6.253.1.1. optimize_cpu_settings Copy linkLink copied to clipboard!
Specifies how the auto CPU and NUMA configuration is applied. If set to true, will adjust the CPU topology to fit the VM pinned host hardware. Otherwise, it will use the VM CPU topology.
6.253.2. cancelmigration POST Copy linkLink copied to clipboard!
This operation stops any migration of a virtual machine to another physical host.
POST /ovirt-engine/api/vms/123/cancelmigration
POST /ovirt-engine/api/vms/123/cancelmigration
The cancel migration action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should cancelled asynchronously. |
6.253.3. clone POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the clone should be performed asynchronously. | |
|
| In |
Use the | |
|
| In | The storage domain on which the virtual machines disks will be copied to. | |
|
| In |
6.253.3.1. discard_snapshots Copy linkLink copied to clipboard!
Use the discard_snapshots parameter when the virtual machine should be clone with its snapshots collapsed. Default is true.
6.253.4. commitsnapshot POST Copy linkLink copied to clipboard!
Permanently restores the virtual machine to the state of the previewed snapshot.
See the preview_snapshot operation for details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the snapshots should be committed asynchronously. |
6.253.5. detach POST Copy linkLink copied to clipboard!
Detaches a virtual machine from a pool.
POST /ovirt-engine/api/vms/123/detach
POST /ovirt-engine/api/vms/123/detach
The detach action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the detach action should be performed asynchronously. |
6.253.6. export POST Copy linkLink copied to clipboard!
Exports the virtual machine.
A virtual machine can be exported to an export domain. For example, to export virtual machine 123 to the export domain myexport:
POST /ovirt-engine/api/vms/123/export
POST /ovirt-engine/api/vms/123/export
With a request body like this:
Since version 4.2 of the engine it is also possible to export a virtual machine as a virtual appliance (OVA). For example, to export virtual machine 123 as an OVA file named myvm.ova that is placed in the directory /home/ovirt/ on host myhost:
POST /ovirt-engine/api/vms/123/export
POST /ovirt-engine/api/vms/123/export
With a request body like this:
Confirm that the export operation has completed before attempting any actions on the export domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the export should be performed asynchronously. | |
|
| In |
Use the | |
|
| In |
Use the | |
|
| In | The (export) storage domain to export the virtual machine to. |
6.253.7. freezefilesystems POST Copy linkLink copied to clipboard!
Freezes virtual machine file systems.
This operation freezes a virtual machine’s file systems using the QEMU guest agent when taking a live snapshot of a running virtual machine. Normally, this is done automatically by the manager, but this must be executed manually with the API for virtual machines using OpenStack Volume (Cinder) disks.
Example:
POST /ovirt-engine/api/vms/123/freezefilesystems
POST /ovirt-engine/api/vms/123/freezefilesystems
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the freeze should be performed asynchronously. |
6.253.8. get GET Copy linkLink copied to clipboard!
Retrieves the description of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the virtual machine should be included in the response. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Indicates if the returned result describes the virtual machine as it is currently running or if describes the virtual machine with the modifications that have already been performed but that will only come into effect when the virtual machine is restarted. | |
|
| In | Indicates if the results should expose the OVF as it appears in OVA files of that VM. | |
|
| Out | Description of the virtual machine. |
6.253.8.1. all_content Copy linkLink copied to clipboard!
Indicates if all of the attributes of the virtual machine should be included in the response.
By default the following attributes are excluded:
-
console -
initialization.configuration.data- The OVF document describing the virtual machine. -
rng_source -
soundcard -
virtio_scsi
For example, to retrieve the complete representation of the virtual machine '123':
GET /ovirt-engine/api/vms/123?all_content=true
GET /ovirt-engine/api/vms/123?all_content=true
These attributes are not included by default as they reduce performance. These attributes are seldom used and require additional queries to the database. Only use this parameter when required as it will reduce performance.
6.253.8.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.253.8.3. next_run Copy linkLink copied to clipboard!
Indicates if the returned result describes the virtual machine as it is currently running or if describes the virtual machine with the modifications that have already been performed but that will only come into effect when the virtual machine is restarted. By default the value is false.
If the parameter is included in the request, but without a value, it is assumed that the value is true. The the following request:
GET /vms/{vm:id};next_run
GET /vms/{vm:id};next_run
Is equivalent to using the value true:
GET /vms/{vm:id};next_run=true
GET /vms/{vm:id};next_run=true
6.253.8.4. ovf_as_ova Copy linkLink copied to clipboard!
Indicates if the results should expose the OVF as it appears in OVA files of that VM. The OVF document describing the virtual machine. This parameter will work only when all_content=True is set. The OVF will be presented in initialization.configuration.data.
For example:
GET /vms/{vm:id}?all_content=true&ovf_as_ova=true
GET /vms/{vm:id}?all_content=true&ovf_as_ova=true
6.253.9. logon POST Copy linkLink copied to clipboard!
Initiates the automatic user logon to access a virtual machine from an external console.
This action requires the ovirt-guest-agent-gdm-plugin and the ovirt-guest-agent-pam-module packages to be installed and the ovirt-guest-agent service to be running on the virtual machine.
Users require the appropriate user permissions for the virtual machine in order to access the virtual machine from an external console.
For example:
POST /ovirt-engine/api/vms/123/logon
POST /ovirt-engine/api/vms/123/logon
Request body:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the logon should be performed asynchronously. |
6.253.10. maintenance POST Copy linkLink copied to clipboard!
Sets the global maintenance mode on the hosted engine virtual machine.
This action has no effect on other virtual machines.
Example:
POST /ovirt-engine/api/vms/123/maintenance
POST /ovirt-engine/api/vms/123/maintenance
<action> <maintenance_enabled>true<maintenance_enabled/> </action>
<action>
<maintenance_enabled>true<maintenance_enabled/>
</action>
6.253.11. migrate POST Copy linkLink copied to clipboard!
Migrates a virtual machine to another physical host.
Example:
POST /ovirt-engine/api/vms/123/migrate
POST /ovirt-engine/api/vms/123/migrate
To specify a specific host to migrate the virtual machine to:
<action> <host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"/> </action>
<action>
<host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"/>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should be performed asynchronously. | |
|
| In | Specifies the cluster the virtual machine should migrate to. | |
|
| In | Specifies that the virtual machine should migrate even if the virtual machine is defined as non-migratable. | |
|
| In | Specifies a specific host that the virtual machine should migrate to. | |
|
| In | Migrate also all other virtual machines in positive enforcing affinity groups with this virtual machine, that are running on the same host. |
6.253.11.1. cluster Copy linkLink copied to clipboard!
Specifies the cluster the virtual machine should migrate to. This is an optional parameter. By default, the virtual machine is migrated to another host within the same cluster.
Live migration to another cluster is not supported. Strongly consider the target cluster’s hardware architecture and network architecture before attempting a migration.
6.253.11.2. force Copy linkLink copied to clipboard!
Specifies that the virtual machine should migrate even if the virtual machine is defined as non-migratable. This is an optional parameter. By default, it is set to false.
6.253.11.3. host Copy linkLink copied to clipboard!
Specifies a specific host that the virtual machine should migrate to. This is an optional parameter. By default, the Red Hat Virtualization Manager automatically selects a default host for migration within the same cluster. If an API user requires a specific host, the user can specify the host with either an id or name parameter.
6.253.11.4. migrate_vms_in_affinity_closure Copy linkLink copied to clipboard!
Migrate also all other virtual machines in positive enforcing affinity groups with this virtual machine, that are running on the same host.
The default value is false.
6.253.12. previewsnapshot POST Copy linkLink copied to clipboard!
Temporarily restores the virtual machine to the state of a snapshot.
The snapshot is indicated with the snapshot.id parameter. It is restored temporarily, so that the content can be inspected. Once that inspection is finished, the state of the virtual machine can be made permanent, using the commit_snapshot method, or discarded using the undo_snapshot method.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the preview should be performed asynchronously. | |
|
| In | Specify the disks included in the snapshot’s preview. | |
|
| In | Specify the lease storage domain ID to use in the preview of the snapshot. | |
|
| In | ||
|
| In | ||
|
| In |
6.253.12.1. disks Copy linkLink copied to clipboard!
Specify the disks included in the snapshot’s preview.
For each disk parameter, it is also required to specify its image_id.
For example, to preview a snapshot with identifier 456 which includes a disk with identifier 111 and its image_id as 222, send a request like this:
POST /ovirt-engine/api/vms/123/previewsnapshot
POST /ovirt-engine/api/vms/123/previewsnapshot
Request body:
6.253.12.2. lease Copy linkLink copied to clipboard!
Specify the lease storage domain ID to use in the preview of the snapshot. If lease parameter is not passed, then the previewed snapshot lease storage domain will be used. If lease parameter is passed with empty storage domain parameter, then no lease will be used for the snapshot preview. If lease parameter is passed with storage domain parameter then the storage domain ID can be only one of the leases domain IDs that belongs to one of the virtual machine snapshots. This is an optional parameter, set by default to null
6.253.13. reboot POST Copy linkLink copied to clipboard!
Sends a reboot request to a virtual machine.
For example:
POST /ovirt-engine/api/vms/123/reboot
POST /ovirt-engine/api/vms/123/reboot
The reboot action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
To reboot the VM even if a backup is running for it, the action should include the 'force' element.
For example, to force reboot virtual machine 123:
POST /ovirt-engine/api/vms/123/reboot
POST /ovirt-engine/api/vms/123/reboot
<action>
<force>true</force>
</action>
<action>
<force>true</force>
</action>
6.253.14. remove DELETE Copy linkLink copied to clipboard!
Removes the virtual machine, including the virtual disks attached to it.
For example, to remove the virtual machine with identifier 123:
DELETE /ovirt-engine/api/vms/123
DELETE /ovirt-engine/api/vms/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates if the attached virtual disks should be detached first and preserved instead of being removed. | |
|
| In | Indicates if the virtual machine should be forcibly removed. |
6.253.14.1. force Copy linkLink copied to clipboard!
Indicates if the virtual machine should be forcibly removed.
Locked virtual machines and virtual machines with locked disk images cannot be removed without this flag set to true.
6.253.15. reordermacaddresses POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.253.16. reset POST Copy linkLink copied to clipboard!
Sends a reset request to a virtual machine.
For example:
POST /ovirt-engine/api/vms/123/reset
POST /ovirt-engine/api/vms/123/reset
The reset action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reset should be performed asynchronously. |
6.253.17. screenshot POST Copy linkLink copied to clipboard!
Captures screenshot of the current state of the VM.
For example:
POST /ovirt-engine/api/vms/123/screenshot
POST /ovirt-engine/api/vms/123/screenshot
The screenshot action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
6.253.18. shutdown POST Copy linkLink copied to clipboard!
This operation sends a shutdown request to a virtual machine.
For example:
POST /ovirt-engine/api/vms/123/shutdown
POST /ovirt-engine/api/vms/123/shutdown
The shutdown action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
To shutdown the VM even if a backup is running for it, the action should include the 'force' element.
For example, to force shutdown virtual machine 123:
POST /ovirt-engine/api/vms/123/shutdown
POST /ovirt-engine/api/vms/123/shutdown
<action>
<force>true</force>
</action>
<action>
<force>true</force>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the shutdown should be performed asynchronously. | |
|
| In | Indicates if the VM should be forcibly shutdown even if a backup is running for it. | |
|
| In | The reason the virtual machine was stopped. |
6.253.18.1. reason Copy linkLink copied to clipboard!
The reason the virtual machine was stopped. Optionally set by user when shutting down the virtual machine.
6.253.19. start POST Copy linkLink copied to clipboard!
Starts the virtual machine.
If the virtual environment is complete and the virtual machine contains all necessary components to function, it can be started.
This example starts the virtual machine:
POST /ovirt-engine/api/vms/123/start
POST /ovirt-engine/api/vms/123/start
With a request body:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the start action should be performed asynchronously. | |
|
| In | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In |
If set to | |
|
| In |
If set to | |
|
| In |
If set to | |
|
| In |
If set to | |
|
| In |
If set to | |
|
| In | The definition of the virtual machine for this specific run. | |
|
| In | Indicates that this run configuration will be discarded even in the case of guest-initiated reboot. |
6.253.19.1. pause Copy linkLink copied to clipboard!
If set to true, start the virtual machine in paused mode. The default is false.
6.253.19.2. use_cloud_init Copy linkLink copied to clipboard!
If set to true, the initialization type is set to cloud-init. The default value is false. See cloud-init documentation for details.
6.253.19.3. use_ignition Copy linkLink copied to clipboard!
If set to true, the initialization type is set to Ignition. The default value is false. See Ignition documentation for details.
6.253.19.4. use_initialization Copy linkLink copied to clipboard!
If set to true, the initialization type is set by the VM’s OS. Windows will set to Sysprep, Linux to cloud-init and RedHat CoreOS to Ignition. If any of the initialization-types are explicitly set (useCloudInit, useSysprep or useIgnition), they will be prioritized and this flag will be ignored. The default value is false.
6.253.19.5. use_sysprep Copy linkLink copied to clipboard!
If set to true, the initialization type is set to Sysprep. The default value is false. See Sysprep for details.
6.253.19.6. vm Copy linkLink copied to clipboard!
The definition of the virtual machine for this specific run.
For example:
This will set the boot device to the CDROM only for this specific start. After the virtual machine is powered off, this definition will be reverted.
6.253.19.7. volatile Copy linkLink copied to clipboard!
Indicates that this run configuration will be discarded even in the case of guest-initiated reboot. The default value is false.
6.253.20. stop POST Copy linkLink copied to clipboard!
This operation forces a virtual machine to power-off.
For example:
POST /ovirt-engine/api/vms/123/stop
POST /ovirt-engine/api/vms/123/stop
The stop action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
To stop the VM even if a backup is running for it, the action should include the 'force' element.
For example, to force stop virtual machine 123:
POST /ovirt-engine/api/vms/123/stop
POST /ovirt-engine/api/vms/123/stop
<action>
<force>true</force>
</action>
<action>
<force>true</force>
</action>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the stop action should be performed asynchronously. | |
|
| In | Indicates if the VM should be forcibly stop even if a backup is running for it. | |
|
| In | The reason the virtual machine was stopped. |
6.253.20.1. reason Copy linkLink copied to clipboard!
The reason the virtual machine was stopped. Optionally set by user when shutting down the virtual machine.
6.253.21. suspend POST Copy linkLink copied to clipboard!
This operation saves the virtual machine state to disk and stops it. Start a suspended virtual machine and restore the virtual machine state with the start action.
For example:
POST /ovirt-engine/api/vms/123/suspend
POST /ovirt-engine/api/vms/123/suspend
The suspend action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the suspend action should be performed asynchronously. |
6.253.22. thawfilesystems POST Copy linkLink copied to clipboard!
Thaws virtual machine file systems.
This operation thaws a virtual machine’s file systems using the QEMU guest agent when taking a live snapshot of a running virtual machine. Normally, this is done automatically by the manager, but this must be executed manually with the API for virtual machines using OpenStack Volume (Cinder) disks.
Example:
POST /api/vms/123/thawfilesystems
POST /api/vms/123/thawfilesystems
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the thaw file systems action should be performed asynchronously. |
6.253.23. ticket POST Copy linkLink copied to clipboard!
Generates a time-sensitive authentication token for accessing a virtual machine’s display.
For example:
POST /ovirt-engine/api/vms/123/ticket
POST /ovirt-engine/api/vms/123/ticket
The client-provided action optionally includes a desired ticket value and/or an expiry time in seconds.
The response specifies the actual ticket value and expiry used.
If the virtual machine is configured to support only one graphics protocol then the generated authentication token will be valid for that protocol. But if the virtual machine is configured to support multiple protocols, VNC and SPICE, then the authentication token will only be valid for the SPICE protocol.
In order to obtain an authentication token for a specific protocol, for example for VNC, use the ticket method of the service, which manages the graphics consoles of the virtual machine, by sending a request:
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket
6.253.24. undosnapshot POST Copy linkLink copied to clipboard!
Restores the virtual machine to the state it had before previewing the snapshot.
See the preview_snapshot operation for details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the undo snapshot action should be performed asynchronously. |
6.253.25. update PUT Copy linkLink copied to clipboard!
Update the virtual machine in the system for the given virtual machine id.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In | Indicates if the update should be applied to the virtual machine immediately or if it should be applied only when the virtual machine is restarted. | |
|
| In/Out |
6.253.25.1. next_run Copy linkLink copied to clipboard!
Indicates if the update should be applied to the virtual machine immediately or if it should be applied only when the virtual machine is restarted. The default value is false, so by default changes are applied immediately.
6.254. VmApplication Copy linkLink copied to clipboard!
A service that provides information about an application installed in a virtual machine.
| Name | Summary |
|---|---|
|
| Returns the information about the application. |
6.254.1. get GET Copy linkLink copied to clipboard!
Returns the information about the application.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the application. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. |
6.254.1.1. application Copy linkLink copied to clipboard!
The information about the application.
The information consists of name attribute containing the name of the application (which is an arbitrary string that may also contain additional information such as version) and vm attribute identifying the virtual machine.
For example, a request like this:
GET /ovirt-engine/api/vms/123/applications/789
GET /ovirt-engine/api/vms/123/applications/789
May return information like this:
<application href="/ovirt-engine/api/vms/123/applications/789" id="789"> <name>ovirt-guest-agent-common-1.0.12-3.el7</name> <vm href="/ovirt-engine/api/vms/123" id="123"/> </application>
<application href="/ovirt-engine/api/vms/123/applications/789" id="789">
<name>ovirt-guest-agent-common-1.0.12-3.el7</name>
<vm href="/ovirt-engine/api/vms/123" id="123"/>
</application>
6.254.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.255. VmApplications Copy linkLink copied to clipboard!
A service that provides information about applications installed in a virtual machine.
| Name | Summary |
|---|---|
|
| Returns a list of applications installed in the virtual machine. |
6.255.1. list GET Copy linkLink copied to clipboard!
Returns a list of applications installed in the virtual machine.
The order of the returned list of applications isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A list of applications installed in the virtual machine. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of applications to return. |
6.255.1.1. applications Copy linkLink copied to clipboard!
A list of applications installed in the virtual machine.
For example, a request like this:
GET /ovirt-engine/api/vms/123/applications/
GET /ovirt-engine/api/vms/123/applications/
May return a list like this:
6.255.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.255.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of applications to return. If not specified all the applications are returned.
6.256. VmBackup Copy linkLink copied to clipboard!
A service managing a backup of a virtual machines.
| Name | Summary |
|---|---|
|
| Finalize the virtual machine backup entity. |
|
| Returns information about the virtual machine backup. |
6.256.1. finalize POST Copy linkLink copied to clipboard!
Finalize the virtual machine backup entity.
End backup, unlock resources, and perform cleanups. To finalize a virtual machine with an id '123' and a backup with an id '456' send a request as follows:
POST /ovirt-engine/api/vms/123/backups/456/finalize
POST /ovirt-engine/api/vms/123/backups/456/finalize
With a request body as follows:
<action />
<action />
6.256.2. get GET Copy linkLink copied to clipboard!
Returns information about the virtual machine backup.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the virtual machine backup entities. | |
|
| In | Indicates which inner links should be followed. |
6.256.2.1. backup Copy linkLink copied to clipboard!
The information about the virtual machine backup entities.
6.256.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.257. VmBackupDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves the description of the disk. |
6.257.1. get GET Copy linkLink copied to clipboard!
Retrieves the description of the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The description of the disk. | |
|
| In | Indicates which inner links should be followed. |
6.257.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.258. VmBackupDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of disks in backup. |
6.258.1. list GET Copy linkLink copied to clipboard!
Returns the list of disks in backup.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of retrieved disks. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. |
6.258.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.258.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified, all the disks are returned.
6.259. VmBackups Copy linkLink copied to clipboard!
Lists the backups of a virtual machine.
| Name | Summary |
|---|---|
|
| Adds a new backup entity to a virtual machine. |
|
| The list of virtual machine backups. |
6.259.1. add POST Copy linkLink copied to clipboard!
Adds a new backup entity to a virtual machine.
For example, to start a new incremental backup of a virtual machine since checkpoint id previous-checkpoint-uuid, send a request like this:
POST /ovirt-engine/api/vms/123/backups
POST /ovirt-engine/api/vms/123/backups
With a request body like this:
The response body:
To provide the ID of the created backup, send a request like this:
POST /ovirt-engine/api/vms/123/backups
POST /ovirt-engine/api/vms/123/backups
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The information about the virtual machine backup entity. | |
|
| In | Indicates if the backup will fail if VM failed to freeze or not. | |
|
| In | Indicate whether to use the active volume for performing the backup. |
6.259.1.1. require_consistency Copy linkLink copied to clipboard!
Indicates if the backup will fail if VM failed to freeze or not.
If requireConsistency=True VM backup will fail in case of a failure to freeze the VM.
The REST API call should look like this:
POST /ovirt-engine/api/vms/123/backups?require_consistency=true
POST /ovirt-engine/api/vms/123/backups?require_consistency=true
The default value of the requireConsistency flag is false.
6.259.1.2. use_active Copy linkLink copied to clipboard!
Indicate whether to use the active volume for performing the backup.
If useActive=False a snapshot will be created for the backup operation.
The REST API call should look like this:
POST /ovirt-engine/api/vms/123/backups?use_active=false
POST /ovirt-engine/api/vms/123/backups?use_active=false
The default value of the useActive flag is false.
6.259.2. list GET Copy linkLink copied to clipboard!
The list of virtual machine backups.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the virtual machine backup entities. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of virtual machine backups to return. |
6.259.2.1. backups Copy linkLink copied to clipboard!
The information about the virtual machine backup entities.
6.259.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.259.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machine backups to return. If not specified, all the virtual machine backups are returned.
6.260. VmCdrom Copy linkLink copied to clipboard!
Manages a CDROM device of a virtual machine.
Changing and ejecting the disk is done using always the update method, to change the value of the file attribute.
| Name | Summary |
|---|---|
|
| Returns the information about this CDROM device. |
|
| Updates the information about this CDROM device. |
6.260.1. get GET Copy linkLink copied to clipboard!
Returns the information about this CDROM device.
The information consists of cdrom attribute containing reference to the CDROM device, the virtual machine, and optionally the inserted disk.
If there is a disk inserted then the file attribute will contain a reference to the ISO image:
<cdrom href="..." id="00000000-0000-0000-0000-000000000000"> <file id="mycd.iso"/> <vm href="/ovirt-engine/api/vms/123" id="123"/> </cdrom>
<cdrom href="..." id="00000000-0000-0000-0000-000000000000">
<file id="mycd.iso"/>
<vm href="/ovirt-engine/api/vms/123" id="123"/>
</cdrom>
If there is no disk inserted then the file attribute won’t be reported:
<cdrom href="..." id="00000000-0000-0000-0000-000000000000"> <vm href="/ovirt-engine/api/vms/123" id="123"/> </cdrom>
<cdrom href="..." id="00000000-0000-0000-0000-000000000000">
<vm href="/ovirt-engine/api/vms/123" id="123"/>
</cdrom>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the CDROM device. | |
|
| In | Indicates if the operation should return the information for the currently running virtual machine. | |
|
| In | Indicates which inner links should be followed. |
6.260.1.1. current Copy linkLink copied to clipboard!
Indicates if the operation should return the information for the currently running virtual machine. This parameter is optional, and the default value is false.
6.260.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.260.2. update PUT Copy linkLink copied to clipboard!
Updates the information about this CDROM device.
It allows to change or eject the disk by changing the value of the file attribute. For example, to insert or change the disk send a request like this:
PUT /ovirt-engine/api/vms/123/cdroms/00000000-0000-0000-0000-000000000000
PUT /ovirt-engine/api/vms/123/cdroms/00000000-0000-0000-0000-000000000000
The body should contain the new value for the file attribute:
<cdrom> <file id="mycd.iso"/> </cdrom>
<cdrom>
<file id="mycd.iso"/>
</cdrom>
The value of the id attribute, mycd.iso in this example, should correspond to a file available in an attached ISO storage domain.
To eject the disk use a file with an empty id:
<cdrom> <file id=""/> </cdrom>
<cdrom>
<file id=""/>
</cdrom>
By default the above operations change permanently the disk that will be visible to the virtual machine after the next boot, but they do not have any effect on the currently running virtual machine. If you want to change the disk that is visible to the current running virtual machine, add the current=true parameter. For example, to eject the current disk send a request like this:
PUT /ovirt-engine/api/vms/123/cdroms/00000000-0000-0000-0000-000000000000?current=true
PUT /ovirt-engine/api/vms/123/cdroms/00000000-0000-0000-0000-000000000000?current=true
With a request body like this:
<cdrom> <file id=""/> </cdrom>
<cdrom>
<file id=""/>
</cdrom>
The changes made with the current=true parameter are never persisted, so they won’t have any effect after the virtual machine is rebooted.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The information about the CDROM device. | |
|
| In | Indicates if the update should apply to the currently running virtual machine, or to the virtual machine after the next boot. |
6.260.2.1. current Copy linkLink copied to clipboard!
Indicates if the update should apply to the currently running virtual machine, or to the virtual machine after the next boot. This parameter is optional, and the default value is false, which means that by default the update will have effect only after the next boot.
6.261. VmCdroms Copy linkLink copied to clipboard!
Manages the CDROM devices of a virtual machine.
Currently virtual machines have exactly one CDROM device. No new devices can be added, and the existing one can’t be removed, thus there are no add or remove methods. Changing and ejecting CDROM disks is done with the update method of the service that manages the CDROM device.
| Name | Summary |
|---|---|
|
| Add a cdrom to a virtual machine identified by the given id. |
|
| Returns the list of CDROM devices of the virtual machine. |
6.261.1. add POST Copy linkLink copied to clipboard!
Add a cdrom to a virtual machine identified by the given id.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.261.2. list GET Copy linkLink copied to clipboard!
Returns the list of CDROM devices of the virtual machine.
The order of the returned list of CD-ROM devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of CDROM devices of the virtual machine. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of CDROMs to return. |
6.261.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.261.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of CDROMs to return. If not specified all the CDROMs are returned.
6.262. VmCheckpoint Copy linkLink copied to clipboard!
A service managing a checkpoint of a virtual machines.
| Name | Summary |
|---|---|
|
| Returns information about the virtual machine checkpoint. |
|
| Remove the virtual machine checkpoint entity. |
6.262.1. get GET Copy linkLink copied to clipboard!
Returns information about the virtual machine checkpoint.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the virtual machine checkpoint entity. | |
|
| In | Indicates which inner links should be followed. |
6.262.1.1. checkpoint Copy linkLink copied to clipboard!
The information about the virtual machine checkpoint entity.
6.262.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.262.2. remove DELETE Copy linkLink copied to clipboard!
Remove the virtual machine checkpoint entity.
Remove the checkpoint from libvirt and the database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.263. VmCheckpointDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves the description of the disk. |
6.263.1. get GET Copy linkLink copied to clipboard!
Retrieves the description of the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The description of the disk. | |
|
| In | Indicates which inner links should be followed. |
6.263.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.264. VmCheckpointDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of disks in checkpoint. |
6.264.1. list GET Copy linkLink copied to clipboard!
Returns the list of disks in checkpoint.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of retrieved disks. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. |
6.264.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.264.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified, all the disks are returned.
6.265. VmCheckpoints Copy linkLink copied to clipboard!
Lists the checkpoints of a virtual machine.
| Name | Summary |
|---|---|
|
| The list of virtual machine checkpoints. |
6.265.1. list GET Copy linkLink copied to clipboard!
The list of virtual machine checkpoints.
To get a list of checkpoints for a virtual machine with an id '123', send a request as follows:
GET /ovirt-engine/api/vms/123/checkpoints
GET /ovirt-engine/api/vms/123/checkpoints
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the virtual machine checkpoint entities. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of virtual machine checkpoints to return. |
6.265.1.1. checkpoints Copy linkLink copied to clipboard!
The information about the virtual machine checkpoint entities.
6.265.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.265.1.3. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machine checkpoints to return. If not specified, all the virtual machine checkpoints are returned.
6.266. VmDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| Reduces the size of the disk image. |
|
| Detach the disk from the virtual machine. |
|
|
6.266.1. activate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.266.2. deactivate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. |
6.266.3. export POST Copy linkLink copied to clipboard!
6.266.4. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. |
6.266.4.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.266.5. move POST Copy linkLink copied to clipboard!
6.266.6. reduce POST Copy linkLink copied to clipboard!
Reduces the size of the disk image.
Invokes reduce on the logical volume (i.e. this is only applicable for block storage domains). This is applicable for floating disks and disks attached to non-running virtual machines. There is no need to specify the size as the optimal size is calculated automatically.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.266.7. remove DELETE Copy linkLink copied to clipboard!
Detach the disk from the virtual machine.
In version 3 of the API this used to also remove the disk completely from the system, but starting with version 4 it doesn’t. If you need to remove it completely use the remove method of the top level disk service.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.266.8. update PUT Copy linkLink copied to clipboard!
6.267. VmDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Returns the list of disks of the virtual machine. |
6.267.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.267.2. list GET Copy linkLink copied to clipboard!
Returns the list of disks of the virtual machine.
The order of the returned list of disks isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of disks to return. |
6.267.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.267.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.268. VmGraphicsConsole Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves the graphics console configuration of the virtual machine. |
|
| |
|
|
Generates the file which is compatible with |
|
| Remove the graphics console from the virtual machine. |
|
| Generates a time-sensitive authentication token for accessing this virtual machine’s console. |
6.268.1. get GET Copy linkLink copied to clipboard!
Retrieves the graphics console configuration of the virtual machine.
By default, when the current parameter is not specified, the data returned corresponds to the next execution of the virtual machine. In the current implementation of the system this means that the address and port attributes will not be populated because the system does not know what address and port will be used for the next execution. Since in most cases those attributes are needed, it is strongly advised to aways explicitly include the current parameter with the value true.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the graphics console of the virtual machine. | |
|
| In | Specifies if the data returned should correspond to the next execution of the virtual machine, or to the current execution. | |
|
| In | Indicates which inner links should be followed. |
6.268.1.1. current Copy linkLink copied to clipboard!
Specifies if the data returned should correspond to the next execution of the virtual machine, or to the current execution.
The address and port attributes will not be populated unless the value is true.
For example, to get data for the current execution of the virtual machine, including the address and port attributes, send a request like this:
GET /ovit-engine/api/vms/123/graphicsconsoles/456?current=true
GET /ovit-engine/api/vms/123/graphicsconsoles/456?current=true
The default value is false.
6.268.1.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.268.2. proxyticket POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the generation of the ticket should be performed asynchronously. | |
|
| Out |
6.268.3. remoteviewerconnectionfile POST Copy linkLink copied to clipboard!
Generates the file which is compatible with remote-viewer client.
Use the following request to generate remote viewer connection file of the graphics console. Note that this action generates the file only if virtual machine is running.
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/remoteviewerconnectionfile
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/remoteviewerconnectionfile
The remoteviewerconnectionfile action does not take any action specific parameters, so the request body should contain an empty action:
<action/>
<action/>
The response contains the file, which can be used with remote-viewer client.
E.g., to fetch the content of remote viewer connection file and save it into temporary file, user can use oVirt Python SDK as follows:
When you create the remote viewer connection file, then you can connect to virtual machine graphic console, as follows:
#!/bin/sh -ex remote-viewer --ovirt-ca-file=/etc/pki/ovirt-engine/ca.pem /tmp/remote_viewer_connection_file.vv
#!/bin/sh -ex
remote-viewer --ovirt-ca-file=/etc/pki/ovirt-engine/ca.pem /tmp/remote_viewer_connection_file.vv
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
Contains the file which is compatible with |
6.268.3.1. remote_viewer_connection_file Copy linkLink copied to clipboard!
Contains the file which is compatible with remote-viewer client.
User can use the content of this attribute to create a file, which can be passed to remote-viewer client to connect to virtual machine graphic console.
6.268.4. remove DELETE Copy linkLink copied to clipboard!
Remove the graphics console from the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.268.5. ticket POST Copy linkLink copied to clipboard!
Generates a time-sensitive authentication token for accessing this virtual machine’s console.
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket
The client-provided action optionally includes a desired ticket value and/or an expiry time in seconds.
In any case, the response specifies the actual ticket value and expiry used.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The generated ticket that can be used to access this console. |
6.269. VmGraphicsConsoles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add new graphics console to the virtual machine. |
|
| Lists all the configured graphics consoles of the virtual machine. |
6.269.1. add POST Copy linkLink copied to clipboard!
Add new graphics console to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.269.2. list GET Copy linkLink copied to clipboard!
Lists all the configured graphics consoles of the virtual machine.
By default, when the current parameter is not specified, the data returned corresponds to the next execution of the virtual machine. In the current implementation of the system this means that the address and port attributes will not be populated because the system does not know what address and port will be used for the next execution. Since in most cases those attributes are needed, it is strongly advised to aways explicitly include the current parameter with the value true.
The order of the returned list of graphics consoles is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of graphics consoles of the virtual machine. | |
|
| In | Specifies if the data returned should correspond to the next execution of the virtual machine, or to the current execution. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of consoles to return. |
6.269.2.1. current Copy linkLink copied to clipboard!
Specifies if the data returned should correspond to the next execution of the virtual machine, or to the current execution.
The address and port attributes will not be populated unless the value is true.
For example, to get data for the current execution of the virtual machine, including the address and port attributes, send a request like this:
GET /ovirt-engine/api/vms/123/graphicsconsoles?current=true
GET /ovirt-engine/api/vms/123/graphicsconsoles?current=true
The default value is false.
6.269.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.269.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
6.270. VmHostDevice Copy linkLink copied to clipboard!
A service to manage individual host device attached to a virtual machine.
| Name | Summary |
|---|---|
|
| Retrieve information about particular host device attached to given virtual machine. |
|
| Remove the attachment of this host device from given virtual machine. |
6.270.1. get GET Copy linkLink copied to clipboard!
Retrieve information about particular host device attached to given virtual machine.
Example:
GET /ovirt-engine/api/vms/123/hostdevices/456
GET /ovirt-engine/api/vms/123/hostdevices/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved information about the host device attached to given virtual machine. | |
|
| In | Indicates which inner links should be followed. |
6.270.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.270.2. remove DELETE Copy linkLink copied to clipboard!
Remove the attachment of this host device from given virtual machine.
In case this device serves as an IOMMU placeholder, it cannot be removed (remove will result only in setting its placeholder flag to true). Note that all IOMMU placeholder devices will be removed automatically as soon as there will be no more non-placeholder devices (all devices from given IOMMU group are detached).
DELETE /ovirt-engine/api/vms/123/hostdevices/456
DELETE /ovirt-engine/api/vms/123/hostdevices/456
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.271. VmHostDevices Copy linkLink copied to clipboard!
A service to manage host devices attached to a virtual machine.
| Name | Summary |
|---|---|
|
| Attach target device to given virtual machine. |
|
| List the host devices assigned to given virtual machine. |
6.271.1. add POST Copy linkLink copied to clipboard!
Attach target device to given virtual machine.
Example:
POST /ovirt-engine/api/vms/123/hostdevices
POST /ovirt-engine/api/vms/123/hostdevices
With request body of type HostDevice, for example
<host_device id="123" />
<host_device id="123" />
A necessary precondition for a successful host device attachment is that the virtual machine must be pinned to exactly one host. The device ID is then taken relative to this host.
Attachment of a PCI device that is part of a bigger IOMMU group will result in attachment of the remaining devices from that IOMMU group as "placeholders". These devices are then identified using the placeholder attribute of the HostDevice type set to true.
In case you want attach a device that already serves as an IOMMU placeholder, simply issue an explicit Add operation for it, and its placeholder flag will be cleared, and the device will be accessible to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The host device to be attached to given virtual machine. |
6.271.2. list GET Copy linkLink copied to clipboard!
List the host devices assigned to given virtual machine.
The order of the returned list of devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved list of host devices attached to given virtual machine. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of devices to return. |
6.271.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.271.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of devices to return. If not specified all the devices are returned.
6.272. VmMediatedDevice Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves the configuration of mediated devices in the virtual machine. |
|
| Remove the mediated device from the virtual machine. |
|
| Updates the information about the mediated device. |
6.272.1. get GET Copy linkLink copied to clipboard!
Retrieves the configuration of mediated devices in the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the mediated device of the virtual machine. | |
|
| In | Indicates which inner links should be followed. |
6.272.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.272.2. remove DELETE Copy linkLink copied to clipboard!
Remove the mediated device from the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.272.3. update PUT Copy linkLink copied to clipboard!
Updates the information about the mediated device.
You can update the information using specParams element.
For example, to update a mediated device, send a request like this:
with response body:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The information about the mediated device. |
6.272.3.1. device Copy linkLink copied to clipboard!
The information about the mediated device.
The request data must contain specParams properties. The response data contains complete information about the updated mediated device.
6.273. VmMediatedDevices Copy linkLink copied to clipboard!
A service that manages mediated devices of a VM.
| Name | Summary |
|---|---|
|
| Add a new mediated device to the virtual machine. |
|
| Lists all the configured mediated devices of the virtual machine. |
6.273.1. add POST Copy linkLink copied to clipboard!
Add a new mediated device to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.273.2. list GET Copy linkLink copied to clipboard!
Lists all the configured mediated devices of the virtual machine.
The order of the returned list of mediated devices is not guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of mediated devices of the virtual machine. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of mediated devices to return. |
6.273.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.273.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of mediated devices to return. If not specified all the mediated devices are returned.
6.274. VmNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| Removes the NIC. |
|
| Updates the NIC. |
6.274.1. activate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.274.2. deactivate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. |
6.274.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.274.3.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.274.4. remove DELETE Copy linkLink copied to clipboard!
Removes the NIC.
For example, to remove the NIC with id 456 from the virtual machine with id 123 send a request like this:
DELETE /ovirt-engine/api/vms/123/nics/456
DELETE /ovirt-engine/api/vms/123/nics/456
The hotplugging feature only supports virtual machine operating systems with hotplugging operations. Example operating systems include:
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
- Windows Server 2008 and
- Windows Server 2003
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.274.5. update PUT Copy linkLink copied to clipboard!
Updates the NIC.
For example, to update the NIC having with 456 belonging to virtual the machine with id 123 send a request like this:
PUT /ovirt-engine/api/vms/123/nics/456
PUT /ovirt-engine/api/vms/123/nics/456
With a request body like this:
<nic> <name>mynic</name> <interface>e1000</interface> <vnic_profile id='789'/> </nic>
<nic>
<name>mynic</name>
<interface>e1000</interface>
<vnic_profile id='789'/>
</nic>
The hotplugging feature only supports virtual machine operating systems with hotplugging operations. Example operating systems include:
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
- Windows Server 2008 and
- Windows Server 2003
6.275. VmNics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Adds a NIC to the virtual machine. |
|
| Returns the list of NICs of the virtual machine. |
6.275.1. add POST Copy linkLink copied to clipboard!
Adds a NIC to the virtual machine.
The following example adds to the virtual machine 123 a network interface named mynic using virtio and the NIC profile 456.
POST /ovirt-engine/api/vms/123/nics
POST /ovirt-engine/api/vms/123/nics
<nic> <name>mynic</name> <interface>virtio</interface> <vnic_profile id="456"/> </nic>
<nic>
<name>mynic</name>
<interface>virtio</interface>
<vnic_profile id="456"/>
</nic>
The following example sends that request using curl:
The hotplugging feature only supports virtual machine operating systems with hotplugging operations. Example operating systems include:
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
- Windows Server 2008 and
- Windows Server 2003
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.275.2. list GET Copy linkLink copied to clipboard!
Returns the list of NICs of the virtual machine.
The order of the returned list of NICs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of NICs to return. | |
|
| Nic[] | Out |
6.275.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.275.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.276. VmNumaNode Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a virtual NUMA node. |
|
| Updates a virtual NUMA node. |
6.276.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.276.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.276.2. remove DELETE Copy linkLink copied to clipboard!
Removes a virtual NUMA node.
An example of removing a virtual NUMA node:
DELETE /ovirt-engine/api/vms/123/numanodes/456
DELETE /ovirt-engine/api/vms/123/numanodes/456
It’s required to remove the numa nodes from the highest index first.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.276.3. update PUT Copy linkLink copied to clipboard!
Updates a virtual NUMA node.
An example of pinning a virtual NUMA node to a physical NUMA node on the host:
PUT /ovirt-engine/api/vms/123/numanodes/456
PUT /ovirt-engine/api/vms/123/numanodes/456
The request body should contain the following:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.277. VmNumaNodes Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new virtual NUMA node for the virtual machine. |
|
| Lists virtual NUMA nodes of a virtual machine. |
6.277.1. add POST Copy linkLink copied to clipboard!
Creates a new virtual NUMA node for the virtual machine.
An example of creating a NUMA node:
POST /ovirt-engine/api/vms/c7ecd2dc/numanodes Accept: application/xml Content-type: application/xml
POST /ovirt-engine/api/vms/c7ecd2dc/numanodes
Accept: application/xml
Content-type: application/xml
The request body can contain the following:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.277.2. list GET Copy linkLink copied to clipboard!
Lists virtual NUMA nodes of a virtual machine.
The order of the returned list of NUMA nodes isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of nodes to return. | |
|
| Out |
6.277.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.277.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of nodes to return. If not specified all the nodes are returned.
6.278. VmPool Copy linkLink copied to clipboard!
A service to manage a virtual machines pool.
| Name | Summary |
|---|---|
|
| This operation allocates a virtual machine in the virtual machine pool. |
|
| Get the virtual machine pool. |
|
| Removes a virtual machine pool. |
|
| Update the virtual machine pool. |
6.278.1. allocatevm POST Copy linkLink copied to clipboard!
This operation allocates a virtual machine in the virtual machine pool.
POST /ovirt-engine/api/vmpools/123/allocatevm
POST /ovirt-engine/api/vmpools/123/allocatevm
The allocate virtual machine action does not take any action specific parameters, so the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the allocation should be performed asynchronously. |
6.278.2. get GET Copy linkLink copied to clipboard!
Get the virtual machine pool.
GET /ovirt-engine/api/vmpools/123
GET /ovirt-engine/api/vmpools/123
You will get a XML response like that one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out | Retrieved virtual machines pool. |
6.278.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.278.3. remove DELETE Copy linkLink copied to clipboard!
Removes a virtual machine pool.
DELETE /ovirt-engine/api/vmpools/123
DELETE /ovirt-engine/api/vmpools/123
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.278.4. update PUT Copy linkLink copied to clipboard!
Update the virtual machine pool.
PUT /ovirt-engine/api/vmpools/123
PUT /ovirt-engine/api/vmpools/123
The name, description, size, prestarted_vms and max_user_vms attributes can be updated after the virtual machine pool has been created.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The virtual machine pool that is being updated. | |
|
| In | Specifies if virtual machines created for the pool should be sealed after creation. |
6.278.4.1. seal Copy linkLink copied to clipboard!
Specifies if virtual machines created for the pool should be sealed after creation.
If this optional parameter is provided, and its value is true, virtual machines created for the pool will be sealed after creation. If the value is 'false', the virtual machines will not be sealed. If the parameter is not provided, the virtual machines will be sealed, only if they are created from a sealed template and their guest OS is not set to Windows. This parameter affects only the virtual machines created when the pool is updated.
For example, to update a virtual machine pool and to seal the additional virtual machines that are created, send a request like this:
PUT /ovirt-engine/api/vmpools/123?seal=true
PUT /ovirt-engine/api/vmpools/123?seal=true
With the following body:
<vmpool> <name>VM_Pool_B</name> <description>Virtual Machine Pool B</description> <size>7</size> </vmpool>
<vmpool>
<name>VM_Pool_B</name>
<description>Virtual Machine Pool B</description>
<size>7</size>
</vmpool>
6.279. VmPools Copy linkLink copied to clipboard!
Provides read-write access to virtual machines pools.
| Name | Summary |
|---|---|
|
| Creates a new virtual machine pool. |
|
| Get a list of available virtual machines pools. |
6.279.1. add POST Copy linkLink copied to clipboard!
Creates a new virtual machine pool.
A new pool requires the name, cluster and template attributes. Identify the cluster and template with the id or name nested attributes:
POST /ovirt-engine/api/vmpools
POST /ovirt-engine/api/vmpools
With the following body:
<vmpool> <name>mypool</name> <cluster id="123"/> <template id="456"/> </vmpool>
<vmpool>
<name>mypool</name>
<cluster id="123"/>
<template id="456"/>
</vmpool>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Pool to add. | |
|
| In | Specifies if virtual machines created for the pool should be sealed after creation. |
6.279.1.1. seal Copy linkLink copied to clipboard!
Specifies if virtual machines created for the pool should be sealed after creation.
If this optional parameter is provided, and its value is true, virtual machines created for the pool will be sealed after creation. If the value is 'false', the virtual machines will not be sealed. If the parameter is not provided, the virtual machines will be sealed, only if they are created from a sealed template and their guest OS is not set to Windows. This parameter affects only the virtual machines created when the pool is created.
For example, to create a virtual machine pool with 5 virtual machines and to seal them, send a request like this:
POST /ovirt-engine/api/vmpools?seal=true
POST /ovirt-engine/api/vmpools?seal=true
With the following body:
6.279.2. list GET Copy linkLink copied to clipboard!
Get a list of available virtual machines pools.
GET /ovirt-engine/api/vmpools
GET /ovirt-engine/api/vmpools
You will receive the following response:
The order of the returned list of pools is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of pools to return. | |
|
| Out | Retrieved pools. | |
|
| In | A query string used to restrict the returned pools. |
6.279.2.1. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.279.2.2. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.279.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of pools to return. If this value is not specified, all of the pools are returned.
6.280. VmReportedDevice Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.280.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.280.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.281. VmReportedDevices Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Returns the list of reported devices of the virtual machine. |
6.281.1. list GET Copy linkLink copied to clipboard!
Returns the list of reported devices of the virtual machine.
The order of the returned list of devices isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of devices to return. | |
|
| Out |
6.281.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.281.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of devices to return. If not specified all the devices are returned.
6.282. VmSession Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.282.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.282.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.283. VmSessions Copy linkLink copied to clipboard!
Provides information about virtual machine user sessions.
| Name | Summary |
|---|---|
|
| Lists all user sessions for this virtual machine. |
6.283.1. list GET Copy linkLink copied to clipboard!
Lists all user sessions for this virtual machine.
For example, to retrieve the session information for virtual machine 123 send a request like this:
GET /ovirt-engine/api/vms/123/sessions
GET /ovirt-engine/api/vms/123/sessions
The response body will contain something like this:
The order of the returned list of sessions isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of sessions to return. | |
|
| Out |
6.283.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.283.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of sessions to return. If not specified all the sessions are returned.
6.284. VmWatchdog Copy linkLink copied to clipboard!
A service managing a watchdog on virtual machines.
| Name | Summary |
|---|---|
|
| Returns the information about the watchdog. |
|
| Removes the watchdog from the virtual machine. |
|
| Updates the information about the watchdog. |
6.284.1. get GET Copy linkLink copied to clipboard!
Returns the information about the watchdog.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out | The information about the watchdog. |
6.284.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.284.1.2. watchdog Copy linkLink copied to clipboard!
The information about the watchdog.
The information consists of model element, action element and the reference to the virtual machine. It may look like this:
6.284.2. remove DELETE Copy linkLink copied to clipboard!
Removes the watchdog from the virtual machine.
For example, to remove a watchdog from a virtual machine, send a request like this:
DELETE /ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000
DELETE /ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.284.3. update PUT Copy linkLink copied to clipboard!
Updates the information about the watchdog.
You can update the information using action and model elements.
For example, to update a watchdog, send a request like this:
PUT /ovirt-engine/api/vms/123/watchdogs <watchdog> <action>reset</action> </watchdog>
PUT /ovirt-engine/api/vms/123/watchdogs
<watchdog>
<action>reset</action>
</watchdog>
with response body:
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <vm href="/ovirt-engine/api/vms/123" id="123"/> <action>reset</action> <model>i6300esb</model> </watchdog>
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000">
<vm href="/ovirt-engine/api/vms/123" id="123"/>
<action>reset</action>
<model>i6300esb</model>
</watchdog>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The information about the watchdog. |
6.284.3.1. watchdog Copy linkLink copied to clipboard!
The information about the watchdog.
The request data must contain at least one of model and action elements. The response data contains complete information about the updated watchdog.
6.285. VmWatchdogs Copy linkLink copied to clipboard!
Lists the watchdogs of a virtual machine.
| Name | Summary |
|---|---|
|
| Adds new watchdog to the virtual machine. |
|
| The list of watchdogs of the virtual machine. |
6.285.1. add POST Copy linkLink copied to clipboard!
Adds new watchdog to the virtual machine.
For example, to add a watchdog to a virtual machine, send a request like this:
POST /ovirt-engine/api/vms/123/watchdogs <watchdog> <action>poweroff</action> <model>i6300esb</model> </watchdog>
POST /ovirt-engine/api/vms/123/watchdogs
<watchdog>
<action>poweroff</action>
<model>i6300esb</model>
</watchdog>
with response body:
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <vm href="/ovirt-engine/api/vms/123" id="123"/> <action>poweroff</action> <model>i6300esb</model> </watchdog>
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000">
<vm href="/ovirt-engine/api/vms/123" id="123"/>
<action>poweroff</action>
<model>i6300esb</model>
</watchdog>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The information about the watchdog. |
6.285.1.1. watchdog Copy linkLink copied to clipboard!
The information about the watchdog.
The request data must contain model element (such as i6300esb) and action element (one of none, reset, poweroff, dump, pause). The response data additionally contains references to the added watchdog and to the virtual machine.
6.285.2. list GET Copy linkLink copied to clipboard!
The list of watchdogs of the virtual machine.
The order of the returned list of watchdogs isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of watchdogs to return. | |
|
| Out | The information about the watchdog. |
6.285.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.285.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
6.285.2.3. watchdogs Copy linkLink copied to clipboard!
The information about the watchdog.
The information consists of model element, action element and the reference to the virtual machine. It may look like this:
6.286. Vms Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new virtual machine. |
|
| Returns the list of virtual machines of the system. |
6.286.1. add POST Copy linkLink copied to clipboard!
Creates a new virtual machine.
The virtual machine can be created in different ways:
- From a template. In this case the identifier or name of the template must be provided. For example, using a plain shell script and XML:
- From a snapshot. In this case the identifier of the snapshot has to be provided. For example, using a plain shel script and XML:
When creating a virtual machine from a template or from a snapshot it is usually useful to explicitly indicate in what storage domain to create the disks for the virtual machine. If the virtual machine is created from a template then this is achieved passing a set of disk_attachment elements that indicate the mapping:
When the virtual machine is created from a snapshot this set of disks is slightly different, it uses the image_id attribute instead of id.
It is possible to specify additional virtual machine parameters in the XML description, e.g. a virtual machine of desktop type, with 2 GiB of RAM and additional description can be added sending a request body like the following:
A bootable CDROM device can be set like this:
In order to boot from CDROM, you first need to insert a disk, as described in the CDROM service. Then booting from that CDROM can be specified using the os.boot.devices attribute:
In all cases the name or identifier of the cluster where the virtual machine will be created is mandatory.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Specifies if and how the auto CPU and NUMA configuration is applied. | |
|
| In | Specifies if the virtual machine should be independent of the template. | |
|
| In | Specifies if the permissions of the template should be copied to the virtual machine. | |
|
| In | Relevant for admin users only. | |
|
| In | Specifies if the virtual machine should be sealed after creation. | |
|
| In/Out |
6.286.1.1. auto_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the auto CPU and NUMA configuration is applied.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. Instead please use POST followed by add operation.
An example for a request:
POST /ovirt-engine/api/vms?auto_pinning_policy=existing/adjust
POST /ovirt-engine/api/vms?auto_pinning_policy=existing/adjust
With a request body like this:
6.286.1.2. clone Copy linkLink copied to clipboard!
Specifies if the virtual machine should be independent of the template.
When a virtual machine is created from a template by default the disks of the virtual machine depend on the disks of the template, they are using the copy on write mechanism so that only the differences from the template take up real storage space. If this parameter is specified and the value is true then the disks of the created virtual machine will be cloned, and independent of the template. For example, to create an independent virtual machine, send a request like this:
POST /ovirt-engine/vms?clone=true
POST /ovirt-engine/vms?clone=true
With a request body like this:
When this parameter is true the permissions of the template will also be copied, as when using clone_permissions=true.
6.286.1.3. clone_permissions Copy linkLink copied to clipboard!
Specifies if the permissions of the template should be copied to the virtual machine.
If this optional parameter is provided, and its values is true then the permissions of the template (only the direct ones, not the inherited ones) will be copied to the created virtual machine. For example, to create a virtual machine from the mytemplate template copying its permissions, send a request like this:
POST /ovirt-engine/api/vms?clone_permissions=true
POST /ovirt-engine/api/vms?clone_permissions=true
With a request body like this:
6.286.1.4. filter Copy linkLink copied to clipboard!
Relevant for admin users only. Indicates whether to assign UserVmManager role on the created Virtual Machine for this user. This will enable the user to later access the Virtual Machine as though he were a non-admin user, foregoing his admin permissions (by providing filter=true).
admin-as-user (meaning providing filter=true) POST requests on an existing Virtual Machine will fail unless the Virtual Machine has been previously created by the admin as a user (meaning with filter=true).
6.286.1.5. seal Copy linkLink copied to clipboard!
Specifies if the virtual machine should be sealed after creation.
If this optional parameter is provided, and its value is true, the virtual machine will be sealed after creation. If the value is 'false', the virtual machine will not be sealed. If the parameter is not provided, the virtual machine will be sealed, only if it is created from a sealed template and its guest OS is not set to Windows.
For example, to create a virtual machine from the mytemplate template and to seal it, send a request like this:
POST /ovirt-engine/api/vms?seal=true
POST /ovirt-engine/api/vms?seal=true
With a request body like this:
6.286.2. list GET Copy linkLink copied to clipboard!
Returns the list of virtual machines of the system.
The order of the returned list of virtual machines is guaranteed only if the sortby clause is included in the search parameter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all the attributes of the virtual machines should be included in the response. | |
|
| In |
Indicates if the search performed using the | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | The maximum number of results to return. | |
|
| In | Indicates if the results should expose the OVF as it appears in OVA files of that VM. | |
|
| In | A query string used to restrict the returned virtual machines. | |
|
| Vm[] | Out |
6.286.2.1. all_content Copy linkLink copied to clipboard!
Indicates if all the attributes of the virtual machines should be included in the response.
By default the following attributes are excluded:
-
console -
initialization.configuration.data- The OVF document describing the virtual machine. -
rng_source -
soundcard -
virtio_scsi
For example, to retrieve the complete representation of the virtual machines send a request like this:
GET /ovirt-engine/api/vms?all_content=true
GET /ovirt-engine/api/vms?all_content=true
The reason for not including these attributes is performance: they are seldom used and they require additional queries to the database. So try to use the this parameter only when it is really needed.
6.286.2.2. case_sensitive Copy linkLink copied to clipboard!
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.286.2.3. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.286.2.4. ovf_as_ova Copy linkLink copied to clipboard!
Indicates if the results should expose the OVF as it appears in OVA files of that VM. The OVF document describing the virtual machine. This parameter will work only when all_content=True is set. The OVF will be presented in initialization.configuration.data.
For example:
GET /vms?all_content=true&ovf_as_ova=true
GET /vms?all_content=true&ovf_as_ova=true
6.287. VnicProfile Copy linkLink copied to clipboard!
This service manages a vNIC profile.
| Name | Summary |
|---|---|
|
| Retrieves details about a vNIC profile. |
|
| Removes the vNIC profile. |
|
| Updates details of a vNIC profile. |
6.287.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.287.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.287.2. remove DELETE Copy linkLink copied to clipboard!
Removes the vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.287.3. update PUT Copy linkLink copied to clipboard!
Updates details of a vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The vNIC profile that is being updated. |
6.288. VnicProfiles Copy linkLink copied to clipboard!
This service manages the collection of all vNIC profiles.
| Name | Summary |
|---|---|
|
| Add a vNIC profile. |
|
| List all vNIC profiles. |
6.288.1. add POST Copy linkLink copied to clipboard!
Add a vNIC profile.
For example to add vNIC profile 123 to network 456 send a request to:
POST /ovirt-engine/api/networks/456/vnicprofiles
POST /ovirt-engine/api/networks/456/vnicprofiles
With the following body:
Please note that there is a default network filter to each VNIC profile. For more details of how the default network filter is calculated please refer to the documentation in NetworkFilters.
The automatically created vNIC profile for the external network will be without network filter.
The output of creating a new VNIC profile depends in the body arguments that were given. In case no network filter was given, the default network filter will be configured. For example:
In case an empty network filter was given, no network filter will be configured for the specific VNIC profile regardless of the VNIC profile’s default network filter. For example:
<vnic_profile> <name>no_network_filter</name> <network_filter/> </vnic_profile>
<vnic_profile>
<name>no_network_filter</name>
<network_filter/>
</vnic_profile>
In case that a specific valid network filter id was given, the VNIC profile will be configured with the given network filter regardless of the VNIC profiles’s default network filter. For example:
<vnic_profile> <name>user_choice_network_filter</name> <network_filter id= "0000001b-001b-001b-001b-0000000001d5"/> </vnic_profile>
<vnic_profile>
<name>user_choice_network_filter</name>
<network_filter id= "0000001b-001b-001b-001b-0000000001d5"/>
</vnic_profile>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The vNIC profile that is being added. |
6.288.2. list GET Copy linkLink copied to clipboard!
List all vNIC profiles.
The order of the returned list of vNIC profiles isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of profiles to return. | |
|
| Out | The list of all vNIC profiles. |
6.288.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.288.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.289. Weight Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.289.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| Out |
6.289.1.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.289.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.290. Weights Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add a weight to a specified user defined scheduling policy. |
|
| Returns the list of weights. |
6.290.1. add POST Copy linkLink copied to clipboard!
Add a weight to a specified user defined scheduling policy.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.290.2. list GET Copy linkLink copied to clipboard!
Returns the list of weights.
The order of the returned list of weights isn’t guaranteed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates which inner links should be followed. | |
|
| In | Sets the maximum number of weights to return. | |
|
| Out |
6.290.2.1. follow Copy linkLink copied to clipboard!
Indicates which inner links should be followed. The objects referenced by these links will be fetched as part of the current request. See here for details.
6.290.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of weights to return. If not specified all the weights are returned.
Chapter 7. Types Copy linkLink copied to clipboard!
This section enumerates all the data types that are available in the API.
7.1. AccessProtocol enum Copy linkLink copied to clipboard!
Represents the access protocols supported by Gluster volumes. gluster and nfs are enabled by default.
| Name | Summary |
|---|---|
|
| CIFS access protocol. |
|
| Gluster access protocol. |
|
| NFS access protocol. |
7.2. Action struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| Free text containing comments about this object. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| A human-readable description in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.3. AffinityGroup struct Copy linkLink copied to clipboard!
An affinity group represents a group of virtual machines with a defined relationship.
| Name | Type | Summary |
|---|---|---|
|
| Specifies if the affinity group is broken. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| Specifies whether the affinity group uses hard or soft enforcement of the affinity applied to virtual machines that are members of that affinity group. | |
|
| Specifies the affinity rule applied between virtual machines and hosts that are members of this affinity group. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Specifies whether the affinity group applies positive affinity or negative affinity to virtual machines that are members of that affinity group. | |
|
| Priority of the affinity group. | |
|
| Specifies the affinity rule applied to virtual machines that are members of this affinity group. |
7.3.1. broken Copy linkLink copied to clipboard!
Specifies if the affinity group is broken. Affinity group is considered broken when any of its rules are not satisfied. Broken field is a computed field in the engine. Because of that, this field is only usable in GET requests.
7.3.2. enforcing Copy linkLink copied to clipboard!
Specifies whether the affinity group uses hard or soft enforcement of the affinity applied to virtual machines that are members of that affinity group.
Please note that this attribute has been deprecated since version 4.1 of the engine, and will be removed in the future. Use the vms_rule attribute from now on.
7.3.3. positive Copy linkLink copied to clipboard!
Specifies whether the affinity group applies positive affinity or negative affinity to virtual machines that are members of that affinity group.
Please note that this attribute has been deprecated since version 4.1 of the engine, and will be removed in the future. Use the vms_rule attribute from now on.
| Name | Type | Summary |
|---|---|---|
|
| A reference to the cluster to which the affinity group applies. | |
|
| A list of all host labels assigned to this affinity group. | |
|
| A list of all hosts assigned to this affinity group. | |
|
| A list of all virtual machine labels assigned to this affinity group. | |
|
| Vm[] | A list of all virtual machines assigned to this affinity group. |
7.4. AffinityLabel struct Copy linkLink copied to clipboard!
The affinity label can influence virtual machine scheduling. It is most frequently used to create a sub-cluster from the available hosts.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| This property enables the legacy behavior for labels. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
The |
7.4.1. has_implicit_affinity_group Copy linkLink copied to clipboard!
This property enables the legacy behavior for labels. If true, the label acts also as a positive enforcing VM-to-host affinity group.
This parameter is only used for clusters with compatibility version 4.3 or lower.
7.4.2. read_only Copy linkLink copied to clipboard!
The read_only property marks a label that can not be modified. This is usually the case when listing internally-generated labels.
7.5. AffinityRule struct Copy linkLink copied to clipboard!
Generic rule definition for affinity group. Each supported resource type (virtual machine, host) is controlled by a separate rule. This allows expressing of rules like: no affinity between defined virtual machines, but hard affinity between defined virtual machines and virtual hosts.
| Name | Type | Summary |
|---|---|---|
|
| Specifies whether the affinity group uses this rule or not. | |
|
| Specifies whether the affinity group uses hard or soft enforcement of the affinity applied to the resources that are controlled by this rule. | |
|
| Specifies whether the affinity group applies positive affinity or negative affinity to the resources that are controlled by this rule. |
7.5.1. enabled Copy linkLink copied to clipboard!
Specifies whether the affinity group uses this rule or not. This attribute is optional during creation and is considered to be true when it is not provided. In case this attribute is not provided to the update operation, it is considered to be true if AffinityGroup positive attribute is set as well. The backend enabled value will be preserved when both enabled and positive attributes are missing.
7.5.2. enforcing Copy linkLink copied to clipboard!
Specifies whether the affinity group uses hard or soft enforcement of the affinity applied to the resources that are controlled by this rule. This argument is mandatory if the rule is enabled and is ignored when the rule is disabled.
7.5.3. positive Copy linkLink copied to clipboard!
Specifies whether the affinity group applies positive affinity or negative affinity to the resources that are controlled by this rule. This argument is mandatory if the rule is enabled and is ignored when the rule is disabled.
7.6. Agent struct Copy linkLink copied to clipboard!
Type representing a fence agent.
| Name | Type | Summary |
|---|---|---|
|
| Fence agent address. | |
|
| Free text containing comments about this object. | |
|
| Specifies whether the agent should be used concurrently or sequentially. | |
|
| A human-readable description in plain text. | |
|
| Specifies whether the options should be encrypted. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Fence agent options (comma-delimited list of key-value pairs). | |
|
| The order of this agent if used with other agents. | |
|
| Fence agent password. | |
|
| Fence agent port. | |
|
| Fence agent type. | |
|
| Fence agent user name. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to the host service. |
7.6.1. host Copy linkLink copied to clipboard!
Reference to the host service. Each fence agent belongs to a single host.
7.7. AgentConfiguration struct Copy linkLink copied to clipboard!
Deprecated Agent configuration settings.
Ignored, because the deployment of OpenStack Neutron agent is dropped since Red Hat Virtualization 4.4.0. The deployment of OpenStack hosts can be done by Red Hat OpenStack Platform Director or TripleO.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| Not recommended to use, because the Open vSwitch interface mappings are managed by VDSM since Red Hat Virtualization 4. | |
|
| ||
|
| ||
|
|
7.7.1. network_mappings Copy linkLink copied to clipboard!
Not recommended to use, because the Open vSwitch interface mappings are managed by VDSM since Red Hat Virtualization 4.2.0.
7.8. Api struct Copy linkLink copied to clipboard!
This type contains the information returned by the root service of the API.
To get that information send a request like this:
GET /ovirt-engine/api
GET /ovirt-engine/api
The result will be like this:
| Name | Type | Summary |
|---|---|---|
|
| Information about the product, such as its name, the name of the vendor, and the version. | |
|
| References to special objects, such as the blank template and the root of the hierarchy of tags. | |
|
| A summary containing the total number of relevant objects, such as virtual machines, hosts, and storage domains. | |
|
| The date and time when this information was generated. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to the authenticated user. | |
|
| Reference to the effective user. |
7.8.1. authenticated_user Copy linkLink copied to clipboard!
Reference to the authenticated user.
The authenticated user is the user whose credentials were verified in order to accept the current request. In the current version of the system the authenticated user and the effective user are always the same. In the future, when support for user impersonation is introduced, they will be potentially different.
7.8.2. effective_user Copy linkLink copied to clipboard!
Reference to the effective user.
The effective user is the user whose permissions apply during the current request. In the current version of the system the authenticated user and the effective user are always the same. In the future, when support for user impersonation is introduced, they will be potentially different.
7.9. ApiSummary struct Copy linkLink copied to clipboard!
A summary containing the total number of relevant objects, such as virtual machines, hosts, and storage domains.
| Name | Type | Summary |
|---|---|---|
|
| The summary of hosts. | |
|
| The summary of storage domains. | |
|
| The summary of users. | |
|
| The summary of virtual machines. |
7.10. ApiSummaryItem struct Copy linkLink copied to clipboard!
This type contains an item of the API summary. Each item contains the total and active number of some kind of object.
7.11. Application struct Copy linkLink copied to clipboard!
Represents an application installed on a virtual machine. Applications are reported by the guest agent, if you deploy one on the virtual machine operating system.
To get that information send a request like this:
GET /ovirt-engine/api/vms/123/applications/456
GET /ovirt-engine/api/vms/123/applications/456
The result will be like this:
<application href="/ovirt-engine/api/vms/123/applications/456" id="456"> <name>application-test-1.0.0-0.el7</name> <vm href="/ovirt-engine/api/vms/123" id="123"/> </application>
<application href="/ovirt-engine/api/vms/123/applications/456" id="456">
<name>application-test-1.0.0-0.el7</name>
<vm href="/ovirt-engine/api/vms/123" id="123"/>
</application>
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| A reference to the virtual machine the application is installed on. |
7.12. Architecture enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| AARCH64 CPU architecture. |
|
| |
|
| IBM S390X CPU architecture. |
|
| |
|
|
7.12.1. s390x Copy linkLink copied to clipboard!
IBM S390X CPU architecture.
Needs to be specified for virtual machines and clusters running on the S390X architecture.
Note that S390 is often used in an ambiguous way to describe either the general machine architecture as such or its 31-bit variant. S390X is used specifically for the 64-bit architecture, which is in line with the other architectures, like X86_64 or PPC64.
7.13. AuthorizedKey struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
|
7.14. AutoNumaStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.15. AutoPinningPolicy enum Copy linkLink copied to clipboard!
Type representing what the CPU and NUMA pinning policy is.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It will be removed in the future. Instead please use CpuPinningPolicy.
| Name | Summary |
|---|---|
|
| The CPU and NUMA pinning will be configured by the dedicated host. |
|
| The CPU and NUMA pinning won’t be calculated. |
|
| The CPU and NUMA pinning will be configured by the virtual machine current state. |
7.15.1. adjust Copy linkLink copied to clipboard!
The CPU and NUMA pinning will be configured by the dedicated host.
Currently, its implication is that the CPU and NUMA pinning will use the dedicated host CPU topology. The virtual machine configuration will automatically be set to fit the host to get the highest possible performance.
7.15.2. disabled Copy linkLink copied to clipboard!
The CPU and NUMA pinning won’t be calculated.
Currently, its implication is that the CPU and NUMA pinning won’t be calculated to the current virtual machine configuration. By default the VM topology set with 1 Socket, 1 Core and 1 Thread.
7.15.3. existing Copy linkLink copied to clipboard!
The CPU and NUMA pinning will be configured by the virtual machine current state.
Currently, its implication is that the CPU and NUMA pinning will use the provided virtual machine CPU topology. Without given CPU topology it will use the engine defaults (the VM topology set with 1 Socket, 1 Core and 1 Thread).
7.16. Backup struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| The backup creation date. | |
|
| A human-readable description in plain text. | |
|
| The checkpoint id at which to start the incremental backup. | |
|
| A unique identifier. | |
|
| The backup modification date. | |
|
| A human-readable name in plain text. | |
|
| The phase of the backup operation. | |
|
| The checkpoint id created by this backup operation. |
7.16.1. to_checkpoint_id Copy linkLink copied to clipboard!
The checkpoint id created by this backup operation. This id can be used as the fromCheckpointId in the next incremental backup.
| Name | Type | Summary |
|---|---|---|
|
| A list of disks contained in the virtual machine backup. | |
|
| The host that was used to start the backup. | |
|
| A reference to the snapshot created if the backup is using a snapshot. | |
|
| A reference to the virtual machine associated with the backup. |
7.17. BackupPhase enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| The final phase, indicates that the backup has failed. |
|
| In this phase, the backup is invoking 'stop_backup' operation in order to complete the backup and unlock the relevant disk. |
|
| The initial phase of the backup. |
|
| The phase means that the relevant disks' backup URLs are ready to be used and downloaded using image transfer. |
|
| The phase is set before invoking 'start_backup' operation in vdsm/libvirt (which means that 'stop_backup' should be invoked to complete the flow). |
|
| The final phase, indicates that the backup has finished successfully. |
7.17.1. initializing Copy linkLink copied to clipboard!
The initial phase of the backup. It is set on entity creation.
7.18. Balance struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.19. Bios struct Copy linkLink copied to clipboard!
7.20. BiosType enum Copy linkLink copied to clipboard!
Type representing a chipset and a BIOS type combination.
| Name | Summary |
|---|---|
|
| Use the cluster-wide default. |
|
| i440fx chipset with SeaBIOS. |
|
| q35 chipset with OVMF (UEFI) BIOS. |
|
| q35 chipset with SeaBIOS. |
|
| q35 chipset with OVMF (UEFI) BIOS with SecureBoot enabled. |
7.20.1. cluster_default Copy linkLink copied to clipboard!
Use the cluster-wide default.
This value cannot be used for cluster.
7.20.2. i440fx_sea_bios Copy linkLink copied to clipboard!
i440fx chipset with SeaBIOS.
For non-x86 architectures this is the only non-default value allowed.
7.21. BlockStatistic struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.22. Bonding struct Copy linkLink copied to clipboard!
Represents a network interfaces bond.
| Name | Type | Summary |
|---|---|---|
|
|
The | |
|
| A list of option elements for a bonded interface. | |
|
| A list of slave NICs for a bonded interface. |
7.22.1. ad_partner_mac Copy linkLink copied to clipboard!
The ad_partner_mac property of the partner bond in mode 4. Bond mode 4 is the 802.3ad standard, which is also called dynamic link aggregation. See Wikipedia and Presentation for more information. ad_partner_mac is the MAC address of the system (switch) at the other end of a bond. This parameter is read-only. Setting it will have no effect on the bond. It is retrieved from /sys/class/net/bondX/bonding/ad_partner_mac file on the system where the bond is located.
7.22.2. options Copy linkLink copied to clipboard!
A list of option elements for a bonded interface. Each option contains property name and value attributes. Only required when adding bonded interfaces.
7.22.3. slaves Copy linkLink copied to clipboard!
A list of slave NICs for a bonded interface. Only required when adding bonded interfaces.
| Name | Type | Summary |
|---|---|---|
|
|
The |
7.22.4. active_slave Copy linkLink copied to clipboard!
The active_slave property of the bond in modes that support it (active-backup, balance-alb and balance-tlb). See Linux documentation for further details. This parameter is read-only. Setting it will have no effect on the bond. It is retrieved from /sys/class/net/bondX/bonding/active_slave file on the system where the bond is located.
For example:
GET /ovirt-engine/api/hosts/123/nics/321
GET /ovirt-engine/api/hosts/123/nics/321
Will respond:
7.23. Bookmark struct Copy linkLink copied to clipboard!
Represents a bookmark in the system.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The bookmark value, representing a search in the engine. |
7.24. Boot struct Copy linkLink copied to clipboard!
Configuration of the boot sequence of a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| Ordered list of boot devices. |
7.24.1. devices Copy linkLink copied to clipboard!
Ordered list of boot devices. The virtual machine will try to boot from the given boot devices, in the given order.
7.25. BootDevice enum Copy linkLink copied to clipboard!
Represents the kinds of devices that a virtual machine can boot from.
| Name | Summary |
|---|---|
|
| Boot from CD-ROM. |
|
| Boot from the hard drive. |
|
| Boot from the network, using PXE. |
7.25.1. cdrom Copy linkLink copied to clipboard!
Boot from CD-ROM. The CD-ROM can be chosen from the list of ISO files available in an ISO domain attached to the ata center that the virtual machine belongs to.
7.25.2. network Copy linkLink copied to clipboard!
Boot from the network, using PXE. It is necessary to have PXE configured on the network that the virtual machine is connected to.
7.27. BootProtocol enum Copy linkLink copied to clipboard!
Defines the options of the IP address assignment method to a NIC.
| Name | Summary |
|---|---|
|
| Stateless address auto-configuration. |
|
| Dynamic host configuration protocol. |
|
| No address configuration. |
|
| DHCP alongside Stateless address auto-configuration (SLAAC). |
|
| Statically-defined address, mask and gateway. |
7.27.1. autoconf Copy linkLink copied to clipboard!
Stateless address auto-configuration.
The mechanism is defined by RFC 4862. Please refer to this wikipedia article for more information.
The value is valid for IPv6 addresses only.
7.27.2. dhcp Copy linkLink copied to clipboard!
Dynamic host configuration protocol.
Please refer to this wikipedia article for more information.
7.27.3. poly_dhcp_autoconf Copy linkLink copied to clipboard!
DHCP alongside Stateless address auto-configuration (SLAAC).
The SLAAC mechanism is defined by RFC 4862. Please refer to the Stateless address auto-configuration article and the DHCP article for more information.
The value is valid for IPv6 addresses only.
7.28. BrickProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.29. Cdrom struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.29.1. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.30. Certificate struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
|
7.31. Checkpoint struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| The checkpoint creation date. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The parent checkpoint id. | |
|
| The state of the checkpoint. |
7.32. CheckpointState enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| The initial state of the checkpoint. |
|
| The INVALID state set when a checkpoint cannot be used anymore for incremental backup and should be removed (For example, after committing to an older VM snapshot). |
7.32.1. created Copy linkLink copied to clipboard!
The initial state of the checkpoint. It is set on entity creation.
7.33. CloudInit struct Copy linkLink copied to clipboard!
Deprecated type to specify cloud-init configuration.
This type has been deprecated and replaced by alternative attributes inside the Initialization type. See the cloud_init attribute documentation for details.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.34. CloudInitNetworkProtocol enum Copy linkLink copied to clipboard!
Defines the values for the cloud-init protocol. This protocol decides how the cloud-init network parameters are formatted before being passed to the virtual machine in order to be processed by cloud-init.
Protocols supported are cloud-init version dependent. For more information, see Network Configuration Sources
| Name | Summary |
|---|---|
|
| Legacy protocol. |
|
| Successor of the ENI protocol, with support for IPv6 and more. |
7.34.1. eni Copy linkLink copied to clipboard!
Legacy protocol. Does not support IPv6. For more information, see Network Configuration ENI (Legacy)
7.34.2. openstack_metadata Copy linkLink copied to clipboard!
Successor of the ENI protocol, with support for IPv6 and more. This is the default value. For more information, see API: Proxy neutron configuration to guest instance
7.35. Cluster struct Copy linkLink copied to clipboard!
Type representation of a cluster.
A JSON representation of a cluster:
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Chipset and BIOS type combination. | |
|
| Free text containing comments about this object. | |
|
| ||
|
| Custom scheduling policy properties of the cluster. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| ||
|
| A custom fencing policy can be defined for a cluster. | |
|
| FIPS mode of the cluster. | |
|
| The type of firewall to be used on hosts in this cluster. | |
|
| ||
|
| The name of the tuned profile. | |
|
| ||
|
| A unique identifier. | |
|
| ||
|
| The memory consumption threshold for logging audit log events. | |
|
| The memory consumption threshold type for logging audit log events. | |
|
| This property has no longer any relevance and has been deprecated. | |
|
| ||
|
| Reference to cluster-wide configuration of migration of a running virtual machine to another host. | |
|
| A human-readable name in plain text. | |
|
| This property has no longer any relevance and has been deprecated. | |
|
| Set of random number generator (RNG) sources required from each host in the cluster. | |
|
| ||
|
| ||
|
| The type of switch to be used by all networks in given cluster. | |
|
| ||
|
| ||
|
| ||
|
| The upgrade correlation identifier. | |
|
| Indicates if an upgrade has been started for the cluster. | |
|
| If an upgrade is in progress, the upgrade’s reported percent complete. | |
|
| The compatibility version of the cluster. | |
|
| ||
|
| Enable VNC encryption. |
7.35.1. bios_type Copy linkLink copied to clipboard!
Chipset and BIOS type combination.
This value is used as default for all virtual machines in the cluster having biosType set to CLUSTER_DEFAULT.
7.35.2. custom_scheduling_policy_properties Copy linkLink copied to clipboard!
Custom scheduling policy properties of the cluster. These optional properties override the properties of the scheduling policy specified by the scheduling_policy link, and apply only for this specific cluster.
For example, to update the custom properties of the cluster, send a request:
PUT /ovirt-engine/api/clusters/123
PUT /ovirt-engine/api/clusters/123
With a request body:
Update operations using the custom_scheduling_policy_properties attribute will not update the the properties of the scheduling policy specified by the scheduling_policy link, they will only be reflected on this specific cluster.
7.35.3. fencing_policy Copy linkLink copied to clipboard!
A custom fencing policy can be defined for a cluster.
For example:
PUT /ovirt-engine/api/cluster/123
PUT /ovirt-engine/api/cluster/123
With request body like this:
7.35.4. fips_mode Copy linkLink copied to clipboard!
FIPS mode of the cluster.
FIPS mode represents the cluster’s policy towards hosts. Hosts added to the cluster will be checked to fulfill the cluster’s FIPS mode, making them non-operational if they do not. Unless a value is explicity provided, new clusters are initialized by default to UNDEFINED. This value changes automatically to the FIPS mode of the first host added to the cluster.
7.35.5. gluster_tuned_profile Copy linkLink copied to clipboard!
The name of the tuned profile.
Tuned profile to set on all the hosts in the cluster. This is not mandatory and relevant only for clusters with Gluster service.
7.35.6. log_max_memory_used_threshold Copy linkLink copied to clipboard!
The memory consumption threshold for logging audit log events.
For percentage, an audit log event is logged if the used memory is more that the value specified. For absolute value, an audit log event is logged when the the free memory falls below the value specified in MB.
7.35.7. log_max_memory_used_threshold_type Copy linkLink copied to clipboard!
The memory consumption threshold type for logging audit log events.
You can choose between 'percentage' and 'absolute_value_in_mb'.
7.35.8. maintenance_reason_required Copy linkLink copied to clipboard!
This property has no longer any relevance and has been deprecated. Its default value is true,
7.35.9. migration Copy linkLink copied to clipboard!
Reference to cluster-wide configuration of migration of a running virtual machine to another host.
API for querying migration policy by ID returned by this method is not implemented yet. Use /ovirt-engine/api/options/MigrationPolicies to get a list of all migration policies with their IDs.
7.35.10. optional_reason Copy linkLink copied to clipboard!
This property has no longer any relevance and has been deprecated. Its default value is true.
7.35.11. required_rng_sources Copy linkLink copied to clipboard!
Set of random number generator (RNG) sources required from each host in the cluster.
When read, it returns the implicit urandom (for cluster version 4.1 and higher) or random (for cluster version 4.0 and lower) plus additional selected RNG sources. When written, the implicit urandom and random RNG sources cannot be removed.
Before version 4.1 of the engine, the set of required random number generators was completely controllable by the administrator; any source could be added or removed, including the random source. But starting with version 4.1, the urandom and random sources will always be part of the set, and can’t be removed.
Engine version 4.1 introduces a new RNG source urandom that replaces random RNG source in clusters with compatibility version 4.1 or higher.
7.35.12. upgrade_correlation_id Copy linkLink copied to clipboard!
The upgrade correlation identifier. Use to correlate events detailing the cluster upgrade to the upgrade itself.
7.35.13. version Copy linkLink copied to clipboard!
The compatibility version of the cluster.
All hosts in this cluster must support at least this compatibility version.
For example:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/123
Will respond with:
To update the compatibility version, use:
PUT /ovirt-engine/api/clusters/123
PUT /ovirt-engine/api/clusters/123
With a request body like this:
In order to update the cluster compatibility version, all hosts in the cluster must support the new compatibility version.
7.35.14. vnc_encryption Copy linkLink copied to clipboard!
Enable VNC encryption. Default value for this property is false.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| Custom features that are enabled for the cluster. | |
|
| A reference to the external network provider available in the cluster. | |
|
| ||
|
| ||
|
| A reference to the MAC pool used by this cluster. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Reference to the default scheduling policy used by this cluster. |
7.35.15. external_network_providers Copy linkLink copied to clipboard!
A reference to the external network provider available in the cluster.
If the automatic deployment of the external network provider is supported, the networks of the referenced network provider are available on every host in the cluster. External network providers of a cluster can only be set during adding the cluster. This value may be overwritten for individual hosts during adding the host.
7.35.16. scheduling_policy Copy linkLink copied to clipboard!
Reference to the default scheduling policy used by this cluster.
The scheduling policy properties are taken by default from the referenced scheduling policy, but they are overridden by the properties specified in the custom_scheduling_policy_properties attribute for this cluster.
7.36. ClusterFeature struct Copy linkLink copied to clipboard!
Type represents an additional feature that is available at a cluster level.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to the cluster level. |
7.37. ClusterLevel struct Copy linkLink copied to clipboard!
Describes the capabilities supported by a specific cluster level.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| The CPU types supported by this cluster level. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The permits supported by this cluster level. |
| Name | Type | Summary |
|---|---|---|
|
| The additional features supported by this cluster level. |
7.38. ClusterUpgradeAction enum Copy linkLink copied to clipboard!
The action type for cluster upgrade action.
| Name | Summary |
|---|---|
|
| The upgrade action to be passed to finish the cluster upgrade process by marking the cluster’s upgrade_running flag to false. |
|
| The upgrade action to be passed to start the cluster upgrade process by marking the cluster’s upgrade_running flag to true. |
|
| The upgrade action to be passed to update the cluster upgrade progress. |
7.38.1. finish Copy linkLink copied to clipboard!
The upgrade action to be passed to finish the cluster upgrade process by marking the cluster’s upgrade_running flag to false. This should be used at the end of the cluster upgrade process.
7.38.2. start Copy linkLink copied to clipboard!
The upgrade action to be passed to start the cluster upgrade process by marking the cluster’s upgrade_running flag to true. This should used at the beginning of the cluster upgrade process.
7.38.3. update_progress Copy linkLink copied to clipboard!
The upgrade action to be passed to update the cluster upgrade progress. This should be used as the upgrade progresses.
7.39. Configuration struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| The document describing the virtual machine. | |
|
|
7.39.1. data Copy linkLink copied to clipboard!
The document describing the virtual machine.
Example of the OVF document:
7.40. ConfigurationType enum Copy linkLink copied to clipboard!
Configuration format types.
| Name | Summary |
|---|---|
|
| ConfigurationType of type standard OVF. |
|
| ConfigurationType of type oVirt-compatible OVF. |
7.40.1. ova Copy linkLink copied to clipboard!
ConfigurationType of type standard OVF.
The provided virtual machine configuration conforms with the Open Virtualization Format (OVF) standard. This value should be used for an OVF configuration that is extracted from an Open Virtual Appliance (OVA) that was generated by oVirt or by other vendors. See the OVF specification.
7.40.2. ovf Copy linkLink copied to clipboard!
ConfigurationType of type oVirt-compatible OVF.
The provided virtual machine configuration conforms with the oVirt-compatible form of the Open Virtualization Format (OVF). Note that the oVirt-compatible form of the OVF may differ from the OVF standard that is used by other vendors. This value should be used for an OVF configuration that is taken from a storage domain.
7.41. Console struct Copy linkLink copied to clipboard!
Representation for serial console device.
| Name | Type | Summary |
|---|---|---|
|
| Enable/disable the serial console device. |
7.42. Core struct Copy linkLink copied to clipboard!
7.43. Cpu struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.44. CpuMode enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.45. CpuPinningPolicy enum Copy linkLink copied to clipboard!
Type representing the CPU and NUMA pinning policy.
| Name | Summary |
|---|---|
|
| The CPU pinning will be automatically calculated by the engine when a vm starts and it will be dropped when the vm stops. |
|
| The CPU pinning will be automatically calculated by the engine when a vm starts, and it will be dropped when the vm stops. |
|
| The CPU pinning will be manually configured. |
|
| The CPU pinning won’t be configured. |
|
| The CPU and NUMA pinning will be configured by the dedicated host. |
7.45.1. dedicated Copy linkLink copied to clipboard!
The CPU pinning will be automatically calculated by the engine when a vm starts and it will be dropped when the vm stops.
The pinning is exclusive, that means that no other VM can use the pinned physical CPU.
7.45.2. isolate_threads Copy linkLink copied to clipboard!
The CPU pinning will be automatically calculated by the engine when a vm starts, and it will be dropped when the vm stops.
The pinning is exclusive, each virtual thread will get an exclusive physical core. That means that no other VM can use the pinned physical CPU.
7.45.3. manual Copy linkLink copied to clipboard!
The CPU pinning will be manually configured.
Currently, this means that the CPU pinning will be manually configured to the current virtual machine configuration. The VM needs to be pinned to at least one host. The Pinning is provided within the CPU configuration, using CpuTune.
7.45.4. none Copy linkLink copied to clipboard!
The CPU pinning won’t be configured.
Currently, this means that the CPU pinning won’t be configured to the current virtual machine configuration. By default, the VM topology is set with 1 Socket, 1 Core and 1 Thread.
7.45.5. resize_and_pin_numa Copy linkLink copied to clipboard!
The CPU and NUMA pinning will be configured by the dedicated host.
The CPU and NUMA pinning will use the dedicated host CPU topology. The virtual machine configuration will automatically be set to fit the host to get the highest possible performance.
7.46. CpuProfile struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.47. CpuTopology struct Copy linkLink copied to clipboard!
7.48. CpuTune struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.49. CpuType struct Copy linkLink copied to clipboard!
Describes a supported CPU type.
| Name | Type | Summary |
|---|---|---|
|
| The architecture of the CPU. | |
|
| The level of the CPU type. | |
|
|
The name of the CPU type, for example |
7.50. CreationStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
7.51. CustomProperty struct Copy linkLink copied to clipboard!
Custom property representation.
7.52. DataCenter struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| The compatibility version of the data center. |
7.52.1. version Copy linkLink copied to clipboard!
The compatibility version of the data center.
All clusters in this data center must already be set to at least this compatibility version.
For example:
GET /ovirt-engine/api/datacenters/123
GET /ovirt-engine/api/datacenters/123
Will respond:
To update the compatibility version, use:
PUT /ovirt-engine/api/datacenters/123
PUT /ovirt-engine/api/datacenters/123
With a request body:
| Name | Type | Summary |
|---|---|---|
|
| Reference to clusters inside this data center. | |
|
| Reference to ISCSI bonds used by this data center. | |
|
| Reference to the MAC pool used by this data center. | |
|
| Reference to networks attached to this data center. | |
|
| Reference to permissions assigned to this data center. | |
|
| Qos[] | Reference to quality of service used by this data center. |
|
| Reference to quotas assigned to this data center. | |
|
| Reference to storage domains attached to this data center. |
7.53. DataCenterStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
7.54. Device struct Copy linkLink copied to clipboard!
A device wraps links to potential parents of a device.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.54.1. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.55. Disk struct Copy linkLink copied to clipboard!
Represents a virtual disk device.
| Name | Type | Summary |
|---|---|---|
|
| Indicates if the disk is visible to the virtual machine. | |
|
| The actual size of the disk, in bytes. | |
|
| ||
|
| The backup behavior supported by the disk. | |
|
| The type of the disk backup (full/incremental), visible only when the disk backup is in progress. | |
|
| Indicates if the disk is marked as bootable. | |
|
| Free text containing comments about this object. | |
|
| Indicates the actual content residing on the disk. | |
|
| A human-readable description in plain text. | |
|
| Use external disk. | |
|
| The underlying storage format. | |
|
| A unique identifier. | |
|
| ||
|
| The initial size of a sparse image disk created on block storage, in bytes. | |
|
| The type of interface driver used to connect the disk device to the virtual machine. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| Indicates if disk errors should cause virtual machine to be paused or if disk errors should be propagated to the the guest operating system instead. | |
|
| The virtual size of the disk, in bytes. | |
|
| The underlying QCOW version of a QCOW volume. | |
|
| Indicates if the disk is in read-only mode. | |
|
| Indicates whether SCSI passthrough is enable and its policy. | |
|
| Indicates if the disk can be attached to multiple virtual machines. | |
|
| Indicates if the physical storage for the disk should not be preallocated. | |
|
| The status of the disk device. | |
|
| ||
|
| The total size of the disk including all of its snapshots, in bytes. | |
|
| ||
|
| Indicates if the disk’s blocks will be read back as zeros after it is deleted: - On block storage, the disk will be zeroed and only then deleted. |
7.55.1. active Copy linkLink copied to clipboard!
Indicates if the disk is visible to the virtual machine.
When adding a disk attachment to a virtual machine, if the server accepts requests that do not contain this attribute the result is undefined. In some cases the disk will be automatically activated and in other cases it will not. To avoid issues it is strongly recommended to always include the this attribute with the desired value.
7.55.2. actual_size Copy linkLink copied to clipboard!
The actual size of the disk, in bytes.
The actual size is the number of bytes actually used by the disk. It will be smaller than the provisioned size for disks that use the cow format.
7.55.3. bootable Copy linkLink copied to clipboard!
Indicates if the disk is marked as bootable.
This attribute only makes sense for disks that are actually connected to virtual machines, and in version 4 of the API it has been moved to the DiskAttachment type. It is preserved here only for backwards compatibility, and it will be removed in the future.
7.55.4. external_disk Copy linkLink copied to clipboard!
Use external disk.
An external disk can be a path to a local file or a block device, or a URL supported by QEMU such as:
- nbd:<host>:<port>[:exportname=<export>]
- nbd:unix:</path>[:exportname=<export>]
- http://[<username>[:<password>]@]<host>/<path>
- https://[<username>[:<password>]@]<host>/<path>
- ftp://[<username>[:<password>]@]<host>/<path>
- ftps://[<username>[:<password>]@]<host>/<path>
See the QEMU manual for additional supported protocols and more info.
7.55.5. initial_size Copy linkLink copied to clipboard!
The initial size of a sparse image disk created on block storage, in bytes.
The initial size is the number of bytes a sparse disk is initially allocated with when created on block storage. The initial size will be smaller than the provisioned size. If not specified the default initial size used by the system will be allocated.
7.55.6. interface Copy linkLink copied to clipboard!
The type of interface driver used to connect the disk device to the virtual machine.
This attribute only makes sense for disks that are actually connected to virtual machines, and in version 4 of the API it has been moved to the DiskAttachment type. It is preserved here only for backwards compatibility, and it will be removed in the future.
7.55.7. provisioned_size Copy linkLink copied to clipboard!
The virtual size of the disk, in bytes.
This attribute is mandatory when creating a new disk.
7.55.8. qcow_version Copy linkLink copied to clipboard!
The underlying QCOW version of a QCOW volume. The QCOW version specifies to the qemu which qemu version the volume supports. This field can be updated using the update API and will be reported only for QCOW volumes. It is determined by the version of the storage domain that the disk is created on. Storage domains with a version lower than V4 support QCOW2 volumes. V4 storage domains also support QCOW2v3. For more information about features of the different QCOW versions, see QCOW3.
7.55.9. read_only Copy linkLink copied to clipboard!
Indicates if the disk is in read-only mode.
Since version 4.0 this attribute is not shown in the API and was moved to DiskAttachment.
Since version 4.1.2 of Red Hat Virtualization Manager this attribute is deprecated, and it will be removed in the future. In order to attach a disk in read only mode use the read_only attribute of the DiskAttachment type. For example:
POST /ovirt-engine/api/vms/123/diskattachments
POST /ovirt-engine/api/vms/123/diskattachments
<disk_attachment> <read_only>true</read_only> ... </disk_attachment>
<disk_attachment>
<read_only>true</read_only>
...
</disk_attachment>
7.55.10. sgio Copy linkLink copied to clipboard!
Indicates whether SCSI passthrough is enable and its policy.
Setting a value of filtered/unfiltered will enable SCSI passthrough for a LUN disk with unprivileged/privileged SCSI I/O. To disable SCSI passthrough the value should be set to disabled
7.55.12. total_size Copy linkLink copied to clipboard!
The total size of the disk including all of its snapshots, in bytes.
The total size is the number of bytes actually used by the disk plus the size of its snapshots. It won’t be populated for direct LUN and Cinder disks. For disks without snapshots the total size is equal to the actual size.
7.55.13. wipe_after_delete Copy linkLink copied to clipboard!
Indicates if the disk’s blocks will be read back as zeros after it is deleted:
- On block storage, the disk will be zeroed and only then deleted.
- On file storage, since the file system already guarantees that previously removed blocks are read back as zeros, the disk will be deleted immediately.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| Optionally references to an instance type the device is used by. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Statistics exposed by the disk. | |
|
| ||
|
| The storage domains associated with this disk. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.55.14. statistics Copy linkLink copied to clipboard!
Statistics exposed by the disk. For example:
These statistics are not directly included when the disk is retrieved, only a link. To obtain the statistics follow the included link:
GET /ovirt-engine/api/disks/123/statistics
GET /ovirt-engine/api/disks/123/statistics
7.55.15. storage_domains Copy linkLink copied to clipboard!
The storage domains associated with this disk.
Only required when the first disk is being added to a virtual machine that was not itself created from a template.
7.55.16. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.56. DiskAttachment struct Copy linkLink copied to clipboard!
Describes how a disk is attached to a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| Defines whether the disk is active in the virtual machine it’s attached to. | |
|
| Defines whether the disk is bootable. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The type of interface driver used to connect the disk device to the virtual machine. | |
|
| The logical name of the virtual machine’s disk, as seen from inside the virtual machine. | |
|
| A human-readable name in plain text. | |
|
| Defines whether the virtual machine passes discard commands to the storage. | |
|
| Indicates whether the disk is connected to the virtual machine as read only. | |
|
| Defines whether SCSI reservation is enabled for this disk. |
7.56.1. active Copy linkLink copied to clipboard!
Defines whether the disk is active in the virtual machine it’s attached to.
A disk attached to a virtual machine in an active status is connected to the virtual machine at run time and can be used.
7.56.2. logical_name Copy linkLink copied to clipboard!
The logical name of the virtual machine’s disk, as seen from inside the virtual machine.
The logical name of a disk is reported only when the guest agent is installed and running inside the virtual machine.
For example, if the guest operating system is Linux and the disk is connected via a VirtIO interface, the logical name will be reported as /dev/vda:
<disk_attachment> ... <logical_name>/dev/vda</logical_name> </disk_attachment>
<disk_attachment>
...
<logical_name>/dev/vda</logical_name>
</disk_attachment>
If the guest operating system is Windows, the logical name will be reported as \\.\PHYSICALDRIVE0.
7.56.3. read_only Copy linkLink copied to clipboard!
Indicates whether the disk is connected to the virtual machine as read only.
When adding a new disk attachment the default value is false.
<disk_attachment> ... <read_only>true</read_only> </disk_attachment>
<disk_attachment>
...
<read_only>true</read_only>
</disk_attachment>
7.56.4. uses_scsi_reservation Copy linkLink copied to clipboard!
Defines whether SCSI reservation is enabled for this disk.
Virtual machines with VIRTIO-SCSI passthrough enabled can set persistent SCSI reservations on disks. If they set persistent SCSI reservations, those virtual machines cannot be migrated to a different host because they would lose access to the disk, because SCSI reservations are specific to SCSI initiators, and therefore hosts. This scenario cannot be automatically detected. To avoid migrating these virtual machines, the user can set this attribute to true, to indicate the virtual machine is using SCSI reservations.
7.57. DiskBackup enum Copy linkLink copied to clipboard!
Represents an enumeration of the backup mechanism that is enabled on the disk.
| Name | Summary |
|---|---|
|
| Incremental backup support. |
|
| No backup support. |
7.58. DiskBackupMode enum Copy linkLink copied to clipboard!
Represents an enumeration of backup modes
| Name | Summary |
|---|---|
|
| This disk supports full backup. |
|
| This disk supports incremental backup. |
7.58.1. full Copy linkLink copied to clipboard!
This disk supports full backup. You can query zero extents and download all disk data.
7.58.2. incremental Copy linkLink copied to clipboard!
This disk supports incremental backup. You can query dirty extents and download changed blocks.
7.59. DiskContentType enum Copy linkLink copied to clipboard!
The actual content residing on the disk.
| Name | Summary |
|---|---|
|
| The disk contains protected VM backup data. |
|
| The disk contains data. |
|
| The disk contains the Hosted Engine VM disk. |
|
| The disk contains the Hosted Engine configuration disk. |
|
| The disk contains the Hosted Engine metadata disk. |
|
| The disk contains the Hosted Engine Sanlock disk. |
|
| The disk contains an ISO image to be used a CDROM device. |
|
| The disk contains a memory dump from a live snapshot. |
|
| The disk contains memory metadata from a live snapshot. |
|
| The disk is an OVF store. |
7.60. DiskFormat enum Copy linkLink copied to clipboard!
The underlying storage format of disks.
| Name | Summary |
|---|---|
|
| The Copy On Write format allows snapshots, with a small performance overhead. |
|
| The raw format does not allow snapshots, but offers improved performance. |
7.61. DiskInterface enum Copy linkLink copied to clipboard!
The underlying storage interface of disks communication with controller.
| Name | Summary |
|---|---|
|
| Legacy controller device. |
|
| SATA controller device. |
|
| Para-virtualized device supported by the IBM pSeries family of machines, using the SCSI protocol. |
|
| Virtualization interface where just the guest’s device driver knows it is running in a virtual environment. |
|
| Para-virtualized SCSI controller device. |
7.61.1. ide Copy linkLink copied to clipboard!
Legacy controller device. Works with almost all guest operating systems, so it is good for compatibility. Performance is lower than with the other alternatives.
7.61.2. virtio Copy linkLink copied to clipboard!
Virtualization interface where just the guest’s device driver knows it is running in a virtual environment. Enables guests to get high performance disk operations.
7.61.3. virtio_scsi Copy linkLink copied to clipboard!
Para-virtualized SCSI controller device. Fast interface with the guest via direct physical storage device address, using the SCSI protocol.
7.62. DiskProfile struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.63. DiskSnapshot struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Indicates if the disk is visible to the virtual machine. | |
|
| The actual size of the disk, in bytes. | |
|
| ||
|
| The backup behavior supported by the disk. | |
|
| The type of the disk backup (full/incremental), visible only when the disk backup is in progress. | |
|
| Indicates if the disk is marked as bootable. | |
|
| Free text containing comments about this object. | |
|
| Indicates the actual content residing on the disk. | |
|
| A human-readable description in plain text. | |
|
| Use external disk. | |
|
| The underlying storage format. | |
|
| A unique identifier. | |
|
| ||
|
| The initial size of a sparse image disk created on block storage, in bytes. | |
|
| The type of interface driver used to connect the disk device to the virtual machine. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| Indicates if disk errors should cause virtual machine to be paused or if disk errors should be propagated to the the guest operating system instead. | |
|
| The virtual size of the disk, in bytes. | |
|
| The underlying QCOW version of a QCOW volume. | |
|
| Indicates if the disk is in read-only mode. | |
|
| Indicates whether SCSI passthrough is enable and its policy. | |
|
| Indicates if the disk can be attached to multiple virtual machines. | |
|
| Indicates if the physical storage for the disk should not be preallocated. | |
|
| The status of the disk device. | |
|
| ||
|
| The total size of the disk including all of its snapshots, in bytes. | |
|
| ||
|
| Indicates if the disk’s blocks will be read back as zeros after it is deleted: - On block storage, the disk will be zeroed and only then deleted. |
7.63.1. active Copy linkLink copied to clipboard!
Indicates if the disk is visible to the virtual machine.
When adding a disk attachment to a virtual machine, if the server accepts requests that do not contain this attribute the result is undefined. In some cases the disk will be automatically activated and in other cases it will not. To avoid issues it is strongly recommended to always include the this attribute with the desired value.
7.63.2. actual_size Copy linkLink copied to clipboard!
The actual size of the disk, in bytes.
The actual size is the number of bytes actually used by the disk. It will be smaller than the provisioned size for disks that use the cow format.
7.63.3. bootable Copy linkLink copied to clipboard!
Indicates if the disk is marked as bootable.
This attribute only makes sense for disks that are actually connected to virtual machines, and in version 4 of the API it has been moved to the DiskAttachment type. It is preserved here only for backwards compatibility, and it will be removed in the future.
7.63.4. external_disk Copy linkLink copied to clipboard!
Use external disk.
An external disk can be a path to a local file or a block device, or a URL supported by QEMU such as:
- nbd:<host>:<port>[:exportname=<export>]
- nbd:unix:</path>[:exportname=<export>]
- http://[<username>[:<password>]@]<host>/<path>
- https://[<username>[:<password>]@]<host>/<path>
- ftp://[<username>[:<password>]@]<host>/<path>
- ftps://[<username>[:<password>]@]<host>/<path>
See the QEMU manual for additional supported protocols and more info.
7.63.5. initial_size Copy linkLink copied to clipboard!
The initial size of a sparse image disk created on block storage, in bytes.
The initial size is the number of bytes a sparse disk is initially allocated with when created on block storage. The initial size will be smaller than the provisioned size. If not specified the default initial size used by the system will be allocated.
7.63.6. interface Copy linkLink copied to clipboard!
The type of interface driver used to connect the disk device to the virtual machine.
This attribute only makes sense for disks that are actually connected to virtual machines, and in version 4 of the API it has been moved to the DiskAttachment type. It is preserved here only for backwards compatibility, and it will be removed in the future.
7.63.7. provisioned_size Copy linkLink copied to clipboard!
The virtual size of the disk, in bytes.
This attribute is mandatory when creating a new disk.
7.63.8. qcow_version Copy linkLink copied to clipboard!
The underlying QCOW version of a QCOW volume. The QCOW version specifies to the qemu which qemu version the volume supports. This field can be updated using the update API and will be reported only for QCOW volumes. It is determined by the version of the storage domain that the disk is created on. Storage domains with a version lower than V4 support QCOW2 volumes. V4 storage domains also support QCOW2v3. For more information about features of the different QCOW versions, see QCOW3.
7.63.9. read_only Copy linkLink copied to clipboard!
Indicates if the disk is in read-only mode.
Since version 4.0 this attribute is not shown in the API and was moved to DiskAttachment.
Since version 4.1.2 of Red Hat Virtualization Manager this attribute is deprecated, and it will be removed in the future. In order to attach a disk in read only mode use the read_only attribute of the DiskAttachment type. For example:
POST /ovirt-engine/api/vms/123/diskattachments
POST /ovirt-engine/api/vms/123/diskattachments
<disk_attachment> <read_only>true</read_only> ... </disk_attachment>
<disk_attachment>
<read_only>true</read_only>
...
</disk_attachment>
7.63.10. sgio Copy linkLink copied to clipboard!
Indicates whether SCSI passthrough is enable and its policy.
Setting a value of filtered/unfiltered will enable SCSI passthrough for a LUN disk with unprivileged/privileged SCSI I/O. To disable SCSI passthrough the value should be set to disabled
7.63.12. total_size Copy linkLink copied to clipboard!
The total size of the disk including all of its snapshots, in bytes.
The total size is the number of bytes actually used by the disk plus the size of its snapshots. It won’t be populated for direct LUN and Cinder disks. For disks without snapshots the total size is equal to the actual size.
7.63.13. wipe_after_delete Copy linkLink copied to clipboard!
Indicates if the disk’s blocks will be read back as zeros after it is deleted:
- On block storage, the disk will be zeroed and only then deleted.
- On file storage, since the file system already guarantees that previously removed blocks are read back as zeros, the disk will be deleted immediately.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| Optionally references to an instance type the device is used by. | |
|
| ||
|
| Parent disk snapshot. | |
|
| ||
|
| ||
|
| ||
|
| Statistics exposed by the disk. | |
|
| ||
|
| The storage domains associated with this disk. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.63.14. statistics Copy linkLink copied to clipboard!
Statistics exposed by the disk. For example:
These statistics are not directly included when the disk is retrieved, only a link. To obtain the statistics follow the included link:
GET /ovirt-engine/api/disks/123/statistics
GET /ovirt-engine/api/disks/123/statistics
7.63.15. storage_domains Copy linkLink copied to clipboard!
The storage domains associated with this disk.
Only required when the first disk is being added to a virtual machine that was not itself created from a template.
7.63.16. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.64. DiskStatus enum Copy linkLink copied to clipboard!
Current status representation for disk.
| Name | Summary |
|---|---|
|
| Disk cannot be accessed by the virtual machine, and the user needs to take action to resolve the issue. |
|
| The disk is being used by the system, therefore it cannot be accessed by virtual machines at this point. |
|
| The disk status is normal and can be accessed by the virtual machine. |
7.64.1. locked Copy linkLink copied to clipboard!
The disk is being used by the system, therefore it cannot be accessed by virtual machines at this point. This is usually a temporary status, until the disk is freed.
7.65. DiskStorageType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| A storage type, used for a storage domain that was created using a cinderlib driver. |
7.66. DiskType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.67. Display struct Copy linkLink copied to clipboard!
Represents a graphic console configuration.
| Name | Type | Summary |
|---|---|---|
|
| The IP address of the guest to connect the graphic console client to. | |
|
| Indicates if to override the display address per host. | |
|
| The TLS certificate in case of a TLS connection. | |
|
| Indicates whether a user is able to copy and paste content from an external host into the graphic console. | |
|
| Returns the action that will take place when the graphic console is disconnected. | |
|
| Delay (in minutes) before the graphic console disconnect action is carried out. | |
|
| Indicates if a user is able to drag and drop files from an external host into the graphic console. | |
|
| The keyboard layout to use with this graphic console. | |
|
| The number of monitors opened for this graphic console. | |
|
| The port address on the guest to connect the graphic console client to. | |
|
| The proxy IP which will be used by the graphic console client to connect to the guest. | |
|
| The secured port address on the guest, in case of using TLS, to connect the graphic console client to. | |
|
| The engine now sets it automatically according to the operating system. | |
|
| Indicates if to use smart card authentication. | |
|
| The graphic console protocol type. |
7.67.1. allow_override Copy linkLink copied to clipboard!
Indicates if to override the display address per host. Relevant only for the Host.display attribute. If set, the graphical console address of a virtual machine will be overridden by the host specified display address. if not set, the graphical console address of a virtual machine will not be overridden.
7.67.2. certificate Copy linkLink copied to clipboard!
The TLS certificate in case of a TLS connection. If TLS isn’t enabled then it won’t be reported.
7.67.3. copy_paste_enabled Copy linkLink copied to clipboard!
Indicates whether a user is able to copy and paste content from an external host into the graphic console. This option is only available for the SPICE console type.
7.67.4. disconnect_action Copy linkLink copied to clipboard!
Returns the action that will take place when the graphic console is disconnected. The options are:
- none
- No action is taken.
- lock_screen
- Locks the currently active user session.
- logout
- Logs out the currently active user session.
- reboot
- Initiates a graceful virtual machine reboot.
- shutdown
- Initiates a graceful virtual machine shutdown.
This option is only available for the SPICE console type.
7.67.5. disconnect_action_delay Copy linkLink copied to clipboard!
Delay (in minutes) before the graphic console disconnect action is carried out. This option is only available for Shutdown disconnect action.
7.67.6. file_transfer_enabled Copy linkLink copied to clipboard!
Indicates if a user is able to drag and drop files from an external host into the graphic console. This option is only available for the SPICE console type.
7.67.7. keyboard_layout Copy linkLink copied to clipboard!
The keyboard layout to use with this graphic console. This option is only available for the VNC console type. If no keyboard is enabled then it won’t be reported.
7.67.8. monitors Copy linkLink copied to clipboard!
The number of monitors opened for this graphic console. This option is only available for the SPICE console type. Possible values are 1, 2 or 4.
7.67.9. proxy Copy linkLink copied to clipboard!
The proxy IP which will be used by the graphic console client to connect to the guest. It is useful when the client is outside the guest’s network. This option is only available for the SPICE console type. This proxy can be set in global configuration, cluster level, virtual machine pool level or disabled per virtual machine. If the proxy is set in any of this mentioned places and not disabled for the virtual machine, it will be returned by this method. If the proxy is not set, nothing will be reported.
7.67.10. secure_port Copy linkLink copied to clipboard!
The secured port address on the guest, in case of using TLS, to connect the graphic console client to. If TLS isn’t enabled then it won’t be reported.
7.67.11. single_qxl_pci Copy linkLink copied to clipboard!
The engine now sets it automatically according to the operating system. Therefore, it has been deprecated since 4.4.5. Indicates if to use one PCI slot for each monitor or to use a single PCI channel for all multiple monitors. This option is only available for the SPICE console type and only for connecting a guest Linux based OS.
7.67.12. smartcard_enabled Copy linkLink copied to clipboard!
Indicates if to use smart card authentication. This option is only available for the SPICE console type.
7.68. DisplayType enum Copy linkLink copied to clipboard!
Represents an enumeration of the protocol used to connect to the graphic console of the virtual machine.
| Name | Summary |
|---|---|
|
| Display of type SPICE. |
|
| Display of type VNC. |
7.68.1. spice Copy linkLink copied to clipboard!
Display of type SPICE. See SPICE documentation for more details.
7.68.2. vnc Copy linkLink copied to clipboard!
Display of type VNC. VNC stands for Virtual Network Computing, and it is a graphical desktop sharing system that uses RFB (Remote Frame Buffer) protocol to remotely control another machine.
7.69. Dns struct Copy linkLink copied to clipboard!
Represents the DNS resolver configuration.
7.70. DnsResolverConfiguration struct Copy linkLink copied to clipboard!
Represents the DNS resolver configuration.
| Name | Type | Summary |
|---|---|---|
|
| Array of addresses of name servers. |
7.70.1. name_servers Copy linkLink copied to clipboard!
Array of addresses of name servers. Either IPv4 or IPv6 addresses may be specified.
7.71. Domain struct Copy linkLink copied to clipboard!
This type represents a directory service domain.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
| A reference to all groups in the directory service. | |
|
| A reference to a list of all users in the directory service. |
7.71.1. users Copy linkLink copied to clipboard!
A reference to a list of all users in the directory service. This information is used to add new users to the Red Hat Virtualization environment.
7.72. DynamicCpu struct Copy linkLink copied to clipboard!
Configuration of the Dynamic CPUs of a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.73. EntityExternalStatus enum Copy linkLink copied to clipboard!
Type representing an external entity status.
| Name | Summary |
|---|---|
|
| The external entity status is erroneous. |
|
| The external entity has an issue that causes failures. |
|
| There external entity status is okay but with some information that might be relevant. |
|
| The external entity status is okay. |
|
| The external entity status is okay but with an issue that might require attention. |
7.73.1. error Copy linkLink copied to clipboard!
The external entity status is erroneous. This might require a moderate attention.
7.73.2. failure Copy linkLink copied to clipboard!
The external entity has an issue that causes failures. This might require immediate attention.
7.74. EntityProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.75. ErrorHandling struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.76. Event struct Copy linkLink copied to clipboard!
Type representing an event.
| Name | Type | Summary |
|---|---|---|
|
| The event code. | |
|
| Free text containing comments about this object. | |
|
| The event correlation identifier. | |
|
| Free text representing custom event data. | |
|
| A custom event identifier. | |
|
| A human-readable description in plain text. | |
|
| Defines the flood rate. | |
|
| A unique identifier. | |
|
| The numeric index of this event. | |
|
| Specifies whether the event should also be written to the ${hypervisor. | |
|
| A human-readable name in plain text. | |
|
| Free text identifying the origin of the event. | |
|
| The event severity. | |
|
| The event time. |
7.76.1. correlation_id Copy linkLink copied to clipboard!
The event correlation identifier. Used in order to correlate several events together.
7.76.2. flood_rate Copy linkLink copied to clipboard!
Defines the flood rate. This prevents flooding in case an event appeared more than once in the defined rate. Defaults is 30 seconds.
7.76.3. index Copy linkLink copied to clipboard!
The numeric index of this event. The indexes of events are always increasing, so events with higher indexes are guaranteed to be older than events with lower indexes.
In the current implementation of the engine, the id attribute has the same value as this index attribute. That is an implementation detail that the user of the API should not rely on. In the future the id attribute may be changed to an arbitrary string, containing non numeric characters and no implicit order. On the other hand this index attribute is guaranteed to stay as integer and ordered.
7.76.4. log_on_host Copy linkLink copied to clipboard!
Specifies whether the event should also be written to the ${hypervisor.name} log. If no host is specified the event description will be written to all hosts. Default is false.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the cluster service. | |
|
| Reference to the data center service. | |
|
| Reference to the host service. | |
|
| Reference to the storage domain service. | |
|
| Reference to the template service. | |
|
| Reference to the user service. | |
|
| Reference to the virtual machine service. |
7.76.5. cluster Copy linkLink copied to clipboard!
Reference to the cluster service. Event can be associated with a cluster.
7.76.6. data_center Copy linkLink copied to clipboard!
Reference to the data center service. Event can be associated with a data center.
7.76.7. host Copy linkLink copied to clipboard!
Reference to the host service. Event can be associated with a host.
7.76.8. storage_domain Copy linkLink copied to clipboard!
Reference to the storage domain service. Event can be associated with a storage domain.
7.76.9. template Copy linkLink copied to clipboard!
Reference to the template service. Event can be associated with a template.
7.76.10. user Copy linkLink copied to clipboard!
Reference to the user service. Event can be associated with a user.
7.76.11. vm Copy linkLink copied to clipboard!
Reference to the virtual machine service. Event can be associated with a virtual machine.
7.77. EventSubscription struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| The email address to which notifications should be sent. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The subscribed-for event. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The notification method: SMTP or SNMP. | |
|
| The subscribing user. |
7.77.1. address Copy linkLink copied to clipboard!
The email address to which notifications should be sent.
When not provided, notifications are sent to the user’s email. Only a single address per user is currently supported. If a subscription with a different email address to that of existing subscriptions is added, a 409 (CONFLICT) status is returned with an explanation that the provided address conflicts with an existing address of an event-subscription for this user.
This field might be deprecated in the future, and notifications will always be sent on the user’s email address.
7.77.2. event Copy linkLink copied to clipboard!
The subscribed-for event.
(Combined with the user, Uniquely identifies the event-subscription).
7.77.3. notification_method Copy linkLink copied to clipboard!
The notification method: SMTP or SNMP.
Currently only SMTP supported by API. Support for SNMP will be added in the future.
7.77.4. user Copy linkLink copied to clipboard!
The subscribing user.
Combined with the event-name, uniquely identifies the event-subscription.
7.78. ExternalComputeResource struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.79. ExternalDiscoveredHost struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.80. ExternalHost struct Copy linkLink copied to clipboard!
Represents a host provisioned by a host provider (such as Foreman/Satellite).
See Foreman documentation for more details. See Satellite documentation for more details on Red Hat Satellite.
| Name | Type | Summary |
|---|---|---|
|
| The address of the host, either IP address of FQDN (Fully Qualified Domain Name). | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| A reference to the external host provider that the host is managed by. |
7.81. ExternalHostGroup struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.82. ExternalHostProvider struct Copy linkLink copied to clipboard!
Represents an external host provider, such as Foreman or Satellite.
See Foreman documentation for more details. See Satellite documentation for more details on Red Hat Satellite.
| Name | Type | Summary |
|---|---|---|
|
| Defines the external provider authentication URL address. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines password for the user during the authentication process. | |
|
| Array of provider name/value properties. | |
|
| Defines whether provider authentication is required or not. | |
|
| Defines URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
7.82.1. requires_authentication Copy linkLink copied to clipboard!
Defines whether provider authentication is required or not.
If authentication is required, both username and password attributes will be used during authentication.
| Name | Type | Summary |
|---|---|---|
|
| A reference to the certificates the engine supports for this provider. | |
|
| A reference to the compute resource as represented in the host provider. | |
|
| A reference to the discovered hosts in the host provider. | |
|
| A reference to the host groups in the host provider. | |
|
| A reference to the hosts provisioned by the host provider. |
7.82.2. compute_resources Copy linkLink copied to clipboard!
A reference to the compute resource as represented in the host provider. Each host provider optionally has the engine defined as a compute resource, which allows to create virtual machines in the engine. This compute resource details are used in the Bare-Metal provisioning use-case, in order to deploy the hypervisor.
7.82.3. discovered_hosts Copy linkLink copied to clipboard!
A reference to the discovered hosts in the host provider. Discovered hosts are hosts that were not provisioned yet.
7.82.4. host_groups Copy linkLink copied to clipboard!
A reference to the host groups in the host provider. Host group contains different properties that the host provider applies on all hosts that are member of this group. Such as installed software, system definitions, passwords and more.
7.83. ExternalNetworkProviderConfiguration struct Copy linkLink copied to clipboard!
Describes how an external network provider is provisioned on a host.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Link to the external network provider. | |
|
| Link to the host. |
7.84. ExternalProvider struct Copy linkLink copied to clipboard!
Represents an external provider.
| Name | Type | Summary |
|---|---|---|
|
| Defines the external provider authentication URL address. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines password for the user during the authentication process. | |
|
| Array of provider name/value properties. | |
|
| Defines whether provider authentication is required or not. | |
|
| Defines URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
7.84.1. requires_authentication Copy linkLink copied to clipboard!
Defines whether provider authentication is required or not.
If authentication is required, both username and password attributes will be used during authentication.
7.85. ExternalStatus enum Copy linkLink copied to clipboard!
Represents an external status. This status is currently used for hosts and storage domains, and allows an external system to update status of objects it is aware of.
| Name | Summary |
|---|---|
|
| Error status. |
|
| Failure status. |
|
| Info status. |
|
| OK status. |
|
| Warning status. |
7.85.1. error Copy linkLink copied to clipboard!
Error status. There is some kind of error in the relevant object.
7.85.2. failure Copy linkLink copied to clipboard!
Failure status. The relevant object is failing.
7.85.3. info Copy linkLink copied to clipboard!
Info status. The relevant object is in OK status, but there is an information available that might be relevant for the administrator.
7.85.4. ok Copy linkLink copied to clipboard!
OK status. The relevant object is working well.
7.85.5. warning Copy linkLink copied to clipboard!
Warning status. The relevant object is working well, but there is some warning that might be relevant for the administrator.
7.86. ExternalSystemType enum Copy linkLink copied to clipboard!
Represents the type of the external system that is associated with the step.
| Name | Summary |
|---|---|
|
|
Represents |
|
|
Represents |
7.87. ExternalTemplateImport struct Copy linkLink copied to clipboard!
Describes the parameters for the template import operation from an external system. Currently supports OVA only.
| Name | Type | Summary |
|---|---|---|
|
| Optional. | |
|
| The URL to be passed to the engine. |
7.87.1. clone Copy linkLink copied to clipboard!
Optional. Indicates if the identifiers of the imported template should be regenerated.
By default when a template is imported the identifiers are preserved. This means that the same template can’t be imported multiple times, as that identifiers needs to be unique. To allow importing the same template multiple times set this parameter to true, as the default is false.
7.87.2. url Copy linkLink copied to clipboard!
The URL to be passed to the engine.
Example:
ova:///mnt/ova/ova_file.ova
ova:///mnt/ova/ova_file.ova
| Name | Type | Summary |
|---|---|---|
|
| Specifies the target cluster for the resulting template. | |
|
| Optional. | |
|
| Specifies the host that the OVA file exists on. | |
|
| Optional. | |
|
| Specifies the target storage domain for disks. | |
|
| The template entity used to specify a name for the newly created template. |
7.87.3. cpu_profile Copy linkLink copied to clipboard!
Optional. Specifies the CPU profile of the resulting template.
7.87.4. quota Copy linkLink copied to clipboard!
Optional. Specifies the quota that will be applied to the resulting template.
7.87.5. template Copy linkLink copied to clipboard!
The template entity used to specify a name for the newly created template.
If a name is not specified, the source template name will be used.
7.88. ExternalVmImport struct Copy linkLink copied to clipboard!
Describes the parameters for the virtual machine import operation from an external system.
| Name | Type | Summary |
|---|---|---|
|
| The name of the virtual machine to be imported, as is defined within the external system. | |
|
| The password to authenticate against the external hypervisor system. | |
|
| The type of external virtual machine provider. | |
|
| Optional. | |
|
|
The URL to be passed to the | |
|
| The username to authenticate against the external hypervisor system. |
7.88.1. sparse Copy linkLink copied to clipboard!
Optional. Specifies the disk allocation policy of the resulting virtual machine: true for sparse, false for preallocated.
If not specified: - When importing an OVA that was produced by oVirt, it will be determined according to the configuration of the disk within the OVF. - Otherwise, it will be set to true.
7.88.2. url Copy linkLink copied to clipboard!
The URL to be passed to the virt-v2v tool for conversion.
Example:
vpx://wmware_user@vcenter-host/DataCenter/Cluster/esxi-host?no_verify=1
vpx://wmware_user@vcenter-host/DataCenter/Cluster/esxi-host?no_verify=1
More examples can be found at http://libguestfs.org/virt-v2v.1.html.
| Name | Type | Summary |
|---|---|---|
|
| Specifies the target cluster for the resulting virtual machine. | |
|
| Optional. | |
|
| Optional. | |
|
| Optional. | |
|
| Optional. | |
|
| Specifies the target storage domain for converted disks. | |
|
| The virtual machine entity used to specify a name for the newly created virtual machine. |
7.88.3. cpu_profile Copy linkLink copied to clipboard!
Optional. Specifies the CPU profile of the resulting virtual machine.
7.88.4. drivers_iso Copy linkLink copied to clipboard!
Optional. The name of the ISO containing drivers that can be used during the virt-v2v conversion process.
7.88.5. host Copy linkLink copied to clipboard!
Optional. Specifies the host (using host’s ID) to be used for the conversion process. If not specified, one is selected automatically.
7.88.6. quota Copy linkLink copied to clipboard!
Optional. Specifies the quota that will be applied to the resulting virtual machine.
7.88.7. vm Copy linkLink copied to clipboard!
The virtual machine entity used to specify a name for the newly created virtual machine.
If a name is not specified, the source virtual machine name will be used.
7.89. ExternalVmProviderType enum Copy linkLink copied to clipboard!
Describes the type of external hypervisor system.
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.90. Fault struct Copy linkLink copied to clipboard!
7.91. FenceType enum Copy linkLink copied to clipboard!
Type representing the type of the fence operation.
| Name | Summary |
|---|---|
|
| Manual host fencing via power management. |
|
| Restart the host via power management. |
|
| Start the host via power management. |
|
| Check the host power status via power management. |
|
| Stop the host via power management. |
7.92. FencingPolicy struct Copy linkLink copied to clipboard!
Type representing a cluster fencing policy.
| Name | Type | Summary |
|---|---|---|
|
| Enable or disable fencing on this cluster. | |
|
| If enabled, we will not fence a host in case more than a configurable percentage of hosts in the cluster lost connectivity as well. | |
|
| A flag indicating if fencing should be skipped if Gluster bricks are up and running in the host being fenced. | |
|
| A flag indicating if fencing should be skipped if Gluster bricks are up and running and Gluster quorum will not be met without those bricks. | |
|
| If enabled, we will skip fencing in case the host maintains its lease in the storage. |
7.92.1. skip_if_connectivity_broken Copy linkLink copied to clipboard!
If enabled, we will not fence a host in case more than a configurable percentage of hosts in the cluster lost connectivity as well. This comes to prevent fencing storm in cases where there is a global networking issue in the cluster.
7.92.2. skip_if_gluster_bricks_up Copy linkLink copied to clipboard!
A flag indicating if fencing should be skipped if Gluster bricks are up and running in the host being fenced. This flag is optional, and the default value is false.
7.92.3. skip_if_gluster_quorum_not_met Copy linkLink copied to clipboard!
A flag indicating if fencing should be skipped if Gluster bricks are up and running and Gluster quorum will not be met without those bricks. This flag is optional, and the default value is false.
7.92.4. skip_if_sd_active Copy linkLink copied to clipboard!
If enabled, we will skip fencing in case the host maintains its lease in the storage. It means that if the host still has storage access then it won’t get fenced.
7.93. File struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.94. Filter struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.95. FipsMode enum Copy linkLink copied to clipboard!
Representation of the FIPS mode to the cluster.
| Name | Summary |
|---|---|
|
| The FIPS mode is disabled. |
|
| The FIPS mode is enabled. |
|
| The FIPS mode is not yet evaluated. |
7.95.1. disabled Copy linkLink copied to clipboard!
The FIPS mode is disabled.
Its implication is that the FIPS mode is disabled and the hosts within should be with FIPS mode disabled, otherwise they would be non-operational.
7.95.2. enabled Copy linkLink copied to clipboard!
The FIPS mode is enabled.
Its implication is that the FIPS mode is enabled and the hosts within should be with FIPS mode enabled, otherwise they should be non-operational.
7.95.3. undefined Copy linkLink copied to clipboard!
The FIPS mode is not yet evaluated.
Currently, its implication is that the FIPS mode is undetermined. Once a host is added, this value will switch according to the host settings.
7.96. FirewallType enum Copy linkLink copied to clipboard!
Describes all firewall types supported by the system.
| Name | Summary |
|---|---|
|
| FirewallD firewall type. |
|
| IPTables firewall type. |
7.96.1. firewalld Copy linkLink copied to clipboard!
FirewallD firewall type.
When a cluster has the firewall type set to firewalld, the firewalls of all hosts in the cluster will be configured using firewalld. FirewallD replaced IPTables in version 4.2. It simplifies configuration using a command line program and dynamic configuration.
7.96.2. iptables Copy linkLink copied to clipboard!
IPTables firewall type.
iptables is deprecated.
7.97. Floppy struct Copy linkLink copied to clipboard!
The underlying representation of a floppy file.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| File object that represent the Floppy device’s content and its type. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.97.1. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.98. FopStatistic struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.99. GlusterBrick struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| ||
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Optionally references to an instance type the device is used by. | |
|
| ||
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.99.1. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.100. GlusterBrickAdvancedDetails struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| ||
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.100.1. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.101. GlusterBrickMemoryInfo struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.102. GlusterBrickStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
Brick is in |
|
| When the status cannot be determined due to host being non-responsive. |
|
|
Brick is in |
7.103. GlusterClient struct Copy linkLink copied to clipboard!
7.104. GlusterHook struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.105. GlusterHookStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Hook is disabled in the cluster. |
|
| Hook is enabled in the cluster. |
|
| Unknown/missing hook status. |
7.106. GlusterMemoryPool struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
|
7.107. GlusterServerHook struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.108. GlusterState enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.109. GlusterVolume struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.110. GlusterVolumeProfileDetails struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
7.111. GlusterVolumeStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Volume needs to be started, for clients to be able to mount and use it. |
|
| When the status cannot be determined due to host being non-responsive. |
|
| Volume is started, and can be mounted and used by clients. |
7.112. GlusterVolumeType enum Copy linkLink copied to clipboard!
Type representing the type of Gluster Volume.
| Name | Summary |
|---|---|
|
| Dispersed volumes are based on erasure codes, providing space-efficient protection against disk or server failures. |
|
| Distributed volumes distributes files throughout the bricks in the volume. |
|
| Distributed dispersed volumes distribute files across dispersed subvolumes. |
|
| Distributed replicated volumes distributes files across replicated bricks in the volume. |
|
| Distributed striped volumes stripe data across two or more nodes in the cluster. |
|
| Distributed striped replicated volumes distributes striped data across replicated bricks in the cluster. |
|
| Replicated volumes replicates files across bricks in the volume. |
|
| Striped volumes stripes data across bricks in the volume. |
|
| Striped replicated volumes stripes data across replicated bricks in the cluster. |
7.112.1. disperse Copy linkLink copied to clipboard!
Dispersed volumes are based on erasure codes, providing space-efficient protection against disk or server failures.
Dispersed volumes an encoded fragment of the original file to each brick in a way that only a subset of the fragments is needed to recover the original file. The number of bricks that can be missing without losing access to data is configured by the administrator on volume creation time.
7.112.2. distribute Copy linkLink copied to clipboard!
Distributed volumes distributes files throughout the bricks in the volume.
Distributed volumes can be used where the requirement is to scale storage and the redundancy is either not important or is provided by other hardware/software layers.
7.112.3. distributed_disperse Copy linkLink copied to clipboard!
Distributed dispersed volumes distribute files across dispersed subvolumes.
This has the same advantages of distribute replicate volumes, but using disperse to store the data into the bricks.
7.112.4. distributed_replicate Copy linkLink copied to clipboard!
Distributed replicated volumes distributes files across replicated bricks in the volume.
Distributed replicated volumes can be used in environments where the requirement is to scale storage and high-reliability is critical. Distributed replicated volumes also offer improved read performance in most environments.
7.112.5. distributed_stripe Copy linkLink copied to clipboard!
Distributed striped volumes stripe data across two or more nodes in the cluster.
Distributed striped volumes should be used where the requirement is to scale storage and in high concurrency environments accessing very large files is critical.
Note: With the introduction of Sharding in Glusterfs 3.7 releases, striped volumes are not recommended and it will be removed in future release.
7.112.6. distributed_striped_replicate Copy linkLink copied to clipboard!
Distributed striped replicated volumes distributes striped data across replicated bricks in the cluster.
For best results, distributed striped replicated volumes should be used in highly concurrent environments where parallel access of very large files and performance is critical.
Note: With the introduction of Sharding in Glusterfs 3.7 releases, striped volumes are not recommended and it will be removed in future release.
7.112.7. replicate Copy linkLink copied to clipboard!
Replicated volumes replicates files across bricks in the volume.
Replicated volumes can be used in environments where high-availability and high-reliability are critical.
7.112.8. stripe Copy linkLink copied to clipboard!
Striped volumes stripes data across bricks in the volume.
For best results, striped volumes should only in high concurrency environments accessing very large files.
Note: With the introduction of Sharding in Glusterfs 3.7 releases, striped volumes are not recommended and it will be removed in future release.
7.112.9. striped_replicate Copy linkLink copied to clipboard!
Striped replicated volumes stripes data across replicated bricks in the cluster.
For best results, striped replicated volumes should be used in highly concurrent environments where there is parallel access of very large files and performance is critical.
Note: With the introduction of Sharding in Glusterfs 3.7 releases, striped volumes are not recommended and it will be removed in future release.
7.113. GracePeriod struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.114. GraphicsConsole struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.115. GraphicsType enum Copy linkLink copied to clipboard!
The graphics protocol used to connect to the graphic console.
| Name | Summary |
|---|---|
|
| Graphics protocol of type SPICE. |
|
| Graphics protocol of type VNC. |
7.115.1. spice Copy linkLink copied to clipboard!
Graphics protocol of type SPICE. See SPICE documentation for more details.
7.115.2. vnc Copy linkLink copied to clipboard!
Graphics protocol of type VNC. VNC stands for Virtual Network Computing, and it is a graphical desktop sharing system that uses RFB (Remote Frame Buffer) protocol to remotely control another machine.
7.116. Group struct Copy linkLink copied to clipboard!
This type represents all groups in the directory service.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The containing directory service domain id. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Namespace where group resides. |
| Name | Type | Summary |
|---|---|---|
|
| A link to the domain containing this group. | |
|
| A link to the permissions sub-collection for permissions attached to this group. | |
|
| A link to the roles sub-collection for roles attached to this group. | |
|
| Tag[] | A link to the tags sub-collection for tags attached to this group. |
7.116.1. roles Copy linkLink copied to clipboard!
A link to the roles sub-collection for roles attached to this group.
Used only to represent the initial role assignments for a new group; thereafter, modification of role assignments is only supported via the roles sub-collection.
7.117. GuestOperatingSystem struct Copy linkLink copied to clipboard!
Represents an operating system installed on the virtual machine.
To get that information send a request like this:
GET /ovirt-engine/api/vms/123
GET /ovirt-engine/api/vms/123
The result will be like this:
| Name | Type | Summary |
|---|---|---|
|
| The architecture of the operating system, such as x86_64. | |
|
|
Code name of the operating system, such as | |
|
| Full name of operating system distribution. | |
|
|
Family of operating system, such as | |
|
| Kernel version of the operating system. | |
|
| Version of the installed operating system. |
7.118. HardwareInformation struct Copy linkLink copied to clipboard!
Represents hardware information of host.
To get that information send a request like this:
GET /ovirt-engine/api/hosts/123
GET /ovirt-engine/api/hosts/123
The result will be like this:
| Name | Type | Summary |
|---|---|---|
|
| Type of host’s CPU. | |
|
| Manufacturer of the host’s machine and hardware vendor. | |
|
|
Host’s product name (for example | |
|
| Unique ID for host’s chassis. | |
|
| Supported sources of random number generator. | |
|
| Unique ID for each host. | |
|
| Unique name for each of the manufacturer. |
7.119. HighAvailability struct Copy linkLink copied to clipboard!
Type representing high availability of a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| Define if the virtual machine is considered highly available. | |
|
| Indicates the priority of the virtual machine inside the run and migration queues. |
7.119.1. enabled Copy linkLink copied to clipboard!
Define if the virtual machine is considered highly available. Configuring a VM lease is highly recommended (refer to that section) in order to prevent split-brain scenarios. Use a boot disk’s storage-domain or any other active storage-domain.
7.119.2. priority Copy linkLink copied to clipboard!
Indicates the priority of the virtual machine inside the run and migration queues.
Virtual machines with higher priorities will be started and migrated before virtual machines with lower priorities.
The value is an integer between 0 and 100. The higher the value, the higher the priority.
The graphical user interface (GUI) does not allow specifying all the possible values, instead it only allows you to select Low, Medium or High. When the value is set using the API, the GUI will set the label as follows:
| API Value | GUI Label |
|---|---|
| 0 - 25 | Low |
| 26 - 74 | Medium |
| 75 - 100 | High |
When the label is selected using the GUI, the value in the API will be set as follows:
| GUI Label | API Value |
|---|---|
| Low | 1 |
| Medium | 50 |
| High | 100 |
7.120. Hook struct Copy linkLink copied to clipboard!
Represents a hook.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| Name of the event to execute the hook on. | |
|
| A unique identifier. | |
|
| Checksum of the hook. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to the host the hook belongs to. |
7.121. HookContentType enum Copy linkLink copied to clipboard!
Represents content type of hook script.
| Name | Summary |
|---|---|
|
| Binary content type of the hook. |
|
| Text content type of the hook. |
7.122. HookStage enum Copy linkLink copied to clipboard!
Type represents a stage of volume event at which hook executes.
| Name | Summary |
|---|---|
|
| Stage after start of volume. |
|
| Stage before start of volume. |
7.123. HookStatus enum Copy linkLink copied to clipboard!
Type represents the status of a hook.
| Name | Summary |
|---|---|
|
| Hook is disabled. |
|
| Hook is enabled. |
|
| Hook is missing. |
7.124. Host struct Copy linkLink copied to clipboard!
Type representing a host.
| Name | Type | Summary |
|---|---|---|
|
| The host address (FQDN/IP). | |
|
| The host auto non uniform memory access (NUMA) status. | |
|
| The host certificate. | |
|
| Free text containing comments about this object. | |
|
| The CPU type of this host. | |
|
| A human-readable description in plain text. | |
|
| Specifies whether host device passthrough is enabled on this host. | |
|
| Optionally specify the display address of this host explicitly. | |
|
| The host external status. | |
|
| The host hardware information. | |
|
| The self-hosted engine status of this host. | |
|
| A unique identifier. | |
|
| The host iSCSI details. | |
|
| The host KDUMP status. | |
|
| Kernel SamePage Merging (KSM) reduces references to memory pages from multiple identical pages to a single page reference. | |
|
| The host libvirt version. | |
|
| The max scheduling memory on this host in bytes. | |
|
| The amount of physical memory on this host in bytes. | |
|
| A human-readable name in plain text. | |
|
| Specifies whether a network-related operation, such as 'setup networks', 'sync networks', or 'refresh capabilities', is currently being executed on this host. | |
|
| Specifies whether non uniform memory access (NUMA) is supported on this host. | |
|
| The operating system on this host. | |
|
| Specifies whether we should override firewall definitions. | |
|
| Indicates if the host has correctly configured OVN. | |
|
| The host port. | |
|
| The host power management definitions. | |
|
| The protocol that the engine uses to communicate with the host. | |
|
| Specifies whether the host should be reinstalled. | |
|
| When creating a new host, a root password is required if the password authentication method is chosen, but this is not subsequently included in the representation. | |
|
| The host SElinux status. | |
|
| The host storage pool manager (SPM) status and definition. | |
|
| The SSH definitions. | |
|
| The host status. | |
|
| The host status details. | |
|
| The virtual machine summary - how many are active, migrating and total. | |
|
| Transparent huge page support expands the size of memory pages beyond the standard 4 KiB limit. | |
|
| Indicates if the host contains a full installation of the operating system or a scaled-down version intended only to host virtual machines. | |
|
| Specifies whether there is an oVirt-related update on this host. | |
|
| The version of VDSM. | |
|
| Specifies the vGPU placement strategy. |
7.124.1. external_status Copy linkLink copied to clipboard!
The host external status. This can be used by third-party software to change the host external status in case of an issue. This has no effect on the host lifecycle, unless a third-party software checks for this status and acts accordingly.
7.124.2. hosted_engine Copy linkLink copied to clipboard!
The self-hosted engine status of this host.
7.124.3. kdump_status Copy linkLink copied to clipboard!
The host KDUMP status. KDUMP happens when the host kernel has crashed and it is now going through memory dumping.
7.124.4. ksm Copy linkLink copied to clipboard!
Kernel SamePage Merging (KSM) reduces references to memory pages from multiple identical pages to a single page reference. This helps with optimization for memory density.
For example, to enable KSM for host 123, send a request like this:
PUT /ovirt-engine/api/hosts/123
PUT /ovirt-engine/api/hosts/123
With a request body like this:
<host>
<ksm>
<enabled>true</enabled>
</ksm>
</host>
<host>
<ksm>
<enabled>true</enabled>
</ksm>
</host>
7.124.5. libvirt_version Copy linkLink copied to clipboard!
The host libvirt version. For more information on libvirt please go to libvirt.
7.124.6. network_operation_in_progress Copy linkLink copied to clipboard!
Specifies whether a network-related operation, such as 'setup networks', 'sync networks', or 'refresh capabilities', is currently being executed on this host.
The header All-Content:true must be added to the request in order for this attribute to be included in the response.
7.124.7. override_iptables Copy linkLink copied to clipboard!
Specifies whether we should override firewall definitions. This applies only when the host is installed or re-installed.
7.124.8. protocol Copy linkLink copied to clipboard!
The protocol that the engine uses to communicate with the host.
Since version 4.1 of the engine the protocol is always set to stomp since xml was removed.
7.124.9. se_linux Copy linkLink copied to clipboard!
The host SElinux status. Security-Enhanced Linux (SELinux) is a component in the Linux kernel that provides a mechanism for supporting access control security policies.
7.124.10. spm Copy linkLink copied to clipboard!
The host storage pool manager (SPM) status and definition. Use it to set the SPM priority of this host, and to see whether this is the current SPM or not.
7.124.11. status_detail Copy linkLink copied to clipboard!
The host status details. Relevant for Gluster hosts.
7.124.12. transparent_huge_pages Copy linkLink copied to clipboard!
Transparent huge page support expands the size of memory pages beyond the standard 4 KiB limit. This reduces memory consumption and increases host performance.
For example, to enable transparent huge page support for host 123, send a request like this:
PUT /ovirt-engine/api/hosts/123
PUT /ovirt-engine/api/hosts/123
With a request body like this:
<host>
<transparent_hugepages>
<enabled>true</enabled>
</transparent_hugepages>
</host>
<host>
<transparent_hugepages>
<enabled>true</enabled>
</transparent_hugepages>
</host>
7.124.13. version Copy linkLink copied to clipboard!
The version of VDSM.
For example:
GET /ovirt-engine/api/hosts/123
GET /ovirt-engine/api/hosts/123
This GET request will return the following output:
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| List of all host’s CPUs with detailed information about the topology (socket, core) and with information about the current CPU pinning. | |
|
| ||
|
| ||
|
| External network providers provisioned on the host. | |
|
| ||
|
| Lists all the Katello errata assigned to the host. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Each host resource exposes a statistics sub-collection for host-specific statistics. | |
|
| ||
|
| ||
|
| Tag[] | |
|
|
7.124.14. cpu_units Copy linkLink copied to clipboard!
List of all host’s CPUs with detailed information about the topology (socket, core) and with information about the current CPU pinning.
GET /ovirt-engine/api/hosts/123/cpuunits
GET /ovirt-engine/api/hosts/123/cpuunits
You will receive response in XML like this one:
7.124.15. external_network_provider_configurations Copy linkLink copied to clipboard!
External network providers provisioned on the host.
This attribute is read-only. Setting it will have no effect on the host. The value of this parameter reflects the Default Network Provider of the cluster.
7.124.16. katello_errata Copy linkLink copied to clipboard!
Lists all the Katello errata assigned to the host.
GET /ovirt-engine/api/hosts/123/katelloerrata
GET /ovirt-engine/api/hosts/123/katelloerrata
You will receive response in XML like this one:
7.124.17. statistics Copy linkLink copied to clipboard!
Each host resource exposes a statistics sub-collection for host-specific statistics.
An example of an XML representation:
This statistics sub-collection is read-only.
The following list shows the statistic types for hosts:
| Name | Description |
|---|---|
|
| Total memory in bytes on the host. |
|
| Memory in bytes used on the host. |
|
| Memory in bytes free on the host. |
|
| Memory in bytes shared on the host. |
|
| I/O buffers in bytes. |
|
| OS caches in bytes. |
|
| Total swap memory in bytes on the host. |
|
| Swap memory in bytes free on the host. |
|
| Swap memory in bytes used on the host. |
|
| Swap memory in bytes also cached in host’s memory. |
|
| Percentage of CPU usage for Kernel SamePage Merging. |
|
| Percentage of CPU usage for user slice. |
|
| Percentage of CPU usage for system. |
|
| Percentage of idle CPU usage. |
|
| CPU load average per five minutes. |
|
| Boot time of the machine. |
7.125. HostCpuUnit struct Copy linkLink copied to clipboard!
Type representing a physical CPU of a host with the current pinning status.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| The id of the core the CPU belongs to. | |
|
| The id of the CPU. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| A flag indicating that the CPU runs the VDSM | |
|
| The id of the socket the CPU belongs to. |
| Name | Type | Summary |
|---|---|---|
|
| Vm[] | A list of VMs that has its virtual CPU pinned to this physical CPU. |
7.126. HostDevice struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The name of the driver this device is bound to. | |
|
| A unique identifier. | |
|
| ||
|
| List of all supported mdev types on the physical device, | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.126.1. driver Copy linkLink copied to clipboard!
The name of the driver this device is bound to.
For example: pcieport or uhci_hcd.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.127. HostDevicePassthrough struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.128. HostNic struct Copy linkLink copied to clipboard!
Represents a host NIC.
For example, the XML representation of a host NIC looks like this:
A bonded interface is represented as a HostNic object containing the bonding and slaves attributes.
For example, the XML representation of a bonded host NIC looks like this:
| Name | Type | Summary |
|---|---|---|
|
|
The | |
|
| The base interface of the NIC. | |
|
| The bonding parameters of the NIC. | |
|
| The IPv4 boot protocol configuration of the NIC. | |
|
| Defines the bridged network status. | |
|
| ||
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The IPv4 address of the NIC. | |
|
| The IPv6 address of the NIC. | |
|
| The IPv6 boot protocol configuration of the NIC. | |
|
| The MAC address of the NIC. | |
|
| The maximum transmission unit for the interface. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Describes the virtual functions configuration of a physical function NIC. | |
|
|
7.128.1. ad_aggregator_id Copy linkLink copied to clipboard!
The ad_aggregator_id property of a bond or bond slave, for bonds in mode 4. Bond mode 4 is the 802.3ad standard, also called dynamic link aggregation. (See Wikipedia and Presentation for more information). This is only valid for bonds in mode 4, or NICs which are part of a bond. It is not present for bonds in other modes, or NICs which are not part of a bond in mode 4. The ad_aggregator_id property indicates which of the bond slaves are active. The value of the ad_aggregator_id of an active slave is the same as the value of the ad_aggregator_id property of the bond. This parameter is read only. Setting it will have no effect on the bond/NIC. It is retrieved from the /sys/class/net/bondX/bonding/ad_aggregator file for a bond, and the /sys/class/net/ensX/bonding_slave/ad_aggregator_id file for a NIC.
7.128.2. bridged Copy linkLink copied to clipboard!
Defines the bridged network status. Set to true for a bridged network and false for a bridgeless network.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| A reference to the network to which the interface should be connected. | |
|
| The labels that are applied to this NIC. | |
|
| A reference to the physical function NIC of a SR-IOV virtual function NIC. | |
|
| A link to the quality-of-service configuration of the interface. | |
|
| A link to the statistics of the NIC. |
7.128.3. network Copy linkLink copied to clipboard!
A reference to the network to which the interface should be connected. A blank network ID is allowed.
7.128.4. statistics Copy linkLink copied to clipboard!
A link to the statistics of the NIC.
The data types for HostNic statistical values:
- data.current.rx - The rate in bytes per second of data received.
- data.current.tx - The rate in bytes per second of data transmitted.
- data.current.rx.bps - The rate in bits per second of data received (since version 4.2).
- data.current.tx.bps - The rate in bits per second of data transmitted (since version 4.2).
- data.total.rx - Total received data.
- data.total.tx - Total transmitted data.
- errors.total.rx - Total errors from receiving data.
- errors.total.tx - Total errors from transmitting data.
7.129. HostNicVirtualFunctionsConfiguration struct Copy linkLink copied to clipboard!
Describes the virtual functions configuration of an SR-IOV-enabled physical function NIC.
| Name | Type | Summary |
|---|---|---|
|
| Defines whether all networks are allowed to be defined on the related virtual functions, or specified ones only. | |
|
| The maximum number of virtual functions the NIC supports. | |
|
| The number of virtual functions currently defined. |
7.129.1. max_number_of_virtual_functions Copy linkLink copied to clipboard!
The maximum number of virtual functions the NIC supports. This property is read-only.
7.129.2. number_of_virtual_functions Copy linkLink copied to clipboard!
The number of virtual functions currently defined. A user-defined value between 0 and max_number_of_virtual_functions.
7.130. HostProtocol enum Copy linkLink copied to clipboard!
The protocol used by the engine to communicate with a host.
Since version 4.1 of the engine the protocol is always set to stomp since xml was removed.
| Name | Summary |
|---|---|
|
| JSON-RPC protocol on top of STOMP. |
|
| XML-RPC protocol. |
7.131. HostStatus enum Copy linkLink copied to clipboard!
Type representing a host status.
| Name | Summary |
|---|---|
|
| The engine cannot communicate with the host for a specific threshold so it is now trying to connect before going through fencing. |
|
| The host is down. |
|
| The host is in error status. |
|
| The host is initializing. |
|
| The host installation failed. |
|
| The host is being installed. |
|
| The host operating system is now installing. |
|
| The host kernel has crashed and it is now going through memory dumping. |
|
| The host is in maintenance status. |
|
| The host is non operational. |
|
| The host is not responsive. |
|
| The host is pending administrator approval. |
|
| The host is preparing for maintenance. |
|
| The host is being rebooted. |
|
| The host is in activation process. |
|
| The host is up. |
7.131.1. error Copy linkLink copied to clipboard!
The host is in error status. This will happen if we will try to run a virtual machine several times and it will fail.
7.131.2. initializing Copy linkLink copied to clipboard!
The host is initializing. This is an intermediate step before moving the host to 'up' status.
7.131.3. install_failed Copy linkLink copied to clipboard!
The host installation failed. In such cases look at the event log to understand what failed the installation, and issue a re-install.
7.131.4. installing_os Copy linkLink copied to clipboard!
The host operating system is now installing. This status is relevant when using a Satellite/Foreman provider, and issuing a bare-metal provisioning (discovered host provisioning).
7.131.5. maintenance Copy linkLink copied to clipboard!
The host is in maintenance status. When a host is in maintenance it cannot run virtual machines.
7.131.6. non_operational Copy linkLink copied to clipboard!
The host is non operational. This can happen due to various reasons, such as not having a connection with the storage, not supporting a mandatory network, not supporting the cluster level, and more.
7.131.7. non_responsive Copy linkLink copied to clipboard!
The host is not responsive. This means that the engine is not able to communicate with the host.
7.131.8. pending_approval Copy linkLink copied to clipboard!
The host is pending administrator approval. This is relevant only for vintage ovirt-node / RHV-H. This property is no longer relevant since Vintage Node is no longer supported, and has been deprecated.
7.131.9. preparing_for_maintenance Copy linkLink copied to clipboard!
The host is preparing for maintenance. During this time the engine makes sure to live migrate all the virtual machines from this host to other hosts. Once all migrations have been completed the host will move to 'maintenance' status.
7.132. HostStorage struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The options to be passed when creating a storage domain using a cinder driver. | |
|
| Parameters containing sensitive information, to be passed when creating a storage domain using a cinder driver. | |
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| The number of times to retry a request before attempting further recovery actions. | |
|
| The time in tenths of a second to wait for a response before retrying NFS requests. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.132.1. driver_options Copy linkLink copied to clipboard!
The options to be passed when creating a storage domain using a cinder driver.
For example (Kaminario backend):
POST /ovirt-engine/api/storagedomains/
POST /ovirt-engine/api/storagedomains/
7.132.2. driver_sensitive_options Copy linkLink copied to clipboard!
Parameters containing sensitive information, to be passed when creating a storage domain using a cinder driver. These parameters are encrypted when they are saved.
For example, the following XML encrypts and saves a username, password and SAN IP address:
POST /ovirt-engine/api/storagedomains/
POST /ovirt-engine/api/storagedomains/
7.132.3. nfs_retrans Copy linkLink copied to clipboard!
The number of times to retry a request before attempting further recovery actions. The value must be in the range of 0 to 65535. For more details see the description of the retrans mount option in the nfs man page.
7.132.4. nfs_timeo Copy linkLink copied to clipboard!
The time in tenths of a second to wait for a response before retrying NFS requests. The value must be in the range of 0 to 65535. For more details see the description of the timeo mount option in the nfs man page.
| Name | Type | Summary |
|---|---|---|
|
|
7.133. HostType enum Copy linkLink copied to clipboard!
This enumerated type is used to determine which type of operating system is used by the host.
| Name | Summary |
|---|---|
|
| The host contains Red Hat Virtualization Host (RHVH): a new implementation of Red Hat Enterprise Virtualization Hypervisor (RHEV-H) which uses the same installer as Red Hat Enterprise Linux, CentOS, or Fedora. |
|
| The host contains a full Red Hat Enterprise Linux, CentOS, or Fedora installation. |
|
| The host contains Red Hat Enterprise Virtualization Hypervisor (RHEV-H), a small-scaled version of Red Hat Enterprise Linux, CentOS, or Fedora, used solely to host virtual machines. |
7.133.1. ovirt_node Copy linkLink copied to clipboard!
The host contains Red Hat Virtualization Host (RHVH): a new implementation of Red Hat Enterprise Virtualization Hypervisor (RHEV-H) which uses the same installer as Red Hat Enterprise Linux, CentOS, or Fedora. The main difference between RHVH and legacy RHEV-H is that RHVH has a writeable file system and will handle its own installation instead of having RPMs pushed to it by the Manager like in legacy RHEV-H.
7.133.2. rhev_h Copy linkLink copied to clipboard!
The host contains Red Hat Enterprise Virtualization Hypervisor (RHEV-H), a small-scaled version of Red Hat Enterprise Linux, CentOS, or Fedora, used solely to host virtual machines.
This property is no longer relevant since Vintage Node is no longer supported, and has been deprecated.
7.134. HostedEngine struct Copy linkLink copied to clipboard!
7.135. Icon struct Copy linkLink copied to clipboard!
Icon of virtual machine or template.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| Base64 encode content of the icon file. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| Format of icon file. | |
|
| A human-readable name in plain text. |
7.135.1. media_type Copy linkLink copied to clipboard!
Format of icon file.
One of:
-
image/jpeg -
image/png -
image/gif
7.136. Identified struct Copy linkLink copied to clipboard!
This interface is the base model for all types that represent objects with an identifier.
7.137. Image struct Copy linkLink copied to clipboard!
Represents an image entity.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The size of the image file. | |
|
| The type of the image file. |
| Name | Type | Summary |
|---|---|---|
|
| The storage domain associated with this image. |
7.138. ImageFileType enum Copy linkLink copied to clipboard!
Represents the file type of an image.
| Name | Summary |
|---|---|
|
| The image is a disk format that can be used as a virtual machine’s disk. |
|
| The image is a floppy disk that can be attached to a virtual machine, for example to install the VirtIO drivers in Windows. |
|
| The image is a `. |
7.138.1. iso Copy linkLink copied to clipboard!
The image is a .iso file that can be used as a CD-ROM to boot and install a virtual machine.
7.139. ImageTransfer struct Copy linkLink copied to clipboard!
This type contains information regarding an image transfer being performed.
| Name | Type | Summary |
|---|---|---|
|
| Indicates whether there’s at least one active session for this transfer, i,e there’s at least one live transfer session between the client and the daemon. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
|
The direction indicates whether the transfer is sending image data ( | |
|
| The format of the data sent during upload or received during download. | |
|
| A unique identifier. | |
|
| The timeout in seconds of client inactivity, after which the transfer is aborted by the Red Hat Virtualization Manager. | |
|
| A human-readable name in plain text. | |
|
| The current phase of the image transfer in progress. | |
|
| The URL of the proxy server that the user inputs or outputs to. | |
|
| Download only the specified image instead of the entire image chain. | |
|
| Timeout policy determines how the system handles the transfer when a client is idle for more than inactivityTimeout. | |
|
| The URL of the daemon server that the user can input or output to directly. | |
|
| Indicates the amount of transferred bytes. |
7.139.1. direction Copy linkLink copied to clipboard!
The direction indicates whether the transfer is sending image data (upload) or receiving image data (download).
If a direction is not set during an addition of a new transfer, The default direction for the transfer will be upload.
7.139.2. format Copy linkLink copied to clipboard!
The format of the data sent during upload or received during download. If not specified, defaults to disk’s format.
7.139.3. inactivity_timeout Copy linkLink copied to clipboard!
The timeout in seconds of client inactivity, after which the transfer is aborted by the Red Hat Virtualization Manager. To disable the inactivity timeout specify '0'. If not specified, the value is defaulted to the engine-config value: TransferImageClientInactivityTimeoutInSeconds.
7.139.4. phase Copy linkLink copied to clipboard!
The current phase of the image transfer in progress. Each transfer needs a managed session, which must be opened for the user to input or output an image. Please refer to image transfer for further documentation.
7.139.5. proxy_url Copy linkLink copied to clipboard!
The URL of the proxy server that the user inputs or outputs to. This attribute is available only if the image transfer is in the transferring phase. See phase for details.
7.139.6. shallow Copy linkLink copied to clipboard!
Download only the specified image instead of the entire image chain.
If true, when using format="raw" and direction="download", the transfer includes data only from the specified disk snapshot, and unallocated areas are reported as holes. By default, the transfer includes data from all disk snapshots.
When specifying a disk snapshot, the transfer includes only data for the specified disk snapshot. When specifying a disk, the transfer includes only data from the active disk snaphost.
This parameter has no effect when not using format="raw" or for direction="upload".
Example: Downloading a single snapshot:
To download the active snapshot disk image (which is not accessible as a disk snapshot), specify the disk:
In both cases you can now download a qcow2 image using imageio client:
7.139.7. transfer_url Copy linkLink copied to clipboard!
The URL of the daemon server that the user can input or output to directly.
This is as an alternative to the proxy_url. I.e. if the client has access to the host machine, it could bypass the proxy and transfer directly to the host, potentially improving the throughput performance. This attribute is available only if the image transfer is in the transferring phase. See phase for details.
| Name | Type | Summary |
|---|---|---|
|
| The backup associated with the image transfer. | |
|
| The disk which is targeted for input or output. | |
|
| The host which will be used to write to the image which is targeted for input or output. | |
|
| The image which is targeted for input or output. | |
|
| The disk snapshot which is targeted for input or output. |
7.139.8. backup Copy linkLink copied to clipboard!
The backup associated with the image transfer. Specify when initiating an image transfer for a disk that is part of a backup.
7.139.9. host Copy linkLink copied to clipboard!
The host which will be used to write to the image which is targeted for input or output. If not specified, an active host will be randomly selected from the data center.
7.139.10. image Copy linkLink copied to clipboard!
The image which is targeted for input or output.
This attribute is deprecated since version 4.2 of the engine. Use the disk or snapshot attributes instead.
7.140. ImageTransferDirection enum Copy linkLink copied to clipboard!
The image transfer direction for a transfer.
When adding a new transfer, the user can choose whether the transfer will be to an image, choosing upload, or to transfer from an image- choosing download as an ImageTransferDirection.
Please refer to image transfer for further documentation.
| Name | Summary |
|---|---|
|
|
The user must choose |
|
|
The user can choose |
7.141. ImageTransferPhase enum Copy linkLink copied to clipboard!
A list of possible phases for an image transfer entity. Each of these values defines a specific point in a transfer flow.
Please refer to image transfer for more information.
| Name | Summary |
|---|---|
|
| This phase will be set as a result of the user cancelling the transfer. |
|
| This phase will be set as a result of the system cancelling the transfer. |
|
| This phase will be set as a result of the user cancelling the transfer. |
|
| This phase indicates that the user cancelled the transfer, and necessary cleanup is being done. |
|
| This phase can only be set in the Administration Portal, and indicates that there was an error during the transfer, and it is being finalized with a failure. |
|
| This phase will be set when the user calls finalize. |
|
| This phase indicates that the user cancelled the transfer, and necessary cleanup is done. |
|
| Indicates that the targeted image failed the verification, and cannot be used. |
|
| Indicates that the transfer session was successfully closed, and the targeted image was verified and ready to be used. |
|
| The initial phase of an image transfer. |
|
| This phase means the session timed out, or some other error occurred with this transfer; for example ovirt-imageio is not running in the selected host. |
|
| This phase is a result of a pause call by the user, using pause. |
|
| The phase where the transfer has been resumed by the client calling resume. |
|
| The phase where the transfer session is open, and the client can input or output the desired image using the preferred tools. |
|
| An unknown phase. |
7.141.1. cancelled Copy linkLink copied to clipboard!
This phase will be set as a result of the user cancelling the transfer. The cancellation can only be performed in the Administration Portal.
7.141.2. finalizing_success Copy linkLink copied to clipboard!
This phase will be set when the user calls finalize. Calling finalize is essential to finish the transfer session, and finish using the targeted image. After finalizing, the phase will be changed to finished_success or finished_failure.
Refer to image transfer for more information.
7.141.3. finished_failure Copy linkLink copied to clipboard!
Indicates that the targeted image failed the verification, and cannot be used. After reaching this phase, the image transfer entity will be deleted, and the targeted image will be set to illegal. System cancelling the transfer will also result in this.
7.141.4. finished_success Copy linkLink copied to clipboard!
Indicates that the transfer session was successfully closed, and the targeted image was verified and ready to be used. After reaching this phase, the image transfer entity will be deleted.
7.141.5. initializing Copy linkLink copied to clipboard!
The initial phase of an image transfer. It is set while the transfer session is establishing. Once the session is established, the phase will be changed to transferring
7.141.6. paused_system Copy linkLink copied to clipboard!
This phase means the session timed out, or some other error occurred with this transfer; for example ovirt-imageio is not running in the selected host. To resume the session, the client should call resume. After resuming, the phase will change to resuming.
7.141.7. resuming Copy linkLink copied to clipboard!
The phase where the transfer has been resumed by the client calling resume. Resuming starts a new session, and after calling it, the phase will be changed to transferring, or paused_system in case of a failure.
7.141.8. unknown Copy linkLink copied to clipboard!
An unknown phase. This will only be set in cases of unpredictable errors.
7.142. ImageTransferTimeoutPolicy enum Copy linkLink copied to clipboard!
The image transfer timeout policy.
Define how the system handles a transfer when the client is inactive for inactivityTimeout seconds.
Please refer to image transfer for further documentation.
| Name | Summary |
|---|---|
|
| Cancel the transfer and unlock the disk. |
|
| LEGACY policy will preserve the legacy functionality which is the default. |
|
| Pause the transfer. |
7.142.1. cancel Copy linkLink copied to clipboard!
Cancel the transfer and unlock the disk. For image transfer using upload direction, the disk is deleted.
7.142.2. legacy Copy linkLink copied to clipboard!
LEGACY policy will preserve the legacy functionality which is the default. The default behaviour will cancel the transfer if the direction is download, and pause it if its upload.
7.142.3. pause Copy linkLink copied to clipboard!
Pause the transfer. The transfer can be resumed or canceled by the user. The disk will remain locked while the transfer is paused.
7.143. InheritableBoolean enum Copy linkLink copied to clipboard!
Enum representing the boolean value that can be either set, or inherited from a higher level. The inheritance order is virtual machine → cluster → engine-config.
| Name | Summary |
|---|---|
|
| Set the value to false on this level. |
|
| Inherit the value from higher level. |
|
| Set the value to true on this level. |
7.144. Initialization struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| Deprecated attribute to specify cloud-init configuration. | |
|
| Attribute specifying the cloud-init protocol to use for formatting the cloud-init network parameters. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.144.1. cloud_init Copy linkLink copied to clipboard!
Deprecated attribute to specify cloud-init configuration.
This attribute and the CloudInit type have been deprecated and will be removed in the future. To specify the cloud-init configuration, use the attributes inside the Initialization type. The mapping between the attributes of these two types are as follows:
| CloudInit | Initialization |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For more details on how to use cloud-init see the examples in Python and Java.
7.144.2. cloud_init_network_protocol Copy linkLink copied to clipboard!
Attribute specifying the cloud-init protocol to use for formatting the cloud-init network parameters. If omitted, a default value is used, as described in the CloudInitNetworkProtocol
7.145. InstanceType struct Copy linkLink copied to clipboard!
Describes the hardware configuration of virtual machines.
For example medium instance type includes 1 virtual CPU and 4 GiB of memory. It is a top-level entity (e.g. not bound to any data center or cluster). The attributes that are used for instance types and are common to virtual machine and template types are:
-
console -
cpu -
custom_cpu_model -
custom_emulated_machine -
display -
high_availability -
io -
memory -
memory_policy -
migration -
migration_downtime -
os -
rng_device -
soundcard_enabled -
usb -
virtio_scsi
When creating a virtual machine from both an instance type and a template, the virtual machine will inherit the hardware configurations from the instance type
An instance type inherits it’s attributes from the template entity although most template attributes are not used in instance types.
| Name | Type | Summary |
|---|---|---|
|
| Specifies if and how the auto CPU and NUMA configuration is applied. | |
|
| Reference to virtual machine’s BIOS configuration. | |
|
| Free text containing comments about this object. | |
|
| Console configured for this virtual machine. | |
|
| The configuration of the virtual machine CPU. | |
|
| Specifies if and how the CPU and NUMA configuration is applied. | |
|
| ||
|
| The virtual machine creation date. | |
|
| Virtual machine custom compatibility version. | |
|
| ||
|
| ||
|
| Properties sent to VDSM to configure various hooks. | |
|
|
If | |
|
| A human-readable description in plain text. | |
|
| The virtual machine display configuration. | |
|
| Domain configured for this virtual machine. | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to the virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| Reference to the storage domain this virtual machine/template lease reside on. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of a running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
|
If | |
|
| A human-readable name in plain text. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| The configuration of the virtual machine’s placement policy. | |
|
| Random Number Generator device configuration for this virtual machine. | |
|
| Virtual machine’s serial number in a cluster. | |
|
| Virtual machine’s small icon. | |
|
|
If | |
|
| Reference to the Single Sign On configuration this virtual machine is configured for. | |
|
|
If | |
|
|
If | |
|
| The status of the template. | |
|
| Determines how the virtual machine will be resumed after storage error. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
If | |
|
|
If | |
|
| Determines whether the virtual machine is optimized for desktop or server. | |
|
| Configuration of USB devices for this virtual machine (count, type). | |
|
| Indicates whether this is the base version or a sub-version of another template. | |
|
| Reference to VirtIO SCSI configuration. | |
|
| Number of queues for a Virtio-SCSI contoller this field requires virtioScsiMultiQueuesEnabled to be true see virtioScsiMultiQueuesEnabled for more info | |
|
|
If | |
|
| The virtual machine configuration associated with this template. |
7.145.1. auto_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the auto CPU and NUMA configuration is applied.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It might be removed in the future. Please use CpuPinningPolicy instead.
7.145.2. cpu Copy linkLink copied to clipboard!
The configuration of the virtual machine CPU.
The socket configuration can be updated without rebooting the virtual machine. The cores and the threads require a reboot.
For example, to change the number of sockets to 4 immediately, and the number of cores and threads to 2 after reboot, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body:
7.145.3. cpu_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the CPU and NUMA configuration is applied. When not specified the previous behavior of CPU pinning string will determine CpuPinningPolicy to None or Manual.
7.145.4. custom_compatibility_version Copy linkLink copied to clipboard!
Virtual machine custom compatibility version.
Enables a virtual machine to be customized to its own compatibility version. If custom_compatibility_version is set, it overrides the cluster’s compatibility version for this particular virtual machine.
The compatibility version of a virtual machine is limited by the data center the virtual machine resides in, and is checked against capabilities of the host the virtual machine is planned to run on.
7.145.5. high_availability Copy linkLink copied to clipboard!
The virtual machine high availability configuration. If set, the virtual machine will be automatically restarted when it unexpectedly goes down.
7.145.6. initialization Copy linkLink copied to clipboard!
Reference to the virtual machine’s initialization configuration.
Since Red Hat Virtualization 4.1.8 this property can be cleared by sending an empty tag.
For example, to clear the initialization attribute send a request like this:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body like this:
<vm> <initialization/> </vm>
<vm>
<initialization/>
</vm>
The response to such a request, and requests with the header All-Content: true will still contain this attribute.
7.145.7. large_icon Copy linkLink copied to clipboard!
Virtual machine’s large icon. Either set by user or refers to image set according to operating system.
7.145.8. lease Copy linkLink copied to clipboard!
Reference to the storage domain this virtual machine/template lease reside on.
A virtual machine running with a lease requires checking while running that the lease is not taken by another host, preventing another instance of this virtual machine from running on another host. This provides protection against split-brain in highly available virtual machines. A template can also have a storage domain defined for a lease in order to have the virtual machines created from this template to be preconfigured with this storage domain as the location of the leases.
7.145.9. memory Copy linkLink copied to clipboard!
The virtual machine’s memory, in bytes.
For example, to update a virtual machine to contain 1 Gibibyte (GiB) of memory, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With the following request body:
<vm> <memory>1073741824</memory> </vm>
<vm>
<memory>1073741824</memory>
</vm>
Memory hot plug is supported from Red Hat Virtualization 3.6 onwards. You can use the example above to increase memory while the virtual machine is in state up. The size increment must be dividable by the value of the HotPlugMemoryBlockSizeMb configuration value (256 MiB by default). If the memory size increment is not dividable by this value, the memory size change is only stored to next run configuration. Each successful memory hot plug operation creates one or two new memory devices.
Memory hot unplug is supported since Red Hat Virtualization 4.2 onwards. Memory hot unplug can only be performed when the virtual machine is in state up. Only previously hot plugged memory devices can be removed by the hot unplug operation. The requested memory decrement is rounded down to match sizes of a combination of previously hot plugged memory devices. The requested memory value is stored to next run configuration without rounding.
Memory in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
Red Hat Virtualization Manager internally rounds values down to whole MiBs (1MiB = 220 bytes)
7.145.10. migration Copy linkLink copied to clipboard!
Reference to configuration of migration of a running virtual machine to another host.
API for querying migration policy by ID returned by this method is not implemented yet. Use /ovirt-engine/api/options/MigrationPolicies to get a list of all migration policies with their IDs.
7.145.11. migration_downtime Copy linkLink copied to clipboard!
Maximum time the virtual machine can be non responsive during its live migration to another host in ms.
Set either explicitly for the virtual machine or by engine-config -s DefaultMaximumMigrationDowntime=[value]
7.145.12. origin Copy linkLink copied to clipboard!
The origin of this virtual machine.
Possible values:
-
ovirt -
rhev -
vmware -
xen -
external -
hosted_engine -
managed_hosted_engine -
kvm -
physical_machine -
hyperv
7.145.13. placement_policy Copy linkLink copied to clipboard!
The configuration of the virtual machine’s placement policy.
This configuration can be updated to pin a virtual machine to one or more hosts.
Virtual machines that are pinned to multiple hosts cannot be live migrated, but in the event of a host failure, any virtual machine configured to be highly available is automatically restarted on one of the other hosts to which the virtual machine is pinned.
For example, to pin a virtual machine to two hosts, send the following request:
PUT /api/vms/123
PUT /api/vms/123
With a request body like this:
7.145.14. small_icon Copy linkLink copied to clipboard!
Virtual machine’s small icon. Either set by user or refers to image set according to operating system.
7.145.15. sso Copy linkLink copied to clipboard!
Reference to the Single Sign On configuration this virtual machine is configured for. The user can be automatically signed in the virtual machine’s operating system when console is opened.
7.145.16. tpm_enabled Copy linkLink copied to clipboard!
If true, a TPM device is added to the virtual machine. By default the value is false. This property is only visible when fetching if "All-Content=true" header is set.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the CD-ROM devices attached to the template. | |
|
| Reference to cluster the virtual machine belongs to. | |
|
| Reference to CPU profile used by this virtual machine. | |
|
| Reference to the disks attached to the template. | |
|
| Reference to the graphic consoles attached to the template. | |
|
| Mediated devices configuration. | |
|
| Nic[] | Reference to the network interfaces attached to the template. |
|
| Reference to the user permissions attached to the template. | |
|
| Reference to quota configuration set for this virtual machine. | |
|
| Reference to storage domain the virtual machine belongs to. | |
|
| Tag[] | Reference to the tags attached to the template. |
|
| Reference to the watchdog devices attached to the template. |
7.146. Io struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.147. Ip struct Copy linkLink copied to clipboard!
Represents the IP configuration of a network interface.
| Name | Type | Summary |
|---|---|---|
|
| The text representation of the IP address. | |
|
| The address of the default gateway. | |
|
| The network mask. | |
|
| The version of the IP protocol. |
7.147.1. address Copy linkLink copied to clipboard!
The text representation of the IP address.
For example, an IPv4 address will be represented as follows:
<ip> <address>192.168.0.1</address> ... </ip>
<ip>
<address>192.168.0.1</address>
...
</ip>
An IPv6 address will be represented as follows:
<ip> <address>2620:52:0:20f0:4216:7eff:feaa:1b50</address> ... </ip>
<ip>
<address>2620:52:0:20f0:4216:7eff:feaa:1b50</address>
...
</ip>
7.147.2. netmask Copy linkLink copied to clipboard!
The network mask.
For IPv6 addresses the value is an integer in the range of 0-128, which represents the subnet prefix.
7.147.3. version Copy linkLink copied to clipboard!
The version of the IP protocol.
From version 4.1 of the Manager this attribute will be optional, and when a value is not provided, it will be inferred from the value of the address attribute.
7.148. IpAddressAssignment struct Copy linkLink copied to clipboard!
Represents an IP address assignment for a network device.
For a static boot protocol assignment, subnet mask and IP address (and optinally default gateway) must be provided in the IP configuration.
| Name | Type | Summary |
|---|---|---|
|
| Sets the boot protocol used to assign the IP configuration for a network device. | |
|
| Sets the IP configuration for a network device. |
7.149. IpVersion enum Copy linkLink copied to clipboard!
Defines the values for the IP protocol version.
| Name | Summary |
|---|---|
|
| IPv4. |
|
| IPv6. |
7.150. IscsiBond struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.151. IscsiDetails struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.152. Job struct Copy linkLink copied to clipboard!
Represents a job, which monitors execution of a flow in the system. A job can contain multiple steps in a hierarchic structure. The steps can be processed in parallel, depends on the implementation of the flow.
| Name | Type | Summary |
|---|---|---|
|
| Indicates if the job should be cleared automatically after it was completed by the system. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The end time of the job. | |
|
| Indicates if the job is originated by an external system. | |
|
| A unique identifier. | |
|
| The last update date of the job. | |
|
| A human-readable name in plain text. | |
|
| The start time of the job. | |
|
| The status of the job. |
7.152.1. external Copy linkLink copied to clipboard!
Indicates if the job is originated by an external system. External jobs are managed externally, by the creator of the job.
7.153. JobStatus enum Copy linkLink copied to clipboard!
Represents the status of the job.
| Name | Summary |
|---|---|
|
| The aborted job status. |
|
| The failed job status. |
|
| The finished job status. |
|
| The started job status. |
|
| The unknown job status. |
7.153.1. aborted Copy linkLink copied to clipboard!
The aborted job status. This status is applicable for an external job that was forcibly aborted.
7.153.2. finished Copy linkLink copied to clipboard!
The finished job status. This status describes a completed job execution.
7.153.3. started Copy linkLink copied to clipboard!
The started job status. This status represents a job which is currently being executed.
7.153.4. unknown Copy linkLink copied to clipboard!
The unknown job status. This status represents jobs which their resolution is not known, i.e. jobs that were executed before the system was unexpectedly restarted.
7.154. KatelloErratum struct Copy linkLink copied to clipboard!
Type representing a Katello erratum.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The date when the Katello erratum was issued. | |
|
| A human-readable name in plain text. | |
|
| The list of packages which solve the issue reported by the Katello erratum. | |
|
| The severity of the Katello erratum. | |
|
| The solution for the issue described by the Katello erratum. | |
|
| The summary of the Katello erratum. | |
|
| The title of the Katello erratum. | |
|
| The type of the Katello erratum. |
7.154.1. severity Copy linkLink copied to clipboard!
The severity of the Katello erratum.
The supported severities are moderate, important or critical.
7.154.2. type Copy linkLink copied to clipboard!
The type of the Katello erratum.
The supported types are bugfix, enhancement or security.
7.155. KdumpStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.156. Kernel struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.157. Ksm struct Copy linkLink copied to clipboard!
7.158. LinkLayerDiscoveryProtocolElement struct Copy linkLink copied to clipboard!
Represents an information element received by Link Layer Discovery Protocol (LLDP). IEEE 802.1AB defines type, length, value (TLV) as a "short, variable length encoding of an information element". This type represents such an information element.
The attribute name is a human-readable string used to describe what the value is about, and may not be unique. The name is redundant, because it could be created from type and the optional oui and subtype. The purpose of name is to simplify the reading of the information element. The name of a property is exactly the same string which is used in IEEE 802.1AB chapter 8.
Organizationally-specific information elements have the type of 127 and the attributes oui and subtype.
For example, the XML representation of an information element may look like this:
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The organizationally-unique identifier (OUI) encoded as an integer. | |
|
| Represents structured data transported by the information element as a list of name/value pairs. | |
|
| The organizationally-defined subtype encoded as an integer. | |
|
| The type of the LinkLayerDiscoveryProtocolElement encoded as an integer. |
7.158.1. oui Copy linkLink copied to clipboard!
The organizationally-unique identifier (OUI) encoded as an integer. Only available if type is 127.
7.158.2. subtype Copy linkLink copied to clipboard!
The organizationally-defined subtype encoded as an integer. Only available if type is 127.
7.159. LogMaxMemoryUsedThresholdType enum Copy linkLink copied to clipboard!
Describes all maximum memory threshold types supported by the system.
| Name | Summary |
|---|---|
|
| Absolute value threshold type. |
|
| Percentage threshold type. |
7.159.1. absolute_value_in_mb Copy linkLink copied to clipboard!
Absolute value threshold type.
When an absolute value is specified, an audit log event is logged if the free memory in MB falls below the value specified in LogMaxMemoryUsedThreshold.
7.159.2. percentage Copy linkLink copied to clipboard!
Percentage threshold type.
When a percentage is specified, an audit log event is logged if the memory used is above the value specified in LogMaxMemoryUsedThreshold.
7.160. LogSeverity enum Copy linkLink copied to clipboard!
Enum representing a severity of an event.
| Name | Summary |
|---|---|
|
| Alert severity. |
|
| Error severity. |
|
| Normal severity. |
|
| Warning severity. |
7.160.1. alert Copy linkLink copied to clipboard!
Alert severity. Used to specify a condition that requires an immediate attention.
7.160.2. error Copy linkLink copied to clipboard!
Error severity. Used to specify that there is an error that needs to be examined.
7.160.3. normal Copy linkLink copied to clipboard!
Normal severity. Used for information events.
7.160.4. warning Copy linkLink copied to clipboard!
Warning severity. Used to warn something might be wrong.
7.161. LogicalUnit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| The maximum number of bytes that can be discarded by the logical unit’s underlying storage in a single operation. | |
|
| True, if previously discarded blocks in the logical unit’s underlying storage are read back as zeros. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.161.1. discard_max_size Copy linkLink copied to clipboard!
The maximum number of bytes that can be discarded by the logical unit’s underlying storage in a single operation. A value of 0 means that the device does not support discard functionality.
This is the software limit, and not the hardware limit, as noted in the queue-sysfs documentation for discard_max_bytes.
7.161.2. discard_zeroes_data Copy linkLink copied to clipboard!
True, if previously discarded blocks in the logical unit’s underlying storage are read back as zeros. For more information please see the queue-sysfs documentation for discard_zeroes_data.
Since version 4.2.1 of the system, the support for this attribute has been removed as the sysfs file, discard_zeroes_data, was deprecated in the kernel. It is preserved for backwards compatibility, but the value will always be false.
7.162. LunStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.163. MDevType struct Copy linkLink copied to clipboard!
Mediated device is a software device that allows to divide physical device’s resources.
See Libvirt-MDEV for further details.
7.164. Mac struct Copy linkLink copied to clipboard!
Represents a MAC address of a virtual network interface.
| Name | Type | Summary |
|---|---|---|
|
| MAC address. |
7.165. MacPool struct Copy linkLink copied to clipboard!
Represents a MAC address pool.
Example of an XML representation of a MAC address pool:
| Name | Type | Summary |
|---|---|---|
|
| Defines whether duplicate MAC addresses are permitted in the pool. | |
|
| Free text containing comments about this object. | |
|
| Defines whether this is the default pool. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines the range of MAC addresses for the pool. |
7.165.1. allow_duplicates Copy linkLink copied to clipboard!
Defines whether duplicate MAC addresses are permitted in the pool. If not specified, defaults to false.
7.165.2. default_pool Copy linkLink copied to clipboard!
Defines whether this is the default pool. If not specified, defaults to false.
7.165.3. ranges Copy linkLink copied to clipboard!
Defines the range of MAC addresses for the pool. Multiple ranges can be defined.
| Name | Type | Summary |
|---|---|---|
|
| Returns a reference to the permissions that are associated with the MacPool. |
7.166. MemoryOverCommit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.167. MemoryPolicy struct Copy linkLink copied to clipboard!
Logical grouping of memory-related properties of virtual machine-like entities.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| The amount of memory, in bytes, that is guaranteed to not be drained by the balloon mechanism. | |
|
| Maximum virtual machine memory, in bytes. | |
|
| ||
|
|
7.167.1. guaranteed Copy linkLink copied to clipboard!
The amount of memory, in bytes, that is guaranteed to not be drained by the balloon mechanism.
The Red Hat Virtualization Manager internally rounds this value down to whole MiB (1MiB = 220 bytes).
7.167.2. max Copy linkLink copied to clipboard!
Maximum virtual machine memory, in bytes.
The user provides the value in bytes, and the Red Hat Virtualization Manager rounds the value down to the nearest lower MiB value.
For example, if the user enters a value of 1073741825 (1 GiB + 1 byte), then the Red Hat Virtualization Manager will truncate that value to the nearest lower MiB boundary: in this case 1073741824 (1 GiB).
7.168. MessageBrokerType enum Copy linkLink copied to clipboard!
Deprecated Message Broker type.
Ignored, because the deployment of OpenStack Neutron agent is dropped since Red Hat Virtualization 4.4.0.
| Name | Summary |
|---|---|
|
| |
|
|
7.169. Method struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.170. MigrateOnError enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.171. MigrationBandwidth struct Copy linkLink copied to clipboard!
Defines the bandwidth used by migration.
| Name | Type | Summary |
|---|---|---|
|
| The method used to assign the bandwidth. | |
|
| Custom bandwidth in Mbps. |
7.171.1. custom_value Copy linkLink copied to clipboard!
Custom bandwidth in Mbps. Will be applied only if the assignmentMethod attribute is custom.
7.172. MigrationBandwidthAssignmentMethod enum Copy linkLink copied to clipboard!
Defines how the migration bandwidth is assigned.
| Name | Summary |
|---|---|
|
| Takes the bandwidth from the Quality of Service if the Quality of Service is defined. |
|
| Custom defined bandwidth in Mbit/s. |
|
| Takes the value as configured on the hypervisor. |
7.172.1. auto Copy linkLink copied to clipboard!
Takes the bandwidth from the Quality of Service if the Quality of Service is defined. If the Quality of Service is not defined the bandwidth is taken from the detected link speed being used. If nothing is detected, bandwidth falls back to the hypervisor_default value.
7.173. MigrationOptions struct Copy linkLink copied to clipboard!
The type for migration options.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| The bandwidth that is allowed to be used by the migration. | |
|
| ||
|
| Specifies how many parallel migration connections to use. | |
|
| Specifies whether the migration should be encrypted or not. | |
|
| Specifies whether and how to use parallel migration connections. |
7.173.1. custom_parallel_migrations Copy linkLink copied to clipboard!
Specifies how many parallel migration connections to use. May be specified only when ParallelMigrationsPolicy is CUSTOM. The valid range of values is 2-255. The recommended range of values is 2-16.
| Name | Type | Summary |
|---|---|---|
|
|
A reference to the migration policy, as defined using |
7.174. MigrationPolicy struct Copy linkLink copied to clipboard!
A policy describing how the migration is treated, such as convergence or how many parallel migrations are allowed.
7.175. Network struct Copy linkLink copied to clipboard!
The type for a logical network.
An example of the JSON representation of a logical network:
An example of the XML representation of the same logical network:
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| Deprecated, 'usages' should be used to define network as a display network. | |
|
| The DNS resolver configuration will be reported when retrieving the network using GET. | |
|
| A unique identifier. | |
|
| Deprecated, not in use. | |
|
| Specifies the maximum transmission unit for the network. | |
|
| A human-readable name in plain text. | |
|
| Defines whether communication between VMs running on the same host is blocked on this network. | |
|
| Specifies whether upon creation of the network a virtual network interface profile should automatically be created. | |
|
| Defines whether the network is mandatory for all the hosts in the cluster. | |
|
| The status of the network. | |
|
| Specifies whether the spanning tree protocol is enabled for the network. | |
|
| Defines a set of usage elements for the network. | |
|
| The name of the network used on the host. | |
|
| A VLAN tag. |
7.175.1. dns_resolver_configuration Copy linkLink copied to clipboard!
The DNS resolver configuration will be reported when retrieving the network using GET. It is optional both when creating a new network or updating existing one.
7.175.2. port_isolation Copy linkLink copied to clipboard!
Defines whether communication between VMs running on the same host is blocked on this network. Applies only to VM networks. It is on the network administrator to ensure that the communication between multiple hosts is blocked. This attribute can be set only on network creation and cannot be edited. When the value is not set, communication between VMs running on the same host is allowed.
7.175.3. required Copy linkLink copied to clipboard!
Defines whether the network is mandatory for all the hosts in the cluster. In case a 'required' operational network is omitted from a host, the host will be marked as non_operational,
7.175.4. status Copy linkLink copied to clipboard!
The status of the network. non_operational if the network defined as 'required' and omitted from any active cluster host. operational otherwise.
7.175.5. usages Copy linkLink copied to clipboard!
Defines a set of usage elements for the network.
For example, users can specify that the network is to be used for virtual machine traffic and also for display traffic with the vm and display values.
7.175.6. vdsm_name Copy linkLink copied to clipboard!
The name of the network used on the host. This alternative name is automatically generated by VDSM when the network name is found unsuitable to serve as a bridge name on the host. Unsuitable names contain spaces, special characters or are longer than 15 characters and are replaced with a UUID on the host. This parameter is read-only. Setting it will have no effect.
| Name | Type | Summary |
|---|---|---|
|
| A reference to the cluster this network is attached to. | |
|
| A reference to the data center that the network is a member of. | |
|
| An optional reference to the OpenStack network provider on which the network is created. | |
|
| An optional reference to a network that should be used for physical network access. | |
|
| A reference to the labels assigned to the network. | |
|
| A reference to the permissions of the network. | |
|
| Reference to quality of service. | |
|
| A reference to the profiles of the network. |
7.175.7. cluster Copy linkLink copied to clipboard!
A reference to the cluster this network is attached to. Will be filled only if the network is accessed from the cluster level.
7.175.8. external_provider Copy linkLink copied to clipboard!
An optional reference to the OpenStack network provider on which the network is created.
If it is specified when a network is created, a matching OpenStack network will be also created.
7.175.9. external_provider_physical_network Copy linkLink copied to clipboard!
An optional reference to a network that should be used for physical network access. Valid only if external_provider is specified.
7.176. NetworkAttachment struct Copy linkLink copied to clipboard!
Describes how a host connects to a network.
An XML representation of a network attachment on a host:
The network element, with either a name or an id, is required in order to attach a network to a network interface card (NIC).
For example, to attach a network to a host network interface card, send a request like this:
POST /ovirt-engine/api/hosts/123/nics/456/networkattachments
POST /ovirt-engine/api/hosts/123/nics/456/networkattachments
With a request body like this:
<networkattachment> <network id="234"/> </networkattachment>
<networkattachment>
<network id="234"/>
</networkattachment>
To attach a network to a host, send a request like this:
POST /ovirt-engine/api/hosts/123/networkattachments
POST /ovirt-engine/api/hosts/123/networkattachments
With a request body like this:
<network_attachment> <network id="234"/> <host_nic id="456"/> </network_attachment>
<network_attachment>
<network id="234"/>
<host_nic id="456"/>
</network_attachment>
The ip_address_assignments and properties elements are updatable post-creation.
For example, to update a network attachment, send a request like this:
PUT /ovirt-engine/api/hosts/123/nics/456/networkattachments/789
PUT /ovirt-engine/api/hosts/123/nics/456/networkattachments/789
With a request body like this:
To detach a network from the network interface card send a request like this:
DELETE /ovirt-engine/api/hosts/123/nics/456/networkattachments/789
DELETE /ovirt-engine/api/hosts/123/nics/456/networkattachments/789
Changes to network attachment configuration must be explicitly committed.
An XML representation of a network attachment’s properties sub-collection:
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| DNS resolver configuration will be reported when retrieving the network attachment using GET. | |
|
| A unique identifier. | |
|
| ||
|
| The IP configuration of the network. | |
|
| A human-readable name in plain text. | |
|
| Defines custom properties for the network configuration. | |
|
| A read-only list of configuration properties. |
7.176.1. dns_resolver_configuration Copy linkLink copied to clipboard!
DNS resolver configuration will be reported when retrieving the network attachment using GET. It is optional when creating a new network attachment or updating an existing one.
7.176.2. properties Copy linkLink copied to clipboard!
Defines custom properties for the network configuration.
Bridge options have the set name of bridge_opts. Separate multiple entries with a whitespace character. The following keys are valid for bridge_opts:
| Name | Default value |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7.177. NetworkConfiguration struct Copy linkLink copied to clipboard!
7.178. NetworkFilter struct Copy linkLink copied to clipboard!
Network filters filter packets sent to and from the virtual machine’s NIC according to defined rules.
There are several types of network filters supported based on libvirt. For more details about the different network filters see here.
The default Network Filter is based on network type and configuration. VM network’s default filter is vdsm-no-mac-spoof if EnableMACAntiSpoofingFilterRules is True, otherwise the filter is not configured, for OVN networks the filter is not configured.
In addition to libvirt’s network filters, there are two additional network filters: The first is called vdsm-no-mac-spoofing and is composed of no-mac-spoofing and no-arp-mac-spoofing. The second is called ovirt-no-filter and is used when no network filter is to be defined for the virtual machine’s NIC. The ovirt-no-filter network filter is only used for internal implementation, and does not exist on the NICs.
This is a example of the XML representation:
If any part of the version is not present, it is represented by -1.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The minimum supported version of a specific NetworkFilter. |
7.178.1. version Copy linkLink copied to clipboard!
The minimum supported version of a specific NetworkFilter. This is the version that the NetworkFilter was first introduced in.
7.179. NetworkFilterParameter struct Copy linkLink copied to clipboard!
Parameter for the network filter.
See Libvirt-Filters for further details. This is a example of the XML representation:
<network_filter_parameter id="123"> <name>IP</name> <value>10.0.1.2</value> </network_filter_parameter>
<network_filter_parameter id="123">
<name>IP</name>
<value>10.0.1.2</value>
</network_filter_parameter>
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Represents the value of the parameter. |
| Name | Type | Summary |
|---|---|---|
|
| The virtual machine NIC the parameter is assiciated to. |
7.180. NetworkLabel struct Copy linkLink copied to clipboard!
Represents a label which can be added to a host network interface and to a network. The label binds the network to the host network interface by the label id.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
7.181. NetworkPluginType enum Copy linkLink copied to clipboard!
Network plug-in type.
Specifies the provider driver implementation on the host.
Since version 4.2 of the Red Hat Virtualization Manager, this type has been deprecated in favour of the external_plugin_type attribute of the OpenStackNetworkProvider type.
| Name | Summary |
|---|---|
|
| Open vSwitch. |
7.181.1. open_vswitch Copy linkLink copied to clipboard!
Open vSwitch.
Specifies that Open vSwitch based driver implementation should be used for this provider.
Since version 4.2 of the Red Hat Virtualization Manager, this value has been deprecated. Use the string open_vswitch in the OpenStackNetworkProvider.external_plugin_type attribute instead.
7.182. NetworkStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.183. NetworkUsage enum Copy linkLink copied to clipboard!
This type indicates the purpose that the network is used for in the cluster.
| Name | Summary |
|---|---|
|
| The default gateway and the DNS resolver configuration of the host will be taken from this network. |
|
| The network will be used for SPICE and VNC traffic. |
|
| The network will be used for Gluster (bricks) data traffic. |
|
| The network will be used for communication between the Red Hat Virtualization Manager and the nodes. |
|
| The network will be used for virtual machine migration. |
|
|
7.183.1. default_route Copy linkLink copied to clipboard!
The default gateway and the DNS resolver configuration of the host will be taken from this network.
If this network is attached to the host, then the DNS resolver configuration will be taken from the dns_resolver_configuration attribute of the network attachment. If there is no dns_resolver_configuration attribute in this network attachment, then they will be taken from the dns_resolver_configuration of the network itself. If dns_resolver_configuration attribute isn’t present even there, DNS resolver configuration won’t be set.
If you set this flag on a network, then the the default gateway for the host will be taken from the gateway attribute of the ip_address_assignment of the network attachment.
7.183.2. management Copy linkLink copied to clipboard!
The network will be used for communication between the Red Hat Virtualization Manager and the nodes. This is the network where the ovirtmgmt bridge will be created.
7.184. NfsProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.185. NfsVersion enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| NFS 4. |
|
| |
|
| NFS 4. |
7.185.1. v4_0 Copy linkLink copied to clipboard!
NFS 4.0.
7.185.2. v4_2 Copy linkLink copied to clipboard!
NFS 4.2.
7.186. Nic struct Copy linkLink copied to clipboard!
Represents a virtual machine NIC.
For example, the XML representation of a NIC will look like this:
| Name | Type | Summary |
|---|---|---|
|
| Defines how an IP address is assigned to the NIC. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The type of driver used for the NIC. | |
|
| Defines if the NIC is linked to the virtual machine. | |
|
| The MAC address of the interface. | |
|
| A human-readable name in plain text. | |
|
| Defines if the network interface should be activated upon operation system startup. | |
|
| Defines if the NIC is plugged in to the virtual machine. | |
|
| Defines if the NIC configuration on the virtual machine is synced with the configuration represented by engine. |
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| A reference to the network that the interface should be connected to. | |
|
| A link to a collection of network attachments that are associated with the host NIC. | |
|
| A link to the network filter parameters. | |
|
| A link to a collection of network labels that are associated with the host NIC. | |
|
| A link to a collection of reported devices that are associated with the virtual network interface. | |
|
| A link to the statistics for the NIC. | |
|
| Optionally references to a template the device is used by. | |
|
| A link to a collection of network labels that are allowed to be attached to the virtual functions of an SR-IOV NIC. | |
|
| A link to a collection of networks that are allowed to be attached to the virtual functions of an SR-IOV NIC. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
|
| A link to an associated virtual network interface profile. |
7.186.1. network Copy linkLink copied to clipboard!
A reference to the network that the interface should be connected to. A blank network ID is allowed.
Usage of this element for creating or updating a NIC is deprecated; use vnic_profile instead. It is preserved because it is still in use by the initialization element, as a holder for IP addresses and other network details.
7.186.2. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.187. NicConfiguration struct Copy linkLink copied to clipboard!
The type describes the configuration of a virtual network interface.
| Name | Type | Summary |
|---|---|---|
|
| IPv4 boot protocol. | |
|
| IPv4 address details. | |
|
| IPv6 address details. | |
|
| IPv6 boot protocol. | |
|
| Network interface name. | |
|
| Specifies whether the network interface should be activated on the virtual machine guest operating system boot. |
7.188. NicInterface enum Copy linkLink copied to clipboard!
Defines the options for an emulated virtual network interface device model.
| Name | Summary |
|---|---|
|
| e1000. |
|
| e1000e. |
|
| PCI Passthrough. |
|
| rtl8139. |
|
| Dual mode rtl8139, VirtIO. |
|
| sPAPR VLAN. |
|
| VirtIO. |
7.189. NicStatus enum Copy linkLink copied to clipboard!
Network interface card status.
| Name | Summary |
|---|---|
|
| The NIC is down and cannot be accessed. |
|
| The NIC is up and can be accessed. |
7.190. NotifiableEvent enum Copy linkLink copied to clipboard!
Type representing a subset of events in the Red Hat Virtualization server: those which a user may subscribe to receive a notification about.
| Name | Summary |
|---|---|
|
| HA Reservation check has failed |
|
| HA Reservation check has passed |
|
| ETL Service Error |
|
| ETL Service Stopped |
|
| Engine backup completed successfully |
|
| Engine backup failed |
|
| Engine backup started |
|
| Engine CA’s certification has expired |
|
| Engine CA’s certification is about to expire |
|
| Engine’s certification has expired |
|
| Engine’s certification is about to expire |
|
| Engine has stopped |
|
| Faulty multipath paths on host |
|
| Detected change in status of brick |
|
| Failed to add Gluster Hook on conflicting servers |
|
| Added Gluster Hook |
|
| Detected conflict in Gluster Hook |
|
| Detected removal of Gluster Hook |
|
| Detected new Gluster Hook |
|
| Gluster Hook Disabled |
|
| Failed to Disable Gluster Hook |
|
| Gluster Hook Enabled |
|
| Failed to Enable Gluster Hook |
|
| Failed to remove Gluster Hook from cluster |
|
| Removed Gluster Hook |
|
| Failed to Add Gluster Server |
|
| Gluster Server Removed |
|
| Failed to Remove Gluster Server |
|
| Failed to re-start Gluster Service |
|
| Gluster Service re-started |
|
| Failed to start Gluster service |
|
| Gluster Service started |
|
| Failed to stop Gluster service |
|
| Gluster Service stopped |
|
| Gluster Volume brick(s) added |
|
| Failed to add brick(s) on Gluster Volume |
|
| Failed to delete snapshots on the volume |
|
| All the snapshots deleted on the volume |
|
| Gluster Volume Brick Replaced |
|
| Low space for volume confirmed |
|
| Gluster Volume Created |
|
| Gluster Volume could not be created |
|
| Gluster Volume deleted |
|
| Gluster Volume could not be deleted |
|
| Gluster Volume migration of data for remove brick finished |
|
| Gluster Volume Option added |
|
| Gluster Volume Option modified |
|
| Gluster Volume Option could not be set |
|
| Gluster Volume Options reset |
|
| All the Gluster Volume Options reset |
|
| Gluster Volume Options could not be reset |
|
| Gluster Volume Profile started |
|
| Failed to start Gluster Volume Profile |
|
| Gluster Volume Profile stopped |
|
| Failed to stop Gluster Volume Profile |
|
| Gluster Volume rebalance finished |
|
| Could not find information for rebalance on volume from CLI. |
|
| Gluster Volume Rebalance started |
|
| Detected start of rebalance on gluster volume from CLI |
|
| Gluster Volume Rebalance could not be started |
|
| Gluster Volume Rebalance stopped |
|
| Gluster Volume Rebalance could not be stopped |
|
| Gluster Volume Bricks Removed |
|
| Gluster Volume Bricks could not be removed |
|
| Stopped removing bricks from Gluster Volume |
|
| Failed to stop remove bricks from Gluster Volume |
|
| Gluster Volume Replace Brick Failed |
|
| Gluster Volume Replace Brick Started |
|
| Gluster Volume Replace Brick could not be started |
|
| Failed to activate snapshot on the volume |
|
| Snapshot activated on the volume |
|
| Could not create snapshot for volume ${glusterVolumeName} on cluster ${clusterName}. |
|
| Snapshot ${snapname} created for volume ${glusterVolumeName} on cluster ${clusterName}. |
|
| Failed to de-activate snapshot on the volume |
|
| Snapshot de-activated on the volume |
|
| Failed to delete snapshot on volume |
|
| Snapshot deleted on volume |
|
| Failed to restore snapshot on the volume |
|
| Snapshot restore on the volume |
|
| Gluster volume started |
|
| Gluster Volume could not be started |
|
| Gluster volume stopped |
|
| Gluster Volume could not be stopped |
|
| Highly-Available VM failed |
|
| Highly-Available VM restart failed |
|
| Failed to activate Host |
|
| Host was activated, but the Hosted Engine HA service may still be in maintenance mode |
|
| Failed to approve Host |
|
| Host’s slave of bond changed state to down |
|
| Host’s certificate contains invalid subject alternative name (SAN) |
|
| Host’s certification has expired |
|
| Host’s certification is about to expire |
|
| Host is non responsive |
|
| Host cpu usage exceeded defined threshold |
|
| Host memory usage exceeded defined threshold |
|
| Host swap memory usage exceeded defined threshold |
|
| Failed to restart VM on a different host |
|
| Host installation failed |
|
| Host network interface usage exceeded defined threshold |
|
| Host’s interface changed state to down |
|
| Host free memory is under defined threshold |
|
| Host free swap memory is under defined threshold |
|
| Host failed to recover |
|
| Host state was set to non-operational |
|
| Host state was set to non-operational due to inaccessible Storage Domain |
|
| Host state was set to non-operational due to a missing Interface |
|
| Slow storage response time |
|
| Host has time-drift |
|
| Host state was set to non-operational. |
|
| Host has available updates |
|
| Host has available packages to update |
|
| Template imported from trusted cluster into non-trusted cluster |
|
| Template imported from non-trusted cluster into trusted cluster |
|
| Import VM from trusted cluster into non-trusted cluster |
|
| Import VM from non-trusted cluster into trusted cluster |
|
| Confirmed low disk space |
|
| Low disk space |
|
| Critically low disk space |
|
| Failed to access Storage |
|
| VM with external MAC address |
|
| Multipath devices without valid paths on host |
|
| Display network was updated on cluster with an active VM |
|
| Display network was updated on host with an active VM |
|
| No faulty multipath paths on host |
|
| Storage Domain’s number of LVs exceeded threshold |
|
| Could not find information for remove brick on volume from CLI. |
|
| Started removing bricks from Volume |
|
| Detected start of brick removal for bricks on volume from CLI |
|
| Could not remove volume bricks |
|
| Failed electing an SPM for the Data-Center |
|
| Storage Domain state was set to inactive |
|
| A non-trusted VM was created from trusted Template |
|
| A trusted VM was created from non-trusted Template |
|
| A non-trusted Template was created from trusted VM |
|
| A trusted Template was created from non-trusted VM |
|
| Host was switched to Maintenance Mode |
|
| Host was switched to Maintenance Mode, but Hosted Engine HA maintenance mode could not be enabled |
|
| Failed to switch Host to Maintenance mode |
|
| VM moved from trusted cluster to non-trusted cluster |
|
| VM moved from non-trusted cluster to trusted cluster |
|
| Template moved from trusted cluster to non-trusted cluster |
|
| Template moved from a non-trusted cluster to a trusted cluster |
|
| VM console connected |
|
| VM console disconnected |
|
| VM is down with error |
|
| VM cannot be found on Host |
|
| Migration failed |
|
| Starting migration of VM |
|
| Migration of VM to a destination host failed |
|
| VM is not responding |
|
| VM has been paused |
|
| VM has been paused due to a storage I/O error |
|
| VM has been paused due to lack of storage space |
|
| VM has been paused due to storage read/write permissions problem |
|
| VM has been paused due to unknown storage error |
|
| VM has recovered from paused back to up |
|
| VM console session initiated |
|
| VM status restored |
7.190.1. gluster_volume_rebalance_not_found_from_cli Copy linkLink copied to clipboard!
Could not find information for rebalance on volume from CLI. Marking it as unknown.
7.190.2. host_untrusted Copy linkLink copied to clipboard!
Host state was set to non-operational. Host is untrusted by the attestation service
7.190.3. remove_gluster_volume_bricks_not_found_from_cli Copy linkLink copied to clipboard!
Could not find information for remove brick on volume from CLI. Marking it as unknown.
7.191. NotificationMethod enum Copy linkLink copied to clipboard!
Type representing the notification method for an event subscription. Currently only SMTP is supported by the API In the future support for SNMP notifications may be added.
| Name | Summary |
|---|---|
|
| Notification by e-mail. |
|
| Notification by SNMP. |
7.191.1. smtp Copy linkLink copied to clipboard!
Notification by e-mail.
Event-subscriptions with SMTP notification method will contain an email address in the address field.
7.191.2. snmp Copy linkLink copied to clipboard!
Notification by SNMP.
Event-subscriptions with SNMP notification method will contain an SNMP address in the address field.
7.192. NumaNode struct Copy linkLink copied to clipboard!
Represents a physical NUMA node.
Example XML representation:
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| Memory of the NUMA node in MB. | |
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Each host NUMA node resource exposes a statistics sub-collection for host NUMA node specific statistics. |
7.192.1. statistics Copy linkLink copied to clipboard!
Each host NUMA node resource exposes a statistics sub-collection for host NUMA node specific statistics.
An example of an XML representation:
This statistics sub-collection is read-only.
The following list shows the statistic types for a host NUMA node:
| Name | Description |
|---|---|
|
| Total memory in bytes on the NUMA node. |
|
| Memory in bytes used on the NUMA node. |
|
| Memory in bytes free on the NUMA node. |
|
| Percentage of CPU usage for user slice. |
|
| Percentage of CPU usage for system. |
|
| Percentage of idle CPU usage. |
7.193. NumaNodePin struct Copy linkLink copied to clipboard!
Represents the pinning of a virtual NUMA node to a physical NUMA node.
| Name | Type | Summary |
|---|---|---|
|
| Deprecated. | |
|
| The index of a physical NUMA node to which the virtual NUMA node is pinned. | |
|
| Deprecated. |
7.193.1. host_numa_node Copy linkLink copied to clipboard!
Deprecated. Has no function.
7.193.2. pinned Copy linkLink copied to clipboard!
Deprecated. Should always be true.
7.194. NumaTuneMode enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.195. OpenStackImage struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
|
7.196. OpenStackImageProvider struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Defines the external provider authentication URL address. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines password for the user during the authentication process. | |
|
| Array of provider name/value properties. | |
|
| Defines whether provider authentication is required or not. | |
|
| Defines the tenant name for OpenStack Identity API v2. | |
|
| Defines URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
7.196.1. requires_authentication Copy linkLink copied to clipboard!
Defines whether provider authentication is required or not.
If authentication is required, both username and password attributes will be used during authentication.
7.196.2. tenant_name Copy linkLink copied to clipboard!
Defines the tenant name for OpenStack Identity API v2.0.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.197. OpenStackNetwork struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
|
7.198. OpenStackNetworkProvider struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Deprecated Agent configuration settings. | |
|
| Defines the external provider authentication URL address. | |
|
| Indicates if the networks of this provider are automatically synchronized. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| Network plug-in type. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines password for the user during the authentication process. | |
|
| Network plug-in type. | |
|
| Defines the project’s domain name for OpenStack Identity API v3. | |
|
| Defines the project name for OpenStack Identity API v3. | |
|
| Array of provider name/value properties. | |
|
| Indicates whether the provider is read-only. | |
|
| Defines whether provider authentication is required or not. | |
|
| Defines the tenant name for OpenStack Identity API v2. | |
|
| The type of provider. | |
|
| Indicates whether the provider is unmanaged by Red Hat Virtualization. | |
|
| Defines URL address of the external provider. | |
|
|
Defines the domain name of the | |
|
| Defines user name to be used during authentication process. |
7.198.1. agent_configuration Copy linkLink copied to clipboard!
Deprecated Agent configuration settings.
Ignored, because the deployment of OpenStack Neutron agent is dropped since Red Hat Virtualization 4.4.0.
7.198.2. auto_sync Copy linkLink copied to clipboard!
Indicates if the networks of this provider are automatically synchronized.
If true, the networks of this provider are automatically and cyclically synchronized to Red Hat Virtualization in the background. This means that all new networks of this provider are imported, and all discarded networks are removed from all clusters that have this external provider as the default provider. If the name of a network is changed on the provider, the change is synchronized to the network entity in Red Hat Virtualization. Furthermore, if a new cluster that has the provider as the default provider is added, already imported networks are attached to this new cluster during synchronization.
The automatically initiated import triggers the following steps:
- The networks of the external provider will be imported to every data center in the data centers of the clusters that have that external provider as the default provider.
- A vNIC profile will be created for each involved data center and network.
- The networks will be assigned to each cluster that has that external provider as the default provider.
All users are allowed to use the new vNIC Profile.
The default is false for backwards compatibility.
7.198.3. external_plugin_type Copy linkLink copied to clipboard!
Network plug-in type.
This attribute allows you to choose the correct provider driver on the host when an external NIC is added or modified. If automated installation of the driver is supported (only available for some predefined implementations, for example ovirt-provider-ovn), this attribute will also allow the system to decide which driver implementation to install on newly added hosts.
7.198.4. plugin_type Copy linkLink copied to clipboard!
Network plug-in type.
Since version 4.2 of the Red Hat Virtualization Manager, this attribute has been deprecated in favour of external_plugin_type. This attribute is only valid for providers of type open_vswitch, and will only be returned when the value of the external_plugin_type attribute value is equal to open_vswitch.
If both plugin_type and external_plugin_type are specified during an update, the value of plugin_type will be ignored.
For external providers this value will not be shown and will be ignored during update requests.
7.198.5. read_only Copy linkLink copied to clipboard!
Indicates whether the provider is read-only.
A read-only provider does not allow adding, modifying, or deleting of networks or subnets. Port-related operations are allowed, as they are required for the provisioning of virtual NICs.
7.198.6. requires_authentication Copy linkLink copied to clipboard!
Defines whether provider authentication is required or not.
If authentication is required, both username and password attributes will be used during authentication.
7.198.7. tenant_name Copy linkLink copied to clipboard!
Defines the tenant name for OpenStack Identity API v2.0.
7.198.8. unmanaged Copy linkLink copied to clipboard!
Indicates whether the provider is unmanaged by Red Hat Virtualization.
If true, authentication and subnet control are entirely left to the external provider and are unmanaged by Red Hat Virtualization.
The default is false for backwards compatibility.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the certificates list. | |
|
| Reference to the OpenStack networks list. | |
|
| Reference to the OpenStack networks subnets list. |
7.199. OpenStackNetworkProviderType enum Copy linkLink copied to clipboard!
The OpenStack network provider can either be implemented by OpenStack Neutron, in which case the Neutron agent is automatically installed on the hosts, or it can be an external provider implementing the OpenStack API, in which case the virtual interface driver is a custom solution installed manually.
| Name | Summary |
|---|---|
|
| Indicates that the provider is an external one, implementing the OpenStack Neutron API. |
|
| Indicates that the provider is OpenStack Neutron. |
7.199.1. external Copy linkLink copied to clipboard!
Indicates that the provider is an external one, implementing the OpenStack Neutron API. The virtual interface driver in this case is implemented by the external provider.
7.199.2. neutron Copy linkLink copied to clipboard!
Indicates that the provider is OpenStack Neutron. The standard OpenStack Neutron agent is used as the virtual interface driver.
7.200. OpenStackProvider struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Defines the external provider authentication URL address. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines password for the user during the authentication process. | |
|
| Array of provider name/value properties. | |
|
| Defines whether provider authentication is required or not. | |
|
| Defines the tenant name for OpenStack Identity API v2. | |
|
| Defines URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
7.200.1. requires_authentication Copy linkLink copied to clipboard!
Defines whether provider authentication is required or not.
If authentication is required, both username and password attributes will be used during authentication.
7.200.2. tenant_name Copy linkLink copied to clipboard!
Defines the tenant name for OpenStack Identity API v2.0.
7.201. OpenStackSubnet struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Defines network CIDR. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| Defines a list of DNS servers. | |
|
| Defines IP gateway. | |
|
| A unique identifier. | |
|
| Defines IP version. | |
|
| A human-readable name in plain text. |
7.201.1. ip_version Copy linkLink copied to clipboard!
Defines IP version.
Values can be v4' for IPv4 or `v6 for IPv6.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the service managing the OpenStack network. |
7.202. OpenStackVolumeProvider struct Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Type | Summary |
|---|---|---|
|
| Defines the external provider authentication URL address. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Defines password for the user during the authentication process. | |
|
| Array of provider name/value properties. | |
|
| Defines whether provider authentication is required or not. | |
|
| Defines the tenant name for OpenStack Identity API v2. | |
|
| Defines URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
7.202.1. requires_authentication Copy linkLink copied to clipboard!
Defines whether provider authentication is required or not.
If authentication is required, both username and password attributes will be used during authentication.
7.202.2. tenant_name Copy linkLink copied to clipboard!
Defines the tenant name for OpenStack Identity API v2.0.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
|
7.203. OpenStackVolumeType struct Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.204. OpenstackVolumeAuthenticationKey struct Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.205. OpenstackVolumeAuthenticationKeyUsageType enum Copy linkLink copied to clipboard!
Openstack Volume (Cinder) integration has been replaced by Managed Block Storage.
| Name | Summary |
|---|---|
|
|
7.206. OperatingSystem struct Copy linkLink copied to clipboard!
Information describing the operating system. This is used for both virtual machines and hosts.
| Name | Type | Summary |
|---|---|---|
|
| Configuration of the boot sequence. | |
|
| Custom kernel parameters for starting the virtual machine if Linux operating system is used. | |
|
| A custom part of the host kernel command line. | |
|
| Path to custom initial ramdisk on ISO storage domain if Linux operating system is used. | |
|
| Path to custom kernel on ISO storage domain if Linux operating system is used. | |
|
| The host kernel command line as reported by a running host. | |
|
| Operating system name in human readable form. | |
|
|
7.206.1. boot Copy linkLink copied to clipboard!
Configuration of the boot sequence.
Not used for hosts.
7.206.2. cmdline Copy linkLink copied to clipboard!
Custom kernel parameters for starting the virtual machine if Linux operating system is used.
Not used for hosts.
7.206.3. custom_kernel_cmdline Copy linkLink copied to clipboard!
A custom part of the host kernel command line. This will be merged with the existing kernel command line.
You must reinstall and then reboot the host to apply the changes implemented by this attribute.
During each host deploy procedure, kernel parameters that were added in the previous host deploy procedure are removed using grubby --update-kernel DEFAULT --remove-args <previous_custom_params>, and the current kernel command line customization is applied using grubby --update-kernel DEFAULT --args <custom_params>. The Manager internally keeps track of the last-applied kernel parameters customization.
This attribute is currently only used for hosts.
7.206.4. initrd Copy linkLink copied to clipboard!
Path to custom initial ramdisk on ISO storage domain if Linux operating system is used.
For example iso://initramfs-3.10.0-514.6.1.el7.x86_64.img.
Not used for hosts.
7.206.5. kernel Copy linkLink copied to clipboard!
Path to custom kernel on ISO storage domain if Linux operating system is used.
For example iso://vmlinuz-3.10.0-514.6.1.el7.x86_64.
Not used for hosts.
7.206.6. reported_kernel_cmdline Copy linkLink copied to clipboard!
The host kernel command line as reported by a running host.
This is a read-only attribute. Attempts to change this attribute are silently ignored.
This attribute is currently only used for hosts.
7.206.7. type Copy linkLink copied to clipboard!
Operating system name in human readable form.
For example Fedora or RHEL. In general one of the names returned by the operating system service.
Read only for hosts.
7.207. OperatingSystemInfo struct Copy linkLink copied to clipboard!
Represents a guest operating system.
| Name | Type | Summary |
|---|---|---|
|
| Operating system architecture. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| Large icon of the guest operating system. | |
|
| A human-readable name in plain text. | |
|
| Small icon of the guest operating system. | |
|
| TPM support status. |
7.207.1. large_icon Copy linkLink copied to clipboard!
Large icon of the guest operating system. Maximum dimensions: width 150px, height 120px.
7.207.2. small_icon Copy linkLink copied to clipboard!
Small icon of the guest operating system. Maximum dimensions: width 43px, height 43px.
7.208. Option struct Copy linkLink copied to clipboard!
7.209. OsType enum Copy linkLink copied to clipboard!
Type representing kind of operating system.
This type has been deprecated with the introduction of the OperatingSystemInfo type. Operating systems are available as a top-level collection in the API: operating_systems.
The end-user declares the type of the operating system installed in the virtual machine (guest operating system) by selecting one of these values. This declaration enables the system to tune the virtual machine configuration for better user experience. For example, the system chooses devices that are most suitable for the operating system. Note that the system rely on user’s selection and does not verify it by inspecting the actual guest operating system installed.
| Name | Summary |
|---|---|
|
| Other type of operating system, not specified by the other values. |
|
| Distribution of Linux other than those specified by the other values. |
|
| Red Hat Enterprise Linux 3 32-bit. |
|
| Red Hat Enterprise Linux 3 64-bit. |
|
| Red Hat Enterprise Linux 4 32-bit. |
|
| Red Hat Enterprise Linux 4 64-bit. |
|
| Red Hat Enterprise Linux 5 32-bit. |
|
| Red Hat Enterprise Linux 5 64-bit. |
|
| Red Hat Enterprise Linux 6 32-bit. |
|
| Red Hat Enterprise Linux 6 64-bit. |
|
|
This value is mapped to |
|
| Windows 2003 32-bit. |
|
| Windows 2003 64-bit. |
|
| Windows 2008 32-bit. |
|
| Windows 2008 R2 64-bit. |
|
| Windows 2008 64-bit. |
|
| Windows 2012 64-bit. |
|
| Windows 7 32-bit. |
|
| Windows 7 64-bit. |
|
| Windows 8 32-bit. |
|
| Windows 8 64-bit. |
|
| Windows XP. |
7.210. Package struct Copy linkLink copied to clipboard!
Type representing a package.
This is an example of the package element:
<package> <name>libipa_hbac-1.9.2-82.11.el6_4.i686</name> </package>
<package>
<name>libipa_hbac-1.9.2-82.11.el6_4.i686</name>
</package>
| Name | Type | Summary |
|---|---|---|
|
| The name of the package. |
7.211. ParallelMigrationsPolicy enum Copy linkLink copied to clipboard!
Type representing parallel migration connections policy.
| Name | Summary |
|---|---|
|
| Choose automatically between parallel and non-parallel connections. |
|
| Use parallel connections and select their number automatically. |
|
| Use manually specified number of parallel connections. |
|
| Use non-parallel connections. |
|
| Use cluster value (applicable only to VMs). |
7.211.1. auto Copy linkLink copied to clipboard!
Choose automatically between parallel and non-parallel connections. If parallel connections are used, select their number automatically.
7.211.2. custom Copy linkLink copied to clipboard!
Use manually specified number of parallel connections. The number of parallel connections must be set in MigrationOptions.customParallelMigrations.
7.212. Payload struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.213. PayloadEncoding enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.214. Permission struct Copy linkLink copied to clipboard!
Type represents a permission.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to cluster. | |
|
| Reference to data center. | |
|
| Reference to disk. | |
|
| Reference to group. | |
|
| Reference to host. | |
|
| Reference to role. | |
|
| Reference to storage domain. | |
|
| Reference to template. | |
|
| Reference to user. | |
|
| Reference to virtual machine. | |
|
| Reference to virtual machines pool. |
7.215. Permit struct Copy linkLink copied to clipboard!
Type represents a permit.
| Name | Type | Summary |
|---|---|---|
|
| Specifies whether permit is administrative or not. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to the role the permit belongs to. |
7.216. PmProxy struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.217. PmProxyType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| The fence proxy is selected from the same cluster as the fenced host. |
|
| The fence proxy is selected from the same data center as the fenced host. |
|
| The fence proxy is selected from a different data center than the fenced host. |
7.218. PolicyUnitType enum Copy linkLink copied to clipboard!
Holds the types of all internal policy unit types.
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.219. PortMirroring struct Copy linkLink copied to clipboard!
7.220. PowerManagement struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| The host name or IP address of the host. | |
|
| Specifies fence agent options when multiple fences are used. | |
|
| Toggles the automated power control of the host in order to save energy. | |
|
| Indicates whether power management configuration is enabled or disabled. | |
|
| Toggles whether to determine if kdump is running on the host before it is shut down. | |
|
| Fencing options for the selected type= specified with the option name="" and value="" strings. | |
|
| A valid, robust password for power management. | |
|
| Determines the power management proxy. | |
|
| Determines the power status of the host. | |
|
| Fencing device code. | |
|
| A valid user name for power management. |
7.220.1. agents Copy linkLink copied to clipboard!
Specifies fence agent options when multiple fences are used.
Use the order sub-element to prioritize the fence agents. Agents are run sequentially according to their order until the fence action succeeds. When two or more fence agents have the same order, they are run concurrently. Other sub-elements include type, ip, user, password, and options.
7.220.2. automatic_pm_enabled Copy linkLink copied to clipboard!
Toggles the automated power control of the host in order to save energy. When set to true, the host will be automatically powered down if the cluster’s load is low, and powered on again when required. This is set to true when a host is created, unless disabled by the user.
7.220.3. kdump_detection Copy linkLink copied to clipboard!
Toggles whether to determine if kdump is running on the host before it is shut down. When set to true, the host will not shut down during a kdump process. This is set to true when a host has power management enabled, unless disabled by the user.
7.220.4. type Copy linkLink copied to clipboard!
Fencing device code.
A list of valid fencing device codes are available in the capabilities collection.
7.221. PowerManagementStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Host is OFF. |
|
| Host is ON. |
|
| Unknown status. |
7.222. Product struct Copy linkLink copied to clipboard!
7.223. ProductInfo struct Copy linkLink copied to clipboard!
Product information.
The entry point contains a product_info element to help an API user determine the legitimacy of the Red Hat Virtualization environment. This includes the name of the product, the vendor and the version.
Verify a genuine Red Hat Virtualization environment
The follow elements identify a genuine Red Hat Virtualization environment:
| Name | Type | Summary |
|---|---|---|
|
| The ID of this particular installation of the product. | |
|
|
The name of the product, for example | |
|
| The name of the vendor, for example `ovirt. | |
|
| The version number of the product. |
7.223.1. vendor Copy linkLink copied to clipboard!
The name of the vendor, for example ovirt.org.
7.224. ProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
|
7.225. Property struct Copy linkLink copied to clipboard!
7.226. ProxyTicket struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.227. QcowVersion enum Copy linkLink copied to clipboard!
The QCOW version specifies to the qemu which qemu version the volume supports.
This field can be updated using the update API and will be reported only for QCOW volumes, it is determined by the storage domain’s version which the disk is created on. Storage domains with version lower than V4 support QCOW2 version 2 volumes, while V4 storage domains also support QCOW2 version 3. For more information about features of the different QCOW versions, see here.
| Name | Summary |
|---|---|
|
| The Copy On Write default compatibility version It means that every QEMU can use it. |
|
| The Copy On Write compatibility version which was introduced in QEMU 1. |
7.227.1. qcow2_v3 Copy linkLink copied to clipboard!
The Copy On Write compatibility version which was introduced in QEMU 1.1 It means that the new format is in use.
7.228. Qos struct Copy linkLink copied to clipboard!
This type represents the attributes to define Quality of service (QoS).
For storage the type is storage, the attributes max_throughput, max_read_throughput, max_write_throughput, max_iops, max_read_iops and max_write_iops are relevant.
For resources with computing capabilities the type is cpu, the attribute cpu_limit is relevant.
For virtual machines networks the type is network, the attributes inbound_average, inbound_peak, inbound_burst, outbound_average, outbound_peak and outbound_burst are relevant.
For host networks the type is hostnetwork, the attributes outbound_average_linkshare, outbound_average_upperlimit and outbound_average_realtime are relevant.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| The maximum processing capability in %. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The desired average inbound bit rate in Mbps (Megabits per sec). | |
|
| The amount of data that can be delivered in a single burst, in MB. | |
|
| The maximum inbound rate in Mbps (Megabits per sec). | |
|
| Maximum permitted number of input and output operations per second. | |
|
| Maximum permitted number of input operations per second. | |
|
| Maximum permitted throughput for read operations. | |
|
| Maximum permitted total throughput. | |
|
| Maximum permitted number of output operations per second. | |
|
| Maximum permitted throughput for write operations. | |
|
| A human-readable name in plain text. | |
|
| The desired average outbound bit rate in Mbps (Megabits per sec). | |
|
| Weighted share. | |
|
| The committed rate in Mbps (Megabits per sec). | |
|
| The maximum bandwidth to be used by a network in Mbps (Megabits per sec). | |
|
| The amount of data that can be sent in a single burst, in MB. | |
|
| The maximum outbound rate in Mbps (Megabits per sec). | |
|
| The kind of resources this entry can be assigned. |
7.228.1. cpu_limit Copy linkLink copied to clipboard!
The maximum processing capability in %.
Used to configure computing resources.
7.228.2. inbound_average Copy linkLink copied to clipboard!
The desired average inbound bit rate in Mbps (Megabits per sec).
Used to configure virtual machines networks. If defined, inbound_peak and inbound_burst also has to be set.
See Libvirt-QOS for further details.
7.228.3. inbound_burst Copy linkLink copied to clipboard!
The amount of data that can be delivered in a single burst, in MB.
Used to configure virtual machine networks. If defined, inbound_average and inbound_peak must also be set.
See Libvirt-QOS for further details.
7.228.4. inbound_peak Copy linkLink copied to clipboard!
The maximum inbound rate in Mbps (Megabits per sec).
Used to configure virtual machines networks. If defined, inbound_average and inbound_burst also has to be set.
See Libvirt-QOS for further details.
7.228.5. max_iops Copy linkLink copied to clipboard!
Maximum permitted number of input and output operations per second.
Used to configure storage. Must not be set if max_read_iops or max_write_iops is set.
7.228.6. max_read_iops Copy linkLink copied to clipboard!
Maximum permitted number of input operations per second.
Used to configure storage. Must not be set if max_iops is set.
7.228.7. max_read_throughput Copy linkLink copied to clipboard!
Maximum permitted throughput for read operations.
Used to configure storage. Must not be set if max_throughput is set.
7.228.8. max_throughput Copy linkLink copied to clipboard!
Maximum permitted total throughput.
Used to configure storage. Must not be set if max_read_throughput or max_write_throughput is set.
7.228.9. max_write_iops Copy linkLink copied to clipboard!
Maximum permitted number of output operations per second.
Used to configure storage. Must not be set if max_iops is set.
7.228.10. max_write_throughput Copy linkLink copied to clipboard!
Maximum permitted throughput for write operations.
Used to configure storage. Must not be set if max_throughput is set.
7.228.11. outbound_average Copy linkLink copied to clipboard!
The desired average outbound bit rate in Mbps (Megabits per sec).
Used to configure virtual machines networks. If defined, outbound_peak and outbound_burst also has to be set.
See Libvirt-QOS for further details.
7.228.13. outbound_average_realtime Copy linkLink copied to clipboard!
The committed rate in Mbps (Megabits per sec).
Used to configure host networks. The minimum bandwidth required by a network. The committed rate requested is not guaranteed and will vary depending on the network infrastructure and the committed rate requested by other networks on the same logical link.
7.228.14. outbound_average_upperlimit Copy linkLink copied to clipboard!
The maximum bandwidth to be used by a network in Mbps (Megabits per sec).
Used to configure host networks. If outboundAverageUpperlimit and outbound_average_realtime are provided, the outbound_averageUpperlimit must not be lower than the outbound_average_realtime.
See Libvirt-QOS for further details.
7.228.15. outbound_burst Copy linkLink copied to clipboard!
The amount of data that can be sent in a single burst, in MB.
Used to configure virtual machine networks. If defined, outbound_average and outbound_peak must also be set.
See Libvirt-QOS for further details.
7.228.16. outbound_peak Copy linkLink copied to clipboard!
The maximum outbound rate in Mbps (Megabits per sec).
Used to configure virtual machines networks. If defined, outbound_average and outbound_burst also has to be set.
See Libvirt-QOS for further details.
| Name | Type | Summary |
|---|---|---|
|
| The data center the QoS is assiciated to. |
7.229. QosType enum Copy linkLink copied to clipboard!
This type represents the kind of resource the Quality of service (QoS) can be assigned to.
| Name | Summary |
|---|---|
|
| The Quality of service (QoS) can be assigned to resources with computing capabilities. |
|
| The Quality of service (QoS) can be assigned to host networks. |
|
| The Quality of service (QoS) can be assigned to virtual machines networks. |
|
| The Quality of service (QoS) can be assigned to storage. |
7.230. Quota struct Copy linkLink copied to clipboard!
Represents a quota object.
An example XML representation of a quota:
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| Vm[] |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.231. QuotaClusterLimit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
|
7.232. QuotaModeType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.233. QuotaStorageLimit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.234. Range struct Copy linkLink copied to clipboard!
7.235. Rate struct Copy linkLink copied to clipboard!
Determines maximum speed of consumption of bytes from random number generator device.
7.236. RegistrationAffinityGroupMapping struct Copy linkLink copied to clipboard!
This type describes how to map affinity groups as part of the object registration. An object can be a virtual machine, template, etc.
An example of an XML representation using this mapping:
| Name | Type | Summary |
|---|---|---|
|
| Reference to the original affinity group. | |
|
| Reference to the destination affinity group. |
7.236.1. from Copy linkLink copied to clipboard!
Reference to the original affinity group. It can be specified using name.
7.237. RegistrationAffinityLabelMapping struct Copy linkLink copied to clipboard!
This type describes how to map affinity labels as part of the object registration. An object can be a virtual machine, template, etc.
An example of an XML representation using mapping:
| Name | Type | Summary |
|---|---|---|
|
| Reference to the original affinity label. | |
|
| Reference to the destination affinity label. |
7.237.1. from Copy linkLink copied to clipboard!
Reference to the original affinity label. It can be specified using name.
7.238. RegistrationClusterMapping struct Copy linkLink copied to clipboard!
This type describes how to map clusters as part of the object registration. An object can be a virtual machine, template, etc.
An example of an XML representation using this mapping:
| Name | Type | Summary |
|---|---|---|
|
| Reference to the original cluster. | |
|
| Reference to the destination cluster. |
7.238.1. from Copy linkLink copied to clipboard!
Reference to the original cluster. It can be specified using the id or the name.
7.238.2. to Copy linkLink copied to clipboard!
Reference to the destination cluster. It can be specified using the id or the name.
7.239. RegistrationConfiguration struct Copy linkLink copied to clipboard!
This type describes how an object (virtual machine, template, etc) is registered, and is used for the implementation of disaster recovery solutions.
Each mapping contained in this type can be used to map objects in the original system to corresponding objects in the system where the virtual machine or template is being registered. For example, there could be a primary setup with a virtual machine configured on cluster A, and an active secondary setup with cluster B. Cluster B is compatible with that virtual machine, and in case of a disaster recovery scenario the storage domain can be imported to the secondary setup, and the user can register the virtual machine to cluster B.
In that case, we can automate the recovery process by defining a cluster mapping. After the entity is registered, its OVF will indicate it belongs to cluster A, but the mapping will indicate that cluster A will be replaced with cluster B. Red Hat Virtualization Manager should do the switch and register the virtual machine to cluster B in the secondary site.
Cluster mapping is just one example, there are different types of mappings:
- Cluster mapping.
- LUN mapping.
- Role mapping.
- Domain mapping.
- Permissions mapping.
- Affinity Group mapping.
- Affinity Label mapping.
- Virtual NIC profile mapping.
Each mapping will be used for its specific OVF’s data once the register operation takes place in the Red Hat Virtualization Manager.
An example of an XML representation using the mapping:
| Name | Type | Summary |
|---|---|---|
|
| Describes how the affinity groups are mapped. | |
|
| Describes how the affinity labels are mapped. | |
|
| Describes how the clusters that the object references are mapped. | |
|
| Describes how the users' domains are mapped. | |
|
| Describes how the LUNs are mapped. | |
|
| Describes how the roles are mapped. | |
|
| Mapping rules for virtual NIC profiles that will be applied during the register process. |
7.240. RegistrationDomainMapping struct Copy linkLink copied to clipboard!
This type describes how to map the users' domain as part of the object registration. An object can be a virtual machine, template, etc. NOTE: This is based on the assumption that user names will be the same, and that only the domain name will be changed.
An example of an XML representation using this mapping:
| Name | Type | Summary |
|---|---|---|
|
| Reference to the original domain. | |
|
| Reference to the destination domain. |
7.240.1. from Copy linkLink copied to clipboard!
Reference to the original domain. It can be specified using name.
7.241. RegistrationLunMapping struct Copy linkLink copied to clipboard!
This type describes how to map LUNs as part of the object registration. An object can be a virtual machine, template, etc.
An external LUN disk is an entity which does not reside on a storage domain. It must be specified because it doesn’t need to exist in the environment where the object is registered. An example of an XML representation using this mapping:
| Name | Type | Summary |
|---|---|---|
|
| Reference to the original LUN. | |
|
| Reference to the LUN which is to be added to the virtual machine. |
7.241.1. from Copy linkLink copied to clipboard!
Reference to the original LUN. This must be specified using the id attribute.
7.242. RegistrationRoleMapping struct Copy linkLink copied to clipboard!
This type describes how to map roles as part of the object registration. An object can be a virtual machine, template, etc.
A role mapping is intended to map correlating roles between the primary site and the secondary site. For example, there may be permissions with role UserVmRunTimeManager for the virtual machine that is being registered. Therefore we can send a mapping that will register the virtual machine in the secondary setup using the SuperUser role instead of UserVmRunTimeManager An example of an XML representation using this mapping:
| Name | Type | Summary |
|---|---|---|
|
| Reference to the original role. | |
|
| Reference to the destination role. |
7.242.1. from Copy linkLink copied to clipboard!
Reference to the original role. It can be specified using name.
7.243. RegistrationVnicProfileMapping struct Copy linkLink copied to clipboard!
Maps an external virtual NIC profile to one that exists in the Red Hat Virtualization Manager. The target may be specified as a profile ID or a pair of profile name and network name.
If, for example, the desired virtual NIC profile mapping includes the following lines:
| Source network name | Source network profile name | Target virtual NIC profile ID\names |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Then the following snippet should be added to RegistrationConfiguration
| Name | Type | Summary |
|---|---|---|
|
| References to the external network and the external network profile. | |
|
| Reference to to an existing virtual NIC profile. |
7.243.1. from Copy linkLink copied to clipboard!
References to the external network and the external network profile. Both should be specified using their name.
7.243.2. to Copy linkLink copied to clipboard!
Reference to to an existing virtual NIC profile. It should be specified using its name or id. Either name or id should be specified but not both.
7.244. ReportedConfiguration struct Copy linkLink copied to clipboard!
7.245. ReportedDevice struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| Ip[] | |
|
| ||
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.246. ReportedDeviceType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
7.247. ResolutionType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.248. RngDevice struct Copy linkLink copied to clipboard!
Random number generator (RNG) device model.
7.249. RngSource enum Copy linkLink copied to clipboard!
Representing the random generator backend types.
| Name | Summary |
|---|---|
|
|
Obtains random data from the |
|
|
Obtains random data from the |
|
|
Obtains random data from the |
7.249.1. urandom Copy linkLink copied to clipboard!
Obtains random data from the /dev/urandom device.
This RNG source is meant to replace random RNG source for non-cluster-aware entities (i.e. Blank template and instance types) and entities associated with clusters with compatibility version 4.1 or higher.
7.250. Role struct Copy linkLink copied to clipboard!
Represents a system role.
| Name | Type | Summary |
|---|---|---|
|
| Defines the role as administrative-only or not. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| Defines the ability to update or delete the role. | |
|
| A human-readable name in plain text. |
7.250.1. mutable Copy linkLink copied to clipboard!
Defines the ability to update or delete the role.
Roles with mutable set to false are predefined roles.
7.251. RoleType enum Copy linkLink copied to clipboard!
Type representing whether a role is administrative or not. A user which was granted at least one administrative role is considered an administrator.
| Name | Summary |
|---|---|
|
| Administrative role. |
|
| User role. |
7.252. SchedulingPolicy struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| A human-readable name in plain text. | |
|
|
7.253. SchedulingPolicyUnit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
|
7.254. ScsiGenericIO enum Copy linkLink copied to clipboard!
When a direct LUN disk is using SCSI passthrough the privileged I/O policy is determined by this enum.
| Name | Summary |
|---|---|
|
| Disable SCSI passthrough. |
|
| Disallow privileged SCSI I/O. |
|
| Allow privileged SCSI I/O. |
7.255. SeLinux struct Copy linkLink copied to clipboard!
Represents SELinux in the system.
| Name | Type | Summary |
|---|---|---|
|
| SELinux current mode. |
7.256. SeLinuxMode enum Copy linkLink copied to clipboard!
Represents an SELinux enforcement mode.
| Name | Summary |
|---|---|
|
| SELinux is disabled in the kernel. |
|
| SELinux is running and enforcing permissions. |
|
| SELinux is running and logging but not enforcing permissions. |
7.257. SerialNumber struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
7.258. SerialNumberPolicy enum Copy linkLink copied to clipboard!
Type representing the policy of a Serial Number.
| Name | Summary |
|---|---|
|
| This policy allows the user to provide an arbitrary string as the Serial Number. |
|
| This policy is the legacy policy. |
|
| This policy is used to remove the Serial Number Policy, moving it to default: null. |
|
| This policy will use the Virtual Machine ID as the Serial Number. |
7.258.1. host Copy linkLink copied to clipboard!
This policy is the legacy policy. It will use the Host ID as the Serial Number.
7.259. Session struct Copy linkLink copied to clipboard!
Describes a user session to a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| Indicates if this is a console session. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The IP address the user is connected from. | |
|
| A human-readable name in plain text. | |
|
| The protocol used by the session. |
7.259.1. console_user Copy linkLink copied to clipboard!
Indicates if this is a console session.
The value will be true for console users (SPICE or VNC), and false for others (such as RDP or SSH).
7.259.2. ip Copy linkLink copied to clipboard!
The IP address the user is connected from.
Currently only available for console users.
7.259.3. protocol Copy linkLink copied to clipboard!
The protocol used by the session.
Currently not used. Intended for info about how the user is connected: through SPICE, VNC, SSH, or RDP.
7.259.4. user Copy linkLink copied to clipboard!
The user related to this session.
If the user is a console user, this is a link to the real Red Hat Virtualization user. Otherwise, only the user name is provided.
7.260. SkipIfConnectivityBroken struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| If enabled, we will not fence a host in case more than a configurable percentage of hosts in the cluster lost connectivity as well. | |
|
| Threshold for connectivity testing. |
7.260.1. enabled Copy linkLink copied to clipboard!
If enabled, we will not fence a host in case more than a configurable percentage of hosts in the cluster lost connectivity as well. This comes to prevent fencing storm in cases where there is a global networking issue in the cluster.
7.260.2. threshold Copy linkLink copied to clipboard!
Threshold for connectivity testing. If at least the threshold percentage of hosts in the cluster lost connectivity then fencing will not take place.
7.261. SkipIfSdActive struct Copy linkLink copied to clipboard!
This type represents the storage related configuration in the fencing policy.
| Name | Type | Summary |
|---|---|---|
|
| If enabled, we will skip fencing in case the host maintains its lease in the storage. |
7.261.1. enabled Copy linkLink copied to clipboard!
If enabled, we will skip fencing in case the host maintains its lease in the storage. It means that if the host still has storage access then it won’t get fenced.
7.262. Snapshot struct Copy linkLink copied to clipboard!
Represents a snapshot object.
Example XML representation:
| Name | Type | Summary |
|---|---|---|
|
| Specifies if and how the auto CPU and NUMA configuration is applied. | |
|
| Reference to virtual machine’s BIOS configuration. | |
|
| Free text containing comments about this object. | |
|
| Console configured for this virtual machine. | |
|
| The configuration of the virtual machine CPU. | |
|
| Specifies if and how the CPU and NUMA configuration is applied. | |
|
| ||
|
| The virtual machine creation date. | |
|
| Virtual machine custom compatibility version. | |
|
| ||
|
| ||
|
| Properties sent to VDSM to configure various hooks. | |
|
| The date when this snapshot has been created. | |
|
|
If | |
|
| A human-readable description in plain text. | |
|
| The virtual machine display configuration. | |
|
| Domain configured for this virtual machine. | |
|
| Fully qualified domain name of the virtual machine. | |
|
| What operating system is installed on the virtual machine. | |
|
| What time zone is used by the virtual machine (as returned by guest agent). | |
|
|
Indicates whether the virtual machine has snapshots with disks in | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to the virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| Reference to the storage domain this virtual machine/template lease reside on. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of a running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
|
If | |
|
| A human-readable name in plain text. | |
|
| Virtual machine configuration has been changed and requires restart of the virtual machine. | |
|
| How the NUMA topology is applied. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| Optional payloads of the virtual machine, used for ISOs to configure it. | |
|
| Indicates if the content of the memory of the virtual machine is included in the snapshot. | |
|
| The configuration of the virtual machine’s placement policy. | |
|
| Random Number Generator device configuration for this virtual machine. | |
|
|
If | |
|
| Virtual machine’s serial number in a cluster. | |
|
| Virtual machine’s small icon. | |
|
| Status of the snapshot. | |
|
| Type of the snapshot. | |
|
|
If | |
|
| Reference to the Single Sign On configuration this virtual machine is configured for. | |
|
|
If | |
|
| The date in which the virtual machine was started. | |
|
|
If | |
|
| The current status of the virtual machine. | |
|
| Human readable detail of current status. | |
|
| The reason the virtual machine was stopped. | |
|
| The date in which the virtual machine was stopped. | |
|
| Determines how the virtual machine will be resumed after storage error. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
If | |
|
|
If | |
|
| Determines whether the virtual machine is optimized for desktop or server. | |
|
| Configuration of USB devices for this virtual machine (count, type). | |
|
|
If | |
|
| Reference to VirtIO SCSI configuration. | |
|
| Number of queues for a Virtio-SCSI contoller this field requires virtioScsiMultiQueuesEnabled to be true see virtioScsiMultiQueuesEnabled for more info | |
|
|
If |
7.262.1. auto_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the auto CPU and NUMA configuration is applied.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It might be removed in the future. Please use CpuPinningPolicy instead.
7.262.2. cpu Copy linkLink copied to clipboard!
The configuration of the virtual machine CPU.
The socket configuration can be updated without rebooting the virtual machine. The cores and the threads require a reboot.
For example, to change the number of sockets to 4 immediately, and the number of cores and threads to 2 after reboot, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body:
7.262.3. cpu_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the CPU and NUMA configuration is applied. When not specified the previous behavior of CPU pinning string will determine CpuPinningPolicy to None or Manual.
7.262.4. custom_compatibility_version Copy linkLink copied to clipboard!
Virtual machine custom compatibility version.
Enables a virtual machine to be customized to its own compatibility version. If custom_compatibility_version is set, it overrides the cluster’s compatibility version for this particular virtual machine.
The compatibility version of a virtual machine is limited by the data center the virtual machine resides in, and is checked against capabilities of the host the virtual machine is planned to run on.
7.262.5. high_availability Copy linkLink copied to clipboard!
The virtual machine high availability configuration. If set, the virtual machine will be automatically restarted when it unexpectedly goes down.
7.262.6. initialization Copy linkLink copied to clipboard!
Reference to the virtual machine’s initialization configuration.
Since Red Hat Virtualization 4.1.8 this property can be cleared by sending an empty tag.
For example, to clear the initialization attribute send a request like this:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body like this:
<vm> <initialization/> </vm>
<vm>
<initialization/>
</vm>
The response to such a request, and requests with the header All-Content: true will still contain this attribute.
7.262.7. large_icon Copy linkLink copied to clipboard!
Virtual machine’s large icon. Either set by user or refers to image set according to operating system.
7.262.8. lease Copy linkLink copied to clipboard!
Reference to the storage domain this virtual machine/template lease reside on.
A virtual machine running with a lease requires checking while running that the lease is not taken by another host, preventing another instance of this virtual machine from running on another host. This provides protection against split-brain in highly available virtual machines. A template can also have a storage domain defined for a lease in order to have the virtual machines created from this template to be preconfigured with this storage domain as the location of the leases.
7.262.9. memory Copy linkLink copied to clipboard!
The virtual machine’s memory, in bytes.
For example, to update a virtual machine to contain 1 Gibibyte (GiB) of memory, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With the following request body:
<vm> <memory>1073741824</memory> </vm>
<vm>
<memory>1073741824</memory>
</vm>
Memory hot plug is supported from Red Hat Virtualization 3.6 onwards. You can use the example above to increase memory while the virtual machine is in state up. The size increment must be dividable by the value of the HotPlugMemoryBlockSizeMb configuration value (256 MiB by default). If the memory size increment is not dividable by this value, the memory size change is only stored to next run configuration. Each successful memory hot plug operation creates one or two new memory devices.
Memory hot unplug is supported since Red Hat Virtualization 4.2 onwards. Memory hot unplug can only be performed when the virtual machine is in state up. Only previously hot plugged memory devices can be removed by the hot unplug operation. The requested memory decrement is rounded down to match sizes of a combination of previously hot plugged memory devices. The requested memory value is stored to next run configuration without rounding.
Memory in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
Red Hat Virtualization Manager internally rounds values down to whole MiBs (1MiB = 220 bytes)
7.262.10. migration Copy linkLink copied to clipboard!
Reference to configuration of migration of a running virtual machine to another host.
API for querying migration policy by ID returned by this method is not implemented yet. Use /ovirt-engine/api/options/MigrationPolicies to get a list of all migration policies with their IDs.
7.262.11. migration_downtime Copy linkLink copied to clipboard!
Maximum time the virtual machine can be non responsive during its live migration to another host in ms.
Set either explicitly for the virtual machine or by engine-config -s DefaultMaximumMigrationDowntime=[value]
7.262.12. next_run_configuration_exists Copy linkLink copied to clipboard!
Virtual machine configuration has been changed and requires restart of the virtual machine. Changed configuration is applied at processing the virtual machine’s shut down.
7.262.13. numa_tune_mode Copy linkLink copied to clipboard!
How the NUMA topology is applied. Deprecated in favor of NUMA tune per vNUMA node.
7.262.14. origin Copy linkLink copied to clipboard!
The origin of this virtual machine.
Possible values:
-
ovirt -
rhev -
vmware -
xen -
external -
hosted_engine -
managed_hosted_engine -
kvm -
physical_machine -
hyperv
7.262.15. persist_memorystate Copy linkLink copied to clipboard!
Indicates if the content of the memory of the virtual machine is included in the snapshot.
When a snapshot is created the default value is true.
7.262.16. placement_policy Copy linkLink copied to clipboard!
The configuration of the virtual machine’s placement policy.
This configuration can be updated to pin a virtual machine to one or more hosts.
Virtual machines that are pinned to multiple hosts cannot be live migrated, but in the event of a host failure, any virtual machine configured to be highly available is automatically restarted on one of the other hosts to which the virtual machine is pinned.
For example, to pin a virtual machine to two hosts, send the following request:
PUT /api/vms/123
PUT /api/vms/123
With a request body like this:
7.262.17. small_icon Copy linkLink copied to clipboard!
Virtual machine’s small icon. Either set by user or refers to image set according to operating system.
7.262.18. sso Copy linkLink copied to clipboard!
Reference to the Single Sign On configuration this virtual machine is configured for. The user can be automatically signed in the virtual machine’s operating system when console is opened.
7.262.19. stop_reason Copy linkLink copied to clipboard!
The reason the virtual machine was stopped. Optionally set by user when shutting down the virtual machine.
7.262.20. tpm_enabled Copy linkLink copied to clipboard!
If true, a TPM device is added to the virtual machine. By default the value is false. This property is only visible when fetching if "All-Content=true" header is set.
| Name | Type | Summary |
|---|---|---|
|
| Optional. | |
|
| List of applications installed on the virtual machine. | |
|
| Reference to the ISO mounted to the CDROM. | |
|
| Reference to cluster the virtual machine belongs to. | |
|
| Reference to CPU profile used by this virtual machine. | |
|
| References the disks attached to the virtual machine. | |
|
| List of disks linked to the snapshot. | |
|
| The dynamic configuration of the virtual machine CPU. | |
|
| ||
|
| Reference to the ISO mounted to the floppy. | |
|
| List of graphics consoles configured for this virtual machine. | |
|
| Reference to the host the virtual machine is running on. | |
|
| References devices associated to this virtual machine. | |
|
| The virtual machine configuration can be optionally predefined via one of the instance types. | |
|
| Lists all the Katello errata assigned to the virtual machine. | |
|
| Mediated devices configuration. | |
|
| Nic[] | References the list of network interface devices on the virtual machine. |
|
| Refers to the NUMA Nodes configuration used by this virtual machine. | |
|
| References the original template used to create the virtual machine. | |
|
| Permissions set for this virtual machine. | |
|
| Reference to quota configuration set for this virtual machine. | |
|
| ||
|
| List of user sessions opened for this virtual machine. | |
|
| Refers to all snapshots taken from the virtual machine. | |
|
| Statistics data collected from this virtual machine. | |
|
| Reference to storage domain the virtual machine belongs to. | |
|
| Tag[] | |
|
| Reference to the template the virtual machine is based on. | |
|
| The virtual machine this snapshot has been taken for. | |
|
| Reference to the pool the virtual machine is optionally member of. | |
|
| Refers to the Watchdog configuration. |
7.262.21. affinity_labels Copy linkLink copied to clipboard!
Optional. Used for labeling of sub-clusters.
7.262.22. katello_errata Copy linkLink copied to clipboard!
Lists all the Katello errata assigned to the virtual machine.
GET /ovirt-engine/api/vms/123/katelloerrata
GET /ovirt-engine/api/vms/123/katelloerrata
You will receive response in XML like this one:
7.262.23. original_template Copy linkLink copied to clipboard!
References the original template used to create the virtual machine.
If the virtual machine is cloned from a template or another virtual machine, the template links to the Blank template, and the original_template is used to track history.
Otherwise the template and original_template are the same.
7.262.24. statistics Copy linkLink copied to clipboard!
Statistics data collected from this virtual machine.
Note that some statistics, notably memory.buffered and memory.cached are available only when Red Hat Virtualization guest agent is installed in the virtual machine.
7.263. SnapshotStatus enum Copy linkLink copied to clipboard!
Represents the current status of the snapshot.
| Name | Summary |
|---|---|
|
| The snapshot is being previewed. |
|
| The snapshot is locked. |
|
| The snapshot is OK. |
7.263.1. locked Copy linkLink copied to clipboard!
The snapshot is locked.
The snapshot is locked when it is in process of being created, deleted, restored or previewed.
7.264. SnapshotType enum Copy linkLink copied to clipboard!
Represents the type of the snapshot.
| Name | Summary |
|---|---|
|
| Reference to the current configuration of the virtual machines. |
|
|
The |
|
| Snapshot created by user. |
|
| Snapshot created internally for stateless virtual machines. |
7.264.1. preview Copy linkLink copied to clipboard!
The active snapshot will become preview if some snapshot is being previewed.
In other words, this is the active snapshot before preview.
7.264.2. stateless Copy linkLink copied to clipboard!
Snapshot created internally for stateless virtual machines.
This snapshot is created when the virtual machine is started and it is restored when the virtual machine is shut down.
7.265. SpecialObjects struct Copy linkLink copied to clipboard!
This type contains references to special objects, such as blank templates and the root of a hierarchy of tags.
7.266. Spm struct Copy linkLink copied to clipboard!
7.267. SpmStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.268. Ssh struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| Fingerprint of SSH public key for a host. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| SSH public key of the host using SSH public key format as defined in link:https://tools. | |
|
|
7.268.1. fingerprint Copy linkLink copied to clipboard!
Fingerprint of SSH public key for a host. This field is deprecated since 4.4.5 and will be removed in the future.
Please use publicKey instead.
7.268.2. public_key Copy linkLink copied to clipboard!
SSH public key of the host using SSH public key format as defined in RFC4253.
7.269. SshAuthenticationMethod enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.270. SshPublicKey struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| Contains a saved SSH key. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
|
7.271. Sso struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
7.272. SsoMethod enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
7.273. Statistic struct Copy linkLink copied to clipboard!
A generic type used for all kinds of statistics.
Statistic contains the statistics values for various entities. The following object contain statistics:
- Disk
- Host
- HostNic
- NumaNode
- Nic
- Vm
- GlusterBrick
- Step
- GlusterVolume
An example of a XML representation:
This statistics sub-collection is read-only.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The type of statistic measures. | |
|
| A human-readable name in plain text. | |
|
| The data type for the statistical values that follow. | |
|
| The unit or rate to measure of the statistical values. | |
|
|
A data set that contains |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
A relationship to the containing | |
|
| ||
|
| ||
|
| A reference to the host NIC. | |
|
| ||
|
| ||
|
| ||
|
|
7.274. StatisticKind enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.275. StatisticUnit enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
7.276. Step struct Copy linkLink copied to clipboard!
Represents a step, which is part of job execution. Step is used to describe and track a specific execution unit which is part of a wider sequence. Some steps support reporting their progress.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The end time of the step. | |
|
| Indicates if the step is originated by an external system. | |
|
| The external system which is referenced by the step. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| The order of the step in current hierarchy level. | |
|
| The step progress (if reported) in percentages. | |
|
| The start time of the step. | |
|
| The status of the step. | |
|
| The type of the step. |
7.276.1. external Copy linkLink copied to clipboard!
Indicates if the step is originated by an external system. External steps are managed externally, by the creator of the step.
| Name | Type | Summary |
|---|---|---|
|
| The host used for the step execution (optional). | |
|
|
References the | |
|
| References the parent step of the current step in the hierarchy. | |
|
|
7.277. StepEnum enum Copy linkLink copied to clipboard!
Type representing a step type.
| Name | Summary |
|---|---|
|
| The executing step type. |
|
| The finalizing step type. |
|
|
The |
|
|
The |
|
| The unknown step type. |
|
| The validation step type. |
7.277.1. executing Copy linkLink copied to clipboard!
The executing step type. Used to track the main execution block of the job. Usually it will be a parent step of several sub-steps which describe portions of the execution step.
7.277.2. finalizing Copy linkLink copied to clipboard!
The finalizing step type. Describes the post-execution steps requires to complete the job.
7.277.3. rebalancing_volume Copy linkLink copied to clipboard!
The rebalancing volume step type. Describes a step type which is part of Gluster flow.
7.277.4. removing_bricks Copy linkLink copied to clipboard!
The removing bricks step type. Describes a step type which is part of Gluster flow.
7.277.5. unknown Copy linkLink copied to clipboard!
The unknown step type. Describes a step type which its origin is unknown.
7.277.6. validating Copy linkLink copied to clipboard!
The validation step type. Used to verify the correctness of parameters and the validity of the parameters prior to the execution.
7.278. StepStatus enum Copy linkLink copied to clipboard!
Represents the status of the step.
| Name | Summary |
|---|---|
|
| The aborted step status. |
|
| The failed step status. |
|
| The finished step status. |
|
| The started step status. |
|
| The unknown step status. |
7.278.1. aborted Copy linkLink copied to clipboard!
The aborted step status. This status is applicable for an external step that was forcibly aborted.
7.278.2. finished Copy linkLink copied to clipboard!
The finished step status. This status describes a completed step execution.
7.278.3. started Copy linkLink copied to clipboard!
The started step status. This status represents a step which is currently being executed.
7.278.4. unknown Copy linkLink copied to clipboard!
The unknown step status. This status represents steps which their resolution is not known, i.e. steps that were executed before the system was unexpectedly restarted.
7.279. StorageConnection struct Copy linkLink copied to clipboard!
Represents a storage server connection.
Example XML representation:
<storage_connection id="123"> <address>mynfs.example.com</address> <type>nfs</type> <path>/exports/mydata</path> </storage_connection>
<storage_connection id="123">
<address>mynfs.example.com</address>
<type>nfs</type>
<path>/exports/mydata</path>
</storage_connection>
| Name | Type | Summary |
|---|---|---|
|
| A storage server connection’s address. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| The mount options of an NFS storage server connection. | |
|
| A human-readable name in plain text. | |
|
| The NFS retrans value of an NFS storage server connection. | |
|
| The NFS timeo value of an NFS storage server connection. | |
|
| The NFS version of an NFS storage server connection. | |
|
| The password of an iSCSI storage server connection. | |
|
| The path of an NFS storage server connection. | |
|
| The port of an iSCSI storage server connection. | |
|
| The portal of an iSCSI storage server connection. | |
|
| The target of an iSCSI storage server connection. | |
|
| A storage server connection’s type. | |
|
| The user name of an iSCSI storage server connection. | |
|
| The VFS type of an NFS storage server connection. |
| Name | Type | Summary |
|---|---|---|
|
| Link to the gluster volume, used by that storage domain. | |
|
|
7.280. StorageConnectionExtension struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.281. StorageDomain struct Copy linkLink copied to clipboard!
Storage domain.
An XML representation of a NFS storage domain with identifier 123:
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| This attribute indicates whether a data storage domain is used as backup domain or not. | |
|
| Specifies block size in bytes for a storage domain. | |
|
| Free text containing comments about this object. | |
|
| ||
|
| ||
|
| A human-readable description in plain text. | |
|
| Indicates whether disks' blocks on block storage domains will be discarded right before they are deleted. | |
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| Indicates whether a block storage domain supports discard operations. | |
|
| Indicates whether a block storage domain supports the property that discard zeroes the data. | |
|
| ||
|
| ||
|
| ||
|
|
Serves as the default value of |
7.281.1. backup Copy linkLink copied to clipboard!
This attribute indicates whether a data storage domain is used as backup domain or not. If the domain is set to backup then it will be used to store virtual machines and templates for disaster recovery purposes in the same way we use export storage domain. This attribute is only available with data storage domain and not with ISO domain or export storage domain. User can use this functionality while creating a data storage domain or importing a data storage domain.
7.281.2. block_size Copy linkLink copied to clipboard!
Specifies block size in bytes for a storage domain. Can be omitted and in that case will be defaulted to 512 bytes. Not all storage domains support all possible sizes.
7.281.3. discard_after_delete Copy linkLink copied to clipboard!
Indicates whether disks' blocks on block storage domains will be discarded right before they are deleted.
If true, and a disk on this storage domain has its wipe_after_delete value enabled, then when the disk is deleted:
- It is first wiped.
- Then its blocks are discarded.
- Finally it is deleted.
Note that:
-
Discard after delete will always be
falsefor non block storage types. -
Discard after delete can be set to
trueonly if the storage domain supports discard.
7.281.4. supports_discard Copy linkLink copied to clipboard!
Indicates whether a block storage domain supports discard operations. A storage domain only supports discard if all of the logical units that it is built from support discard; that is, if each logical unit’s discard_max_size value is greater than 0. This is one of the conditions necessary for a virtual disk in this storage domain to have its pass_discard attribute enabled.
7.281.5. supports_discard_zeroes_data Copy linkLink copied to clipboard!
Indicates whether a block storage domain supports the property that discard zeroes the data. A storage domain only supports the property that discard zeroes the data if all of the logical units that it is built from support it; that is, if each logical unit’s discard_zeroes_data value is true.
Since version 4.2.1 of the system, the support for this attribute has been removed as the sysfs file, discard_zeroes_data, was deprecated in the kernel. It is preserved for backwards compatibility, but the value will always be false.
7.281.6. wipe_after_delete Copy linkLink copied to clipboard!
Serves as the default value of wipe_after_delete for disks on this storage domain.
That is, newly created disks will get their wipe_after_delete value from their storage domains by default. Note that the configuration value SANWipeAfterDelete serves as the default value of block storage domains' wipe_after_delete value.
| Name | Type | Summary |
|---|---|---|
|
| A link to the data center that the storage domain is attached to. | |
|
| A set of links to the data centers that the storage domain is attached to. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Host is only relevant at creation time. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Vm[] |
7.281.7. data_center Copy linkLink copied to clipboard!
A link to the data center that the storage domain is attached to. This is preserved for backwards compatibility only, as the storage domain may be attached to multiple data centers (if it is an ISO domain). Use the dataCenters element instead.
7.282. StorageDomainLease struct Copy linkLink copied to clipboard!
Represents a lease residing on a storage domain.
A lease is a Sanlock resource residing on a special volume on the storage domain, this Sanlock resource is used to provide storage base locking.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the storage domain on which the lock resides on. |
7.283. StorageDomainStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
7.284. StorageDomainType enum Copy linkLink copied to clipboard!
Indicates the kind of data managed by a storage domain.
| Name | Summary |
|---|---|
|
| Data domains are used to store the disks and snapshots of the virtual machines and templates in the system. |
|
| Export domains are temporary storage repositories used to copy and move virtual machines and templates between data centers and Red Hat Virtualization environments. |
|
| Image domain store images that can be imported into from an external system. |
|
| ISO domains store ISO files (or logical CDs) used to install and boot operating systems and applications for the virtual machines. |
|
| Managed block storage domains are created on block storage devices. |
|
| Volume domains store logical volumes that can be used as disks for virtual machines. |
7.284.1. data Copy linkLink copied to clipboard!
Data domains are used to store the disks and snapshots of the virtual machines and templates in the system. In addition, snapshots of the disks are also stored in data domains. Data domains cannot be shared across data centers.
7.284.2. export Copy linkLink copied to clipboard!
Export domains are temporary storage repositories used to copy and move virtual machines and templates between data centers and Red Hat Virtualization environments. Export domains can also be used to backup virtual machines. An export domain can be moved between data centers but it can only be active in one data center at a time.
7.284.3. image Copy linkLink copied to clipboard!
Image domain store images that can be imported into from an external system. For example, images from an OpenStack Glance image repository.
7.284.4. iso Copy linkLink copied to clipboard!
ISO domains store ISO files (or logical CDs) used to install and boot operating systems and applications for the virtual machines. ISO domains remove the data center’s need for physical media. An ISO domain can be shared across different data centers.
7.284.5. managed_block_storage Copy linkLink copied to clipboard!
Managed block storage domains are created on block storage devices. These domains are accessed and managed by cinder.
7.284.6. volume Copy linkLink copied to clipboard!
Volume domains store logical volumes that can be used as disks for virtual machines. For example, volumes from an OpenStack Cincer block storage service.
7.285. StorageFormat enum Copy linkLink copied to clipboard!
Type which represents a format of storage domain.
| Name | Summary |
|---|---|
|
| Version 1 of the storage domain format is applicable to NFS, iSCSI and FC storage domains. |
|
| Version 2 of the storage domain format is applicable to iSCSI and FC storage domains. |
|
| Version 3 of the storage domain format is applicable to NFS, POSIX, iSCSI and FC storage domains. |
|
| Version 4 of the storage domain format. |
|
| Version 5 of the storage domain format is applicable to NFS, POSIX, and Gluster storage domains. |
7.285.1. v1 Copy linkLink copied to clipboard!
Version 1 of the storage domain format is applicable to NFS, iSCSI and FC storage domains.
Each storage domain contains metadata describing its own structure, and all of the names of physical volumes that are used to back virtual machine disk images. Master domains additionally contain metadata for all the domains and physical volume names in the storage pool. The total size of this metadata is limited to 2 KiB, limiting the number of storage domains that can be in a pool. Template and virtual machine base images are read only.
7.285.2. v2 Copy linkLink copied to clipboard!
Version 2 of the storage domain format is applicable to iSCSI and FC storage domains.
All storage domain and pool metadata is stored as logical volume tags rather than written to a logical volume. Metadata about virtual machine disk volumes is still stored in a logical volume on the domains. Physical volume names are no longer included in the metadata. Template and virtual machine base images are read only.
7.285.3. v3 Copy linkLink copied to clipboard!
Version 3 of the storage domain format is applicable to NFS, POSIX, iSCSI and FC storage domains.
All storage domain and pool metadata is stored as logical volume tags rather than written to a logical volume. Metadata about virtual machine disk volumes is still stored in a logical volume on the domains. Virtual machine and template base images are no longer read only. This change enables live snapshots, live storage migration, and clone from snapshot. Support for Unicode metadata is added, for non-English volume names.
7.285.4. v5 Copy linkLink copied to clipboard!
Version 5 of the storage domain format is applicable to NFS, POSIX, and Gluster storage domains.
Added support for 4096 bytes block sizes and variable sanlock alignments.
7.286. StorageType enum Copy linkLink copied to clipboard!
Type representing a storage domain type.
| Name | Summary |
|---|---|
|
| Cinder storage domain. |
|
| Fibre-Channel storage domain. |
|
| Glance storage domain. |
|
| Gluster-FS storage domain. |
|
| iSCSI storage domain. |
|
| Storage domain on Local storage. |
|
| Managed block storage domain. |
|
| NFS storage domain. |
|
| POSIX-FS storage domain. |
7.286.1. cinder Copy linkLink copied to clipboard!
Cinder storage domain. For more details on Cinder please go to Cinder.
7.286.2. glance Copy linkLink copied to clipboard!
Glance storage domain. For more details on Glance please go to Glance.
7.286.3. glusterfs Copy linkLink copied to clipboard!
Gluster-FS storage domain. For more details on Gluster please go to Gluster.
7.286.4. managed_block_storage Copy linkLink copied to clipboard!
Managed block storage domain. A storage domain managed using cinderlib. For supported storage drivers, see Available Drivers.
7.287. SwitchType enum Copy linkLink copied to clipboard!
Describes all switch types supported by the Manager.
| Name | Summary |
|---|---|
|
| The native switch type. |
|
| The Open vSwitch type. |
7.288. SystemOption struct Copy linkLink copied to clipboard!
Type representing a configuration option of the system.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Values of the option for various system versions. |
7.289. SystemOptionValue struct Copy linkLink copied to clipboard!
Type representing a pair of value and version of a configuration option.
7.290. Tag struct Copy linkLink copied to clipboard!
Represents a tag in the system.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| Reference to the group which has this tag assigned. | |
|
| Reference to the host which has this tag assigned. | |
|
| Reference to the parent tag of this tag. | |
|
| Reference to the template which has this tag assigned. | |
|
| Reference to the user who has this tag assigned. | |
|
| Reference to the virtual machine which has this tag assigned. |
7.291. Template struct Copy linkLink copied to clipboard!
The type that represents a virtual machine template. Templates allow for a rapid instantiation of virtual machines with common configuration and disk states.
| Name | Type | Summary |
|---|---|---|
|
| Specifies if and how the auto CPU and NUMA configuration is applied. | |
|
| Reference to virtual machine’s BIOS configuration. | |
|
| Free text containing comments about this object. | |
|
| Console configured for this virtual machine. | |
|
| The configuration of the virtual machine CPU. | |
|
| Specifies if and how the CPU and NUMA configuration is applied. | |
|
| ||
|
| The virtual machine creation date. | |
|
| Virtual machine custom compatibility version. | |
|
| ||
|
| ||
|
| Properties sent to VDSM to configure various hooks. | |
|
|
If | |
|
| A human-readable description in plain text. | |
|
| The virtual machine display configuration. | |
|
| Domain configured for this virtual machine. | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to the virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| Reference to the storage domain this virtual machine/template lease reside on. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of a running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
|
If | |
|
| A human-readable name in plain text. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| The configuration of the virtual machine’s placement policy. | |
|
| Random Number Generator device configuration for this virtual machine. | |
|
| Virtual machine’s serial number in a cluster. | |
|
| Virtual machine’s small icon. | |
|
|
If | |
|
| Reference to the Single Sign On configuration this virtual machine is configured for. | |
|
|
If | |
|
|
If | |
|
| The status of the template. | |
|
| Determines how the virtual machine will be resumed after storage error. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
If | |
|
|
If | |
|
| Determines whether the virtual machine is optimized for desktop or server. | |
|
| Configuration of USB devices for this virtual machine (count, type). | |
|
| Indicates whether this is the base version or a sub-version of another template. | |
|
| Reference to VirtIO SCSI configuration. | |
|
| Number of queues for a Virtio-SCSI contoller this field requires virtioScsiMultiQueuesEnabled to be true see virtioScsiMultiQueuesEnabled for more info | |
|
|
If | |
|
| The virtual machine configuration associated with this template. |
7.291.1. auto_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the auto CPU and NUMA configuration is applied.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It might be removed in the future. Please use CpuPinningPolicy instead.
7.291.2. cpu Copy linkLink copied to clipboard!
The configuration of the virtual machine CPU.
The socket configuration can be updated without rebooting the virtual machine. The cores and the threads require a reboot.
For example, to change the number of sockets to 4 immediately, and the number of cores and threads to 2 after reboot, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body:
7.291.3. cpu_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the CPU and NUMA configuration is applied. When not specified the previous behavior of CPU pinning string will determine CpuPinningPolicy to None or Manual.
7.291.4. custom_compatibility_version Copy linkLink copied to clipboard!
Virtual machine custom compatibility version.
Enables a virtual machine to be customized to its own compatibility version. If custom_compatibility_version is set, it overrides the cluster’s compatibility version for this particular virtual machine.
The compatibility version of a virtual machine is limited by the data center the virtual machine resides in, and is checked against capabilities of the host the virtual machine is planned to run on.
7.291.5. high_availability Copy linkLink copied to clipboard!
The virtual machine high availability configuration. If set, the virtual machine will be automatically restarted when it unexpectedly goes down.
7.291.6. initialization Copy linkLink copied to clipboard!
Reference to the virtual machine’s initialization configuration.
Since Red Hat Virtualization 4.1.8 this property can be cleared by sending an empty tag.
For example, to clear the initialization attribute send a request like this:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body like this:
<vm> <initialization/> </vm>
<vm>
<initialization/>
</vm>
The response to such a request, and requests with the header All-Content: true will still contain this attribute.
7.291.7. large_icon Copy linkLink copied to clipboard!
Virtual machine’s large icon. Either set by user or refers to image set according to operating system.
7.291.8. lease Copy linkLink copied to clipboard!
Reference to the storage domain this virtual machine/template lease reside on.
A virtual machine running with a lease requires checking while running that the lease is not taken by another host, preventing another instance of this virtual machine from running on another host. This provides protection against split-brain in highly available virtual machines. A template can also have a storage domain defined for a lease in order to have the virtual machines created from this template to be preconfigured with this storage domain as the location of the leases.
7.291.9. memory Copy linkLink copied to clipboard!
The virtual machine’s memory, in bytes.
For example, to update a virtual machine to contain 1 Gibibyte (GiB) of memory, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With the following request body:
<vm> <memory>1073741824</memory> </vm>
<vm>
<memory>1073741824</memory>
</vm>
Memory hot plug is supported from Red Hat Virtualization 3.6 onwards. You can use the example above to increase memory while the virtual machine is in state up. The size increment must be dividable by the value of the HotPlugMemoryBlockSizeMb configuration value (256 MiB by default). If the memory size increment is not dividable by this value, the memory size change is only stored to next run configuration. Each successful memory hot plug operation creates one or two new memory devices.
Memory hot unplug is supported since Red Hat Virtualization 4.2 onwards. Memory hot unplug can only be performed when the virtual machine is in state up. Only previously hot plugged memory devices can be removed by the hot unplug operation. The requested memory decrement is rounded down to match sizes of a combination of previously hot plugged memory devices. The requested memory value is stored to next run configuration without rounding.
Memory in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
Red Hat Virtualization Manager internally rounds values down to whole MiBs (1MiB = 220 bytes)
7.291.10. migration Copy linkLink copied to clipboard!
Reference to configuration of migration of a running virtual machine to another host.
API for querying migration policy by ID returned by this method is not implemented yet. Use /ovirt-engine/api/options/MigrationPolicies to get a list of all migration policies with their IDs.
7.291.11. migration_downtime Copy linkLink copied to clipboard!
Maximum time the virtual machine can be non responsive during its live migration to another host in ms.
Set either explicitly for the virtual machine or by engine-config -s DefaultMaximumMigrationDowntime=[value]
7.291.12. origin Copy linkLink copied to clipboard!
The origin of this virtual machine.
Possible values:
-
ovirt -
rhev -
vmware -
xen -
external -
hosted_engine -
managed_hosted_engine -
kvm -
physical_machine -
hyperv
7.291.13. placement_policy Copy linkLink copied to clipboard!
The configuration of the virtual machine’s placement policy.
This configuration can be updated to pin a virtual machine to one or more hosts.
Virtual machines that are pinned to multiple hosts cannot be live migrated, but in the event of a host failure, any virtual machine configured to be highly available is automatically restarted on one of the other hosts to which the virtual machine is pinned.
For example, to pin a virtual machine to two hosts, send the following request:
PUT /api/vms/123
PUT /api/vms/123
With a request body like this:
7.291.14. small_icon Copy linkLink copied to clipboard!
Virtual machine’s small icon. Either set by user or refers to image set according to operating system.
7.291.15. sso Copy linkLink copied to clipboard!
Reference to the Single Sign On configuration this virtual machine is configured for. The user can be automatically signed in the virtual machine’s operating system when console is opened.
7.291.16. tpm_enabled Copy linkLink copied to clipboard!
If true, a TPM device is added to the virtual machine. By default the value is false. This property is only visible when fetching if "All-Content=true" header is set.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the CD-ROM devices attached to the template. | |
|
| Reference to cluster the virtual machine belongs to. | |
|
| Reference to CPU profile used by this virtual machine. | |
|
| Reference to the disks attached to the template. | |
|
| Reference to the graphic consoles attached to the template. | |
|
| Mediated devices configuration. | |
|
| Nic[] | Reference to the network interfaces attached to the template. |
|
| Reference to the user permissions attached to the template. | |
|
| Reference to quota configuration set for this virtual machine. | |
|
| Reference to storage domain the virtual machine belongs to. | |
|
| Tag[] | Reference to the tags attached to the template. |
|
| Reference to the watchdog devices attached to the template. |
7.292. TemplateStatus enum Copy linkLink copied to clipboard!
Type representing a status of a virtual machine template.
| Name | Summary |
|---|---|
|
| This status indicates that at least one of the disks of the template is illegal. |
|
| This status indicates that some operation that prevents other operations with the template is being executed. |
|
| This status indicates that the template is valid and ready for use. |
7.293. TemplateVersion struct Copy linkLink copied to clipboard!
Type representing a version of a virtual machine template.
| Name | Type | Summary |
|---|---|---|
|
| The name of this version. | |
|
| The index of this version in the versions hierarchy of the template. |
7.293.1. version_number Copy linkLink copied to clipboard!
The index of this version in the versions hierarchy of the template. The index 1 represents the original version of a template that is also called base version.
| Name | Type | Summary |
|---|---|---|
|
| References the template that this version is associated with. |
7.294. Ticket struct Copy linkLink copied to clipboard!
Type representing a ticket that allows virtual machine access.
7.295. TimeZone struct Copy linkLink copied to clipboard!
Time zone representation.
| Name | Type | Summary |
|---|---|---|
|
| Name of the time zone. | |
|
| UTC offset. |
7.295.1. utc_offset Copy linkLink copied to clipboard!
UTC offset.
Offset from UTC.
7.296. TpmSupport enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| TPM is required by the operating system |
|
| TPM is supported but optional |
|
|
7.297. TransparentHugePages struct Copy linkLink copied to clipboard!
Type representing a transparent huge pages (THP) support.
| Name | Type | Summary |
|---|---|---|
|
| Enable THP support. |
7.298. TransportType enum Copy linkLink copied to clipboard!
Protocol used to access a Gluster volume.
| Name | Summary |
|---|---|
|
| Remote direct memory access. |
|
| TCP. |
7.299. UnmanagedNetwork struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
7.300. Usb struct Copy linkLink copied to clipboard!
Configuration of the USB device of a virtual machine.
7.301. UsbType enum Copy linkLink copied to clipboard!
Type of USB device redirection.
| Name | Summary |
|---|---|
|
| Legacy USB redirection. |
|
| Native USB redirection. |
7.301.1. legacy Copy linkLink copied to clipboard!
Legacy USB redirection.
This USB type has been deprecated since version 3.6 of the engine, and has been completely removed in version 4.1. It is preserved only to avoid syntax errors in existing scripts. If it is used it will be automatically replaced by native.
7.301.2. native Copy linkLink copied to clipboard!
Native USB redirection.
Native USB redirection allows KVM/SPICE USB redirection for Linux and Windows virtual machines. Virtual (guest) machines require no guest-installed agents or drivers for native USB. On Linux clients, all packages required for USB redirection are provided by the virt-viewer package. On Windows clients, you must also install the usbdk package.
7.302. User struct Copy linkLink copied to clipboard!
Represents a user in the system.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| ||
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| Namespace where the user resides. | |
|
| ||
|
|
Similar to | |
|
| The user’s username. | |
|
| User options allow you to save key/value properties which are used to customize the settings per individual user. |
7.302.1. namespace Copy linkLink copied to clipboard!
Namespace where the user resides. When using the authorization provider that stores users in the LDAP server, this attribute equals the naming context of the LDAP server. See oVirt Engine Extension AAA LDAP for more information. When using the built-in authorization provider that stores users in the database this attribute is ignored. See oVirt Engine extension - AAA - JDBC for more information.
7.302.2. principal Copy linkLink copied to clipboard!
Similar to user_name. The format depends on the LDAP provider. With most LDAP providers it is the value of the uid LDAP attribute. In the case of Active Directory it is the User Principal Name (UPN).
7.302.3. user_name Copy linkLink copied to clipboard!
The user’s username. The format depends on authorization provider type. In most LDAP providers it is the value of the uid LDAP attribute. In Active Directory it is the User Principal Name (UPN). UPN or uid must be followed by the authorization provider name. For example, in the case of LDAP’s uid attribute it is: myuser@myextension-authz. In the case of Active Directory using UPN it is: myuser@mysubdomain.mydomain.com@myextension-authz. This attribute is a required parameter when adding a new user.
7.302.4. user_options Copy linkLink copied to clipboard!
User options allow you to save key/value properties which are used to customize the settings per individual user. Note that since version 4.4.5 this property is deprecated and preserved only for backwards compatibility. It will be removed in the future. Please use the options endpoint instead.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| A link to the roles sub-collection for user resources. | |
|
| ||
|
| Tag[] | A link to the tags sub-collection for user resources. |
7.303. UserOption struct Copy linkLink copied to clipboard!
User options allow you to save key/value properties which are used to customize the settings per individual user.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| JSON content encoded as string. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
7.303.1. content Copy linkLink copied to clipboard!
JSON content encoded as string. Any valid JSON is supported.
| Name | Type | Summary |
|---|---|---|
|
|
7.304. Value struct Copy linkLink copied to clipboard!
7.305. ValueType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.306. VcpuPin struct Copy linkLink copied to clipboard!
7.307. Vendor struct Copy linkLink copied to clipboard!
7.308. Version struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
|
7.309. VgpuPlacement enum Copy linkLink copied to clipboard!
The vGPU placement strategy.
It can either put vGPUs on the first available physical cards, or spread them over multiple physical cards.
| Name | Summary |
|---|---|
|
| Use consolidated placement. |
|
| Use separated placement. |
7.309.1. consolidated Copy linkLink copied to clipboard!
Use consolidated placement. Each vGPU is placed on the first physical card with available space.
This is the default placement, utilizing all available space on the physical cards.
7.309.2. separated Copy linkLink copied to clipboard!
Use separated placement. Each vGPU is placed on a separate physical card, if possible.
This can be useful for improving vGPU performance.
7.310. VirtioScsi struct Copy linkLink copied to clipboard!
Type representing the support of virtio-SCSI. If it supported we use virtio driver for SCSI guest device.
| Name | Type | Summary |
|---|---|---|
|
| Enable Virtio SCSI support. |
7.311. VirtualNumaNode struct Copy linkLink copied to clipboard!
Represents the virtual NUMA node.
An example XML representation:
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| ||
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| ||
|
| Memory of the NUMA node in MB. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| How the NUMA topology is applied. |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Each host NUMA node resource exposes a statistics sub-collection for host NUMA node specific statistics. | |
|
|
7.311.1. statistics Copy linkLink copied to clipboard!
Each host NUMA node resource exposes a statistics sub-collection for host NUMA node specific statistics.
An example of an XML representation:
This statistics sub-collection is read-only.
The following list shows the statistic types for a host NUMA node:
| Name | Description |
|---|---|
|
| Total memory in bytes on the NUMA node. |
|
| Memory in bytes used on the NUMA node. |
|
| Memory in bytes free on the NUMA node. |
|
| Percentage of CPU usage for user slice. |
|
| Percentage of CPU usage for system. |
|
| Percentage of idle CPU usage. |
7.312. Vlan struct Copy linkLink copied to clipboard!
Type representing a Virtual LAN (VLAN) type.
| Name | Type | Summary |
|---|---|---|
|
| Virtual LAN ID. |
7.313. Vm struct Copy linkLink copied to clipboard!
Represents a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| Specifies if and how the auto CPU and NUMA configuration is applied. | |
|
| Reference to virtual machine’s BIOS configuration. | |
|
| Free text containing comments about this object. | |
|
| Console configured for this virtual machine. | |
|
| The configuration of the virtual machine CPU. | |
|
| Specifies if and how the CPU and NUMA configuration is applied. | |
|
| ||
|
| The virtual machine creation date. | |
|
| Virtual machine custom compatibility version. | |
|
| ||
|
| ||
|
| Properties sent to VDSM to configure various hooks. | |
|
|
If | |
|
| A human-readable description in plain text. | |
|
| The virtual machine display configuration. | |
|
| Domain configured for this virtual machine. | |
|
| Fully qualified domain name of the virtual machine. | |
|
| What operating system is installed on the virtual machine. | |
|
| What time zone is used by the virtual machine (as returned by guest agent). | |
|
|
Indicates whether the virtual machine has snapshots with disks in | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to the virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| Reference to the storage domain this virtual machine/template lease reside on. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of a running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
|
If | |
|
| A human-readable name in plain text. | |
|
| Virtual machine configuration has been changed and requires restart of the virtual machine. | |
|
| How the NUMA topology is applied. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| Optional payloads of the virtual machine, used for ISOs to configure it. | |
|
| The configuration of the virtual machine’s placement policy. | |
|
| Random Number Generator device configuration for this virtual machine. | |
|
|
If | |
|
| Virtual machine’s serial number in a cluster. | |
|
| Virtual machine’s small icon. | |
|
|
If | |
|
| Reference to the Single Sign On configuration this virtual machine is configured for. | |
|
|
If | |
|
| The date in which the virtual machine was started. | |
|
|
If | |
|
| The current status of the virtual machine. | |
|
| Human readable detail of current status. | |
|
| The reason the virtual machine was stopped. | |
|
| The date in which the virtual machine was stopped. | |
|
| Determines how the virtual machine will be resumed after storage error. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
If | |
|
|
If | |
|
| Determines whether the virtual machine is optimized for desktop or server. | |
|
| Configuration of USB devices for this virtual machine (count, type). | |
|
|
If | |
|
| Reference to VirtIO SCSI configuration. | |
|
| Number of queues for a Virtio-SCSI contoller this field requires virtioScsiMultiQueuesEnabled to be true see virtioScsiMultiQueuesEnabled for more info | |
|
|
If |
7.313.1. auto_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the auto CPU and NUMA configuration is applied.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It might be removed in the future. Please use CpuPinningPolicy instead.
7.313.2. cpu Copy linkLink copied to clipboard!
The configuration of the virtual machine CPU.
The socket configuration can be updated without rebooting the virtual machine. The cores and the threads require a reboot.
For example, to change the number of sockets to 4 immediately, and the number of cores and threads to 2 after reboot, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body:
7.313.3. cpu_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the CPU and NUMA configuration is applied. When not specified the previous behavior of CPU pinning string will determine CpuPinningPolicy to None or Manual.
7.313.4. custom_compatibility_version Copy linkLink copied to clipboard!
Virtual machine custom compatibility version.
Enables a virtual machine to be customized to its own compatibility version. If custom_compatibility_version is set, it overrides the cluster’s compatibility version for this particular virtual machine.
The compatibility version of a virtual machine is limited by the data center the virtual machine resides in, and is checked against capabilities of the host the virtual machine is planned to run on.
7.313.5. high_availability Copy linkLink copied to clipboard!
The virtual machine high availability configuration. If set, the virtual machine will be automatically restarted when it unexpectedly goes down.
7.313.6. initialization Copy linkLink copied to clipboard!
Reference to the virtual machine’s initialization configuration.
Since Red Hat Virtualization 4.1.8 this property can be cleared by sending an empty tag.
For example, to clear the initialization attribute send a request like this:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body like this:
<vm> <initialization/> </vm>
<vm>
<initialization/>
</vm>
The response to such a request, and requests with the header All-Content: true will still contain this attribute.
7.313.7. large_icon Copy linkLink copied to clipboard!
Virtual machine’s large icon. Either set by user or refers to image set according to operating system.
7.313.8. lease Copy linkLink copied to clipboard!
Reference to the storage domain this virtual machine/template lease reside on.
A virtual machine running with a lease requires checking while running that the lease is not taken by another host, preventing another instance of this virtual machine from running on another host. This provides protection against split-brain in highly available virtual machines. A template can also have a storage domain defined for a lease in order to have the virtual machines created from this template to be preconfigured with this storage domain as the location of the leases.
7.313.9. memory Copy linkLink copied to clipboard!
The virtual machine’s memory, in bytes.
For example, to update a virtual machine to contain 1 Gibibyte (GiB) of memory, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With the following request body:
<vm> <memory>1073741824</memory> </vm>
<vm>
<memory>1073741824</memory>
</vm>
Memory hot plug is supported from Red Hat Virtualization 3.6 onwards. You can use the example above to increase memory while the virtual machine is in state up. The size increment must be dividable by the value of the HotPlugMemoryBlockSizeMb configuration value (256 MiB by default). If the memory size increment is not dividable by this value, the memory size change is only stored to next run configuration. Each successful memory hot plug operation creates one or two new memory devices.
Memory hot unplug is supported since Red Hat Virtualization 4.2 onwards. Memory hot unplug can only be performed when the virtual machine is in state up. Only previously hot plugged memory devices can be removed by the hot unplug operation. The requested memory decrement is rounded down to match sizes of a combination of previously hot plugged memory devices. The requested memory value is stored to next run configuration without rounding.
Memory in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
Red Hat Virtualization Manager internally rounds values down to whole MiBs (1MiB = 220 bytes)
7.313.10. migration Copy linkLink copied to clipboard!
Reference to configuration of migration of a running virtual machine to another host.
API for querying migration policy by ID returned by this method is not implemented yet. Use /ovirt-engine/api/options/MigrationPolicies to get a list of all migration policies with their IDs.
7.313.11. migration_downtime Copy linkLink copied to clipboard!
Maximum time the virtual machine can be non responsive during its live migration to another host in ms.
Set either explicitly for the virtual machine or by engine-config -s DefaultMaximumMigrationDowntime=[value]
7.313.12. next_run_configuration_exists Copy linkLink copied to clipboard!
Virtual machine configuration has been changed and requires restart of the virtual machine. Changed configuration is applied at processing the virtual machine’s shut down.
7.313.13. numa_tune_mode Copy linkLink copied to clipboard!
How the NUMA topology is applied. Deprecated in favor of NUMA tune per vNUMA node.
7.313.14. origin Copy linkLink copied to clipboard!
The origin of this virtual machine.
Possible values:
-
ovirt -
rhev -
vmware -
xen -
external -
hosted_engine -
managed_hosted_engine -
kvm -
physical_machine -
hyperv
7.313.15. placement_policy Copy linkLink copied to clipboard!
The configuration of the virtual machine’s placement policy.
This configuration can be updated to pin a virtual machine to one or more hosts.
Virtual machines that are pinned to multiple hosts cannot be live migrated, but in the event of a host failure, any virtual machine configured to be highly available is automatically restarted on one of the other hosts to which the virtual machine is pinned.
For example, to pin a virtual machine to two hosts, send the following request:
PUT /api/vms/123
PUT /api/vms/123
With a request body like this:
7.313.16. small_icon Copy linkLink copied to clipboard!
Virtual machine’s small icon. Either set by user or refers to image set according to operating system.
7.313.17. sso Copy linkLink copied to clipboard!
Reference to the Single Sign On configuration this virtual machine is configured for. The user can be automatically signed in the virtual machine’s operating system when console is opened.
7.313.18. stop_reason Copy linkLink copied to clipboard!
The reason the virtual machine was stopped. Optionally set by user when shutting down the virtual machine.
7.313.19. tpm_enabled Copy linkLink copied to clipboard!
If true, a TPM device is added to the virtual machine. By default the value is false. This property is only visible when fetching if "All-Content=true" header is set.
| Name | Type | Summary |
|---|---|---|
|
| Optional. | |
|
| List of applications installed on the virtual machine. | |
|
| Reference to the ISO mounted to the CDROM. | |
|
| Reference to cluster the virtual machine belongs to. | |
|
| Reference to CPU profile used by this virtual machine. | |
|
| References the disks attached to the virtual machine. | |
|
| The dynamic configuration of the virtual machine CPU. | |
|
| ||
|
| Reference to the ISO mounted to the floppy. | |
|
| List of graphics consoles configured for this virtual machine. | |
|
| Reference to the host the virtual machine is running on. | |
|
| References devices associated to this virtual machine. | |
|
| The virtual machine configuration can be optionally predefined via one of the instance types. | |
|
| Lists all the Katello errata assigned to the virtual machine. | |
|
| Mediated devices configuration. | |
|
| Nic[] | References the list of network interface devices on the virtual machine. |
|
| Refers to the NUMA Nodes configuration used by this virtual machine. | |
|
| References the original template used to create the virtual machine. | |
|
| Permissions set for this virtual machine. | |
|
| Reference to quota configuration set for this virtual machine. | |
|
| ||
|
| List of user sessions opened for this virtual machine. | |
|
| Refers to all snapshots taken from the virtual machine. | |
|
| Statistics data collected from this virtual machine. | |
|
| Reference to storage domain the virtual machine belongs to. | |
|
| Tag[] | |
|
| Reference to the template the virtual machine is based on. | |
|
| Reference to the pool the virtual machine is optionally member of. | |
|
| Refers to the Watchdog configuration. |
7.313.20. affinity_labels Copy linkLink copied to clipboard!
Optional. Used for labeling of sub-clusters.
7.313.21. katello_errata Copy linkLink copied to clipboard!
Lists all the Katello errata assigned to the virtual machine.
GET /ovirt-engine/api/vms/123/katelloerrata
GET /ovirt-engine/api/vms/123/katelloerrata
You will receive response in XML like this one:
7.313.22. original_template Copy linkLink copied to clipboard!
References the original template used to create the virtual machine.
If the virtual machine is cloned from a template or another virtual machine, the template links to the Blank template, and the original_template is used to track history.
Otherwise the template and original_template are the same.
7.313.23. statistics Copy linkLink copied to clipboard!
Statistics data collected from this virtual machine.
Note that some statistics, notably memory.buffered and memory.cached are available only when Red Hat Virtualization guest agent is installed in the virtual machine.
7.314. VmAffinity enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
7.315. VmBase struct Copy linkLink copied to clipboard!
Represents basic virtual machine configuration. This is used by virtual machines, templates and instance types.
| Name | Type | Summary |
|---|---|---|
|
| Specifies if and how the auto CPU and NUMA configuration is applied. | |
|
| Reference to virtual machine’s BIOS configuration. | |
|
| Free text containing comments about this object. | |
|
| Console configured for this virtual machine. | |
|
| The configuration of the virtual machine CPU. | |
|
| Specifies if and how the CPU and NUMA configuration is applied. | |
|
| ||
|
| The virtual machine creation date. | |
|
| Virtual machine custom compatibility version. | |
|
| ||
|
| ||
|
| Properties sent to VDSM to configure various hooks. | |
|
|
If | |
|
| A human-readable description in plain text. | |
|
| The virtual machine display configuration. | |
|
| Domain configured for this virtual machine. | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to the virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| Reference to the storage domain this virtual machine/template lease reside on. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of a running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
|
If | |
|
| A human-readable name in plain text. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| The configuration of the virtual machine’s placement policy. | |
|
| Random Number Generator device configuration for this virtual machine. | |
|
| Virtual machine’s serial number in a cluster. | |
|
| Virtual machine’s small icon. | |
|
|
If | |
|
| Reference to the Single Sign On configuration this virtual machine is configured for. | |
|
|
If | |
|
|
If | |
|
| Determines how the virtual machine will be resumed after storage error. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
If | |
|
|
If | |
|
| Determines whether the virtual machine is optimized for desktop or server. | |
|
| Configuration of USB devices for this virtual machine (count, type). | |
|
| Reference to VirtIO SCSI configuration. | |
|
| Number of queues for a Virtio-SCSI contoller this field requires virtioScsiMultiQueuesEnabled to be true see virtioScsiMultiQueuesEnabled for more info | |
|
|
If |
7.315.1. auto_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the auto CPU and NUMA configuration is applied.
Since version 4.5 of the engine this operation is deprecated, and preserved only for backwards compatibility. It might be removed in the future. Please use CpuPinningPolicy instead.
7.315.2. cpu Copy linkLink copied to clipboard!
The configuration of the virtual machine CPU.
The socket configuration can be updated without rebooting the virtual machine. The cores and the threads require a reboot.
For example, to change the number of sockets to 4 immediately, and the number of cores and threads to 2 after reboot, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body:
7.315.3. cpu_pinning_policy Copy linkLink copied to clipboard!
Specifies if and how the CPU and NUMA configuration is applied. When not specified the previous behavior of CPU pinning string will determine CpuPinningPolicy to None or Manual.
7.315.4. custom_compatibility_version Copy linkLink copied to clipboard!
Virtual machine custom compatibility version.
Enables a virtual machine to be customized to its own compatibility version. If custom_compatibility_version is set, it overrides the cluster’s compatibility version for this particular virtual machine.
The compatibility version of a virtual machine is limited by the data center the virtual machine resides in, and is checked against capabilities of the host the virtual machine is planned to run on.
7.315.5. high_availability Copy linkLink copied to clipboard!
The virtual machine high availability configuration. If set, the virtual machine will be automatically restarted when it unexpectedly goes down.
7.315.6. initialization Copy linkLink copied to clipboard!
Reference to the virtual machine’s initialization configuration.
Since Red Hat Virtualization 4.1.8 this property can be cleared by sending an empty tag.
For example, to clear the initialization attribute send a request like this:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With a request body like this:
<vm> <initialization/> </vm>
<vm>
<initialization/>
</vm>
The response to such a request, and requests with the header All-Content: true will still contain this attribute.
7.315.7. large_icon Copy linkLink copied to clipboard!
Virtual machine’s large icon. Either set by user or refers to image set according to operating system.
7.315.8. lease Copy linkLink copied to clipboard!
Reference to the storage domain this virtual machine/template lease reside on.
A virtual machine running with a lease requires checking while running that the lease is not taken by another host, preventing another instance of this virtual machine from running on another host. This provides protection against split-brain in highly available virtual machines. A template can also have a storage domain defined for a lease in order to have the virtual machines created from this template to be preconfigured with this storage domain as the location of the leases.
7.315.9. memory Copy linkLink copied to clipboard!
The virtual machine’s memory, in bytes.
For example, to update a virtual machine to contain 1 Gibibyte (GiB) of memory, send the following request:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
With the following request body:
<vm> <memory>1073741824</memory> </vm>
<vm>
<memory>1073741824</memory>
</vm>
Memory hot plug is supported from Red Hat Virtualization 3.6 onwards. You can use the example above to increase memory while the virtual machine is in state up. The size increment must be dividable by the value of the HotPlugMemoryBlockSizeMb configuration value (256 MiB by default). If the memory size increment is not dividable by this value, the memory size change is only stored to next run configuration. Each successful memory hot plug operation creates one or two new memory devices.
Memory hot unplug is supported since Red Hat Virtualization 4.2 onwards. Memory hot unplug can only be performed when the virtual machine is in state up. Only previously hot plugged memory devices can be removed by the hot unplug operation. The requested memory decrement is rounded down to match sizes of a combination of previously hot plugged memory devices. The requested memory value is stored to next run configuration without rounding.
Memory in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
Red Hat Virtualization Manager internally rounds values down to whole MiBs (1MiB = 220 bytes)
7.315.10. migration Copy linkLink copied to clipboard!
Reference to configuration of migration of a running virtual machine to another host.
API for querying migration policy by ID returned by this method is not implemented yet. Use /ovirt-engine/api/options/MigrationPolicies to get a list of all migration policies with their IDs.
7.315.11. migration_downtime Copy linkLink copied to clipboard!
Maximum time the virtual machine can be non responsive during its live migration to another host in ms.
Set either explicitly for the virtual machine or by engine-config -s DefaultMaximumMigrationDowntime=[value]
7.315.12. origin Copy linkLink copied to clipboard!
The origin of this virtual machine.
Possible values:
-
ovirt -
rhev -
vmware -
xen -
external -
hosted_engine -
managed_hosted_engine -
kvm -
physical_machine -
hyperv
7.315.13. placement_policy Copy linkLink copied to clipboard!
The configuration of the virtual machine’s placement policy.
This configuration can be updated to pin a virtual machine to one or more hosts.
Virtual machines that are pinned to multiple hosts cannot be live migrated, but in the event of a host failure, any virtual machine configured to be highly available is automatically restarted on one of the other hosts to which the virtual machine is pinned.
For example, to pin a virtual machine to two hosts, send the following request:
PUT /api/vms/123
PUT /api/vms/123
With a request body like this:
7.315.14. small_icon Copy linkLink copied to clipboard!
Virtual machine’s small icon. Either set by user or refers to image set according to operating system.
7.315.15. sso Copy linkLink copied to clipboard!
Reference to the Single Sign On configuration this virtual machine is configured for. The user can be automatically signed in the virtual machine’s operating system when console is opened.
7.315.16. tpm_enabled Copy linkLink copied to clipboard!
If true, a TPM device is added to the virtual machine. By default the value is false. This property is only visible when fetching if "All-Content=true" header is set.
| Name | Type | Summary |
|---|---|---|
|
| Reference to cluster the virtual machine belongs to. | |
|
| Reference to CPU profile used by this virtual machine. | |
|
| Reference to quota configuration set for this virtual machine. | |
|
| Reference to storage domain the virtual machine belongs to. |
7.316. VmDeviceType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
7.317. VmMediatedDevice struct Copy linkLink copied to clipboard!
VM mediated device is a fake device specifying properties of vGPU mediated devices. It is not an actual device, it just serves as a specification how to configure a part of a host device.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
| Properties of the device. |
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.317.1. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.318. VmPlacementPolicy struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
| Name | Type | Summary |
|---|---|---|
|
|
7.319. VmPool struct Copy linkLink copied to clipboard!
Type representing a virtual machines pool.
| Name | Type | Summary |
|---|---|---|
|
| Indicates if the pool should automatically distribute the disks of the virtual machines across the multiple storage domains where the template is copied. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The display settings configured for virtual machines in the pool. | |
|
| A unique identifier. | |
|
| The maximum number of virtual machines in the pool that could be assigned to a particular user. | |
|
| A human-readable name in plain text. | |
|
| The system attempts to prestart the specified number of virtual machines from the pool. | |
|
| The random number generator device configured for virtual machines in the pool. | |
|
| The number of virtual machines in the pool. | |
|
| Indicates if sound card should be configured for virtual machines in the pool. | |
|
| Virtual machine pool’s stateful flag. | |
|
|
If | |
|
| The deallocation policy of virtual machines in the pool. | |
|
| Indicates if virtual machines in the pool are updated to newer versions of the template the pool is based on. |
7.319.1. auto_storage_select Copy linkLink copied to clipboard!
Indicates if the pool should automatically distribute the disks of the virtual machines across the multiple storage domains where the template is copied.
When the template used by the pool is present in multiple storage domains, the disks of the virtual machines of the pool will be created in one of those storage domains. By default, or when the value of this attribute is false, that storage domain is selected when the pool is created, and all virtual machines will use the same. If this attribute is true, then, when a virtual machine is added to the pool, the storage domain that has more free space is selected.
7.319.2. display Copy linkLink copied to clipboard!
The display settings configured for virtual machines in the pool.
Please note that this attribute is not working and is now deprecated. Please use Vm.display instead.
7.319.3. prestarted_vms Copy linkLink copied to clipboard!
The system attempts to prestart the specified number of virtual machines from the pool.
These virtual machines are started without being attached to any user. That way, users can acquire virtual machines from the pool faster.
7.319.4. stateful Copy linkLink copied to clipboard!
Virtual machine pool’s stateful flag.
Virtual machines from a stateful virtual machine pool are always started in stateful mode (stateless snapshot is not created). The state of the virtual machine is preserved even when the virtual machine is passed to a different user.
7.319.5. tpm_enabled Copy linkLink copied to clipboard!
If true, a TPM device is added to the virtual machine. By default the value is false. This property is only visible when fetching if "All-Content=true" header is set.
| Name | Type | Summary |
|---|---|---|
|
| Reference to the cluster the pool resides in. | |
|
| Reference to the instance type on which this pool is based. | |
|
| Permissions set for this virtual machine pool. | |
|
| Reference to the template the pool is based on. | |
|
| Reference to an arbitrary virtual machine that is part of the pool. |
7.319.6. instance_type Copy linkLink copied to clipboard!
Reference to the instance type on which this pool is based. It can be set only on pool creation and cannot be edited.
7.319.7. vm Copy linkLink copied to clipboard!
Reference to an arbitrary virtual machine that is part of the pool.
Note that this virtual machine may not be based to the latest version of the pool’s template.
7.320. VmPoolType enum Copy linkLink copied to clipboard!
Type representing the deallocation policy of virtual machines in a virtual machines pool.
| Name | Summary |
|---|---|
|
| This policy indicates that virtual machines in the pool are automcatically deallocated by the system. |
|
| This policy indicates that virtual machines in the pool are deallocated manually by the administrator. |
7.320.1. automatic Copy linkLink copied to clipboard!
This policy indicates that virtual machines in the pool are automcatically deallocated by the system.
With this policy, when a virtual machine that is part of the pool and is assigned to a user is shut-down, it is detached from the user, its state is restored to the pool’s default state, and the virtual machine returns to pool (i.e., the virtual machine can then be assigned to another user).
7.320.2. manual Copy linkLink copied to clipboard!
This policy indicates that virtual machines in the pool are deallocated manually by the administrator.
With this policy, a virtual machine that is part of the pool remains assigned to its user and preserves its state on shut-down. In order to return the virtual machine back to the pool, the administrator needs to deallocate it explicitly by removing the user’s permissions on that virtual machine.
7.321. VmStatus enum Copy linkLink copied to clipboard!
Type representing a status of a virtual machine.
| Name | Summary |
|---|---|
|
| This status indicates that the virtual machine process is not running. |
|
| This status indicates that the virtual machine process is not running and there is some operation on the disks of the virtual machine that prevents it from being started. |
|
| This status indicates that the virtual machine process is running and the virtual machine is being migrated from one host to another. |
|
| This status indicates that the hypervisor detected that the virtual machine is not responding. |
|
| This status indicates that the virtual machine process is running and the virtual machine is paused. |
|
| This status indicates that the virtual machine process is running and it is about to stop running. |
|
| This status indicates that the virtual machine process is running and the guest operating system is being loaded. |
|
| This status indicates that the virtual machine process is running and the guest operating system is being rebooted. |
|
| This status indicates that the virtual machine process is about to run and the virtual machine is going to awake from hibernation. |
|
| This status indicates that the virtual machine process is running and the virtual machine is being hibernated. |
|
| This status indicates that the virtual machine process is not running and a running state of the virtual machine was saved. |
|
| This status is set when an invalid status is received. |
|
| This status indicates that the system failed to determine the status of the virtual machine. |
|
| This status indicates that the virtual machine process is running and the guest operating system is loaded. |
|
| This status indicates that the virtual machine process is about to run. |
7.321.1. paused Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is running and the virtual machine is paused. This may happen in two cases: when running a virtual machine is paused mode and when the virtual machine is being automatically paused due to an error.
7.321.2. powering_up Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is running and the guest operating system is being loaded. Note that if no guest-agent is installed, this status is set for a predefined period of time, that is by default 60 seconds, when running a virtual machine.
7.321.3. restoring_state Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is about to run and the virtual machine is going to awake from hibernation. In this status, the running state of the virtual machine is being restored.
7.321.4. saving_state Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is running and the virtual machine is being hibernated. In this status, the running state of the virtual machine is being saved. Note that this status does not mean that the guest operating system is being hibernated.
7.321.5. suspended Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is not running and a running state of the virtual machine was saved. This status is similar to Down, but when the VM is started in this status its saved running state is restored instead of being booted using the normal procedue.
7.321.6. unknown Copy linkLink copied to clipboard!
This status indicates that the system failed to determine the status of the virtual machine. The virtual machine process may be running or not running in this status. For instance, when host becomes non-responsive the virtual machines that ran on it are set with this status.
7.321.7. up Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is running and the guest operating system is loaded. Note that if no guest-agent is installed, this status is set after a predefined period of time, that is by default 60 seconds, when running a virtual machine.
7.321.8. wait_for_launch Copy linkLink copied to clipboard!
This status indicates that the virtual machine process is about to run. This status is set when a request to run a virtual machine arrives to the host. It is possible that the virtual machine process will fail to run.
7.322. VmStorageErrorResumeBehaviour enum Copy linkLink copied to clipboard!
If the storage, on which this virtual machine has some disks gets unresponsive, the virtual machine gets paused.
This are the possible options, what should happen with the virtual machine in the moment the storage gets available again.
| Name | Summary |
|---|---|
|
| The virtual machine gets resumed automatically in the moment the storage is available again. |
|
| The virtual machine will be killed after a timeout (configurable on the hypervisor). |
|
| Do nothing with the virtual machine. |
7.322.1. auto_resume Copy linkLink copied to clipboard!
The virtual machine gets resumed automatically in the moment the storage is available again.
This is the only behavior available before 4.2.
7.322.2. kill Copy linkLink copied to clipboard!
The virtual machine will be killed after a timeout (configurable on the hypervisor).
This is the only option supported for highly available virtual machines with leases. The reason is that the highly available virtual machine is restarted using the infrastructure and any kind of resume risks split brains.
7.322.3. leave_paused Copy linkLink copied to clipboard!
Do nothing with the virtual machine.
Useful if there is a custom failover implemented and the user does not want the virtual machine to get resumed.
7.323. VmSummary struct Copy linkLink copied to clipboard!
Type containing information related to virtual machines on a particular host.
7.324. VmType enum Copy linkLink copied to clipboard!
Type representing what the virtual machine is optimized for.
| Name | Summary |
|---|---|
|
| The virtual machine is intended to be used as a desktop. |
|
| The virtual machine is intended to be used as a high performance virtual machine. |
|
| The virtual machine is intended to be used as a server. |
7.324.1. desktop Copy linkLink copied to clipboard!
The virtual machine is intended to be used as a desktop.
Currently, its implication is that a sound device will automatically be added to the virtual machine.
7.324.2. high_performance Copy linkLink copied to clipboard!
The virtual machine is intended to be used as a high performance virtual machine.
Currently, its implication is that the virtual machine configuration will automatically be set for running with the highest possible performance, and with performance metrics as close to bare metal as possible.
Some of the recommended configuration settings for the highest possible performance cannot be set automatically; manually setting them before running the virtual machine is recommended.
The following configuration changes are set automatically:
- Enable headless mode.
- Enable serial console.
- Enable pass-through host CPU.
- Enable I/O threads.
- Enable I/O threads pinning and set the pinning topology.
- Enable the paravirtualized random number generator PCI (virtio-rng) device.
- Disable all USB devices.
- Disable the soundcard device.
- Disable the smartcard device.
- Disable the memory balloon device.
- Disable the watchdog device.
- Disable migration.
- Disable high availability.
The following recommended configuration changes have to be set manually by the user:
- Enable CPU pinning topology.
- Enable non-uniform memory access (NUMA) pinning topology.
- Enable and set huge pages configuration.
- Disable kernel same-page merging (KSM).
7.324.3. server Copy linkLink copied to clipboard!
The virtual machine is intended to be used as a server.
Currently, its implication is that a sound device will not automatically be added to the virtual machine.
7.325. VnicPassThrough struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Defines whether the vNIC will be implemented as a virtual device, or as a pass-through to a host device. |
7.326. VnicPassThroughMode enum Copy linkLink copied to clipboard!
Describes whether the vNIC is to be implemented as a pass-through device or a virtual one.
| Name | Summary |
|---|---|
|
| To be implemented as a virtual device. |
|
| To be implemented as a pass-through device. |
7.327. VnicProfile struct Copy linkLink copied to clipboard!
A vNIC profile is a collection of settings that can be applied to individual NIC.
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| Custom properties applied to the vNIC profile. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
|
Marks whether | |
|
| A human-readable name in plain text. | |
|
| Enables passthrough to an SR-IOV-enabled host NIC. | |
|
| Enables port mirroring. |
7.327.1. migratable Copy linkLink copied to clipboard!
Marks whether pass_through NIC is migratable or not.
If pass_through.mode is set to disabled this option has no meaning, and it will be considered to be true. If you omit this option from a request, by default, this will be set to true.
When migrating a virtual machine, this virtual machine will be migrated only if all pass_through NICs are flagged as migratable.
7.327.2. pass_through Copy linkLink copied to clipboard!
Enables passthrough to an SR-IOV-enabled host NIC.
A vNIC profile enables a NIC to be directly connected to a virtual function (VF) of an SR-IOV-enabled host NIC, if passthrough is enabled. The NIC will then bypass the software network virtualization and connect directly to the VF for direct device assignment.
Passthrough cannot be enabled if the vNIC profile is already attached to a NIC. If a vNIC profile has passthrough enabled, qos and port_mirroring are disabled for the vNIC profile.
7.327.3. port_mirroring Copy linkLink copied to clipboard!
Enables port mirroring.
Port mirroring copies layer 3 network traffic on a given logical network and host to a NIC on a virtual machine. This virtual machine can be used for network debugging and tuning, intrusion detection, and monitoring the behavior of other virtual machines on the same host and logical network. The only traffic copied is internal to one logical network on one host. There is no increase in traffic on the network external to the host; however a virtual machine with port mirroring enabled uses more host CPU and RAM than other virtual machines.
Port mirroring has the following limitations:
- Hot linking a NIC with a vNIC profile that has port mirroring enabled is not supported.
- Port mirroring cannot be altered when the vNIC profile is attached to a virtual machine.
Given the above limitations, it is recommended that you enable port mirroring on an additional, dedicated vNIC profile.
Enabling port mirroring reduces the privacy of other network users.
| Name | Type | Summary |
|---|---|---|
|
| Failover vNIC profile for SR-IOV migration without downtime | |
|
| Reference to the network that the vNIC profile is applied to. | |
|
| Reference to the top-level network filter that applies to the NICs that use this profile. | |
|
| Permissions to allow usage of the vNIC profile. | |
|
| Reference to the quality of service attributes to apply to the vNIC profile. |
7.327.4. network_filter Copy linkLink copied to clipboard!
Reference to the top-level network filter that applies to the NICs that use this profile.
Network filters enhance the ability to manage the network packets traffic to and from virtual machines. The network filter may either contain a reference to other filters, rules for traffic filtering, or a combination of both.
7.327.5. qos Copy linkLink copied to clipboard!
Reference to the quality of service attributes to apply to the vNIC profile.
Quality of Service attributes regulate inbound and outbound network traffic of the NIC.
7.328. VnicProfileMapping struct Copy linkLink copied to clipboard!
Deprecated type that maps an external virtual NIC profile to one that exists in the Red Hat Virtualization Manager.
If, for example, the desired virtual NIC profile’s mapping includes the following two lines:
| Source network name | Source network profile name | Target virtual NIC profile ID |
|---|---|---|
|
|
|
|
|
|
|
|
The following form is deprecated since 4.2.1 and will be removed in the future:
| Name | Type | Summary |
|---|---|---|
|
| Deprecated attribute describing the name of the external network. | |
|
| Deprecated attribute describing the name of the external network profile. |
7.328.1. source_network_name Copy linkLink copied to clipboard!
Deprecated attribute describing the name of the external network.
Please note that this attribute has been deprecated since version 4.2.1 of the engine, and preserved only for backward compatibility. It will be removed in the future.
7.328.2. source_network_profile_name Copy linkLink copied to clipboard!
Deprecated attribute describing the name of the external network profile.
Please note that this attribute has been deprecated since version 4.2.1 of the engine, and preserved only for backward compatibility. It will be removed in the future.
| Name | Type | Summary |
|---|---|---|
|
| Deprecated attribute describing an existing virtual NIC profile. |
7.328.3. target_vnic_profile Copy linkLink copied to clipboard!
Deprecated attribute describing an existing virtual NIC profile.
Please note that this attribute has been deprecated since version 4.2.1 of the engine, and preserved only for backward compatibility. It will be removed in the future.
7.329. VolumeGroup struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
7.330. Watchdog struct Copy linkLink copied to clipboard!
This type represents a watchdog configuration.
| Name | Type | Summary |
|---|---|---|
|
| Watchdog action to be performed when watchdog is triggered. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| A unique identifier. | |
|
| Model of watchdog device. | |
|
| A human-readable name in plain text. |
7.330.1. model Copy linkLink copied to clipboard!
Model of watchdog device. Currently supported only I6300ESB.
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| Optionally references to a template the device is used by. | |
|
|
Do not use this element, use | |
|
| Vm[] | References to the virtual machines that are using this device. |
7.330.2. vms Copy linkLink copied to clipboard!
References to the virtual machines that are using this device. A device may be used by several virtual machines; for example, a shared disk my be used simultaneously by two or more virtual machines.
7.331. WatchdogAction enum Copy linkLink copied to clipboard!
This type describes available watchdog actions.
| Name | Summary |
|---|---|
|
| Virtual machine process will get core dumped to the default path on the host. |
|
| No action will be performed when watchdog action is triggered. |
|
| Virtual machine will be paused when watchdog action is triggered. |
|
| Virtual machine will be powered off when watchdog action is triggered. |
|
| Virtual machine will be rebooted when watchdog action is triggered. |
7.331.1. none Copy linkLink copied to clipboard!
No action will be performed when watchdog action is triggered. However log message will still be generated.
7.332. WatchdogModel enum Copy linkLink copied to clipboard!
This type represents the watchdog model.
| Name | Summary |
|---|---|
|
| The watchdog model for S390X machines. |
|
| PCI based watchdog model. |
7.332.1. diag288 Copy linkLink copied to clipboard!
The watchdog model for S390X machines.
S390X has an integrated watchdog facility that is controlled via the DIAG288 instruction. Use this model for S390X virtual machines.
7.332.2. i6300esb Copy linkLink copied to clipboard!
PCI based watchdog model.
Use the I6300ESB watchdog for x86_64 and PPC64 virtual machines.
7.333. Weight struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| A unique identifier. | |
|
| A human-readable name in plain text. |
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
Appendix A. Primitive types Copy linkLink copied to clipboard!
This section describes the primitive data types supported by the API.
A.1. String primitive Copy linkLink copied to clipboard!
A finite sequence of Unicode characters.
A.2. Boolean primitive Copy linkLink copied to clipboard!
Represents the false and true concepts used in mathematical logic.
The valid values are the strings false and true.
Case is ignored by the engine, so for example False and FALSE also valid values. However the server will always return lower case values.
For backwards compatibility with older versions of the engine, the values 0 and 1 are also accepted. The value 0 has the same meaning than false, and 1 has the same meaning than true. Try to avoid using these values, as support for them may be removed in the future.
A.3. Integer primitive Copy linkLink copied to clipboard!
Represents the mathematical concept of integer number.
The valid values are finite sequences of decimal digits.
Currently the engine implements this type using a signed 32 bit integer, so the minimum value is -231 (-2147483648) and the maximum value is 231-1 (2147483647).
However, there are some attributes in the system where the range of values possible with 32 bit isn’t enough. In those exceptional cases the engine uses 64 bit integers, in particular for the following attributes:
-
Disk.actual_size -
Disk.provisioned_size -
GlusterClient.bytes_read -
GlusterClient.bytes_written -
Host.max_scheduling_memory -
Host.memory -
HostNic.speed -
LogicalUnit.size -
MemoryPolicy.guaranteed -
NumaNode.memory -
QuotaStorageLimit.limit -
StorageDomain.available -
StorageDomain.used -
StorageDomain.committed -
VmBase.memory
For these exception cases the minimum value is -263 (-9223372036854775808) and the maximum value is 263-1 (9223372036854775807).
In the future the integer type will be implemented using unlimited precission integers, so the above limitations and exceptions will eventually disappear.
A.4. Decimal primitive Copy linkLink copied to clipboard!
Represents the mathematical concept of real number.
Currently the engine implements this type using 32-bit IEEE 754 single precision floating point numbers.
For some attributes this isn’t enough precision. In those exceptional cases the engine uses 64 bit double precision floating point numbers, in particular for the following attributes:
-
QuotaStorageLimit.usage -
QuotaStorageLimit.memory_limit -
QuotaStorageLimit.memory_usage
In the future the decimal type will be implemented using unlimited precision decimal numbers, so the above limitations and exceptions will eventually disappear.
A.5. Date primitive Copy linkLink copied to clipboard!
Represents a date and time.
The format returned by the engine is the one described in the XML Schema specification when requesting XML. For example, if you send a request like this to retrieve the XML representation of a virtual machine:
GET /ovirt-engine/api/vms/123 Accept: application/xml
GET /ovirt-engine/api/vms/123
Accept: application/xml
The response body will contain the following XML document:
<vm id="123" href="/ovirt-engine/api/vms/123"> ... <creation_time>2016-09-08T09:53:35.138+02:00</creation_time> ... </vm>
<vm id="123" href="/ovirt-engine/api/vms/123">
...
<creation_time>2016-09-08T09:53:35.138+02:00</creation_time>
...
</vm>
When requesting the JSON representation the engine uses a different, format: an integer containing the number of milliseconds since Jan 1st 1970, also known as epoch time. For example, if you send a request like this to retrieve the JSON representation of a virtual machine:
GET /ovirt-engine/api/vms/123 Accept: application/json
GET /ovirt-engine/api/vms/123
Accept: application/json
The response body will contain the following JSON document:
In both cases, the dates returned by the engine use the time zone configured in the server where it is running. In these examples, the time zone is UTC+2.
Appendix B. Changes in version 4 of the API Copy linkLink copied to clipboard!
This section enumerates the backwards-compatibility breaking changes that have been introduced in and since version 4 of the API.
B.1. Changes in API version 4.0 (succeeding version 3.6) Copy linkLink copied to clipboard!
B.1.1. Removed YAML support Copy linkLink copied to clipboard!
The support for YAML has been completely removed.
B.1.2. Renamed complex types Copy linkLink copied to clipboard!
The following XML schema complex types have been renamed:
| Version 3 | Version 4 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
B.1.3. Replaced the Status type with enum types Copy linkLink copied to clipboard!
Currently the status of different objects is reported using the Status type, which contains a state string describing the status and another detail string for additional details. For example, the status of a virtual machine that is paused due to an IO error is currently reported as follows:
In version 4 of the API this Status type has been removed and replaced by enum types. When the additional detail string is needed it has been replaced with an additional status_detail attribute. So, for example, the status of the same virtual machine will now be reported as follows:
B.1.4. Remove the NIC network and port_mirroring properties Copy linkLink copied to clipboard!
The NIC network and port_mirroring elements have been replaced by the vnic_profile element, so when creating or updating a NIC instead of specifying the network and port mirroring configuration, these are previusly specified creating a vNIC profile:
POST /ovirt-engine/api/vnicprofiles
POST /ovirt-engine/api/vnicprofiles
<vnic_profile> <name>myprofile</name> <network id="..."/> <port_mirroring>true</port_mirroring> </vnic_profile>
<vnic_profile>
<name>myprofile</name>
<network id="..."/>
<port_mirroring>true</port_mirroring>
</vnic_profile>
And then the NIC is created or referencing the existing vNIC profile:
PUT /ovirt-engine/api/vms/123/nics/456
PUT /ovirt-engine/api/vms/123/nics/456
<nic> <vnic_profile id="/vnicprofiles/..."> </nic>
<nic>
<vnic_profile id="/vnicprofiles/...">
</nic>
The old elements and their meaning were preserved for backwards compatibility, but they have now been completely removed.
Note that the network element hasn’t been removed from the XML schema because it is still used by the initialization element, but it will be completely ignored if provided when creating or updating a NIC.
B.1.5. Remove the NIC active property Copy linkLink copied to clipboard!
The NIC active property was replaced by plugged some time ago. It has been completely removed now.
B.1.6. Remove the disk type property Copy linkLink copied to clipboard!
The type property of disks has been removed, but kept in the XML schema and ignored. It has been completely removed now.
B.1.7. Remove the disk size property Copy linkLink copied to clipboard!
The disk size property has been replaced by provisioned_size long ago. It has been completely removed now.
B.1.8. Removed support for pinning a VM to a single host Copy linkLink copied to clipboard!
Before version 3.6 the API had the possibility to pin a VM to a single host, using the placement_policy element of the VM entity:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
<vm>
<placement_policy>
<host id="456"/>
</placement_policy>
<vm>
<vm>
<placement_policy>
<host id="456"/>
</placement_policy>
<vm>
In version 3.6 this capability was enhanced to support multiple hosts, and to do so a new hosts element was added:
PUT /ovirt-engine/api/vms/123
PUT /ovirt-engine/api/vms/123
To preserve backwards compatibility the single host element was preserved. In 4.0 this has been removed, so applications will need to use the hosts element even if when pinning to a single host.
B.1.9. Removed the capabilities.permits element Copy linkLink copied to clipboard!
The list of permits is potentiall different for each cluster level, and it has been added to the version element long ago, but it has been kept into the capabilities element as well, just for backwards compatibility.
In 4.0 it the capabilities service has been completely removed, and replaced by the new clusterlevels service. To find the permits supported by cluster level 4.0 a request like this should be used:
GET /ovirt-engine/api/clusterlevels/4.0
GET /ovirt-engine/api/clusterlevels/4.0
The result will be a document containing the information specific to that cluster level, in particular the set of supported permits:
B.1.10. Removed the storage_manager element Copy linkLink copied to clipboard!
The storage_manager element was replaced by the spm element some time ago. The old one was kept for backwards compatibility, but it has been completely removed now.
B.1.11. Removed the data center storage_type element Copy linkLink copied to clipboard!
Data centers used to be associated to a specific storage type (NFS, Fiber Channel, iSCSI, etc) but they have been changed some time so that there are only two types: with local storage and with shared storage. A new local element was introduced to indicate this, and the old storage_type was element was preserved for backwards compatibility. This old element has now been completely removed.
B.1.12. Remove the timezone element Copy linkLink copied to clipboard!
The VM resource used to contain a timezone element to represent the time zone. This element only allowed a string:
<vm> <timezone>Europe/Madrid</timezone> </vm>
<vm>
<timezone>Europe/Madrid</timezone>
</vm>
This doesn’t allow extension, and as a it was necessary to add the UTC offset, it was replaced with a new structured time_zone element:
The old timezone element was preserved, but it has been completely removed now.
B.1.13. Removed the guest_info element Copy linkLink copied to clipboard!
The guest_info element was used to hold information gathered by the guest agent, like the IP addresses and the fully qualified host name. This information is also available in other places. For example, the IP addresses are available within VM resource:
GET /ovirt-engine/api/vms/123
GET /ovirt-engine/api/vms/123
And also within the NIC resource, using the newer reported_devices element:
GET /ovirt-engine/api/vms/{vm:id}/nics/{nic:id}
GET /ovirt-engine/api/vms/{vm:id}/nics/{nic:id}
In addition this newer reported_devices element provides more complete information, like multiple IP addresses, MAC addresses, etc.
To remove this duplication the guest_info element has been removed.
To support the fully qualified domain name a new fqdn element has been added to the VM resource:
GET /ovirt-engine/api/vms/123
GET /ovirt-engine/api/vms/123
<vm> <fqdn>myvm.example.com</fqdn> </vms>
<vm>
<fqdn>myvm.example.com</fqdn>
</vms>
This will contain the same information that guest_info.fqdn used to contain.
B.1.14. Replaced CPU id attribute with type element Copy linkLink copied to clipboard!
The cpu element used to have an id attribute that indicates the type of CPU:
<cpu id="Intel Nehalem Family"> <architecture>X86_64</architecture> ... </cpu>
<cpu id="Intel Nehalem Family">
<architecture>X86_64</architecture>
...
</cpu>
This is in contradiction with the rest of the elements of the API model, where the id attribute is used for opaque identifiers. This id attribute has been replaced with a new type element:
<cpu> <type>Intel Nehalem Family</type> <architecture>X86_64</architecture> </cpu>
<cpu>
<type>Intel Nehalem Family</type>
<architecture>X86_64</architecture>
</cpu>
B.1.15. Use elements instead of attributes in CPU topology Copy linkLink copied to clipboard!
In the past the CPU topology element used attributes for its properties:
<cpu> <topology sockets="1" cores="1" threads="1"/> ... </cpu>
<cpu>
<topology sockets="1" cores="1" threads="1"/>
...
</cpu>
This is contrary to the common practice in the API. They have been replaced by inner elements:
B.1.16. Use elements instead of attributes in VCPU pin Copy linkLink copied to clipboard!
In the past the VCPU pin element used attributes for its properties:
<cpu_tune> <vcpu_pin vcpu="0" cpu_set="0"/> </cpu_tune>
<cpu_tune>
<vcpu_pin vcpu="0" cpu_set="0"/>
</cpu_tune>
This is contrary to the common practice in the API. They have been replaced by inner elements:
B.1.17. Use elements instead of attributes in VCPU pin Copy linkLink copied to clipboard!
In the past the version element used attributes for its properties:
<version major="3" minor="5" ../>
<version major="3" minor="5" ../>
This is contrary to the common practice in the API. They have been replaced by inner elements:
<version> <major>3</minor> <minor>5</minor> ... </version>
<version>
<major>3</minor>
<minor>5</minor>
...
</version>
B.1.18. Use elements instead of attributes in memory overcommit Copy linkLink copied to clipboard!
In the past the overcommit element used attributes for its properties:
<memory_policy> <overcommit percent="100"/> ... </memory_policy>
<memory_policy>
<overcommit percent="100"/>
...
</memory_policy>
This is contrary to the common practice in the API. They have been replaced by inner elements:
B.1.19. Use elements instead of attributes in console Copy linkLink copied to clipboard!
In the past the console element used attributes for its properties:
<console enabled="true"/>
<console enabled="true"/>
This is contrary to the common practice in the API. They have been replaced by inner elements:
<console> <enabled>true</enabled> </console>
<console>
<enabled>true</enabled>
</console>
B.1.20. Use elements instead of attributes in VIRTIO SCSI Copy linkLink copied to clipboard!
In the past the VIRTIO ISCSI element used attributes for its properties:
<virtio_scsi enabled="true"/>
<virtio_scsi enabled="true"/>
This is contrary to the common practice in the API. They have been replaced by inner elements:
<virtio_scsi> <enabled>true</enabled> </virtio_scsi>
<virtio_scsi>
<enabled>true</enabled>
</virtio_scsi>
B.1.21. Use element instead of attribute for power management agent type Copy linkLink copied to clipboard!
The power management type property was represented as an attribute:
<agent type="apc"> <username>myuser</username> ... </agent>
<agent type="apc">
<username>myuser</username>
...
</agent>
This is contrary to the common practice in the API. It has been replaced with an inner element:
<agent> <type>apc</type> <username>myuser</username> ... </agent>
<agent>
<type>apc</type>
<username>myuser</username>
...
</agent>
B.1.22. Use elements instead of attributes in power management agent options Copy linkLink copied to clipboard!
In the past the power management agent options element used attributes for its properties:
<options> <option name="port" value="22"/> <option name="slot" value="5"/> ... </options>
<options>
<option name="port" value="22"/>
<option name="slot" value="5"/>
...
</options>
This is contrary to the common practice in the API. They have been replaced with inner elements:
B.1.23. Use elements instead of attributes in IP address: Copy linkLink copied to clipboard!
In the past the IP address element used attributes for its properties:
<ip address="192.168.122.1" netmask="255.255.255.0"/>
<ip address="192.168.122.1" netmask="255.255.255.0"/>
This is contrary to the common practice in the API. They have been replaced with inner elements:
<ip> <address>192.168.122.1</address> <netmask>255.255.255.0</netmask> </ip>
<ip>
<address>192.168.122.1</address>
<netmask>255.255.255.0</netmask>
</ip>
B.1.24. Use elements instead of attributes in MAC address: Copy linkLink copied to clipboard!
In the past the MAC address element used attributes for its properties:
<mac address="66:f2:c5:5f:bb:8d"/>
<mac address="66:f2:c5:5f:bb:8d"/>
This is contrary to the common practice in the API. They have been replaced by inner elements:
<mac> <address>66:f2:c5:5f:bb:8d</address> </mac>
<mac>
<address>66:f2:c5:5f:bb:8d</address>
</mac>
B.1.25. Use elements instead of attributes in boot device: Copy linkLink copied to clipboard!
In the past the boot device element used attributes for its properties:
<boot dev="cdrom"/>
<boot dev="cdrom"/>
This is contrary to the common practice in the API. They have been replaced by inner elements:
<boot> <dev>cdrom</dev> </boot>
<boot>
<dev>cdrom</dev>
</boot>
B.1.26. Use element instead of attribute for operating system type Copy linkLink copied to clipboard!
The operating system type property was represented as an attribute:
<os type="other"> ... </os>
<os type="other">
...
</os>
This is contrary to the common practice in the API. It has been replaced with an inner element:
<os> <type>other</type> ... </os>
<os>
<type>other</type>
...
</os>
B.1.27. Removed the force parameter from the request to retrieve a host Copy linkLink copied to clipboard!
The request to retrieve a host used to support a force matrix parameter to indicate that the data of the host should be refreshed (calling VDSM to reload host capabilities and devices) before retrieving it from the database:
GET /ovirt-engine/api/hosts/123;force
GET /ovirt-engine/api/hosts/123;force
This force parameter has been superseded by the host refresh action, but kept for backwards compatibility. It has been completely removed now. Applications that require this functionality should perform two requests, first one to refresh the host:
POST /ovirt-engine/api/hosts/123/refresh
POST /ovirt-engine/api/hosts/123/refresh
<action/>
<action/>
And then one to retrieve it, without the force parameter:
GET /ovirt-engine/api/hosts/123
GET /ovirt-engine/api/hosts/123
B.1.28. Removed deprecated host power management configuration Copy linkLink copied to clipboard!
The host power management configuration used to be part of the host resource, using embedded configuration elements:
This has been changed some time ago, in order to support multiple power management agents, introducing a new /hosts/123/fenceagents collection.
The old type attribute, the old address, username and password elements, and the inner agents element directly inside power_management were preserved for backwards compatibility. All these elements have been completely removed, so the only way to query or modify the power management agents is now the /hosts/123/fenceagents sub-collection.
B.1.29. Use multiple boot.devices.device instead of multiple boot Copy linkLink copied to clipboard!
In the past the way to specify the boot sequence when starting a virtual machine was to use multiple boot elements, each containing a dev element. For example, to specify that the virtual machine should first try to boot from CDROM and then from hard disk the following request was used:
POST /ovirt-engine/api/vms/123/start
POST /ovirt-engine/api/vms/123/start
The common practice in other parts of the API is to represent arrays with a wrapper element. In that case that wrapper element could be named boots, but that doesn’t make much sense, as what can have multiple values here is the boot device, not the boot sequence. To fix this inconsistence this has been replaced with a single boot element that can contain multiple devices:
POST /ovirt-engine/api/vms/123/start
POST /ovirt-engine/api/vms/123/start
B.1.30. Removed the disks.clone and disks.detach_only elements Copy linkLink copied to clipboard!
These elements aren’t really part of the representation of disks, but parameters of the operations to add and remove virtual machines.
The disks.clone element was used to indicate that the disks of a new virtual machine have to be cloned:
POST /ovirt-engine/api/vms
POST /ovirt-engine/api/vms
This has been now removed, and replaced by a new clone query parameter:
POST /ovirt-engine/api/vms?clone=true
POST /ovirt-engine/api/vms?clone=true
<vm> ... </vm>
<vm>
...
</vm>
The disks.detach_only element was used to indicate that when removing a virtual machine the disks do not have to be removed, but just detached from the virtual machine:
DELETE /ovirt-engine/api/vms/123
DELETE /ovirt-engine/api/vms/123
This has been now removed, and replaced by a new detach_only query parameter:
DELETE /ovirt-engine/api/vms/123?detach_only=true
DELETE /ovirt-engine/api/vms/123?detach_only=true
B.1.31. Rename element vmpool to vm_pool Copy linkLink copied to clipboard!
The names of the elements that represent pools of virtual machines used to be vmpool and vmpools. They have been renamed to vm_pool and vm_pools in order to have a consistent correspondence between names of complex types (VmPool and VmPools in this case) and elements.
B.1.32. Use logical_units instead of multiple logical_unit Copy linkLink copied to clipboard!
The logical units that are part of a volume group used to be reported as an unbounded number of logical_unit elements. For example, when reporting the details of a storage domain:
GET /ovirt-engine/api/storagedomains/123
GET /ovirt-engine/api/storagedomains/123
This is contrary to the usual practice in the API, as list of elements are always wrapped with an element. This has been fixed now, so the list of logical units will be wrapped with the logical_units element:
GET /ovirt-engine/api/storagedomains/123
GET /ovirt-engine/api/storagedomains/123
B.1.33. Removed the snapshots.collapse_snapshots element Copy linkLink copied to clipboard!
This element isn’t really part of the representation of snapshots, but a parameter of the operation that imports a virtual machine from an export storage domain:
POST /ovirt-engine/api/storagedomains/123/vms/456/import
POST /ovirt-engine/api/storagedomains/123/vms/456/import
This has been now removed, and replaced by a new collapse_snapshots query parameter:
POST /ovirt-engine/api/storagedomains/123/vms/456/import?collapse_snapshots=true
POST /ovirt-engine/api/storagedomains/123/vms/456/import?collapse_snapshots=true
<action/>
<action/>
B.1.34. Renamed storage and host_storage elements Copy linkLink copied to clipboard!
The host storage collection used the storage and host_storage elements and the Storage and HostStorage complex types to report the storage associated to a host:
GET /ovirt-engine/api/hosts/123/storage
GET /ovirt-engine/api/hosts/123/storage
This doesn’t follow the pattern used in the rest of the API, where the outer element is a plural name and the inner element is the same name but in singular. This has now been changed to use host_storages as the outer element and host_storage as the inner element:
GET /ovirt-engine/api/hosts/123/storage
GET /ovirt-engine/api/hosts/123/storage
B.1.35. Removed the permissions.clone element Copy linkLink copied to clipboard!
This element isn’t really part of the representation of permissions, but a parameter of the operations to create virtual machines or templates:
POST /ovirt-engine/api/vms
POST /ovirt-engine/api/vms
POST /ovirt-engine/api/templates
POST /ovirt-engine/api/templates
This has been now removed, and replaced by a new clone_permissions query parameter:
POST /ovirt-engine/api/vms?clone_permissions=true
POST /ovirt-engine/api/vms?clone_permissions=true
<vm> <template id="..."/> </vm>
<vm>
<template id="..."/>
</vm>
POST /ovirt-engine/api/templates?clone_permissions=true
POST /ovirt-engine/api/templates?clone_permissions=true
<template> <vm id="..."/> </template>
<template>
<vm id="..."/>
</template>
B.1.36. Renamed the random number generator source elements Copy linkLink copied to clipboard!
The random number generator sources used to be reported using a collection of source elements wrapped by an element with a name reflecting its use. For example, the required random number generator sources of a cluster used to be reported as follows:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/123
And the random number generator sources suported by a host used to be reported as follows:
GET /ovirt-engine/api/hosts/123
GET /ovirt-engine/api/hosts/123
This isn’t consistent with the rest of the API, where collections are wrapped by a name in plural and elements by the same name in singular. This has been now fixed. The required random number generator sources will now be reported as follows:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/123
And the random number generator sources supported by a host will be reported as follows:
GET /ovirt-engine/api/hosts/123
GET /ovirt-engine/api/hosts/123
Note the use of required_rng_source and supported_rng_source instead of just source.
B.1.37. Removed the intermediate tag.parent element Copy linkLink copied to clipboard!
The relationship bettween a tag and it’s parent tag used to be represented using an intermedite parent tag, that in turn contains another tag element:
This structure has been simplified so that only one parent element is used now:
<tag> <name>mytag</name> <parent id="..." href="..."/> </tag>
<tag>
<name>mytag</name>
<parent id="..." href="..."/>
</tag>
B.1.38. Remove scheduling built-in names and thresholds Copy linkLink copied to clipboard!
In the past the specification of scheduling policies for clusters was based in built-in names and thresholds. For example a cluster that used the evenly distributed scheduling policy was represented as follows:
This mechanism was replaced with a top level /schedulingpolicies collection where scheduling policies can be defined with arbitrary names and properties. For example, the same scheduling policy is represented as follows in that top level collection:
The representation of the cluster references the scheduling policy with its identifier:
<cluster> <name>mycluster</name> <scheduling_policy id="..."/> ... </cluster>
<cluster>
<name>mycluster</name>
<scheduling_policy id="..."/>
...
</cluster>
To preserve backwards compatibility the old policy and thresholds elements were preserved. The scheduling policy representation embedded within the cluster was also preserved. All these things have been completely removed now, so the only way to reference a scheduling policy when retrieving, creating or updating a cluster is to reference an existing one using its identifier. For example, when retrieving a cluster only the id (and href) will be populated:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/123
<cluster> ... <scheduling_policy id="..." href="..."/> ... </cluster>
<cluster>
...
<scheduling_policy id="..." href="..."/>
...
</cluster>
When creating or updating a cluster only the id will be accepted.
B.1.39. Removed the bricks.replica_count and bricks.stripe_count elements Copy linkLink copied to clipboard!
These elements aren’t really part of the representation of a collection of bricks, but parameters of the operations to add and remove bricks. They have now been removed, and replaced by new replica_count and stripe_count parameters:
POST .../bricks?replica_count=3&stripe_count=2
POST .../bricks?replica_count=3&stripe_count=2
DELETE .../bricks?replica_count=3
DELETE .../bricks?replica_count=3
B.1.40. Renamed the statistics type property to kind Copy linkLink copied to clipboard!
The statistics used to be represented using a type element that indicates the kind of statistic (gauge, counter, etc) and also a type attribute that indicates the type of the values (integer, string, etc):
To avoid the use of the type concept for both things the first has been replaced by kind, and both kind and type are now elements:
B.1.41. Use multiple vcpu_pins.vcpu_pin instead of multiple vcpu_pin Copy linkLink copied to clipboard!
In the past the way to specify the virtual to physical CPU pinning of a virtual machine was to use multiple vcpu_pin elements:
In order to conform to the common practice in other parts of the API this has been changed to use a wrapper element, in this case vcpu_pins:
B.1.42. Use force parameter to force remove a data center Copy linkLink copied to clipboard!
The operation that removes a data center supports a force parameter. In order to use it the DELETE operation used to support an optional action parameter:
DELETE /ovirt-engine/api/datacenters/123
DELETE /ovirt-engine/api/datacenters/123
<action> <force>true</force> </action>
<action>
<force>true</force>
</action>
This optional action parameter has been replaced with an optional parameter:
DELETE /ovirt-engine/api/datacenters/123?force=true
DELETE /ovirt-engine/api/datacenters/123?force=true
B.1.43. Use force parameter to force remove a host Copy linkLink copied to clipboard!
The operation that removes a host supports a force parameter. In order to use it the DELETE operation used to support an optional action parameter:
DELETE /ovirt-engine/api/host/123
DELETE /ovirt-engine/api/host/123
<action> <force>true</force> </action>
<action>
<force>true</force>
</action>
This optional action parameter has been replaced with an optional parameter:
DELETE /ovirt-engine/api/host/123?force=true
DELETE /ovirt-engine/api/host/123?force=true
B.1.44. Use parameters for force remove storage domain Copy linkLink copied to clipboard!
The operation that removes a storage domain supports the force, destroy and host parameters. These parameters were passed to the DELETE method using the representation of the storage domain as the body:
DELETE /ovirt-engine/api/storagedomains/123
DELETE /ovirt-engine/api/storagedomains/123
This was problematic, as the HTTP DELETE parameters shouldn’t have a body, and the representation of the storage domain shouldn’t include things that aren’t attributes of the storage domain, rather parameters of the operation.
The force, delete and host attributes have been replaced by equivalent parameters, and the operation doesn’t now accept a body. For example, now the correct way to delete a storage domain with the force parameter is the following:
DELETE /ovirt-engine/api/storagedomain/123?host=myhost&force=true
DELETE /ovirt-engine/api/storagedomain/123?host=myhost&force=true
To delete with the destroy parameter:
DELETE /ovirt-engine/api/storagedomain/123?host=myhost&destroy=true
DELETE /ovirt-engine/api/storagedomain/123?host=myhost&destroy=true
B.1.45. Use host parameter to remove storage server connection Copy linkLink copied to clipboard!
The operation that removes a storage server connection supports a host parameter. In order to use it the DELETE method used to support an optional action parameter:
DELETE /ovirt-engine/api/storageconnections/123
DELETE /ovirt-engine/api/storageconnections/123
<action>
<host id="...">
<name>...</name>
</host>
</action>
<action>
<host id="...">
<name>...</name>
</host>
</action>
This optional action parameter has been replaced with an optional parameter:
DELETE /ovirt-engine/api/storageconnections/123?host=myhost
DELETE /ovirt-engine/api/storageconnections/123?host=myhost
B.1.46. Use force and storage_domain parameters to remove template disks Copy linkLink copied to clipboard!
The operation that removes a template disk supports the force and storage_domain parameters. In order to use it them the DELETE method used to support an optional action parameter:
DELETE /ovirt-engine/api/templates/123/disks/456
DELETE /ovirt-engine/api/templates/123/disks/456
<action> <force>...</force> <storage_domain id="..."/> </action>
<action>
<force>...</force>
<storage_domain id="..."/>
</action>
In version 4 of the API this operation has been moved to the new diskattachments collection, and the request body has been replaced with the query parameters force and storage_domain:
DELETE /ovirt-engine/api/templates/123/disksattachments/456?force=true
DELETE /ovirt-engine/api/templates/123/disksattachments/456?force=true
DELETE /ovirt-engine/api/templates/123/disksattachments/456?storage_domain=123
DELETE /ovirt-engine/api/templates/123/disksattachments/456?storage_domain=123
B.1.47. Do not remove disks via the VM disk API Copy linkLink copied to clipboard!
Removing an entity by deleting /vms/123/disks/456 means removing the relationship between the VM and the disk - i.e., this operation should just detach the disk from the VM. This operation is no longer able to remove disks completely from the system, which was prone to user errors and had unreverseable consequences. To remove a disk, instead use the /disk/456 API:
DELETE /ovirt-engine/api/disks/456
DELETE /ovirt-engine/api/disks/456
B.1.48. Use force query parameter to force remove a virtual machine Copy linkLink copied to clipboard!
The operation that removes a virtual machine supports a force parameter. In order to use it the DELETE method used to support an optional action parameter:
DELETE /ovirt-engine/api/vms/123
DELETE /ovirt-engine/api/vms/123
<action> <force>true</force> </action>
<action>
<force>true</force>
</action>
This optional action parameter has been replaced with an optional query parameter:
DELETE /ovirt-engine/api/vms/123?force=true
DELETE /ovirt-engine/api/vms/123?force=true
B.1.49. Use POST instead of DELETE to remove multiple bricks Copy linkLink copied to clipboard!
The operation that removes multiple Gluster bricks was implemented using the DELETE method and passing the list of bricks as the body of the request:
DELETE /ovirt-engine/api/clusters/123/glustervolumes/456/bricks
DELETE /ovirt-engine/api/clusters/123/glustervolumes/456/bricks
<bricks> <bricks id="..."/> <bricks id="..."/> ... </bricks>
<bricks>
<bricks id="..."/>
<bricks id="..."/>
...
</bricks>
This is problematic because the DELETE method shouldn’t have a body, so it has been replaced with a new remove action that uses the POST method:
POST /ovirt-engine/api/clusters/123/glustervolumes/456/bricks/remove
POST /ovirt-engine/api/clusters/123/glustervolumes/456/bricks/remove
<bricks> <bricks id="..."/> <bricks id="..."/> ... </bricks>
<bricks>
<bricks id="..."/>
<bricks id="..."/>
...
</bricks>
B.1.50. Removed the scheduling_policy.policy element Copy linkLink copied to clipboard!
The element was kept for backward compatibility. Use scheduling_policy.name instead.
POST /ovirt-engine/api/schedulingpolicies
POST /ovirt-engine/api/schedulingpolicies
<scheduling_policy> ... <name>policy_name</name> ... </scheduling_policy>
<scheduling_policy>
...
<name>policy_name</name>
...
</scheduling_policy>
PUT /ovirt-engine/api/schedulingpolicies/123
PUT /ovirt-engine/api/schedulingpolicies/123
<scheduling_policy> ... <name>policy_name</name> ... </scheduling_policy>
<scheduling_policy>
...
<name>policy_name</name>
...
</scheduling_policy>
B.1.51. Added snapshot.snapshot_type Copy linkLink copied to clipboard!
Enums are being gradually introduces to the API. Some fields which were string until now, are replaced with an appropriate enum. One such field is vm.type. But this field is inherited by snapshot, and snapshot type is different than vm type. So a new field has been added to snapshot entity: snapshot.snapshot_type.
<snapshot> ... <snapshot_type>regular|active|stateless|preview</snapshot_type> ... </snapshot>
<snapshot>
...
<snapshot_type>regular|active|stateless|preview</snapshot_type>
...
</snapshot>
B.1.52. Removed move action from VM Copy linkLink copied to clipboard!
The deprecated move action of the VM entity has been removed. Instead, you can move inidividual disks.
B.1.53. Moved reported_configurations.in_sync to network_attachment Copy linkLink copied to clipboard!
In version 3 of the API the XML schema type ReportedConfigurations had a in_sync property:
In the specification mechanism used by version 4 of the API this can’t be expressed, because list types (the list of reported configurations) can’t have attributes. To be able to represent it the attribute has been moved to the enclosing network_attachment:
B.1.54. Replaced capabilities with clusterlevels Copy linkLink copied to clipboard!
The top level capabilities collection has been replaced by the new clusterlevels collection. This new collection will contain the information that isn’t available in the model, like the list of CPU types available for each cluster level:
GET /ovirt-engine/api/clusterlevels
GET /ovirt-engine/api/clusterlevels
This will return a list of ClusterLevel objects containing the details for all the cluster levels supported by the system:
Each specific cluster level has it’s own subresource, identified by the version itself:
GET /ovirt-engine/api/clusterlevels/3.6
GET /ovirt-engine/api/clusterlevels/3.6
This will return the details of that version:
B.1.55. Replaced disks with diskattachments Copy linkLink copied to clipboard!
In version 3 of the API virtual machines and templates had a disks collection containing all the information of the disks attached to them. In version 4 of the API these disks collections have been removed and replaced with a new diskattachments collection that will contain only the references to the disk and the attributes that are specific of the relationship between disks and the virtual machine or template that they are attached to: interface and bootable.
To find what disks are attached to a virtual machine, for example, send a request like this:
GET /ovirt-engine/api/vms/123/diskattachments
GET /ovirt-engine/api/vms/123/diskattachments
That will return a response like this:
To find the rest of the details of the disk, follow the link provided.
Adding disks to a virtual machine or template uses the new disk_attachment element as well: request like this:
POST /ovirt-engine/api/vms/123/diskattachments
POST /ovirt-engine/api/vms/123/diskattachments
With the following body if the disk doesn’t exist and you want to create it:
Or with the following body if the disk already exists, and you just want to attach it to the virtual machine:
<disk_attachment> <bootable>false</bootable> <interface>virtio</interface> <disk id="456"/> </disk_attachment>
<disk_attachment>
<bootable>false</bootable>
<interface>virtio</interface>
<disk id="456"/>
</disk_attachment>
Take into account that the vm.disks and template.disks attribtes have disk_attachments for all usages. For example, when creating a template the vm.disks element was used to indicate in which storage domain to create the disks of the template. This usage has also been replaced by vm.disk_attachments, so the request to creaate a template with disks in specific storage domains will now look like this:
B.1.56. Use iscsi_targets element to discover unregistered storage Copy linkLink copied to clipboard!
In version 3 of the API the operation to discover unregistered storage domains used to receive a list of iSCSI targets, using multiple iscsi_target elements:
POST /ovirt-engine/api/hosts/123/unregisteredstoragedomaindiscover
POST /ovirt-engine/api/hosts/123/unregisteredstoragedomaindiscover
In version 4 of the API all repeating elements, like iscsi_target in this case, are wrapped with another element, iscsi_targets in case. So the same request should now look like this:
POST /ovirt-engine/api/hosts/123/unregisteredstoragedomaindiscover
POST /ovirt-engine/api/hosts/123/unregisteredstoragedomaindiscover
B.2. Changes in Engine version 4.5 Copy linkLink copied to clipboard!
B.2.1. Openstack Volume (Cinder) integration replaced by Managed Block Storage. Copy linkLink copied to clipboard!
Appendix C. Legal notice Copy linkLink copied to clipboard!
Copyright © 2022 Red Hat, Inc.
Licensed under the (Creative Commons Attribution–ShareAlike 4.0 International License). Derived from documentation for the (oVirt Project). If you distribute this document or an adaptation of it, you must provide the URL for the original version.
Modified versions must remove all Red Hat trademarks.
Red Hat, Red Hat Enterprise Linux, the Red Hat logo, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.