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
(cherry picked from commit 4e8a05833cb9679bc6140839305d075389dc4822)
(cherry picked from commit 6efb29dcc7294a289a78cf380b14eaf146a1a49e)
(cherry picked from commit 688b59301dd880bc15da7539dd9c5b7946903346)
(cherry picked from commit 2026fa444e3a93ca8c249f37aaa5820883265215)
(cherry picked from commit 9862730ce282ac135a7361879e927d35bfd66fda)
Reviewed: https:/ /review. opendev. org/753608 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=49f1396d604 8a0c0e297f3f889 a6f816bb67a321
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 49f1396d6048a0c 0e297f3f889a6f8 16bb67a321
Author: Tom Barron <email address hidden>
Date: Tue Jul 28 14:04:07 2020 -0400
Use appropriate allocation pools for StorageNFS
The StorageNFS network was defined in network_ data_ganesha. yaml controller case, one for the regular StorageNFS interface on
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-
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 data_ganesha. yaml with network_data.yaml since the former
network_
was derived from the latter and should differ from it only by
inclustion of the StorageNFS network.
Closes-bug: #1889682
Change-Id: Ibb50dad42ec3dc 154cd27ae9094a9 be5d0a2dd28 bc6140839305d07 5389dc4822) 89a78cf380b14ea f146a1a49e) c15da7539dd9c5b 7946903346) a8c249f37aaa582 0883265215) 35a7361879e927d 35bfd66fda)
(cherry picked from commit 4e8a05833cb9679
(cherry picked from commit 6efb29dcc7294a2
(cherry picked from commit 688b59301dd880b
(cherry picked from commit 2026fa444e3a93c
(cherry picked from commit 9862730ce282ac1