Skip to content

Jof mas minor edits 1.5 #421

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 3 commits into from
Dec 9, 2022
Merged

Jof mas minor edits 1.5 #421

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ce7c855
changes to Primary parameters of the ServiceTelemetry object
JoanneOFlynn2018 Dec 8, 2022
75b5880
Minor edits mostly reducing future tense
JoanneOFlynn2018 Dec 8, 2022
5288102
Apply suggestions from code review
JoanneOFlynn2018 Dec 8, 2022
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
9 changes: 2 additions & 7 deletions ...ry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,6 @@ The `ServiceTelemetry` object comprises the following primary configuration para

You can configure each of these configuration parameters to provide different features in an {ProjectShort} deployment.

[IMPORTANT]
====
Support for `servicetelemetry.infra.watch/v1alpha1` was removed from {ProjectShort} 1.3.
====

[id="backends_{context}"]
[discrete]
== The backends parameter
Expand Down Expand Up @@ -129,7 +124,7 @@ Use the `pvcStorageRequest` parameter to define the minimum required volume size

.Procedure

* List the available storage classes:
. List the available storage classes:
+
[source,bash,options="nowrap"]
----
Expand All @@ -140,7 +135,7 @@ standard (default) kubernetes.io/cinder Delete WaitForFirstCons
standard-csi cinder.csi.openstack.org Delete WaitForFirstConsumer true 20h
----

* Configure the `ServiceTelemetry` object:
. Configure the `ServiceTelemetry` object:
+
[source,yaml]
----
Expand Down
7 changes: 4 additions & 3 deletions ...ework/modules/proc_checking-for-an-expired-amq-interconnect-ca-certificate.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
= Checking for an expired {MessageBus} CA certificate

[role="_abstract"]
When the CA certificate expires the {MessageBus} connections will remain up, but will be unable to reconnect if they are interrupted. Eventually you will find that some or all of the connections from your {Openstack} ({OpenStackShort}) Routers have failed, showing errors on both sides, and the expiry (or "Not After") field in your CA certificate will be in the past.
When the CA certificate expires, the {MessageBus} connections remain up, but cannot reconnect if they are interrupted. Eventually, some or all of the connections from your {Openstack} ({OpenStackShort}) dispatch routers fail, showing errors on both sides, and the expiry or *Not After* field in your CA certificate is in the past.

.Procedure

Expand All @@ -14,7 +14,7 @@ When the CA certificate expires the {MessageBus} connections will remain up, but
$ oc project service-telemetry
----

. Check that some or all Router connections have failed:
. Verify that some or all dispatch router connections have failed:
+
[source,bash,options="nowrap"]
----
Expand All @@ -32,7 +32,8 @@ $ oc logs -l application=default-interconnect | tail
----

. Log into your {OpenStackShort} undercloud.
. Check for this error in the {OpenStackShort}-hosted {MessageBus} logs of a node where the connection has failed:

. Check for this error in the {OpenStackShort}-hosted {MessageBus} logs of a node with a failed connection:
+
[source,bash,options="nowrap"]
----
Expand Down
9 changes: 5 additions & 4 deletions ...emetry-Framework/modules/proc_updating-the-amq-interconnect-ca-certificate.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
= Updating the {MessageBus} CA certificate

[role="_abstract"]
To update the {MessageBus} certificate, you will need to export it from {OpenShift} and copy it to your {OpenStack} ({OpenStackShort}) nodes.
To update the {MessageBus} certificate, you must export it from {OpenShift} and copy it to your {OpenStack} ({OpenStackShort}) nodes.

.Procedure

Expand All @@ -21,13 +21,14 @@ $ oc project service-telemetry
$ oc get secret/default-interconnect-selfsigned -o jsonpath='{.data.ca\.crt}' | base64 -d > STFCA.pem
----

. Copy STFCA.pem to your {OpenStackShort} undercloud.
. Copy `STFCA.pem` to your {OpenStackShort} undercloud.
. Log into your {OpenStackShort} undercloud.
. Edit the stf-connectors.yaml file to contain the new caCertFileContent (For more information, see xref:configuring-the-stf-connection-for-the-overcloud_assembly-completing-the-stf-configuration[])
. Edit the `stf-connectors.yaml` file to contain the new caCertFileContent. For more information, see xref:configuring-the-stf-connection-for-the-overcloud_assembly-completing-the-stf-configuration[].
+
[NOTE]
You do not need to perform an overcloud deploy after performing the steps below. We edit the stf-connectors.yaml file only to make sure that future deployments will not overwrite the new CA certificate.

. Copy the STFCA.pem file to each {OpenStackShort} overcloud node:
. Copy the `STFCA.pem` file to each {OpenStackShort} overcloud node:
+
[source,bash,options="nowrap"]
----
Expand Down