Adjustments and reworking some layouts #213
Merged
Conversation
This file contains hidden or 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
|
Sorry that this PR is so large. The refactoring got a bit away from me today, but I'm really happy how this turned out. I was doing testing between OSP13 and OSP16 configurations as well to verify that everything was aligning as it should. A few minor bugs and tweaks were found in the OSP13 docs as well, which should make importing this for OSP13 much much nicer. |
leifmadsen
force-pushed
the
stf13/multicloud_enable_stf
branch
from
60019d2 to
fc74218
Compare
Various adjustments and reworking some layout and placements across the documentation to help provide better guidance and to try and reduce jumping around the document. Focus is to make things more obvious during the OSP deployment for planning purposes rather than having administrators having to update their overcloud deployments. * Fix leveloffset for OSP overcloud configuration procedures * Update multicloud configuration to presume the enable-stf.yaml exists as part of the deployment in order to simplify configuration * Move OSP related configurations from advanced assembly in to OSP related assembly * Hide container and API monitoring when not deployed via OSP13 * Update multicloud configurations for latest STF * Various syntax clean ups and highlight controls * Synchronize overcloud deployment steps between various modules * Increase TOC levels generated from 2 to 3 * Re-jig the CA certificate configuration for OSP13 to be more in line with other OSP configuration steps * Add warning about not exceeding 19 chars between STF instance name and cloud names * Converted modules for container health checks and OSP service monitoring to be disabling rather than enabling since they are enabled by default in enable-stf.yaml now.
leifmadsen
force-pushed
the
stf13/multicloud_enable_stf
branch
from
fc74218 to
51b8108
Compare
doc-Service-Telemetry-Framework/assemblies/assembly_completing-the-stf-configuration.adoc
Outdated
Show resolved
Hide resolved
doc-Service-Telemetry-Framework/assemblies/assembly_completing-the-stf-configuration.adoc
Outdated
Show resolved
Hide resolved
doc-Service-Telemetry-Framework/assemblies/assembly_completing-the-stf-configuration.adoc
Outdated
Show resolved
Hide resolved
doc-Service-Telemetry-Framework/modules/con_configuring-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
...elemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
…k-environment-file-for-multiple-clouds.adoc Minor: Prereq tense change
...elemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
…k-environment-file-for-multiple-clouds.adoc Minor: Prereq tense change
...elemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
…k-environment-file-for-multiple-clouds.adoc Minor: Prereq tense change
...elemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
…k-environment-file-for-multiple-clouds.adoc Minor: punctuation
...elemetry-Framework/modules/proc_creating-openstack-environment-file-for-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
…k-environment-file-for-multiple-clouds.adoc Minor: remove should
doc-Service-Telemetry-Framework/modules/proc_deploying-smart-gateways.adoc
Outdated
Show resolved
Hide resolved
…ateways.adoc Minor: wording of warning
doc-Service-Telemetry-Framework/modules/proc_monitoring-container-health-and-api-status.adoc
Show resolved
Hide resolved
...ervice-Telemetry-Framework/modules/proc_monitoring-resource-usage-of-openstack-services.adoc
Show resolved
Hide resolved
…-the-stf-configuration.adoc Co-authored-by: JoanneOFlynn2018 <45287002+JoanneOFlynn2018@users.noreply.github.com>
…-the-stf-configuration.adoc Co-authored-by: JoanneOFlynn2018 <45287002+JoanneOFlynn2018@users.noreply.github.com>
…-the-stf-configuration.adoc Co-authored-by: JoanneOFlynn2018 <45287002+JoanneOFlynn2018@users.noreply.github.com>
Update the gnocchi-connectors.yaml based on feedback from repository testing changes in infrawatch/service-telemetry-operator@b38117d Signed-off-by: Leif Madsen <lmadsen@redhat.com>
doc-Service-Telemetry-Framework/modules/con_configuring-multiple-clouds.adoc
Outdated
Show resolved
Hide resolved
…le-clouds.adoc "Data stored by the Smart Gateway in to the data storage domain, is filtered by using the metadata created by each of the Smart Gateways."
JoanneOFlynn2018
approved these changes
Jun 21, 2021
|
Ready to merge. Just waiting for @mrunge for a quick review around the Gnocchi templates to match what we have in our testing repo. |
|
I'm going to merge this now to get things in sync. If we need to make adjustments to the gnocchi configuration we can do that separately. Risk is low here based on latest changes included. |
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.
Various adjustments and reworking some layout and placements across the
documentation to help provide better guidance and to try and reduce
jumping around the document. Focus is to make things more obvious during
the OSP deployment for planning purposes rather than having
administrators having to update their overcloud deployments.
as part of the deployment in order to simplify configuration
assembly
with other OSP configuration steps
cloud names
monitoring to be disabling rather than enabling since they are enabled
by default in enable-stf.yaml now.