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.
Reviewed: https:/ /review. openstack. org/624567 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=719d0098f25 172609e5e006bb0 fa6760d71903fb
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 719d0098f251726 09e5e006bb0fa67 60d71903fb
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 /review. openstack. org/624563 d7436431c58f22a 559a190773)
Depends-On: #https:/
Closes-Bug: #1800811
(cherry picked from commit 5d275fb9223c722