Browse Source
In Pike and later, the name_lower field in network_data.yaml can be re-defined to contain a custom network name. When this is done the ServiceNetMap field must be overridden to reflect the new name in all places. This changes adds a new optional field to network_data.yaml that should be set to the original default name_lower value. ServiceNetMap will then be automatically updated and will not need to be overridden. This also fixes the VipPort naming for the StorageManagement network to not use a static value. Change-Id: I8a238038122288899cef49faf38ea2c2ffc2176bchanges/69/574269/4
4 changed files with 15 additions and 8 deletions
@ -0,0 +1,8 @@
|
||||
--- |
||||
fixes: |
||||
- The name_lower field in network_data.yaml can be used to |
||||
define custom network names but the ServiceNetMap must be |
||||
updated with the new names in all places. This change |
||||
adds a new field to network_data.yaml - service_net_map_replace, |
||||
that should be set to the original name_lower so that ServiceNetMap |
||||
will be automatically updated. |
Loading…
Reference in new issue