Abiquo 5.1

Skip to end of metadata
Go to start of metadata

The platform will automatically manage hardware profiles as follows:

  • Provider hardware profiles
    • If you synchronize a public cloud region and a VM has a hardware profile that is not allowed for the enterprise, the platform will automatically allow the hardware profile
    • For AWS, Abiquo recommends hardware profiles based on information supplied by AWS and filters:
      • Virtualization type of Paravirtual or HVM

      • Root device type of Instance store or EBS

      • Architecture of I386, X86_64, or ARM64
    • If the provider does not support CPU and RAM as well as hardware profiles, and if there is no hardware profile that matches the CPU and RAM values, the platform cannot create a hardware profile, so the user will have to select another one

    • During onboarding, if there is a cost code assigned to the VM template, the platform will match the template cost code with a hardware profile cost code and assign the corresponding hardware profile
  • Abiquo hardware profiles
    • If a tenant enterprise already has VMs deployed when you enable hardware profiles, the platform will try to assign existing hardware profiles. If the templates of the deployed VMs have cost codes, the platform will match the cost codes with the cost codes of hardware profiles and assign the corresponding hardware profiles. If an existing profile is inactive, the platform will activate this profile and assign it. Otherwise, the platform will create a new hardware profile named ABQ_HP_{cpu}_{ram}_ID.
    • If you capture a VM, the platform will behave as for VMs that were already deployed when you enabled hardware profiles. During capture, the template has no cost code, so the platform cannot match cost codes to assign a hardware profile 
  • VApp specs
    • When you create a VApp spec, the platform records the CPU and RAM of each VM. It also records the name, family, dynamic CPU, and dynamic RAM properties of the hardware profile. When you create a virtual appliance from a spec, the hardware profiles used for the VMs created by the spec are found following these criteria:
      1. An active hardware profile that matches CPU, RAM of the VM and all the other properties.
      2. Active hardware profiles with the same size or larger with the same family.
      3. Active hardware profiles with the same size or larger in all families.
    • If more than one hardware profile is found, the hardware profiles will be ordered using the following properties:

      1. Dynamic CPU

      2. Dynamic RAM

      3. Current generation

      4. Cores per socket

    • The platform will select a hardware property that:

      • Does not have dynamic CPU and/or dynamic RAM

      • Is of the current generation

      • Has the smallest cores per socket (if applicable). 

    • The others will appear as warnings on the Warning tab of the Spec creation dialog. 

    • If the CPU and RAM do not match exactly with the VM, there will also be a warning. 

    • The selected hardware profile can be changed on the Virtual machines tab


 Click here to show/hide the screenshots

Screenshot: Warning that the hardware profile does not exactly match

Screenshot: Warning that there are multiple hardware profiles available