Existing/New API

API name

Parameters

Existing

createServiceOffering

diskofferingid (optional) (UUID) - to associate the disk offering (with one of the existing disk offerings) with the compute offering

diskofferingstrictness - (optional, default value false) (boolean) - to indicate the strictness of the disk offering association with the compute offering. When set to true, override disk offering is not allowed on deploy VM and change disk offering is not allowed for the ROOT disk

Existing

createDiskOffering

disksizestrictness (optional, default value false) (boolean) - to allow or disallow the resize operation on the disks created from this disk offering, if the flag is true then resize is not allowed

Existing

resizeVolume

Existing parameter "size" is now used to change to resize volume directly without having to provide new disk offering. Previously this parameter is taken only when custom disk offering is provided.

Existing

deployVirtualMachine

overridediskofferingid - the ID of the disk offering for the virtual machine to be used for root volume instead of the disk offering mapped in service offering. In case of virtual machine deploying from ISO, then the diskofferingid specified for root volume is ignored and uses this override disk offering id

Existing

listDiskOffering

volumeid: id of the volume. When provided “disksizestrictness” flag added to the volume is used to list disk offering. If disk size strictness is true, then disk offerings with same size will be listed. This volume is also used to list disk offerings based on the storage tags of the existing disk offering of the volume, when the configuration parameter “match.storage.pool.tags.with.disk.offering” is true.

storageid: id of the storage pool. When provided, storage tags on the storage pool will be considered to filter the disk offerings list, when the configuration parameter “match.storage.pool.tags.with.disk.offering” is true.

Both volumeid and storageid cannot be provided at the same time.

New

changeOfferingForVolume

id - id of the volume

diskofferingid – id of the new disk offering to which offering has to be changed

size, miniops, maxiops – details required if the provided offering is custom disk offering

automigrate - flag for automatic migration of the volume with new disk offering whenever migration is required to apply the offering

Table name

New columns

service_offering

Following are the new columns added to the table, these changes are mainly to decouple from disk offering.

`uuid` - unique identifier

`name` - name of the service offering

`display_text` - display text of the service offering

`unique_name` - unique name for system offerings

`customized` - indicates if service offering is customizable or not

`created` - date when service offering was created

`removed` - date when service offering was removed

`state` - state of service offering either Active or Inactive

`disk_offering_strictness` - defines strict binding with disk offering or not

`disk_offering_id` - ID of the disk offering to which service offering is linked to

`system_use`- is this service offering for system use only

disk_offering

`disk_size_strictness` - To allow or disallow the resize operation on the disks created from this offering

`compute_only` - when set to 1, disk offering has one to one binding with compute offering and used for root disk only

Table name

Removed columns

disk_offering

`type` - This used to hold values "Service" or "Disk", this column is now changed to `compute_only`

`system_use` - This is applicable only for service offering, so moved it to the service offering table

vm_instance

`disk_offering_id` - this is a redundant column since root volume entry already holds the actual disk offering. Also, the disk_offering_id may not hold actual value if the disk offering is overridden during VM deployment.