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.2. 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 Ruby 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. The Internet Engineering Task Force provides a Request for Comments (RFC) explaining the Hypertext Transfer Protocol at http://www.ietf.org/rfc/rfc2616.txt.
- Knowledge of Extensible Markup Language (XML) or JavaScript Object Notation (JSON), which the API uses to construct resource representations. The W3C provides a full specification on XML at http://www.w3.org/TR/xml. ECMA International provide a free publication on JSON at http://www.ecma-international.org.
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) [1] 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 a command like this: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 This command will connect to the server and display output similar to the following:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow The text between the
-----BEGIN CERTIFICATE-----and-----END CERTIFICATE-----marks shows the certificates presented by the server. The first one is the certificate of the server itself, and the last one is the certificate of the CA. Copy the CA certificate, including the marks, to theca.crtfile. The result should look like this:-----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 it has been manually replaced by the administrator of the server.
- Method 2
If you cannot use the
openssl s_clientmethod described above, you can instead use a command line tool to download the CA certificate from the Red Hat Virtualization Manager.Examples of command line tools include
curlandwget, both of which are 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
https://myengine.example.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CACopy to Clipboard Copied! Toggle word wrap Toggle overflow Depending on the chosen browser, the certificate either downloads or imports 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 from the browser’s certification 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
-
Log in to the Red Hat Virtualization Manager machine as
Each of these methods results in a certificate file named ca.crt on your client machine. You must then import this file into the certificate store of the client.
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 section 4.3 of 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 [2] 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. Quick start example Copy linkLink copied to clipboard!
This chapter provides an example to demonstrate the REST API’s ability to setup a basic Red Hat Virtualization environment and create a virtual machine. In addition to the standard prerequisites, this example requires the following:
- A networked and configured Red Hat Virtualization installation;
- An ISO file containing a desired virtual machine operating system to install. This chapter uses CentOS 7 for our installation ISO example; and
-
Red Hat Virtualization’s
engine-iso-uploadertool to upload your chosen operating system ISO file.
This example uses curl to demonstrate API requests with a client application. Note that any application capable of HTTP requests can substitute for curl.
For simplicity, 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.
All the curl examples use admin@internal as the user name, mypassword as the password, /etc/pki/ovirt-engine/ca.pem as the certificate location and myengine.example.com as the host name. These are just examples, Make sure to replace them with valid values for your environment.
Red Hat Virtualization generates an unique identifier for the id attribute for each resource. Identifier codes in this example might appear different to the identifier codes in your Red Hat Virtualization environment.
In many examples of this section some of the attributes of results returned by the API have been omitted, to make them shorter. You can always use the reference to find the complete list of attributes. For example, if you want to see the complete list of attributes of the Cluster type, just go here.
3.1. Example: Access API entry point Copy linkLink copied to clipboard!
The following request retrieves a representation of the main entry point for version 4 of 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
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
Same request, using the curl command:
The result will be 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 don’t 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.
3.2. Example: 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 our 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
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.
3.3. Example: 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
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.
3.4. Example: 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 our Default cluster and is a member of the Default data center. This example uses the ovirtmgmt network to connect our 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
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.
3.5. Example: 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
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.
3.6. Example: 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):
3.7. Example: 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):
3.8. Example: 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>
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>
Same request, using the curl command:
3.9. Example: 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:
Same request, using the curl command:
The response body will be an object of the Vm type:
3.10. Example: 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>
Same request, using the curl command:
3.11. Example: Create virtual 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:
Same request, using the curl command:
The storage_domains attribute tells the API to store the disk on the mydata storage domain.
3.12. Example: Attach ISO image to virtual machine Copy linkLink copied to clipboard!
The boot media for our example virtual machine requires an CD-ROM or DVD ISO image for an operating system installation. This example uses a CentOS 7 image for installation.
ISO images must be available in the myisos ISO domain for the virtual machines to use. Red Hat Virtualization provides an uploader tool that ensures that the ISO images are uploaded into the correct directory path with the correct user permissions.
Once the ISO 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
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 our 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>
Same request, using the curl command:
For more details see the documentation of the service that manages virtual machine CD-ROMS.
3.13. Example: 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:
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 4. 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}
- 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}/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}/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}/resetemulatedmachine
- 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}/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}/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}/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}/resetemulatedmachine
- 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}
- PUT /datacenters/{datacenter:id}/networks/{network:id}
- DELETE /datacenters/{datacenter:id}/networks/{network:id}
- POST /datacenters/{datacenter:id}/networks/{network:id}/networklabels
- GET /datacenters/{datacenter:id}/networks/{network:id}/networklabels
- GET /datacenters/{datacenter:id}/networks/{network:id}/networklabels/{label:id}
- DELETE /datacenters/{datacenter:id}/networks/{network:id}/networklabels/{label:id}
- POST /datacenters/{datacenter:id}/networks/{network:id}/permissions
- GET /datacenters/{datacenter:id}/networks/{network:id}/permissions
- GET /datacenters/{datacenter:id}/networks/{network:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/networks/{network:id}/permissions/{permission:id}
- POST /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles
- GET /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles
- GET /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles/{profile:id}
- DELETE /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles/{profile:id}
- POST /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions
- GET /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions
- GET /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions/{permission:id}
- DELETE /datacenters/{datacenter:id}/networks/{network:id}/vnicprofiles/{profile:id}/permissions/{permission: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}/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
- 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}
- 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
- GET /disks/{disk:id}
- DELETE /disks/{disk:id}
- POST /disks/{disk:id}/copy
- 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}
- 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 /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}/deactivate
- GET /hosts/{host:id}/devices
- GET /hosts/{host:id}/devices/{device:id}
- POST /hosts/{host:id}/enrollcertificate
- 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}
- 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}/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
- GET /icons
- GET /icons/{icon:id}
- POST /imagetransfers
- GET /imagetransfers
- GET /imagetransfers/{imagetransfer:id}
- 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}
- 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}
- 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
- 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}
- 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}/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}/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}
- DELETE /users/{user: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}/cancelmigration
- GET /vms/{vm:id}/cdroms
- GET /vms/{vm:id}/cdroms/{cdrom:id}
- PUT /vms/{vm:id}/cdroms/{cdrom: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}/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}/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}/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}
- 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 5. Services Copy linkLink copied to clipboard!
This section enumerates all the services that are available in the API.
5.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. |
5.1.1. get GET Copy linkLink copied to clipboard!
Retrieve the affinity group details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The affinity group. |
5.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 remove should be performed asynchronously. |
5.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. |
5.2. 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. |
5.2.1. remove DELETE Copy linkLink copied to clipboard!
Remove this virtual machine from the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.3. AffinityGroupVms Copy linkLink copied to clipboard!
This service manages a collection of all virtual machines assigned to an affinity group.
| Name | Summary |
|---|---|
|
| Add a virtual machine to the affinity group. |
|
| List all virtual machines assigned to this affinity group. |
5.3.1. add POST Copy linkLink copied to clipboard!
Add a virtual machine to the affinity group.
For example to add the virtual machine 000-000 to affinity group 123-456 send a request to:
POST /ovirt-engine/api/clusters/000-000/affinitygroups/123-456/vms
POST /ovirt-engine/api/clusters/000-000/affinitygroups/123-456/vms
With the following body:
<vm id="000-000"/>
<vm id="000-000"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.3.2. list GET Copy linkLink copied to clipboard!
List all virtual machines assigned to this affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of virtual machines to return. | |
|
| Out |
5.3.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machines to return. If not specified all the virtual machines are returned.
5.4. AffinityGroups Copy linkLink copied to clipboard!
Affinity groups service manages virtual machine relationships and dependencies.
| Name | Summary |
|---|---|
|
| Create a new affinity group. |
|
| List existing affinity groups. |
5.4.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:
<affinity_group> <name>AF_GROUP_001</name> <positive>true</positive> <enforcing>true</enforcing> </affinity_group>
<affinity_group>
<name>AF_GROUP_001</name>
<positive>true</positive>
<enforcing>true</enforcing>
</affinity_group>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The affinity group object to create. |
5.4.2. list GET Copy linkLink copied to clipboard!
List existing affinity groups.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of existing affinity groups. | |
|
| In | Sets the maximum number of affinity groups to return. |
5.4.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of affinity groups to return. If not specified all the affinity groups are returned.
5.5. AffinityLabel Copy linkLink copied to clipboard!
Single affinity label details.
| Name | Summary |
|---|---|
|
| Retrieves details about a label. |
|
| Removes a label from system and clears all assignments of the removed label. |
|
| Updates a label. |
5.5.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.5.2. remove DELETE Copy linkLink copied to clipboard!
Removes a label from system and clears all assignments of the removed label.
5.5.3. update PUT Copy linkLink copied to clipboard!
Updates a label.
This call will update all metadata like name or description.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.6. 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. |
5.6.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a host that has this label assigned.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.6.2. remove DELETE Copy linkLink copied to clipboard!
Remove a label from a host.
5.7. 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. |
5.7.1. add POST Copy linkLink copied to clipboard!
Add a label to a host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.7.2. list GET Copy linkLink copied to clipboard!
List all hosts with the label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.8. 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. |
5.8.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a vm that has this label assigned.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.8.2. remove DELETE Copy linkLink copied to clipboard!
Remove a label from a vm.
5.9. 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 vms with the label. |
5.9.1. add POST Copy linkLink copied to clipboard!
Add a label to a vm.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.9.2. list GET Copy linkLink copied to clipboard!
List all vms with the label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.10. 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. |
5.10.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 |
5.10.2. list GET Copy linkLink copied to clipboard!
Lists all labels present in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of labels to return. |
5.10.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of labels to return. If not specified all the labels are returned.
5.11. 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. |
5.11.1. get GET Copy linkLink copied to clipboard!
Retrieves details about the attached label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.11.2. remove DELETE Copy linkLink copied to clipboard!
Removes the label from an entity. Does not touch the label itself.
5.12. 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. |
5.12.1. add POST Copy linkLink copied to clipboard!
Attaches a label to an entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.12.2. list GET Copy linkLink copied to clipboard!
Lists all labels that are attached to an entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.13. AssignedCpuProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.13.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.13.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.14. AssignedCpuProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.14.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.14.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
5.14.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
5.15. AssignedDiskProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.15.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.15.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.16. AssignedDiskProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.16.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.16.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
5.16.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
5.17. AssignedNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.17.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.17.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.17.3. update PUT Copy linkLink copied to clipboard!
5.18. AssignedNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.18.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.18.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
5.18.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
5.19. 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. |
5.19.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. |
5.19.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of permissions. |
5.20. AssignedRoles Copy linkLink copied to clipboard!
Represents a roles sub-collection, for example scoped by user.
| Name | Summary |
|---|---|
|
|
5.20.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of roles to return. | |
|
| Out |
5.20.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of roles to return. If not specified all the roles are returned.
5.21. 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. |
5.21.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 |
|---|---|---|---|
|
| Out | The assigned tag. |
5.21.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. |
5.22. 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. |
5.22.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. |
5.22.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of tags to return. | |
|
| Out | The list of assigned tags. |
5.22.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of tags to return. If not specified all the tags are returned.
5.23. AssignedVnicProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.23.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.23.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.24. AssignedVnicProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.24.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.24.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
5.24.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
5.25. AttachedStorageDomain Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| This operation activates an attached storage domain. |
|
| This operation deactivates an attached storage domain. |
|
| |
|
|
5.25.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. |
5.25.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.
POST /ovirt-engine/api/datacenters/123/storagedomains/456/deactivate
POST /ovirt-engine/api/datacenters/123/storagedomains/456/deactivate
The deactivate 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 deactivation should be performed asynchronously. |
5.25.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.25.4. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.26. AttachedStorageDomains Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.26.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.26.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of storage domains to return. | |
|
| Out |
5.26.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of storage domains to return. If not specified all the storage domains are returned.
5.27. Balance Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.27.1. get GET Copy linkLink copied to clipboard!
5.27.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.28. Balances Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.28.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.28.2. list 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 | Sets the maximum number of balances to return. |
5.28.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of balances to return. If not specified all the balances are returned.
5.29. Bookmark Copy linkLink copied to clipboard!
A service to manage a bookmark.
| Name | Summary |
|---|---|
|
| Get a bookmark. |
|
| Remove a bookmark. |
|
| Update a bookmark. |
5.29.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. |
5.29.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. |
5.29.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>
5.30. Bookmarks Copy linkLink copied to clipboard!
A service to manage bookmarks.
| Name | Summary |
|---|---|
|
| Adding a new bookmark. |
|
| Listing all the available bookmarks. |
5.30.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. |
5.30.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of available bookmarks. | |
|
| In | Sets the maximum number of bookmarks to return. |
5.30.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of bookmarks to return. If not specified all the bookmarks are returned.
5.31. Cluster Copy linkLink copied to clipboard!
A service to manage specific cluster.
| Name | Summary |
|---|---|
|
| Get information about the cluster. |
|
| Removes cluster from the system. |
|
| |
|
| Updates information about the cluster. |
5.31.1. get GET Copy linkLink copied to clipboard!
Get information about the cluster.
An example of getting a cluster:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/123
5.31.2. remove DELETE Copy linkLink copied to clipboard!
Removes 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. |
5.31.3. resetemulatedmachine POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reset should be performed asynchronously. |
5.31.4. update PUT Copy linkLink copied to clipboard!
Updates information about the cluster.
Only specified fields are updated, others remain unchanged.
E.g. update cluster’s CPU:
PUT /ovirt-engine/api/clusters/123
PUT /ovirt-engine/api/clusters/123
With request body like:
<cluster>
<cpu>
<type>Intel Haswell-noTSX Family</type>
</cpu>
</cluster>
<cluster>
<cpu>
<type>Intel Haswell-noTSX Family</type>
</cpu>
</cluster>
5.32. 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. |
5.32.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 |
|---|---|---|---|
|
| Out | Retreived cluster level. |
5.33. 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. |
5.33.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.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved cluster levels. |
5.34. Clusters Copy linkLink copied to clipboard!
A service to manage clusters.
| Name | Summary |
|---|---|
|
| Creates a new cluster. |
|
|
5.34.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 attributes.
POST /ovirt-engine/api/clusters
POST /ovirt-engine/api/clusters
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.34.2. list GET Copy linkLink copied to clipboard!
| 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 | Sets the maximum number of clusters to return. | |
|
| In | A query string used to restrict the returned clusters. |
5.34.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.
5.34.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of clusters to return. If not specified all the clusters are returned.
5.35. Copyable Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.35.1. copy POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the copy should be performed asynchronously. |
5.36. CpuProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.36.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.36.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.36.3. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.37. CpuProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.37.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.37.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
5.37.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
5.38. DataCenter Copy linkLink copied to clipboard!
A service to manage a data center.
| Name | Summary |
|---|---|
|
| Get a data center. |
|
| Removes the data center. |
|
| Updates the data center. |
5.38.1. 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. |
5.38.2. 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. |
5.38.2.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.
5.38.3. 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. |
5.39. DataCenters Copy linkLink copied to clipboard!
A service to manage data centers.
| Name | Summary |
|---|---|
|
| Creates a new data center. |
|
| Lists the data centers. |
5.39.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. |
5.39.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.
| 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 | Sets the maximum number of data centers to return. | |
|
| In | A query string used to restrict the returned data centers. |
5.39.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.
5.39.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of data centers to return. If not specified all the data centers are returned.
5.40. Disk Copy linkLink copied to clipboard!
Manages a single disk.
| Name | Summary |
|---|---|
|
| This operation copies a disk to the specified storage domain. |
|
| |
|
| |
|
| Moves a disk to another storage domain. |
|
|
5.40.1. copy POST Copy linkLink copied to clipboard!
This operation copies a disk to the specified storage domain.
For example, copy of a disk can be facilitated using the following request:
POST /ovirt-engine/api/disks/123/copy
POST /ovirt-engine/api/disks/123/copy
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the copy should be performed asynchronously. | |
|
| In | ||
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In |
5.40.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 |
5.40.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.40.4. 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>
| 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 |
5.40.5. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.41. 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. |
5.41.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 |
5.41.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. |
5.41.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.
5.41.3. update PUT Copy linkLink copied to clipboard!
Update the disk attachment and the disk properties within it.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.42. 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. |
5.42.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 don’t 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 |
5.42.2. list GET Copy linkLink copied to clipboard!
List the disk that are attached to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.43. DiskProfile Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.43.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.43.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.43.3. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.44. DiskProfiles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.44.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.44.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
5.44.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
5.45. DiskSnapshot Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.45.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.45.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.46. DiskSnapshots Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.46.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of snapshots to return. | |
|
| Out |
5.46.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of snapshots to return. If not specified all the snapshots are returned.
5.47. 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. |
5.47.1. add POST Copy linkLink copied to clipboard!
Adds a new floating disk.
When creating a new floating Disk, the API requires the storage_domain, provisioned_size and format attributes.
To create a new floating disk with specified provisioned_size, format and name on a storage domain with an id e9fedf39-5edc-4e0a-8628-253f1b9c5693, send a request as follows:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disks
With a request body as follows:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The disk. |
5.47.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | List of retrieved disks. | |
|
| In | Sets the maximum number of disks to return. | |
|
| In | A query string used to restrict the returned disks. |
5.47.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.
5.47.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
5.48. 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. |
5.48.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. |
5.49. DomainGroup Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.49.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.50. DomainGroups Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.50.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Sets the maximum number of groups to return. | |
|
| In | A query string used to restrict the returned groups. |
5.50.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.
5.50.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of groups to return. If not specified all the groups are returned.
5.51. DomainUser Copy linkLink copied to clipboard!
A service to view a domain user in the system.
| Name | Summary |
|---|---|
|
| Gets the domain user information. |
5.51.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 |
|---|---|---|---|
|
| Out | The domain user. |
5.52. 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. |
5.52.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| 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. |
5.52.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.
5.52.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of users to return. If not specified all the users are returned.
5.53. 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. |
5.53.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of domains. | |
|
| In | Sets the maximum number of domains to return. |
5.53.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of domains to return. If not specified all the domains are returned.
5.54. 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. |
5.54.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A representation of Katello errata. | |
|
| In | Sets the maximum number of errata to return. |
5.54.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of errata to return. If not specified all the errata are returned.
5.55. 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. |
5.55.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 |
5.55.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. |
5.56. 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. |
|
|
5.56.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 |
5.56.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.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Indicates the identifier of the the first event that should be returned. | |
|
| In | Sets the maximum number of events to return. | |
|
| In | The events service provides search queries similar to other resource services. |
5.56.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.
5.56.2.2. from Copy linkLink copied to clipboard!
Indicates the identifier of the the first event that should be returned. The identifiers of events are strictly increasing, so when this parameter is used only the events with that identifiers equal or greater than the given value will be returned. For example, the following request will return only the events with identifiers greater or equal 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.
5.56.2.3. max Copy linkLink copied to clipboard!
Sets the maximum number of events to return. If not specified all the events are returned.
5.56.2.4. 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
5.56.3. undelete POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the un-delete should be performed asynchronously. |
5.57. ExternalComputeResource Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.57.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.58. ExternalComputeResources Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.58.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of resources to return. | |
|
| Out |
5.58.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of resources to return. If not specified all the resources are returned.
5.59. ExternalDiscoveredHost Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.59.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.60. ExternalDiscoveredHosts Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.60.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. |
5.60.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
5.61. ExternalHost Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.61.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.62. ExternalHostGroup Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.62.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.63. ExternalHostGroups Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.63.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of groups to return. |
5.63.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of groups to return. If not specified all the groups are returned.
5.64. ExternalHostProvider Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
5.64.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.64.2. importcertificates POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
5.64.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.64.4. testconnectivity POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
5.64.5. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.65. ExternalHostProviders Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.65.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.65.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
5.65.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
5.66. ExternalHosts Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.66.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. |
5.66.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
5.67. ExternalProvider Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.67.1. importcertificates POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
5.67.2. testconnectivity POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
5.68. ExternalProviderCertificate Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.68.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.69. ExternalProviderCertificates Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.69.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of certificates to return. |
5.69.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of certificates to return. If not specified all the certificates are returned.
5.70. 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. |
5.70.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 |
5.71. FenceAgent Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.71.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.71.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.71.3. update PUT Copy linkLink copied to clipboard!
5.72. FenceAgents Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.72.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.72.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of agents to return. |
5.72.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of agents to return. If not specified all the agents are returned.
5.73. File Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.73.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.74. Files Copy linkLink copied to clipboard!
Provides a way for clients to list available files.
This services is specifically targeted to ISO storage domains, which contain ISO images and virtual floppy disks (VFDs) that an administrator uploads.
The addition of a CDROM device to a virtual machine requires an ISO image from the files of an ISO storage domain.
| Name | Summary |
|---|---|
|
|
5.74.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Sets the maximum number of files to return. | |
|
| In | A query string used to restrict the returned files. |
5.74.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.
5.74.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of files to return. If not specified all the files are returned.
5.75. Filter Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.75.1. get GET Copy linkLink copied to clipboard!
5.75.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.76. Filters Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.76.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.76.2. list 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. | |
|
| Out | ||
|
| In | Sets the maximum number of filters to return. |
5.76.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of filters to return. If not specified all the filters are returned.
5.77. 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. |
5.77.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 |
5.77.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. |
5.77.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.
5.78. 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. |
5.78.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. |
5.78.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. |
5.78.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of bricks to return. |
5.78.3.1. max Copy linkLink copied to clipboard!
Sets the maximum number of bricks to return. If not specified all the bricks are returned.
5.78.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. |
5.78.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. |
5.78.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. |
5.78.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.
5.79. 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. |
5.79.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. |
5.79.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. |
5.79.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.79.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. |
5.79.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.
5.80. GlusterHooks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.80.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hooks to return. |
5.80.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of hooks to return. If not specified all the hooks are returned.
5.81. 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. |
5.81.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 |
|---|---|---|---|
|
| Out | Representation of the gluster volume. |
5.81.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. |
5.81.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. |
5.81.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.
5.81.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.
5.81.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. |
5.81.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. |
5.81.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>
5.81.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>
5.81.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. |
5.81.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.
5.81.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. |
5.81.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
5.81.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. |
5.81.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. |
5.82. 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. |
5.82.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. |
5.82.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Sets the maximum number of volumes to return. | |
|
| In | A query string used to restrict the returned volumes. | |
|
| Out |
5.82.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.
5.82.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of volumes to return. If not specified all the volumes are returned.
5.83. GraphicsConsole Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets the configuration of the graphics console. |
|
|
5.83.1. get GET Copy linkLink copied to clipboard!
Gets the configuration of the graphics console.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Use the following query to obtain the current run-time configuration of the graphics console. |
5.83.1.1. current Copy linkLink copied to clipboard!
Use the following query to obtain the current run-time configuration of the graphics console.
GET /ovit-engine/api/vms/{vm:id}/graphicsconsoles/{console:id}?current=true
GET /ovit-engine/api/vms/{vm:id}/graphicsconsoles/{console:id}?current=true
The default value is false.
5.83.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.84. GraphicsConsoles Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Lists all the configured graphics consoles of the virtual machine. |
5.84.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.84.2. list GET Copy linkLink copied to clipboard!
Lists all the configured graphics consoles of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Use the following query to obtain the current run-time configuration of the graphics consoles. | |
|
| In | Sets the maximum number of consoles to return. |
5.84.2.1. current Copy linkLink copied to clipboard!
Use the following query to obtain the current run-time configuration of the graphics consoles.
GET /ovirt-engine/api/vms/123/graphicsconsoles?current=true
GET /ovirt-engine/api/vms/123/graphicsconsoles?current=true
The default value is false.
5.84.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
5.85. Group Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.85.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.85.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.86. Groups Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add group from a directory service. |
|
|
5.86.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 |
5.86.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Sets the maximum number of groups to return. | |
|
| In | A query string used to restrict the returned groups. |
5.86.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.
5.86.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of groups to return. If not specified all the groups are returned.
5.87. Host Copy linkLink copied to clipboard!
A service to manage a host.
| Name | Summary |
|---|---|
|
| Activate the host for use, such as running 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. |
|
| Deactivate the host to perform maintenance tasks. |
|
| Enroll certificate of the host. |
|
| Controls host’s power management device. |
|
| Manually set a host as the storage pool manager (SPM). |
|
| Get the host details. |
|
| Install VDSM and related software on the host. |
|
| Discover iSCSI targets on the host, using the initiator details. |
|
| 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. |
|
| |
|
| Update the host properties. |
|
| Upgrade VDSM and selected software on the host. |
5.87.1. activate POST Copy linkLink copied to clipboard!
Activate the host for use, such as running virtual machines.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
5.87.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.
5.87.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/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
5.87.4. deactivate POST Copy linkLink copied to clipboard!
Deactivate 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. |
5.87.4.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.
5.87.5. enrollcertificate POST Copy linkLink copied to clipboard!
Enroll certificate of the host. Useful in case you get a warning that it is about to, or already expired.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the enrollment should be performed asynchronously. |
5.87.6. fence POST Copy linkLink copied to clipboard!
Controls host’s power management device.
For example, let’s assume you want to start the host. This can be done via:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the fencing should be performed asynchronously. | |
|
| In | ||
|
| Out |
5.87.7. forceselectspm POST Copy linkLink copied to clipboard!
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. |
5.87.8. get GET Copy linkLink copied to clipboard!
Get the host details.
5.87.9. install POST Copy linkLink copied to clipboard!
Install VDSM and related software on the host. 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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the installation should be performed asynchronously. | |
|
| In |
When set to | |
|
| In |
This | |
|
| In | When installing an oVirt node a image ISO file is needed. | |
|
| In |
The password of of the | |
|
| In | The SSH details used to connect to the host. | |
|
| In |
When set to |
5.87.9.1. deploy_hosted_engine Copy linkLink copied to clipboard!
When set to true it means this host should deploy also hosted engine components. Missing value is treated as true i.e deploy. Omitting this parameter means false and will perform no operation in hosted engine area.
5.87.9.2. undeploy_hosted_engine Copy linkLink copied to clipboard!
When set to true it means this host should un-deploy hosted engine components and this host will not function as part of the High Availability cluster. Missing value is treated as true i.e un-deploy Omitting this parameter means false and will perform no operation in hosted engine area.
5.87.10. iscsidiscover POST Copy linkLink copied to clipboard!
Discover iSCSI targets on the host, using the initiator details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the discovery should be performed asynchronously. | |
|
| In | The target iSCSI device. | |
|
| Out | The iSCSI targets. |
5.87.11. iscsilogin POST Copy linkLink copied to clipboard!
Login to iSCSI targets on the host, using the target details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the login should be performed asynchronously. | |
|
| In | The target iSCSI device. |
5.87.12. 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. |
5.87.13. 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. |
5.87.14. setupnetworks POST Copy linkLink copied to clipboard!
This method is used to change the configuration of the network interfaces of a host.
For example, lets assume that you have a host with three network interfaces eth0, eth1 and eth2 and that 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:
Note that 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"/>
Using the Python SDK the same can be done 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.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In |
5.87.15. unregisteredstoragedomainsdiscover POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the discovery should be performed asynchronously. | |
|
| In | ||
|
| Out |
5.87.16. 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>
5.87.17. upgrade POST Copy linkLink copied to clipboard!
Upgrade VDSM and selected software on the host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the upgrade should be performed asynchronously. |
5.88. 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. |
5.88.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 |
5.89. HostDevices Copy linkLink copied to clipboard!
A service to access host devices.
| Name | Summary |
|---|---|
|
| List the devices of a host. |
5.89.1. list GET Copy linkLink copied to clipboard!
List the devices of a host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of devices to return. |
5.89.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of devices to return. If not specified all the devices are returned.
5.90. HostHook Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.90.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.91. HostHooks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.91.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hooks to return. |
5.91.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of hooks to return. If not specified all the hooks are returned.
5.92. 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. |
5.92.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.92.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 |
5.93. HostNics Copy linkLink copied to clipboard!
A service to manage the network interfaces of a host.
| Name | Summary |
|---|---|
|
|
5.93.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
5.93.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
5.94. HostNumaNode Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.94.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.95. HostNumaNodes Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.95.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of nodes to return. | |
|
| Out |
5.95.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of nodes to return. If not specified all the nodes are returned.
5.96. HostStorage Copy linkLink copied to clipboard!
A service to manage host storages.
| Name | Summary |
|---|---|
|
| Get list of storages. |
5.96.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the status of the LUNs in the storage should be checked. | |
|
| Out | Retrieved list of storages. |
5.96.1.1. 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 :
5.97. Hosts Copy linkLink copied to clipboard!
A service that manages hosts.
| Name | Summary |
|---|---|
|
| Creates a new host. |
|
| Get a list of all available hosts. |
5.97.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.
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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
When set to | |
|
| In/Out | The host definition from which to create the new host is passed as parameter, and the newly created host is returned. | |
|
| In |
When set to |
5.97.1.1. deploy_hosted_engine Copy linkLink copied to clipboard!
When set to true it means this host should deploy also hosted engine components. Missing value is treated as true i.e deploy. Omitting this parameter means false and will perform no operation in hosted engine area.
5.97.1.2. undeploy_hosted_engine Copy linkLink copied to clipboard!
When set to true it means this host should un-deploy hosted engine components and this host will not function as part of the High Availability cluster. Missing value is treated as true i.e un-deploy. Omitting this parameter means false and will perform no operation in hosted engine area.
5.97.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 something like this:
| 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. | |
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. | |
|
| In | A query string used to restrict the returned hosts. |
5.97.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.
5.97.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
5.98. Icon Copy linkLink copied to clipboard!
A service to manage an icon (read-only).
| Name | Summary |
|---|---|
|
| Get an icon. |
5.98.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 |
|---|---|---|---|
|
| Out | Retrieved icon. |
5.99. Icons Copy linkLink copied to clipboard!
A service to manage icons.
| Name | Summary |
|---|---|
|
| Get a list of icons. |
5.99.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved list of icons. | |
|
| In | Sets the maximum number of icons to return. |
5.99.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of icons to return. If not specified all the icons are returned.
5.100. Image Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.100.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.100.2. import POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In | Cluster where the image should be imported. | |
|
| In | The disk which should be imported. | |
|
| In | Specify if template should be created from the imported disk. | |
|
| In | Storage domain where disk should be imported. | |
|
| In | Name of the template, which should be created. |
5.100.2.1. cluster Copy linkLink copied to clipboard!
Cluster where the image should be imported. Has effect only in case import_as_template parameter is set to true.
5.100.2.2. template Copy linkLink copied to clipboard!
Name of the template, which should be created. Has effect only in case import_as_template parameter is set to true.
5.101. 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 Section 5.102, “ImageTransfers” service, stating the image to transfer data to/from.
After doing that, the transfer is managed by this service.
E.g., for uploading to the disk image with id 52cb593f-837c-4633-a444-35a0a0383706, the client can use oVirt’s Python’s SDK as follows:
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 transfer’s phase is paused_system, then the session was not successfully established. One possible reason for that is that the ovirt-imageio-daemon is not running in the host that was selected for transfer. The transfer can be resumed by calling resume of the service that manages it.
If the session was successfully established - the returned transfer entity will contain the proxy_url and signed_ticket attributes, which the client needs to use in order to transfer the required data. The client can choose whatever technique and tool for sending the HTTPS request with the image’s data.
-
proxy_urlis the address of a proxy server to the image, to do I/O to. -
signed_ticketis the content that needs to be added to theAuthenticationheader in the HTTPS request, in order to perform a trusted communication.
For example, Python’s HTTPSConnection can be used in order to perform an upload, so an upload_headers dict is set for the upcoming upload:
upload_headers = {
'Authorization' : transfer.signed_ticket,
}
upload_headers = {
'Authorization' : transfer.signed_ticket,
}
Using Python’s HTTPSConnection, a new connection is established:
The specific content range being sent must be noted in the Content-Range HTTPS header. This can be used in order to split the transfer into several requests for a more flexible process.
For doing that, the client will have to repeatedly extend the transfer session to keep the channel open. Otherwise, the session will terminate and the transfer will get into paused_system phase, and HTTPS requests to the server will be rejected.
E.g., the client can iterate on chunks of the file, and send them to the proxy server while asking the service to extend the session:
When finishing the transfer, the user should call finalize. This will make the final adjustments and verifications for finishing the transfer process.
For example:
transfer_service.finalize()
transfer_service.finalize()
In case of an error, the transfer’s phase will be changed to finished_failure, and the disk’s status will be changed to Illegal. Otherwise it will be changed to finished_success, and the disk will be ready to be used. In both cases, the transfer entity will be removed shortly after.
| Name | Summary |
|---|---|
|
| 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. |
5.101.1. extend POST Copy linkLink copied to clipboard!
Extend the image transfer session.
5.101.2. 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.
5.101.3. get GET Copy linkLink copied to clipboard!
Get the image transfer entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.101.4. pause POST Copy linkLink copied to clipboard!
Pause the image transfer session.
5.101.5. 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:
5.102. ImageTransfers Copy linkLink copied to clipboard!
This service manages image transfers, for performing Image I/O API in oVirt. 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. |
5.102.1. add POST Copy linkLink copied to clipboard!
Add a new image transfer. An image needs to be specified in order to make a new transfer.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.102.2. list GET Copy linkLink copied to clipboard!
Retrieves the list of image transfers that are currently being performed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.103. Images Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.103.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of images to return. |
5.103.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of images to return. If not specified all the images are returned.
5.104. 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. |
5.104.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 |
|---|---|---|---|
|
| Out |
5.104.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. |
5.104.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 |
5.105. 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. |
5.105.1. get GET Copy linkLink copied to clipboard!
Gets network interface configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.105.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. |
5.105.3. update PUT Copy linkLink copied to clipboard!
Updates the network interface configuration of the instance type.
5.106. 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. |
5.106.1. add POST Copy linkLink copied to clipboard!
Add new network interface to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.106.2. list GET Copy linkLink copied to clipboard!
Lists all the configured network interface of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned templates. |
5.106.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
5.107. 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. |
5.107.1. get GET Copy linkLink copied to clipboard!
Gets watchdog configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.107.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. |
5.107.3. update PUT Copy linkLink copied to clipboard!
Updates the watchdog configuration of the instance type.
5.108. InstanceTypeWatchdogs Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Add new watchdog to the instance type. |
|
| Lists all the configured watchdogs of the instance type. |
5.108.1. add POST Copy linkLink copied to clipboard!
Add new watchdog to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.108.2. list GET Copy linkLink copied to clipboard!
Lists all the configured watchdogs of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of watchdogs to return. | |
|
| In | A query string used to restrict the returned templates. | |
|
| Out |
5.108.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
5.109. InstanceTypes Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new instance type. |
|
| Lists all existing instance types in the system. |
5.109.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 |
5.109.2. list GET Copy linkLink copied to clipboard!
Lists all existing instance types in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Sets the maximum number of instance types to return. | |
|
| In | A query string used to restrict the returned templates. |
5.109.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.
5.109.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of instance types to return. If not specified all the instance types are returned.
5.110. IscsiBond Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes of an existing iSCSI bond. |
|
| Updates an iSCSI bond. |
5.110.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.110.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. |
5.110.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>
5.111. IscsiBonds Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Create a new iSCSI bond on a data center. |
|
|
5.111.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 |
5.111.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of bonds to return. |
5.111.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of bonds to return. If not specified all the bonds are returned.
5.112. 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. |
5.112.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. |
5.112.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>
5.112.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 |
|---|---|---|---|
|
| Out | Retrieves the representation of the job. |
5.113. Jobs Copy linkLink copied to clipboard!
A service to manage jobs.
| Name | Summary |
|---|---|
|
| Add an external job. |
|
| Retrieves the representation of the jobs. |
5.113.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. |
5.113.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A representation of jobs. | |
|
| In | Sets the maximum number of jobs to return. |
5.113.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of jobs to return. If not specified all the jobs are returned.
5.114. 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. |
5.114.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | A representation of Katello errata. | |
|
| In | Sets the maximum number of errata to return. |
5.114.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of errata to return. If not specified all the errata are returned.
5.115. KatelloErratum Copy linkLink copied to clipboard!
A service to manage a Katello erratum.
| Name | Summary |
|---|---|
|
| Retrieves a Katello erratum. |
5.115.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. |
5.116. MacPool Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a MAC address pool. |
|
| Updates a MAC address pool. |
5.116.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.116.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. |
5.116.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:
5.117. MacPools Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new MAC address pool. |
|
|
5.117.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 |
5.117.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of pools to return. | |
|
| Out |
5.117.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of pools to return. If not specified all the pools are returned.
5.118. Measurable Copy linkLink copied to clipboard!
5.119. Moveable Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.119.1. move POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the move should be performed asynchronously. |
5.120. 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. |
5.120.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 |
|---|---|---|---|
|
| Out |
5.120.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.120.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>
5.121. NetworkAttachment Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.121.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.121.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.121.3. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.122. NetworkAttachments Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.122.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.122.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of attachments to return. |
5.122.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of attachments to return. If not specified all the attachments are returned.
5.123. 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. |
5.123.1. get GET Copy linkLink copied to clipboard!
Retrieves a representation of the network filter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.124. 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. |
5.124.1. list GET Copy linkLink copied to clipboard!
Retrieves the representations of the network filters.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.125. NetworkLabel Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a label from a logical network. |
5.125.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.125.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/labels/exemplary
DELETE /ovirt-engine/api/networks/123/labels/exemplary
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.126. NetworkLabels Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Attaches label to logical network. |
|
|
5.126.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/labels
POST /ovirt-engine/api/networks/123/labels
With a request body like this:
<label id="mylabel"/>
<label id="mylabel"/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.126.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of labels to return. |
5.126.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of labels to return. If not specified all the labels are returned.
5.127. 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. |
5.127.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>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.127.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Sets the maximum number of networks to return. | |
|
| Out | ||
|
| In | A query string used to restrict the returned networks. |
5.127.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.
5.127.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
5.128. OpenstackImage Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Imports a virtual machine from a Glance image storage domain. |
5.128.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.128.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 |
5.129. OpenstackImageProvider Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
5.129.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.129.2. importcertificates POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
5.129.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.129.4. testconnectivity POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
5.129.5. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.130. OpenstackImageProviders Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.130.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.130.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
5.130.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
5.131. OpenstackImages Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Lists the images of a Glance image storage domain. |
5.131.1. list GET Copy linkLink copied to clipboard!
Lists the images of a Glance image storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of images to return. |
5.131.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of images to return. If not specified all the images are returned.
5.132. OpenstackNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| This operation imports an external network into oVirt. |
5.132.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.132.2. import POST Copy linkLink copied to clipboard!
This operation imports an external network into oVirt. The network will be added to the data center specified.
| 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. |
5.132.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.
5.133. OpenstackNetworkProvider Copy linkLink copied to clipboard!
This service manages OpenStack network provider.
| Name | Summary |
|---|---|
|
| Returns the representation of the object managed by this service. |
|
| |
|
| Removes the provider. |
|
| |
|
| Updates the provider. |
5.133.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 |
|---|---|---|---|
|
| Out |
5.133.2. importcertificates POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
5.133.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. |
5.133.4. testconnectivity POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
5.133.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. |
5.134. OpenstackNetworkProviders Copy linkLink copied to clipboard!
This service manages OpenStack network providers.
| Name | Summary |
|---|---|
|
| The operation adds a new network provider to the system. |
|
|
5.134.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 |
5.134.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
5.134.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
5.135. OpenstackNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.135.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
5.135.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
5.136. OpenstackSubnet Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.136.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.136.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.137. OpenstackSubnets Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.137.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.137.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of sub-networks to return. | |
|
| Out |
5.137.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of sub-networks to return. If not specified all the sub-networks are returned.
5.138. OpenstackVolumeAuthenticationKey Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.138.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.138.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.138.3. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.139. OpenstackVolumeAuthenticationKeys Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.139.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.139.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of keys to return. |
5.139.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of keys to return. If not specified all the keys are returned.
5.140. OpenstackVolumeProvider Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
5.140.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.140.2. importcertificates POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
5.140.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.140.4. testconnectivity POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
5.140.5. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.141. OpenstackVolumeProviders Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Adds a new volume provider. |
|
| Retrieves the list of volume providers. |
5.141.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 |
5.141.2. list GET Copy linkLink copied to clipboard!
Retrieves the list of volume providers.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
5.141.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of providers to return. If not specified all the providers are returned.
5.142. OpenstackVolumeType Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.142.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.143. OpenstackVolumeTypes Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.143.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of volume types to return. | |
|
| Out |
5.143.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of volume types to return. If not specified all the volume types are returned.
5.144. OperatingSystem Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.144.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.145. OperatingSystems Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.145.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
5.145.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
5.146. Permission Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.146.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.146.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.147. 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. |
5.147.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 |
|---|---|---|---|
|
| Out | The permit of the role. |
5.147.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. |
5.148. 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. |
5.148.1. add POST Copy linkLink copied to clipboard!
Adds a permit to the role. The permit name can be retrieved from the Section 5.33, “ClusterLevels” 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. |
5.148.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of permits to return. | |
|
| Out | List of permits. |
5.148.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of permits to return. If not specified all the permits are returned.
5.149. Qos Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.149.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.149.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.149.3. update PUT Copy linkLink copied to clipboard!
5.150. Qoss Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.150.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.150.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of QoS descriptors to return. | |
|
| Out |
5.150.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of QoS descriptors to return. If not specified all the descriptors are returned.
5.151. Quota Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves a quota. |
|
| Delete a quota. |
|
| Updates a quota. |
5.151.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 |
|---|---|---|---|
|
| Out |
5.151.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. |
5.151.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
5.152. QuotaClusterLimit Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.152.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.152.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.153. QuotaClusterLimits Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.153.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.153.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of limits to return. |
5.153.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of limits to return. If not specified all the limits are returned.
5.154. QuotaStorageLimit Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.154.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.154.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. |
5.155. QuotaStorageLimits Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.155.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.155.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of limits to return. |
5.155.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of limits to return. If not specified all the limits are returned.
5.156. Quotas Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new quota. |
|
| Lists quotas of a data center |
5.156.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 |
5.156.2. list GET Copy linkLink copied to clipboard!
Lists quotas of a data center
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of quota descriptors to return. | |
|
| Out |
5.156.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of quota descriptors to return. If not specified all the descriptors are returned.
5.157. Role Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Get the role. |
|
| Removes the role. |
|
| Updates a role. |
5.157.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 |
|---|---|---|---|
|
| Out | Retrieved role. |
5.157.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. |
5.157.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>
5.158. Roles Copy linkLink copied to clipboard!
Provides read-only access to the global set of roles
| Name | Summary |
|---|---|
|
| Create a new role. |
|
| List roles. |
5.158.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. |
5.158.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of roles to return. | |
|
| Out | Retrieved list of roles. |
5.158.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of roles to return. If not specified all the roles are returned.
5.159. SchedulingPolicies Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.159.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.159.2. list 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 | Sets the maximum number of policies to return. | |
|
| Out |
5.159.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of policies to return. If not specified all the policies are returned.
5.160. SchedulingPolicy Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.160.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. | |
|
| Out |
5.160.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.160.3. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.161. SchedulingPolicyUnit Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.161.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. | |
|
| Out |
5.161.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.162. SchedulingPolicyUnits Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.162.1. list 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 | Sets the maximum number of policy units to return. | |
|
| Out |
5.162.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of policy units to return. If not specified all the policy units are returned.
5.163. Snapshot Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Restores a virtual machine snapshot. |
5.163.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.163.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.163.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/>
5.164. SnapshotCdrom Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.164.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.165. SnapshotCdroms Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.165.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of CDROMS to return. |
5.165.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of CDROMS to return. If not specified all the CDROMS are returned.
5.166. SnapshotDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.166.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.167. SnapshotDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.167.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of disks to return. |
5.167.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
5.168. SnapshotNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.168.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.169. SnapshotNics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.169.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
5.169.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
5.170. Snapshots Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a virtual machine snapshot. |
|
|
5.170.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>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.170.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of snapshots to return. | |
|
| Out |
5.170.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of snapshots to return. If not specified all the snapshots are returned.
5.171. SshPublicKey Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.171.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.171.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.171.3. update PUT Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
5.172. SshPublicKeys Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.172.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.172.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of keys to return. |
5.172.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of keys to return. If not specified all the keys are returned.
5.173. Statistic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.173.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.174. Statistics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Retrieves a list of statistics. |
5.174.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of statistics to return. | |
|
| Out |
5.174.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of statistics to return. If not specified all the statistics are returned.
5.175. Step Copy linkLink copied to clipboard!
A service to manage a step.
| Name | Summary |
|---|---|
|
| Marks an external step execution as ended. |
|
| Retrieves a step. |
5.175.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>
5.175.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 |
|---|---|---|---|
|
| Out | Retrieves the representation of the step. |
5.176. 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. |
5.176.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. |
5.176.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of steps to return. | |
|
| Out | A representation of steps. |
5.176.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of steps to return. If not specified all the steps are returned.
5.177. Storage Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.177.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the status of the LUNs in the storage should be checked. | |
|
| Out |
5.177.1.1. 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 :
5.178. StorageDomain Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| This operation refreshes the LUN size. |
|
| Removes the storage domain. |
|
| Updates a storage domain. |
|
|
This operation forces the update of the |
5.178.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. | |
|
| Out |
5.178.2. isattached POST Copy linkLink copied to clipboard!
5.178.3. 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. |
5.178.4. 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 different setup, with all the data on it. If the storage isn’t accessible the operation will fail.
If the destroy parameter is true then the operation will always succeed, even if the storage isn’t 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 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 isn’t 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 what host should be used to remove the storage domain. |
5.178.4.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 isn’t 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.
5.178.4.2. host Copy linkLink copied to clipboard!
Indicates what host should be used to remove the storage domain.
This parameter is mandatory, and it can 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
5.178.5. update PUT Copy linkLink copied to clipboard!
Updates a storage domain.
Not all of the StorageDomain's attributes are updatable post-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 |
5.178.6. 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 meta-data of virtual machines and disks that reside in the storage domain. This meta-data 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 |
5.179. StorageDomainContentDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.179.1. get GET Copy linkLink copied to clipboard!
5.180. StorageDomainContentDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.180.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| Out | ||
|
| In | Sets the maximum number of disks to return. | |
|
| In | A query string used to restrict the returned disks. |
5.180.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.
5.180.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
5.181. StorageDomainServerConnection Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Detaches a storage connection from storage. |
5.181.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.181.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. |
5.182. StorageDomainServerConnections Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.182.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.182.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of connections to return. |
5.182.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of connections to return. If not specified all the connections are returned.
5.183. StorageDomainTemplate Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
5.183.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.183.2. import POST Copy linkLink copied to clipboard!
5.183.3. register POST Copy linkLink copied to clipboard!
5.183.4. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.184. StorageDomainTemplates Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.184.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of templates to return. | |
|
| Out |
5.184.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of templates to return. If not specified all the templates are returned.
5.185. 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. |
5.185.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.185.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:
| 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 |
5.185.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.
5.185.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.
5.185.3. register POST Copy linkLink copied to clipboard!
5.185.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. |
5.186. 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. |
5.186.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. |
5.187. 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. |
5.187.1. list GET Copy linkLink copied to clipboard!
List the disks that are attached to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.188. 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 |
|---|---|
|
|
5.188.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of virtual machines to return. | |
|
| Out |
5.188.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of virtual machines to return. If not specified all the virtual machines are returned.
5.189. StorageDomains Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Adds a new storage domain. |
|
|
5.189.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 oVirt 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 by using a host with an id 123, send a request as follows:
POST /ovirt-engine/api/storagedomains
POST /ovirt-engine/api/storagedomains
With a request body as follows:
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 |
5.189.2. list GET Copy linkLink copied to clipboard!
| 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 | Sets the maximum number of storage domains to return. | |
|
| In | A query string used to restrict the returned storage domains. | |
|
| Out |
5.189.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.
5.189.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.
5.190. StorageServerConnection Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a storage connection. |
|
| Updates the storage connection. |
5.190.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.190.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). |
5.190.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
5.190.3. update PUT Copy linkLink copied to clipboard!
Updates the storage connection.
For example, to change the address of the 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:
| 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. |
5.190.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.
5.191. StorageServerConnectionExtension Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update a storage server connection extension for the given host. |
5.191.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.191.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.191.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 |
5.192. StorageServerConnectionExtensions Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new storage server connection extension for the given host. |
|
|
5.192.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 |
5.192.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of extensions to return. |
5.192.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of extensions to return. If not specified all the extensions are returned.
5.193. StorageServerConnections Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new storage connection. |
|
|
5.193.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 |
5.193.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of connections to return. |
5.193.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of connections to return. If not specified all the connections are returned.
5.194. 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. |
|
|
5.194.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 |
5.194.2. reloadconfigurations POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reload should be performed asynchronously. |
5.195. 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. |
5.195.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. |
5.195.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of permissions. |
5.196. 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. |
5.196.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 |
|---|---|---|---|
|
| Out | The tag. |
5.196.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. |
5.196.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>
5.197. 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. |
5.197.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. |
5.197.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)
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of tags to return. | |
|
| Out | List of all tags in the system. |
5.197.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of tags to return. If not specified all the tags are returned.
5.198. 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. |
5.198.1. export POST Copy linkLink copied to clipboard!
Exports a template to the data center export domain.
For example, the operation can be facilitated using 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>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the existing templates with the same name should be overwritten. | |
|
| In | Specifies the destination export storage domain. |
5.198.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.
5.198.2. get GET Copy linkLink copied to clipboard!
Returns the information about this template or template version.
5.198.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 remove should be performed asynchronously. |
5.198.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 to 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>
5.199. 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. |
5.199.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. |
5.199.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>
5.200. TemplateCdroms Copy linkLink copied to clipboard!
Lists the CD-ROM devices of a template.
| Name | Summary |
|---|---|
|
|
5.200.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of CD-ROM devices of the template. | |
|
| In | Sets the maximum number of CD-ROMs to return. |
5.200.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of CD-ROMs to return. If not specified all the CD-ROMs are returned.
5.201. TemplateDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
5.201.1. copy POST Copy linkLink copied to clipboard!
5.201.2. export POST Copy linkLink copied to clipboard!
5.201.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.201.4. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.202. 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. |
5.202.1. get GET Copy linkLink copied to clipboard!
Returns the details of the attachment.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.202.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
5.203. 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. |
5.203.1. list GET Copy linkLink copied to clipboard!
List the disks that are attached to the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.204. TemplateDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.204.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of disks to return. |
5.204.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
5.205. TemplateNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.205.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.205.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.205.3. update PUT Copy linkLink copied to clipboard!
5.206. TemplateNics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.206.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.206.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
5.206.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
5.207. TemplateWatchdog Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
5.207.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.207.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.207.3. update PUT Copy linkLink copied to clipboard!
5.208. TemplateWatchdogs Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.208.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.208.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of watchdogs to return. | |
|
| Out |
5.208.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
5.209. 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. |
5.209.1. add POST Copy linkLink copied to clipboard!
Creates a new template.
This requires the name and vm elements. Identify the virtual machine with the id name attributes.
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>
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.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Specifies if the permissions of the virtual machine should be copied to the template. | |
|
| In/Out | The information about the template or template version. |
5.209.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 values 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:
5.209.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.
| 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 | 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. |
5.209.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.
5.209.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of templates to return. If not specified all the templates are returned.
5.210. UnmanagedNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.210.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.210.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.211. UnmanagedNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.211.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
5.211.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
5.212. 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 Section 5.213, “Users”.
| Name | Summary |
|---|---|
|
| Gets the system user information. |
|
| Removes the system user. |
5.212.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 |
|---|---|---|---|
|
| Out | The system user. |
5.212.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. |
5.213. 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. |
5.213.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 |
5.213.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
Indicates if the search performed using the | |
|
| In | Sets the maximum number of users to return. | |
|
| In | A query string used to restrict the returned users. | |
|
| Out | The list of users. |
5.213.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.
5.213.2.2. max Copy linkLink copied to clipboard!
Sets the maximum number of users to return. If not specified all the users are returned.
5.214. VirtualFunctionAllowedNetwork Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.214.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.214.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.215. VirtualFunctionAllowedNetworks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.215.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.215.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
5.215.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of networks to return. If not specified all the networks are returned.
5.216. Vm Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| This operation stops any migration of a virtual machine to another physical host. |
|
| |
|
| |
|
| Detaches a virtual machine from a pool. |
|
| Export a virtual machine to an export domain. |
|
| Freeze 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. |
|
| |
|
| This operation migrates a virtual machine to another physical host. |
|
| |
|
| This operation sends a reboot request to a virtual machine. |
|
| Removes the virtual machine, including the virtual disks attached to it. |
|
| |
|
| 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. |
|
| Thaw virtual machine file systems. |
|
| Generates a time-sensitive authentication token for accessing a virtual machine’s display. |
|
| |
|
|
5.216.1. 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, so the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should cancelled asynchronously. |
5.216.2. clone POST Copy linkLink copied to clipboard!
5.216.3. commitsnapshot POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the snapshots should be committed asynchronously. |
5.216.4. 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, so the request body should contain an empty action:
<action/>
<action/>
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the detach should be performed asynchronously. |
5.216.5. export POST Copy linkLink copied to clipboard!
Export a virtual machine to an export domain.
For example to export virtual machine 123 to the export domain myexport, send a request like this:
POST /ovirt-engine/api/vms/123/export
POST /ovirt-engine/api/vms/123/export
With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the export should be performed asynchronously. | |
|
| In |
The | |
|
| In |
The | |
|
| In |
5.216.6. freezefilesystems POST Copy linkLink copied to clipboard!
Freeze 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. |
5.216.7. get GET Copy linkLink copied to clipboard!
Retrieves the description of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all 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 if the returned result describes the virtual machine as it is currently running, or if describes it with the modifications that have already been performed but that will have effect only when it is restarted. | |
|
| Out | Description of the virtual machine. |
5.216.7.1. all_content Copy linkLink copied to clipboard!
Indicates if all 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' send a request like this:
GET /ovirt-engine/api/vms/123?all_content=true
GET /ovirt-engine/api/vms/123?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.
5.216.7.2. next_run Copy linkLink copied to clipboard!
Indicates if the returned result describes the virtual machine as it is currently running, or if describes it with the modifications that have already been performed but that will have effect only when it is restarted. By default the values is false.
If the parameter is included in the request, but without a value, it is assumed that the value is true, so 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
5.216.8. 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.
This is how an example request would look like:
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. |
5.216.9. maintenance POST Copy linkLink copied to clipboard!
5.216.10. migrate POST Copy linkLink copied to clipboard!
This operation migrates a virtual machine to another physical host.
POST /ovirt-engine/api/vms/123/migrate
POST /ovirt-engine/api/vms/123/migrate
One can 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 the virtual machine should migrate although it might be defined as non migratable. | |
|
| In | Specifies a specific host the virtual machine should migrate to. |
5.216.10.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.
5.216.10.2. force Copy linkLink copied to clipboard!
Specifies the virtual machine should migrate although it might be defined as non migratable. This is an optional parameter. By default, it is set to false.
5.216.10.3. host Copy linkLink copied to clipboard!
Specifies a specific host the virtual machine should migrate to. This is an optional parameters. By default, the oVirt Engine 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.
5.216.11. previewsnapshot POST Copy linkLink copied to clipboard!
5.216.12. reboot POST Copy linkLink copied to clipboard!
This operation sends a reboot request to a virtual machine.
POST /ovirt-engine/api/vms/123/reboot
POST /ovirt-engine/api/vms/123/reboot
The reboot 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 reboot should be performed asynchronously. |
5.216.13. 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 send a request like this:
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. |
5.216.13.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.
5.216.14. reordermacaddresses POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
5.216.15. shutdown POST Copy linkLink copied to clipboard!
This operation sends a shutdown request to a virtual machine.
POST /ovirt-engine/api/vms/123/shutdown
POST /ovirt-engine/api/vms/123/shutdown
The shutdown 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 shutdown should be performed asynchronously. |
5.216.16. 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 action should be performed asynchronously. | |
|
| 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 | The definition of the virtual machine for this specific run. |
5.216.16.1. pause Copy linkLink copied to clipboard!
If set to true, start the virtual machine in paused mode. Default is false.
5.216.16.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 this for details.
5.216.16.3. use_sysprep Copy linkLink copied to clipboard!
If set to true, the initialization type is set to Sysprep. The default value is false. See this for details.
5.216.16.4. 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 will be powered off, this definition will be reverted.
5.216.17. stop POST Copy linkLink copied to clipboard!
This operation forces a virtual machine to power-off.
POST /ovirt-engine/api/vms/123/stop
POST /ovirt-engine/api/vms/123/stop
The stop 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 action should be performed asynchronously. |
5.216.18. 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.
POST /ovirt-engine/api/vms/123/suspend
POST /ovirt-engine/api/vms/123/suspend
The suspend 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 action should be performed asynchronously. |
5.216.19. thawfilesystems POST Copy linkLink copied to clipboard!
Thaw 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 action should be performed asynchronously. |
5.216.20. ticket POST Copy linkLink copied to clipboard!
Generates a time-sensitive authentication token for accessing a virtual machine’s display.
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.
In any case, the response specifies the actual ticket value and expiry used.
5.216.21. undosnapshot POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
5.216.22. update PUT Copy linkLink copied to clipboard!
| 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 |
5.216.22.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.
5.217. 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. |
5.217.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. |
5.217.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>
5.218. 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. |
5.218.1. list GET Copy linkLink copied to clipboard!
Returns a list of applications installed in the virtual machine.
| 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 | Sets the maximum number of applications to return. |
5.218.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:
5.218.1.2. max Copy linkLink copied to clipboard!
Sets the maximum number of applications to return. If not specified all the applications are returned.
5.219. 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. |
5.219.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. |
5.219.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.
5.219.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 don’t 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. |
5.219.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.
5.220. 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 |
|---|---|
|
| Returns the list of CDROM devices of the virtual machine. |
5.220.1. list GET Copy linkLink copied to clipboard!
Returns the list of CDROM devices of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of CDROM devices of the virtual machine. | |
|
| In | Sets the maximum number of CDROMs to return. |
5.220.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of CDROMs to return. If not specified all the CDROMs are returned.
5.221. VmDisk Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| Detach the disk from the virtual machine. |
|
|
5.221.1. activate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
5.221.2. deactivate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. |
5.221.3. export POST Copy linkLink copied to clipboard!
5.221.4. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.221.5. move POST Copy linkLink copied to clipboard!
5.221.6. 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. |
5.221.7. update PUT Copy linkLink copied to clipboard!
5.222. VmDisks Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.222.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.222.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of disks to return. |
5.222.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of disks to return. If not specified all the disks are returned.
5.223. VmGraphicsConsole Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Gets the configuration of the graphics console. |
|
| |
|
|
5.223.1. get GET Copy linkLink copied to clipboard!
Gets the configuration of the graphics console.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Use the following query to obtain the current run-time configuration of the graphics console. |
5.223.1.1. current Copy linkLink copied to clipboard!
Use the following query to obtain the current run-time configuration of the graphics console.
GET /ovit-engine/api/vms/{vm:id}/graphicsconsoles/{console:id}?current=true
GET /ovit-engine/api/vms/{vm:id}/graphicsconsoles/{console:id}?current=true
The default value is false.
5.223.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 |
5.223.3. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.224. 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. |
5.224.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. |
5.224.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. |
5.225. 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. |
5.225.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. |
5.225.2. list GET Copy linkLink copied to clipboard!
List the host devices assigned to given virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved list of host devices attached to given virtual machine. | |
|
| In | Sets the maximum number of devices to return. |
5.225.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of devices to return. If not specified all the devices are returned.
5.226. VmNic Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| Removes the NIC. |
|
| Updates the NIC. |
5.226.1. activate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
5.226.2. deactivate POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. |
5.226.3. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.226.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. |
5.226.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> </nic>
<nic>
<name>mynic</name>
<interface>e1000</interface>
</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
5.227. VmNics Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Adds a NIC to the virtual machine. |
|
|
5.227.1. add POST Copy linkLink copied to clipboard!
Adds a NIC to the virtual machine.
The following example adds a network interface named mynic using virtio and the ovirtmgmt network to the virtual machine.
POST /ovirt-engine/api/vms/123/nics
POST /ovirt-engine/api/vms/123/nics
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 |
5.227.2. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
5.227.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
5.228. VmNumaNode Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| Removes a virtual NUMA node. |
|
| Updates a virtual NUMA node. |
5.228.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.228.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
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.228.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 |
5.229. 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. |
5.229.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 |
5.229.2. list GET Copy linkLink copied to clipboard!
Lists virtual NUMA nodes of a virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of nodes to return. | |
|
| Out |
5.229.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of nodes to return. If not specified all the nodes are returned.
5.230. 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. |
5.230.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. |
5.230.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:
5.230.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. |
5.230.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.
5.231. 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. |
5.231.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. |
5.231.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:
| 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 | Sets the maximum number of pools to return. | |
|
| Out | Retrieved pools. | |
|
| In | A query string used to restrict the returned pools. |
5.231.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.
5.231.2.2. 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.
5.232. VmReportedDevice Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.232.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.233. VmReportedDevices Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.233.1. list GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of devices to return. | |
|
| Out |
5.233.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of devices to return. If not specified all the devices are returned.
5.234. VmSession Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
5.234.1. get GET Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.235. VmSessions Copy linkLink copied to clipboard!
Provides information about virtual machine user sessions.
| Name | Summary |
|---|---|
|
| Lists all user sessions for this virtual machine. |
5.235.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:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of sessions to return. | |
|
| Out |
5.235.1.1. max Copy linkLink copied to clipboard!
Sets the maximum number of sessions to return. If not specified all the sessions are returned.
5.236. 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. |
5.236.1. get GET Copy linkLink copied to clipboard!
Returns the information about the watchdog.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the watchdog. |
5.236.1.1. 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:
5.236.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. |
5.236.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. |
5.236.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.
5.237. 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. |
5.237.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. |
5.237.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.
5.237.2. list GET Copy linkLink copied to clipboard!
The list of watchdogs of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of watchdogs to return. | |
|
| Out | The information about the watchdog. |
5.237.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
5.237.2.2. 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:
5.238. Vms Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Creates a new virtual machine. |
|
|
5.238.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 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/Out |
5.238.1.1. 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.
5.238.1.2. 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:
5.238.2. list GET Copy linkLink copied to clipboard!
| 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 | The maximum number of results to return. | |
|
| In | A query string used to restrict the returned virtual machines. | |
|
| Out |
5.238.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.
5.238.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.
5.239. 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. |
5.239.1. get GET Copy linkLink copied to clipboard!
Retrieves details about a vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
5.239.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. |
5.239.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. |
5.240. 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. |
5.240.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 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. |
5.240.2. list GET Copy linkLink copied to clipboard!
List all vNIC profiles.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out | The list of all vNIC profiles. |
5.240.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
5.241. Weight Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.241.1. get GET Copy linkLink copied to clipboard!
5.241.2. remove DELETE Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
5.242. Weights Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
5.242.1. add POST Copy linkLink copied to clipboard!
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
5.242.2. list 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 | Sets the maximum number of weights to return. | |
|
| Out |
5.242.2.1. max Copy linkLink copied to clipboard!
Sets the maximum number of weights to return. If not specified all the weights are returned.
Chapter 6. Types Copy linkLink copied to clipboard!
This section enumerates all the data types that are available in the API.
6.1. AccessProtocol enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.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. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.3. AffinityGroup struct Copy linkLink copied to clipboard!
An affinity group represents a group of virtual machines with a defined relationship.
| Name | Type | Summary |
|---|---|---|
|
| 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. | |
|
| 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. |
6.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. | |
|
| A unique identifier. | |
|
| A human-readable name in plain text. | |
|
|
The |
6.4.1. 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.
6.5. 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. |
6.5.1. host Copy linkLink copied to clipboard!
Reference to the host service. Each fence agent belongs to a single host.
6.6. AgentConfiguration struct Copy linkLink copied to clipboard!
6.7. 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. |
6.8. 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. |
6.9. 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.
6.10. Application 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 |
|---|---|---|
|
|
6.11. Architecture enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.12. 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 |
|---|---|---|
|
|
6.13. AutoNumaStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.14. 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 |
|---|---|---|
|
| ||
|
|
6.15. Bios struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.16. BlockStatistic struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.17. 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. |
6.17.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, also called dynamic link aggregation - Wikipedia, Presentation. 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.
6.17.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.
6.17.3. slaves Copy linkLink copied to clipboard!
A list of slave NICs for a bonded interface. Only required when adding bonded interfaces.
6.18. Bookmark struct Copy linkLink copied to clipboard!
6.19. Boot struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.20. BootDevice enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.22. 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. |
|
| Statically-defined address, mask and gateway. |
6.22.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.
6.22.2. dhcp Copy linkLink copied to clipboard!
Dynamic host configuration protocol.
Please refer to this wikipedia article for more information.
6.23. BrickProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
| Name | Type | Summary |
|---|---|---|
|
|
6.24. 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.24.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.
6.25. 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. | |
|
| ||
|
|
6.26. CloudInit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.27. Cluster struct Copy linkLink copied to clipboard!
Type representation of a cluster.
A JSON representation of a cluster
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Free text containing comments about this object. | |
|
| ||
|
| Custom scheduling policy properties of the cluster. | |
|
| A human-readable description in plain text. | |
|
| ||
|
| ||
|
| Custom fencing policy can be defined for a cluster. | |
|
| ||
|
| ||
|
| A unique identifier. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Type of switch to be used by all networks in given cluster. | |
|
| ||
|
| ||
|
| ||
|
| The compatibility version of the cluster. | |
|
|
6.27.1. 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.
6.27.2. fencing_policy Copy linkLink copied to clipboard!
Custom fencing policy can be defined for a cluster.
Here is an example:
PUT /ovirt-engine/api/cluster/123
PUT /ovirt-engine/api/cluster/123
With request body:
6.27.3. 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:
To update the compatibility version, use:
PUT /ovirt-engine/api/clusters/123
PUT /ovirt-engine/api/clusters/123
With a request body:
In order to update the cluster compatibility version, all hosts in the cluster must support the new compatibility version.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| Reference to the default scheduling policy used by this cluster. |
6.27.4. 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.
6.28. 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. |
6.29. Configuration struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| The document describing the virtual machine. | |
|
|
6.29.1. data Copy linkLink copied to clipboard!
The document describing the virtual machine.
Example of the OVF document:
6.30. ConfigurationType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.31. Console struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.32. Core struct Copy linkLink copied to clipboard!
6.33. Cpu struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.34. CpuMode enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.35. 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 |
|---|---|---|
|
| ||
|
| ||
|
|
6.36. CpuTopology struct Copy linkLink copied to clipboard!
6.37. CpuTune struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.38. 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 |
6.39. CreationStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
6.40. CustomProperty struct Copy linkLink copied to clipboard!
6.41. 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. |
6.41.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. | |
|
| 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. |
6.42. DataCenterStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
6.43. 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.43.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.
6.44. 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. | |
|
| ||
|
| Indicates if the disk is marked as bootable. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The underlying storage format. | |
|
| A unique identifier. | |
|
| ||
|
| 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 not cause virtual machine to be paused and, instead, disk errors should be propagated to the the guest operating system. | |
|
| The virtual size of the disk, in bytes. | |
|
| Indicates if the disk is in read-only mode. | |
|
| ||
|
| 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. | |
|
| ||
|
| ||
|
| 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. |
6.44.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, the server accepts requests that don’t contain this attribute, but the effect is then 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 this attribute with the desired value.
6.44.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, and it will be smaller than the provisioned size for disks that use the cow format.
6.44.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.
6.44.4. 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.
6.44.5. provisioned_size Copy linkLink copied to clipboard!
The virtual size of the disk, in bytes.
This attribute is mandatory when creating a new disk.
6.44.7. 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.44.8. statistics Copy linkLink copied to clipboard!
Statistics exposed by the disk. For example:
These statistics aren’t directly included when the disk is retrieved, only a link. To obtain the statistics follow that link:
GET /ovirt-engine/api/disks/123/statistics
GET /ovirt-engine/api/disks/123/statistics
6.44.9. 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.
6.44.10. 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.
6.45. DiskAttachment struct Copy linkLink copied to clipboard!
Describes how a disk is attached to a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| This flag indicates if 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. |
6.45.1. active Copy linkLink copied to clipboard!
This flag indicates if 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.
6.45.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.
6.46. 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. |
6.47. DiskInterface enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
6.48. 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 |
|---|---|---|
|
| ||
|
| ||
|
|
6.49. 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. | |
|
| ||
|
| Indicates if the disk is marked as bootable. | |
|
| Free text containing comments about this object. | |
|
| A human-readable description in plain text. | |
|
| The underlying storage format. | |
|
| A unique identifier. | |
|
| ||
|
| 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 not cause virtual machine to be paused and, instead, disk errors should be propagated to the the guest operating system. | |
|
| The virtual size of the disk, in bytes. | |
|
| Indicates if the disk is in read-only mode. | |
|
| ||
|
| 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. | |
|
| ||
|
| ||
|
| 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. |
6.49.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, the server accepts requests that don’t contain this attribute, but the effect is then 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 this attribute with the desired value.
6.49.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, and it will be smaller than the provisioned size for disks that use the cow format.
6.49.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.
6.49.4. 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.
6.49.5. provisioned_size Copy linkLink copied to clipboard!
The virtual size of the disk, in bytes.
This attribute is mandatory when creating a new disk.
6.49.7. 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.49.8. statistics Copy linkLink copied to clipboard!
Statistics exposed by the disk. For example:
These statistics aren’t directly included when the disk is retrieved, only a link. To obtain the statistics follow that link:
GET /ovirt-engine/api/disks/123/statistics
GET /ovirt-engine/api/disks/123/statistics
6.49.9. 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.
6.49.10. 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.
6.50. DiskStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.51. DiskStorageType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.52. DiskType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.53. Display struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.54. DisplayType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.55. Dns struct Copy linkLink copied to clipboard!
Represents the DNS resolver configuration.
6.56. 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. |
6.56.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.
6.57. 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. |
6.57.1. error Copy linkLink copied to clipboard!
The external entity status is erroneous. This might require a moderate attention.
6.57.2. failure Copy linkLink copied to clipboard!
The external entity has an issue that causes failures. This might require immediate attention.
6.58. EntityProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.59. ErrorHandling struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.60. 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. | |
|
| A human-readable name in plain text. | |
|
| Free text identifying the origin of the event. | |
|
| The event severity. | |
|
| The event time. |
6.60.1. correlation_id Copy linkLink copied to clipboard!
The event correlation identifier. Used in order to correlate several events together.
6.60.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.
| 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. |
6.60.3. cluster Copy linkLink copied to clipboard!
Reference to the cluster service. Event can be associated with a cluster.
6.60.4. data_center Copy linkLink copied to clipboard!
Reference to the data center service. Event can be associated with a data center.
6.60.5. host Copy linkLink copied to clipboard!
Reference to the host service. Event can be associated with a host.
6.60.6. storage_domain Copy linkLink copied to clipboard!
Reference to the storage domain service. Event can be associated with a storage domain.
6.60.7. template Copy linkLink copied to clipboard!
Reference to the template service. Event can be associated with a template.
6.60.8. user Copy linkLink copied to clipboard!
Reference to the user service. Event can be associated with a user.
6.60.9. vm Copy linkLink copied to clipboard!
Reference to the virtual machine service. Event can be associated with a virtual machine.
6.61. 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 |
|---|---|---|
|
|
6.62. 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 |
|---|---|---|
|
|
6.63. ExternalHost 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 |
|---|---|---|
|
|
6.64. 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 |
|---|---|---|
|
|
6.65. ExternalHostProvider 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 URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
6.65.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 |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.66. 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. |
6.66.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.
6.67. ExternalStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
6.68. ExternalSystemType enum Copy linkLink copied to clipboard!
Represents the type of the external system that is associated with the step.
| Name | Summary |
|---|---|
|
|
Represents |
|
|
Represents |
6.69. ExternalVmImport struct Copy linkLink copied to clipboard!
Describes parameters of virtual machine import operation from external system.
| Name | Type | Summary |
|---|---|---|
|
| Name of the virtual machine to be imported as is defined within the external system. | |
|
| Password to authenticate against external hypervisor system. | |
|
| Type of external virtual machine provider. | |
|
|
Specifies the disk allocation policy of resulting virtual machine: | |
|
|
URL to be passed to the | |
|
| Username to authenticate against external hypervisor system. |
6.69.1. url Copy linkLink copied to clipboard!
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 of the resulting virtual machine. | |
|
| Optionally specifies the cpu profile of the resulting virtual machine. | |
|
| Optional name of ISO carrying drivers that can be used during the virt-v2v conversion process. | |
|
| Optional specification of host (using host’s ID) to be used for the conversion process. | |
|
| Optionally specifies the quota that will be applied to the resulting virtual machine. | |
|
| Specifies the target storage domain for converted disks. | |
|
| Virtual machine entity used to specify the name of the newly created virtual machine. |
6.69.2. host Copy linkLink copied to clipboard!
Optional specification of host (using host’s ID) to be used for the conversion process. If not specified, one is selected automatically.
6.69.3. vm Copy linkLink copied to clipboard!
Virtual machine entity used to specify the name of the newly created virtual machine.
If name is not specified, the source virtual machine name will be used.
6.70. ExternalVmProviderType enum Copy linkLink copied to clipboard!
Describes type of external hypervisor system.
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.71. Fault struct Copy linkLink copied to clipboard!
6.72. 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. |
6.73. 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. | |
|
| If enabled, we will skip fencing in case the host maintains its lease in the storage. |
6.73.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.
6.73.2. 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.
6.74. 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 |
|---|---|---|
|
|
6.75. 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 |
|---|---|---|
|
|
6.76. Floppy 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.76.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.
6.77. FopStatistic struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
6.78. 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.78.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.
6.79. 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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.79.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.
6.80. GlusterBrickMemoryInfo struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.81. 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 |
6.82. GlusterClient struct Copy linkLink copied to clipboard!
6.83. 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 |
|---|---|---|
|
| ||
|
|
6.84. 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. |
6.85. 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. | |
|
| ||
|
| ||
|
|
6.86. 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 |
|---|---|---|
|
|
6.87. GlusterState enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.88. 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 |
|---|---|---|
|
| ||
|
| ||
|
|
6.89. 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. | |
|
|
6.90. 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. |
6.91. 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. |
6.91.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.
6.91.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.
6.91.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.
6.91.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.
6.91.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.
6.91.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.
6.91.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.
6.91.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.
6.91.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.
6.92. GracePeriod struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.93. 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 |
|---|---|---|
|
| ||
|
| ||
|
|
6.94. GraphicsType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.95. 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. | |
|
| A link to the tags sub-collection for tags attached to this group. |
6.95.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 are only supported via the roles sub-collection.
6.96. GuestOperatingSystem struct Copy linkLink copied to clipboard!
6.97. HardwareInformation struct Copy linkLink copied to clipboard!
6.98. HighAvailability struct Copy linkLink copied to clipboard!
6.99. Hook 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 |
|---|---|---|
|
|
6.100. 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. |
6.101. HookStage enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.102. 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. |
6.103. 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 hosted engine status on 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 non uniform memory access (NUMA) is supported on this host. | |
|
| The operating system on this host. | |
|
| Specifies whether we should override firewall definitions. | |
|
| The host port. | |
|
| The host power management definitions. | |
|
| The protocol that the engine uses to communicate with the host. | |
|
| 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. |
6.103.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.
6.103.2. 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.
6.103.3. 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>
6.103.4. libvirt_version Copy linkLink copied to clipboard!
The host libvirt version. For more information on libvirt please go to libvirt.
6.103.5. 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.
6.103.6. 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.
6.103.7. 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.
6.103.8. status_detail Copy linkLink copied to clipboard!
The host status details. Relevant for Gluster hosts.
6.103.9. 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>
6.103.10. 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 |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| Lists all the Katello errata assigned to the host. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Each host resource exposes a statistics sub-collection for host-specific statistics. | |
|
| ||
|
| ||
|
| ||
|
|
6.103.11. 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:
6.103.12. 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. |
6.104. HostDevice 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 |
|---|---|---|
|
| ||
|
| ||
|
|
6.105. HostDevicePassthrough struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.106. 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. | |
|
| The labels that are applied to this NIC. | |
|
| ||
|
| ||
|
| ||
|
| A link to the statistics of the NIC. | |
|
| ||
|
| For a SR-IOV physical function NIC describes its virtual functions configuration. | |
|
|
6.106.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 - WikipediaPresentation. This is only valid for bonds in mode 4, or NICs (NIC - network interface card) which are part of a bond. It is not present for bonds in other modes, or NICs which are not part in 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 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 /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.
6.106.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.
6.106.3. 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.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.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| A reference to the network which the interface should be connected. | |
|
| For a SR-IOV virtual function NIC references to its physical function NIC. | |
|
| A link to the quality-of-service configuration of the interface. |
6.106.4. network Copy linkLink copied to clipboard!
A reference to the network which the interface should be connected. A blank network id is allowed.
6.107. HostNicVirtualFunctionsConfiguration struct Copy linkLink copied to clipboard!
Describes virtual functions configuration for 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. | |
|
| Maximum number of virtual functions the NIC supports. | |
|
| Number of currently defined virtual functions. |
6.107.1. max_number_of_virtual_functions Copy linkLink copied to clipboard!
Maximum number of virtual functions the NIC supports. Read-only property.
6.107.2. number_of_virtual_functions Copy linkLink copied to clipboard!
Number of currently defined virtual functions. User-defined value between 0 and maxNumberOfVirtualFunctions.
6.108. HostProtocol enum Copy linkLink copied to clipboard!
The protocol used by the engine to communicate with a host.
| Name | Summary |
|---|---|
|
| JSON-RPC protocol on top of STOMP. |
|
| XML-RPC protocol. |
6.109. 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. |
6.109.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.
6.109.2. initializing Copy linkLink copied to clipboard!
The host is initializing. This is an intermediate step before moving the host to 'up' status.
6.109.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.
6.109.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).
6.109.5. maintenance Copy linkLink copied to clipboard!
The host is in maintenance status. When a host is in maintenance it cannot run virtual machines.
6.109.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.
6.109.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.
6.109.8. pending_approval Copy linkLink copied to clipboard!
The host is pending administrator approval. This is relevant only for vintage ovirt-node / RHV-H.
6.109.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.
6.110. HostStorage 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 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. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.110.1. 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.
6.110.2. 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 |
|---|---|---|
|
|
6.111. HostType enum Copy linkLink copied to clipboard!
This enumerated type is used to what type of operating system is used by the host.
| Name | Summary |
|---|---|
|
| The host is NGN (Next Generation Node) - a new implementation of RHEV_H which is like RHEL, CentOS or Fedora installation. |
|
| The host contains a full RHEL, CentOS or Fedora installation. |
|
| The host contains a small scaled version of RHEL, CentOS or Fedora, used solely to host virtual machines. |
6.111.1. ovirt_node Copy linkLink copied to clipboard!
The host is NGN (Next Generation Node) - a new implementation of RHEV_H which is like RHEL, CentOS or Fedora installation. The main difference between NGN and legacy RHEV-H is that NGN has a writeable file system and will handle its installation instead of pushing RPMs to it by the engine in legacy RHEV-H.
6.112. HostedEngine struct Copy linkLink copied to clipboard!
6.113. 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. |
6.113.1. media_type Copy linkLink copied to clipboard!
Format of icon file.
One of:
-
image/jpeg -
image/png -
image/gif
6.114. Identified struct Copy linkLink copied to clipboard!
This interface is the base model for all types that represent objects with an identifier.
6.115. Image 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 |
|---|---|---|
|
|
6.116. ImageTransfer struct Copy linkLink copied to clipboard!
This type contains information regarding an image transfer being performed.
| 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 current phase of the image transfer in progress. | |
|
| The URL of the proxy server that the user inputs or outputs to. | |
|
|
The signed ticket that should be attached as an |
6.116.1. 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.
6.116.2. 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 entity is in the transferring phase. See phase for details.
6.117. 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 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. |
|
| 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-daemon 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. |
6.117.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.
6.117.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.
6.117.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.
6.117.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.
6.117.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
6.117.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-daemon is not running in the selected host. To resume the session, the client should call resume. After resuming, the phase will change to resuming.
6.117.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.
6.117.8. unknown Copy linkLink copied to clipboard!
An unknown phase. This will only be set in cases of unpredictable errors.
6.118. 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. |
6.119. Initialization struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.120. 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 |
|---|---|---|
|
| 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. | |
|
| ||
|
| 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 virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
| A human-readable name in plain text. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| 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. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
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 a base version or a sub version of another template. | |
|
| Reference to VirtIO SCSI configuration. | |
|
| The virtual machine configuration associated with this template. |
6.120.1. 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:
6.120.2. 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.
6.120.3. 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.
6.120.4. 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.
6.120.5. 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 in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
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 running.
6.120.6. 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]
6.120.7. 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
6.120.8. 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.
6.120.9. 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.
| Name | Type | Summary |
|---|---|---|
|
| References 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. | |
|
| References to the disks attached to the template. | |
|
| References to the graphic consoles attached to the template. | |
|
| References to the network interfaces attached to the template. | |
|
| References 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. | |
|
| References to the tags attached to the template. | |
|
| References to the watchdog devices attached to the template. |
6.121. Io struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.122. 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. |
6.122.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>
6.122.2. 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.
6.123. IpAddressAssignment struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
6.124. IpVersion enum Copy linkLink copied to clipboard!
Defines the values for the IP protocol version.
| Name | Summary |
|---|---|
|
| IPv4. |
|
| IPv6. |
6.125. 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 |
|---|---|---|
|
| ||
|
| ||
|
|
6.126. IscsiDetails struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.127. 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. |
6.127.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.
6.128. 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. |
6.128.1. aborted Copy linkLink copied to clipboard!
The aborted job status. This status is applicable for an external job that was forcibly aborted.
6.128.2. finished Copy linkLink copied to clipboard!
The finished job status. This status describes a completed job execution.
6.128.3. started Copy linkLink copied to clipboard!
The started job status. This status represents a job which is currently being executed.
6.128.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.
6.129. 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. |
6.129.1. severity Copy linkLink copied to clipboard!
The severity of the Katello erratum.
The supported severities are moderate, important or critical.
6.129.2. type Copy linkLink copied to clipboard!
The type of the Katello erratum.
The supported types are bugfix, enhancement or security.
6.130. KdumpStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.131. Kernel struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.132. Ksm struct Copy linkLink copied to clipboard!
6.133. LogSeverity enum Copy linkLink copied to clipboard!
Enum representing a severity of an event.
| Name | Summary |
|---|---|
|
| Alert severity. |
|
| Error severity. |
|
| Normal severity. |
|
| Warning severity. |
6.133.1. alert Copy linkLink copied to clipboard!
Alert severity. Used to specify a condition that requires an immediate attention.
6.133.2. error Copy linkLink copied to clipboard!
Error severity. Used to specify that there is an error that needs to be examined.
6.133.3. normal Copy linkLink copied to clipboard!
Normal severity. Used for information events.
6.133.4. warning Copy linkLink copied to clipboard!
Warning severity. Used to warn something might be wrong.
6.134. LogicalUnit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.135. LunStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.136. Mac struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.137. 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. |
6.137.1. allow_duplicates Copy linkLink copied to clipboard!
Defines whether duplicate MAC addresses are permitted in the pool. If not specified, defaults to false.
6.137.2. default_pool Copy linkLink copied to clipboard!
Defines whether this is the default pool. If not specified, defaults to false.
6.137.3. ranges Copy linkLink copied to clipboard!
Defines the range of MAC addresses for the pool. Multiple ranges can be defined.
6.138. MemoryOverCommit struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.139. MemoryPolicy struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
|
6.140. MessageBrokerType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.141. Method struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.142. MigrateOnError enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.143. 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. |
6.143.1. custom_value Copy linkLink copied to clipboard!
Custom bandwidth in Mbps. Will be applied only if the assignmentMethod attribute is custom.
6.144. MigrationBandwidthAssignmentMethod enum Copy linkLink copied to clipboard!
Defines the method how the migration bandwidth is assigned.
| Name | Summary |
|---|---|
|
| Takes the bandwidth from QoS if QoS defined. |
|
| Custom defined bandwidth in Mbit/s. |
|
| Takes the value as configured on the hypervisor. |
6.144.1. auto Copy linkLink copied to clipboard!
Takes the bandwidth from QoS if QoS defined. If not, taken from detected link speed being used. If nothing detected, falls back to hypervisor_default value.
6.145. MigrationOptions struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| The bandwidth which is allowed to be used by the migrations. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
Reference to the migration policy as defined using |
6.146. MigrationPolicy struct Copy linkLink copied to clipboard!
A policy describing how the migration is going to be treated (convergence, how many parallel migrations allowed).
6.147. Network struct Copy linkLink copied to clipboard!
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. | |
|
| ||
|
| A unique identifier. | |
|
| ||
|
| Specifies the maximum transmission unit for the network. | |
|
| A human-readable name in plain text. | |
|
| ||
|
| ||
|
| ||
|
| Specifies whether spanning tree protocol is enabled for the network. | |
|
| Defines a set of usage elements for the network. | |
|
|
6.147.1. usages Copy linkLink copied to clipboard!
Defines a set of usage elements for the network.
Users can, for example, specify that the network is to be used for virtual machine traffic and also for display traffic with the vm and display values.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| A reference to the data center of which the network is a member. | |
|
| A reference to the labels assigned to the network. | |
|
| A reference to the permissions of the network. | |
|
| ||
|
| A reference to the profiles of the network. |
6.148. 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:
When attaching a network to a network interface card, the network element is required, with either an id or a name.
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 newtwork 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 newtork 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. | |
|
| 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. |
6.148.1. 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 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.149. NetworkConfiguration struct Copy linkLink copied to clipboard!
6.150. NetworkFilter struct Copy linkLink copied to clipboard!
Network filter enables to filter packets send to/from the VM’s nic according to defined rules.
There are several types of network filters supported based on libvirt. More details about the different network filters can be found here.
In addition to libvirt’s network filters, there are two additional network filters: The first called vdsm-no-mac-spoofing, composed of no-mac-spoofing and no-arp-mac-spoofing. The second called ovirt-no-filter is used when no network filter is to be defined for the VM’s nic. ovirt-no-filter network filter is only used for internal implementation, and doesn’t 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. | |
|
| Represent the minimal supported version of the specific NetworkFilter for which it was first introduced. |
6.151. NetworkLabel struct Copy linkLink copied to clipboard!
Represents a label which can be added to a host network interface.
| 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. |
6.152. NetworkPluginType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.153. NetworkStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.154. NetworkUsage enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| The network will be used for Gluster(bricks) data traffic. |
|
| |
|
| |
|
|
6.155. NfsProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
6.156. NfsVersion enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
6.157. Nic struct Copy linkLink copied to clipboard!
Represents a NIC of a virtual machine.
For example, the XML representation of a NIC will look like this:
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| 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 NIC is plugged in to the virtual machine. |
| Name | Type | Summary |
|---|---|---|
|
| Optionally references to an instance type the device is used by. | |
|
| A reference to the network which the interface should be connected to. | |
|
| ||
|
| ||
|
| ||
|
| A link to the statistics for the NIC. | |
|
| Optionally references to a template the device is used by. | |
|
| ||
|
| ||
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. | |
|
|
6.157.1. network Copy linkLink copied to clipboard!
A reference to the network which 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.
6.157.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.
6.158. NicConfiguration struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
|
6.159. NicInterface enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
6.160. NicStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.161. 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 |
|---|---|---|
|
| ||
|
|
6.162. NumaNodePin struct Copy linkLink copied to clipboard!
Represents pinning of a virtual NUMA node to a physical NUMA node.
6.163. NumaTuneMode enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.164. 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 |
|---|---|---|
|
|
6.165. 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 URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
6.165.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 |
|---|---|---|
|
| ||
|
|
6.166. 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 |
|---|---|---|
|
|
6.167. OpenStackNetworkProvider struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| Agent configuration settings. | |
|
| 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. | |
|
| Network plugin type. | |
|
| Array of provider name/value properties. | |
|
| Indicates whether the provider is read-only. | |
|
| Defines whether provider authentication is required or not. | |
|
| ||
|
| The type of provider. | |
|
| Defines URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
6.167.1. 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.
6.167.2. 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 |
|---|---|---|
|
| Reference to the certificates list. | |
|
| Reference to OpenStack networks list. | |
|
| Reference to OpenStack networks subnets list. |
6.168. 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 will be 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. |
6.168.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.
6.168.2. neutron Copy linkLink copied to clipboard!
Indicates that the provider is OpenStack Neutron. The standard OpenStack Neutron agent will be used as the virtual interface driver.
6.169. 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 URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
6.169.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.
6.170. 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. |
6.170.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. |
6.171. OpenStackVolumeProvider 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 URL address of the external provider. | |
|
| Defines user name to be used during authentication process. |
6.171.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 |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
|
6.172. OpenStackVolumeType 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 |
|---|---|---|
|
|
6.173. OpenstackVolumeAuthenticationKey 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 |
|---|---|---|
|
|
6.174. OpenstackVolumeAuthenticationKeyUsageType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.175. OperatingSystem struct Copy linkLink copied to clipboard!
Information describing the operating system. Used for virtual machines and hosts.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| A custom part of the host kernel command line. | |
|
| ||
|
| ||
|
| Host kernel command line as reported by a running host. | |
|
| ||
|
|
6.175.1. 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 re-install and then reboot the host to apply the changes implemented by this attribute.
Parameters merging: 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 Engine internally keeps track of the last applied kernel parameters customization.
This attribute is currently only used for hosts.
6.175.2. reported_kernel_cmdline Copy linkLink copied to clipboard!
Host kernel command line as reported by a running host.
Read-only attribute. Attempts to change this attribute are silently ignored.
This attribute is currently only used for hosts.
6.176. OperatingSystemInfo struct Copy linkLink copied to clipboard!
6.177. Option struct Copy linkLink copied to clipboard!
6.178. OsType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
6.179. 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. |
6.180. Payload struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
6.181. PayloadEncoding enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.182. Permission 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. |
6.183. 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. |
6.184. PmProxy struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.185. PmProxyType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Fence proxy is selected from the same cluster as fenced host. |
|
| Fence proxy is selected from the same data center as fenced host. |
|
| Fence proxy is selected from a different data center than fenced host. |
6.186. PolicyUnitType enum Copy linkLink copied to clipboard!
This enum holds the types of all internal policy units types
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.187. PortMirroring struct Copy linkLink copied to clipboard!
6.188. 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. |
6.188.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.
6.188.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.
6.188.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.
6.188.4. type Copy linkLink copied to clipboard!
Fencing device code.
A list of valid fencing device codes are available in the capabilities collection.
6.189. PowerManagementStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| Host is OFF. |
|
| Host is ON. |
|
| Unknown status. |
6.190. Product struct Copy linkLink copied to clipboard!
6.191. 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 name of the product, for example | |
|
| The name of the vendor, for example `ovirt. | |
|
| The version number of the product. |
6.191.1. vendor Copy linkLink copied to clipboard!
The name of the vendor, for example ovirt.org.
6.192. ProfileDetail struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.193. Property struct Copy linkLink copied to clipboard!
6.194. ProxyTicket struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.195. 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. | |
|
| The amount of data that can be delivered in a single burst in MiB. | |
|
| The maximum inbound rate in Mbps. | |
|
| 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. | |
|
| Weighted share. | |
|
| The committed rate in Mbps. | |
|
| The maximum bandwidth to be used by a network in Mbps. | |
|
| The amount of data that can be sent in a single burst in MiB. | |
|
| The maximum outbound rate in Mbps. | |
|
| The kind of resources this entry can be assigned. |
6.195.1. cpu_limit Copy linkLink copied to clipboard!
The maximum processing capability in %.
Used to configure computing resources.
6.195.2. inbound_average Copy linkLink copied to clipboard!
The desired average inbound bit rate in Mbps.
Used to configure virtual machines networks. If defined, inbound_peak and inbound_burst also has to be set.
See Libvirt-QOS for further details.
6.195.3. inbound_burst Copy linkLink copied to clipboard!
The amount of data that can be delivered in a single burst in MiB.
Used to configure virtual machines networks. If defined, inbound_average and inbound_peak also has to be set.
See Libvirt-QOS for further details.
6.195.4. inbound_peak Copy linkLink copied to clipboard!
The maximum inbound rate in Mbps.
Used to configure virtual machines networks. If defined, inbound_average and inbound_burst also has to be set.
See Libvirt-QOS for further details.
6.195.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.
6.195.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.
6.195.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.
6.195.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.
6.195.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.
6.195.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.
6.195.11. outbound_average Copy linkLink copied to clipboard!
The desired average outbound bit rate in Mbps.
Used to configure virtual machines networks. If defined, outbound_peak and outbound_burst also has to be set.
See Libvirt-QOS for further details.
6.195.13. outbound_average_realtime Copy linkLink copied to clipboard!
The committed rate in Mbps.
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.
6.195.14. outbound_average_upperlimit Copy linkLink copied to clipboard!
The maximum bandwidth to be used by a network in Mbps.
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.
6.195.15. outbound_burst Copy linkLink copied to clipboard!
The amount of data that can be sent in a single burst in MiB.
Used to configure virtual machines networks. If defined, outbound_average and outbound_peak also has to be set.
See Libvirt-QOS for further details.
6.195.16. outbound_peak Copy linkLink copied to clipboard!
The maximum outbound rate in Mbps.
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. |
6.196. 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. |
6.197. 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. | |
|
| ||
|
| ||
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
6.198. 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. | |
|
| ||
|
|
6.199. QuotaModeType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.200. 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 |
|---|---|---|
|
| ||
|
|
6.201. Range struct Copy linkLink copied to clipboard!
6.202. Rate struct Copy linkLink copied to clipboard!
Determines maximum speed of consumption of bytes from random number generator device.
6.203. ReportedConfiguration struct Copy linkLink copied to clipboard!
6.204. 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. | |
|
| ||
|
| ||
|
| A human-readable name in plain text. | |
|
|
| Name | Type | Summary |
|---|---|---|
|
|
6.205. ReportedDeviceType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.206. ResolutionType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.207. RngDevice struct Copy linkLink copied to clipboard!
Random number generator (RNG) device model.
6.208. 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 |
6.209. 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. |
6.209.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.
6.210. 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. |
6.211. 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. | |
|
|
6.212. 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. | |
|
| ||
|
|
6.213. ScsiGenericIO enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.214. SeLinux struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.215. SeLinuxMode enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.216. SerialNumber struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
|
6.217. SerialNumberPolicy enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.218. Session struct Copy linkLink copied to clipboard!
Describes 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. | |
|
| IP address user is connected from. | |
|
| A human-readable name in plain text. | |
|
| Protocol used by the session. |
6.218.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, false for others: e.g. RDP, SSH.
6.218.2. ip Copy linkLink copied to clipboard!
IP address user is connected from.
Currently only available for console users.
6.218.3. protocol Copy linkLink copied to clipboard!
Protocol used by the session.
Currently not used, intended for info about how is user connected: SPICE, VNC, SSH, RDP.
6.218.4. user Copy linkLink copied to clipboard!
User related to this session.
If user is a console user, it is a link to real oVirt user. Otherwise only username is provided.
6.219. 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. |
6.219.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.
6.219.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.
6.220. 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. |
6.220.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.
6.221. Snapshot struct Copy linkLink copied to clipboard!
Represents a snapshot object.
| Name | Type | Summary |
|---|---|---|
|
| 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. | |
|
| ||
|
| 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). | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
| 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. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
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. |
6.221.1. 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:
6.221.2. 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.
6.221.3. 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.
6.221.4. 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.
6.221.5. 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 in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
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 running.
6.221.6. 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]
6.221.7. 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.
6.221.8. 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
6.221.9. 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:
6.221.10. 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.
6.221.11. 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.
6.221.12. stop_reason Copy linkLink copied to clipboard!
The reason the virtual machine was stopped. Optionally set by user when shutting down the virtual machine.
| 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. | |
|
| ||
|
| 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. | |
|
| References the list of network interface devices on the virtual machine. | |
|
| Refers to the NUMA Nodes configuration used by this 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. | |
|
| ||
|
| 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. |
6.221.13. affinity_labels Copy linkLink copied to clipboard!
Optional. Used for labeling of sub-clusters.
6.221.14. 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:
6.222. SnapshotStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.223. SnapshotType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
6.224. SpecialObjects struct Copy linkLink copied to clipboard!
This type contains references to special objects, like the blank template and the root of the hierarchy of tags.
6.225. Spm struct Copy linkLink copied to clipboard!
6.226. SpmStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.227. Ssh 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. | |
|
| ||
|
|
6.228. SshAuthenticationMethod enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.229. SshPublicKey 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 |
|---|---|---|
|
|
6.230. Sso struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
6.231. SsoMethod enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
|
6.232. 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. | |
|
| ||
|
| ||
|
| ||
|
|
6.233. StatisticKind enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.234. StatisticUnit enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
6.235. 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 start time of the step. | |
|
| The status of the step. | |
|
| The type of the step. |
6.235.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 |
|---|---|---|
|
|
References the | |
|
| References the parent step of the current step in the hierarchy. | |
|
|
6.236. 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. |
6.236.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.
6.236.2. finalizing Copy linkLink copied to clipboard!
The finalizing step type. Describes the post-execution steps requires to complete the job.
6.236.3. rebalancing_volume Copy linkLink copied to clipboard!
The rebalancing volume step type. Describes a step type which is part of Gluster flow.
6.236.4. removing_bricks Copy linkLink copied to clipboard!
The removing bricks step type. Describes a step type which is part of Gluster flow.
6.236.5. unknown Copy linkLink copied to clipboard!
The unknown step type. Describes a step type which its origin is unknown.
6.236.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.
6.237. 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. |
6.237.1. aborted Copy linkLink copied to clipboard!
The aborted step status. This status is applicable for an external step that was forcibly aborted.
6.237.2. finished Copy linkLink copied to clipboard!
The finished step status. This status describes a completed step execution.
6.237.3. started Copy linkLink copied to clipboard!
The started step status. This status represents a step which is currently being executed.
6.237.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.
6.238. StorageConnection struct Copy linkLink copied to clipboard!
Represents a storage server connection.
Example:
<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 |
|---|---|---|
|
| ||
|
| 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 |
|---|---|---|
|
|
6.239. 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 |
|---|---|---|
|
|
6.240. StorageDomain struct Copy linkLink copied to clipboard!
Storage domain.
An XML representation of a NFS storage domain with identifier 123:
| 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. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
|
|
Serves as the default value of |
6.240.1. 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 |
|---|---|---|
|
| This is used to link to the data center that the storage domain is attached to. | |
|
| This is a set of links to the data centers that the storage domain is attached to. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Host is only relevant at creation time. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
|
6.240.2. data_center Copy linkLink copied to clipboard!
This is used to link to the data center that the storage domain is attached to. It is preserved for backwards compatibility, as the storage domain may be attached to multiple data centers (if it is an ISO domain). Use the dataCenters element instead.
6.241. StorageDomainStatus enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
6.242. StorageDomainType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
6.243. StorageFormat enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.244. 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. |
|
| NFS storage domain. |
|
| POSIX-FS storage domain. |
6.244.1. cinder Copy linkLink copied to clipboard!
Cinder storage domain. For more details on Cinder please go to Cinder.
6.244.2. glance Copy linkLink copied to clipboard!
Glance storage domain. For more details on Glance please go to Glance.
6.244.3. glusterfs Copy linkLink copied to clipboard!
Gluster-FS storage domain. For more details on Gluster please go to Gluster.
6.245. 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. |
6.246. 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. |
6.247. Template struct Copy linkLink copied to clipboard!
Type representing a virtual machine template. This allows a rapid instanstiation of virtual machines with common configuration and disk states.
| Name | Type | Summary |
|---|---|---|
|
| 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. | |
|
| ||
|
| 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 virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
| A human-readable name in plain text. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| 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. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
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 a base version or a sub version of another template. | |
|
| Reference to VirtIO SCSI configuration. | |
|
| The virtual machine configuration associated with this template. |
6.247.1. 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:
6.247.2. 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.
6.247.3. 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.
6.247.4. 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.
6.247.5. 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 in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
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 running.
6.247.6. 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]
6.247.7. 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
6.247.8. 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.
6.247.9. 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.
| Name | Type | Summary |
|---|---|---|
|
| References 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. | |
|
| References to the disks attached to the template. | |
|
| References to the graphic consoles attached to the template. | |
|
| References to the network interfaces attached to the template. | |
|
| References 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. | |
|
| References to the tags attached to the template. | |
|
| References to the watchdog devices attached to the template. |
6.248. 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. |
6.249. 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. |
6.249.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. |
6.250. Ticket struct Copy linkLink copied to clipboard!
Type representing a ticket that allows virtual machine access.
6.251. TimeZone struct Copy linkLink copied to clipboard!
Time zone representation.
| Name | Type | Summary |
|---|---|---|
|
| Name of the time zone. | |
|
| Offset from https://en. |
6.251.1. utc_offset Copy linkLink copied to clipboard!
Offset from UTC.
6.252. TransparentHugePages struct Copy linkLink copied to clipboard!
Type representing a transparent huge pages (THP) support.
| Name | Type | Summary |
|---|---|---|
|
| Enable THP support. |
6.253. TransportType enum Copy linkLink copied to clipboard!
Protocol used to access a Gluster volume.
| Name | Summary |
|---|---|
|
| Remote direct memory access. |
|
| TCP. |
6.254. 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. |
6.255. Usb struct Copy linkLink copied to clipboard!
6.256. UsbType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.257. 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 user resides. | |
|
| ||
|
|
Same as | |
|
| Username of the user. |
6.257.1. namespace Copy linkLink copied to clipboard!
Namespace where user resides. When using the authorization provider that stores users in the LDAP (see here for details) this attribute equals to naming context of the LDAP. When using the built-in authorization provider that stores users in the database (see here for details) this attribute is ignored.
6.257.2. principal Copy linkLink copied to clipboard!
Same as user_name principal has different formats based on LDAP provider. In case of most LDAP providers it is value of the uid LDAP attribute. In case of Active Directory it is the user principal name (UPN).
6.257.3. user_name Copy linkLink copied to clipboard!
Username of the user. The format depends on authorization provider type. In case of most LDAP providers it is value of the uid LDAP attribute. In case of Active Directory it is the user principal name (UPN). UPN or uid must be followed by authorization provider name. For example in case of LDAP using uid attribute it is: myuser@myextension-authz. In case of Active Directory using UPN it is: myuser@mysubdomain.mydomain.com@myextension-authz. This attribute is required parameter when adding new user.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
| ||
|
| A link to the roles sub-collection for user resources. | |
|
| ||
|
| A link to the tags sub-collection for user resources. |
6.258. Value struct Copy linkLink copied to clipboard!
6.259. ValueType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.260. VcpuPin struct Copy linkLink copied to clipboard!
6.261. Vendor struct Copy linkLink copied to clipboard!
6.262. 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. | |
|
|
6.263. 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. |
6.264. 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. | |
|
| ||
|
|
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
6.265. Vlan struct Copy linkLink copied to clipboard!
Type representing a Virtual LAN (VLAN) type.
| Name | Type | Summary |
|---|---|---|
|
| Virtual LAN ID. |
6.266. Vm struct Copy linkLink copied to clipboard!
Represents a virtual machine.
| Name | Type | Summary |
|---|---|---|
|
| 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. | |
|
| ||
|
| 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). | |
|
| The virtual machine high availability configuration. | |
|
| A unique identifier. | |
|
| Reference to virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
| 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. | |
|
| The virtual machine’s time zone set by oVirt. | |
|
|
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. |
6.266.1. 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:
6.266.2. 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.
6.266.3. 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.
6.266.4. 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.
6.266.5. 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 in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
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 running.
6.266.6. 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]
6.266.7. 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.
6.266.8. 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
6.266.9. 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:
6.266.10. 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.
6.266.11. 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.
6.266.12. stop_reason Copy linkLink copied to clipboard!
The reason the virtual machine was stopped. Optionally set by user when shutting down the virtual machine.
| 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. | |
|
| ||
|
| 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. | |
|
| References the list of network interface devices on the virtual machine. | |
|
| Refers to the NUMA Nodes configuration used by this 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. | |
|
| ||
|
| 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. |
6.266.13. affinity_labels Copy linkLink copied to clipboard!
Optional. Used for labeling of sub-clusters.
6.266.14. 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:
6.267. VmAffinity enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.268. 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 |
|---|---|---|
|
| 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. | |
|
| ||
|
| 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 virtual machine’s initialization configuration. | |
|
| For performance tuning of IO threading. | |
|
| Virtual machine’s large icon. | |
|
| The virtual machine’s memory, in bytes. | |
|
| Reference to virtual machine’s memory management configuration. | |
|
| Reference to configuration of migration of running virtual machine to another host. | |
|
| Maximum time the virtual machine can be non responsive during its live migration to another host in ms. | |
|
| A human-readable name in plain text. | |
|
| The origin of this virtual machine. | |
|
| Operating system type installed on the virtual machine. | |
|
| 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 virtual machine’s time zone set by oVirt. | |
|
|
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. |
6.268.1. 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:
6.268.2. 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.
6.268.3. 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.
6.268.4. 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.
6.268.5. 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 in the example is converted to bytes using the following formula:
1 GiB = 230 bytes = 1073741824 bytes.
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 running.
6.268.6. 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]
6.268.7. 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
6.268.8. 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.
6.268.9. 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.
| 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. |
6.269. VmDeviceType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.270. VmPlacementPolicy struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
|
| Name | Type | Summary |
|---|---|---|
|
|
6.271. VmPool 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. | |
|
| ||
|
| ||
|
| ||
|
| ||
|
| Virtual machine pool’s stateful flag. | |
|
| ||
|
|
6.271.1. 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.
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| Reference to the instance type on which this pool is based. | |
|
| ||
|
| ||
|
|
6.271.2. 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.
6.272. VmPoolType enum Copy linkLink copied to clipboard!
| Name | Summary |
|---|---|
|
| |
|
|
6.273. VmStatus enum Copy linkLink copied to clipboard!
Type represeting 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. |
6.273.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.
6.273.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.
6.273.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.
6.273.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.
6.273.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.
6.273.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.
6.273.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.
6.273.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.
6.274. VmSummary struct Copy linkLink copied to clipboard!
6.275. 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 server. |
6.275.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 be automatically added to the virtual machine.
6.275.2. 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 be automatically added to the virtual machine.
6.276. 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. |
6.277. VnicPassThroughMode enum Copy linkLink copied to clipboard!
The enum describes whether vNIC to be implemented as a pass-through device or a virtual one. Currently it supports only 2 option, but there is a plan to add more in the future.
| Name | Summary |
|---|---|
|
| To be implemented as a virtual device |
|
| To be implemented as a pass-through device |
6.278. VnicProfile 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 |
|---|---|---|
|
| ||
|
| Network filter will enhance the admin ability to manage the network packets traffic from/to the participated VMs. | |
|
| ||
|
|
6.279. VolumeGroup struct Copy linkLink copied to clipboard!
| Name | Type | Summary |
|---|---|---|
|
| ||
|
| ||
|
|
6.280. 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. |
6.280.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. | |
|
|
Don’t use this element, use | |
|
| References to the virtual machines that are using this device. |
6.280.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.
6.281. 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. |
6.281.1. none Copy linkLink copied to clipboard!
No action will be performed when watchdog action is triggered. However log message will still be generated.
6.282. WatchdogModel enum Copy linkLink copied to clipboard!
This type represents the watchdog model.
| Name | Summary |
|---|---|
|
| Currently only model supported is model I6300ESB. |
6.283. 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 seconds since Jan 1st 1970, also know 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 the above examples it is UTC+2.