This feature is currently not available in public datacenters
There are two main types of virtual storage available in Abiquo: hard disks and volumes. Abiquo supports all iSCSI storage for creating: In Abiquo, hard disks on the hypervisor datastore are deleted when the virtual machine they are attached to is undeployed. In contrast, volumes on external storage devices remain on the storage device after a virtual machine is undeployed. In Abiquo, external storage is persistent storage that is not part of the hypervisor datastore. The following table compares the characteristics of Abiquo virtual storage types. Abiquo Storage Volumes of Integrated External Storage Generic iSCSI Storage Persistence Persistent Persistent Architecture Abiquo plug-in architecture manages the disk cabinet Generic interface mounts an existing iSCSI LUN Storage as a Service Yes, users manage virtual disks Not automatic Configuration Automatic disk configuration discovery Requires iSCSI information and volume size Created by Abiquo user Abiquo user Control of Storage Abiquo manages hypervisor datastore Abiquo manages disk cabinet Storage administrator manages the storage device Flexibility Cloud administrator can configure all parameters Cloud administrator cannot control disk size or other parameters
Hard Disks on Hypervisor Datastore
iSCSI and NFS
Terminology Hard disks Volumes Volumes Hypervisor Support ESXi, Oracle, Hyper-V, XenServer
XenServer: no NFS support Automatic Storage level Virtual machine Virtual datacenter, virtual machine Infrastructure, virtual datacenter, virtual machine User can specify disk size Persistent VM Support Cannot store persistent virtual machine disks Can store persistent virtual machines Can store persistent virtual machines
if the volume size is larger than the raw template disk size
Disk resize User can resize disks where supported User can resize disks where supported User cannot resize disks
Abiquo supports all iSCSI storage for creating:
In Abiquo, hard disks on the hypervisor datastore are deleted when the virtual machine they are attached to is undeployed. In contrast, volumes on external storage devices remain on the storage device after a virtual machine is undeployed. In Abiquo, external storage is persistent storage that is not part of the hypervisor datastore.
The following table compares the characteristics of Abiquo virtual storage types.
Volumes of Integrated External Storage
Generic iSCSI Storage
Abiquo plug-in architecture manages the disk cabinet
Generic interface mounts an existing iSCSI LUN
Storage as a Service
Yes, users manage virtual disks
Automatic disk configuration discovery
Requires iSCSI information and volume size
Control of Storage
Abiquo manages hypervisor datastore
Abiquo manages disk cabinet
Storage administrator manages the storage device
Cloud administrator can configure all parameters
Cloud administrator cannot control disk size or other parameters
This section describes how to manage persistent external storage devices in Abiquo. Users can then create volumes for their virtual datacenters. See Manage Virtual Storage and Configure Virtual Machines .
Non-persistent hard disks are configured by cloud users directly for their virtual machines. See Configure Virtual Machines
There are two main types of persistent storage available to virtual machines in Abiquo: integrated managed storage and generic iSCSI storage.
For further information, see Abiquo Virtual Storage.
To manage a datacenter's external storage, go to the Infrastructure View by clicking thebutton at the top of the main screen, select the datacenter in the list, and click the button to view the Datacenter detail. Click the Storage tab to manage the external storage infrastructure.
Abiquo can directly manage the following storage device types to provide storage as a service to cloud users:
For iSCSI storage devices that are not directly supported, you can
The first step in working with persistent storage is to create a Storage Device. A storage device provides access to the storage technology so you can configure the Management and Service networks that the cloud nodes will use to access it. You can manage storage devices with the buttons located in the lower left corner of the storage screen, beneath the storage devices list.
Add a storage device.
Remove a storage device.
Edit the selected storage device.
Click thebutton, select Storage Device, and complete this form:
Add NetApp Credentials When Creating the Storage Device
You must add the NetApp credentials when creating or editing a storage device. You cannot add the NetApp credentials in the abiquo.properties file.
After you have created a storage device, you can check its details by selecting it in the list of storage devices.
Abiquo offers support for generic iSCSI storage without storage management capacity.
Clickand complete the form to create a storage device, selecting GENERIC_iSCSI storage technology:
Adding and deleting volumes is described in the Managing Generic iSCSI Volumes section below.
Add storage pools.
Remove storage pools.
Update storage pool information.
Edit the selected storage pool.
After you create a managed storage device, you can add storage pools. Abiquo automatically detects all the pools in the target storage and allows you to add them to the platform. After the managed storage pools have been added, users will be able to create volumes. The volumes will be automatically allocated to storage pools in the chosen tier, in accordance with the selected storage pool allocation method.
Abiquo creates a single pool for an entire generic iSCSI storage device because it cannot communicate with the device's management interface to detect the pools already created on the storage. For generic iSCSI storage, volumes must be created outside Abiquo in the storage device and then manually entered into Abiquo in the Virtual Datacenters view. For more information please see Manage Virtual Storage.
Storage Pools can be added directly after creating the managed storage device or later.
To add Storage Pools to your infrastructure, click the, and select the option "storage pool" from the drop-down list.
Select the storage device from the popup.
The Add Storage Pool popup will open and you will see the list of available storage pools. Those already selected are disabled, which means that they are already added to your Infrastructure and it is not possible to add them again.
Each Managed Storage Pool must be associated with a tier, according to its service level. When users create a volume and select a Tier (Service level) for the volume, it will be created in a pool belonging to that tier in accordance with the storage pool allocation method.
After you create the storage pool, you can check its details by selecting it in the list of devices.
To modify a Storage Pool, select it and click thebutton to open the Edit form. You cannot modify the name of the Storage Pool because it is already defined. You can change the tier of all types of storage. You can also set the usable percentage of a pool, as well a the maximum number of volumes in the pool.
To remove a storage pool, first remove all of the volumes within it. Then select the pool in the list and click thebutton to remove it.
The Tiers tab allows you to configure different service levels for external managed storage. Storage service levels are set with tiers that are configured to enable end users to choose the service level they want for the volumes they create under Storage as a Service. Click on the triangle beside a tier to view its contents listed in the format "pool (storage device)".
The Tiers tab contains the default tiers in Abiquo. You cannot add or remove Tiers, but you can change the tier name and enable/disable the required tiers. Select a Tier and click thebutton to edit it.
Restrict Enterprise Access to Tiers
After an enterprise has created volumes in a tier, you cannot restrict access to the tier for that enterprise.
You cannot disable a Tier if it contains volumes.
Multiple Pools in Tiers
Abiquo uses all pools assigned to a tier. When you create a volume, Abiquo will automatically allocate it to a pool in the chosen tier in accordance with the Storage Pool Allocation.
When you click on the Enteprise Access tab, you will see a list of all the enterprises with access to the storage tier. Click the buttons to "Allow for all enterprises" or "Restrict for all enterprises". This setting will override the checkbox on the previous page for all existing enterprises. However, newly created enterprises will receive the option specified with the checkbox.
The Allow for all enterprises or Restrict for all enterprises setting can later be changed for individual enterprises. See Controlling Access to Storage Tiers in the Manage Enterprises documentation
The Volume list contains all the volumes created in the pool with detailed information such as the internal volume ID or IQN used to identify the volume in the target storage technology, the volume size, etc.
The details panel of each volume contains a table of the Initiator mappings. Each storage technology will have its own access policies for each volume, so the different clients (hypervisors) may access the volume using different IQNs or LUN numbers. The Initiator mapping table shows, for each Initiator IQN (representing a single client), the IQN and LUN number that will be used to connect to the volume.
Volumes that have been already created on generic iSCSI storage can be added and deleted from Abiquo. They cannot be modified within Abiquo because there is no communication with the management interface of the generic iSCSI storage device.
To add a pre-existing generic iSCSI volume, open your datacenter and generic iSCSI storage device. Then click thebutton below the Volume list and complete the form. Note that many storage systems will automatically generate a LUN of 0 by default.
If a volume has been removed or replaced in the storage device, Abiquo may try to attach a volume that does not exist or is completely different to one previously configured. This situation may occur with: managed storage volumes, generic iSCSI volumes and persistent virtual machines. It can be resolved by manually performing a full HBA rescan of all ESX or ESXi hosts that had raw device mappings for the devices involved. In general, Abiquo avoids performing a full HBA rescan of storage on ESX or ESXi for performance reasons. Instead it checks for a raw device mapping for a given IQN and LUN, which means that changes to volumes can lead to this situation.