To create a version of a spec, go to the owner enterprise (that created the spec)→ Virtual datacenters → Open a Virtual appliance created from the spec → Virtual appliance spec button → Create new spec version.
Screenshot: create a spec or spec version
To create a virtual appliance based on a spec, go to Virtual datacenters → V. Appliances list → select Create virtual appliance based on spec.
Screenshot: create a virtual appliance based on a spec
To manage specs, go to the owner enterprise → Apps library → Virtual appliance specs.
Screenshot: Apps library specs tab
When creating the new virtual appliance based on the spec, the platform will:
The following VM configuration elements are saved and created by virtual appliance specs. Support for elements is marked for datacenters (DC) and public cloud regions (PCR). When creating a virtual appliance from a spec, the platform will assign the spec icon to the virtual appliance.
|Element||DC||PCR||Save in Spec||Create in VApp|
|General information: hardware profiles, CPU, RAM, remote access and description||Same. If a matching hardware profile is not found, the platform will activate or create one, or the user can select another available hardware profile|
|Anti-affinity layers||VMs in layers||Same|
|Scaling groups||Scaling groups are not supported|
|VM templates||Template name is saved|
The system matches the spec template name against the Apps library template name. The user selects from a list of templates with names that contain the spec template name. The match is done with an SQL %LIKE% command from the spec to the template, so spec template "m0n0" will match with "m0n0" and "m0n0wall" in the Apps library. But spec template "m0n0wall" will not match with "m0n0" in the Apps library
|Template auxiliary hard disks||N/A|
Template system disks and other datastore hard disks and their tiers are saved
The platform will create template disks in order as in the template with no gaps in the sequence. Then empty additional hard drives and volumes will be added in the same order as in the base virtual appliance. The platform will search for datastore tiers by name, as for templates
|Persistent VMs||Persistent VMs are not supported. To create a spec from a persistent VM, first create an instance, which is a non-persistent template|
|Private network, Private IPs||Save private network characteristics: network address and mask only. Save private IPs|
The materialize process will present the addresses of the spec private networks. Abiquo will display matching networks in the virtual datacenter in green text, and ones that are not present in red text. Abiquo will display the number of private IPs to use in each network.
The user can choose to change any private network, even if it matches the spec network. The user can choose to create a new network (specifying the IP address, mask and gateway), or replace the network with an existing VDC network.
|Network gateways||Abiquo will determine if a NIC has a gateway IP address and save this information in the spec|
|Public network||Number of public IPs is saved|
The materialize process will try to use public IPs that were already purchased by the enterprise. These public IPs will be momentarily quarantined during the materialization process. If not, the materialize process will purchase new public IPs. The public networks will be used in the order returned by the API. In public cloud, the platform will use floating IPs
|External IPs||Not supported, except for basic support in vCloud|
If you create a spec containing an external IP, the materialize process will fail because the external IP is unsupported.
In vCloud, specs have basic support for external networks. The validation process will list the network, and you can select it and then continue with the process. The platform will create the VApp correctly. Remember to ensure that there are enough external IP addresses available for the new virtual appliance
|Unmanaged IPs||Not supported||If you create a spec containing an unmanaged IP, the materialize process will fail because the unmanaged IP is unsupported.|
Data on external storage volumes is not included. To use data on a volume, create an instance to save it to a template disk
The specifications, disk controller types, and tiers of the volumes are saved.
|Hard disk (data)|
Data on hard disks attached to the VM is not included. To use data on a hard disk, create an instance to save it to the template
|Empty hard disks with the same specifications as the attached hard disks are created. Empty disks are named Empty disk-UUID|
|Hard disk (specifications)|
The specifications, disk controller types and tiers of the hard disks are saved.
|Backup configuration||Configured backups are stored||Backups are configured|
Firewalls attached to VMs or load balancers are saved
|Load balancers||Load balancers attached to VMs are saved, including health checks and so on|
|Alarms and Alerts|
Alarms and alerts are saved
The materialize process creates all existing alarms and alerts, regardless of the existence of their corresponding metrics
|VM variables||VM variables are saved|
Chef status, runlist and attributes are stored