4e8a05833c
The StorageNFS network was defined in network_data_ganesha.yaml using allocation ranges that mirrored those of the other isolated networks. But TripleO and the undercloud only need to use a small number of addresses for overcloud deployment -- in the default three-controller case, one for the regular StorageNFS interface on each ControllerNfs role node, and one for the VIP on which the NFS service is offered. The bulk of the addresses in the StorageNFS CIDR should be left out of the allocation range defined in network_data so that they can be used by the allocation pool for the overcloud Netron StorageNFS provider network's subnet without danger of overlap. This change uses a CIDR with a shorter prefix so that there will be sufficient IPs left over after the undercloud's TripleO allocation pool to deploy almost 4000 clients on the Neutron StorageNFS provider network's subnet. This commit also includes some minor changes to synchronize network_data_ganesha.yaml with network_data.yaml since the former was derived from the latter and should differ from it only by inclustion of the StorageNFS network. Closes-bug: #1889682 Change-Id: Ibb50dad42ec3dc154cd27ae9094a9be5d0a2dd28
20 lines
1.0 KiB
YAML
20 lines
1.0 KiB
YAML
---
|
|
upgrade:
|
|
- |
|
|
The CIDR for the StorageNFS network in the sample network_data_ganesha.yaml file
|
|
has been modified to provide more usable IPs for the corresponding Neutron
|
|
overcloud StorageNFS provider network. Since the CIDR of an existing network
|
|
cannot be modified, deployments with existing StorageNFS networks should be
|
|
sure to customize the StorageNFS network definition to use the same CIDR
|
|
as that in their existing deployment in order to avoid a heat resource failure
|
|
when updating or upgrading the overcloud.
|
|
fixes:
|
|
- |
|
|
Fixed issue in the sample network_data_ganesha.yaml file where the
|
|
IPv4 allocation range for the StorageNFS network occupies almost
|
|
the whole of its CIDR. If network_data_ganesha.yaml is used
|
|
without modification in a customer deployment then there are too
|
|
few IPs left over in its CIDR for use by the corresponding
|
|
overcloud Neutron StorageNFS provider network for its overcloud
|
|
DHCP service.
|
|
(See `bug: #1889682 <https://bugs.launchpad.net/tripleo/+bug/1889682>`_) |