Skip to content

Jof vernum13 cp #221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 23, 2021
Merged

Jof vernum13 cp #221

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bafbb5e
first set of changes
JoanneOFlynn2018 Jun 23, 2021
1896c2d
Changes to assembly
JoanneOFlynn2018 Jun 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 2 additions & 13 deletions doc-Service-Telemetry-Framework/assemblies/assembly_advanced-features.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,3 @@
// This assembly is included in the following assemblies:
//
// <List assemblies here, each on a new line>

////
Retains the context of the parent assembly if this assembly is nested within another assembly.
For more information about nesting assemblies, see: https://redhat-documentation.github.io/modular-docs/#nesting-assemblies
See also the complementary step on the last line of this file.
////

ifdef::context[:parent-context: {context}]


[id="assembly-advanced-features_{context}"]
= Advanced features

Expand All @@ -28,7 +15,9 @@ The following optional features can provide additional functionality to the {Pro
* xref:high-availability_assembly-advanced-features[]
* xref:dashboards_assembly-advanced-features[]
* xref:ephemeral-storage_assembly-advanced-features[]
ifdef::include_when_16[]
* xref:monitoring-resource-usage-of-openstack-services_assembly-advanced-features[]
endif::include_when_16[]
* xref:creating-a-route-in-ocp_assembly-advanced-features[]

// Customizing the deployment (manifest overrides)
Expand Down
2 changes: 1 addition & 1 deletion doc-Service-Telemetry-Framework/docinfo.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
<title>Service Telemetry Framework 1.3</title>
<subtitle>Installing and deploying Service Telemetry Framework 1.3</subtitle>
<productname>Red Hat OpenStack Platform</productname>
<productnumber>16.1</productnumber>
<productnumber>13</productnumber>
<pubsnumber>0</pubsnumber>
<abstract>
<para>
Expand Down
2 changes: 1 addition & 1 deletion doc-Service-Telemetry-Framework/master.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
= Service Telemetry Framework 1.3
OpenStack Documentation Team <rhos-docs@redhat.com>
:imagesdir: images
:vernum: 16.1
:vernum: 13
:toc: left
:toclevels: 3
:icons: font
Expand Down
2 changes: 2 additions & 0 deletions ...ework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,10 @@
[role="_abstract"]
To label traffic according to the cloud of origin, you must create a configuration with cloud-specific instance names. Create an `stf-connectors.yaml` file and adjust the values of `CeilometerQdrEventsConfig`, `CeilometerQdrMetricsConfig` and `CollectdAmqpInstances` to match the AMQP address prefix scheme.

ifdef::include_when_16[]
[NOTE]
If you enabled container health and API status monitoring, you must also modify the `CollectdSensubilityResultsChannel` parameter. For more information, see xref:monitoring-container-health-and-api-status_assembly-advanced-features[].
endif::include_when_16[]

.Prerequisites

Expand Down