Infrastructure

Next Page: Virtual Datacenter Statistics

In the Infrastructure view, on the Private tab, you can incorporate your compute, storage, and network resources into the Abiquo platform. You can also create allocation rules to control the use of these resources.

Compute

In Abiquo datacenters, compute resources are servers that can run one of the supported hypervisors or container servers. The Cloud Admin adds compute resources to logical groups on Abiquo racks with similar hypervisors or hardware. For a standard networking configuration, you would usually align the Abiquo rack to the top of rack network switch. The Abiquo rack is also the level where you enable High Availability, so you can align VMWare clusters with Abiquo racks.

Abiquo is a thin unintrusive management layer to the existing infrastructure and there is no impact on any VMs that are already running. The Cloud Admins can add the physical and virtual infrastructure to Abiquo in a controlled way on their own timescales. Cloud Admins can easily add hypervisors to Abiquo by entering the IP address of the hypervisor managers or the hypervisors.

Click here to show/hide the task: Create a rack

To create a rack:

Open the Infrastructure view and select Private and the datacenter name. If you are not in the Infrastructure details tab (with Servers, Network, etc.), open it by clicking the server button in the top right corner of the screen.
At the top of the DATACENTERS list, click the plus button
Enter information for "Rack"
Click Network and enter details for your switch and environment. The platform will use these settings to create a pool of VLAN tags to assign to private networks
Click "Save"

When you add hypervisor datastores to Abiquo, you can present them to the Cloud users in datastore tiers. Tiers enable you to provide multiple storage types with different performance, features and price points. They also enable cloud users to select the tier that is suitable for their requirements or their price point.

Click here to show/hide the task: Create datastore tiers

To create datastore tiers

In the Infrastructure view, click the Datastore tiers tab, and click + Add to create a datastore tier.
On the Enterprise access tab, allow all enterprises to access the tier.

Through the hypervisor, Abiquo will retrieve information about the physical machine and add the CPU and memory resources to the resource pool. As part of the physical machine configuration, the Cloud Admin will select a virtual switch that Abiquo will use to configure virtual networks, and the datastore/s that Abiquo can use when deploying new VMs.

Click here to show/hide the task: Add a physical machine

Task: Add a physical machine

Use the + button to create a new physical machine. For example, for vCenter.

Select the hosts to add to Abiquo and configure them as described here.
1. For each hypervisor host, you must enable a network interface (by assigning a Network Service Type). This is the network interface that is listening on VLANs.
2. For each hypervisor host, you must enable at least one datastore (mark the checkbox). Do not enable the vm_repository for use as a datastore.

If necessary, edit the datastore to complete the configuration, for example, on KVM you may wish to add the datastore directory, such as var/lib/virt. Repeat the process of adding the physical machine for additional hypervisor hosts. Add the datastores to a datastore tier.

The platform can import VMs that were deployed before the machine was added. You can capture these VMs and manage them with Abiquo.

Click here to show/hide the task: Capture VMs

Once a physical machine is discovered by Abiquo, customers can scan the host for existing VMs. The existing VMs that are not managed by Abiquo will be highlighted and customers will have the opportunity to capture the existing VMs and bring them under Abiquo management. This functionality allows customers to phase in the deployment of Abiquo

Create virtual datacenters for the host hypervisor type and appropriate networks for the VMs
In Infrastructure view, select the host and press the button to scan for VMs
Select a VM that is not managed by Abiquo
Click the Capture VM button.

See: Import and Capture VMs for more information. Some VMs will be prefixed with ABQ and managed by Abiquo, and some will be already running and not managed by Abiquo.

Network

In private cloud, there are two main options for Abiquo networking: SDN integrations and standard networking. Abiquo integrates with software defined networking systems including VMware NSX and OpenStack Neutron to manage private networks, firewalls and load balancers in Abiquo virtual datacenters. With standard networking Abiquo will manage the virtual networks that are provisioned with VMs. It does not integrate with network devices (e.g. switches), so the Network Admin will need to configure the switches and routers and provide a pool of VLANs that Abiquo can manage. In datacenters, Abiquo manages virtual networks of 3 distinct types: private networks, external networks, and public networks.

Private Networks

Private networks only exist within the Abiquo cloud environment. As such Abiquo can completely manage these networks and users can be allowed to create their own private networks on a self-service basis.

