Bug 1895755

Summary:	Deploying Red Hat Hyperconverged Infrastructure for Virtualization on a single node - network clarification
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Marcus West <mwest>
Component:	Documentation	Assignee:	Laura Bailey <lbailey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhhiv-1.8	CC:	dwalveka, mmuench, rhs-bugs, sasundar, storage-doc, storage-qa-internal
Target Milestone:	---
Target Release:	RHHI-V 1.8.z Async Update
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:	2021-05-18 06:13:47 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:	1898439

Description Marcus West 2020-11-09 00:54:50 UTC

From the docs, 6.2. (Copying SSH keys) shows how to copy to multiple hosts via multiple networks.  However this can be confusing as this is a single node cluster, so separate storage/management networks are not required.  It's also confusing that there are examples for multiple nodes (this is for single node deployment).

Chapter 2 mentions in the requirements: 

 *  1 Network Interface Controller 

So I'm assuming environments with a single network are permitted.

What I'd like to see is:

* Chapter 2 - clarify that, while multiple networks are recommended/supported, only one is needed.
* Chapter 6.2 - remove the examples for multiple nodes, add reminder (note) that multiple networks are recommended/supported, but not a hard requirement.


https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/deploying_red_hat_hyperconverged_infrastructure_for_virtualization_on_a_single_node/task-configure-key-based-ssh-auth-single-node#generating-ssh-key-pairs-without-password

Comment 4 SATHEESARAN 2020-12-01 06:17:02 UTC

(In reply to Marcus West from comment #0)
> From the docs, 6.2. (Copying SSH keys) shows how to copy to multiple hosts
> via multiple networks.  However this can be confusing as this is a single
> node cluster, so separate storage/management networks are not required. 
> It's also confusing that there are examples for multiple nodes (this is for
> single node deployment).
> 
> Chapter 2 mentions in the requirements: 
> 
>  *  1 Network Interface Controller 
> 
> So I'm assuming environments with a single network are permitted.
> 
> What I'd like to see is:
> 
> * Chapter 2 - clarify that, while multiple networks are
> recommended/supported, only one is needed.
> * Chapter 6.2 - remove the examples for multiple nodes, add reminder (note)
> that multiple networks are recommended/supported, but not a hard requirement.
> 
> 
> https://access.redhat.com/documentation/en-us/
> red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/
> deploying_red_hat_hyperconverged_infrastructure_for_virtualization_on_a_singl
> e_node/task-configure-key-based-ssh-auth-single-node#generating-ssh-key-
> pairs-without-password

Hello Marcus,

Thanks for the bug.

Chapter 2 clearly states that 'requires': 1 network interface controller
For single node RHHI-V deployment, single network is sufficient and required.
There is no recommendation to make use of 2 networks for single node deployment.

The changes in chapter 6.2 makes sense, and I will suggest the technical writer for those changes.

Comment 12 SATHEESARAN 2020-12-08 12:24:21 UTC

Verified with the internal doc link.
Chapter 6.2 now has updated content to copy ssh public key from the node to itself.
The irrelevant copy to host2 and host3 are now removed

Comment 13 SATHEESARAN 2021-05-18 06:13:47 UTC

The document is fixed and published