Bug 1642224

Summary: Document single node RHHI deployment using cockpit
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, lbailey, rcyriac, rhs-bugs, sabose, sankarshan, seamurph
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: 2019-05-20 04:43:20 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-10-24 03:30:11 UTC 
Description of problem:
-----------------------
Single node RHHI deployment feature is made available with RHHI 2.0 (RHV 4.2.7).
This feature should be documented with proper screenshots in RHHI for Virtualization for DC guide ( Dalton use case guide )

Version-Release number of selected component (if applicable):
------------------------------------------------------------
RHHI 2.0 RHHI4V for DC guide

Expected results:
-----------------
Include cockpit way of deployment of single node

Additional info:
----------------
Let me attach the required screenshots to this bug
Comment 8 SATHEESARAN 2018-11-06 16:20:13 UTC 
Couple of changes required

1. Chapter 4, section 4.1, point 2 has a older screenshot which states RHV version as 4.2.3 & RHEL 7.5. Its better to have the screenshot without RHV & RHEL version and make that generic

2. Chapter 4, section 4.1, point 4 asks user to select volume type as 'distribute' which will not be available in the dropdown. Here we should  inform the user to use 'replica' though the volume type 'distribute' will be created. This is a known_issue already documented in release notes

Except this all looks good

@Laura, could you make the relevant changes ?