Bug 1493020

Summary: [Docs][SHE] Add link to Planning Guide networking recommendations from SHE guide
Product: Red Hat Enterprise Virtualization Manager Reporter: Yaniv Kaul <ykaul>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED CURRENTRELEASE QA Contact: Tahlia Richardson <trichard>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.1.6CC: apinnick, lbopf, lsurette, rbalakri, srevivo, ykaul
Target Milestone: ovirt-4.1.8   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-19 10:13:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2017-09-19 07:48:46 UTC
Description of problem:
You may need to create a bond, a VLAN or a VLAN on top of a bond for your hosted-engine deployment, ovirtmgmt, for its storage, whatever - this is completely missing from https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/self-hosted_engine_guide/chap-deploying_self-hosted_engine#Deploying_Self-Hosted_Engine_on_RHEL

Comment 3 Yaniv Kaul 2017-09-24 13:32:48 UTC
(In reply to Lucy Bopf from comment #2)
> Sorry, used internal links in Comment 1. Making private.
> 
> Public links are as follows:
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> html-single/planning_and_prerequisites_guide/#networking-requirements
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> html-single/planning_and_prerequisites_guide/#networking-considerations
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> html-single/planning_and_prerequisites_guide/#networking-recommendations

Only the last link is relevant. And is not referenced from the HE guide.

Comment 4 Lucy Bopf 2017-09-26 00:45:06 UTC
(In reply to Yaniv Kaul from comment #3)
> (In reply to Lucy Bopf from comment #2)
> > Sorry, used internal links in Comment 1. Making private.
> > 
> > Public links are as follows:
> > 
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> > html-single/planning_and_prerequisites_guide/#networking-requirements
> > 
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> > html-single/planning_and_prerequisites_guide/#networking-considerations
> > 
> > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> > html-single/planning_and_prerequisites_guide/#networking-recommendations
> 
> Only the last link is relevant. And is not referenced from the HE guide.

So, if we add a link from the SHE Guide to the last link in the list, that would address this bug?

Comment 5 Yaniv Kaul 2017-09-26 06:35:09 UTC
(In reply to Lucy Bopf from comment #4)
> (In reply to Yaniv Kaul from comment #3)
> > (In reply to Lucy Bopf from comment #2)
> > > Sorry, used internal links in Comment 1. Making private.
> > > 
> > > Public links are as follows:
> > > 
> > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> > > html-single/planning_and_prerequisites_guide/#networking-requirements
> > > 
> > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> > > html-single/planning_and_prerequisites_guide/#networking-considerations
> > > 
> > > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/
> > > html-single/planning_and_prerequisites_guide/#networking-recommendations
> > 
> > Only the last link is relevant. And is not referenced from the HE guide.
> 
> So, if we add a link from the SHE Guide to the last link in the list, that
> would address this bug?

Definitely a step in the right direction.

I think a production-quality example of setting up SHE would be great, eventually.

Comment 6 Lucy Bopf 2017-10-03 00:28:31 UTC
Thanks, Yaniv. We'll start with that for this bug, then, and raise a separate bug to track the production quality example, which we'll need to source from an SME.