Bug 1889196 - Detail Documentation for disconnected (or manually added) OpenShift Cluster-id
Summary: Detail Documentation for disconnected (or manually added) OpenShift Cluster-id
Keywords:
Status: NEW
Alias: None
Product: Cloud Software Services (cloud.redhat.com)
Classification: Red Hat
Component: Subscription Watch - Documentation
Version: unspecified
Hardware: All
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Matt Werner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-19 00:35 UTC by jalviso
Modified: 2020-11-06 08:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description jalviso 2020-10-19 00:35:20 UTC
Description of problem:

The following documentation is unclear and needs detailed section/description:

1.

https://access.redhat.com/documentation/en-us/subscription_central/2020-10/html/getting_started_with_subscription_watch/con-how-to-select-datacollection-tool_assembly-requirements-and-your-responsibilities-ctxt#red_hat_openshift

------>%<------
5.4. Red Hat OpenShift

Subscription watch is designed to work with customers who use Red Hat OpenShift 4.1 and later in connected environments. Customers with disconnected Red Hat OpenShift Container Platform environments can use Red Hat OpenShift as a data collection tool by manually creating each cluster in Red Hat OpenShift Cluster Manager. This workaround enables customers with disconnected environments to simulate an account-level view of their Red Hat OpenShift usage. For example, an organization with disconnected clusters distributed across several departments might find this workaround useful.

This workaround enables customers with disconnected environments to simulate an account-level view of their Red Hat OpenShift usage. For example, an organization with disconnected clusters distributed across several departments might find this workaround useful.
------>%<------

2.

https://access.redhat.com/documentation/en-us/subscription_central/2020-10/html/getting_started_with_subscription_watch/con-how-to-set-subscription-attributes_assembly-requirements-and-your-responsibilities-ctxt#setting_subscription_attributes_for_red_hat_openshift

------>%<------
6.2. Setting subscription attributes for Red Hat OpenShift

You can set subscription attributes from Red Hat OpenShift Cluster Manager for version 4. For version 3, you use the same reporting tools as those defined for RHEL.

Setting the subscription attributes for Red Hat OpenShift 4

You can set subscription attributes at the cluster level from Red Hat OpenShift Cluster Manager.

From the Clusters view, select a cluster to display the cluster details.
Click Edit Subscription Settings on the cluster details page or from the Actions menu.

Make any needed changes to the values for the subscription attributes and then save those changes.
------>%<------

3.

https://access.redhat.com/documentation/en-us/subscription_central/2020-10/html/getting_started_with_subscription_watch/proc-connecting-rhocp-to-subscriptionwatch_assembly-setting-up-subscriptionwatch-ctxt

------>%<------
CHAPTER 12. CONNECTING RED HAT OPENSHIFT TO SUBSCRIPTION WATCH

If you are using Red Hat OpenShift as the data collection tool, the steps you must do to connect to subscription watch depend on multiple factors. These factors include the installed version of Red Hat OpenShift Container Platform, whether you are working in a connected or disconnected environment, and whether you are using Red Hat Enterprise Linux, Red Hat Enterprise Linux CoreOS, or both as the operating system for clusters.

Subscription watch is designed to work with customers who use Red Hat OpenShift 4.1 and later in connected environments. For Red Hat OpenShift version 4.1 and later, this communication is enabled through connected Red Hat OpenShift Container Platform clusters, specifically, clusters that report data to Red Hat through Telemetry. These connected clusters can communicate through Red Hat OpenShift Cluster Manager to supply information to the data pipeline for subscription watch.

Customers with disconnected Red Hat OpenShift Container Platform 4.1 and later environments can use Red Hat OpenShift as a data collection tool by manually creating each cluster in Red Hat OpenShift Cluster Manager.
------>%<------

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

How reproducible: Always

Steps to Reproduce:

1. Refer to above 3 documentation link about disconnected OpenShift Cluster can be added and data can be collected.

Actual results:

No detailed information about how to do it and how does it works.


Expected results:

The documentation to provide a section about details of disconnected OpenShift cluster and:

a.) How can Subscription Watch collect data on a manually added OpenShift Cluster?
b.) How is this done? How does it works?
c) What relevant information are involve?
d) How to use the result?

Additional info:

According to the diagram below, data collection can be done on a connected OpenShift Cluster. 


(Reference:   Figure 18.2. The Red Hat OpenShift data pipeline for subscription watch  
https://access.redhat.com/documentation/en-us/subscription_central/2020-10/html/getting_started_with_subscription_watch/con-how-subscriptionwatch-gets-refreshes-data_assembly-opening-subscriptionwatch-ctxt )

Question:

For disconnected/manually added OpenShift Cluster, how is this done?

Comment 1 Masaki Hatada 2020-11-06 08:15:40 UTC
Hi Red Hat,

Case 02774294's owner guided us to this Bugzilla for Subscription Watch issue.

Our question is very simple.

Can Subscription Watch work with disconneced cluster?
If yes, how can we check which subscription we have was attached actually by Subscription Watch? 
If no, how can we attach subscription to disconnected cluster?

As I wrote at Bug 1886701, we have many subscripions and all of them are listed on https://access.redhat.com/management/subscriptions.
Each subscription has ach contract number, start/end date and so on.
So which subscription was attached is very important for us to manage our subscriptions.
If we cannot know that, we wouldn't be able to notice when subscription attached to the cluster expired.

Best Regards,
Masaki Hatada


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