API Changelog v3.8

Abiquo API Changes

Abiquo is committed to maintaining backwards compatibility for 2 minor releases. If for some reason, backwards compatibility were not possible to maintain, Abiquo would detail the changes in the API Changelog. For example, Abiquo 3.6 should be compatible with 3.4 and 3.2. The best practice to ensure compatibility is to use the version number in the header of your API request with the media type and content type.

For major versions such as 3.0, Abiquo will make a best effort to maintain compatibility with at least the previous version, in the case of 3.0 this would be 2.6. Abiquo will provide details of any changes in the API Changelog. 

Abiquo API 3.8 Changelog

The Abiquo 3.8 API includes support for all of the new Abiquo 3.8 features.

Datastore tiers feature

See Datastore tiers for the basic information about this feature.

To support the datastore tiers feature to offer service levels on local storage on hypervisors, Abiquo 3.8 has a new DatastoreTier resource for managing datastore tiers, adding datastores, allowing access for all enterprises, and so on. See DatastoreTierResource.  

In addition, you can retrieve the datastore tiers that are available at a given location through the locations resource. See LocationsResource

There are new single data transfer object and list media types for datastore tiers. See Abiquo Data Media Types#DatastoreTier Media Type

In addition, there are new links to datastore tiers in objects that may have a default tier for a disk or disks (including virtual machine templates and virtual datacenters) or for objects that may be deployed to a datastore tier (virtual machine disks).

Here is an example datastore tier link:

...
      {  
         "title":"Renardotier",
         "rel":"defaultdatastoretier",
         "type":"application/vnd.abiquo.datastoretier+json",
         "href":"https://demotesting.bcn.abiquo.com:443/api/cloud/locations/1/datastoretiers/2"
      },
...

To add datastores to a tier or remove datastores from a tier, you should use a collection of links to datastores.

The default datastore tier for a virtual datacenter is set as a link to the datastore tier object. Note that this must be one of the enabled tiers that is available in the location. If you perform retrieve the virtual datacenter when the datastore tier is disabled, the link will not be present.

Disk objects can now have a default datastore tier, which is also set with a link to the datastore tier object. Again, this must be one of the enabled tiers that is available in the location.

Virtual appliance spec feature

The virtual appliance spec feature enables configuration reuse. Specs are stored for each enterprise.

See VirtualApplianceSpecResource

They can be shared using resource scopes for enterprises, created with the Scopes Resource

Users can create a virtual appliance from a spec. See VirtualApplianceResource#Createavirtualappliancefromaspec

Changes to monitoring

• DTO changes in "Push custom metric datapoints", datapoint attributes 'doubleValue' and 'longValue' are replaced by the attribute "value"
• DTO changes in "Get metrics datapoints", datapoint attributes 'doubleValue' and 'longValue' are replaced by the attribute "value"
• DTO changes in "Get metric datapoints", datapoint attributes 'doubleValue' and 'longValue' are replaced by the attribute "value"
• Updated DTOs with new alarm links
• Added alarm and alert functionality sections

Alarms and alerts feature

Extension of the monitoring and metrics features. You can create alarms for virtual machine metrics. See MetricAlarmResource

Then for a group of alarms at virtual appliance level, you can create an alert. See AlertResource

Virtual machine template variables

To support the collectd feature, a new request has been created to push collectd value lists in JSON format. See VirtualMachineMetricsResource

OpenStack Neutron Integration

When you create a datacenter to use Neutron, you must add the cloud provider proxy remote service.

Devices

Abiquo 3.8 introduced devices to manage SDN and firewall and load balancer integrations in private datacenters with four device types.

In Abiquo 3.8.3, these devices were deprecated and a unified device was introduced. See #Abiquo API 3.8.3 Changelog

Abiquo API 3.8.2 Changelog