[STF 1.3] Upgrading from STF 1.2 to STF 1.3 #235
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* first set of changes * Changes to assembly
Align the OSP13 base configuration for STF across OSP versions by setting the same default configuration as OSP16 where not defined. Signed-off-by: Leif Madsen <[email protected]>
* New assembly for upgrading to 1.2. Two new modules Reusing 1 module * Resolve issues with xref linking Cherry picked from commit 4f16e24 Co-authored-by: Leif Madsen <[email protected]>
The use of an empty clouds object results in an error in Service Telemetry Operator since a list is expected. Using an empty list will result in the expected outcome of no Smart Gateways being defined rather than an error.
leifmadsen
changed the title
|
This is a work in progress. Failure is expected. I am going to eat dinner now :) |
...etry-Framework/assemblies/assembly_upgrading-service-telemetry-framework-to-version-1-3.adoc
Outdated
Show resolved
Hide resolved
…service-telemetry-framework-to-version-1-3.adoc
...etry-Framework/assemblies/assembly_upgrading-service-telemetry-framework-to-version-1-3.adoc
Outdated
Show resolved
Hide resolved
…service-telemetry-framework-to-version-1-3.adoc
...etry-Framework/assemblies/assembly_upgrading-service-telemetry-framework-to-version-1-3.adoc
Outdated
Show resolved
Hide resolved
…service-telemetry-framework-to-version-1-3.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
Instead of having a versioned value for stf-catalog index image (which only contains AMQ Certificate Manager) migrate to using the stable tag instead.
…telemetry-framework-1-2-operators.adoc
…telemetry-framework-1-2-operators.adoc
* Adjust multi-cloud config to avoid extra topics When using collectd-write-qdr.yaml in a multi-cloud configuration, multiple topics will be published to as the defaults in collectd-write-qdr.yaml will be merged with the configured values in the stf-connectors.yaml. Directly load the resource_registry and collectd service directly in the stf-connectors.yaml instead. * Update doc-Service-Telemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc * Update doc-Service-Telemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc Co-authored-by: JoanneOFlynn2018 <[email protected]> * Update doc-Service-Telemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc Co-authored-by: JoanneOFlynn2018 <[email protected]> Co-authored-by: JoanneOFlynn2018 <[email protected]>
* adjust sensubility publish address * Update doc-Service-Telemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc Co-authored-by: Leif Madsen <[email protected]> * Update doc-Service-Telemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc Co-authored-by: Leif Madsen <[email protected]> * updates for new sensubility address * sensubility clarification * Update doc-Service-Telemetry-Framework/modules/proc_planning-amqp-address-prefixes.adoc Co-authored-by: Leif Madsen <[email protected]> * adjustments * some items OSP16 only * All SG output show show 2/2 pods * Update doc-Service-Telemetry-Framework/modules/proc_deploying-smart-gateways.adoc * Update doc-Service-Telemetry-Framework/modules/proc_deploying-smart-gateways.adoc * Update doc-Service-Telemetry-Framework/modules/proc_planning-amqp-address-prefixes.adoc Co-authored-by: JoanneOFlynn2018 <[email protected]> * Update doc-Service-Telemetry-Framework/modules/proc_planning-amqp-address-prefixes.adoc Co-authored-by: JoanneOFlynn2018 <[email protected]> Co-authored-by: Leif Madsen <[email protected]> Co-authored-by: JoanneOFlynn2018 <[email protected]>
The upstream ceilometer-write-qdr for Train is not in sync with the contents deployed downstream for ceilometer-write-qdr.yaml. The upstream implements the Publish parameters, but the current 16.1 deployment does not provide those. Added appropriate configuration required for RHOSP16.1. Signed-off-by: Leif Madsen <[email protected]>
Update import paths and add instructions for including new cloud events dashboard
When building all, build both the html and html13 documents. Add a new 'downstream' option so you can build for downstream testing as well.
…en-upgrading-to-1-3
Drop the subs +quotes for the oc patch command so that the content is correctly displayed in the code blocks.
The upgrade document doesn't need any +quotes subs for the code blocks. Dropping them to avoid any future issues.
leifmadsen
added
1.3
needs-backport
|
@JoanneOFlynn2018 I've done a final walk through and I'm pretty sure this is good to go for merge. I will backport it to the stable-1.3 branch after merge. Thanks! |
...etry-Framework/assemblies/assembly_upgrading-service-telemetry-framework-to-version-1-3.adoc
Outdated
Show resolved
Hide resolved
…service-telemetry-framework-to-version-1-3.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
...ice-Telemetry-Framework/modules/proc_removing-service-telemetry-framework-1-2-operators.adoc
Outdated
Show resolved
Hide resolved
…telemetry-framework-1-2-operators.adoc
JoanneOFlynn2018
approved these changes
Jul 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrade instructions for STF 1.3 from STF 1.2.