Solution Evaluation Criteria
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:
- Enterprises: https://www.abiquo.com/enterprise-cloud-management/
- Service Providers: https://www.abiquo.com/cloud-managed-service-providers/
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: https://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 Platform and Customer Success Team engineer |
Outline Tasks for 5+ Days Schedule of work
Schedule | Activity | 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 |
Installation and configuration | Customer/Abiquo | |
Day 1 | Discover physical infrastructure for cloud operator | Cloud Operator |
| Create a datacenter | Cloud Operator |
| Define logical racks and VLAN network requirements | Cloud Operator |
| Create datastore tiers for datastore service levels | Cloud Operator |
| Acquire the physical infrastructure | Cloud Operator |
| Define the data center utilization rules | Cloud Operator |
Create Public IPs for consumption by cloud tenants | Cloud Operator | |
| Capture existing VMs and support a phased deployment | Cloud Operator |
| Create public cloud regions | Cloud Operator |
| Add public cloud credentials | Cloud Operator |
Day 2 | Create a global catalogue for VM templates and blueprints | Cloud Operator |
| Create a global service catalogue as a template repository | Cloud Operator |
| Leverage existing VM templates by importing into the catalogue | Cloud Operator |
| Create a cache of approved public cloud templates | Cloud Operator |
| Create customer organization hierarchy | Cloud Operator |
| Create a reseller and an enterprise for a cloud tenant to consume cloud resources | Cloud Operator |
| Define resource allocation limits for the enterprise | Cloud Operator |
| Delegate administration of an enterprise | Cloud Operator |
| Define enterprise business policy | Cloud Operator |
Day 3 | Manage Enterprise for Enterprise Administrator | Enterprise Admin |
Create a virtual datacenter from the resource cloud | Enterprise Admin | |
| Create private networks | Enterprise Admin |
| Reserve Public or External IPs | Enterprise Admin |
| Onboard the existing virtual infrastructure from public cloud | Enterprise Admin |
| Define allocation limits for the virtual datacenter | Enterprise Admin |
| Obtain floating public IPs from the cloud provider | Enterprise Admin |
Create enterprise users | Enterprise Admin | |
| Create custom user roles | Cloud Operator |
| Manage Virtual Appliances for Enterprise User | Enterprise Admin / Standard User |
| Create Virtual Appliances | Enterprise Admin / Standard User |
| Deploy and undeploy a virtual appliance | Enteprise Admin / Standard User |
| Reconfigure a VM to add network and storage | Enterprise Admin / Standard User |
Day 4 | Additional public cloud use cases | Cloud Operator |
Create virtual storage volumes in public cloud | Cloud Operator | |
| Export a virtual machine template from private datacenter to public cloud | Cloud Operator |
Validate Cloud Application | Cloud Operator | |
Access the running virtual machine via the Abiquo platform | Cloud Operator | |
Validate co-existence with existing management tools | Cloud Operator | |
Cloud User Self Service | Cloud User | |
Cloud users can access the platform on a self-service basis | Cloud User | |
Cloud users can monitor their virtual machines | Cloud User | |
Day 5+ (optional) | Integration | Cloud Operator |
Integrate the cloud management integration with a customer portal | Cloud Operator | |
Extract billing or chargeback data from the cloud platform | Cloud Operator | |
Integrate the cloud platform with an existing LDAP/AD or OpenID user source | Cloud Operator | |
Advanced use cases | Cloud Operator | |
Display provider billing data on dashboard | Cloud Operator | |
Configure VM template cost codes | Cloud Operator | |
Users can run collectd plugin to push custom metrics | Cloud User | |
Use load balancers | Enterprise Admin | |
Create security groups | Enterprise Admin | |
Create web servers | Enterprise Admin | |
Create load balancer | Enterprise Admin | |
Retrieve index files from web servers | Enterprise Admin |
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.
Use cases
Discover physical infrastructure for cloud operator
Use Case 1.1 - Create a private cloud datacenter
Description | Customers wish to leverage existing virtualized infrastructure. Abiquo can manage a pool of IT resources (servers, networking, etc.) that are in the same physical location in 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. |
Expected results | A new Abiquo datacenter is created with resources managed by Abiquo. |
Comments | Note: You can create public cloud regions that will share the same remote services. |
Use Case 1.1 - Steps to create a private cloud datacenter
To create a new private cloud datacenter:
- Go to Infrastructure view
- Go to the Private tab, click the + add button
- Enter the Name of the datacenter and the Location. Click Next
- Enter the IP address of the monolithic Abiquo server, and click Duplicate IP addresses to copy the remote service locations
- Click Accept to use this remote services configuration for the datacenter.
Use Case 1.2 - Define logical racks and VLAN network requirements
Use Case 1.2 | Define logical racks and VLAN network requirements |
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 |
|
Requires | Naming convention for racks and network tag range |
Steps | To create a rack:
|
Expected results | The rack will be available in the datacenter to add hypervisors to the physical infrastructure. |
Comments |
|
Use Case 1.3 - Create datastore tiers for datastore service levels
Use Case 1.3 | Create datastore tiers for datastore service levels |
Description | Create storage service levels to provide datastore storage to users. You can limit and price storage by service levels by enterprise, even across different datacenters, in which case the tiers will be automatically grouped by name into Abstract datastore tiers. |
Pre-requisites |
|
Requires | |
Steps | To create datastore tiers
|
Expected results | When you add your hypervisors, you can add their datastores to the appropriate service levels. |
Comments | See Manage Datastore Service Levels with Datastore Tiers and Abstract datastore tiers for storage service levels |
Use Case 1.4 - Acquire the physical infrastructure
Use Case 1.4 | Acquire the physical infrastructure |
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) is running and user credentials are available. |
Requires | Must be logged into Abiquo as the Cloud Operator and have network access to the resources. |
Steps | To add a physical machine (host):
Repeat the process of adding the physical machine for additional hypervisor hosts. Add the datastores to a datastore tier. |
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 |
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 | To create allocation rules
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 |
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 |
|
Requires |
|
Steps | To create a public network and IPs
|
Expected results | Users of the datacenter will be able to obtain public IPs for their virtual datacenters. |
Comments |
Use Case 1.7 - Capture existing VMs and support a phased deployment
Use Case 1.7 | Capture existing VMs and support a phased deployment |
Description | Abiquo customers can leverage existing hardware and existing VMs. Abiquo allows customers to phase in the deployment. After you add a physial machine to Abiquo, you can scan it for existing VMs. Abiquo highlights existing VMs that it does not manage with a warning symbol () and you can later capture these VMs to manage them with Abiquo. This functionality allows customers to phase in the deployment of Abiquo |
Pre-requisites |
|
Requires | Existing hypervisor server with VMs that were not created by Abiquo. |
Steps |
See: Import and Capture Virtual Machines for more information. |
Expected results | When you capture a VM to add it to Abiquo, it is almost identical to a VM that you can create in Abiquo. You can also save a copy of the VM disks as a VM template in the Catalogue. This is called an Instance template, and it can be useful if you wish to destroy and recreate the VM from the initial template. |
Comments |
Use Case 1.8 - Create public cloud regions
Use Case 1.8 | Create public cloud regions |
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 | To create a new public cloud region
|
Expected results | Abiquo creates new public cloud region(s) and resources can 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 1.9 - Add public cloud credentials
Use Case 1.9 | Add public cloud credentials |
Description | Abiquo enables the Cloud Operator or Tenant Administrator to enter their public cloud credentials. |
Pre-requisites |
|
Requires | Public cloud credentials, see Obtain public cloud credentials |
Steps | To add credentials for the current enterprise:
|
Expected results | The credentials will be added to the tenant's account |
Comments |
|
Create a Global Catalogue for templates and blueprints
Use Case 2.1 - Create a global service catalogue with a remote template repository
Use Case 2.1 | Create a global service catalogue with a remote template repository |
Description | A Remote Template Repository can provide VM templates that are ready to download. These VM templates use the OVF standard. A Remote Template Repository contains an index of VM Templates. This index can be published on the Internet for public access or on the Intranet of your company for controlled and secured access. This system allows VM template creators to share their templates with many Abiquo users. |
Pre-requisites | Internet access |
Requires | 20G of space on an NFS storage |
Steps | Abiquo supplies some sample templates in a Remote Repository hosted on Amazon S3. You can download some of these templates for testing.
Note that by default the Cloud Admin has the privilege to Manage repository (to add and delete remote repositories) and Admins have access to the Apps library (Catalogue) and the privilege to Download VM templates from remote repository. |
Expected results | Templates can be downloaded from the Remote Repository to the datacenter's local repository. |
Comments | There are many ways to make VM templates available to users in the Apps library (Catalogue). See Use Case 2.2. |
Use Case 2.2 - Leverage existing VM templates by importing into the catalogue
Use Case 2.2 | Leverage existing VM templates by importing into the catalogue |
Description | Some customers have built standard VM templates for inclusion in a global catalogue. These templates allow customers to enforce standards across their datacenters. |
Pre-requisites | An established Apps library (Catalogue). |
Requires | 20 GB of space on the NFS repository storage. Abiquo imports OVAs created in VMware. The OVA should contain a single virtual system and the disk format should be compatible with Abiquo. See Template Compatibility Table |
Steps | To upload a custom VM template:
|
Expected results | The template will be uploaded to your Apps library (Catalogue) and you can use it to deploy VMs within a virtual appliance.
|
Comments | For more details about how to add templates, see Add Virtual Machine Templates to Abiquo |
Use Case 2.3 - Create a cache of approved VM templates in public cloud
Use Case 2.3 | Create a cache of approved VM templates in public cloud |
Description | A public cloud provider may offer thousands of Vm templates in each region. There are no guarantees that these VM templates are appropriate and safe for your users. You can create a cache with a selection of approved VM templates that can be made available to your users on a self-service basis. |
Pre-requisites |
|
Requires |
|
Steps | To import a template from a public cloud region into the platform's template cache, do the following steps:
|
Expected results | Abiquo caches the details of the VM Templates to make them available to users on a self-service basis |
Comments
| You can now customize (e.g. add an icon) and share the template as required. You can also export correctly prepared VM templates from your the Apps library to public cloud. |
Create customer organization hierarchy
Use Case 3.1 - Create a reseller and an enterprise for a cloud tenant to consume cloud resources
Use Case 3.1 | Create a reseller and an enterprise for a cloud tenant to consume cloud resources |
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.
You can manage reseller customers and their credentials in a tenant hierarchy. Your customers will be able to access their billing data on the Dashboard. |
Pre-requisites |
|
Requires | Enterprise Name |
Steps | To define a basic enterprise hierarchy, first define a reseller enterprise, and a reseller scope.
Then create a customer of your reseller:
|
Expected results | After you create users, the enterprises 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. See Abiquo Cloud Reseller Guide |
Use Case 3.2 - Define resource allocation limits for an enterprise
Use Case 3.2 | Define resource allocation limits for an enterprise |
Description | The hard and soft limits offer the Cloud Operator a way to limit the amount of physical resources that an 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.
Hard and Soft Limits are used by the Resource Scheduler in order to decide if a user can deploy a virtual appliance or not. |
Pre-requisites |
|
Requires | Limits set based on business agreement with enterprise holder |
Steps | To set limits based on the business agreement with the enterprise holder: The platform will display a warning when the tenant reaches a Soft limit and enterprise users will not be able to deploy VMs after the tenant reaches the Hard limits. You can create an integration with the event streaming API to perform additional actions when tenants reach either limit. An example of a basic integration is an event notifier. |
Expected results | The platform will create an event for administrators if the users approach their Soft Limit and enterprise users will not be able to deploy VMs past the Hard Limits. |
Comments |
|
Use Case 3.3 - Delegate administration of an enterprise
Use Case 3.3 | Delegate administration of an enterprise |
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 |
|
Requires | User details including email for the person who will use this account |
Steps | To create an Enterprise Admin user do these steps:
|
Expected results | An Enterprise Admin will be available. This user can manage template libraries and users for the enterprise. To enable the user to access more Abiquo features, you may wish to clone the Enterprise Admin role and add more privileges. See Manage Roles |
Comments |
|
Use Case 3.4 - Define enterprise business policy
Use Case 3.4 | Define enterprise business policy |
Description | Business policies are used to help manage where enterprise tenants can deploy. The policies include
|
Pre-requisites |
|
Requires | Limits set based on business agreement with Enterprise holder |
Steps | To set limits based on the business agreement with the Enterprise holder
|
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. You can also restrict users by role for specific providers or virtual datacenters. E.g. allow read only access to AWS. See Control access with VDC roles |
Manage enterprise for enterprise administrator
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 |
Description | A 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:
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. Note: you may choose to bill your customers by virtual datacenter, and as such, you may prefer that your administrators create the virtual datacenters for your customers, or automate their creation. |
Pre-requisites | Physical infrastructure added to Abiquo |
Requires |
|
Steps | To create a virtual datacenter:
Note: To create a virtual datacenter for another cloud tenant, you will need to switch to that tenant first in Home view or Users view. |
Expected results | A virtual datacenter for the enterprise will be available for virtual appliances to be created and deployed within. |
Comments | Abiquo gives you a lot of control at VDC level, for example:
|
Use Case 4.3 - Create private networks
Use Case 4.3 | Create private networks |
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 |
|
Requires |
|
Steps | 1. From V. Datacenters, select a virtual datacenter and select the Network tab, then the Private sub-tab |
Expected results | A specified private IP range is now available for the specific enterprise/virtual datacenter |
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 IPs or use external IPs
Use Case 4.4 | Reserve public IPs or use external IPs |
Description | Virtual datacenters within each enterprise has can purchase or reserve public IP addresses to be used on their VMs. External IPs can be made available to the enterprise without the need for users to reserve them. |
Pre-requisites | The public/external IP addresses shown in the public/external IP list contains the IP addresses configured in the Infrastructure view. The administrator must add an existing network (with its tag) to Abiquo. See Manage Public Networks and Manage External Networks. |
Requires |
|
Steps | To optionally obtain public IP addresses for your virtual datacenter, so that you can later assign them to your VMs:
Now when you edit a VM in the VDC and go to Network → Public, the platform will display the public IP address and you can add it to your VM. To obtain a public IP directly for a VM, the user with appropriate privileges can click Purchase public IPs. |
Expected results | When a user creates a VM on the virtual appliance screen and configures the VM, there are Public IPs available to use. |
Comments |
|
Use Case 4.5 - Onboard the existing virtual infrastructure from public cloud
Use Case 4.5 | Onboard the existing virtual infrastructure from public cloud |
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 | To onboard public cloud resources
Abiquo will import this virtual infrastructure from the provider. Note that Abiquo will detect network configuration but it will not enforce a standard configuration. |
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):
|
Use Case 4.6 - Define allocation limits for the virtual datacenter
Use Case 4.6 | Define allocation limits for the virtual datacenter |
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. Go to the Allocation limits tab. |
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 from the cloud provider |
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 evaluation, you may wish to perform this action AFTER you create a VM and just before you launch it, in order to reduce costs. |
Pre-requisites |
|
Requires |
|
Steps |
|
Expected results | A public IP will be created and can be added to the virtual datacenter and VM as required. As in private cloud you can also obtain a public IP from within the VM configuration. |
Comments |
|
Use Case 4.8 - Create enterprise users
Use Case 4.8 | Create Enterprise Users |
Description | Enterprise users are able to log in via the enterprise's management console and deploy virtual resources. |
Pre-requisites |
|
Requires | Enterprise user Name and Email address |
Steps |
|
Expected results | An Enterprise user is created and they can log in and deploy VMs in the selected enterprise. |
Comments |
|
Use Case 4.9 - Create custom user roles
Use Case 4.9 | Create Custom User Roles |
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 |
|
Requires | Enterprise user Name and Email address |
Steps | To create a custom user role:
|
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. One function of a scope is to restrict administrator roles to certain enterprises and datacenters. Typically you would have one scope per enterprise for the cloud users. If an administrator will manage users and VM templates for multiple enterprises, then their scope should include all of these enterprises. See Manage Scopes |
Manage virtual appliances for enterprise user
Use Case 5.1 - Create virtual appliances
Use Case 5.1 | Create virtual appliances |
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 | To create a virtual appliance:
|
Expected results | A virtual appliance is created with a VM template available from the Apps library (Catalogue). |
Comments |
|
Use Case 5.2 - Deploy and undeploy a virtual appliance
Use Case 5.2 | Deploy and undeploy a virtual appliance |
Description | Enterprise users should be able to to manage their virtual appliances. They can easily deploy and undeploy their virtual appliances. |
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. You can also deploy virtual appliances using the controls that appear when a virtual appliance is selected in the virtual datacenter view. When the virtual appliance is deployed, the Deploy button becomes an Undeploy button or a Deploy all VMs button. To destroy all the VMs and all your data on the hard disks, click the Undeploy button. |
Expected results |
|
Comments | For more details, see Manage Virtual Machines |
Use Case 5.3 - Reconfigure a VM to add network and storage
Use Case 5.3 | Reconfigure a VM |
Description | Enterprise users should have the ability to modify their VMs. |
Pre-requisites | |
Requires | A virtual appliance has already been deployed. If the VM and its operating system do not support hot reconfigure, then power off the VM before you modify it |
Steps |
|
Expected results | The platform will reconfigure your VM |
Comments | Remember to configure your disk in the VM operating system. For more details, see and Configure Virtual Machines |
Additional public cloud use cases
Use Case 6.1 - Create virtual storage volumes in public cloud
Use Case 6.1 | Create virtual storage volumes in public cloud |
Description | You can create storage volumes and attach them to a VM to extend usable disk space capacity. These volumes are usually persistent, so you can reuse them after you detach them and even after you destroy the VM. |
Pre-requisites |
|
Requires | Volume name and size of volume |
Steps | To create a new storage volume:
|
Expected results | The volume is now available to be attached to a virtual machine before or after it is deployed. |
Comments |
Use Case 6.2 - Export a VM template from a private cloud datacenter
Use Case 6.2 | Export a VM template from a private cloud datacenter |
Description | The cloud platform can support multiple datacenters and public cloud regions, with different technologies and service levels. |
Pre-requisites | A cloud environment with a datacenter plus a public cloud region (or another datacenter) |
Requires |
|
Steps | You must first prepare the template according to the cloud provider instructions. See VM Template Mobility
|
Expected results | A compatible VM template can be exported (copied) to another private cloud datacenter or a public cloud region |
Comments |
Validate Cloud Application
Use Case 7.1 - Access the running VM via the Abiquo platform
Use Case 7.1 | Access the running VM via the Abiquo platform |
Description | Customers should be able to access VMs deployed by the cloud management application |
Pre-requisites | A virtual appliance that is successfully deployed and powered on |
Requires |
|
Steps |
|
Expected results | A console window will open and the user is presented with the login to the VM |
Comments |
|
Use Case 7.2 - Validate co-existence with existing management tools
Use Case 7.2 | Validate Co-existence with existing management tools |
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, when using vCenter hosts, if a VM is moved by vMotion, then Abiquo will recognise the move. If you are using vCenter clusters as hosts, then Abiquo does not need to recognise the moves because the VMs are effectively on the same host. |
Pre-requisites |
|
Requires | VM running on hypervisor hosts |
Steps | Deploy VMs using Abiquo and Hypervisor management tools |
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 |
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 |
|
Expected results | A customer user can deploy a virtual appliance and consume physical resources that have been made available to them. |
Comments | You can also save virtual appliance configurations as blueprints, so cloud users can also create these configurations using self-service. See Manage Virtual Appliance Specs |
Use Case 8.2 Cloud users can monitor their VMs
Use Case 8.2 | Cloud users can monitor their VMs |
Description | Users can monitor their VMs and retrieve metrics |
Pre-requisites |
|
Requires | Monitoring privileges (by default these are assigned to the user) |
Steps |
|
Expected results | A customer user can retrieve and display metrics to monitor the performance of their VM |
Comments | The following features can also use metrics to drive actions in the platform:
|
Integration
Use Case 9.1 - Integrate the cloud management platform with a customer portal
Use Case 9.1 | Integrate the cloud management platform with a customer portal |
Description | Hosting providers may want to integrate the Cloud Management Platform (CMP) with an existing system such as an existing customer portal or provisioning system. This will provide administrators or customers access to the Abiquo functionality through a familiar interface |
Pre-requisites | Familiarization with the Abiquo REST API |
Requires |
|
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 or ITSM system using the REST API |
Comments |
|
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 |
Description | Hosting providers offering a cloud service will want to charge customers for resources that have been reserved or consumed. Abiquo meters usage data and you can import it into your billing system. |
Pre-requisites | Abiquo database supports accounting/metering of system usages by default. For details, see Abiquo Accounting Services Integration |
Requires | Abiquo Cloud Platform with consumption data. |
Steps | You can use database scripts and Excel sheets to view accounting data. Alternatively you can create or use Abiquo 'billing connector' to extract this data. See Abiquo Billing Integration |
Expected results | Accounting data can be extracted from Abiquo and viewed in Excel (CSV) and/or imported into an existing billing system. |
Comments |
|
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 |
Description | An LDAP or AD user source may already exist and will be the preferred repository for user accounts of the cloud management platform (CMP). The CMP will be able to authenticate against the LDAP/AD user source and create the appropriate users. You can also configure Abiquo to authenticate using SAML. |
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
|
Steps |
|
Expected results | A user can log in to Abiquo using the credentials that already exist in the Abiquo/LDAP source. |
Comments |
Advanced 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 - Display cloud provider billing data on dashboard
User Case 10.1 | Display cloud provider billing data on dashboard | ||||||||
Description | Abiquo can obtain public cloud cost and usage from the providers and display it on a single multicloud dashboard for the user. If you are using reseller credentials, then if your users have customer credentials, their billing data can also display. | ||||||||
Pre-requisites | |||||||||
Requires | Public cloud region with reseller credential or standard credentials, and pricing credentials. See Obtain public cloud credentials | ||||||||
Steps | To enable the display of the billing details on the dashboard, configure the dashboard according to the instructions for the provider. See Display cloud provider billing data. For example, to configure billing dashboards for Google Cloud Platform (GCP):
| ||||||||
Expected results | The billing data will display on the dashboard | ||||||||
Comments |
|
Use Case 10.2 - Configure cost codes on VM templates
Use Case 10.2 | Configure cost codes on VM templates |
Description | Hosting providers may need to track the licenses used by VMs (e.g. Microsoft Windows licensing), or may wish to offer cloud services based on a per VM pricing model. You can also assign cost codes to hardware profiles. Note that Abiquo can also onboard prices of basic Linux templates from public cloud providers. |
Pre-requisites | N/A |
Requires | A working Cloud Management Platform (CMP) and populated Apps library (Catalogue) |
Steps |
|
Expected results | A virtual image or hardware profile can be tracked for licensing or chargeback purposes. |
Comments | See Pricing View |
Use Case 10.3 - Users can run collectd plugin to push custom metrics
Use Case 10.3 | Use collectd plugin to push custom metrics |
Description | Users may wish to view custom performance data for a VM. 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 |
|
Requires | Privilege allowing the user to push own metrics must be assigned to the collectd OAuth application |
Steps |
|
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 these secondary use cases:
- Create security group
- Create web servers
- Add load balancer
- Retrieve index files from web servers
Use Case 11.1 - Create security groups
Use Case 11.1 | Create security group |
Description | Abiquo tenant administrators can create firewalls that are security groups, in public cloud (e.g. AWS) or private cloud (using the VMware NSX integration) |
Pre-requisites |
|
Requires |
|
Steps | To create firewalls:
|
Expected results | Each firewall is created with the appropriate security group policies. As always, check your provider documentation for specific information about security group functionality. And see Manage Firewalls |
Comments | Note: cloud users will require appropriate privileges to use firewalls |
Use Case 11.2 - Create web servers
Use Case 11.2 | Create web servers | |
Description | Create two basic web servers that will be load balanced | |
Pre-requisites |
| |
Requires |
| |
Steps |
| |
Expected results | This command will start a HTTP server listening on port 8000 | |
Comments |
Use Case 11.3 - Create load balancer
Use Case 11.3 | Create load balancer |
Description | Abiquo can create load balancers in public cloud providers such as AWS and also in private cloud using VMware NSX |
Pre-requisites | Public cloud credentials added. Where appropriate (NSX and AWS) firewalls created, firewall rules created for SSH and the appropriate load balancer protocol. Firewalls are synchronized. |
Requires | Existing virtual datacenter, either newly created or onboarded. |
Steps | To add a load balancer:
A load balancer is created. As always, check you provider documentation for pricing and functionality. For more information about load balancers in Abiquo, see Manage Load Balancers. Note: cloud users will require appropriate privileges to use load balancers. |
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 11.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.
Test Case Results Summary
You can use this check sheet to track completion of the test use cases. Please contact your Platform and Customer Success Engineer if you require any assistance executing the tests or if there are any tests that do not complete successfully. They will be happy to work with you and propose a resolution.
UC # | Objective | Success/Fail | Proposed resolution and Notes |
---|---|---|---|
1 | Discover physical infrastructure for cloud operator | ||
1.1 | Create a datacenter | ||
1.2 | Define logical racks and VLAN network requirements | ||
1.3 | Create datastore tiers for datastore service levels | ||
1.4 | Acquire the physical infrastructure | ||
1.5 | Define the data center utilization rules | ||
1.6 | Create public IPs for consumption by cloud tenants | ||
1.7 | Capture existing VMs and support a phased deployment | ||
1.8 | Create public cloud regions | ||
1.9 | Add public cloud credentials | ||
2 | Create a global catalogue for VM templates and blueprints | ||
2.1 | Create a global service catalogue as a template repository | ||
2.2 | Leverage existing VM templates by importing into the catalogue | ||
2.3 | Create a cache of approved public cloud templates | ||
3 | Create customer organization hierarchy | ||
3.1 | Create a reseller and an enterprise for a cloud tenant to consume cloud resources | ||
3.2 | Define resource allocation limits for the enterprise | ||
3.3 | Delegate administration of an enterprise | ||
3.4 | Define enterprise business policy | ||
4 | Manage enterprise for enterprise administrator | ||
4.1 | Create a virtual datacenter from the resource cloud | ||
4.2 | Create private networks | ||
4.3 | Reserve public IPs or external IPs | ||
4.4 | Onboard the existing virtual infrastructure from public cloud | ||
4.5 | Define allocation limits for the virtual datacenter | ||
4.6 | Obtain floating public IPs from the cloud provider | ||
4.7 | Create enterprise users | ||
4.8 | Create custom user roles | ||
5 | Manage virtual appliances for enterprise user | ||
5.1 | Create virtual appliances | ||
5.2 | Deploy and undeploy a virtual appliance | ||
5.3 | Reconfigure a VM to add network and storage | ||
6 | Additional public cloud use cases | ||
6.1 | Create virtual storage volumes in public cloud | ||
6.2 | Export a VM template from private datacenter to public cloud | ||
7 | Validate Cloud Application | ||
7.1 | Access the running VM via the Abiquo platform | ||
7.2 | Validate co-existence with existing management tools | ||
8 | Cloud User Self Service | ||
8.1 | Cloud users can access the platform on a self-service basis | ||
8.2 | Cloud users can monitor their VMs | ||
9 | Integration | ||
9.1 | Integrate the cloud management integration with a customer portal | ||
9.2 | Extract billing or chargeback data from the cloud platform | ||
9.3 | Integrate the cloud platform with an existing LDAP/AD or OpenID user source | ||
10 | Advanced use cases | ||
10.1 | Display provider billing data on dashboard | ||
10.2 | Configure VM template cost codes | ||
10.3 | Users can run collectd plugin to push custom metrics | ||
11 | Use load balancers | ||
11.1 | Create security groups | ||
11.2 | Create web servers | ||
11.3 | Create load balancer | ||
11.4 | Retrieve index files from web servers |
Copyright © 2006-2022, Abiquo Holdings SL. All rights reserved