Bug 1521102 - [RFE] Change 'Standard' term in cockpit deployment to 'Hosted Engine Only Deployment'
Summary: [RFE] Change 'Standard' term in cockpit deployment to 'Hosted Engine Only Dep...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhi-1.1
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: RHHI-V 1.5
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1523573
Blocks: 1724792 1520833 1536132
TreeView+ depends on / blocked
 
Reported: 2017-12-05 19:48 UTC by Dave
Modified: 2019-06-28 16:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1523573 (view as bug list)
Environment:
Last Closed: 2018-11-08 05:37:25 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:3523 0 None None None 2018-11-08 05:38:25 UTC

Description Dave 2017-12-05 19:48:18 UTC 
Description of problem:
The term 'standard' is a bit ambiguous.


Expected results:
Might want to change 'standard' to Hosted Engine Only Deployment and explain that this is to be used when gluster has already been installed/deployed/configured (Or add a note that standard will not setup gluster).


Additional info:
This would lead to a better UX experience and prevent user confusion. Documentation should reflect this as well
Comment 5 Dave 2018-01-18 18:56:28 UTC 
CSS Update: after additional thought having a third option for RH-HI deployment would be the preferred approach.
Comment 6 SATHEESARAN 2018-05-06 17:59:15 UTC 
Tested with cockpit-ovirt-dashboard-0.11.23

The statements under the topic are made very clear
Comment 7 Dave 2018-05-21 17:16:25 UTC 
Bug Scrub: As CS&S is currently only testing RHHI 1.1 we cannot verify this due to scope. I am comfortable closing this is SAS is confident with the outcome.
Comment 9 errata-xmlrpc 2018-11-08 05:37:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:3523
Note You need to log in before you can comment on or make changes to this bug.