This manual is a basic guide to how to Administer and Use Public Cloud in Abiquo
The following basic roles are described in this manual: cloud administrator, enterprise administrator, and user.
|Table of Contents|
This section describes the cloud administrator tasks in public cloud.
All users should configure their user accounts before starting work with the cloud platform.
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.
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.
By default, when a datacenter or public cloud region is created it is automatically assigned as Allowed for the current user's enterprise only.
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.
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.
As for overall enterprise limits, resource limits in a datacenter or public cloud region are validated as described in the following table.
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.
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
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.
This section describes tasks that will generally be performed by a tenant administrator.
Abiquo provides basic guides to obtaining credentials, but the you should always consult the cloud provider for the most up-to-date information.
Depending on their user privileges, the tenant administrator may be able to do the following tasks
If you public cloud provider does not support virtual datacenter entities, Abiquo will automatically onboard when you select the public cloud region.
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.
This section describes the tasks performed by the cloud user. Depending on user privileges, some of these functions may be performed by the tenant administrator.
Click on your user name in the top right-hand corner of the screen.
Edit your user account and update your details. Add a public key for SSH access to VMs deployed in public cloud.
To create a new virtual appliance, open the Virtual datacenters view. Then select the virtual datacenter where the virtual appliance will be deployed, click the add button, and complete the form.
The basic process for working with VMs is the same throughout the whole Abiquo cloud platform, regardless of the underlying technology, which may be hypervisors, public clouds or Docker. The following screenshots show a private cloud environment, but they would be very similar for a public cloud or even a Docker environment.
Configuring VMs in public cloud is similar to private cloud.
Do not change the Abiquo platform's tag on an Amazon instance in Amazon or you will break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo.
You can edit the network configuration of an AWS machine if it is:
Click on the Network tab to edit the network configuration.
Do not change the virtualmachine tag of an AWS instance in AWS or you will break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo.
To add a floating public IP to your VM:
A floating public IP should be displayed as shown in the following screenshot. The floating IP is not part of any Abiquo VLAN.
To remove a floating IP from your VM, power off or undeploy the VM and click the X button near the IP address.
The floating IP will still be assigned to your virtual datacenter.
Your public cloud provider may charge for a public IP that is assigned to a virtual datacenter but not in use.
When you undeploy the VM, remember to remove the floating IP after you undeploy the VM because AWS charges for floating IPs that are not in use.
To ensure that your public cloud provider does not charge you for the floating public IP, remove it from your virtual datacenter. The floating public IP will be released and you cannot add it to another machine. When you add another floating IP to your virtual datacenter and VM, there is no guarantee that it will have the same IP address.
If firewalls are offered in your datacenter and firewalls have been created in your virtual datacenter, then you can assign firewalls to your VMs.
Privilege: Assign firewall
To assign a firewall from the virtual datacenter to a VM, edit the VM and open the Firewalls tab. Mark the firewall with a tick in the Firewall policies checklist. You can add as many firewall policies as necessary, up the public cloud provider's limit. See http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_SecurityGroups.html#VPCSecurityGroups
Privilege: Assign firewall
To remove a firewall from a VM, edit the VM and open the Firewalls tab. Remove the tick beside the firewall in the Firewall policies checklist. Click Save.
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.
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.
If you have the privilege to Manage VM monitoring and it is configured in your virtual datacenter, you can enable the option to fetch metrics from the hypervisor or public cloud region.
To enable VM monitoring and metrics, work with a VM that is powered off or undeployed.
Edit the VM and go to the Monitoring tab.
Mark the fetch metrics checkbox.
Select from the available options, f or example, for AWS, you can select detailed or basic monitoring.
The functionality and list of available metrics depend on the underlying virtualization technology.
Select the individual metrics you would like to retrieve for your VM.
On the VM icon, click the Monitoring symbol to display the metrics.
The metrics panel will open.
Select the refresh buttonto update the display of a metric.
Select the filter buttonto configure the display of the metric.
Click Accept to save the values.
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.