Bug 1317364

Summary:	[Docs] [Director] Address feedback on Chapter 6
Product:	Red Hat OpenStack	Reporter:	Lucy Bopf <lbopf>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0 (Liberty)	CC:	adahms, dmacpher, dsorrent, lbopf, yeylon
Target Milestone:	ga	Keywords:	Documentation
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-13 04:55:16 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:

Description Lucy Bopf 2016-03-14 06:35:13 UTC

The following items must be addressed in Chapter 6. of the Director Installation and Usage guide:

* In Section 6.1.5, 'Configuring NFS Storage', "~/templates" is needed at the end of the cp command.

* Add a reference to Appendix F.1 in Section 6.1.6.1 and Section 6.2.6.1. (relates to request below)


The following item must be addressed in Appendix F.1:

* In Appendix F.1, there should be more detailed information about the interface name mapping rules (how the interfaces are mapped to nicX). Please add the information provided in https://access.redhat.com/solutions/2148221

Comment 1 Dan Macpherson 2016-03-17 03:06:06 UTC

(In reply to Lucy Bopf from comment #0)
> The following item must be addressed in Appendix F.1:
> 
> * In Appendix F.1, there should be more detailed information about the
> interface name mapping rules (how the interfaces are mapped to nicX). Please
> add the information provided in https://access.redhat.com/solutions/2148221

I can implement this, but I'm not sure if it's necessary. Ihe network interface templates allow you to specify either either the actual interface name ("eth0", "eth1", "enp0s25") or a set of numbered interfaces ("nic1", "nic2", "nic3").

Comment 3 Dan Macpherson 2016-03-21 01:58:05 UTC

*** Bug 1319333 has been marked as a duplicate of this bug. ***

Comment 6 Lucy Bopf 2016-03-24 01:09:39 UTC

Thanks, Dan.

I have confirmed with the requester that the requirements for this bug are now complete.

Moving to VERIFIED.

Comment 7 Andrew Dahms 2016-04-13 04:55:16 UTC

This content is now live on the Customer Portal.

Closing.