Table of Contents |
---|
...
Infrastructure → Public → select provider region → Hardware profiles
Infrastructure → Private → select datacenter → Servers view → Hardware profiles
...
Before you create hardware profiles in private cloud, the platform will display the default hardware profile families and types.
...
Manage hardware profiles with the API
...
Excerpt | ||
---|---|---|
| ||
In public cloud providers with hardware profiles, when you create a public cloud region and add credentials for an enterprise, Abiquo will automatically retrieve the hardware profiles for the public cloud region.
To synchronize hardware profiles:
By default, for each enterprise with credentials, the hardware profiles mode is enabled. By default, all hardware profiles are available to all enterprises. |
...
Classify hardware profiles in private cloud
Excerpt | ||
---|---|---|
| ||
To help users to easily select the right hardware profile for their VMs, providers usually classify hardware profiles by family and type. The platform contains one set of default families that are available in both public and private cloud. In private cloud and in public cloud regions without native hardware profiles, you can also create your own hardware profile families and types that will be available in all of these locations. To classify hardware profiles, first create families, then create types. To create a hardware profile family or type:
Create a hardware profile family
Create a hardware profile type |
...
Create a hardware profile
Excerpt
name | Create a hardware profile |
---|
Panel |
---|
Privileges: Access infrastructure view and private DCs, View datacenter details, Manage datacenter infrastructure elements |
To create a hardware profile:
Go to Infrastructure → Private or Public
Select a location and go to Hardware profiles
Click the + add button
Enter the details of the hardware profile
Click Save
...
Field | Value |
---|---|
Family | Select a family to classify the hardware profile. The family can help users understand the main purpose of the hardware profile |
Type | Select a type to classify the hardware profile. The type can help users understand the performance specifications of the hardware profile |
Name | Enter a unique name for the hardware profile. Identify it to users who will select it for their VMs. |
CPU | The number of virtual CPUs to assign to VMs using this hardware profile. The combination of CPU and RAM must be unique in the datacenter. For dynamic hardware profiles this is the default value. |
Cores per socket | The number of cores per socket to use for supported hypervisors such as VMware. The number of CPUs must be divisible by this value. For dynamic hardware profiles this is the default value. |
RAM | The amount of virtual RAM to assign to VMs using this hardware profile. The combination of CPU and RAM must be unique in the datacenter. Select RAM units of MB, GB or TB. For dynamic hardware profiles, this is the default value. |
Dynamic | To allow the user to enter CPU and/or RAM values, select the Dynamic option/s. Pricing and billing of dynamic hardware profiles will include cost codes, and CPU and RAM usage pricing. |
Extra charges | For pricing and billing, select extra charges for the hardware profile. See Create a new cost code for an extra charge in Pricing view. |
Active | Select this checkbox to activate or deactivate the hardware profile. |
Current generation | Select this checkbox to mark that the hardware profile is compatible with current VM templates |
...
Set prices for hardware profiles
Excerpt | ||||
---|---|---|---|---|
| ||||
To set prices for hardware profiles using cost codes for extra charges:
|
...
Enable users to work with hardware profiles
After you have prepared hardware profiles, do the following steps:
Enable hardware profiles for your tenants and select allowed hardware profiles. See Configure an enterprise in a cloud location#Allowatenanttousehardwareprofiles.
By default, users can select from all custom hardware profiles for all templates. You can edit a VM template and
Recommend a set of hardware profiles OR
Enable a set of selected hardware profiles for each template.
See Modify a VM template#ActivatehardwareprofilesforaVMtemplate
...
Automatic management of hardware profiles
...
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:
An active hardware profile that matches CPU, RAM of the VM and all the other properties.
Active hardware profiles with the same size or larger with the same family.
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:
Dynamic CPU
Dynamic RAM
Current generation
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
Screenshot: Warning that the hardware profile does not exactly match
...
Screenshot: Warning that there are multiple hardware profiles available
...
...
Prevent users from working with a hardware profile
...