-
Notifications
You must be signed in to change notification settings - Fork 165
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.
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
procedures: Add PostgreSQL migration guides #2163
Conversation
Signed-off-by: Anatolii Bazko <[email protected]>
Signed-off-by: Anatolii Bazko <[email protected]>
Signed-off-by: Anatolii Bazko <[email protected]>
@tolusha I see merge conflicts, can you resolve them or do you need assistance? |
|
||
:context: migration-to-external-database-setup | ||
|
||
Follow the procedures below to migrate from internal to external database setup successfully without any data loss. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow the procedures below to migrate from internal to external database setup successfully without any data loss. | |
You can migrate from the internal database to an external database without losing data. |
|
||
By the 11th of November, 2021, the PostgreSQL version 9.6 came out of support, and {prod-short} team recommends that all users undergo migrating to version 13. | ||
|
||
Follow the procedures below to migrate to a newer version of PostgreSQL successfully without any data loss. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow the procedures below to migrate to a newer version of PostgreSQL successfully without any data loss. | |
You can upgrade to a newer version of PostgreSQL without losing data. |
|
||
:context: migration-from-postgresql-9-to-postgresql-13 | ||
|
||
By the 11th of November, 2021, the PostgreSQL version 9.6 came out of support, and {prod-short} team recommends that all users undergo migrating to version 13. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a release note to me. If we need to tell this information to customers, I propose that we create a release note and link to this procedure from the release note.
Let me know what you think about this possibility.
:parent-context-of-migration-from-postgresql-9-to-postgresql-13: {context} | ||
|
||
[id="migration-from-postgresql-9-to-postgresql-13_{context}"] | ||
= Migration from PostgreSQL 9 to PostgreSQL 13 | ||
|
||
:context: migration-from-postgresql-9-to-postgresql-13 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:parent-context-of-migration-from-postgresql-9-to-postgresql-13: {context} | |
[id="migration-from-postgresql-9-to-postgresql-13_{context}"] | |
= Migration from PostgreSQL 9 to PostgreSQL 13 | |
:context: migration-from-postgresql-9-to-postgresql-13 | |
:parent-context-of-upgrading-postgresql: {context} | |
[id="upgrading-postgresql_{context}"] | |
= Upgrading PostgreSQL | |
:context: upgrading-postgresql |
|
||
include::partial$snip_verification-che-working.adoc[] | ||
|
||
:context: {parent-context-of-migration-from-postgresql-9-to-postgresql-13} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:context: {parent-context-of-migration-from-postgresql-9-to-postgresql-13} | |
:context: {parent-context-of-upgrading-postgresql} |
|
||
:context: migration-from-helm-charts-to-operator | ||
|
||
Follow the procedures below to migrate from Helm Charts to Operator successfully without any data loss. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow the procedures below to migrate from Helm Charts to Operator successfully without any data loss. | |
You can migrate from Helm Charts to Operator without losing data. |
[id="migration-to-external-database-setup"] | ||
:navtitle: Migration to external database setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[id="migration-to-external-database-setup"] | |
:navtitle: Migration to external database setup | |
[id="migration-to-an-external-database-setup"] | |
:navtitle: Migration to an external database setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll probably need to change the file name too.
:keywords: administration-guide, external-database, migration | ||
:page-aliases: .:migration-to-external-database-setup | ||
|
||
include::partial$assembly_migration-to-external-database-setup.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might have suggested renaming that file too.
:keywords: administration-guide, external-database, migration | ||
:page-aliases: .:migration-to-external-database-setup | ||
|
||
include::partial$assembly_migration-to-external-database-setup.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
include::partial$assembly_migration-to-external-database-setup.adoc[] | |
include::partial$assembly_migration-to-an-external-database-setup.adoc[] |
[id="migration-from-postgresql-9-to-postgresql-13"] | ||
:navtitle: Migration from PostgreSQL 9 to PostgreSQL 13 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[id="migration-from-postgresql-9-to-postgresql-13"] | |
:navtitle: Migration from PostgreSQL 9 to PostgreSQL 13 | |
[id="upgrading-postgresql"] | |
:navtitle: Upgrading PostgreSQL |
|
||
include::partial$proc_migration_from_postgresql_9_to_postgresql_13.adoc[] | ||
include::partial$assembly_migration-from-postgresql-9-to-postgresql-13.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
include::partial$assembly_migration-from-postgresql-9-to-postgresql-13.adoc[] | |
include::partial$assembly_upgrading-postgresql.adoc[] |
@@ -45,8 +45,10 @@ | |||
*** xref:define-backup-server-for-operator.adoc[] | |||
** xref:persistent-volumes-backups.adoc[] | |||
** xref:external-database-setup.adoc[] | |||
** xref:migration-to-external-database-setup.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
** xref:migration-to-external-database-setup.adoc[] | |
** xref:migration-to-an-external-database-setup.adoc[] |
@@ -45,8 +45,10 @@ | |||
*** xref:define-backup-server-for-operator.adoc[] | |||
** xref:persistent-volumes-backups.adoc[] | |||
** xref:external-database-setup.adoc[] | |||
** xref:migration-to-external-database-setup.adoc[] | |||
|
|||
* xref:migration-from-postgresql-9-to-postgresql-13.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* xref:migration-from-postgresql-9-to-postgresql-13.adoc[] | |
* xref:upgrading-postgresql.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Anatolii, I reviewed the files. If you go through my suggestions and apply those that you agree with, then after that I will clone this branch and review and preview this PR locally to make any remaining edits, and then you will see/approve my final changes when I open a PR to your branch.
⚡️ Deploying pull request preview... |
I committed/applied some of my minor suggestions (like adding |
Closing this PR after discussing it with @tolusha. |
Signed-off-by: Anatolii Bazko [email protected]
What does this pull request change?
What issues does this pull request fix or reference?
chectl server:deploy --installer=helm
as described in the official documentation for "Installing Che on AWS" che#20712Specify the version of the product this pull request applies to
Pull Request checklist
The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.
Validate language on files added or modified
step reports no vale warnings.