Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 5.0

Skip to end of metadata
Go to start of metadata

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

 

  • No labels