Bug 1600075

Summary: [day2]SSH public key authentication needs to be configured within the newly added hosts
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: doc-Maintaining_RHHIAssignee: Laura Bailey <lbailey>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.5CC: asriram, rhs-bugs, sankarshan
Target Milestone: ---   
Target Release: RHHI-V 1.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-17 09:32:21 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: 1534399    

Description SATHEESARAN 2018-07-11 11:25:43 UTC 
Description of problem:
-----------------------
Due to the limitation of sanity check script, the newly added hosts should have SSH public key authentication from the first new host to other hosts.

For example. Let us take host1, host2, host3 form the cluster POD. Now admin prefers to expand this cluster, with 3 more nodes host4, host5, host6. In this case, admin need to SSH public key authentication from host4 -> host4, host4 -> host5, host4-> host6


Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHHI 2.0 Day2 doc


Expected results:
----------------
Add documentation that there should be a SSH public key authentication from the following hosts:
1. First host in the cluster to all the hosts ( including the same host, and nodes to be expanded )
2. First host in the newly added set of 3 nodes to all the newly added nodes( including the self )