[Director] After introducing external LB feature additional documentation needed regarding how to to noop the VIP creation which is driven by a specific resource. Before introducing External LB feature we needed to noop network and port only. Now it's network, port and vip. If one wants to noop a network in which case now to do that one has to noop the VIP creation as well, which is driven by a specific resource.
Assigning to Dan for review.
To be clear, the additional lines which noop one or multiple VIPs are only needed when one intends to deploy in network isolation and without one or more of the isolated networks. For example, when deploying in network isolation and without the Storage and StorageMgmt networks, then the VIPs on those two need to be nooped; to do so, one should add the following two into his network customization YAML: resource_registry: OS::TripleO::Network::Ports::StorageVipPort: network/ports/noop.yaml OS::TripleO::Network::Ports::StorageMgmtVipPort: network/ports/noop.yaml
This is pretty much covered in "Selecting Networks to Deploy" in the Advanced Overcloud Guide: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/advanced_overcloud_customization/sect-isolating_networks#sect-Selecting_Networks_to_Deploy Closing BZ.