Abiquo 5.1

Skip to end of metadata
Go to start of metadata

Introduction

The purpose of this document is to support a technical evaluation of the Abiquo cloud platform with a structured test plan to evaluate Abiquo functionality.  This document assumes that the reader has a basic understanding, and has seen a demonstration of the Abiquo solution.

Intended Audience

This document is intended to provide Abiquo customers and evaluators the information that they require to evaluate Abiquo within their existing lab environment. The document assumes that readers are already familiar with the Virtualization, Storage and Network technologies that the Abiquo platform will manage.

Evaluation Documentation and Support

An Abiquo trial license includes the following for the trial period;

  • Access to dedicated Sales Engineers and Account Management teams
  • Abiquo software and documentation
  • Access to Abiquo support

For an overview of the Abiquo solution visit 

This document is not intended to replace the full product documentation which can be accessed online. The most up to date information can also be found on our Wiki.
http://wiki.abiquo.com

During the trial process don't hesitate to reach out to our support desk if you need assistance. The support desk can be reached at http://www.support.abiquo.com


Sample test schedule

The following represents a sample schedule for a trial of Abiquo. Estimated times are indicative only and the actual time taken for some tasks may be longer or shorter in some environments.

The following is an example schedule that allows the trial to be completed in one week or less and for the key objectives to be demonstrated during that period. The schedule assumes that all pre-requisites are in place and that dedicated technical resources familiar with the environment are available. Depending on the organization's objectives and the environment available, not all test cases will be relevant. A more detailed plan linking tasks to resources can be created in collaboration with the customer's project team.


Participants and Users in Tests

Participants

Abiquo Role

Comments

Cloud Operator

Could Admin

User with the cloud admin privileges. Default user 'admin' and password of 'xabiquo' is a cloud admin (unless changed on install)

Enterprise Admin

Enterprise Admin

No default user defined

Standard User

User

Default user for Abiquo username 'user' and default password of 'xabiquo'. Consumer of resources (your client)

Customer

n/a

Customer technical resources assigned to POC/Trial

Abiquo

n/a

Abiquo Sales Engineer or Abiquo Support



Outline Tasks for 4/5 Day Schedule of work

Schedule

Activity

Comments

Participants

Preparation

Hardware and test environment readiness

 

Customer technical resources

Preparation

All pre-requisites in place

 

Customer/Abiquo

Preparation

POC kick off meeting

 

Customer/Abiquo

Day 1

Installation and Configuration

 

Customer/Abiquo

 

Acquire hypervisor nodes

 

Cloud Operator

 

Acquire storage platform

 

Cloud Operator

 

Create IP address pools

 

Cloud Operator

 

Create logical groupings of physical resources

 

Cloud Operator

 

Create template/image repository

 

Cloud Operator

 

Download sample templates

 

Cloud Operator

Day 2

Create enterprises (customers/departments) and virtual datacenters

 

Cloud Operator

 

Delegate enterprise administration

 

Cloud Operator

 

Create enterprise users

 

Enterprise Admin

 

Create custom user roles

 

Cloud Operator

 

Define hard and soft resource limits for each enterprise

 

Cloud Operator

 

Define business rules for resource consumption

 

Cloud Operator

 

Create pricing models, cost codes and currencies

 

Cloud Operator

 

Assign cost codes to all templates

 

Cloud Operator

 

Create virtual storage volumes

 

Enterprise Admin

 

Create private VLANs

 

Enterprise Admin

 

Reserve public IPs

 

Enterprise Admin

 

Create virtual appliance

 

Enterprise Admin

 

Deploy and undeploy virtual appliance

 

Enterprise Admin

 

Configure and administer a virtual appliance

 

Enterprise Admin

Day 3

Move a virtual appliance to a different hypervisor

 

Enterprise Admin

 

Perform self-service resource consumption

 

Enterprise User

 

Validate Abiquo's co-existence with existing hypervisor management tools (e.g. VMware vCenter)

 

Cloud Operator

 

View resource consumption

 

Cloud Operator

 

Extract billing information

 

 

 

Integrate with an existing LDAP/AD user source

LDAP or AD user source required

Cloud Operator

Day 4/5 (optional use cases)

Integrate the cloud management application with existing applications (e.g. a provisioning system)

 

Cloud Operator

 

HA – Restart a VM if the host fails

 

Cloud Operator

 

Validate compatibility with VMware Distributed Virtual Switch (DVS)

VMware environments only

 

 

Validate compatibility with VMWare Distributed Resource Scheduler (DRS)

VMware environments only

 

 

Configure virtual machine cost codes

 

Cloud Operator

 

Integration with Chef

Requires Chef server (hosted or instance)

Cloud Operator

 

Create and upload a custom virtual machine

 

Customer technical resources

 

Enable and customize branding (white labeling)

 

Abiquo

 

 

 

 



The following sections describe some typical test cases that can be performed to evaluate the Abiquo solution in support of the customer business case and objectives.

Discover Physical Infrastructure for Cloud Operator

Private cloud

Use Case 1.1 - Create a datacenter

Use Case 1.1

Create a private cloud datacenter

Use Case Description

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

Pre-requisites

Abiquo installed and running.

Requires

Must be logged into Abiquo as the Cloud Operator and have network access to the resources.

Steps

1. Create a new private cloud physical datacenter from the + button in Infrastructure view.
2. Enter the name of the datacenter and the location

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.

You can create public cloud regions that will share the same remote services.

Expected results

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

Comments

 

 

 

Use Case 1.2 - Define logical racks and VLAN network requirements

Use Case 1.2

Define logical racks and VLAN network requirements

Use Case Description

Abiquo enables the Cloud Operator to group physical servers into logical racks. The cloud operator determines the groupings of physical servers. For examples, some data centers would group servers with similar specifications together and provide those resources with a certain service level to end users. Racks must be added to a physical datacenter to begin adding physical hypervisors to the physical infrastructure.

Pre-requisites

  • Abiquo management server
  • Physical datacenter created

Requires

Naming convention for racks

Steps

  1. Click on Infrastructure view and select the datacenter name
  2. 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
  3. At the top of the DATACENTERS list, click the plus button 
  4. Enter information for "Rack"
  5. Click Network and enter details for your switch and environment
  6. Click "Accept

Expected results

The rack will be available in datacenter to add hypervisors to the physical infrastructure.

Comments

 

 

Use Case 1.3 - Create datastore tiers for datastore service levels

Also in the Infrastructure view, click the Datastore tiers tab, and click + Add to create a datastore tier. 

 

Use Case 1.4 - Acquire the Physical Infrastructure

Use Case 1.4

Acquire the Physical Infrastructure

Use Case Description

Customers will use Abiquo to manage the physical infrastructure. That infrastructure needs to be acquired by Abiquo so that it can be managed and so that the resources can be consumed.

Pre-requisites

Abiquo installed and running. Physical infrastructure (e.g. hypervisors and storage) are running and user credentials are available.

Requires

Must be logged into Abiquo as the Cloud Operator and have network access to the resources.

Steps

After a datacenter has been created, enter it. Select the Infrastructure tab and click the button to add a new rack (logical machine grouping). Once that is created 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.

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.


For each hypervisor host, you must enable at least one datastore (mark the checkbox).

(minus) Do not enable the vm_repository for use as a datastore.

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

