0bbf54f84f
3PAR driver so far did not support multiple pools per backend. This patch aims to allow support for multiple pools per backend. The configuration now accepts multiple pool entries per backend. In manila.conf, hpe3par_fpg was used to represent one pool (FPG in terms of 3PAR) under a backend. Now, hpe3par_fpg can be used multiple times within a backend, each entry will represent a pool (FPG name). Sample configuration to supply pools 'testfpg' and 'sharenetfpg': hpe3par_fpg = sharenetfpg, 10.50.158.8 hpe3par_fpg = testfpg, 10.50.158.7 Note that the configuration now also accepts IP address of share server. 3PAR supports up to 4 IP addresses per share server. So the format to supply multiple share server IP addresses per pool: hpe3par_fpg = fpgname, IPaddress1, IPaddress2, IPaddress3, IPaddress4 If the share server is already setup and configured with IP address, it need not be passed with hpe3par_fpg. When DHSS=True, the format remains same as above, except the IP address of share server is silently ignored if provided. Obsoletes: hpe3par_share_ip_address from config Release note added. Change-Id: Ic08452f3ddf6b7b2f2dc1ba5ee32b4ebe5ae2614 Implements: blueprint hpe3par-pool-support
9 lines
325 B
YAML
9 lines
325 B
YAML
|
|
---
|
|
features:
|
|
- HPE 3PAR driver now supports configuring multiple pools per backend.
|
|
upgrade:
|
|
- HPE 3PAR driver no longer uses hpe3par_share_ip_address option in
|
|
configuration. With pool support, configuration just requires
|
|
hpe3par_fpg option or optionally supply share IP address(es) along with
|
|
hpe3par_fpg. |