Documentation

Skip to end of metadata
Go to start of metadata

 

Description of new VApp Specs functionality

This document describes changes to Virtual Appliance Specs in Abiquo 3.8.x versions.

Abiquo 3.8.3

The following changes to Virtual Appliance Specs were introduced in Abiquo 3.8.3

Public cloud support for Virtual Appliance Specs

With public cloud support for Virtual Appliance Specs you can

  1. Create Specs in private cloud for use in public cloud
  2. Materialize Specs in public cloud
  3. Create Specs from public cloud for use in private cloud

Specs save the number of virtual resources in an abstract notation that is not related to any specific cloud technology. For example, for floating IPs in public cloud, Abiquo will save the use of a public network with the corresponding number of public IPs.

The following table provides some general guidelines about using Specs in hybrid cloud 

ElementNotes
TemplatePrivate cloud may allow multiple disk templates. In public cloud, Abiquo templates always have a single disk
Additional disks

Private cloud may allow additional disks. In public cloud the user may not add external disks within Abiquo

Networks
  • Private networks in private cloud will be translated to external networks in providers supporting external networks (e.g. Azure) and vice versa
    • In public cloud, Abiquo will look for the default VLAN's globalNetwork in the target VDC to use or create an external network (subnet) of this network
  • Public networks in private cloud will be translated to floating IPs in public cloud and vice versa.

Network gateways

When creating a network for use in hybrid cloud specs, check that your network gateway address is not a reserved IP address in the public cloud provider. the gateway address is reserved, the Spec will fail when the user tries to deploy it.

  • The default gateway in AWS and Azure is address 5
  • The default gateway in Neutron and NSX is address 1
  • A gateway that is compatible with all providers and default reserved addresses in SDN solutions is address 22
NICs
  • Note that some IP addresses may be reserved by the provider
    • Azure and AWS reserve the first 4 IP addresses and the last IP address of private networks
    • By default, Neutron and NSX reserve IP addresses from address 1 to address 21 but this range is configurable by the system administrator
  • The number of NICs allowed per virtual machine may vary across different private and public cloud environments.
Change to how VApp Specs manages NICs with gateway IPs
  1. When you create a Spec, Abiquo now checks if NICs have gateway addresses and stores this information in the Spec 
  2. When Abiquo materializes the Spec, if the NIC has a gateway address, Abiquo tries to assign the gateway address
  3. Abiquo will not assign a gateway address to a non-gateway NIC
  4. The user must check that there are sufficient IPs available, not including the gateway address

Abiquo 3.8.2

The following changes to Virtual Appliance Specs were introduced in Abiquo 3.8.2

  1. Specs now save the following additional configuration elements:
    1. VM metrics (hypervisor and custom), alarms and alerts
    2. Volume and disk controller types
      1. If you are using a controller type that is not compatible with the target hypervisor, (e.g. KVM VIRTIO -> ESXi), Abiquo will create VApps using hypervisor default
  2. When creating a VApp from a Spec (materializing), there are new preview screens that include:
    1. General Information
      1. Details of firewalls and load balancers
    2. Virtual machines preview where you can select each VM to display details
  3. From the VApp preview you can edit:
    1. An individual VM to modify:
      1. VM variables
      2. Chef
        1. Runlist
        2. Attributes
    2. Alert subscribers
  4. When materializing metrics
    1. Built-in metrics of the exact same name (i.e. same hypervisor, or very standard name e.g. CPU) will be materialized
      1. Other metrics will not be materialized
    2. All custom metrics will be materialized
  5. All alarms and alerts will be materialized even if their metrics do not exist 
  6. When materializing disks and volumes: 
    1. If the spec controller type is not compatible with the target hypervisor, (e.g. KVM VIRTIO -> ESXi), Abiquo will materialize the spec with the hypervisor default controller type
    2. The order of disks and volumes is now: 
      1. Template disks in sequence order without any gaps
      2. Other disks and volumes in VM sequence order without any gaps

For full details of Spec save and materialize functionality, see the table in Introduction to virtual appliance specs

Screenshots

General information optional display of firewall and load balancer details:


Virtual machines preview: select to display a virtual machine and edit its details

Edit VM variables

Edit VM Chef runlist

Edit VM Chef attributes

Edit alert subscribers

  • No labels