Configure your user account
All users should configure their user accounts before starting work with the cloud platform.
Edit user details
Configure two-factor authentication
This section describes the administrator tasks in public cloud.
Create public cloud regions
Control tenant resources
You can control the resources that an enterprise may consume. This will help prevent resource over allocation, enterprises using resources from other enterprises, and even DoS attacks. Allocation limits will also help system administrators to anticipate user needs and forecast resource demand. Hard and soft limits are used by the resource scheduler to decide if a user can deploy a virtual appliance or not.
Enterprise allocation limits are checked during configuration or deploy, or before operations as shown in the above table.
Allow the tenant to access regions
To set the datacenters and public cloud regions that an enterprise is allowed to access, edit the Enterprise and click the Datacenters tab.
Select one or more datacenters or public cloud regions in the left pane and drag and drop them into the "Allowed Datacenters" right pane.
Access to at least one datacenter or public cloud region is required in order to deploy VMs. The left pane contains datacenters, which are "Prohibited Datacenters" by default.
Note that Allowed datacenters are working datacenters where users can deploy. This is different to an admin user having administration Scope to administer the infrastructure of datacenter.
Limit tenant resources in the region
You can set resource allocation limits for this enterprise in each allowed datacenter or public cloud region. To set allocation limits, select one of the Allowed Datacenters in the right pane and click the edit button. Set these limit values in the pop-up that opens.
Limit resources for an enterprise in a public cloud region
Validation of resource limits in a location
As for overall enterprise limits, resource limits in a datacenter or public cloud region are validated as described in the following table.
Tenants obtain cloud provider credentials
If the tenant does not have cloud provider credentials, they should follow their cloud provider's instructions on how to obtain access to the provider's API.
Abiquo provides basic guides to obtaining credentials, but the tenant should always consult the cloud provider for the most up-to-date information.
Add tenant credentials for each provider
Before you enter public cloud credentials, there must be an existing public cloud region for the provider.
To add credentials for a public cloud provider
Prepare foundation template library
In the Abiquo Apps Library you can compile a selection of certified public cloud templates for your users to deploy by self-service.
Abiquo will store the details of these templates but not their disks.
Tenant administrator tasks
This section describes tasks that will generally be performed by a tenant administrator. These tasks will vary depending on the cloud platform configuration.
Prepare enterprise templates
Depending on their user privileges, the tenant administrator may be able to do the following tasks
Onboard from public cloud
Onboard virtual datacenters from public cloud
Abiquo automatically onboards from public cloud regions
If your public cloud provider does not support virtual datacenter entities, the platform will automatically onboard when you select the public cloud region.
Restrict user access to virtual datacenters
By default, all users have access to all virtual datacenters. However, you can select a list of virtual datacenters for each user and they will only be able to access these virtual datacenters.
To restrict VDC access, open Users view and create or edit a user who is not an administrator or who does not have the No VDC restriction privilege.
On the create or edit dialog, select the Restrict access to VDC checkbox to open the list of available virtual datacenters. If none are selected, the user will have access to all VDCs. Select the VDCs where this user will be able to deploy VMs. You can only restrict the VDC access of users without the No VDC restriction privilege.
This section describes how to manage networks in private datacenters and public cloud providers.
Cloud user tasks
This section describes the tasks that may be performed by the cloud user.
Edit your user account details
After you log in, you may need to edit your user account to update your details:
Create a virtual appliance to group your VMs
A virtual appliance is folder that holds a group of VMs so that you can easily access them and launch them into the cloud together. At the virtual appliance level, you may also be able to create templates from the disks of your VMs, view VM metrics and create alarms.
To create a new virtual appliance:
The platform will create the virtual appliance. To open it, click on its name.
To create a VM:
The platform will create your VM. The status bar below the VM icon says NOT_ALLOCATED, which means that the VM has not yet been launched into the cloud. Select your VM to display its details in the lower panel.
Screenshot: Create a VM with drag and drop
Screenshot: Select a hardware profile
To launch your VMs, click the Deploy virtual appliance button on the right-hand side of the screen.
The platform will launch the VMs and power them on. The status bar below each VM icon will be coloured green. And the Deploy button changes to become the Undeploy button, which you can use to destroy the VMs.
Screenshot: Deploy a virtual appliance
To display the VM control panel, select the VM icon. From this panel, you can:
By default, the description panel provides a short description of the VM template.
The following screenshots show the Network and Storage panels, which are an easy way to check what IP addresses and storage are assigned to your machine.
Obtain public IPs for VMs
Configure or reconfigure a VM
To change the general configuration of a VM:
If the VM is deployed but other VMs are not deployed, the changes might not be applied directly. You may need to click the Deploy all VMs button to apply the changes in the hypervisor.
Configure Chef Recipes and Roles
Chef is an infrastructure automation product that uses configuration recipes. You can use Abiquo Chef Integration to deploy a VM that will then configure itself using Chef recipes and roles.
The Chef tab is enabled if the enterprise is Chef-enabled and the VM template is Chef-enabled. Before the VM is deployed, you can select from the available roles and recipes. These will be added to the machine's runlist. When the machine is deployed it will download the roles and recipes, and run them in order. Click the Chef tab. By default on this tab you can select roles. Mark the "Select individual components" checkbox to select individual recipes too. The selected recipes will be added to the Virtual Appliance's runlist in order of selection.
To change the order of the runlist, click on the pencil button beside a role or recipe, then edit the order number, then click OK.
Change the Order of Roles and Recipes After Deployment
To change the runlist order after deployment click on the pencil button, then edit the order number, then click OK. The Abiquo Chef Agent will connect to the Chef Server and update the runlist.
Configure Monitoring and Metrics
You can enable the option to fetch metrics from the public cloud region.
To enable VM monitoring and metrics,work with a VM that is powered off or undeployed:
Display Metrics for a VM
To display metrics for a VM, on the VM icon, click the Monitoring symbol. The metrics panel will open.
To update the display of a metric, click the refresh button.
To configure the display of a metric
To view the exact metric values in a call-out box, mouse over the monitoring graph line.
To create a highlight point, click on the metric graph line.
To simultaneously view the data for more than one VM, use the virtual appliance monitoring view.
Delete a VM
To delete a VM, move the mouse over the VM icon, and from the options menu, select Delete. You can delete a VM that is deployed. If you undeploy a VM before you delete it, the platform may request that you synchronize the virtual appliance until you delete the undeployed VM.