Skip to content

Oadp 5634 improving threescale user story #89491

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 4 additions & 0 deletions _topic_maps/_topic_map.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3660,6 +3660,10 @@ Topics:
Topics:
- Name: Backing up and restoring 3scale by using OADP
File: backing-up-and-restoring-3scale-by-using-oadp
- Name: Backing up 3scale by using OADP
File: backing-up-3scale-by-using-oadp
- Name: Restoring 3scale by using OADP
File: restoring-3scale-by-using-oadp
- Name: OADP Data Mover
Dir: installing
Topics:
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
:_mod-docs-content-type: ASSEMBLY
[id="backing-up-3scale-by-using-oadp"]
= Backing up 3scale by using OADP
include::_attributes/common-attributes.adoc[]
:context: backing-up-3scale-by-using-oadp

toc::[]

You can back up 3scale by backing up 3scale Operator, and databses such as mysql and Redis.

include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]

include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources
* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]

include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]

include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
:_mod-docs-content-type: ASSEMBLY
[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
[id="backing-up-and-restoring-3scale-by-using-oadp"]
= Backing up and restoring 3scale by using OADP
include::_attributes/common-attributes.adoc[]
:context: backing-up-and-restoring-3scale-by-using-oadp
Expand All @@ -15,29 +15,9 @@ In this example, the non-service affecting approach is used to back up and resto
Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
====

You can xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[back up 3scale] and xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[restore 3scale] by using OADP.

.Prerequisites

* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].

include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]

include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources
* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]

include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]

include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]

include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]

include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]

include::modules/restoring-the-backend-redis-database.adoc[leveloffset=+1]

include::modules/scaling-up-the-3scale-operator-and-deployment.adoc[leveloffset=+1]
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
:_mod-docs-content-type: ASSEMBLY
[id="restoring-3scale-by-using-oadp"]
= Restoring 3scale by using OADP
include::_attributes/common-attributes.adoc[]
:context: restoring-3scale-by-using-oadp

toc::[]

You can restore the 3scale by restoring the backed up 3scale Operator resources, and databses such as mysql and Redis. Once the data has been restored, you can scale up the 3scale Operator and deployment.

include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]

include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]

include::modules/restoring-the-backend-redis-database.adoc[leveloffset=+1]

include::modules/scaling-up-the-3scale-operator-and-deployment.adoc[leveloffset=+1]
2 changes: 1 addition & 1 deletion modules/backing-up-the-mysql-database.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ spec:
$ oc create -f ts_pvc.yml
----

. Attach the PVC to the system database pod by editing the system database deployment to use the `mysql` dump:
. Attach the PVC to the system database pod by editing the `system-mysql` deployment to use the `mysql` dump:
+
[source,terminal]
----
Expand Down
4 changes: 2 additions & 2 deletions modules/scaling-up-the-3scale-operator-and-deployment.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,11 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
$ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
----

. Ensure that the 3scale Operator was deployed by running the following command:
. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command:
+
[source,terminal]
----
$ oc get deployment -n threescale
$ oc get pods -n threescale
----

. Scale up the deployments by executing the following script:
Expand Down