Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Go to Infrastructure → Private → select datacenter → Datacenter details view → Persistent storage → Devices
  2. Click the + add button
  3. Select Storage device
  4. Complete the dialog

Include Page
ABI54:GUI Add Storage DeviceABI54:
GUI Add Storage Device

After you have created a storage device, you can check its details by selecting it in the list of storage devices.

...

  1. Go to Infrastructure → Private → select datacenter → Datacenter details view → Persistent storage → Devices
  2. Click the + add button
  3. Select Storage device
  4. As you complete the dialog, select the GENERIC_iSCSI storage technology

Include Page
ABI54:GUI Add storage device Generic iSCSIABI54:
GUI Add storage device Generic iSCSI

For details of how to add and delete volumes, see Managing Generic iSCSI Volumes 410615847 section below.

To refresh the storage device in the platform, click the round arrow synchronize button.

...

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 Infrastructure view. See #Manage Generic iSCSI Volumes


...


Add Storage Pools

Storage Pools can be added directly after creating the managed storage device or later.

...

  1. Select the storage pool
  2. Click the edit button
    1. You cannot modify the name of the Storage Pool after you create the pool 
    2. You can change 
      1. the tier of all types of storage. 
      2. the usable percentage of a pool
      3. the maximum number of volumes in the pool.

Include Page
ABI54:GUI Edit storage poolABI54:
GUI Edit storage pool


...


Remove a Storage Pool

...

  1. Go to Infrastructure → Private → select datacenter → Datacenter details view → Persistent storage → Tiers
  2. Select the tier
  3. Click the pencil edit button and you can:
    1. Change the tier Name
    2. Enable/disable the tier
      1. After an enterprise has created volumes in a tier, you cannot restrict access to the tier for that enterprise
      2. You cannot disable a tier if it contains volumes.

Include Page
ABI54:GUI Edit tier Storage General informationABI54:
GUI Edit tier Storage General information

...

  • For all existing enterprises, this setting will override the checkbox on the General information tab
    • But you cannot restrict the access of enterprises that have already created volumes in this tier
  • New enterprises will have the option specified with the checkbox on the General information tab
  • You can later change these settings for individual enterprises. See Controlling Access to Storage Tiers in the Manage Enterprises documentation

 


The Volume List

The Volume list contains all the volumes created in the pool with tiers, volume sizes and details of the virtual appliances and VMs the volumes are attached to.

  • In managed storage, volumes are created by users under Storage as a Service in Virtual Datacenters view. For more information see Manage Virtual Storage in Datacenters
  • In generic iSCSI storage, volumes must be created outside Abiquo in the storage device itself and manually added by an administrator in the Infrastructure view. For more information see Managing Generic iSCSI Storage Volumes.

 


...


Manage Generic iSCSI Volumes

...

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 VMs. 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.