Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »


Introduction

The Abiquo platform enables service providers and enterprises to build multicloud environments for IAAS. Abiquo is a flexible platform where you can provide controlled self-service to cloud users. And users work with an intuitive, easy-to-use interface. They can create new virtual environments by simply dragging and dropping templates or using application blueprints provided by the administrators. And you can completely whitelabel the user interface with corporate branding at the tenant level.

All of the Abiquo functions that you can perform through the GUI are also available through a RESTful API, enabling additional integration or automated configuration of the platform.

The Abiquo UI is divided into a series of views that you can access from the main menu.

The Infrastructure view provides the Cloud Admin with a summary view of the cloud infrastructure. The Statistics tab shows compute (CPU/Memory), storage and networking resources. The Cloud Admin can easily see the resources allocated to cloud users (limits in black) and the used resources (red). It is possible to allocate more resources than those that actually exist, until the users need to consume the real resources.

The resources come from the multiple cloud locations (datacenters and public cloud regions) that are listed in the Infrastructure view on the left of the GUI. The Cloud Admin is able to view and administer multiple locations from the same interface (or single pane of glass). Each location is defined by the presence of Abiquo Remote Services that manage its resources. So a “datacenter” may represent all the resources in one geographic location, or one part of a large environment that is broken down into multiple data centers. And a "public cloud region" represents resources in a public cloud provider, for example, Amazon EC2. The Abiquo datacenter or public cloud region is one level at which you can apply Abiquo control policies. Within the cloud location, the Cloud Admin can view and administer resources, such as compute, networking, and storage.


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

Customers wish to leverage existing virtualized infrastructure. Abiquo can mange a pool of IT resources (servers, networking and storage) that are in the same physical location on the same Local Area Network (LAN).

To create a new private cloud datacenter:

  1. Go to Infrastructure view, on the Private tab, and click the + button
  2. Enter the name of the datacenter and the location
    Create a datacenter adding basic details
  3. Enter the IP address of the monolithic Abiquo server, and click Duplicate IP addresses to copy the remote service locations
  4. Click the "Accept" button to use this remote services configuration for the datacenter.
    Create a datacenter and add remote services

A new Datacenter is created with all available resources managed by Abiquo.

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

Note: For OpenStack and vCloud Director, you must enter public cloud credentials in order to retrieve the public cloud regions (for example, in vCloud this is equivalent to a Provider or Org VDC).

  1. Create a new public cloud region from the + button in Infrastructure view.
  2. Enter the name for the region, select the public cloud provider and mark the checkboxes for the region(s) you wish to use. Click next.
    Create a public cloud region entering general information
  3. Enter the first digits of the IP address of the monolithic Abiquo server, select it from the dropdown list and click Duplicate IP addresses to copy remote service location, ports, and components
  4. Click the "Accept" button to use this remote services configuration for the datacenter.

Abiquo creates new public cloud region(s) with all available resources managed by Abiquo. New public cloud regions are named first with the name that the user enters, and then with this name and a suffix of _1, _2, for example, AWS, AWS_1, AWS_2, and so on.


Next section: Infrastructure

  • No labels