In standard networking, the Abiquo rack configuration defines an available pool of VLANs and Abiquo will automatically assign an unused VLAN to a new private network. Private networks enable VMs in the same virtual datacenter to communicate with each other. When SDN integrations are used, Abiquo creates the private networks in the domain of the SDN system as specified by the Admin and using the SDN technology for example VXLANs with VMware NSX. The Admin can also assign an IP on the external network as a gateway IP for the private networks, enabling external connectivity for the VDC. In public cloud regions that support networking, users can create private networks and work with features such as Availability Zones and NAT.

External Networks

In Abiquo datacenters, External networks allow communication with the external infrastructure. So the Cloud Admin must define IP ranges and VLANs that align with the switches and routers beyond the cloud environment.

The Cloud Admin assigns an external network (VLAN) to an Abiquo enterprise (cloud tenant). For example, for service providers, you can assign each customer a dedicated VLAN and provide seamless connectivity to the cloud through existing MPLS or VPN connections. And for enterprise customers, your departments (Abiquo enterprises) can connect to the corporate LAN. For a tenant and/or virtual datacenter, you can change the default private network to make an external network the default, which provides easy connectivity when you deploy a new environment. When using SDN integrations, Abiquo may manage the IP addresses of the external networks. An Unmanaged network is a type of the External network with IP addresses that are managed outside of Abiquo.

Public Network

In an Abiquo datacenter, tenants can share a public network. First tenants obtain (purchase or reserve) IPs in public networks for their virtual datacenters and then they assign them to VMs. Abiquo's accounting services track public networks, so they are ideal for providing true public IP addresses that will be charged back to an enterprise.

In public cloud, the Cloud Admin does not manage public networks. However, tenants acquire floating IPs for their virtual datacenters and assign them to their VMs as in private cloud.

Click here to show/hide the task: Create a public network

To create a public network and IPs

From the Infrastructure side, select Datacenter, Network tab, and select the "Public" sub-tab.
Click the + icon to add a VLAN
Fill in the necessary information and click Save
Create IPs as required. Click Accept
Review the list of available IPs and make unavailable any IPs that are required for administration purposes
If a specific Public IP might have been misused, it can be quarantined. A quarantined IP cannot be used by any enterprise to provision to their VMs. Mark the "Quarantine" checkbox to make an IP unavailable to enterprises in the 'PUBLIC IPS' table.

Storage

In Abiquo datacenters, Abiquo uses several different storage types.

Through the hypervisor, Abiquo supports any storage that can be used as a hypervisor datastore. So Abiquo can provision a new VM to any storage type including Fibre Channel, iSCSi, and NFS. Abiquo uses datastore tiers to offer different service levels for the user to deploy and also to create self-service VM hard disks, which are not persistent.

Abiquo uses NFS storage for its Apps Library where VM images and templates are stored within each datacenter.

Abiquo also supports integrated storage and external storage volumes, using iSCSI and NFS. Integrated storage provides the user with a complete self-service experience. The user can create their own volumes, attach those volumes to VMs or delete those volumes, without an Admin being involved. Additionally, Abiquo supports generic iSCSI volumes added by the Admin and provides a storage SDK. External storage devices can be presented to the Cloud users in storage tiers. Tiers enable you to provide multiple storage types with different performance, features and price points. They also enable cloud users to select the tier that is suitable for their requirements or their price point.

Allocation Rules

In Abiquo datacenters, allocation rules define how Abiquo will use the underlying infrastructure to deploy VMs. The allocation rules include compute load level rules where you can configure allocation or subscription of CPU and RAM, and storage load level rules for datastores. Abiquo supports compute allocation rules at the VMware cluster level and the Cloud Admin can also use features built into the underlying hypervisor technology, such as VMware's Dynamic Resource Scheduler (DRS).

Click here to show/hide the task: Create allocation rules

To create allocation rules

Select the Data Center and edit. Select the Allocation Rules tab
Add a new 'DATACENTER' rule on the right pane with the + icon. Select the Rule type such as 'Compute load level' as below. This rule can be used for oversubscription of CPU. For example, in a test system with small VM templates, you could set RAM to 100% and CPU to 400%. You can also set a storage load level rule for datastore usage.