For network isolation, we specifcy available networks for role.
Therefore, there is no point in creating noop network resources for
networks that are not available/connected. This results in redundant
host entries for not available networks on overcloud nodes.
If a network is not available for a role we don't need to create
those extra noop resources.
For Undercloud/Standalone role we keep all networks in roles data
as the default ServiceNetMap specifies non ctlplane networks though
they map to ctlplane.
Change-Id: I07822ec0cba7eed352c0010eb893b5e5a522e95c
Closes-Bug: #1800811
(cherry picked from commit 5d275fb9223c722d7436431c58f22a559a190773)
Reviewed: https:/ /review. openstack. org/623051 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=2e620b9367e 298ac5d1c0a31fd f98f72c4520985
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 2e620b9367e298a c5d1c0a31fdf98f 72c4520985
Author: Rabi Mishra <email address hidden>
Date: Wed Oct 31 14:27:16 2018 +0530
Check for available networks for a role
For network isolation, we specifcy available networks for role. connected. This results in redundant
Therefore, there is no point in creating noop network resources for
networks that are not available/
host entries for not available networks on overcloud nodes.
If a network is not available for a role we don't need to create
those extra noop resources.
For Undercloud/ Standalone role we keep all networks in roles data
as the default ServiceNetMap specifies non ctlplane networks though
they map to ctlplane.
Change-Id: I07822ec0cba7ee d352c0010eb893b 5e5a522e95c d7436431c58f22a 559a190773)
Closes-Bug: #1800811
(cherry picked from commit 5d275fb9223c722