Bug 1649289 - RHHI-V 1.5 - Documentation - Single node deployments
Summary: RHHI-V 1.5 - Documentation - Single node deployments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhhiv-1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHHI-V 1.5.z Async
Assignee: Laura Bailey
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On:
Blocks: RHHIV-1.5.z-Doc-Backlog-BZs
TreeView+ depends on / blocked
 
Reported: 2018-11-13 10:35 UTC by Alessandro Arrichiello
Modified: 2019-05-20 04:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-20 04:46:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Alessandro Arrichiello 2018-11-13 10:35:50 UTC
Description of problem:
Hi,

In the Documentation for "DEPLOYING RED HAT HYPERCONVERGED INFRASTRUCTURE FOR VIRTUALIZATION ON A SINGLE NODE":
"Single node deployments cannot be scaled, and are not highly available."
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.5/html-single/deploying_red_hat_hyperconverged_infrastructure_for_virtualization_on_a_single_node/index

But instead in the general Deploying guide, this statement seems to leave door open for 1 node deployment and its scale up to 3:

"Red Hat Hyperconverged Infrastructure for Virtualization is supported for one node, and for clusters of 3, 6, 9, and 12 nodes.

The initial deployment is either 1 or 3 nodes."
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.5/html-single/deploying_red_hat_hyperconverged_infrastructure_for_virtualization/#rhhi-req-scaling


Is the scaling up from 1 to 3 supported or not?

Version-Release number of selected component (if applicable):
RHHI-V 1.5

Comment 9 Mugdha Soni 2019-01-29 06:17:16 UTC
The clarification for single node deployment is present in RHHI4V 1.5 documentation .
Hence moving the bug to verified state.


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