Bug 1264955

Summary:	[Director] After introducing external LB feature additional documentation needed regarding how to to noop the VIP creation which is driven by a specific resource.
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	adahms, gfidente, mburns, mcornea, rhel-osp-director-maint, srevivo
Target Milestone:	y1	Keywords:	Documentation
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-19 01:55:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1244032

Description Leonid Natapov 2015-09-21 17:46:49 UTC

[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.

Comment 2 Andrew Dahms 2015-09-23 23:03:13 UTC

Assigning to Dan for review.

Comment 3 Giulio Fidente 2015-10-14 15:46:58 UTC

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

Comment 4 Dan Macpherson 2017-06-19 01:55:09 UTC

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.