If a storage platform is being used for Abiquo managed external storage then this can also be acquired. Please review the documentation or contact your Sales Engineer for the steps to add your particular storage platform.

Expected results

Physical resources are managed by Abiquo and are available to be consumed by virtual datacenters.

Comments

The platform automatically detects clusters.

 

Use Case 1.5 - Define the data center utilization rules

Use Case 1.5

Define the Data Center Utilization rules

Use Case Description

Customers need the ability to define Utilization rules for the data center. Performance based load balancing rules will always look for a physical host with the most resources available. Progressive load balancing will continue to fill up each server with virtual machines until it reaches the percentage capacity defined by the customer. Once capacity is reached Abiquo will begin to fill the next server.

Pre-requisites

Abiquo installed and running.

Requires

Must be logged into Abiquo as the Cloud Operator and have network access to the resources

Steps

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.

Expected results

A Utilization business rule will defined for the data center

Comments

 

Use Case 1.6 - Create Public IPs for consumption by cloud tenants

Use Case 1.6

Create Public IPs for consumption by cloud tenants

Use Case Description

Abiquo uses the Public IP management function to offer Virtual Datacenter users the opportunity to use available public IPs in their virtual infrastructure

Pre-requisites

  • Virtual Datacenters
  • Public IPs or IP ranges purchased from an ISP

Requires

  • Name for Public IP Network
  • Public IP Netmask
  • Public IP Address start
  • Public IP Gateway

Steps

1. From the Infrastructure side, select Datacenter, Network tab, and select the "Public" sub-tab.
2. Click the + icon to add a VLAN.
3. Fill in the necessary information and select 'next'.

4. Create IPs as required

5. Review the list of available IPs and make unavailable any IPs that are required for administration purposes


6. 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 virtual machines. Check the "Quarantine" checkbox to make unavailable to enterprises in the 'PUBLIC IPS' table.

Expected results

Public IPs will be accessible for addition to Enterprises and Virtual Data Centers using the designated Data Center.
*Note: External networks are functionally the same as public networks but DO NOT get accounted for billing purposes. External networks can also use an external DHCP server (as Unmanaged networks) and be set as defaults for VM machines at Enterprise and VDC level. Public networks can be set as the default at virtual datacenter level.

Comments

 

Use Case 1.7 - Capture existing virtual machines and support a phased deployment

Use Case 1.7

Capture existing virtual machines and support a phased deployment

Use Case Description

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

Pre-requisites

  • Abiquo Management Server
  • Physical Datacenter, Rack and Discovered server

Requires

Existing hypervisor server with virtual machines that were not created by Abiquo.

Steps

  1. Select the host and press the scan for virtual machines
  2. Highlight a virtual machine that is not managed by Abiquo
  3. Select Capture Virtual Machine.

Expected results

Some virtual machines will be prefixed with ABQ and managed by Abiquo and some will be already running and not managed by Abiquo.

Comments

See: Import and Capture Virtual Machines

 

Use Case 1.8 - Leverage existing storage platforms for persistent virtual machines

Use Case 1.8

Leverage existing storage platforms for persistent virtual machines

Use Case Description

Abiquo is capable of leveraging your existing storage platform to make additional disk space available to virtual machines running on the enterprise's Cloud as volumes of external storage. This storage is also available for persistent virtual machine templates. Virtual machines created with a persistent system disk are available regardless of virtual machine state (deployed or undeployed).
In this example we'll attach an external storage device using the iSCSI protocol and configure the Storage Pool to make these storage features available via the self-service component. We will also assign the Storage Pool as a Tier 1 storage device.

Pre-requisites

Storage Device: Local, NFS, iSCSI, Nexenta, LVM, External Storage, (NetApp, EMC Solera)

Requires

  • Storage Manager Remote Service up and available (as detailed in prior use case)
  • Storage IP or URL
  • Port for storage
  • Associated install and configuration for storage type as detailed in "Cloud Nodes and Persistent Storage guide.pdf"

Steps

  1. After the Storage Manager Remote Service has been created and is up and available (as detailed in prior use case), a Storage Pool must be created.
  2. On the Infrastructure side, open the Storage tab, add a new storage device via the + icon
    Enter necessary fields as specified in the pre-requisites
  3. Each managed storage pool must be associated with a tier

Expected results

Once complete you'll be able to create and add volumes in the Virtual Datacenters as well as create persistent Virtual Machine templates on the Storage Device.

Comments

 

Public cloud

Use Case 1.9 - Create public cloud regions

Use Case 1.9

Create public cloud regions

Use Case Description

Customers wish to offer convenient public cloud services with the same easy user interface. Your trial Abiquo monolithic server can manage one datacenter and multiple public cloud regions.

Pre-requisites

Abiquo installed and running.

Requires

Must be logged into Abiquo as the Cloud Operator and have network access to the resources.

Steps

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.

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.

Expected results

Abiquo creates new public cloud region(s) with all available resources managed by Abiquo.

Comments

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.

 

 

Use Case 2.0 - Add public cloud credentials

Use Case 2.0

Add public cloud credentials

Use Case Description

Abiquo enables the Cloud Operator or Tenant Administrator to enter their public cloud credentials.

Pre-requisites

  • Abiquo management server
  • Abiquo public cloud region created
  • Log in as the cloud operator or the tenant administrator

Requires

Public cloud credentials, see Obtain public cloud credentials

Steps

  1. In the top right-hand corner of the screen, click on the user icon
  2. From the dropdown menu, select Edit credentials
  3. Select the cloud provider
  4. Enter the Access key ID and the Secret access key
  5. Click Add account
  6. Click Close

Expected results

The credentials will be added to the tenant's account

Comments

 


Create a Global Template Library

Private cloud

Use Case 2.1 - Create a global template repository and share approved templates

Use Case 2.1

Create a global template repository and share approved templates with virtual enterprises

Use Case Description

A Remote Repository exposes different appliances ready to download. These appliances are defined by the OVF standard. You can see a Repository Space as an index of Virtual Machine Templates. This index can be published on the Internet for public access or in the Intranet of your company for controlled and secured access. This system allows virtual machine template creators to share their templates with many Abiquo users.

Pre-requisites

Internet access

Requires

20G of space on an NFS storage

