HPE Storage Configurations
Overview
HPE storage arrays provide enterprise-grade block storage solutions for data centers. Private Cloud Director supports the following HPE storage arrays:
HPE 3PAR and Primera - Enterprise block storage over Fibre Channel and iSCSI using the HPE 3PAR driver.
HPE Alletra 9000/10000 - High-end block storage using the same HPE 3PAR driver over Fibre Channel and iSCSI.
HPE Nimble (HPE Alletra 5000/6000) - Predictive analytics-driven storage over Fibre Channel and iSCSI using the HPE Nimble driver.
NOTE
HPE 3PAR, Primera, and Alletra 9000/10000 arrays use the same driver family (hpe_3par), which provides consistent configuration and management across these models. They support thin provisioning, deduplication, and compression (DECO) for volumes 16 GiB and larger. HPE Nimble and Alletra 5000/6000 arrays use a separate driver (hpe_nimble); see the Nimble tabs for configuration details.
Select a storage array and protocol below to view the complete configuration steps for your environment.
HPE 3PAR and Primera arrays use the same driver and configuration parameters for Fibre Channel connectivity, providing high-performance block storage for enterprise workloads.
Prerequisites
Before you configure the 3PAR/Primera Fibre Channel backend, complete these requirements:
Minimum 3PAR OS version: 3.2.1 or later.
Supported Primera models: A650 and A670.
Install Fibre Channel HBAs on all hosts.
Enable the Web Services API (WSAPI) on the 3PAR/Primera array. Private Cloud Directoruses WSAPI to programmatically manage volumes, snapshots, and CPG operations.
Create a Common Provisioning Group (CPG) on the array. Platform9 provisions all volumes from the specified CPG.
Configure FC zoning between hosts and the 3PAR/Primera array. Proper zoning ensures hosts can discover and access storage LUNs.
Volume backend configuration
[hpe_3par_fc_backend]
volume_driver = cinder.volume.drivers.hpe.hpe_3par_fc.HPE3PARFCDriver
volume_backend_name = hpe_3par_fc
san_ip = <3PAR_MGMT_IP>
san_login = <3PAR_USER>
san_password = <3PAR_PASSWORD>
hpe3par_api_url = https://<3PAR_MGMT_IP>/api/v1
hpe3par_username = <3PAR_USER>
hpe3par_password = <3PAR_PASSWORD>
hpe3par_cpg = <CPG_NAME>
hpe3par_debug = false
# Persona 2 configures volumes for generic ALUA hosts (recommended)
hpe3par_persona = 2
use_multipath_for_image_xfer = true
volumes_dir = /opt/pf9/etc/pf9-cindervolume-base/volumes/Configuration parameters
hpe3par_persona Configures the host type for volume attachments. Set to
2for generic ALUA hosts, which is recommended for most deployments. This ensures proper multipath failover behavior.use_multipath_for_image_xfer Enables multipath for image transfers, improving reliability during volume creation from images.
Image management configuration
To enable a storage backend for image uploads, add the following parameters:
Optional parameters
Enable image-volume caching when you use a storage backend for image storage. Caching stores converted images locally on each storage host, which reduces image transfer time for subsequent volume creation requests.
Configuration notes
These arrays support thin provisioning with deduplication and compression (DECO) for volumes 16 GiB and larger.
The system thin-provisions volumes smaller than 16 GiB without DECO.
HPE 3PAR and Primera arrays provide block storage over IP networks through iSCSI, offering flexible connectivity using standard Ethernet infrastructure.
Prerequisites
Before you configure the 3PAR/Primera iSCSI backend, complete these requirements:
Minimum 3PAR OS version: 3.2.1 or later.
Supported Primera models: A650 and A670.
Install
open-iscsion all hosts. The iSCSI initiator enables hosts to discover and connect to iSCSI targets.Enable the Web Services API (WSAPI) on the 3PAR/Primera array. Platform9 uses WSAPI to programmatically manage volumes, snapshots, and CPG operations.
Create a Common Provisioning Group (CPG) on the array. Platform9 provisions all volumes from the specified CPG.
Enable iSCSI ports on the array and verify network connectivity.
Configure iSCSI connectivity between hosts and the array. Verify hosts can reach all iSCSI portal IPs.
Volume backend configuration
Configuration parameters
hpe3par_iscsi_ips Comma-separated list of iSCSI portal IP addresses. Specify multiple IPs for multipath redundancy and higher availability.
use_multipath_for_image_xfer Enables multipath for image transfers, improving reliability during volume creation from images.
Configuration notes
Verify all iSCSI IPs are accessible from hypervisor hosts before configuring the backend.
Configure CHAP authentication for additional security if required.
These arrays support thin provisioning with DECO for volumes 16 GiB and larger.
HPE Alletra 9000 and 10000 series arrays use the same driver and API as HPE 3PAR and Primera, providing modern enterprise storage with Fibre Channel connectivity.
Prerequisites
Before you configure the Alletra Fibre Channel backend, complete these requirements:
Install Fibre Channel HBAs on all hosts.
Enable Web Services API (WSAPI) on the Alletra array. Platform9 uses WSAPI to programmatically manage volumes, snapshots, and CPG operations.
Create a Common Provisioning Group (CPG) on the array. Platform9 provisions all volumes from the specified CPG.
Configure FC zoning between hosts and the Alletra array. Proper zoning ensures hosts can discover and access storage LUNs.
Volume backend configuration
Configuration parameters
hpe3par_persona Configures the host type for volume attachments. Set to
2for generic ALUA hosts, which is recommended for most deployments. This ensures proper multipath failover behavior.use_multipath_for_image_xfer Enables multipath for image transfers, improving reliability during volume creation from images.
Image management configuration
To enable a storage backend for image uploads, add the following parameters:
Optional parameters
Enable image-volume caching when you use a storage backend for image storage. Caching stores converted images locally on each storage host, which reduces image transfer time for subsequent volume creation requests.
Configuration notes
Configuration parameters are identical to 3PAR/Primera.
Alletra 9000 uses the same API endpoints as 3PAR.
These arrays support thin provisioning with DECO compression for volumes 256MB
The system thin-provisions volumes smaller than 16 GiB without DECO.
HPE Alletra 9000 and 10000 series arrays provide block storage over iSCSI using the same driver as HPE 3PAR and Primera.
Prerequisites
Before you configure the Alletra iSCSI backend, complete these requirements:
Install
open-iscsion all hosts. The iSCSI initiator enables hosts to discover and connect to iSCSI targets.Enable Web Services API (WSAPI) on the Alletra array. Private Cloud Director uses WSAPI to programmatically manage volumes, snapshots, and CPG operations.
Create a Common Provisioning Group (CPG) on the array. Private Cloud Director provisions all volumes from the specified CPG.
Enable iSCSI ports on the array and verify network connectivity.
Configure iSCSI connectivity between hosts and the array. Verify hosts can reach all iSCSI portal IPs.
Volume backend configuration
Configuration parameters
hpe3par_iscsi_ips Comma-separated list of iSCSI portal IP addresses. Specify multiple IPs for multipath redundancy and higher availability.
use_multipath_for_image_xfer Enables multipath for image transfers, improving reliability during volume creation from images.
Configuration notes
Configuration parameters are identical to 3PAR/Primera iSCSI.
These arrays support thin provisioning with DECO compression for volumes 16 GiB and larger.
The system thin-provisions volumes smaller than 16 GiB without DECO.
HPE Nimble arrays provide predictive analytics-driven storage with built-in replication and space-efficient snapshots. Private Cloud Director supports Nimble arrays through the Nimble driver using iSCSI.
Prerequisites
Before you configure the Nimble iSCSI backend, complete these requirements:
Install
open-iscsion all hosts. The iSCSI initiator enables hosts to discover and connect to iSCSI targets.Verify the Nimble array management interface is accessible from Private Cloud Directorcontrol plane hosts.
Create a storage pool on the array. Private Cloud Director provisions all volumes from the specified pool.
Configure iSCSI connectivity between hosts and the array. Verify hosts can reach the Nimble iSCSI network.
Volume backend configuration
Configuration parameters
nimble_pool_name Specifies the storage pool name on the Nimble array where Platform9 provisions volumes.
use_multipath_for_image_xfer Enables multipath for image transfers, improving reliability during volume creation from images.
Volume type configuration
Nimble requires specific extra specifications for the volume type of encrypted volumes and for performance policies.
For encrypted volumes:
Enable encryption at the volume-type level using the nimble:encryption attribute:
Nimble encrypted volumes require the nimble:encryption = yes attribute in the volume type. If you omit this attribute, volume allocation to encrypted pools fails with unclear error messages.
For performance policies:
To assign a specific performance policy, add the following extra spec to the volume type:
Example performance policies available on Nimble arrays:
SQL Server 2012
Exchange 2010
VMware
Default
Configuration notes
Performance policies are predefined on the Nimble array and must exist before you reference them in volume types.
Nimble supports automatic compression and space reclamation without additional configuration.
Snapshots are instant and crash-consistent, enabling rapid backup and recovery workflows.
HPE Nimble arrays, sold as HPE Alletra 5000 and 6000 in current product lines, provide predictive analytics-driven storage with built-in replication and space-efficient snapshots. Private Cloud Director supports Nimble arrays through the Nimble driver using Fibre Channel.
Prerequisites
Complete the following before you configure the Nimble Fibre Channel backend.
Fabric and array side
Install Fibre Channel HBAs on all hypervisor hosts.
Configure FC zoning between host HBA WWPNs and Nimble target WWPNs on the SAN switches. Zoning is not automated by the Nimble driver and must be in place before LUNs can be discovered.
Enable FC at the Nimble group level. Confirm with
group --infothatFC enabled: Yes.Create a storage pool on the array. Private Cloud Director provisions all volumes from the specified pool.
Use a Nimble account with at least power-user privilege.
Do not pre-create initiator groups for the host WWPNs. The driver automatically creates and manages igroups pre-existing igroups for the same WWPNs, causing membership conflicts.
Network
Ensure the Private Cloud Director control plane can reach the Nimble management IP on TCP/5392. The driver uses the Nimble REST API directly; no external SDK is required.
Compute host packages
On RHEL 9:
dnf install device-mapper-multipath sg3_utils sysfsutils, thenmpathconf --enable && systemctl enable --now multipathd.On Ubuntu 22.04 or later:
apt install multipath-tools sg3-utils sysfsutils, thensystemctl enable --now multipathd.HBA kernel modules (
lpfcfor Emulex,qla2xxxfor QLogic/Marvell) ship with both distributions and load automatically.iscsidis not required for pure FC deployments.
NOTE
Do not install the HPE Nimble Linux Toolkit (NLT) on compute hosts. OpenStack Cinder is not compatible with NLT.
Volume backend configuration
Add the backend to enabled_backends in the [DEFAULT] section:
Restart cinder-api, cinder-scheduler, and cinder-volume after applying configuration changes. Verify the backend is registered with cinder service-list.
Configuration parameters
nimble_pool_name Specifies the storage pool name on the Nimble array where Private Cloud Director provisions volumes. Use
defaultif the array uses the default pool.nimble_verify_certificate Controls TLS certificate verification when Private Cloud Director connects to the Nimble management API. Set to
truefor production deployments that use trusted certificates.nimble_verify_cert_path Path to the CA bundle used to verify the Nimble management certificate. Required only when
nimble_verify_certificate = true. Omit the parameter when certificate verification is disabled. Example:nimble_verify_cert_path = /etc/pki/tls/certs/nimble-ca.pem.use_multipath_for_image_xfer Enables multipath for image transfers, improving reliability during volume creation from images.
enforce_multipath_for_image_xfer Requires multipath connectivity for image transfers and fails the operation if multipath is not available. Set to
trueto ensure that volume operations never fall back to a single path.
NOTE
Set nimble_verify_cert_path only to a valid filesystem path or omit it. The driver treats the value as a literal path; placeholder strings such as none cause certificate loading to fail when verification is enabled.
Compute host configuration
To enable multipath for volume attachments on hypervisor hosts, add the following to nova_override.conf:
volume_enforce_multipath is available in 2025.1 Epoxy and later. When enabled, nova-compute fails to start if multipathd is not running, which prevents silent fallback to single-path attachments. It requires volume_use_multipath = true.
Restart nova-compute on each hypervisor after applying changes.
Multipath configuration
Configure /etc/multipath.conf on all hypervisor and storage hosts. The following defaults and blacklist configuration is recommended for Nimble FC deployments:
After editing multipath.conf, run multipathd reconfigure.
Configuration notes
Set
find_multipathstoyesso multipath creates a device only when at least two non-blacklisted paths exist with the same WWID. Setting it tonocauses multipath to wrap every non-blacklisted path, including local disks with single paths.Add the WWID of each host's local boot disk to the
blacklist {}block. This prevents multipath from managing local disks as if they were LUNs from external storage. To find the WWID of a local disk, run/usr/lib/udev/scsi_id -g -u -d /dev/<disk>on the host.
Optional: device-specific tuning
For deployments that require fine-grained control over Nimble device behavior, add a devices {} block to multipath.conf with Nimble-specific settings:
This block is not required. Default multipath behavior is sufficient for most Nimble FC deployments. Notes on selected values:
fast_io_fail_tmo 5matches the HPE Nimble Linux Integration Guide. The value applies during FC RSCN events.no_path_retry 30queues I/O for approximately 150 seconds before failing. Usequeuefor indefinite queueing only when host shutdown behavior under total path loss is acceptable.rr_min_io_rq 1is the request-based equivalent of the deprecatedrr_min_io. The legacy key is silently ignored on RHEL 6.2 and later kernels.hardware_handler "1 alua"is functionally redundant on RHEL 8/9 and Ubuntu 20.04 or later becausescsi_dh_aluais auto-attached by the kernel. The line is preserved for explicitness.
Volume type configuration
After the backend is enabled, create a volume type and bind it to volume_backend_name:
In multi-backend deployments, this binding is mandatory. Without it, the scheduler returns "No valid host was found" when users request volumes for the Nimble backend.
Nimble supports volume-type extra specifications for encrypted volumes and performance policies. These specifications apply to both iSCSI and Fibre Channel backends.
For encrypted volumes
Enable encryption at the volume-type level using the nimble:encryption attribute:
NOTE
Nimble encrypted volumes require the nimble:encryption = yes attribute in the volume type. If you omit this attribute, volume allocation to encrypted pools fails with unclear error messages.
For performance policies
To assign a specific performance policy, add the following extra spec to the volume type:
Performance policies are predefined on the Nimble array and must exist before you reference them in volume types.
Multi-attach volumes
For multi-attach support, set the standard multiattach capability on the volume type. The legacy nimble:multi-initiator extra spec is no longer parsed by the driver and must not be used.
Verification
After applying the storage role, verify the configuration on a hypervisor:
systemctl is-active multipathdreturnsactive.multipath -lllists Nimble LUNs with multiple paths grouped by priority.cinder service-listshowscinder-volume@nimble_fc_backendasup.A test volume created against the
nimble_fcvolume type attaches to an instance and appears as/dev/dm-Ninside the guest.
Additional notes
Nimble supports automatic compression and space reclamation without additional configuration.
Snapshots are instant and crash-consistent, enabling rapid backup and recovery workflows.
Last updated
Was this helpful?