Bug 1802320 - [RHHIV] Document how to convert existing RHHI deployment to 4K support
Summary: [RHHIV] Document how to convert existing RHHI deployment to 4K support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Maintaining_RHHI
Version: rhhiv-1.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHHI-V 1.7.z Async Update
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1804071
TreeView+ depends on / blocked
 
Reported: 2020-02-12 21:51 UTC by Marina Kalinin
Modified: 2020-02-26 08:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-26 08:05:45 UTC
Embargoed:

Attachments (Terms of Use)
Specify_hosts_screenshot (37.33 KB, image/png)
2020-02-24 09:50 UTC, SATHEESARAN 		no flags Details
specify_volume_screenshot (23.79 KB, image/png)
2020-02-24 09:50 UTC, SATHEESARAN 		no flags Details
specify_bricks (51.44 KB, image/png)
2020-02-24 09:51 UTC, SATHEESARAN 		no flags Details
Final review tab (53.46 KB, image/png)
2020-02-24 09:51 UTC, SATHEESARAN 		no flags Details
View All

Description Marina Kalinin 2020-02-12 21:51:13 UTC 
With RHHI-V 1.7 will support 4K Storage Domains. However, it is not a user transparent conversion.

A new domain will need to be created and the old one would need to be migrated over. This should be documented.
Comment 13 SATHEESARAN 2020-02-24 09:50:05 UTC 
Created attachment 1665352 [details]
Specify_hosts_screenshot

First tab of volume create - Specify Host
Comment 14 SATHEESARAN 2020-02-24 09:50:39 UTC 
Created attachment 1665353 [details]
specify_volume_screenshot
Comment 15 SATHEESARAN 2020-02-24 09:51:22 UTC 
Created attachment 1665354 [details]
specify_bricks
Comment 16 SATHEESARAN 2020-02-24 09:51:55 UTC 
Created attachment 1665355 [details]
Final review tab
Comment 17 SATHEESARAN 2020-02-24 09:53:10 UTC 
Laura,

I have updated the screenshots and also replaced IPs with recommended approach of using FQDNs ( host{1,2,3}.example.com )
Note You need to log in before you can comment on or make changes to this bug.