Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 6. Services
This section enumerates all the services that are available in the API.
6.1. AffinityGroup
This service manages a single affinity group.
| Name | Summary |
|---|---|
|
| Retrieve the affinity group details. |
|
| Remove the affinity group. |
|
| Update the affinity group. |
6.1.1. get GET
Retrieve the affinity group details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The affinity group. |
6.1.2. remove DELETE
Remove the affinity group.
DELETE /ovirt-engine/api/clusters/000-000/affinitygroups/123-456
DELETE /ovirt-engine/api/clusters/000-000/affinitygroups/123-456| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.1.3. update PUT
Update the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The affinity group. |
6.2. AffinityGroupVm
This service manages a single virtual machine to affinity group assignment.
| Name | Summary |
|---|---|
|
| Remove this virtual machine from the affinity group. |
6.2.1. remove DELETE
Remove this virtual machine from the affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the removal should be performed asynchronously. |
6.3. AffinityGroupVms
This service manages a collection of all the 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. |
6.3.1. add POST
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/vmsWith the following body:
<vm id="000-000"/>
<vm id="000-000"/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.3.2. list GET
List all virtual machines assigned to this affinity group.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of virtual machines to return. | |
|
| Out |
6.3.2.1. max
Sets the maximum number of virtual machines to return. If not specified, all the virtual machines are returned.
6.4. AffinityGroups
The affinity groups service manages virtual machine relationships and dependencies.
| Name | Summary |
|---|---|
|
| Create a new affinity group. |
|
| List existing affinity groups. |
6.4.1. add POST
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/affinitygroupsAnd 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. |
6.4.2. list GET
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. |
6.4.2.1. max
Sets the maximum number of affinity groups to return. If not specified all the affinity groups are returned.
6.5. AffinityLabel
The details of a single affinity label.
| Name | Summary |
|---|---|
|
| Retrieves the details of a label. |
|
| Removes a label from the system and clears all assignments of the removed label. |
|
| Updates a label. |
6.5.1. get GET
Retrieves the details of a label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.5.2. remove DELETE
Removes a label from the system and clears all assignments of the removed label.
6.5.3. update PUT
Updates a label. This call will update all metadata, such as the name or description.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.6. AffinityLabelHost
This service represents a host that has a specific label when accessed through the affinitylabels/hosts subcollection.
| Name | Summary |
|---|---|
|
| Retrieves details about a host that has this label assigned. |
|
| Remove a label from a host. |
6.6.1. get GET
Retrieves details about a host that has this label assigned.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.6.2. remove DELETE
Remove a label from a host.
6.7. AffinityLabelHosts
This service represents list of hosts that have a specific label when accessed through the affinitylabels/hosts subcollection.
| Name | Summary |
|---|---|
|
| Add a label to a host. |
|
| List all hosts with the label. |
6.7.1. add POST
Add a label to a host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.7.2. list GET
List all hosts with the label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.8. AffinityLabelVm
This service represents a vm that has a specific label when accessed through the affinitylabels/vms subcollection.
| Name | Summary |
|---|---|
|
| Retrieves details about a vm that has this label assigned. |
|
| Remove a label from a vm. |
6.8.1. get GET
Retrieves details about a vm that has this label assigned.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.8.2. remove DELETE
Remove a label from a vm.
6.9. AffinityLabelVms
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. |
6.9.1. add POST
Add a label to a vm.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.9.2. list GET
List all vms with the label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.10. AffinityLabels
Manages the affinity labels available in the system.
| Name | Summary |
|---|---|
|
| Creates a new label. |
|
| Lists all labels present in the system. |
6.10.1. add POST
Creates a new label. The label is automatically attached to all entities mentioned in the vms or hosts lists.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.10.2. list GET
Lists all labels present in the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of labels to return. |
6.10.2.1. max
Sets the maximum number of labels to return. If not specified all the labels are returned.
6.11. AssignedAffinityLabel
This service represents one label to entity assignment when accessed using the entities/affinitylabels subcollection.
| Name | Summary |
|---|---|
|
| Retrieves details about the attached label. |
|
| Removes the label from an entity. |
6.11.1. get GET
Retrieves details about the attached label.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.11.2. remove DELETE
Removes the label from an entity. Does not touch the label itself.
6.12. AssignedAffinityLabels
This service is used to list and manipulate affinity labels that are assigned to supported entities when accessed using entities/affinitylabels.
| Name | Summary |
|---|---|
|
| Attaches a label to an entity. |
|
| Lists all labels that are attached to an entity. |
6.12.1. add POST
Attaches a label to an entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.12.2. list GET
Lists all labels that are attached to an entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.13. AssignedCpuProfile
| Name | Summary |
|---|---|
|
| |
|
|
6.13.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.13.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.14. AssignedCpuProfiles
| Name | Summary |
|---|---|
|
| |
|
|
6.14.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.14.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.14.2.1. max
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.15. AssignedDiskProfile
| Name | Summary |
|---|---|
|
| |
|
|
6.15.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.15.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.16. AssignedDiskProfiles
| Name | Summary |
|---|---|
|
| |
|
|
6.16.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.16.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.16.2.1. max
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.17. AssignedPermissions
Represents a permission sub-collection, scoped by user, group or some entity type.
| Name | Summary |
|---|---|
|
| Assign a new permission to a user or group for specific entity. |
|
| List all the permissions of the specific entity. |
6.17.1. add POST
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/permissionsWith 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/permissionsWith 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/permissionsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The permission. |
6.17.2. list GET
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. |
6.18. AssignedRoles
Represents a roles sub-collection, for example scoped by user.
| Name | Summary |
|---|---|
|
|
6.18.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of roles to return. | |
|
| Out |
6.18.1.1. max
Sets the maximum number of roles to return. If not specified all the roles are returned.
6.19. AssignedTag
A service to manage assignment of specific tag to specific entities in system.
| Name | Summary |
|---|---|
|
| Gets the information about the assigned tag. |
|
| Unassign tag from specific entity in the system. |
6.19.1. get GET
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. |
6.19.2. remove DELETE
Unassign tag from specific entity in the system.
For example to unassign the tag with id 456 from virtual machine with id 123 send a request like this:
DELETE /ovirt-engine/api/vms/123/tags/456
DELETE /ovirt-engine/api/vms/123/tags/456| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.20. AssignedTags
A service to manage collection of assignment of tags to specific entities in system.
| Name | Summary |
|---|---|
|
| Assign tag to specific entity in the system. |
|
| List all tags assigned to the specific entity. |
6.20.1. add POST
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/tagsWith a request body like this:
<tag> <name>mytag</name> </tag>
<tag>
<name>mytag</name>
</tag>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The assigned tag. |
6.20.2. list GET
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. |
6.20.2.1. max
Sets the maximum number of tags to return. If not specified all the tags are returned.
6.21. AssignedVnicProfile
| Name | Summary |
|---|---|
|
| |
|
|
6.21.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.21.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.22. AssignedVnicProfiles
| Name | Summary |
|---|---|
|
| |
|
|
6.22.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.22.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.22.2.1. max
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.23. AttachedStorageDomain
| Name | Summary |
|---|---|
|
| This operation activates an attached storage domain. |
|
| This operation deactivates an attached storage domain. |
|
| |
|
|
6.23.1. activate POST
This operation activates an attached storage domain. Once the storage domain is activated it is ready for use with the data center.
POST /ovirt-engine/api/datacenters/123/storagedomains/456/activate
POST /ovirt-engine/api/datacenters/123/storagedomains/456/activate
The activate action does not take any action specific parameters, so the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.23.2. deactivate POST
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. |
6.23.3. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.23.4. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.24. AttachedStorageDomains
| Name | Summary |
|---|---|
|
| |
|
|
6.24.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.24.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of storage domains to return. | |
|
| Out |
6.24.2.1. max
Sets the maximum number of storage domains to return. If not specified all the storage domains are returned.
6.25. Balance
| Name | Summary |
|---|---|
|
| |
|
|
6.25.1. get GET
6.25.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.26. Balances
| Name | Summary |
|---|---|
|
| |
|
|
6.26.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.26.2. list GET
| 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. |
6.26.2.1. max
Sets the maximum number of balances to return. If not specified all the balances are returned.
6.27. Bookmark
A service to manage a bookmark.
| Name | Summary |
|---|---|
|
| Get a bookmark. |
|
| Remove a bookmark. |
|
| Update a bookmark. |
6.27.1. get GET
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. |
6.27.2. remove DELETE
Remove a bookmark.
An example for removing a bookmark:
DELETE /ovirt-engine/api/bookmarks/123
DELETE /ovirt-engine/api/bookmarks/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.27.3. update PUT
Update a bookmark.
An example for updating a bookmark:
PUT /ovirt-engine/api/bookmarks/123
PUT /ovirt-engine/api/bookmarks/123With the request body:
<bookmark> <name>new_example_vm</name> <value>vm: name=new_example*</value> </bookmark>
<bookmark>
<name>new_example_vm</name>
<value>vm: name=new_example*</value>
</bookmark>6.28. Bookmarks
A service to manage bookmarks.
| Name | Summary |
|---|---|
|
| Adding a new bookmark. |
|
| Listing all the available bookmarks. |
6.28.1. add POST
Adding a new bookmark.
Example of adding a bookmark:
POST /ovirt-engine/api/bookmarks
POST /ovirt-engine/api/bookmarks<bookmark> <name>new_example_vm</name> <value>vm: name=new_example*</value> </bookmark>
<bookmark>
<name>new_example_vm</name>
<value>vm: name=new_example*</value>
</bookmark>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The added bookmark. |
6.28.2. list GET
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. |
6.28.2.1. max
Sets the maximum number of bookmarks to return. If not specified all the bookmarks are returned.
6.29. Cluster
A service to manage specific cluster.
| Name | Summary |
|---|---|
|
| Get information about the cluster. |
|
| Removes cluster from the system. |
|
| |
|
| Updates information about the cluster. |
6.29.1. get GET
Get information about the cluster.
An example of getting a cluster:
GET /ovirt-engine/api/clusters/123
GET /ovirt-engine/api/clusters/1236.29.2. remove DELETE
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. |
6.29.3. resetemulatedmachine POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reset should be performed asynchronously. |
6.29.4. update PUT
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/123With request body like:
<cluster>
<cpu>
<type>Intel Haswell-noTSX Family</type>
</cpu>
</cluster>
<cluster>
<cpu>
<type>Intel Haswell-noTSX Family</type>
</cpu>
</cluster>6.30. ClusterLevel
Provides information about a specific cluster level. See the ClusterLevels service for more information.
| Name | Summary |
|---|---|
|
| Provides the information about the capabilities of the specific cluster level managed by this service. |
6.30.1. get GET
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.6That 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. |
6.31. ClusterLevels
Provides information about the capabilities of different cluster levels supported by the engine. Version 4.0 of the engine supports levels 4.0 and 3.6. Each of these levels support different sets of CPU types, for example. This service provides that information.
| Name | Summary |
|---|---|
|
| Lists the cluster levels supported by the system. |
6.31.1. list GET
Lists the cluster levels supported by the system.
GET /ovirt-engine/api/clusterlevels
GET /ovirt-engine/api/clusterlevelsThis will return a list of available cluster levels.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved cluster levels. |
6.32. ClusterNetwork
A service to manage a specific cluster network.
| Name | Summary |
|---|---|
|
| Retrieves the cluster network details. |
|
| Unassigns the network from a cluster. |
|
| Updates the network in the cluster. |
6.32.1. get GET
Retrieves the cluster network details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The cluster network. |
6.32.2. remove DELETE
Unassigns the network from a cluster.
6.32.3. update PUT
Updates the network in the cluster.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The cluster network. |
6.33. ClusterNetworks
A service to manage cluster networks.
| Name | Summary |
|---|---|
|
| Assigns the network to a cluster. |
|
| Lists the networks that are assigned to the cluster. |
6.33.1. add POST
Assigns the network to a cluster.
Post a request like in the example below to assign the network to a cluster:
POST /ovirt-engine/api/clusters/123/networks
POST /ovirt-engine/api/clusters/123/networksUse the following example in its body:
<network id="123" />
<network id="123" />| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The network object to be assigned to the cluster. |
6.33.2. list GET
Lists the networks that are assigned to the cluster.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out | The list of networks that are assigned to the cluster. |
6.33.2.1. max
Sets the maximum number of networks to return. If not specified, all the networks are returned.
6.34. Clusters
A service to manage clusters.
| Name | Summary |
|---|---|
|
| Creates a new cluster. |
|
|
6.34.1. add POST
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/clustersWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.34.2. list GET
| 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. |
6.34.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.34.2.2. max
Sets the maximum number of clusters to return. If not specified all the clusters are returned.
6.35. Copyable
| Name | Summary |
|---|---|
|
|
6.35.1. copy POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the copy should be performed asynchronously. |
6.36. CpuProfile
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.36.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.36.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.36.3. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.37. CpuProfiles
| Name | Summary |
|---|---|
|
| |
|
|
6.37.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.37.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.37.2.1. max
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.38. DataCenter
A service to manage a data center.
| Name | Summary |
|---|---|
|
| Get a data center. |
|
| Removes the data center. |
|
| Updates the data center. |
6.38.1. get GET
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. |
6.38.2. remove DELETE
Removes the data center.
DELETE /ovirt-engine/api/datacenters/123
DELETE /ovirt-engine/api/datacenters/123Without any special parameters, the storage domains attached to the data center are detached and then removed from the storage. If something fails when performing this operation, for example if there is no host available to remove the storage domains from the storage, the complete operation will fail.
If the force parameter is true then the operation will always succeed, even if something fails while removing one storage domain, for example. The failure is just ignored and the data center is removed from the database anyway.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates if the operation should succeed, and the storage domain removed from the database, even if something fails during the operation. |
6.38.2.1. force
Indicates if the operation should succeed, and the storage domain removed from the database, even if something fails during the operation.
This parameter is optional, and the default value is false.
6.38.3. update PUT
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/123With a request body like this:
<data_center> <name>myupdatedname</name> <description>An updated description for the data center</description> </data_center>
<data_center>
<name>myupdatedname</name>
<description>An updated description for the data center</description>
</data_center>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The data center that is being updated. |
6.39. DataCenterNetwork
A service to manage a specific data center network.
| Name | Summary |
|---|---|
|
| Retrieves the data center network details. |
|
| Removes the network. |
|
| Updates the network in the data center. |
6.39.1. get GET
Retrieves the data center network details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The data center network. |
6.39.2. remove DELETE
Removes the network.
6.39.3. update PUT
Updates the network in the data center.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The data center network. |
6.40. DataCenterNetworks
A service to manage data center networks.
| Name | Summary |
|---|---|
|
| Create a new network in a data center. |
|
| Lists networks in the data center. |
6.40.1. add POST
Create a new network in a data center.
Post a request like in the example below to create a new network in a data center with an ID of 123.
POST /ovirt-engine/api/datacenters/123/networks
POST /ovirt-engine/api/datacenters/123/networksUse the following example in its body:
<network> <name>mynetwork</name> </network>
<network>
<name>mynetwork</name>
</network>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The network object to be created in the data center. |
6.40.2. list GET
Lists networks in the data center.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out | The list of networks which are in the data center. |
6.40.2.1. max
Sets the maximum number of networks to return. If not specified, all the networks are returned.
6.41. DataCenters
A service to manage data centers.
| Name | Summary |
|---|---|
|
| Creates a new data center. |
|
| Lists the data centers. |
6.41.1. add POST
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/datacentersWith a request body like this:
<data_center> <name>mydc</name> <local>false</local> </data_center>
<data_center>
<name>mydc</name>
<local>false</local>
</data_center>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The data center that is being added. |
6.41.2. list GET
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. |
6.41.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.41.2.2. max
Sets the maximum number of data centers to return. If not specified all the data centers are returned.
6.42. Disk
Manages a single disk.
| Name | Summary |
|---|---|
|
| This operation copies a disk to the specified storage domain. |
|
| |
|
| |
|
| Moves a disk to another storage domain. |
|
| |
|
| Sparsify the disk. |
6.42.1. copy POST
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/copyWith 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 |
6.42.2. export POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the export should be performed asynchronously. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In |
6.42.3. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.42.4. move POST
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/moveWith 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 |
6.42.5. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.42.6. sparsify POST
Sparsify the disk.
Sparsification frees space in the disk image that is not used by its filesystem. As a result, the image will occupy less space on the storage.
Currently sparsification works only on disks without snapshots. Disks having derived disks are also not allowed.
6.43. DiskAttachment
This service manages the attachment of a disk to a virtual machine.
| Name | Summary |
|---|---|
|
| Returns the details of the attachment, including the bootable flag and link to the disk. |
|
| Removes the disk attachment. |
|
| Update the disk attachment and the disk properties within it. |
6.43.1. get GET
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 |
6.43.2. remove DELETE
Removes the disk attachment.
This will only detach the disk from the virtual machine, but won’t remove it from the system, unless the detach_only parameter is false.
An example of removing a disk attachment:
DELETE /ovirt-engine/api/vms/123/diskattachments/456?detach_only=true
DELETE /ovirt-engine/api/vms/123/diskattachments/456?detach_only=true| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the disk should only be detached from the virtual machine, but not removed from the system. |
6.43.2.1. detach_only
Indicates if the disk should only be detached from the virtual machine, but not removed from the system. The default value is true, which won’t remove the disk from the system.
6.43.3. update PUT
Update the disk attachment and the disk properties within it.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.44. DiskAttachments
This service manages the set of disks attached to a virtual machine. Each attached disk is represented by a DiskAttachment, containing the bootable flag, the disk interface and the reference to the disk.
| Name | Summary |
|---|---|
|
| Adds a new disk attachment to the virtual machine. |
|
| List the disk that are attached to the virtual machine. |
6.44.1. add POST
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 |
6.44.2. list GET
List the disk that are attached to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.45. DiskProfile
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.45.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.45.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.45.3. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.46. DiskProfiles
| Name | Summary |
|---|---|
|
| |
|
|
6.46.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.46.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out |
6.46.2.1. max
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.47. DiskSnapshot
| Name | Summary |
|---|---|
|
| |
|
|
6.47.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.47.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.48. DiskSnapshots
| Name | Summary |
|---|---|
|
|
6.48.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of snapshots to return. | |
|
| Out |
6.48.1.1. max
Sets the maximum number of snapshots to return. If not specified all the snapshots are returned.
6.49. Disks
Manages the collection of disks available in the system.
| Name | Summary |
|---|---|
|
| Adds a new floating disk. |
|
| Get list of disks. |
6.49.1. add POST
Adds a new floating disk.
There are three types of disks that can be added - disk image, direct LUN and Cinder disk.
Adding a new image disk:
When creating a new floating image Disk, the API requires the storage_domain, provisioned_size and format attributes.
To create a new floating image disk with specified provisioned_size, format and name on a storage domain with an id 123, send a request as follows:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disksWith a request body as follows:
Adding a new direct LUN disk:
When adding a new floating direct LUN via the API, there are two flavors that can be used:
-
With a
hostelement - in this case, the host is used for sanity checks (e.g., that the LUN is visible) and to retrieve basic information about the LUN (e.g., size and serial). -
Without a
hostelement - in this case, the operation is a database-only operation, and the storage is never accessed.
To create a new floating direct LUN disk with a host element with an id 123, specified alias, type and logical_unit with an id 456 (that has the attributes address, port and target), send a request as follows:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disksWith a request body as follows:
To create a new floating direct LUN disk without using a host, remove the host element.
Adding a new Cinder disk:
To create a new floating Cinder disk, send a request as follows:
POST /ovirt-engine/api/disks
POST /ovirt-engine/api/disksWith a request body as follows:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The disk. |
6.49.2. list GET
Get list of disks.
GET /ovirt-engine/api/disks
GET /ovirt-engine/api/disksYou 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. | |
|
| In | Indicates whether to retrieve a list of registered or unregistered disks in the storage domain. |
6.49.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.49.2.2. max
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.49.2.3. unregistered
Indicates whether to retrieve a list of registered or unregistered disks in the storage domain. To get a list of unregistered disks in the storage domain the call should indicate the unregistered flag. For example, to get a list of unregistered disks the REST API call should look like this:
GET /ovirt-engine/api/storagedomains/123/disks?unregistered=true
GET /ovirt-engine/api/storagedomains/123/disks?unregistered=true
The default value of the unregistered flag is false.
This parameter only applies to the disks sub-collection of attached storage domains, it does not apply to the top level disks collection.
6.50. Domain
A service to view details of an authentication domain in the system.
| Name | Summary |
|---|---|
|
| Gets the authentication domain information. |
6.50.1. get GET
Gets the authentication domain information.
Usage:
GET /ovirt-engine/api/domains/5678
GET /ovirt-engine/api/domains/5678Will return the domain information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The authentication domain. |
6.51. DomainGroup
| Name | Summary |
|---|---|
|
|
6.51.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.52. DomainGroups
| Name | Summary |
|---|---|
|
|
6.52.1. list GET
| 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. |
6.52.1.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.52.1.2. max
Sets the maximum number of groups to return. If not specified all the groups are returned.
6.53. DomainUser
A service to view a domain user in the system.
| Name | Summary |
|---|---|
|
| Gets the domain user information. |
6.53.1. get GET
Gets the domain user information.
Usage:
GET /ovirt-engine/api/domains/5678/users/1234
GET /ovirt-engine/api/domains/5678/users/1234Will return the domain user information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The domain user. |
6.54. DomainUsers
A service to list all domain users in the system.
| Name | Summary |
|---|---|
|
| List all the users in the domain. |
6.54.1. list GET
List all the users in the domain.
Usage:
GET /ovirt-engine/api/domains/5678/users
GET /ovirt-engine/api/domains/5678/usersWill 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. |
6.54.1.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.54.1.2. max
Sets the maximum number of users to return. If not specified all the users are returned.
6.55. Domains
A service to list all authentication domains in the system.
| Name | Summary |
|---|---|
|
| List all the authentication domains in the system. |
6.55.1. list GET
List all the authentication domains in the system.
Usage:
GET /ovirt-engine/api/domains
GET /ovirt-engine/api/domainsWill return the list of domains:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of domains. | |
|
| In | Sets the maximum number of domains to return. |
6.55.1.1. max
Sets the maximum number of domains to return. If not specified all the domains are returned.
6.56. EngineKatelloErrata
A service to manage Katello errata assigned to the engine. The information is retrieved from Katello.
| Name | Summary |
|---|---|
|
| Retrieves the representation of the Katello errata. |
6.56.1. list GET
Retrieves the representation of the Katello errata.
GET /ovirt-engine/api/katelloerrata
GET /ovirt-engine/api/katelloerrataYou 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. |
6.56.1.1. max
Sets the maximum number of errata to return. If not specified all the errata are returned.
6.57. Event
A service to manage an event in the system.
| Name | Summary |
|---|---|
|
| Get an event. |
|
| Removes an event from internal audit log. |
6.57.1. get GET
Get an event.
An example of getting an event:
GET /ovirt-engine/api/events/123
GET /ovirt-engine/api/events/123Note 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 |
6.57.2. remove DELETE
Removes an event from internal audit log.
An event can be removed by sending following request
DELETE /ovirt-engine/api/events/123
DELETE /ovirt-engine/api/events/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.58. Events
A service to manage events in the system.
| Name | Summary |
|---|---|
|
| Adds an external event to the internal audit log. |
|
| Get list of events. |
|
|
6.58.1. add POST
Adds an external event to the internal audit log.
This is intended for integration with external systems that detect or produce events relevant for the administrator of the system. For example, an external monitoring tool may be able to detect that a file system is full inside the guest operating system of a virtual machine. This event can be added to the internal audit log sending a request like this:
Events can also be linked to specific objects. For example, the above event could be linked to the specific virtual machine where it happened, using the vm link:
When using links, like the vm in the previous example, only the id attribute is accepted. The name attribute, if provided, is simply ignored.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.58.2. list GET
Get list of events.
GET /ovirt-engine/api/events
GET /ovirt-engine/api/eventsTo 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. |
6.58.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.58.2.2. from
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=123This parameter is optional, and if not specified then the first event returned will be most recently generated.
6.58.2.3. max
Sets the maximum number of events to return. If not specified all the events are returned.
6.58.2.4. search
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 1Below 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%201Increase 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%2026.58.3. undelete POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the un-delete should be performed asynchronously. |
6.59. ExternalComputeResource
| Name | Summary |
|---|---|
|
|
6.59.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.60. ExternalComputeResources
| Name | Summary |
|---|---|
|
|
6.60.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of resources to return. | |
|
| Out |
6.60.1.1. max
Sets the maximum number of resources to return. If not specified all the resources are returned.
6.61. ExternalDiscoveredHost
| Name | Summary |
|---|---|
|
|
6.61.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.62. ExternalDiscoveredHosts
| Name | Summary |
|---|---|
|
|
6.62.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. |
6.62.1.1. max
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
6.63. ExternalHost
| Name | Summary |
|---|---|
|
|
6.63.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.64. ExternalHostGroup
| Name | Summary |
|---|---|
|
|
6.64.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.65. ExternalHostGroups
| Name | Summary |
|---|---|
|
|
6.65.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of groups to return. |
6.65.1.1. max
Sets the maximum number of groups to return. If not specified all the groups are returned.
6.66. ExternalHostProvider
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
6.66.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.66.2. importcertificates POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.66.3. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.66.4. testconnectivity POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.66.5. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.67. ExternalHostProviders
| Name | Summary |
|---|---|
|
| |
|
|
6.67.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.67.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
6.67.2.1. max
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.68. ExternalHosts
| Name | Summary |
|---|---|
|
|
6.68.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hosts to return. |
6.68.1.1. max
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
6.69. ExternalProvider
| Name | Summary |
|---|---|
|
| |
|
|
6.69.1. importcertificates POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.69.2. testconnectivity POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.70. ExternalProviderCertificate
| Name | Summary |
|---|---|
|
|
6.70.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.71. ExternalProviderCertificates
| Name | Summary |
|---|---|
|
|
6.71.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of certificates to return. |
6.71.1.1. max
Sets the maximum number of certificates to return. If not specified all the certificates are returned.
6.72. ExternalVmImports
Provides capability to import external virtual machines.
| Name | Summary |
|---|---|
|
| This operation is used to import a virtual machine from external hypervisor, such as KVM, XEN or VMware. |
6.72.1. add POST
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 /externalvmimportsWith request body of type ExternalVmImport, for example:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.73. FenceAgent
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.73.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.73.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.73.3. update PUT
6.74. FenceAgents
| Name | Summary |
|---|---|
|
| |
|
|
6.74.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.74.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of agents to return. |
6.74.2.1. max
Sets the maximum number of agents to return. If not specified all the agents are returned.
6.75. File
| Name | Summary |
|---|---|
|
|
6.75.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.76. Files
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 |
|---|---|
|
|
6.76.1. list GET
| 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. |
6.76.1.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.76.1.2. max
Sets the maximum number of files to return. If not specified all the files are returned.
6.77. Filter
| Name | Summary |
|---|---|
|
| |
|
|
6.77.1. get GET
6.77.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.78. Filters
| Name | Summary |
|---|---|
|
| |
|
|
6.78.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.78.2. list GET
| 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. |
6.78.2.1. max
Sets the maximum number of filters to return. If not specified all the filters are returned.
6.79. GlusterBrick
This service manages a single gluster brick.
| Name | Summary |
|---|---|
|
| Get details of a brick. |
|
| Removes a brick. |
|
| Replaces this brick with a new one. |
6.79.1. get GET
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/234Which will return a response body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.79.2. remove DELETE
Removes a brick.
Removes a brick from the underlying gluster volume and deletes entries from database. This can be used only when removing a single brick without data migration. To remove multiple bricks and with data migration, use migrate instead.
For example, to delete brick 234 from gluster volume 123, send a request like this:
DELETE /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/234
DELETE /ovirt-engine/api/clusters/567/glustervolumes/123/glusterbricks/234| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.79.3. replace POST
Replaces this brick with a new one.
This operation has been deprecated since version 3.5 of the engine and will be removed in the future. Use add brick(s) and migrate brick(s) instead.
6.80. GlusterBricks
This service manages the gluster bricks in a gluster volume
| Name | Summary |
|---|---|
|
| Activate the bricks post data migration of remove brick operation. |
|
| Adds a list of bricks to gluster volume. |
|
| Lists the bricks of a gluster volume. |
|
| Start migration of data prior to removing bricks. |
|
| Removes bricks from gluster volume. |
|
| Stops migration of data from bricks for a remove brick operation. |
6.80.1. activate POST
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/activateWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. | |
|
| In | The list of bricks that need to be re-activated. |
6.80.2. add POST
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/glusterbricksWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The list of bricks to be added to the volume | |
|
| In | Replica count of volume post add operation. | |
|
| In | Stripe count of volume post add operation. |
6.80.3. list GET
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/glusterbricksProvides an output as below:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of bricks to return. |
6.80.3.1. max
Sets the maximum number of bricks to return. If not specified all the bricks are returned.
6.80.4. migrate POST
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/migrateWith a request body like this:
The migration process can be tracked from the job id returned from the API using job and steps in job using step
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should be performed asynchronously. | |
|
| In | List of bricks for which data migration needs to be started. |
6.80.5. remove DELETE
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/glusterbricksWith a request body like this:
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | The list of bricks to be removed | |
|
| In | Replica count of volume post add operation. |
6.80.6. stopmigrate POST
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/stopmigrateWith a request body like this:
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>
<bricks>
<brick>
<name>host:brick_directory</name>
</brick>
</bricks>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | List of bricks for which data migration needs to be stopped. |
6.80.6.1. bricks
List of bricks for which data migration needs to be stopped. This list should match the arguments passed to migrate.
6.81. GlusterHook
| Name | Summary |
|---|---|
|
| Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. |
|
| Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. |
|
| |
|
| Removes the this Gluster hook from all servers in cluster and deletes it from the database. |
|
| Resolves missing hook conflict depending on the resolution type. |
6.81.1. disable POST
Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. This updates the hook status to DISABLED in database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.81.2. enable POST
Resolves status conflict of hook among servers in cluster by disabling Gluster hook in all servers of the cluster. This updates the hook status to DISABLED in database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.81.3. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.81.4. remove DELETE
Removes the this Gluster hook from all servers in cluster and deletes it from the database.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.81.5. resolve POST
Resolves missing hook conflict depending on the resolution type.
For ADD resolves by copying hook stored in engine database to all servers where the hook is missing. The engine maintains a list of all servers where hook is missing.
For COPY resolves conflict in hook content by copying hook stored in engine database to all servers where the hook is missing. The engine maintains a list of all servers where the content is conflicting. If a host id is passed as parameter, the hook content from the server is used as the master to copy to other servers in cluster.
6.82. GlusterHooks
| Name | Summary |
|---|---|
|
|
6.82.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hooks to return. |
6.82.1.1. max
Sets the maximum number of hooks to return. If not specified all the hooks are returned.
6.83. GlusterVolume
This service manages a single gluster volume.
| Name | Summary |
|---|---|
|
| Get the gluster volume details. |
|
| Get gluster volume profile statistics. |
|
| Rebalance the gluster volume. |
|
| Removes the gluster volume. |
|
| Resets all the options set in the gluster volume. |
|
| Resets a particular option in the gluster volume. |
|
| Sets a particular option in the gluster volume. |
|
| Starts the gluster volume. |
|
| Start profiling the gluster volume. |
|
| Stops the gluster volume. |
|
| Stop profiling the gluster volume. |
|
| Stop rebalancing the gluster volume. |
6.83.1. get GET
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/123This GET request will return the following output:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Representation of the gluster volume. |
6.83.2. getprofilestatistics POST
Get gluster volume profile statistics.
For example, to get profile statistics for a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/getprofilestatistics
POST /ovirt-engine/api/clusters/456/glustervolumes/123/getprofilestatistics| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Gluster volume profiling information returned from the action. |
6.83.3. rebalance POST
Rebalance the gluster volume.
Rebalancing a gluster volume helps to distribute the data evenly across all the bricks. After expanding or shrinking a gluster volume (without migrating data), we need to rebalance the data among the bricks. In a non-replicated volume, all bricks should be online to perform the rebalance operation. In a replicated volume, at least one of the bricks in the replica should be online.
For example, to rebalance a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/rebalance
POST /ovirt-engine/api/clusters/456/glustervolumes/123/rebalance| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the rebalance should be performed asynchronously. | |
|
| In | If set to true, rebalance will only fix the layout so that new data added to the volume is distributed across all the hosts. | |
|
| In | Indicates if the rebalance should be force started. |
6.83.3.1. fix_layout
If set to true, rebalance will only fix the layout so that new data added to the volume is distributed across all the hosts. But it will not migrate/rebalance the existing data. Default is false.
6.83.3.2. force
Indicates if the rebalance should be force started. The rebalance command can be executed with the force option even when the older clients are connected to the cluster. However, this could lead to a data loss situation. Default is false.
6.83.4. remove DELETE
Removes the gluster volume.
For example, to remove a volume with identifier 123 in cluster 456, send a request like this:
DELETE /ovirt-engine/api/clusters/456/glustervolumes/123
DELETE /ovirt-engine/api/clusters/456/glustervolumes/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.83.5. resetalloptions POST
Resets all the options set in the gluster volume.
For example, to reset all options in a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/resetalloptions
POST /ovirt-engine/api/clusters/456/glustervolumes/123/resetalloptions| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reset should be performed asynchronously. |
6.83.6. resetoption POST
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/resetoptionWith the following request body:
<action> <option name="option1"/> </action>
<action>
<option name="option1"/>
</action>6.83.7. setoption POST
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/setoptionWith the following request body:
<action> <option name="option1" value="value1"/> </action>
<action>
<option name="option1" value="value1"/>
</action>6.83.8. start POST
Starts the gluster volume.
A Gluster Volume should be started to read/write data. For example, to start a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/start
POST /ovirt-engine/api/clusters/456/glustervolumes/123/start| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Indicates if the volume should be force started. |
6.83.8.1. force
Indicates if the volume should be force started. If a gluster volume is started already but few/all bricks are down then force start can be used to bring all the bricks up. Default is false.
6.83.9. startprofile POST
Start profiling the gluster volume.
For example, to start profiling a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/startprofile
POST /ovirt-engine/api/clusters/456/glustervolumes/123/startprofile| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.83.10. stop POST
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/stop6.83.11. stopprofile POST
Stop profiling the gluster volume.
For example, to stop profiling a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stopprofile
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stopprofile| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.83.12. stoprebalance POST
Stop rebalancing the gluster volume.
For example, to stop rebalancing a gluster volume with identifier 123 in cluster 456, send a request like this:
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stoprebalance
POST /ovirt-engine/api/clusters/456/glustervolumes/123/stoprebalance| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.84. GlusterVolumes
This service manages a collection of gluster volumes available in a cluster.
| Name | Summary |
|---|---|
|
| Creates a new gluster volume. |
|
| Lists all gluster volumes in the cluster. |
6.84.1. add POST
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/glustervolumesWith the following request body:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The gluster volume definition from which to create the volume is passed as input and the newly created volume is returned. |
6.84.2. list GET
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 |
6.84.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.84.2.2. max
Sets the maximum number of volumes to return. If not specified all the volumes are returned.
6.85. Group
| Name | Summary |
|---|---|
|
| |
|
|
6.85.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.85.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.86. Groups
| Name | Summary |
|---|---|
|
| Add group from a directory service. |
|
|
6.86.1. add POST
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/groupsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.86.2. list GET
| 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. |
6.86.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.86.2.2. max
Sets the maximum number of groups to return. If not specified all the groups are returned.
6.87. Host
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. |
|
| Check if there are upgrades available for the host. |
6.87.1. activate POST
Activate the host for use, such as running virtual machines.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.87.2. approve POST
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.
6.87.3. commitnetconfig POST
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/commitnetconfigWith a request body like this:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.87.4. deactivate POST
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. |
6.87.4.1. stop_gluster_service
Indicates if the gluster service should be stopped as part of deactivating the host. It can be used while performing maintenance operations on the gluster host. Default value for this variable is false.
6.87.5. enrollcertificate POST
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. |
6.87.6. fence POST
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 |
6.87.7. forceselectspm POST
Manually set a host as the storage pool manager (SPM).
POST /ovirt-engine/api/hosts/123/forceselectspm
POST /ovirt-engine/api/hosts/123/forceselectspmWith a request body like this:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.87.8. get GET
Get the host details.
6.87.9. install POST
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:
Since version 4.1.2 of the engine when a host is reinstalled we override the host firewall definitions by default.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | 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 |
6.87.9.1. deploy_hosted_engine
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.
6.87.9.2. undeploy_hosted_engine
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.
6.87.10. iscsidiscover POST
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. |
6.87.11. iscsilogin POST
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. |
6.87.12. refresh POST
Refresh the host devices and capabilities.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the refresh should be performed asynchronously. |
6.87.13. remove DELETE
Remove the host from the system.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.87.14. setupnetworks POST
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 |
6.87.15. unregisteredstoragedomainsdiscover POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the discovery should be performed asynchronously. | |
|
| In | ||
|
| Out |
6.87.16. update PUT
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/123With request body like this:
<host>
<os>
<custom_kernel_cmdline>vfio_iommu_type1.allow_unsafe_interrupts=1</custom_kernel_cmdline>
</os>
</host>
<host>
<os>
<custom_kernel_cmdline>vfio_iommu_type1.allow_unsafe_interrupts=1</custom_kernel_cmdline>
</os>
</host>6.87.17. upgrade POST
Upgrade VDSM and selected software on the host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the upgrade should be performed asynchronously. |
6.87.18. upgradecheck POST
Check if there are upgrades available for the host. If there are upgrades available an icon will be displayed next to host status icon in the webadmin. Audit log messages are also added to indicate the availability of upgrades. The upgrade can be started from the webadmin or by using the upgrade host action.
6.88. HostDevice
A service to access a particular device of a host.
| Name | Summary |
|---|---|
|
| Retrieve information about a particular host’s device. |
6.88.1. get GET
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 |
6.89. HostDevices
A service to access host devices.
| Name | Summary |
|---|---|
|
| List the devices of a host. |
6.89.1. list GET
List the devices of a host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of devices to return. |
6.89.1.1. max
Sets the maximum number of devices to return. If not specified all the devices are returned.
6.90. HostHook
| Name | Summary |
|---|---|
|
|
6.90.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.91. HostHooks
| Name | Summary |
|---|---|
|
|
6.91.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of hooks to return. |
6.91.1.1. max
Sets the maximum number of hooks to return. If not specified all the hooks are returned.
6.92. HostNic
A service to manage a network interface of a host.
| Name | Summary |
|---|---|
|
| |
|
| The action updates virtual function configuration in case the current resource represents an SR-IOV enabled NIC. |
6.92.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.92.2. updatevirtualfunctionsconfiguration POST
The action updates virtual function configuration in case the current resource represents an SR-IOV enabled NIC. The input should be consisted of at least one of the following properties:
-
allNetworksAllowed -
numberOfVirtualFunctions
Please see the HostNicVirtualFunctionsConfiguration type for the meaning of the properties.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In |
6.93. HostNics
A service to manage the network interfaces of a host.
| Name | Summary |
|---|---|
|
|
6.93.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
6.93.1.1. max
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.94. HostNumaNode
| Name | Summary |
|---|---|
|
|
6.94.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.95. HostNumaNodes
| Name | Summary |
|---|---|
|
|
6.95.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of nodes to return. | |
|
| Out |
6.95.1.1. max
Sets the maximum number of nodes to return. If not specified all the nodes are returned.
6.96. HostStorage
A service to manage host storages.
| Name | Summary |
|---|---|
|
| Get list of storages. |
6.96.1. list GET
Get list of storages.
GET /ovirt-engine/api/hosts/123/storage
GET /ovirt-engine/api/hosts/123/storageThe 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. |
6.96.1.1. report_status
Indicates if the status of the LUNs in the storage should be checked. Checking the status of the LUN is an heavy weight operation and this data is not always needed by the user. This parameter will give the option to not perform the status check of the LUNs.
The default is true for backward compatibility.
Here an example with the LUN status :
Here an example without the LUN status :
6.97. Hosts
A service that manages hosts.
| Name | Summary |
|---|---|
|
| Creates a new host. |
|
| Get a list of all available hosts. |
6.97.1. add POST
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/hostsWith the following request body:
<host> <name>myhost</name> <address>myhost.example.com</address> <root_password>myrootpassword</root_password> </host>
<host>
<name>myhost</name>
<address>myhost.example.com</address>
<root_password>myrootpassword</root_password>
</host>
The root_password element is only included in the client-provided initial representation and is not exposed in the representations returned from subsequent requests.
Since version 4.1.2 of the engine when a host is newly added we override the host firewall definitions by default.
To add a hosted engine host, use the optional deploy_hosted_engine parameter:
POST /ovirt-engine/api/hosts?deploy_hosted_engine=true
POST /ovirt-engine/api/hosts?deploy_hosted_engine=true| 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 |
6.97.1.1. deploy_hosted_engine
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.
6.97.1.2. undeploy_hosted_engine
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.
6.97.2. list GET
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/hostsThe 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. |
6.97.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.97.2.2. max
Sets the maximum number of hosts to return. If not specified all the hosts are returned.
6.98. Icon
A service to manage an icon (read-only).
| Name | Summary |
|---|---|
|
| Get an icon. |
6.98.1. get GET
Get an icon.
GET /ovirt-engine/api/icons/123
GET /ovirt-engine/api/icons/123You 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. |
6.99. Icons
A service to manage icons.
| Name | Summary |
|---|---|
|
| Get a list of icons. |
6.99.1. list GET
Get a list of icons.
GET /ovirt-engine/api/icons
GET /ovirt-engine/api/iconsYou 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. |
6.99.1.1. max
Sets the maximum number of icons to return. If not specified all the icons are returned.
6.100. Image
| Name | Summary |
|---|---|
|
| |
|
| Imports an image. |
6.100.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.100.2. import POST
Imports an image.
If the import_as_template parameter is true then the image will be imported as a template, otherwise it will be imported as a disk.
When imported as a template, the name of the template can be specified by the optional template.name parameter. If that parameter is not specified, then the name of the template will be automatically assigned by the engine as GlanceTemplate-x (where x will be seven random hexadecimal characters).
When imported as a disk, the name of the disk can be specified by the optional disk.name parameter. If that parameter is not specified, then the name of the disk will be automatically assigned by the engine as GlanceDisk-x (where x will be the seven hexadecimal characters of the image identifier).
It is recommended to always explicitly specify the template or disk name, to avoid these automatic names generated by the engine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In |
The cluster to which the image should be imported if the | |
|
| In | The disk to import. | |
|
| In | Specifies if a template should be created from the imported disk. | |
|
| In | The storage domain to which the disk should be imported. | |
|
| In |
The name of the template being created if the |
6.101. ImageTransfer
This service provides a mechanism to control an image transfer. The client will have to create a transfer by using add of the Section 6.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:
If the user wishes to download a disk rather than upload, he/she should specify download as the direction attribute of the transfer. This will grant a read permission from the image, instead of a write permission.
E.g:
Transfers have phases, which govern the flow of the upload/download. A client implementing such a flow should poll/check the transfer’s phase and act accordingly. All the possible phases can be found in ImageTransferPhase.
After adding a new transfer, its phase will be initializing. The client will have to poll on the transfer’s phase until it changes. When the phase becomes transferring, the session is ready to start the transfer.
For example:
transfer_service = transfers_service.image_transfer_service(transfer.id) while transfer.phase == types.ImageTransferPhase.INITIALIZING: time.sleep(3) transfer = transfer_service.get()
transfer_service = transfers_service.image_transfer_service(transfer.id)
while transfer.phase == types.ImageTransferPhase.INITIALIZING:
time.sleep(3)
transfer = transfer_service.get()At that stage, if the 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 a transfer, so an transfer_headers dict is set for the upcoming transfer:
transfer_headers = {
'Authorization' : transfer.signed_ticket,
}
transfer_headers = {
'Authorization' : transfer.signed_ticket,
}
Using Python’s HTTPSConnection, a new connection is established:
For upload, 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:
Similarly, for a download transfer, a Range header must be sent, making the download process more easily managed by downloading the disk in chunks.
E.g., the client will again iterate on chunks of the disk image, but this time he/she will download it to a local file, rather than uploading its own file to the image:
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. |
6.101.1. extend POST
Extend the image transfer session.
6.101.2. finalize POST
After finishing to transfer the data, finalize the transfer.
This will make sure that the data being transferred is valid and fits the image entity that was targeted in the transfer. Specifically, will verify that if the image entity is a QCOW disk, the data uploaded is indeed a QCOW file, and that the image doesn’t have a backing file.
6.101.3. get GET
Get the image transfer entity.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.101.4. pause POST
Pause the image transfer session.
6.101.5. resume POST
Resume the image transfer session. The client will need to poll the transfer’s phase until it is different than resuming. For example:
6.102. ImageTransfers
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. |
6.102.1. add POST
Add a new image transfer. An image needs to be specified in order to make a new transfer.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.102.2. list GET
Retrieves the list of image transfers that are currently being performed.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.103. Images
| Name | Summary |
|---|---|
|
|
6.103.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of images to return. |
6.103.1.1. max
Sets the maximum number of images to return. If not specified all the images are returned.
6.104. InstanceType
| Name | Summary |
|---|---|
|
| Get a specific instance type and it’s attributes. |
|
| Removes a specific instance type from the system. |
|
| Update a specific instance type and it’s attributes. |
6.104.1. get GET
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 |
6.104.2. remove DELETE
Removes a specific instance type from the system.
If a virtual machine was created using an instance type X after removal of the instance type the virtual machine’s instance type will be set to custom.
DELETE /ovirt-engine/api/instancetypes/123
DELETE /ovirt-engine/api/instancetypes/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.104.3. update PUT
Update a specific instance type and it’s attributes.
All the attributes are editable after creation. If a virtual machine was created using an instance type X and some configuration in instance type X was updated, the virtual machine’s configuration will be updated automatically by the engine.
PUT /ovirt-engine/api/instancetypes/123
PUT /ovirt-engine/api/instancetypes/123
For example, to update the memory of instance type 123 to 1 GiB and set the cpu topology to 2 sockets and 1 core, send a request like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.105. InstanceTypeGraphicsConsole
| Name | Summary |
|---|---|
|
| Gets graphics console configuration of the instance type. |
|
| Remove the graphics console from the instance type. |
6.105.1. get GET
Gets graphics console configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the graphics console of the instance type. |
6.105.2. remove DELETE
Remove the graphics console from the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.106. InstanceTypeGraphicsConsoles
| Name | Summary |
|---|---|
|
| Add new graphics console to the instance type. |
|
| Lists all the configured graphics consoles of the instance type. |
6.106.1. add POST
Add new graphics console to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.106.2. list GET
Lists all the configured graphics consoles of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of graphics consoles of the instance type. | |
|
| In | Sets the maximum number of consoles to return. |
6.106.2.1. max
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
6.107. InstanceTypeNic
| Name | Summary |
|---|---|
|
| Gets network interface configuration of the instance type. |
|
| Remove the network interface from the instance type. |
|
| Updates the network interface configuration of the instance type. |
6.107.1. get GET
Gets network interface configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.107.2. remove DELETE
Remove the network interface from the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.107.3. update PUT
Updates the network interface configuration of the instance type.
6.108. InstanceTypeNics
| Name | Summary |
|---|---|
|
| Add new network interface to the instance type. |
|
| Lists all the configured network interface of the instance type. |
6.108.1. add POST
Add new network interface to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.108.2. list GET
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. |
6.108.2.1. max
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.109. InstanceTypeWatchdog
| Name | Summary |
|---|---|
|
| Gets watchdog configuration of the instance type. |
|
| Remove a watchdog from the instance type. |
|
| Updates the watchdog configuration of the instance type. |
6.109.1. get GET
Gets watchdog configuration of the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.109.2. remove DELETE
Remove a watchdog from the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.109.3. update PUT
Updates the watchdog configuration of the instance type.
6.110. InstanceTypeWatchdogs
| Name | Summary |
|---|---|
|
| Add new watchdog to the instance type. |
|
| Lists all the configured watchdogs of the instance type. |
6.110.1. add POST
Add new watchdog to the instance type.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.110.2. list GET
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 |
6.110.2.1. max
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
6.111. InstanceTypes
| Name | Summary |
|---|---|
|
| Creates a new instance type. |
|
| Lists all existing instance types in the system. |
6.111.1. add POST
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/instancetypesWith a request body like this:
<instance_type> <name>myinstancetype</name> </template>
<instance_type>
<name>myinstancetype</name>
</template>Creating an instance type with all hardware configurations with a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.111.2. list GET
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. |
6.111.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.111.2.2. max
Sets the maximum number of instance types to return. If not specified all the instance types are returned.
6.112. IscsiBond
| Name | Summary |
|---|---|
|
| |
|
| Removes of an existing iSCSI bond. |
|
| Updates an iSCSI bond. |
6.112.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.112.2. remove DELETE
Removes of an existing iSCSI bond.
For example, to remove the iSCSI bond 456 send a request like this:
DELETE /ovirt-engine/api/datacenters/123/iscsibonds/456
DELETE /ovirt-engine/api/datacenters/123/iscsibonds/456| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.112.3. update PUT
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/1234The request body should look like this:
<iscsi_bond> <name>mybond</name> <description>My iSCSI bond</description> </iscsi_bond>
<iscsi_bond>
<name>mybond</name>
<description>My iSCSI bond</description>
</iscsi_bond>6.113. IscsiBonds
| Name | Summary |
|---|---|
|
| Create a new iSCSI bond on a data center. |
|
|
6.113.1. add POST
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/iscsibondsThe request body should look like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.113.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of bonds to return. |
6.113.2.1. max
Sets the maximum number of bonds to return. If not specified all the bonds are returned.
6.114. Job
A service to manage a job.
| Name | Summary |
|---|---|
|
| Set an external job execution to be cleared by the system. |
|
| Marks an external job execution as ended. |
|
| Retrieves a job. |
6.114.1. clear POST
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/clearWith the following request body:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.114.2. end POST
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/endWith the following request body:
<action> <force>true</force> <status>finished</status> </action>
<action>
<force>true</force>
<status>finished</status>
</action>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Indicates if the job should be forcibly terminated. | |
|
| In | Indicates if the job should be marked as successfully finished or as failed. |
6.114.2.1. succeeded
Indicates if the job should be marked as successfully finished or as failed.
This parameter is optional, and the default value is true.
6.114.3. get GET
Retrieves a job.
GET /ovirt-engine/api/jobs/123
GET /ovirt-engine/api/jobs/123You will receive response in XML like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieves the representation of the job. |
6.115. Jobs
A service to manage jobs.
| Name | Summary |
|---|---|
|
| Add an external job. |
|
| Retrieves the representation of the jobs. |
6.115.1. add POST
Add an external job.
For example, to add a job with the following request:
POST /ovirt-engine/api/jobs
POST /ovirt-engine/api/jobsWith the following request body:
<job> <description>Doing some work</description> <auto_cleared>true</auto_cleared> </job>
<job>
<description>Doing some work</description>
<auto_cleared>true</auto_cleared>
</job>The response should look like:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Job that will be added. |
6.115.2. list GET
Retrieves the representation of the jobs.
GET /ovirt-engine/api/jobs
GET /ovirt-engine/api/jobsYou 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. |
6.115.2.1. max
Sets the maximum number of jobs to return. If not specified all the jobs are returned.
6.116. KatelloErrata
A service to manage Katello errata. The information is retrieved from Katello.
| Name | Summary |
|---|---|
|
| Retrieves the representation of the Katello errata. |
6.116.1. list GET
Retrieves the representation of the Katello errata.
GET /ovirt-engine/api/katelloerrata
GET /ovirt-engine/api/katelloerrataYou 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. |
6.116.1.1. max
Sets the maximum number of errata to return. If not specified all the errata are returned.
6.117. KatelloErratum
A service to manage a Katello erratum.
| Name | Summary |
|---|---|
|
| Retrieves a Katello erratum. |
6.117.1. get GET
Retrieves a Katello erratum.
GET /ovirt-engine/api/katelloerrata/123
GET /ovirt-engine/api/katelloerrata/123You will receive response in XML like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieves the representation of the Katello erratum. |
6.118. MacPool
| Name | Summary |
|---|---|
|
| |
|
| Removes a MAC address pool. |
|
| Updates a MAC address pool. |
6.118.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.118.2. remove DELETE
Removes a MAC address pool.
For example, to remove the MAC address pool having id 123 send a request like this:
DELETE /ovirt-engine/api/macpools/123
DELETE /ovirt-engine/api/macpools/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.118.3. update PUT
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/123With a request body like this:
6.119. MacPools
| Name | Summary |
|---|---|
|
| Creates a new MAC address pool. |
|
|
6.119.1. add POST
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/macpoolsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.119.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of pools to return. | |
|
| Out |
6.119.2.1. max
Sets the maximum number of pools to return. If not specified all the pools are returned.
6.120. Measurable
6.121. Moveable
| Name | Summary |
|---|---|
|
|
6.121.1. move POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the move should be performed asynchronously. |
6.122. Network
A service managing a network
| Name | Summary |
|---|---|
|
| Gets a logical network. |
|
| Removes a logical network, or the association of a logical network to a data center. |
|
| Updates a logical network. |
6.122.1. get GET
Gets a logical network.
For example:
GET /ovirt-engine/api/networks/123
GET /ovirt-engine/api/networks/123Will respond:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.122.2. remove DELETE
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. |
6.122.3. update PUT
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/123With 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/456With a request body like this:
<network> <mtu>1500</mtu> </network>
<network>
<mtu>1500</mtu>
</network>6.123. NetworkAttachment
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.123.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.123.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.123.3. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.124. NetworkAttachments
| Name | Summary |
|---|---|
|
| |
|
|
6.124.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.124.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of attachments to return. |
6.124.2.1. max
Sets the maximum number of attachments to return. If not specified all the attachments are returned.
6.125. NetworkFilter
Manages a network filter.
Please note that version is referring to the minimal support version for the specific filter.
| Name | Summary |
|---|---|
|
| Retrieves a representation of the network filter. |
6.125.1. get GET
Retrieves a representation of the network filter.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.126. NetworkFilters
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}/networkfiltersOutput:
| Name | Summary |
|---|---|
|
| Retrieves the representations of the network filters. |
6.126.1. list GET
Retrieves the representations of the network filters.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.127. NetworkLabel
| Name | Summary |
|---|---|
|
| |
|
| Removes a label from a logical network. |
6.127.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.127.2. remove DELETE
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. |
6.128. NetworkLabels
| Name | Summary |
|---|---|
|
| Attaches label to logical network. |
|
|
6.128.1. add POST
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/labelsWith a request body like this:
<label id="mylabel"/>
<label id="mylabel"/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.128.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of labels to return. |
6.128.2.1. max
Sets the maximum number of labels to return. If not specified all the labels are returned.
6.129. Networks
Manages logical networks.
The engine creates a default ovirtmgmt network on installation. This network acts as the management network for access to hypervisor hosts. This network is associated with the Default cluster and is a member of the Default data center.
| Name | Summary |
|---|---|
|
| Creates a new logical network, or associates an existing network with a data center. |
|
| List logical networks. |
6.129.1. add POST
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/networksWith 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/networksWith a request body like this:
<network> <name>ovirtmgmt</name> </network>
<network>
<name>ovirtmgmt</name>
</network>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.129.2. list GET
List logical networks.
For example:
GET /ovirt-engine/api/networks
GET /ovirt-engine/api/networksWill 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. |
6.129.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.129.2.2. max
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.130. OpenstackImage
| Name | Summary |
|---|---|
|
| |
|
| Imports a virtual machine from a Glance image storage domain. |
6.130.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.130.2. import POST
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/importWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In |
This parameter is mandatory in case of using | |
|
| In | ||
|
| In | Indicates whether the image should be imported as a template. | |
|
| In | ||
|
| In |
6.131. OpenstackImageProvider
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
6.131.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.131.2. importcertificates POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.131.3. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.131.4. testconnectivity POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.131.5. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.132. OpenstackImageProviders
| Name | Summary |
|---|---|
|
| |
|
|
6.132.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.132.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
6.132.2.1. max
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.133. OpenstackImages
| Name | Summary |
|---|---|
|
| Lists the images of a Glance image storage domain. |
6.133.1. list GET
Lists the images of a Glance image storage domain.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of images to return. |
6.133.1.1. max
Sets the maximum number of images to return. If not specified all the images are returned.
6.134. OpenstackNetwork
| Name | Summary |
|---|---|
|
| |
|
| This operation imports an external network into oVirt. |
6.134.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.134.2. import POST
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. |
6.134.2.1. data_center
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.
6.135. OpenstackNetworkProvider
This service manages OpenStack network provider.
| Name | Summary |
|---|---|
|
| Returns the representation of the object managed by this service. |
|
| |
|
| Removes the provider. |
|
| |
|
| Updates the provider. |
6.135.1. get GET
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 |
6.135.2. importcertificates POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.135.3. remove DELETE
Removes the provider.
For example, to remove the OpenStack network provider with identifier 1234, send a request like this:
DELETE /ovirt-engine/api/openstacknetworkproviders/1234
DELETE /ovirt-engine/api/openstacknetworkproviders/1234| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.135.4. testconnectivity POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.135.5. update PUT
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/1234With a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The provider to update. |
6.136. OpenstackNetworkProviders
This service manages OpenStack network providers.
| Name | Summary |
|---|---|
|
| The operation adds a new network provider to the system. |
|
|
6.136.1. add POST
The operation adds a new network provider to the system. If the type property is not present, a default value of NEUTRON will be used.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.136.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
6.136.2.1. max
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.137. OpenstackNetworks
| Name | Summary |
|---|---|
|
|
6.137.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.137.1.1. max
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.138. OpenstackSubnet
| Name | Summary |
|---|---|
|
| |
|
|
6.138.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.138.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.139. OpenstackSubnets
| Name | Summary |
|---|---|
|
| |
|
|
6.139.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.139.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of sub-networks to return. | |
|
| Out |
6.139.2.1. max
Sets the maximum number of sub-networks to return. If not specified all the sub-networks are returned.
6.140. OpenstackVolumeAuthenticationKey
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.140.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.140.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.140.3. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.141. OpenstackVolumeAuthenticationKeys
| Name | Summary |
|---|---|
|
| |
|
|
6.141.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.141.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of keys to return. |
6.141.2.1. max
Sets the maximum number of keys to return. If not specified all the keys are returned.
6.142. OpenstackVolumeProvider
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
6.142.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.142.2. importcertificates POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In |
6.142.3. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.142.4. testconnectivity POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the test should be performed asynchronously. |
6.142.5. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.143. OpenstackVolumeProviders
| Name | Summary |
|---|---|
|
| Adds a new volume provider. |
|
| Retrieves the list of volume providers. |
6.143.1. add POST
Adds a new volume provider.
For example:
POST /ovirt-engine/api/openstackvolumeproviders
POST /ovirt-engine/api/openstackvolumeprovidersWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.143.2. list GET
Retrieves the list of volume providers.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of providers to return. | |
|
| Out |
6.143.2.1. max
Sets the maximum number of providers to return. If not specified all the providers are returned.
6.144. OpenstackVolumeType
| Name | Summary |
|---|---|
|
|
6.144.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.145. OpenstackVolumeTypes
| Name | Summary |
|---|---|
|
|
6.145.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of volume types to return. | |
|
| Out |
6.145.1.1. max
Sets the maximum number of volume types to return. If not specified all the volume types are returned.
6.146. OperatingSystem
| Name | Summary |
|---|---|
|
|
6.146.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.147. OperatingSystems
| Name | Summary |
|---|---|
|
|
6.147.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.147.1.1. max
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.148. Permission
| Name | Summary |
|---|---|
|
| |
|
|
6.148.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.148.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.149. Permit
A service to manage a specific permit of the role.
| Name | Summary |
|---|---|
|
| Gets the information about the permit of the role. |
|
| Removes the permit from the role. |
6.149.1. get GET
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. |
6.149.2. remove DELETE
Removes the permit from the role.
For example to remove the permit with id 456 from the role with id 123 send a request like this:
DELETE /ovirt-engine/api/roles/123/permits/456
DELETE /ovirt-engine/api/roles/123/permits/456| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.150. Permits
Represents a permits sub-collection of the specific role.
| Name | Summary |
|---|---|
|
| Adds a permit to the role. |
|
| List the permits of the role. |
6.150.1. add POST
Adds a permit to the role. The permit name can be retrieved from the Section 6.31, “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/permitsWith a request body like this:
<permit> <name>create_vm</name> </permit>
<permit>
<name>create_vm</name>
</permit>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The permit to add. |
6.150.2. list GET
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. |
6.150.2.1. max
Sets the maximum number of permits to return. If not specified all the permits are returned.
6.151. Qos
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.151.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.151.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.151.3. update PUT
6.152. Qoss
| Name | Summary |
|---|---|
|
| |
|
|
6.152.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.152.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of QoS descriptors to return. | |
|
| Out |
6.152.2.1. max
Sets the maximum number of QoS descriptors to return. If not specified all the descriptors are returned.
6.153. Quota
| Name | Summary |
|---|---|
|
| Retrieves a quota. |
|
| Delete a quota. |
|
| Updates a quota. |
6.153.1. get GET
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 |
6.153.2. remove DELETE
Delete a quota.
An example of deleting a quota:
DELETE /ovirt-engine/api/datacenters/123-456/quotas/654-321 -0472718ab224 HTTP/1.1 Accept: application/xml Content-type: application/xml
DELETE /ovirt-engine/api/datacenters/123-456/quotas/654-321
-0472718ab224 HTTP/1.1
Accept: application/xml
Content-type: application/xml| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.153.3. update PUT
Updates a quota.
An example of updating a quota:
PUT /ovirt-engine/api/datacenters/123/quotas/456
PUT /ovirt-engine/api/datacenters/123/quotas/4566.154. QuotaClusterLimit
| Name | Summary |
|---|---|
|
| |
|
|
6.154.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.154.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.155. QuotaClusterLimits
| Name | Summary |
|---|---|
|
| |
|
|
6.155.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.155.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of limits to return. |
6.155.2.1. max
Sets the maximum number of limits to return. If not specified all the limits are returned.
6.156. QuotaStorageLimit
| Name | Summary |
|---|---|
|
| |
|
|
6.156.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.156.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. |
6.157. QuotaStorageLimits
| Name | Summary |
|---|---|
|
| |
|
|
6.157.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.157.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of limits to return. |
6.157.2.1. max
Sets the maximum number of limits to return. If not specified all the limits are returned.
6.158. Quotas
| Name | Summary |
|---|---|
|
| Creates a new quota. |
|
| Lists quotas of a data center |
6.158.1. add POST
Creates a new quota.
An example of creating a new quota:
POST /ovirt-engine/api/datacenters/123/quotas
POST /ovirt-engine/api/datacenters/123/quotas<quota> <name>myquota</name> <description>My new quota for virtual machines</description> </quota>
<quota>
<name>myquota</name>
<description>My new quota for virtual machines</description>
</quota>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.158.2. list GET
Lists quotas of a data center
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of quota descriptors to return. | |
|
| Out |
6.158.2.1. max
Sets the maximum number of quota descriptors to return. If not specified all the descriptors are returned.
6.159. Role
| Name | Summary |
|---|---|
|
| Get the role. |
|
| Removes the role. |
|
| Updates a role. |
6.159.1. get GET
Get the role.
GET /ovirt-engine/api/roles/123
GET /ovirt-engine/api/roles/123You will receive XML response like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieved role. |
6.159.2. remove DELETE
Removes the role.
To remove the role you need to know its id, then send request like this:
DELETE /ovirt-engine/api/roles/{role_id}
DELETE /ovirt-engine/api/roles/{role_id}| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.159.3. update PUT
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/123With a request body like this:
<role> <name>MyNewRoleName</name> <description>My new description of the role</description> <administrative>true</administrative> </group>
<role>
<name>MyNewRoleName</name>
<description>My new description of the role</description>
<administrative>true</administrative>
</group>6.160. Roles
Provides read-only access to the global set of roles
| Name | Summary |
|---|---|
|
| Create a new role. |
|
| List roles. |
6.160.1. add POST
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/rolesWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Role that will be added. |
6.160.2. list GET
List roles.
GET /ovirt-engine/api/roles
GET /ovirt-engine/api/rolesYou 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. |
6.160.2.1. max
Sets the maximum number of roles to return. If not specified all the roles are returned.
6.161. SchedulingPolicies
| Name | Summary |
|---|---|
|
| |
|
|
6.161.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.161.2. list GET
| 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 |
6.161.2.1. max
Sets the maximum number of policies to return. If not specified all the policies are returned.
6.162. SchedulingPolicy
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.162.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| Out |
6.162.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.162.3. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.163. SchedulingPolicyUnit
| Name | Summary |
|---|---|
|
| |
|
|
6.163.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| Out |
6.163.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.164. SchedulingPolicyUnits
| Name | Summary |
|---|---|
|
|
6.164.1. list GET
| 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 |
6.164.1.1. max
Sets the maximum number of policy units to return. If not specified all the policy units are returned.
6.165. Snapshot
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Restores a virtual machine snapshot. |
6.165.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.165.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.165.3. restore POST
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/>6.166. SnapshotCdrom
| Name | Summary |
|---|---|
|
|
6.166.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.167. SnapshotCdroms
| Name | Summary |
|---|---|
|
|
6.167.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of CDROMS to return. |
6.167.1.1. max
Sets the maximum number of CDROMS to return. If not specified all the CDROMS are returned.
6.168. SnapshotDisk
| Name | Summary |
|---|---|
|
|
6.168.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.169. SnapshotDisks
| Name | Summary |
|---|---|
|
|
6.169.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of disks to return. |
6.169.1.1. max
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.170. SnapshotNic
| Name | Summary |
|---|---|
|
|
6.170.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.171. SnapshotNics
| Name | Summary |
|---|---|
|
|
6.171.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
6.171.1.1. max
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.172. Snapshots
| Name | Summary |
|---|---|
|
| Creates a virtual machine snapshot. |
|
|
6.172.1. add POST
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/snapshotsWith a request body like this:
<snapshot> <description>My snapshot</description> </snapshot>
<snapshot>
<description>My snapshot</description>
</snapshot>
When a snapshot is created the default value for the persist_memorystate attribute is true. That means that the content of the memory of the virtual machine will be included in the snapshot, and it also means that the virtual machine will be paused for a longer time. That can negatively affect applications that are very sensitive to timing (NTP servers, for example). In those cases make sure that you set the attribute to false:
<snapshot> <description>My snapshot</description> <persist_memorystate>false</persist_memorystate> </snapshot>
<snapshot>
<description>My snapshot</description>
<persist_memorystate>false</persist_memorystate>
</snapshot>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.172.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of snapshots to return. | |
|
| Out |
6.172.2.1. max
Sets the maximum number of snapshots to return. If not specified all the snapshots are returned.
6.173. SshPublicKey
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.173.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.173.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.173.3. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.174. SshPublicKeys
| Name | Summary |
|---|---|
|
| |
|
|
6.174.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.174.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of keys to return. |
6.174.2.1. max
Sets the maximum number of keys to return. If not specified all the keys are returned.
6.175. Statistic
| Name | Summary |
|---|---|
|
|
6.175.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.176. Statistics
| Name | Summary |
|---|---|
|
| Retrieves a list of statistics. |
6.176.1. list GET
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/statisticsThe 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/456Outputs:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of statistics to return. | |
|
| Out |
6.176.1.1. max
Sets the maximum number of statistics to return. If not specified all the statistics are returned.
6.177. Step
A service to manage a step.
| Name | Summary |
|---|---|
|
| Marks an external step execution as ended. |
|
| Retrieves a step. |
6.177.1. end POST
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/endWith the following request body:
<action> <force>true</force> <succeeded>true</succeeded> </action>
<action>
<force>true</force>
<succeeded>true</succeeded>
</action>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. | |
|
| In | Indicates if the step should be forcibly terminated. | |
|
| In | Indicates if the step should be marked as successfully finished or as failed. |
6.177.1.1. succeeded
Indicates if the step should be marked as successfully finished or as failed.
This parameter is optional, and the default value is true.
6.177.2. get GET
Retrieves a step.
GET /ovirt-engine/api/jobs/123/steps/456
GET /ovirt-engine/api/jobs/123/steps/456You will receive response in XML like this one:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | Retrieves the representation of the step. |
6.178. Steps
A service to manage steps.
| Name | Summary |
|---|---|
|
| Add an external step to an existing job or to an existing step. |
|
| Retrieves the representation of the steps. |
6.178.1. add POST
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/stepsWith the following request body:
The response should look like:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | Step that will be added. |
6.178.2. list GET
Retrieves the representation of the steps.
GET /ovirt-engine/api/job/123/steps
GET /ovirt-engine/api/job/123/stepsYou 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. |
6.178.2.1. max
Sets the maximum number of steps to return. If not specified all the steps are returned.
6.179. Storage
| Name | Summary |
|---|---|
|
|
6.179.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the status of the LUNs in the storage should be checked. | |
|
| Out |
6.179.1.1. report_status
Indicates if the status of the LUNs in the storage should be checked. Checking the status of the LUN is an heavy weight operation and this data is not always needed by the user. This parameter will give the option to not perform the status check of the LUNs.
The default is true for backward compatibility.
Here an example with the LUN status :
Here an example without the LUN status :
6.180. StorageDomain
| Name | Summary |
|---|---|
|
| |
|
| |
|
| This operation reduces logical units from the storage domain. |
|
| This operation refreshes the LUN size. |
|
| Removes the storage domain. |
|
| Updates a storage domain. |
|
|
This operation forces the update of the |
6.180.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| Out |
6.180.2. isattached POST
6.180.3. reduceluns POST
This operation reduces logical units from the storage domain.
In order to do so the data stored on the provided logical units will be moved to other logical units of the storage domain and only then they will be reduced from the storage domain.
For example, in order to reduce two logical units from a storage domain send a request like this:
POST /ovirt-engine/api/storagedomains/123/reduceluns
POST /ovirt-engine/api/storagedomains/123/reducelunsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | The logical units that needs to be reduced from the storage domain. |
6.180.4. refreshluns POST
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/refreshlunsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the refresh should be performed asynchronously. | |
|
| In | The LUNs that need to be refreshed. |
6.180.5. remove DELETE
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. |
6.180.5.1. destroy
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.
6.180.5.2. host
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=myhost6.180.6. update PUT
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/123With 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 |
6.180.7. updateovfstore POST
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 |
6.181. StorageDomainContentDisk
| Name | Summary |
|---|---|
|
|
6.181.1. get GET
6.182. StorageDomainContentDisks
| Name | Summary |
|---|---|
|
|
6.182.1. list GET
| 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. |
6.182.1.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.182.1.2. max
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.183. StorageDomainServerConnection
| Name | Summary |
|---|---|
|
| |
|
| Detaches a storage connection from storage. |
6.183.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.183.2. remove DELETE
Detaches a storage connection from storage.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.184. StorageDomainServerConnections
| Name | Summary |
|---|---|
|
| |
|
|
6.184.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.184.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of connections to return. |
6.184.2.1. max
Sets the maximum number of connections to return. If not specified all the connections are returned.
6.185. StorageDomainTemplate
| Name | Summary |
|---|---|
|
| |
|
| Action to import a template from an export storage domain. |
|
| |
|
|
6.185.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.185.2. import POST
Action to import a template from an export storage domain.
For example, to import the template 456 from the storage domain 123 send the following request:
POST /ovirt-engine/api/storagedomains/123/templates/456/import
POST /ovirt-engine/api/storagedomains/123/templates/456/importWith the following request body:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the import should be performed asynchronously. | |
|
| In |
Use the optional | |
|
| In | ||
|
| In | ||
|
| In | ||
|
| In | ||
|
| In |
6.185.2.1. clone
Use the optional clone parameter to generate new UUIDs for the imported template and its entities.
The user might want to import a template with the clone parameter set to false when importing a template from an export domain, with templates that was exported by a different Red Hat Virtualization environment.
6.185.3. register POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates whether a template is allowed to be registered with only some of its disks. | |
|
| In | Indicates if the registration should be performed asynchronously. | |
|
| In | ||
|
| In | ||
|
| In | ||
|
| In |
6.185.3.1. allow_partial_import
Indicates whether a template is allowed to be registered with only some of its disks.
If this flag is true, the engine will not fail in the validation process if an image is not found, but instead it will allow the template to be registered without the missing disks. This is mainly used during registration of a template when some of the storage domains are not available. The default value is false.
6.185.4. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.186. StorageDomainTemplates
| Name | Summary |
|---|---|
|
|
6.186.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of templates to return. | |
|
| Out | ||
|
| In | Indicates whether to retrieve a list of registered or unregistered templates which contain disks on the storage domain. |
6.186.1.1. max
Sets the maximum number of templates to return. If not specified all the templates are returned.
6.186.1.2. unregistered
Indicates whether to retrieve a list of registered or unregistered templates which contain disks on the storage domain. To get a list of unregistered templates the call should indicate the unregistered flag. For example, to get a list of unregistered templates the REST API call should look like this:
GET /ovirt-engine/api/storagedomains/123/templates?unregistered=true
GET /ovirt-engine/api/storagedomains/123/templates?unregistered=true
The default value of the unregisterd flag is false. The request only apply to storage domains that are attached.
6.187. StorageDomainVm
| Name | Summary |
|---|---|
|
| |
|
| Imports a virtual machine from an export storage domain. |
|
| |
|
| Deletes a virtual machine from an export storage domain. |
6.187.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.187.2. import POST
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/importWith 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 |
6.187.2.1. clone
Indicates if the identifiers of the imported virtual machine should be regenerated.
By default when a virtual machine is imported the identifiers are preserved. This means that the same virtual machine can’t be imported multiple times, as that identifiers needs to be unique. To allow importing the same machine multiple times set this parameter to true, as the default is false.
6.187.2.2. collapse_snapshots
Indicates of the snapshots of the virtual machine that is imported should be collapsed, so that the result will be a virtual machine without snapshots.
This parameter is optional, and if it isn’t explicitly specified the default value is false.
6.187.3. register POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates whether a virtual machine is allowed to be registered with only some of its disks. | |
|
| In | Indicates if the registration should be performed asynchronously. | |
|
| In | ||
|
| In | ||
|
| In | Indicates if the problematic MAC addresses should be re-assigned during the import process by the engine. | |
|
| In | ||
|
| In | Mapping rules for virtual NIC profiles that will be applied during the import process. |
6.187.3.1. allow_partial_import
Indicates whether a virtual machine is allowed to be registered with only some of its disks.
If this flag is true, the engine will not fail in the validation process if an image is not found, but instead it will allow the virtual machine to be registered without the missing disks. This is mainly used during registration of a virtual machine when some of the storage domains are not available. The default value is false.
6.187.3.2. reassign_bad_macs
Indicates if the problematic MAC addresses should be re-assigned during the import process by the engine.
A MAC address would be considered as a problematic one if one of the following is true:
- It conflicts with a MAC address that is already allocated to a virtual machine in the target environment.
- It’s out of the range of the target MAC address pool.
6.187.4. remove DELETE
Deletes a virtual machine from an export storage domain.
For example, to delete the virtual machine 456 from the storage domain 123, send a request like this:
DELETE /ovirt-engine/api/storagedomains/123/vms/456
DELETE /ovirt-engine/api/storagedomains/123/vms/456| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.188. StorageDomainVmDiskAttachment
Returns the details of the disks attached to a virtual machine in the export domain.
| Name | Summary |
|---|---|
|
| Returns the details of the attachment with all its properties and a link to the disk. |
6.188.1. get GET
Returns the details of the attachment with all its properties and a link to the disk.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The disk attachment. |
6.189. StorageDomainVmDiskAttachments
Returns the details of a disk attached to a virtual machine in the export domain.
| Name | Summary |
|---|---|
|
| List the disks that are attached to the virtual machine. |
6.189.1. list GET
List the disks that are attached to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.190. StorageDomainVms
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/vmsThis 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 |
|---|---|
|
|
6.190.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of virtual machines to return. | |
|
| In | Indicates whether to retrieve a list of registered or unregistered virtual machines which contain disks on the storage domain. | |
|
| Out |
6.190.1.1. max
Sets the maximum number of virtual machines to return. If not specified all the virtual machines are returned.
6.190.1.2. unregistered
Indicates whether to retrieve a list of registered or unregistered virtual machines which contain disks on the storage domain. To get a list of unregistered virtual machines the call should indicate the unregistered flag. For example, to get a list of unregistered virtual machines the REST API call should look like this:
GET /ovirt-engine/api/storagedomains/123/vms?unregistered=true
GET /ovirt-engine/api/storagedomains/123/vms?unregistered=true
The default value of the unregisterd flag is false. The request only apply to storage domains that are attached.
6.191. StorageDomains
| Name | Summary |
|---|---|
|
| Adds a new storage domain. |
|
|
6.191.1. add POST
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/storagedomainsWith 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 |
6.191.2. list GET
| 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 |
6.191.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.191.2.2. max
Sets the maximum number of storage domains to return. If not specified all the storage domains are returned.
6.192. StorageServerConnection
| Name | Summary |
|---|---|
|
| |
|
| Removes a storage connection. |
|
| Updates the storage connection. |
6.192.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.192.2. remove DELETE
Removes a storage connection.
A storage connection can only be deleted if neither storage domain nor LUN disks reference it. The host name or id is optional; providing it disconnects (unmounts) the connection from that host.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | The name or identifier of the host from which the connection would be unmounted (disconnected). |
6.192.2.1. host
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=4566.192.3. update PUT
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/123With 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. |
6.192.3.1. force
Indicates if the operation should succeed regardless to the relevant storage domain’s status (i.e. updating is also applicable when storage domain’s status is not maintenance).
This parameter is optional, and the default value is false.
6.193. StorageServerConnectionExtension
| Name | Summary |
|---|---|
|
| |
|
| |
|
| Update a storage server connection extension for the given host. |
6.193.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.193.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.193.3. update PUT
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/456With a request body like this:
<storage_connection_extension> <target>iqn.2016-01.com.example:mytarget</target> <username>myuser</username> <password>mypassword</password> </storage_connection_extension>
<storage_connection_extension>
<target>iqn.2016-01.com.example:mytarget</target>
<username>myuser</username>
<password>mypassword</password>
</storage_connection_extension>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.194. StorageServerConnectionExtensions
| Name | Summary |
|---|---|
|
| Creates a new storage server connection extension for the given host. |
|
|
6.194.1. add POST
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/storageconnectionextensionsWith a request body like this:
<storage_connection_extension> <target>iqn.2016-01.com.example:mytarget</target> <username>myuser</username> <password>mypassword</password> </storage_connection_extension>
<storage_connection_extension>
<target>iqn.2016-01.com.example:mytarget</target>
<username>myuser</username>
<password>mypassword</password>
</storage_connection_extension>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.194.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of extensions to return. |
6.194.2.1. max
Sets the maximum number of extensions to return. If not specified all the extensions are returned.
6.195. StorageServerConnections
| Name | Summary |
|---|---|
|
| Creates a new storage connection. |
|
|
6.195.1. add POST
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/storageconnectionsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.195.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of connections to return. |
6.195.2.1. max
Sets the maximum number of connections to return. If not specified all the connections are returned.
6.196. System
| Name | Summary |
|---|---|
|
| Returns basic information describing the API, like the product name, the version number and a summary of the number of relevant objects. |
|
|
6.196.1. get GET
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/apiWe 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 |
6.196.2. reloadconfigurations POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reload should be performed asynchronously. |
6.197. SystemPermissions
This service doesn’t add any new methods, it is just a placeholder for the annotation that specifies the path of the resource that manages the permissions assigned to the system object.
| Name | Summary |
|---|---|
|
| Assign a new permission to a user or group for specific entity. |
|
| List all the permissions of the specific entity. |
6.197.1. add POST
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/permissionsWith 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/permissionsWith 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/permissionsWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The permission. |
6.197.2. list GET
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. |
6.198. Tag
A service to manage a specific tag in the system.
| Name | Summary |
|---|---|
|
| Gets the information about the tag. |
|
| Removes the tag from the system. |
|
| Updates the tag entity. |
6.198.1. get GET
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. |
6.198.2. remove DELETE
Removes the tag from the system.
For example to remove the tag with id 123 send a request like this:
DELETE /ovirt-engine/api/tags/123
DELETE /ovirt-engine/api/tags/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.198.3. update PUT
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/123With request body like:
<tag> <parent id="456"/> </tag>
<tag>
<parent id="456"/>
</tag>
You may also specify a tag name instead of id. For example to update parent tag to tag with name mytag of the tag with id 123 send a request like this:
<tag>
<parent>
<name>mytag</name>
</parent>
</tag>
<tag>
<parent>
<name>mytag</name>
</parent>
</tag>6.199. Tags
Represents a service to manage collection of the tags in the system.
| Name | Summary |
|---|---|
|
| Add a new tag to the system. |
|
| List the tags in the system. |
6.199.1. add POST
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/tagsWith a request body like this:
<tag> <name>mytag</name> </tag>
<tag>
<name>mytag</name>
</tag>The root tag is a special pseudo-tag assumed as the default parent tag if no parent tag is specified. The root tag cannot be deleted nor assigned a parent tag.
To create new tag with specific parent tag send a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The added tag. |
6.199.2. list GET
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/tagsIn 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. |
6.199.2.1. max
Sets the maximum number of tags to return. If not specified all the tags are returned.
6.200. Template
Manages the virtual machine template and template versions.
| Name | Summary |
|---|---|
|
| Exports a template to the data center export domain. |
|
| Returns the information about this template or template version. |
|
| Removes a virtual machine template. |
|
| Updates the template. |
6.200.1. export POST
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/exportWith 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. |
6.200.1.1. exclusive
Indicates if the existing templates with the same name should be overwritten.
The export action reports a failed action if a template of the same name exists in the destination domain. Set this parameter to true to change this behavior and overwrite any existing template.
6.200.2. get GET
Returns the information about this template or template version.
6.200.3. remove DELETE
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. |
6.200.4. update PUT
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/123With the following request body:
<template> <memory>1073741824</memory> </template>
<template>
<memory>1073741824</memory>
</template>
The version_name name attribute is the only one that can be updated within the version attribute used for template versions:
<template>
<version>
<version_name>mytemplate_2</version_name>
</version>
</template>
<template>
<version>
<version_name>mytemplate_2</version_name>
</version>
</template>6.201. TemplateCdrom
A service managing a CD-ROM device on templates.
| Name | Summary |
|---|---|
|
| Returns the information about this CD-ROM device. |
6.201.1. get GET
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. |
6.201.1.1. cdrom
The information about the CD-ROM device.
The information consists of cdrom attribute containing reference to the CD-ROM device, the template, and optionally the inserted disk.
If there is a disk inserted then the file attribute will contain a reference to the ISO image:
<cdrom href="..." id="00000000-0000-0000-0000-000000000000"> <template href="/ovirt-engine/api/templates/123" id="123"/> <file id="mycd.iso"/> </cdrom>
<cdrom href="..." id="00000000-0000-0000-0000-000000000000">
<template href="/ovirt-engine/api/templates/123" id="123"/>
<file id="mycd.iso"/>
</cdrom>
If there is no disk inserted then the file attribute won’t be reported:
<cdrom href="..." id="00000000-0000-0000-0000-000000000000"> <template href="/ovirt-engine/api/templates/123" id="123"/> </cdrom>
<cdrom href="..." id="00000000-0000-0000-0000-000000000000">
<template href="/ovirt-engine/api/templates/123" id="123"/>
</cdrom>6.202. TemplateCdroms
Lists the CD-ROM devices of a template.
| Name | Summary |
|---|---|
|
|
6.202.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of CD-ROM devices of the template. | |
|
| In | Sets the maximum number of CD-ROMs to return. |
6.202.1.1. max
Sets the maximum number of CD-ROMs to return. If not specified all the CD-ROMs are returned.
6.203. TemplateDisk
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
|
6.203.1. copy POST
6.203.2. export POST
6.203.3. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.203.4. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.204. TemplateDiskAttachment
This service manages the attachment of a disk to a template.
| Name | Summary |
|---|---|
|
| Returns the details of the attachment. |
|
| Removes the disk from the template. |
6.204.1. get GET
Returns the details of the attachment.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.204.2. remove DELETE
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-a5ca22dd1d746.205. TemplateDiskAttachments
This service manages the set of disks attached to a template. Each attached disk is represented by a DiskAttachment.
| Name | Summary |
|---|---|
|
| List the disks that are attached to the template. |
6.205.1. list GET
List the disks that are attached to the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.206. TemplateDisks
| Name | Summary |
|---|---|
|
|
6.206.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of disks to return. |
6.206.1.1. max
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.207. TemplateGraphicsConsole
| Name | Summary |
|---|---|
|
| Gets graphics console configuration of the template. |
|
| Remove the graphics console from the template. |
6.207.1. get GET
Gets graphics console configuration of the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the graphics console of the template. |
6.207.2. remove DELETE
Remove the graphics console from the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.208. TemplateGraphicsConsoles
| Name | Summary |
|---|---|
|
| Add new graphics console to the template. |
|
| Lists all the configured graphics consoles of the template. |
6.208.1. add POST
Add new graphics console to the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.208.2. list GET
Lists all the configured graphics consoles of the template.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of graphics consoles of the template. | |
|
| In | Sets the maximum number of consoles to return. |
6.208.2.1. max
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
6.209. TemplateNic
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.209.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.209.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.209.3. update PUT
6.210. TemplateNics
| Name | Summary |
|---|---|
|
| |
|
|
6.210.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.210.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
6.210.2.1. max
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.211. TemplateWatchdog
| Name | Summary |
|---|---|
|
| |
|
| |
|
|
6.211.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.211.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.211.3. update PUT
6.212. TemplateWatchdogs
| Name | Summary |
|---|---|
|
| |
|
|
6.212.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.212.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of watchdogs to return. | |
|
| Out |
6.212.2.1. max
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
6.213. Templates
This service manages the virtual machine templates available in the system.
| Name | Summary |
|---|---|
|
| Creates a new template. |
|
| Returns the list of virtual machine templates. |
6.213.1. add POST
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/templatesWith 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 | Seal the template. | |
|
| In/Out | The information about the template or template version. |
6.213.1.1. clone_permissions
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=trueWith a request body like this:
6.213.1.2. seal
Seal the template.
If this optional parameter is provided and its value is true, then the template is sealed after creation.
Sealing erases all host-specific configuration from the filesystem: SSH keys, UDEV rules, MAC addresses, system ID, hostname etc., thus making easy to use the template to create multiple virtual machines without manual intervention.
Currently sealing is supported only for Linux OS.
6.213.2. list GET
Returns the list of virtual machine templates.
For example:
GET /ovirt-engine/api/templates
GET /ovirt-engine/api/templatesWill 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. |
6.213.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.213.2.2. max
Sets the maximum number of templates to return. If not specified all the templates are returned.
6.214. UnmanagedNetwork
| Name | Summary |
|---|---|
|
| |
|
|
6.214.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.214.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.215. UnmanagedNetworks
| Name | Summary |
|---|---|
|
|
6.215.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.215.1.1. max
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.216. User
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 6.217, “Users”.
| Name | Summary |
|---|---|
|
| Gets the system user information. |
|
| Removes the system user. |
6.216.1. get GET
Gets the system user information.
Usage:
GET /ovirt-engine/api/users/1234
GET /ovirt-engine/api/users/1234Will return the user information:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The system user. |
6.216.2. remove DELETE
Removes the system user.
Usage:
DELETE /ovirt-engine/api/users/1234
DELETE /ovirt-engine/api/users/1234| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.217. Users
A service to manage the users in the system.
| Name | Summary |
|---|---|
|
| Add user from a directory service. |
|
| List all the users in the system. |
6.217.1. add POST
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/usersWith a request body like this:
In case you are working with Active Directory you have to pass user principal name (UPN) as username, followed by authorization provider name. Due to bug 1147900 you need to provide also principal parameter set to UPN of the user.
For example, to add the user with UPN myuser@mysubdomain.mydomain.com from the myextension-authz authorization provider send a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.217.2. list GET
List all the users in the system.
Usage:
GET /ovirt-engine/api/users
GET /ovirt-engine/api/usersWill 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. |
6.217.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.217.2.2. max
Sets the maximum number of users to return. If not specified all the users are returned.
6.218. VirtualFunctionAllowedNetwork
| Name | Summary |
|---|---|
|
| |
|
|
6.218.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.218.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.219. VirtualFunctionAllowedNetworks
| Name | Summary |
|---|---|
|
| |
|
|
6.219.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.219.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of networks to return. | |
|
| Out |
6.219.2.1. max
Sets the maximum number of networks to return. If not specified all the networks are returned.
6.220. Vm
| Name | Summary |
|---|---|
|
| This operation stops any migration of a virtual machine to another physical host. |
|
| |
|
| Permanently restores the virtual machine to the state of the previewed snapshot. |
|
| Detaches a virtual machine from a pool. |
|
| Exports a virtual machine to an export domain. |
|
| Freezes virtual machine file systems. |
|
| Retrieves the description of the virtual machine. |
|
| Initiates the automatic user logon to access a virtual machine from an external console. |
|
| Sets the global maintenance mode on the hosted engine virtual machine. |
|
| Migrates a virtual machine to another physical host. |
|
| Temporarily restores the virtual machine to the state of a snapshot. |
|
| Sends a reboot request to a virtual machine. |
|
| Removes the virtual machine, including the virtual disks attached to it. |
|
| |
|
| This operation sends a shutdown request to a virtual machine. |
|
| Starts the virtual machine. |
|
| This operation forces a virtual machine to power-off. |
|
| This operation saves the virtual machine state to disk and stops it. |
|
| Thaws virtual machine file systems. |
|
| Generates a time-sensitive authentication token for accessing a virtual machine’s display. |
|
| Restores the virtual machine to the state it had before previewing the snapshot. |
|
|
6.220.1. cancelmigration POST
This operation stops any migration of a virtual machine to another physical host.
POST /ovirt-engine/api/vms/123/cancelmigration
POST /ovirt-engine/api/vms/123/cancelmigration
The cancel migration action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should cancelled asynchronously. |
6.220.2. clone POST
6.220.3. commitsnapshot POST
Permanently restores the virtual machine to the state of the previewed snapshot.
See the preview_snapshot operation for details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the snapshots should be committed asynchronously. |
6.220.4. detach POST
Detaches a virtual machine from a pool.
POST /ovirt-engine/api/vms/123/detach
POST /ovirt-engine/api/vms/123/detach
The detach action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the detach action should be performed asynchronously. |
6.220.5. export POST
Exports a virtual machine to an export domain.
For example, to export virtual machine 123 to the export domain myexport:
POST /ovirt-engine/api/vms/123/export
POST /ovirt-engine/api/vms/123/exportWith a request body like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the export should be performed asynchronously. | |
|
| In |
Use the | |
|
| In |
Use the | |
|
| In |
6.220.6. freezefilesystems POST
Freezes virtual machine file systems.
This operation freezes a virtual machine’s file systems using the QEMU guest agent when taking a live snapshot of a running virtual machine. Normally, this is done automatically by the manager, but this must be executed manually with the API for virtual machines using OpenStack Volume (Cinder) disks.
Example:
POST /ovirt-engine/api/vms/123/freezefilesystems
POST /ovirt-engine/api/vms/123/freezefilesystems<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the freeze should be performed asynchronously. |
6.220.7. get GET
Retrieves the description of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if all of the attributes of the virtual machine should be included in the response. | |
|
| In | Indicates if the results should be filtered according to the permissions of the user. | |
|
| In | Indicates if the returned result describes the virtual machine as it is currently running or if describes the virtual machine with the modifications that have already been performed but that will only come into effect when the virtual machine is restarted. | |
|
| Out | Description of the virtual machine. |
6.220.7.1. all_content
Indicates if all of the attributes of the virtual machine should be included in the response.
By default the following attributes are excluded:
-
console -
initialization.configuration.data- The OVF document describing the virtual machine. -
rng_source -
soundcard -
virtio_scsi
For example, to retrieve the complete representation of the virtual machine '123':
GET /ovirt-engine/api/vms/123?all_content=true
GET /ovirt-engine/api/vms/123?all_content=trueThese attributes are not included by default as they reduce performance. These attributes are seldom used and require additional queries to the database. Only use this parameter when required as it will reduce performance.
6.220.7.2. next_run
Indicates if the returned result describes the virtual machine as it is currently running or if describes the virtual machine with the modifications that have already been performed but that will only come into effect when the virtual machine is restarted. By default the value is false.
If the parameter is included in the request, but without a value, it is assumed that the value is true. The the following request:
GET /vms/{vm:id};next_run
GET /vms/{vm:id};next_run
Is equivalent to using the value true:
GET /vms/{vm:id};next_run=true
GET /vms/{vm:id};next_run=true6.220.8. logon POST
Initiates the automatic user logon to access a virtual machine from an external console.
This action requires the ovirt-guest-agent-gdm-plugin and the ovirt-guest-agent-pam-module packages to be installed and the ovirt-guest-agent service to be running on the virtual machine.
Users require the appropriate user permissions for the virtual machine in order to access the virtual machine from an external console.
For example:
POST /ovirt-engine/api/vms/123/logon
POST /ovirt-engine/api/vms/123/logonRequest body:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the logon should be performed asynchronously. |
6.220.9. maintenance POST
Sets the global maintenance mode on the hosted engine virtual machine.
This action has no effect on other virtual machines.
Example:
POST /ovirt-engine/api/vms/123/maintenance
POST /ovirt-engine/api/vms/123/maintenance<action> <maintenance_enabled>true<maintenance_enabled/> </action>
<action>
<maintenance_enabled>true<maintenance_enabled/>
</action>6.220.10. migrate POST
Migrates a virtual machine to another physical host.
Example:
POST /ovirt-engine/api/vms/123/migrate
POST /ovirt-engine/api/vms/123/migrateTo specify a specific host to migrate the virtual machine to:
<action> <host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"/> </action>
<action>
<host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"/>
</action>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the migration should be performed asynchronously. | |
|
| In | Specifies the cluster the virtual machine should migrate to. | |
|
| In | Specifies that the virtual machine should migrate even if the virtual machine is defined as non-migratable. | |
|
| In | Specifies a specific host that the virtual machine should migrate to. |
6.220.10.1. cluster
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.
6.220.10.2. force
Specifies that the virtual machine should migrate even if the virtual machine is defined as non-migratable. This is an optional parameter. By default, it is set to false.
6.220.10.3. host
Specifies a specific host that the virtual machine should migrate to. This is an optional parameter. By default, the Red Hat Virtualization Manager automatically selects a default host for migration within the same cluster. If an API user requires a specific host, the user can specify the host with either an id or name parameter.
6.220.11. previewsnapshot POST
Temporarily restores the virtual machine to the state of a snapshot.
The snapshot is indicated with the snapshot.id parameter. It is restored temporarily, so that the content can be inspected. Once that inspection is finished, the state of the virtual machine can be made permanent, using the commit_snapshot method, or discarded using the undo_snapshot method.
6.220.12. reboot POST
Sends a reboot request to a virtual machine.
For example:
POST /ovirt-engine/api/vms/123/reboot
POST /ovirt-engine/api/vms/123/reboot
The reboot action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the reboot should be performed asynchronously. |
6.220.13. remove DELETE
Removes the virtual machine, including the virtual disks attached to it.
For example, to remove the virtual machine with identifier 123:
DELETE /ovirt-engine/api/vms/123
DELETE /ovirt-engine/api/vms/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. | |
|
| In | Indicates if the attached virtual disks should be detached first and preserved instead of being removed. | |
|
| In | Indicates if the virtual machine should be forcibly removed. |
6.220.13.1. force
Indicates if the virtual machine should be forcibly removed.
Locked virtual machines and virtual machines with locked disk images cannot be removed without this flag set to true.
6.220.14. reordermacaddresses POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the action should be performed asynchronously. |
6.220.15. shutdown POST
This operation sends a shutdown request to a virtual machine.
For example:
POST /ovirt-engine/api/vms/123/shutdown
POST /ovirt-engine/api/vms/123/shutdown
The shutdown action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the shutdown should be performed asynchronously. |
6.220.16. start POST
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/startWith a request body:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the start 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. |
6.220.16.1. pause
If set to true, start the virtual machine in paused mode. The default is false.
6.220.16.2. use_cloud_init
If set to true, the initialization type is set to cloud-init. The default value is false. See this for details.
6.220.16.3. use_sysprep
If set to true, the initialization type is set to Sysprep. The default value is false. See this for details.
6.220.16.4. vm
The definition of the virtual machine for this specific run.
For example:
This will set the boot device to the CDROM only for this specific start. After the virtual machine is powered off, this definition will be reverted.
6.220.17. stop POST
This operation forces a virtual machine to power-off.
For example:
POST /ovirt-engine/api/vms/123/stop
POST /ovirt-engine/api/vms/123/stop
The stop action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the stop action should be performed asynchronously. |
6.220.18. suspend POST
This operation saves the virtual machine state to disk and stops it. Start a suspended virtual machine and restore the virtual machine state with the start action.
For example:
POST /ovirt-engine/api/vms/123/suspend
POST /ovirt-engine/api/vms/123/suspend
The suspend action does not take any action specific parameters; therefore, the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the suspend action should be performed asynchronously. |
6.220.19. thawfilesystems POST
Thaws virtual machine file systems.
This operation thaws a virtual machine’s file systems using the QEMU guest agent when taking a live snapshot of a running virtual machine. Normally, this is done automatically by the manager, but this must be executed manually with the API for virtual machines using OpenStack Volume (Cinder) disks.
Example:
POST /api/vms/123/thawfilesystems
POST /api/vms/123/thawfilesystems<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the thaw file systems action should be performed asynchronously. |
6.220.20. ticket POST
Generates a time-sensitive authentication token for accessing a virtual machine’s display.
For example:
POST /ovirt-engine/api/vms/123/ticket
POST /ovirt-engine/api/vms/123/ticketThe client-provided action optionally includes a desired ticket value and/or an expiry time in seconds.
The response specifies the actual ticket value and expiry used.
If the virtual machine is configured to support only one graphics protocol then the generated authentication token will be valid for that protocol. But if the virtual machine is configured to support multiple protocols, VNC and SPICE, then the authentication token will only be valid for the SPICE protocol.
In order to obtain an authentication token for a specific protocol, for example for VNC, use the ticket method of the service, which manages the graphics consoles of the virtual machine, by sending a request:
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket6.220.21. undosnapshot POST
Restores the virtual machine to the state it had before previewing the snapshot.
See the preview_snapshot operation for details.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the undo snapshot action should be performed asynchronously. |
6.220.22. update PUT
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In | Indicates if the update should be applied to the virtual machine immediately or if it should be applied only when the virtual machine is restarted. | |
|
| In/Out |
6.220.22.1. next_run
Indicates if the update should be applied to the virtual machine immediately or if it should be applied only when the virtual machine is restarted. The default value is false, so by default changes are applied immediately.
6.221. VmApplication
A service that provides information about an application installed in a virtual machine.
| Name | Summary |
|---|---|
|
| Returns the information about the application. |
6.221.1. get GET
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. |
6.221.1.1. application
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/789May return information like this:
<application href="/ovirt-engine/api/vms/123/applications/789" id="789"> <name>ovirt-guest-agent-common-1.0.12-3.el7</name> <vm href="/ovirt-engine/api/vms/123" id="123"/> </application>
<application href="/ovirt-engine/api/vms/123/applications/789" id="789">
<name>ovirt-guest-agent-common-1.0.12-3.el7</name>
<vm href="/ovirt-engine/api/vms/123" id="123"/>
</application>6.222. VmApplications
A service that provides information about applications installed in a virtual machine.
| Name | Summary |
|---|---|
|
| Returns a list of applications installed in the virtual machine. |
6.222.1. list GET
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. |
6.222.1.1. applications
A list of applications installed in the virtual machine.
For example, a request like this:
GET /ovirt-engine/api/vms/123/applications/
GET /ovirt-engine/api/vms/123/applications/May return a list like this:
6.222.1.2. max
Sets the maximum number of applications to return. If not specified all the applications are returned.
6.223. VmCdrom
Manages a CDROM device of a virtual machine.
Changing and ejecting the disk is done using always the update method, to change the value of the file attribute.
| Name | Summary |
|---|---|
|
| Returns the information about this CDROM device. |
|
| Updates the information about this CDROM device. |
6.223.1. get GET
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. |
6.223.1.1. current
Indicates if the operation should return the information for the currently running virtual machine. This parameter is optional, and the default value is false.
6.223.2. update PUT
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=trueWith a request body like this:
<cdrom> <file id=""/> </cdrom>
<cdrom>
<file id=""/>
</cdrom>
The changes made with the current=true parameter are never persisted, so they won’t have any effect after the virtual machine is rebooted.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The information about the CDROM device. | |
|
| In | Indicates if the update should apply to the currently running virtual machine, or to the virtual machine after the next boot. |
6.223.2.1. current
Indicates if the update should apply to the currently running virtual machine, or to the virtual machine after the next boot. This parameter is optional, and the default value is false, which means that by default the update will have effect only after the next boot.
6.224. VmCdroms
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. |
6.224.1. list GET
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. |
6.224.1.1. max
Sets the maximum number of CDROMs to return. If not specified all the CDROMs are returned.
6.225. VmDisk
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| Detach the disk from the virtual machine. |
|
|
6.225.1. activate POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.225.2. deactivate POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. |
6.225.3. export POST
6.225.4. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.225.5. move POST
6.225.6. remove DELETE
Detach the disk from the virtual machine.
In version 3 of the API this used to also remove the disk completely from the system, but starting with version 4 it doesn’t. If you need to remove it completely use the remove method of the top level disk service.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.225.7. update PUT
6.226. VmDisks
| Name | Summary |
|---|---|
|
| |
|
|
6.226.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.226.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | ||
|
| In | Sets the maximum number of disks to return. |
6.226.2.1. max
Sets the maximum number of disks to return. If not specified all the disks are returned.
6.227. VmGraphicsConsole
| Name | Summary |
|---|---|
|
| Gets graphics console configuration of the virtual machine. |
|
| |
|
|
Generates the file which is compatible with |
|
| Remove the graphics console from the virtual machine. |
|
| Generates a time-sensitive authentication token for accessing this virtual machine’s console. |
6.227.1. get GET
Gets graphics console configuration of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the graphics console of the virtual machine. | |
|
| In | Use the following query to obtain the current run-time configuration of the graphics console. |
6.227.1.1. current
Use the following query to obtain the current run-time configuration of the graphics console.
GET /ovit-engine/api/vms/123/graphicsconsoles/456?current=true
GET /ovit-engine/api/vms/123/graphicsconsoles/456?current=true
The default value is false.
6.227.2. proxyticket POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the generation of the ticket should be performed asynchronously. | |
|
| Out |
6.227.3. remoteviewerconnectionfile POST
Generates the file which is compatible with remote-viewer client.
Use the following request to generate remote viewer connection file of the graphics console. Note that this action generates the file only if virtual machine is running.
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/remoteviewerconnectionfile
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/remoteviewerconnectionfile
The remoteviewerconnectionfile action does not take any action specific parameters, so the request body should contain an empty action:
<action/>
<action/>
The response contains the file, which can be used with remote-viewer client.
E.g., to fetch the content of remote viewer connection file and save it into temporary file, user can use oVirt Python SDK as follows:
When you create the remote viewer connection file, then you can connect to virtual machine graphic console, as follows:
#!/bin/sh -ex remote-viewer --ovirt-ca-file=/etc/pki/ovirt-engine/ca.pem /tmp/remote_viewer_connection_file.vv
#!/bin/sh -ex
remote-viewer --ovirt-ca-file=/etc/pki/ovirt-engine/ca.pem /tmp/remote_viewer_connection_file.vv| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
Contains the file which is compatible with |
6.227.3.1. remote_viewer_connection_file
Contains the file which is compatible with remote-viewer client.
User can use the content of this attribute to create a file, which can be passed to remote-viewer client to connect to virtual machine graphic console.
6.227.4. remove DELETE
Remove the graphics console from the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.227.5. ticket POST
Generates a time-sensitive authentication token for accessing this virtual machine’s console.
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticket
POST /ovirt-engine/api/vms/123/graphicsconsoles/456/ticketThe client-provided action optionally includes a desired ticket value and/or an expiry time in seconds.
In any case, the response specifies the actual ticket value and expiry used.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The generated ticket that can be used to access this console. |
6.228. VmGraphicsConsoles
| Name | Summary |
|---|---|
|
| Add new graphics console to the virtual machine. |
|
| Lists all the configured graphics consoles of the virtual machine. |
6.228.1. add POST
Add new graphics console to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.228.2. list GET
Lists all the configured graphics consoles of the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The list of graphics consoles of the virtual machine. | |
|
| 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. |
6.228.2.1. current
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.
6.228.2.2. max
Sets the maximum number of consoles to return. If not specified all the consoles are returned.
6.229. VmHostDevice
A service to manage individual host device attached to a virtual machine.
| Name | Summary |
|---|---|
|
| Retrieve information about particular host device attached to given virtual machine. |
|
| Remove the attachment of this host device from given virtual machine. |
6.229.1. get GET
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. |
6.229.2. remove DELETE
Remove the attachment of this host device from given virtual machine.
In case this device serves as an IOMMU placeholder, it cannot be removed (remove will result only in setting its placeholder flag to true). Note that all IOMMU placeholder devices will be removed automatically as soon as there will be no more non-placeholder devices (all devices from given IOMMU group are detached).
DELETE /ovirt-engine/api/vms/123/hostdevices/456
DELETE /ovirt-engine/api/vms/123/hostdevices/456| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.230. VmHostDevices
A service to manage host devices attached to a virtual machine.
| Name | Summary |
|---|---|
|
| Attach target device to given virtual machine. |
|
| List the host devices assigned to given virtual machine. |
6.230.1. add POST
Attach target device to given virtual machine.
Example:
POST /ovirt-engine/api/vms/123/hostdevices
POST /ovirt-engine/api/vms/123/hostdevicesWith request body of type HostDevice, for example
<host_device id="123" />
<host_device id="123" />A necessary precondition for a successful host device attachment is that the virtual machine must be pinned to exactly one host. The device ID is then taken relative to this host.
Attachment of a PCI device that is part of a bigger IOMMU group will result in attachment of the remaining devices from that IOMMU group as "placeholders". These devices are then identified using the placeholder attribute of the HostDevice type set to true.
In case you want attach a device that already serves as an IOMMU placeholder, simply issue an explicit Add operation for it, and its placeholder flag will be cleared, and the device will be accessible to the virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The host device to be attached to given virtual machine. |
6.230.2. list GET
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. |
6.230.2.1. max
Sets the maximum number of devices to return. If not specified all the devices are returned.
6.231. VmNic
| Name | Summary |
|---|---|
|
| |
|
| |
|
| |
|
| Removes the NIC. |
|
| Updates the NIC. |
6.231.1. activate POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the activation should be performed asynchronously. |
6.231.2. deactivate POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the deactivation should be performed asynchronously. |
6.231.3. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.231.4. remove DELETE
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/456The hotplugging feature only supports virtual machine operating systems with hotplugging operations. Example operating systems include:
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
- Windows Server 2008 and
- Windows Server 2003
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.231.5. update PUT
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/456With a request body like this:
<nic> <name>mynic</name> <interface>e1000</interface> <vnic_profile id='789'/> </nic>
<nic>
<name>mynic</name>
<interface>e1000</interface>
<vnic_profile id='789'/>
</nic>The hotplugging feature only supports virtual machine operating systems with hotplugging operations. Example operating systems include:
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
- Windows Server 2008 and
- Windows Server 2003
6.232. VmNics
| Name | Summary |
|---|---|
|
| Adds a NIC to the virtual machine. |
|
|
6.232.1. add POST
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 |
6.232.2. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of NICs to return. | |
|
| Out |
6.232.2.1. max
Sets the maximum number of NICs to return. If not specified all the NICs are returned.
6.233. VmNumaNode
| Name | Summary |
|---|---|
|
| |
|
| Removes a virtual NUMA node. |
|
| Updates a virtual NUMA node. |
6.233.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.233.2. remove DELETE
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. |
6.233.3. update PUT
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/456The request body should contain the following:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out |
6.234. VmNumaNodes
| Name | Summary |
|---|---|
|
| Creates a new virtual NUMA node for the virtual machine. |
|
| Lists virtual NUMA nodes of a virtual machine. |
6.234.1. add POST
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/xmlThe request body can contain the following:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.234.2. list GET
Lists virtual NUMA nodes of a virtual machine.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of nodes to return. | |
|
| Out |
6.234.2.1. max
Sets the maximum number of nodes to return. If not specified all the nodes are returned.
6.235. VmPool
A service to manage a virtual machines pool.
| Name | Summary |
|---|---|
|
| This operation allocates a virtual machine in the virtual machine pool. |
|
| Get the virtual machine pool. |
|
| Removes a virtual machine pool. |
|
| Update the virtual machine pool. |
6.235.1. allocatevm POST
This operation allocates a virtual machine in the virtual machine pool.
POST /ovirt-engine/api/vmpools/123/allocatevm
POST /ovirt-engine/api/vmpools/123/allocatevm
The allocate virtual machine action does not take any action specific parameters, so the request body should contain an empty action:
<action/>
<action/>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the allocation should be performed asynchronously. |
6.235.2. get GET
Get the virtual machine pool.
GET /ovirt-engine/api/vmpools/123
GET /ovirt-engine/api/vmpools/123You will get a XML response like that one:
6.235.3. remove DELETE
Removes a virtual machine pool.
DELETE /ovirt-engine/api/vmpools/123
DELETE /ovirt-engine/api/vmpools/123| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.235.4. update PUT
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.
6.236. VmPools
Provides read-write access to virtual machines pools.
| Name | Summary |
|---|---|
|
| Creates a new virtual machine pool. |
|
| Get a list of available virtual machines pools. |
6.236.1. add POST
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/vmpoolsWith 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. |
6.236.2. list GET
Get a list of available virtual machines pools.
GET /ovirt-engine/api/vmpools
GET /ovirt-engine/api/vmpoolsYou 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. |
6.236.2.1. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.236.2.2. max
Sets the maximum number of pools to return. If this value is not specified, all of the pools are returned.
6.237. VmReportedDevice
| Name | Summary |
|---|---|
|
|
6.237.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.238. VmReportedDevices
| Name | Summary |
|---|---|
|
|
6.238.1. list GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of devices to return. | |
|
| Out |
6.238.1.1. max
Sets the maximum number of devices to return. If not specified all the devices are returned.
6.239. VmSession
| Name | Summary |
|---|---|
|
|
6.239.1. get GET
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.240. VmSessions
Provides information about virtual machine user sessions.
| Name | Summary |
|---|---|
|
| Lists all user sessions for this virtual machine. |
6.240.1. list GET
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/sessionsThe response body will contain something like this:
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of sessions to return. | |
|
| Out |
6.240.1.1. max
Sets the maximum number of sessions to return. If not specified all the sessions are returned.
6.241. VmWatchdog
A service managing a watchdog on virtual machines.
| Name | Summary |
|---|---|
|
| Returns the information about the watchdog. |
|
| Removes the watchdog from the virtual machine. |
|
| Updates the information about the watchdog. |
6.241.1. get GET
Returns the information about the watchdog.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out | The information about the watchdog. |
6.241.1.1. watchdog
The information about the watchdog.
The information consists of model element, action element and the reference to the virtual machine. It may look like this:
6.241.2. remove DELETE
Removes the watchdog from the virtual machine.
For example, to remove a watchdog from a virtual machine, send a request like this:
DELETE /ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000
DELETE /ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.241.3. update PUT
Updates the information about the watchdog.
You can update the information using action and model elements.
For example, to update a watchdog, send a request like this:
PUT /ovirt-engine/api/vms/123/watchdogs <watchdog> <action>reset</action> </watchdog>
PUT /ovirt-engine/api/vms/123/watchdogs
<watchdog>
<action>reset</action>
</watchdog>with response body:
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <vm href="/ovirt-engine/api/vms/123" id="123"/> <action>reset</action> <model>i6300esb</model> </watchdog>
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000">
<vm href="/ovirt-engine/api/vms/123" id="123"/>
<action>reset</action>
<model>i6300esb</model>
</watchdog>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The information about the watchdog. |
6.241.3.1. watchdog
The information about the watchdog.
The request data must contain at least one of model and action elements. The response data contains complete information about the updated watchdog.
6.242. VmWatchdogs
Lists the watchdogs of a virtual machine.
| Name | Summary |
|---|---|
|
| Adds new watchdog to the virtual machine. |
|
| The list of watchdogs of the virtual machine. |
6.242.1. add POST
Adds new watchdog to the virtual machine.
For example, to add a watchdog to a virtual machine, send a request like this:
POST /ovirt-engine/api/vms/123/watchdogs <watchdog> <action>poweroff</action> <model>i6300esb</model> </watchdog>
POST /ovirt-engine/api/vms/123/watchdogs
<watchdog>
<action>poweroff</action>
<model>i6300esb</model>
</watchdog>with response body:
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <vm href="/ovirt-engine/api/vms/123" id="123"/> <action>poweroff</action> <model>i6300esb</model> </watchdog>
<watchdog href="/ovirt-engine/api/vms/123/watchdogs/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000">
<vm href="/ovirt-engine/api/vms/123" id="123"/>
<action>poweroff</action>
<model>i6300esb</model>
</watchdog>| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out | The information about the watchdog. |
6.242.1.1. watchdog
The information about the watchdog.
The request data must contain model element (such as i6300esb) and action element (one of none, reset, poweroff, dump, pause). The response data additionally contains references to the added watchdog and to the virtual machine.
6.242.2. list GET
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. |
6.242.2.1. max
Sets the maximum number of watchdogs to return. If not specified all the watchdogs are returned.
6.242.2.2. watchdogs
The information about the watchdog.
The information consists of model element, action element and the reference to the virtual machine. It may look like this:
6.243. Vms
| Name | Summary |
|---|---|
|
| Creates a new virtual machine. |
|
|
6.243.1. add POST
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 |
6.243.1.1. clone
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=trueWith a request body like this:
When this parameter is true the permissions of the template will also be copied, as when using clone_permissions=true.
6.243.1.2. clone_permissions
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=trueWith a request body like this:
6.243.2. list GET
| 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 |
6.243.2.1. all_content
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=trueThe reason for not including these attributes is performance: they are seldom used and they require additional queries to the database. So try to use the this parameter only when it is really needed.
6.243.2.2. case_sensitive
Indicates if the search performed using the search parameter should be performed taking case into account. The default value is true, which means that case is taken into account. If you want to search ignoring case set it to false.
6.244. VnicProfile
This service manages a vNIC profile.
| Name | Summary |
|---|---|
|
| Retrieves details about a vNIC profile. |
|
| Removes the vNIC profile. |
|
| Updates details of a vNIC profile. |
6.244.1. get GET
Retrieves details about a vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| Out |
6.244.2. remove DELETE
Removes the vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.244.3. update PUT
Updates details of a vNIC profile.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the update should be performed asynchronously. | |
|
| In/Out | The vNIC profile that is being updated. |
6.245. VnicProfiles
This service manages the collection of all vNIC profiles.
| Name | Summary |
|---|---|
|
| Add a vNIC profile. |
|
| List all vNIC profiles. |
6.245.1. add POST
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/vnicprofilesWith 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. |
6.245.2. list GET
List all vNIC profiles.
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Sets the maximum number of profiles to return. | |
|
| Out | The list of all vNIC profiles. |
6.245.2.1. max
Sets the maximum number of profiles to return. If not specified all the profiles are returned.
6.246. Weight
| Name | Summary |
|---|---|
|
| |
|
|
6.246.1. get GET
6.246.2. remove DELETE
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In | Indicates if the remove should be performed asynchronously. |
6.247. Weights
| Name | Summary |
|---|---|
|
| |
|
|
6.247.1. add POST
| Name | Type | Direction | Summary |
|---|---|---|---|
|
| In/Out |
6.247.2. list GET
| 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 |
6.247.2.1. max
Sets the maximum number of weights to return. If not specified all the weights are returned.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}