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

Bug 2196865

Summary:	Clarify AMQ Interconnect topic configuration for STF (parent)
Product:	Service Telemetry Framework	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	Leif Madsen <lmadsen>
Status:	CLOSED ERRATA	QA Contact:	Alex Yefimov <ayefimov>
Severity:	high	Docs Contact:	mgeary <mgeary>
Priority:	high
Version:	1.5	CC:	lmadsen
Target Milestone:	z2	Keywords:	Documentation, Triaged, ZStream
Target Release:	1.5 (STF)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	The documentation at "Configuring the STF connection for the overcloud" has been updated to clarify the Interconnect topic parameters and how it relates to the topic address configured for cloud configurations in the ServiceTelmetry object.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-22 19:06:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2189677, 2189678
Bug Blocks:

Description Direct Docs Feedback 2023-05-10 14:50:17 UTC

Format example provided for Ceilometer configuration options is confusing

The format for the Ceilometer topic configuration is confusing as it shows the entire format that would be provided to the Smart Gateway configuration.

On the OSP side, the topic should actually be set to just the unique portion, such as `cloud1-metering` instead of `anycast/ceilometer/cloud1-metering.sample` which does get populated on the STF side, but not in the OSP configuration side.

Should make it clear that the resulting topic is anycast/ceilometer/.sample but that only the  part needs to be defined here.

Reported by: lmadsen

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/service_telemetry_framework_1.5/assembly-completing-the-stf-configuration_assembly#annotations:10bdd8e0-b2b7-4be1-9ce0-9062fc95f68f

Comment 1 Leif Madsen 2023-05-17 16:01:15 UTC

This is effectively a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2189678 and https://bugzilla.redhat.com/show_bug.cgi?id=2189677

I'm going to track all of these together to make sure they are covered.

Comment 2 Leif Madsen 2023-06-05 20:00:02 UTC

Documentation patch is up to cover this as a parent issue and the two child issues (Depends On): https://github.com/infrawatch/documentation/pull/467

Comment 9 errata-xmlrpc 2023-06-22 19:06:03 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 (Release for Service Telemetry Framework 1.5.2), 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-2023:3785