Bug 1809165 - [Doc RFE] Document how to deploy RHHI-V 1.8
Summary: [Doc RFE] Document how to deploy RHHI-V 1.8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhhiv-1.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHHI-V 1.8
Assignee: Disha Walvekar
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: RHHI-V-1.8-Documentation-RFE-BZs
TreeView+ depends on / blocked
 
Reported: 2020-03-02 14:14 UTC by Anjana Suparna Sriram
Modified: 2020-08-11 13:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-11 13:15:26 UTC
Embargoed:
dwalveka: needinfo-


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2020-03-02 14:14:16 UTC
User Story: As a deployment operator, I need to know how to install RHHI-V 1.8 without having to navigate to additional documentation to complete deployment.

Content Plan: https://docs.google.com/document/d/1jsDzppkhlD1o_WYxK4TVnLg8Cgj3-ou7ajohI5RF6Hg/edit?usp=sharing

Comment 7 SATHEESARAN 2020-07-21 07:22:30 UTC
Chapter-11 point-3 (iii), under specify hosts, there is a mention of a note:
"Ensure that you specify the hyperconverged host that can SSH using key pairs as Host1"

This statement doesn't convey the right meaning.I do not see any usefulness rather may be raising ambiguity.

Please remove this statement

Comment 8 SATHEESARAN 2020-07-21 08:11:09 UTC
Few more changes:

1. Update the brick tab screenshot ( under specify bricks ) to reflect the 'Select Host' name as 'server1-backend.example.com', to maintain consistency with first hosts FQDN
2. Device Name for luks_device is suggested to be luks_device, but the format should be '/dev/mapper/luks_sdX'

Comment 9 SATHEESARAN 2020-07-21 11:29:05 UTC
Also remove 'Logical Size' option explanation under 'Specify Bricks' section, as this option is
no longer available.

<snip>
Enable Dedupe & Compression
    Specify whether to provision the volume using VDO for compression and deduplication at deployment time. 
Logical Size (GB)
    Specify the logical size of the VDO volume. This can be up to 10 times the size of the physical volume, with an absolute maximum logical size of 4 PB. 
</snip>

But the information about logical size becomes the 10 times the size of physical volume is the worthy information to retain
So update that as:

<snip>
Enable Dedupe & Compression
    Specify whether to provision the volume using VDO for compression and deduplication at deployment time. When enabling dedupe & compression,
    the logical size of that brick is expanded to 10 times the size of the physical volume as the result of VDO space savings.
       Note: When enabling dedupe & compression, enable it on all the bricks part of the volume
</snip>

Comment 10 SATHEESARAN 2020-07-21 12:33:31 UTC
chapter-12, procedure step 2 -> Says "Enter the following details and click Validate for FQDN fields."
There is no 'Validate' button with hosted engine deployment, so just remove 'click validate for FQDN fields'

Comment 11 SATHEESARAN 2020-07-21 16:41:53 UTC
Few more changes:

1. Deployment guide, chapter-12, procedure step-3

"Enter the password to be used by the admin account in the Administration Portal. You can also specify an email address for notifications, which requires further configuration after deployment; see Chapter 15, Post-deployment configuration suggestions. "

This statement means that there is additional config required post deployment,
but this is not right. This notification can also be configured post dedployment; see chapter 15 is the right way


2. Chapter-12, Procedure step-5
" 5. Specify storage for the Hosted Engine virtual machine

    i) Specify the primary host and the location of the engine volume. "

The information in this tab is pre-populated and customers needs to just validate those.
So Update the title to '5. Validate storage for the Hosted Engine virtual machine'
and remove (i). No need for the statement to specify primary host.

3. Update screenshot under chapter-12, procedure step 8.
The screenshot shows 1 host in the cluster.

Comment 13 SATHEESARAN 2020-07-22 06:34:02 UTC
Screenshots correction required for screenshots in Chapter-12, procedure step-5 and step-6,
as the hostnames of the servers have IP address.

Comment 15 SATHEESARAN 2020-07-29 02:06:12 UTC
Verified with the doc link, all the following new enhancements are covered
 -  new enhancements in web console and information related to blacklist device changes are well covered
 -  Changes related to IPV6 flow in cockpit is explained well
 -  All the screenshots show the information about the latest install workflow.


Note You need to log in before you can comment on or make changes to this bug.