6.4. REST API

BZ#755492
In Red Hat Enterprise Virtualization Manager, a status field for storage objects has been added under "Storage/API". This allows you to tell, for instance, whether a storage type is attached to a Data Center.
BZ#755499
Previously, the Red Hat Enterprise Virtualization REST API required clients to supply network IDs and names when detaching NICs from hosts, though the backend could retrieve this information.

Red Hat Enterprise Virtualization's REST API no longer requires you to supply network IDs and names when detaching NICs from hosts.
BZ#755546
Previously in Red Hat Enterprise Virtualization's REST API, there was no way to set a null scheduling policy. Selecting "None" as the scheduling policy caused "<scheduling policy></scheduling policy>" to be exported.

It is now possible to set a null scheduling policy in Red Hat Enterprise Virtualization's REST API by setting "<policy>None</policy>".
BZ#755549
Previously, Red Hat Enterprise Virtualization's REST API did not support functionality for destroying a storage domain (where "destroy" means "logical removal from the manager"), though the Red Hat Enterprise Virtualization User Interface did support such functionality. 

Red Hat Enterprise Virtualization's REST API now supports functionality for destroying a storage domain.
BZ#755566
Previously, it was not possible in Red Hat Enterprise Virtualization's REST API to add group permissions in the same way as user permissions. The API has been updated and the same mechanism is available for adding both group and user permissions.
BZ#755572
Previously, creating a resource asynchronously in Red Hat Enterprise Virtualization's REST API caused AbstractBackendCollectionResource.resolveCreated to throw an NPE (Null Pointer Exception). 

This issue has been fixed, and creating a resource asynchronously in Red Hat Enterprise Virtualization's REST API no longer causes AbstractBackendCollectionResource.resolveCreated to throw an NPE (Null Pointer Exception).
BZ#755576
Previously, Red Hat Enterprise Virtualization Manager's REST API would not allow you to attach a network to a cluster by name.

Red Hat Enterprise Virtualization Manager's REST API has been updated and now allows you to attach a network to a cluster by name.
BZ#759831
Previously, Red Hat Enterprise Linux's REST API did not properly interpret input boot sequences, which meant that you could not set the boot sequence with REST API.

The boot sequence was held in the data-structure: java.util.EnumSet, which does not maintain order. After the change, the boot sequence is held in a java.util.LinkedHashSet, which does maintain order. This ensures that Red Hat Enterprise Virtualization's REST API passes the boot sequence in the same order that the user specified.