Steps

  1. On the Apps Library Tab select the data center.
    Click the + Add button on the right hand side and select Create from remote repository

  2. The Abiquo Official Repository should have been added as default (http://abiquo-repository.abiquo.com/ovfindex.xml). This is sample set of pre-built VMs templates.
  3. Select the templates and click Download to save them to the local datacenter Apps library

Expected results

Templates can be downloaded from the Remote Repository to the datacenter's local repository.

Comments

 

 

 

Use Case 2.2 - Leverage existing virtual templates by importing into the global repository

Use Case 2.2

Leverage existing virtual images by importing into the global repository

Use Case Description

Some customers have built standard Virtual Machine templates for inclusion in a global repository. These templates allow customers to enforce standards across their data centers.

Pre-requisites

An established Apps library

Requires

20G of space on an NFS storage

Steps

To upload a custom VM template:

  1. On the Apps Library Tab select the data center
    Select the option to Create from OVA (the third option in the screen capture in the previous section).
  2. Select the OVA file. Abiquo imports OVAs created in VMware. The OVA shoulld contain a single virtual system and the disk format should be compatible with Abiquo. See Template Compatibility Table
  3. After you upload the OVA, edit the template as required. Check on the Advanced tab that the Operating system is set correctly

Expected results

Template is uploaded to your Apps Library and can be used to deploy virtual machines within a virtual appliance.

Comments

Note: Your appliance manager must be correctly configured to allow disk uploads. Browser upload uses HTTP, larger disk files may require a different process.

 

Public cloud

Use Case 2.3 - Create a cache of approved public cloud templates 

Use Case 2.3

Create a cache of approved public cloud templates

Use Case Description

A public cloud provider may offer thousands of templates in each region. There are no guarantees that these templates are appropriate and safe for your users. You can create a cache with a selection of approved public cloud templates that can be made available to your users on a self-service basis.

Pre-requisites

  • Public cloud region created
  • Cloud provider credentials added

Requires

  • User logged in as Cloud Operator or Tenant Administrator
  • Provider ID of approved templates in public cloud

Steps

  1. To add a new template, first from the Apps Library view select the Public tab 
  2. Click on the name of the public cloud region
  3. In the top right-hand corner of the Templates pane, click the Import template button
  4. Enter the template ID or other criteria to identify your template as required and click Search
  5. Mouse over the retrieved template(s), which will display template details popup. Select the appropriate template and click the Import symbol


     

Expected results

Templates details can be cached in Abiquo to be made available to users on a self-service basis

Comments

 

 

You can now customize (e.g. add an icon) and share the template as required. Note that the same method is used to add Docker templates to the Abiquo template cache.

You can also export correctly prepared templates from your the Apps library to public cloud.


Create Customer Organization Hierarchy

Use Case 3.1 - Create an enterprise for a cloud tenant to consume cloud resources

Use Case 3.1

Create an enterprise for a cloud tenant to consume cloud resources

Use Case Description

In the Abiquo platform an enterprise can be created to make logical deployment resources available to cloud tenants. The following example depicts a sample enterprise hierarchy.

  • ACME Hosting {root level – corporate or Service Provider level}
    1. Local Bank {Enterprise}
    2. Wernham Hogg {Enterprise}
    3. Dundler Mifflin {Enterprise}
      ##

Pre-requisites

  • Abiquo Management Server
  • Physical Infrastructure Deployed

Requires

Enterprise Name

Steps

1. Login as SysAdmin
2. From the "Users" pane click + to add the new enterprise
3. Enter Enterprise Name in Name box (the Enterprise logo and theme are optional)

4. Click on "Datacenters" tab and select a datacenter for the enterprise to use. Move the datacenter to the Allowed Datacenters list

5. Click "Save"  

Expected results

The enterprise will be available for logins, resource allocation, and for the customer to login to via the customer portal.

Comments

The administrator can switch to use an enterprise by clicking the switch enterprise button on the list in the Home view 

 

Use Case 3.2 - Define resource allocation limits for the enterprise

Use Case 3.2

Define Resource Allocation limits for the Enterprise.

Use Case Description

The Hard and Soft Limits offer the Cloud Operator a way to limit the amount of physical resources that and Enterprise will be able to consume. This is very useful to avoid common problems in cloud platforms, such as resource over allocation or an enterprise using resources belonging to others, or even preventing DoS attacks. These limits will also help System Administrators to anticipate user needs and anticipate resource demands.
The exact meaning of these limits is:
Hard Limit: The maximum amount of virtual resources (CPU, RAM, Local Hard Disk, External Storage, Repository, VLANs, Public IPs) that an enterprise will be allowed to consume.
Soft Limit: A limit that is always less than the Hard Limit that is used to alert users. When an enterprise reaches the soft limit, an alert will be shown to users to inform that they are reaching the resource allocation limits for their enterprise.
Hard and Soft Limits are used by the Resource Scheduler in order to decide if a user can or cannot deploy a virtual appliance.

Pre-requisites

  • Abiquo Management Server
  • Enterprise created

Requires

Limits set based on business agreement with enterprise holder

Steps

1. Login as SysAdmin
2. On the users screen select a specific Enterprise
3. Select configuration button and select the "allocation limits" tab
4. Set "Soft limits" for warning and "Hard Limits" to set maximum allowable limits for use by enterprise to deploy virtual appliances/virtual machines

Expected results

The platform will create an event for administrators if the users approach the "Soft Limit" and Enterprise users will not be able to deploy virtual machines past the "Hard Limits".

Comments

 

 

Use Case 3.3 - Delegate administration of the enterprise

Use Case 3.3

Delegate Administration of the Enterprise

Use Case Description

The Enterprise Administrator can manage configurations at the enterprise level and provide access to standard users within the enterprise. Typically, this role is assigned to people who are responsible for administration of Cloud services for a specific group.

Pre-requisites

  • Abiquo Management Server
  • An Enterprise

Requires

User details including email for person who will use this account

Steps

1. Login as SysAdmin
2. Select a specific Enterprise
3. In the "Users" pane click + to add the new user
4. Select the default role "ENTERPRISE_ADMIN"

Advanced tab
5. Enter the user details

Expected results

An Enterprise Admin will be available. This user can manage template libraries and users for the enterprise.

Comments

 

 

Use Case 3.4 - Define enterprise business policy

Use Case 3.4

Define Enterprise Business Policy

Use Case Description

Business policies are used to help manage where Virtual Enterprises can deploy virtual appliances. The Policies include

  • Limits – Resource limits manage overall allocation that can be consumed by the enterprise
  • Permissions – Define what data centers the Enterprise is permitted to deploy into
  • Reservations
  • Restrictions

Pre-requisites

  • Abiquo Management Server
  • Enterprise created

Requires

Limits set based on business agreement with Enterprise holder

Steps

1. Login as SysAdmin
2. Select a specific Enterprise
3. Select edit and select "reservations"
4. Select a datacenter and RACK where a server will be reserved for this enterprise
5. Move one of the available servers to add the server to the 'reserved servers' list.


6. Log in as ANY user NOT in this enterprise (note RACK reserved servers not available).
7. Log in as ANY user in the enterprise with the reserved server.

Expected results

The reserved hardware is only available to the users in the enterprise that has been allocated the reservation of the hardware.

Comments

Note that you can also set a 'Load Level' Datacenter allocation rule to oversubscribe the resource (i.e. 200% CPU = double the amount of physical CPUs)

Reserve hardware BEFORE the enterprise deploys in the cloud




Manage Enterprise for Enterprise Administrator

Private cloud

Use Case 4.1 - Create a virtual datacenter from the resource cloud

Use Case 4.1

Create a virtual data center from the resource cloud

Use Case Description

Virtual Datacenter is an abstraction of a physical Datacenter that offers the same capabilities (such as network infrastructure, external storage system, backup, security, etc) with the added advantages of cloud computing:

  • Virtualization
  • Pay-as-you-go billing
  • Quick scalability
  • Technology and hardware abstraction.

This gives cloud users the opportunity to run their applications in a more economical and flexible way. A Virtual Datacenter offers the classical Datacenter infrastructure, as a service.
A VDC groups virtual appliances and other resources such as volumes and public IP addresses that will be attached to virtual machines within the virtual appliances

Pre-requisites

Physical infrastructure added to Abiquo

Requires

 

Steps

1. Login as the Enterprise Admin user you created earlier (Not the SysAdmin)
2. Go to "Virtual Datacenters"
3. Click on the + icon in the "Virtual Datacenters" pane
4. Fill in necessary info, select Datacenter, and Hypervisor type


Specify the virtual datacenter's name, select the physical datacenter where its applications will be deployed and the hypervisor you want to use. Please note that the hypervisor depends on the physical datacenter configuration, so select the physical datacenter first. Click OK.

5. Click on "Accept"

Expected results

A virtual datacenter for the enterprise will be available for virtual appliances to be created and deployed within.

Comments

 

Use Case 4.3 - Create virtual storage volumes

Use Case 4.2

Create Virtual Storage Volumes

Use Case Description

Storage volumes can be created and attached to a virtual machine to extend their usable disk space capacity. These volumes are persistent, so they will not be deleted when the virtual machine is destroyed.

Pre-requisites

  • Abiquo Management server
  • Enterprise
  • Storage Device attached and configured

Requires

Abiquo managed external storage
Volume name and size of volume

Steps

1. Login as the Enterprise Admin or Enterprise User (Not the SysAdmin)
2. Go to "Virtual Datacenters" pane and select a Virtual Datacenter
3. Select the "Volumes" tab
4. Click on the + icon in the "Volumes" pane
5. Choose Virtual Datacenter, size of volume, Tier and enter description

6. Click "Accept"

Expected results

Volume is now available to be attached to a virtual machine when deployed.

Comments

To create a virtual machine system disk on a persistent volume, create a persistent virtual machine template.

Use Case 4.3 - Create private VLANs

Use Case 4.3

Create Private VLANs

Use Case Description

Abiquo uses the Private IP management function to offer Virtual Datacenter users the opportunity to use different Private IP ranges and networks in their virtual infrastructure

Pre-requisites

  • Abiquo Management Server
  • Network Infrastructure

Requires

  • Name for Private IP Network
  • Private IP Netmask
  • Private IP Gateway

Steps

1. From the Virtual Datacenters, select a Datacenter and select the 'network' tab, then the 'Private' sub-tab
2. Click the + icon to add a new VLAN
3. Fill in the necessary information

4. Click "Accept"

Expected results

A specified Private IP range is now available for the specific Enterprise/Virtual Data Center

Comments

NOTE: Private IP addresses are usually created by Enterprise Admin within an enterprise. This is not a function of the System Administrator.

Use Case 4.4 - Reserve Public or External IPs

Use Case 4.4

Reserve Public or External IPs

Use Case Description

Virtual Datacenters within each enterprise has can purchase or reserve public IP addresses to be used on their virtual machines

Pre-requisites

The public/external IP addresses shown in the public/external IP list contains the IP addresses configured in the Infrastructure view.

Requires

  • Abiquo Management Server
  • Network Infrastructure
  • IP subnet and IP address range allocated for External or public consumption (external to Abiquo)
  • IP Netmask
  • IP Gateway

Steps

  1. Select the Networking tab to access Public IP management
  2. Select a Physical Datacenter
  3. Click the '+' button to reserve the selected IP addresses for use in the selected enterprise's Physical Datacenter
  4. Select the desired available IP address(es).
  5. The user will now be able to use the IP addresses when creating virtual machines in the virtual appliance creation section.

Expected results

When a user creates a VM in the virtual appliance screen and configure the VM, there are Public IPs available to use.

Comments

 

Public cloud

Use Case 4.5 - Onboard the existing virtual infrastructure from public cloud

Use Case 4.5

Onboard the existing virtual infrastructure

Use Case Description

Customers will use Abiquo to manage virtual infrastructure in the public cloud. The tenant administrator can acquire the existing virtual infrastructure so that it can be managed by Abiquo

Pre-requisites

Abiquo installed and running. Public cloud regions are created and valid public cloud credentials have been entered.

Requires

Must be logged into Abiquo as the Tenant Administrator

Steps

Go to Virtual datacenters view. Click the plus button and select synchronize from public cloud from the menu.

Select the public cloud region.

Select the virtual datacenter to synchronize from the list.

Abiquo will import this virtual infrastructure from the provider.

Expected results

Imported virtual infrastructure is now managed by Abiquo and is available to virtual datacenter users.

Comments

 

 

Changes made directly in the provider can be updated in Abiquo by clicking the synchronize button beside the virtual datacenter name in the VDC list.

Abiquo will import the following (as supported by the provider):

  • virtual datacenters
  • virtual datacenter networks
  • public IPs
  • firewalls
  • load balancers
  • virtual machines
  • templates used to create virtual machines

Use Case 4.6 - Define allocation limits for the virtual datacenter

Use Case 4.6

Define allocation limits for the virtual datacenter

Use Case Description

Tenant administrators can define allocation limits to restrict resources available to cloud users in the virtual datacenter. These allocation limits complement the limits set by cloud operators for the tenant. When users reach the soft limit, a warning message can be displayed. When users reach the hard limit, their action will be blocked. In public cloud the external storage limit is not used.

Pre-requisites

Abiquo installed and running.

Requires

Must be logged into Abiquo as the Tenant Administrator

Steps

Select the virtual datacenter and edit. Select the Allocation Rules tab.
To allow your users unlimited resources, set the limits to 0.

Expected results

A set of allocation limits will be defined for the virtual datacenter.

Comments

 

Use Case 4.7 - Obtain floating public IPs from the cloud provider

Use Case 4.7

Obtain floating public IPs for consumption by cloud users

Use Case Description

Tenant administrators can obtain public IPs from certain cloud providers and make them available to users in their enterprises. These IPs may be called floating IPs in Abiquo because they are not attached to an Abiquo network. They may be called by different names in different providers, for example, in AWS, they are called Elastic IPs. Note that some cloud providers may charge for public IPs as soon as you obtain them from the provider. As part of an evaulation, you may wish to perform this action AFTER you create a virtual machine in order to reduce costs.

Pre-requisites

  • Virtual datacenters in public cloud regions with support for floating public IPs:
    • AWS
    • Azure
  • Virtual machine created to use the public IP address

Requires

 

Steps

  1. In the Virtual datacenters list, click on the name of a virtual datacenter in public cloud
  2. Click on the public tab
  3. Click on the synchronize button to obtain any existing public IP addresses
  4. Click on the + button to obtain a new floating IP address
  5. Click on the Add to virtual datacenter link
  6. If you have created a virtual machine, then you can now edit its configuration and add the IP address. Or you can remove the IP address from the virtual datacenter and delete it from Abiquo.

Expected results

A public IP will be created and added to the virtual datacenter and virtual machine as required.

Comments

As part of an evaulation, you may wish to perform this action AFTER you create a virtual machine in order to reduce costs.

Enterprise

Use Case 4.8 - Create enterprise users

Use Case 4.8

Create Enterprise Users

Use Case Description

Enterprise Users are able to log in via the Enterprise's management console and deploy virtual resources
The enterprise User role is the one with the least privileges. This role can manage (create/modify/delete) a group's virtual infrastructure. Typically, this role is assigned to someone who uses the Cloud service each day for virtual provisioning.

Pre-requisites

  • Abiquo Management Server
  • Enterprise created

Requires

Enterprise User Name and email address

Steps

1. Login as SysAdmin or Enterprise Admin
2. Select Enterprise
3. In the "Users" pane click + to add the new user
4. Select Role "USER" and Scope "Global Scope" and fill in necessary info

Optionally restrict the user to a set of VDCs

Enter public key for remote access to VMs

Expected results

An Enterprise user is created which allows for login and deployment of virtual machines in the selected Enterprise.

Comments

 

Use Case 4.9 - Create custom user roles

Use Case 4.9

Create Custom User Roles

Use Case Description

The Abiquo installation creates 3 default roles each configured with a set of pre-defined privileges. For some deployments additional roles will be required to support the desired models for system administration.

Pre-requisites

  • Abiquo Management Server
  • Enterprise created

Requires

Enterprise User Name and email address

Steps

1. Login as SysAdmin
2. Select Users → Roles
3. Select the USER role and click the Clone button (or click + to add the new role)
4. Fill in necessary info. (External roles are not necessary at this time)

5. Save the role and select the required privileges. See Manage Roles#Privileges table

6. Create a new user and assign the new role to this user

Expected results

A Custom role is created and a user who is assigned the new role is restricted by the selected privileges.

Comments

You can also create a scope for a user. A scope is designed to restrict administrator roles to certain enterprises and datacenters.
Manage Scopes


Manage Virtual Appliances for Enterprise User 

Use Case 5.1 - Create Virtual Appliances

Use Case 5.1

Create Virtual Appliances

Use Case Description

A virtual appliance is simply a group of one or more related virtual machines that can be used to offer a service. Each virtual machine is an independently installable run-time entity comprising an operating system, applications and other application-specific data. Note that a default virtual appliance will be created in each virtual datacenter.

Pre-requisites

At least one Virtual Datacenter has been created.

Requires

 

Steps

  1. Click on the Virtual Appliances tab.
  2. Select the virtual datacenter you want to deploy a virtual appliance in
  3. Click the 'Create virtual appliance' button in the main body of the Virtual Appliances tab


  4. Click on a virtual appliance name to enter the virtual appliance editor. A virtual appliance will not do anything unless you add at least one virtual machine template to it
  5. The virtual appliance editor is divided into:
    • The Virtual Machine Templates side bar, which shows the virtual machine templates ready to be deployed
    • The Virtual Machines box where you will be able to design your virtual application and do actions with it
  6. Simply double-click a template or drag and drop it into the virtual machines box

Expected results

A virtual appliance is created based on a virtual machine template available from the Apps Library.

Comments

 

Use Case 5.2 - Deploy and undeploy a virtual appliance

Use Case 5.2

Deploy and Undeploy a Virtual Appliance

Use Case Description

Enterprise users should have the ability to manage their Virtual Appliances. The Appliances can be easily deployed and undeployed.

Pre-requisites

 

Requires

A virtual appliance has already been created

Steps

To start the virtual appliance, click the Deploy virtual appliance button in the top right-hand corner of the Virtual machines panel.

This will deploy and start the VMs in the virtual appliance.
Note: if this icon is red, then the virtual appliance is already in a deployed state.

You can easily deploy or undeploy Virtual appliances using the controls that appear when a virtual appliance is selected in the virtual datacenter view. Or by selecting the red undeploy button in the Virtual machines view.
A table containing alerts related to the Virtual Appliance is displayed.
When the Virtual appliance is deployed, the Deploy button becomes a red Undeploy button. Click this same button to undeploy the virtual appliance.

Expected results

 

Comments

You can reconfigure deployed machines (CPU, RAM, disk, network, remote access password, and so on) in the powered off state, or when powered on for ESXi if you have configured hot-add and hot-reconfigure in your template and your OS supports it.
You can power off a machine by selecting the stop or 'power button' and if you have the appropriate configuration (VM tools), you can perform a graceful shutdown. Otherwise, connect directly to the VM to perform a graceful shutdown.

To reconfigure and change settings, from the VM options menu, select Edit and modify the appropriate settings.


Convert and move VM templates

Use Case 6.1 - Move a virtual appliance between hypervisors (V2V conversion)

Use Case 6.1

Move a virtual appliance between Hypervisors (V2V conversion)

Use Case Description

The cloud platform can support multiple hypervisor technologies, perhaps with different levels of service being offered on each of them.
The V2V conversion service allows for virtual appliances to be moved between hypervisor technologies and perhaps upgraded, or downgraded between the different services being offered.

Pre-requisites

A cloud environment with two or more hypervisor types running

Requires

  • Abiquo Server
  • V2V Services in datacenter
  • Physical datacenter with at least two hypervisors running
  • Virtual datacenters each linked to different hypervisor types

Steps

  1. Go to the virtual datacenters dashboard. It defaults to the virtual appliances tab.
    Select a virtual appliance in a virtual datacenter running hypervisor type #1 Drag the virtual appliance to a second virtual datacenter running hypervisor type #2


  2. Accept to confirm the move
  3. View the second virtual datacenter to see that the virtual appliance is successfully moved and converted

Expected results

A Virtual Appliance can be moved between two virtual datacenters running different hypervisor technologies and can be deployed onto the new hypervisor

Comments

See Template Compatibility Table


Validate Cloud Application

Use Case 7.1 - Access the running virtual machine via the Abiquo platform

Use Case 7.1

Access the running virtual machine via the Abiquo platform

Use Case Description

Customers should be able to access virtual machines deployed by the cloud management application

Pre-requisites

Virtual Appliance successfully deployed

Requires

  • Network connectivity between browser and hypervisor
    • VNC console is through the hypervisor, not directly to the VM
  • VNC password set in the virtual machine 
    • Power off the VM to change the default password

Steps

1. Select the Virtual Machine
2. Click the eye icon

Expected results

A VNC window will open and the user is presented with the login to the Virtual Machine.

Comments

  • The console window is displayed using the noVNC HTML5 client

 

Use Case 7.2 - Validate co-existence with existing management tools

Use Case 7.2

Validate Co-existence with existing management tools

Use Case Description

Customers that already use hypervisor management tools such as VMware's vCenter want to ensure that the cloud management application will seamlessly coexist with the existing tools. For example if a virtual machine is moved by vMotion Abiquo will recognize the move.

Pre-requisites

  • Abiquo installed and configured
  • Existing tools to manage the hypervisor hosts. 
    • E.g. VMware vCenter managing ESX
      • vCenter credentials in abiquo.properties file

Requires

Virtual Machines running on hypervisor hosts

Steps

Perform deployment of Virtual Machines using Abiquo and Hypervisor management tools
Review the results in both the Abiquo console and the management tool.
Exact tests and the steps to perform them will depend on the deployed infrastructure

Expected results

Abiquo co-exists with the management tool with no adverse affects.

Comments

For more details of the vMotion example, see How to make VMware vMotion work with Abiquo


Cloud User Self Service

Use Case 8.1 Cloud users can access the platform on a self-service basis

Use Case 8.1

Cloud users can access the Abiquo Platform and consume physical resources on a self-service basis

Use Case Description

Customers want to use a self-service model in order to speed up the provisioning of applications/services and improve the efficiency of the IT operation

Pre-requisites

Running Abiquo Platform with enterprise and virtual datacenter created

Requires

Resources available to the enterprise (customer)

Steps

  1. Log in to the platform as an enterprise user
  2. Create a virtual appliance within an existing virtual datacenter using templates available from the apps library
  3. Deploy the virtual appliance
  4. Review the virtual appliance configuration. E.g. networking

Expected results

A customer user can deploy a virtual appliance and consume physical resources that have been made available to them.

Comments

 

 

Use Case 8.2 Cloud users can monitor their virtual machines

Use Case 8.2

Cloud users can monitor their virtual machines

Use Case Description

Users can monitor their machines and retrieve metrics

Pre-requisites

  • Abiquo monitoring server configured by systems administrator
  • Running Abiquo Platform with enterprise and virtual datacenter and virtual appliance
  • Deployed virtual machines

Requires

Monitoring privileges (by default these are assigned to the user)

Steps

  1. Log in to the platform as an enterprise user
  2. Open the configuration of a deployed virtual machine
  3. Mark the checkbox to Retrieve metrics
  4. Select the metrics you wish to retrieve
  5. Save the virtual machine configuration
  6. Open the monitoring view; the metrics should be displayed

Expected results

A customer user can retrieve and display metrics to monitor the performance of their virtual machine

Comments

 


Integration

Use Case 9.1 - Integrate the cloud management integration with a customer portal

Use Case 9.1

Integrate the cloud management application with a customer portal

Use Case Description

Hosting providers may want to integrate the Cloud Management platform with an existing system such as an existing customer portal or provisioning system. Providing customers access to the Abiquo functionality through a familiar interface

Pre-requisites

Familiarization with the Abiquo Restful API

Requires

Abiquo Cloud Management Platform
Abqiuo API documentation

Steps

Exact steps will depend on the existing application. Please read the API documentation and discuss with the Abiquo Sales Engineer

Expected results

Abiquo functionality can be integrated into an existing portal using the Restful API

Comments

The Abiquo API

 

Use Case 9.2 - Extract billing or chargeback data from the cloud platform

Use Case 9.2

Extract Billing or Chargeback data from the Cloud Platform

Use Case Description

Hosting providers offering a Cloud Service will want to charge customers based on resources that have been reserved or consumed.

Pre-requisites

Abiquo database supports Accounting/metering of system usages by default. See the Accounting document for details.
Abiquo Accounting Services Integration

Requires

Abiquo Cloud Platform with consumption data.

Steps

Contact your Abiquo Sales Engineer who can supply sample database scripts and Excel sheets to view accounting data. Alternatively you can create or use Abiquo 'billing connector' to extract this data;
Abiquo Billing Integration

Expected results

Accounting data can be extracted from Abiquo and viewed in Excel (csv) or/and imported to an existing billing system.

Comments

Abiquo Billing Integration

 

Use Case 9.3 - Integrate the cloud platform with an existing LDAP/AD or OpenID user source

Use Case 9.3

Integrate the Cloud Platform with an existing LDAP/AD or OpenID user source

Use Case Description

An LDAP or AD user source may already exist and will be the preferred repository for user account of the Cloud Platform. The Cloud Platform will be able to authenticate against the LDAP/AD user source

Pre-requisites

An existing LDAP or AD user source and an account that is able to logon and view user data

Requires

LDAP directory information including

  • Hostname/IP of directory server
  • Server port
  • Base DN of the user store
  • User DN Pattern
  • LDAP attribute that will map to Abiquo Enterprise (e.g. Company or Department).

Steps

  1. Configure the Abiquo server to use LDAP authentication. Please review the Wiki documentation as this requires manual editing of the config file.
  2. Assign the LDAP groups or OpenID groups to User roles as external roles. A user in matching groups will be assigned the Abiquo Role
  3. Logon to Abiquo using the credentials of an LDAP user in the Abiquo group.

Expected results

A user can logon to Abiquo using the credentials that already exist in the Abiquo/LDAP source.

Comments

LDAP and Active Directory Integration

Abiquo OpenID Connect Integration 


Optional Use Cases

This section contains some advanced or optional use cases that may not always be relevant when running an evaluation of a Cloud Management Platform. Whether they are relevant will depend on the overall platform requirements and the existing technology stack that will support the cloud.

Use Case 10.1 - HA - restart a VM if the host fails

Use Case 10.1

HA – Restart a VM if the host fails

Use Case Description

Hosting providers may want to offer a simple and predictable HA across multiple hypervisors.
Abiquo HA will move a VM from a failed host, to another host in the same Rack running the same Hypervisor.

Pre-requisites

Hypervisor hosts must have the Intelligent Platform Management Interface (IPMI). Hypervisor hosts must use a shared storage datastore.

Requires

Abiquo Cloud Management Platform
Hypervisor host IPMI information

Steps

  1. The Abiquo Rack must be enabled for HA


    Modify the physical Server configuration to add the IPMI data

  2. Deploy a virtual appliance onto the HA enabled Rack. For testing purposes it may be advisable to disconnect some of the rack servers to ensure that the virtual appliance is deployed to a specific physical server
  3. When the virtual appliance is deployed power on the remaining rack servers
  4. Simulate a failure of the host server. i.e. so that it cannot be contacted using IPMI
  5. The cloud platform will detect the failed host and restart the virtual appliance on a new host in the rack

Expected results

A Virtual Appliance is restarted on a new host (in the same rack with the same hypervisor) if the original host fails. The failed host will be marked as Disabled by HA until there is manual intervention.

Comments

See Configure HA for VMs

Use Case 10.2 - Configure the cloud platform to use VMware's Distributed Virtual Switch

Use Case 10.2

Configure the Cloud Platform to use VMWare's Distributed Virtual Switch (DVS)

Use Case Description

In VM centric environments there may be a number of reasons why the Distributed Virtual Switch is the preferred virtual switch on the hypervisor. It should be possible for the Cloud Management platform to support DVS

Pre-requisites

VMWare deployment with licensing and configuration to support Distributed Virtual Switch

Requires

vCenter credentials and vCenter to be managed by Abiquo

Steps

  1. Create a DVS in vSphere
  2. Add the vCenter and select an ESXi host to add to the physical datacenter and select the DVS switch as the virtual switch for the host
  3. Deploy a virtual appliance to the ESXi host

Expected results

The VMWare Distributed Virtual Switch can be supported by the Cloud Platform. Virtual Appliances can be deployed to VMWare hosts and can use the DVS.

Comments

How to configure the Distributed Virtual Switch feature for use in Abiquo.

You can also configure the load sharing mechanism and the maximum size of the portgroup in the /opt/abiquo/config/abiquo.properties file on the Remote Services. See Abiquo Configuration Properties#dvsandvcenter

Use Case 10.3 - Configure Virtual Machine Template Cost Codes

Use Case 10.3

Configure Virtual Machine Template Cost Codes

Use Case Description

Hosting providers may need to track the licenses used by Virtual Machines (e.g. Microsoft Windows licensing), or may wish to offer Cloud services based on a per VM pricing model.

Pre-requisites

N/A

Requires

A working Cloud Management platform and populated Apps library.

Steps

  1. Create COST codes in the Pricing view and optionally a pricing model and assign it to your enterprise.
  2. Configure a VM image in the Apps Library and open the Advanced tab
  3. From the drop down select the relevant Cost code for the VM
  4. This code can be used to track the VM in the Abiquo database either for licensing or charge back.

Expected results

A virtual image can be tracked for licensing or chargeback purposes.

Comments

Pricing View

 

Use Case 10.4 - Users can run collectd plugin to push custom metrics

Use Case 10.4

Use collectd plugin to push custom metrics

Use Case Description

Users may wish to view custom performance data for a virtual machine. Users can install and configure collectd to gather this data. Users can then install the Abiquo collectd plugin to push the data to the Abiquo API. You can provide VM templates with collectd and the Abiquo collectd plugin already installed to your cloud users

Pre-requisites

  • Deployed virtual machine(s)
  • User has added collectd as an OAuth application in Abiquo. See Authentication
  • Following the instructions at Use collectd plugin for custom metrics
    • Collectd is installed and running on the virtual machine(s)
    • Abiquo collectd plugin is installed and running on the virtual machine(s).

Requires

Privilege allowing the user to push own metrics must be assigned to the collectd OAuth application

Steps

  1. User should configure collectd to gather the metrics they wish to display in Abiquo
    • By default, all collectd metrics will be pushed by the Abiquo plugin
  2. Open the virtual machine configuration
  3. Click Retrieve metrics
  4. Open the monitoring view for the virtual machine or virtual appliance

Expected results

The user should be able to view the metrics gathered by collectd in Abiquo

Comments

 


Use Load Balancers

This use case describes a basic load balancing setup for you to test load balancers in public or private cloud. It contains three secondary use cases:

  1. Create security group
  2. Create web servers
  3. Add load balancer
  4. Retrieve index files from web servers

Use Case 1a.1 - Create security groups

Use Case 1a.1

Create security group

Use Case Description

Abiquo tenant administrators can create firewalls that are security groups, in public cloud (e.g. AWS) or private cloud (using the OpenStack Neutron integration)

Pre-requisites

  • Virtual Datacenter
    • In public cloud this can be onboarded and synchronized
  • Private cloud
    • Abiquo OpenStack Neutron integration or other firewall and load balancer integration
    • Devices created for the enterprise in the cloud location
  • Public cloud
    • Credentials for public cloud provider with firewall support, for example, AWS

Requires

  • Logged in as cloud admin using this enterprise, or tenant admin

Steps

  1. Open the Network tab for the VDC at the Firewalls page. Synchronize firewalls by clicking the synchronize button  in the top right-hand corner of the page. Abiquo should load the default security group that will allow all outbound traffic
  2. Click the + button and enter firewall general information
  3. Click the synchronize button to synchronize firewall rules. If there is no rule to allow all outbound traffic, you will need to create one.
  4. Click the pencil edit button to enter firewall rules, for example, for a VM

    1. incoming SSH - in the Sources field, replace 0.0.0.0/0 with your IP address

    2. incoming HTTP - change port range to 8000

    3. all outbound traffic

  5. After you enter each firewall rule and click Add. When you have added all rules, click Save.


Expected results

Each firewall is created with the appropriate security group policies. For the load balancer, you may wish to allow See Manage Firewalls

Comments

This step is not required for Rackspace

 

Use Case 1a.2 - Create web servers

Use Case 1a.2

Create web servers

Use Case Description

Create two basic web servers that will be load balanced

Pre-requisites

  • Virtual Datacenter  
    • In public cloud this can be onboarded; All public cloud virtual datacenters must be synchronized
  • Private cloud
    • Security group (firewall) if using Abiquo OpenStack Neutron integration or other firewall and load balancer integration
  • Public cloud
    • Security group (firewall) if using public cloud provider with firewall support, for example, AWS

Requires

  • Linux template added to the Abiquo Apps library
  • SSH public key added to Abiquo user account
  • Prepurchase of two public IP addresses

Steps

  1. Use a Linux template to create two virtual machines (AWS instances)

  2. Assign a private IP to each virtual machine that is in the same availability zone (determined by private network)

  3. Assign a public IP to each virtual machine

  4. If your cloud provider supports firewalls, assign the firewall you created earlier to the virtual machine

  5. Deploy the virtual machine

  6. Log in using SSH and perform the following actions on both instances:

    echo "Displaying content from machine 1" > index.html 
    python -mSimpleHTTPServer

    For machine 2, change the text string to "Displaying content from machine 2"

Expected results

This command will start a HTTP server listening on port 8000

Comments

 

Use Case 1a.2 - Create load balancer

Use Case 1a.2

Create load balancer

Use Case Description

Abiquo can create load balancers in public cloud providers such as AWS and Rackspace (and also in private cloud (using OpenStack Neutron))

Pre-requisites

Public cloud credentials added. Where appropriate (OSN and AWS) firewalls created, firewall rules created for SSH and the appropriate loadbalancer protocol. Firewalls synchronized.

Requires

Existing virtual datacenter, either newly created or synchronized

Steps

  1. Open the Network tab for the VDC at the Load Balancers page. Synchronize any existing load balancers in your provider by clicking the synchronize button  in the top right-hand corner of the page
  2. Click the + button and create a load balancer:

    1. General Info tab: enter name, select subnet, algorithm ROUND ROBIN, select public address --> An automatically created public address

    2. Routing rules: add a routing rule with HTTP and port 8000 - 

    3. Health check: - name, HTTP, 8000, Path: /index.html, interval (sec) e.g. 30, timeout (sec) e.g. 5 and attempts e.g. 3

    4. Select the firewall you created earlier 

    5. Nodes: Add both instances

Expected results

Once complete you'll be able to go to the load balancer's public IP address and retrieve the index files from the web servers.

Comments 

 

 

Use Case 1a.4 - Retrieve index files from web servers

To retrieve the files from your web servers, open your browser and enter the public IP address of the load balancer with the port and /index.html.

Reload the page to retrieve the index file from the other web server.


Create hybrid cloud

Use Case 1a.1 - Create public cloud regions

Use Case 1a.1

Create public cloud regions

Use Case Description

Customers wish to offer convenient public cloud services with the same easy user interface. In addition to local datacenters, Abiquo can manage public cloud resources

Pre-requisites

Abiquo installed and running.

Requires

Must be logged into Abiquo as the Cloud Operator and have network access to the resources.

Steps

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.

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.

Expected results

Abiquo creates new public cloud region(s) with all available resources managed by Abiquo.

Comments

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.

 

 

Use Case 1a.2 - Add public cloud credentials

Use Case 1a.2

Add public cloud credentials

Use Case Description

Abiquo enables the Tenant Administrator to enter their public cloud credentials.

Pre-requisites

  • Abiquo management server
  • Abiquo public cloud region created
  • Log in as the cloud operator or the tenant administrator

Requires

Public cloud credentials.

See:

 

Steps

  1. In the top right-hand corner of the screen, click on the user icon.
  2. From the dropdown menu, select Edit credentials
  3. Select the cloud provider
  4. Enter the Access key ID and the Secret access key
  5. Click Add account
  6. Click Close

Expected results

The credentials will be added to the tenant's account

Comments

 

 

 

Use Case 1a.3 - Onboard the existing virtual infrastructure

Use Case 1a.3

Onboard the existing virtual infrastructure

Use Case Description

Customers will use Abiquo to manage virtual infrastructure in the public cloud. The cloud operator or tenant administrator can acquire the existing virtual infrastructure so that it can be managed by Abiquo

Pre-requisites

Abiquo installed and running. Public cloud regions are created and valid public cloud credentials have been entered.

Requires

Must be logged into Abiquo as the Cloud Operator or Tenant Administrator.

Steps

Go to Virtual datacenters view. Click the plus button and select synchronize from public cloud from the dropdown menu.

Select the public cloud region.

Select the virtual datacenter to synchronize from the list.

Abiquo will import this virtual infrastructure from the provider.

Expected results

Imported virtual infrastructure is now managed by Abiquo and is available to virtual datacenter users.

Comments

 

 

Changes made directly in the provider can be updated in Abiquo by clicking the synchronize button beside the virtual datacenter name in the VDC list.

Abiquo will import the following (as supported by the provider):

  • virtual datacenters
  • virtual datacenter networks
  • public IPs
  • firewalls
  • load balancers
  • virtual machines
  • templates used to create virtual machines

 

Use Case 1a.4 - Define allocation limits for the virtual datacenter

Use Case 1a.4

Define allocation limits for the virtual datacenter

Use Case Description

Tenant administrators can define allocation limits to restrict resources available to cloud users in the virtual datacenter. These allocation limits complement the limits set by cloud operators for the tenant.

Pre-requisites

Abiquo installed and running.

Requires

Must be logged into Abiquo as the Cloud Operator or the Tenant Administrator

Steps

When creating the VDC, enter Allocation limits

Expected results

An allocation limit will be defined for the virtual datacenter

Comments

Users should see a popup as they exceed the soft limit and will be prevented from surpassing the hard limit.

 

Use Case 1a.5 - Obtain Public IPs for consumption by cloud users

Use Case 1a.5

Create Public IPs for consumption by cloud tenants

Use Case Description

Tenant administrators can obtain public IPs from the cloud provider and make them available to users in their enterprises.

Pre-requisites

  • Virtual Datacenter created and synchronized in public cloud
  • Public cloud provider with public IP support, for example, AWS with Elastic IPs or Azure

Requires

  • Public IPs available in user account
  • Logged in as cloud admin using this enterprise, or tenant admin

Steps

1.In the virtual datacenter, go to the network tab and open the Public page. Synchronize public IPs.


2. Click the + button and add a public IP. Then click Add to VDC.

Expected results

The public IP is now ready for adding to a virtual machine

Comments

Check how your cloud provider charges for public IPs. For example, they may charge for public IPs when they are not attached to deployed virtual machines.

See Manage Public Cloud Networks

Use Case 1a.6 - Create security groups

Use Case 1a.6

Create security groups

Use Case Description

Abiquo tenant administrators can create firewalls (security groups) in public cloud providers that support them

Pre-requisites

  • Virtual Datacenter created and synchronized in public cloud
  • Public cloud provider with firewall support, for example, AWS

Requires

  • Logged in as cloud admin using this enterprise, or tenant admin

Steps

  1. Select the location or the virtual datacenter and click the synchronize button in the top right-hand corner of the page
  2. Click the + button and enter firewall general information
  3. Click the synchronize button to synchronize firewall rules. You will probably see a default rule to allow all outbound traffic.
  4. Click the pencil edit button to edit firewall rules. Enter firewall rules, for example, to allow SSH


Expected results

A firewall is created

Comments

See Manage Firewalls

 

Use Case 1a.7 - Create basic load balancer

Use Case 1a.7

Create load balancer

Use Case Description

Abiquo tenant administrators can create load balancers in public cloud providers that support them

Pre-requisites

  • Virtual Datacenter created and synchronized in public cloud
  • Public cloud provider with load balancer support, for example, AWS, RackSpace, OpenStack with Neutron integration

Requires

  • Logged in as cloud admin using this enterprise, or tenant admin

Steps

  1. Select the location or the virtual datacenter and synchronize (or synchronize the individual elements: firewalls (where applicable) and load balancers).
  2. Click the + button and enter load balancer general information
  3. Create routing rules
  4. Enter a health check if required - AWS will automatically create one if you do not enter one
  5. Assign a firewall if required - Rackspace will automatically allow traffic to the appropriate load balancer ports
  6. Assign nodes
  7. Click Save

Expected results

A load balancer is created 

Comments

See Manage Load Balancers

 

Use Case 1a.8 - Export a virtual machine template from private datacenter to public cloud

Use Case 1a.8

Export a virtual machine template from a private datacenter to public cloud (or another private cloud datacenter)

Use Case Description

The cloud platform can support multiple datacenters and public cloud regions, with different technologies and service levels.
The template mobility feature enables virtual machine templates to be moved between datacenters and public cloud regions.

Pre-requisites

A cloud environment with a datacenter plus a public cloud region (or another

Requires

  • Abiquo Server
  • V2V Services in datacenter (for conversion)
  • Two private cloud datacenters or one private cloud datacenter and a public cloud region
    • Check tenant is allowed to use the physical datacenter and the public cloud region
    • For public cloud region, you will need a compatible template (see VM Template Mobility)

Steps

  1. Go to the Apps library on the private datacenter templates tab.
    Select a compatible template and from the options menu, select Export
  2. Select the provider type (Public or Private) and for public cloud, select the Provider and Region. Click Next
  3. Select the disk(s). For public cloud, you can only select one system disk
  4. Click Export to continue. The export may take some time.
  5. Open the Apps library in the new datacenter or public cloud region to check that the template is successfully copied and converted

Expected results

A compatible VM template can be exported (copied) to another private cloud datacenter or a public cloud region

Comments

See VM Template Mobility


Create persistent external storage

These use cases work with persistent external storage, which is optional in a trial platform.

Use Case S.1 - Leverage existing storage platforms for persistent virtual machines

Use Case S.1

Leverage existing storage platforms for persistent virtual machines

Use Case Description

Abiquo is capable of leveraging your existing storage platform to make additional disk space available to virtual machines running on the enterprise's Cloud as volumes of external storage. This storage is also available for persistent virtual machine templates. Virtual machines created with a persistent system disk are available regardless of virtual machine state (deployed or undeployed).
In this example we'll attach an external storage device using the iSCSI protocol and configure the Storage Pool to make these storage features available via the self-service component. We will also assign the Storage Pool as a Tier 1 storage device.

Pre-requisites

Storage Device: Local, NFS, iSCSI, Nexenta, LVM, External Storage, (NetApp, EMC Solera)

Requires

  • Storage Manager Remote Service up and available (as detailed in prior use case)
  • Storage IP or URL
  • Port for storage
  • Associated install and configuration for storage type as detailed in "Cloud Nodes and Persistent Storage guide.pdf"

Steps

  1. Log in as the Cloud Administrator
  2. In the Infrastructure view, open the Storage tab, add a new storage device via the + icon
    Enter necessary fields as specified in the pre-requisites
  3. Each managed storage pool must be associated with a tier to define the storage service level

Expected results

Once complete you'll be able to create and add volumes in the Virtual Datacenters as well as create persistent Virtual Machine templates on the Storage Device.

Comments

 

 

Use Case S.2 - Create virtual storage volumes

Use Case S.2

Create Virtual Storage Volumes

Use Case Description

Storage volumes can be created and attached to a virtual machine to extend their usable disk space capacity. These volumes are persistent, so they will not be deleted when the virtual machine is destroyed.

Pre-requisites

  • Abiquo Management server
  • Enterprise
  • Storage Device attached and configured

Requires

Abiquo managed external storage
Volume name and size of volume

Steps

1. Log in as the Enterprise Admin or Enterprise User (Not the SysAdmin)
2. Go to "Virtual Datacenters" pane and select a Virtual Datacenter
3. Select the "Volumes" tab
4. Click on the + icon in the "Volumes" pane
5. Choose Virtual Datacenter, size of volume, Tier and enter description

6. Click "Accept"

Expected results

Volume is now available to be attached to a virtual machine when deployed.

Comments

To create a virtual machine system disk on a persistent volume, create a persistent virtual machine template.