f1cb8e5d8f
The 3PAR driver uses the FQDN of the node that is doing the attach as an unique identifier to map the volume. The problem is that the FQDN is not always unique, there are environments where the same FQDN can be found in different systems, and in those cases if both try to attach volumes the second system will fail. One example of this happening would be on a QA environment where you are creating VMs and they all have names like controller-0.localdomain and compute-0.localdomain. This patch adds a configuration option to the 3PAR driver called `unique_fqdn_network` to support these kind of environments. Change-Id: I781144cbe68d6908333234a614e021365b0a6d4a Closes-Bug: #1834695
8 lines
195 B
YAML
8 lines
195 B
YAML
---
|
|
issues:
|
|
- |
|
|
HPE 3PAR driver now supports networks with duplicated FQDNs via configuration
|
|
option `unique_fqdn_network` so attaching in these networks will work
|
|
(bug #1834695).
|
|
|