Bug 752462

Summary:	[RFE] Documentation update to Deployment Guide --> Networking section 8.2.2 from `alias bond0 bonding` to `alias netdev-bond0 bonding`
Product:	Red Hat Enterprise Linux 6	Reporter:	J.H.M. Dassen (Ray) <rdassen>
Component:	doc-Deployment_Guide	Assignee:	Stephen Wadeley <swadeley>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.3	CC:	alyoung, jekirkpa, mmilgram, rbinkhor
Target Milestone:	rc	Keywords:	Documentation, FutureFeature, Triaged
Target Release:	6.5
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-02 22:28:26 UTC	Type:	---
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:	607248, 806907

Description J.H.M. Dassen (Ray) 2011-11-09 15:31:05 UTC

3.  What is the nature and description of the request?

The customer would like to see the Deployment Guide's Networking Section
modified to suggest using `alias netdev-bond0 bonding` in place of `alias bond0
bonding` due to BZ 680360.

        4.  Why does the customer need this? (List the business requirements
        here)

The customer specifically requested for this enhancement after following the
documentation and receiving warning messages.

        5.  How would the customer like to achieve this? (List the functional
        requirements here)

The customer would like to see the official documentation updated to reflect
that `alias netdev-bond0 bonding` should be used in place of `alias bond0
bonding`

        6.  For each functional requirement listed in question 4, specify how
        Red Hat and the customer can test to confirm the requirement is
        successfully implemented.

Red Hat can modify the documentation and the customer can verify that it
appears similar to the warning message displayed.

        7.  Is there already an existing RFE upstream or in Red Hat bugzilla?

No, BZ 680360 describes the issue and the resolution, but does not include
documentation modification.

        8.  How quickly does this need resolved? (desired target release)

As soon as possible, pending resources.

        9.  Does this request meet the RHEL Bug and Feature Inclusion Criteria
        (please review)

Yes, documentation modification.

        10.  List the affected packages

N/A

        11.  Would the customer be able to assist in testing this functionality
        if implemented?

N/A