Bug 1394543

Summary:	State clearly the support state of RHV/Insights integration and properly productize insights-coordinator-* components
Product:	Red Hat Hybrid Cloud Console (console.redhat.com)	Reporter:	Andrea Perotti <aperotti>
Component:	Documentation	Assignee:	Kevin Blake <kblake>
Status:	CLOSED WONTFIX	QA Contact:	Jeff Needle <jneedle>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	chenders, robwilli, wduffee
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-07 18:48:27 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:

Description Andrea Perotti 2016-11-13 09:54:14 UTC

Description of problem:
Among the various way on how to get in touch with Insights is reported to be also RHEV:

https://access.redhat.com/insights/getting-started/rhv/

But asking to customers to enable 3rd party repos unrelated to Red Hat, using a tool that is not installed by default on RHEL (yum-config-manager is part of yum-utils) make the experience very beta style and do not offer the level of confidence with a tool that should be fire and forget and production ready.

Also, suggesting to customers to avoid the gpg-check is a perpetration of some BAD security habits that should not be present on any official Red Hat Document.

Plus explain more clearly that this will allow you to put under insight all the components of your RHV infra, because Sat and CF pages are instead enabler for the final rhel clients, and if not stated clearly can set some wrong expectation that also the running RHEL VMs inside RHV will be somehow automagically analyzed.

How reproducible:
Always

Steps to Reproduce:
1. Go to https://access.redhat.com/insights/getting-started/rhv/
2. Follow the instructions

Expected results:
- if it's a beta component, state it clearly in the text, plus using some graphics sign. Bleeding edge customer could accept it, but have to be stated clearly.
- publish all the required rpms in the official repo: no external whatsoever repo have to be involved
- ensure the rpms works on all the major products out there (RHV4 too, not only RHEV3 - see #1394541)

All this is valid for OpenStack as well:
https://access.redhat.com/insights/getting-started/osp/
even if in there at least one time is reported the beta word.

Comment 1 Wesley Duffee-Braun 2016-11-14 16:05:40 UTC

Hello Andrea,

Right now the Insights for RH(E)V Coordinator is in beta, and as we've never had a GA'd Insights RH(E)V Coordinator so there isn't a place in the official repo for the packages. Once we are GA'd with the Coordinator we will be in an official repo.

Thank you for the documentation assessments. I have created AI's for us to improve our Coordinator docs based on the feedback.

We have also picked up and are working on BZ 1394541. Please let me know if you have any additional questions!

 - Wesley

Comment 2 Kevin Blake 2019-05-07 18:48:27 UTC

Closing because documentation no longer needed.