refined the topology-specific config procedure #511
Conversation
docs_user/modules/proc_retrieving-topology-specific-service-configuration.adoc
Show resolved
Hide resolved
| [IMPORTANT] | ||
| After the source control plane services are shut down, if any of the exported | ||
| values are lost, the values cannot be evaluated again. To avoid data loss, preserve the exported values in an environment file before shutting down the control plane services. |
There was a problem hiding this comment.
@matbu I have the following questions regarding this note:
- What is meant by “the values cannot be evaluated again”?
- Is this note referring to when customers stop their RHOSP services in section 3.5?https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0-beta/html-single/adopting_a_red_hat_openstack_platform_17.1_deployment/index#stopping-openstack-services_migrating-databases
- Does this note apply more to step 6, where we're telling customers to store the variables for future use?
There was a problem hiding this comment.
the values cannot be evaluated again - if we re-run the commands, they will fail as there are no longer control plane services running on the source cloud to get the data from (and those cannot be started back).
klgill
force-pushed
the
Docs-Refine-Retrieving-topology-specific-service-config
branch
from
a7109c4
to
615cd62
Compare
| @@ -4,7 +4,7 @@ | |||
|
|
|||
| = Migrating databases to the control plane | |||
|
|
|||
| To begin creating the control plane, enable backend services and import the databases from your original {rhos_prev_long} {rhos_prev_ver} deployment. | |||
| To begin creating the control plane, enable back-end services and import the databases from your original {rhos_prev_long} {rhos_prev_ver} deployment. | |||
There was a problem hiding this comment.
Is this assembly/user story just the beginning (To begin creating the control plane) of the creation of the control plane? I'd like to see a complete picture (super procedure) somewhere of the list of user stories in order, that you must complete.
There was a problem hiding this comment.
@JoanneOFlynn2018 I have a plan to write an adoption workflow checklist, which would detail the preparation, main adoption procedure, and post-adoption tasks. Is that what you're referring to?
docs_user/modules/proc_retrieving-topology-specific-service-configuration.adoc
Outdated
Show resolved
Hide resolved
| values in an environment file should protect you from such a situation. | ||
| [IMPORTANT] | ||
| After the {OpenStackShort} control plane services are shut down, if any of the exported | ||
| values are lost, re-running the command fails because the values cannot be evaluated again. To avoid data loss, preserve the exported values in an environment file before shutting down the control plane services. |
There was a problem hiding this comment.
Will the user understand "the values cannot be evaluated again"?
There was a problem hiding this comment.
I have elaborated the meaning in the comment above: "the values cannot be evaluated again" - if we re-run the commands, they will fail as there are no longer control plane services running on the source cloud to get the data from (and those cannot be started back).
Feel free to rephrase, with preserving the original intent
There was a problem hiding this comment.
Thanks @bogdando . When you say "re-run the commands", do you mean the "export" commands specifically, or any commands in this procedure?
There was a problem hiding this comment.
None of the commands in this chapter would work after its related services stopped on the source cloud
klgill
force-pushed
the
Docs-Refine-Retrieving-topology-specific-service-config
branch
from
7c21d20
to
64b8839
Compare
@matbu Can you please review my edits to the "Retrieving topology-specific service configuration" procedure and address the questions I've asked on this PR?
Thank you.