Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2017960

Summary: Update documentation to conform to new use_community deployment strategy
Product: Service Telemetry Framework Reporter: Leif Madsen <lmadsen>
Component: DocumentationAssignee: Chris Sibbitt <csibbitt>
Status: CLOSED CURRENTRELEASE QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact: Joanne O'Flynn <joflynn>
Priority: high    
Version: 1.4CC: csibbitt
Target Milestone: GAKeywords: FutureFeature, Triaged
Target Release: 1.4 (STF)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
When you install Service Telemetry Framework 1.4, the Service Telemetry Operator no longer requires Operators other than the Smart Gateway Operator to be installed as dependencies. As a result, administrators must now install other dependent Operators if you need to store metrics and events. For more information, see the installation chapter of the Service Telemetry Framework guide.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-03 14:27:56 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:
Embargoed:

Description Leif Madsen 2021-10-27 19:01:23 UTC 
In Service Telemetry Framework 1.4 we add a new API parameter to the ServiceTelemetry interface called `deploymentStrategy` with the options `use_community` (default, legacy), `use_community_sub`, `use_openshift`, and `none`.

We need to implement and update our existing documentation to make use of this new parameter and document the new values.

The use of `deploymentStrategy: use_community` effectively follows the existing deployment strategy present in STF 1.3 except that it will require one or two additional steps in the "3.1. Deploying STF to the OCP environment" module.

We'll need to add steps for deploying 2 additional Operators:

* prometheus (from OperatorHub.IO)
* AMQ Certificate Manager (from redhat-operators)

Previously STF would get these through the `requires` list added to the CSV. Those have been removed in order to allow the Service Telemetry Operator and Smart Gateway Operator to be deployed in a disconnected manner.

Installation of third-party software will now be done separately, opening the door to more flexible STF deployment scenarios.