From 41fe278b28153ce0f4c1dfb514baf0924b234045 Mon Sep 17 00:00:00 2001 From: Zack Kayyali Date: Mon, 5 Jun 2023 16:32:02 -0400 Subject: [PATCH] 2.2 - Add final ops image references --- .../proc-aap-aws-application-upgrade.adoc | 12 ++++++++++-- .../proc-aap-aws-backup-and-recovery.adoc | 18 ++++++++++-------- .../proc-aap-aws-create-extension-nodes.adoc | 10 +++++++++- .../proc-aap-aws-removing-extension-nodes.adoc | 10 +++++++++- .../proc-aap-gcp-application-upgrade.adoc | 10 +++++++++- .../topics/proc-aap-gcp-backup-process.adoc | 10 +++++++++- .../topics/proc-aap-gcp-restore-process.adoc | 10 +++++++++- 7 files changed, 65 insertions(+), 15 deletions(-) diff --git a/stories/topics/proc-aap-aws-application-upgrade.adoc b/stories/topics/proc-aap-aws-application-upgrade.adoc index d867ab348..41cbaaed7 100644 --- a/stories/topics/proc-aap-aws-application-upgrade.adoc +++ b/stories/topics/proc-aap-aws-application-upgrade.adoc @@ -110,12 +110,20 @@ The following instructions describe how to run the upgrade playbook. [NOTE] ===== -The Ansible on Clouds operational image tag must match with the version which you want to upgrade to. For example, if your foundation deployment version is 2.2.0, pull operational image with tag 2.2.20230215 to upgrade to version 2.2.20230215. +The Ansible on Clouds operational image tag must match with the version which you want to upgrade to. For example, if your foundation deployment version is 2.2.0, pull operational image with tag 2.2.20230211 to upgrade to version 2.2.20230211. ===== [source,bash] ---- -$ export IMAGE= +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 +$ docker pull $IMAGE +---- + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + +[source, bash] +---- +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- diff --git a/stories/topics/proc-aap-aws-backup-and-recovery.adoc b/stories/topics/proc-aap-aws-backup-and-recovery.adoc index 0b8420bc8..e052f6b41 100644 --- a/stories/topics/proc-aap-aws-backup-and-recovery.adoc +++ b/stories/topics/proc-aap-aws-backup-and-recovery.adoc @@ -31,14 +31,15 @@ Can use the AWS Backup Default Service Role for this which has the format `arn:a + [source,bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.20230215-00 +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 $ docker pull $IMAGE ---- -for EMEA regions (Europe, Middle East, Africa) run the command below instead -+ + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + [source, bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.20230215-00-limited +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- + @@ -151,14 +152,15 @@ The keypair used must exist in the aws region you are restoring to. + [source,bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.20230215-00 +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 $ docker pull $IMAGE ---- -for EMEA regions (Europe, Middle East, Africa) run the command below instead -+ + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + [source, bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.20230215-00-limited +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- + diff --git a/stories/topics/proc-aap-aws-create-extension-nodes.adoc b/stories/topics/proc-aap-aws-create-extension-nodes.adoc index 21b0f4af9..5bd8e3f46 100644 --- a/stories/topics/proc-aap-aws-create-extension-nodes.adoc +++ b/stories/topics/proc-aap-aws-create-extension-nodes.adoc @@ -15,7 +15,15 @@ The following procedure describes how to run the playbook to create the extensio + [source,bash] ---- -$ export IMAGE= +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 +$ docker pull $IMAGE +---- + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + +[source, bash] +---- +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- diff --git a/stories/topics/proc-aap-aws-removing-extension-nodes.adoc b/stories/topics/proc-aap-aws-removing-extension-nodes.adoc index 87b06ef4d..c1493ad9b 100644 --- a/stories/topics/proc-aap-aws-removing-extension-nodes.adoc +++ b/stories/topics/proc-aap-aws-removing-extension-nodes.adoc @@ -121,7 +121,15 @@ The `ansible-on-clouds-ops` container image tag must match the current installed [source,bash] ---- -$ export IMAGE= +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 +$ docker pull $IMAGE +---- + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + +[source, bash] +---- +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- diff --git a/stories/topics/proc-aap-gcp-application-upgrade.adoc b/stories/topics/proc-aap-gcp-application-upgrade.adoc index 206d9351e..1afc3be6a 100644 --- a/stories/topics/proc-aap-gcp-application-upgrade.adoc +++ b/stories/topics/proc-aap-gcp-application-upgrade.adoc @@ -105,7 +105,15 @@ For example, if your foundation deployment version is 2.2.1, pull the `ansible-o + [source,bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.1 +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 +$ docker pull $IMAGE +---- + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + +[source, bash] +---- +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- diff --git a/stories/topics/proc-aap-gcp-backup-process.adoc b/stories/topics/proc-aap-gcp-backup-process.adoc index defc4f3f9..dbbe5e059 100644 --- a/stories/topics/proc-aap-gcp-backup-process.adoc +++ b/stories/topics/proc-aap-gcp-backup-process.adoc @@ -66,7 +66,15 @@ For example, if your foundation deployment version is 2.2.1, pull the `ansible-o + [source,bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.1 +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 +$ docker pull $IMAGE +---- + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + +[source, bash] +---- +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ---- diff --git a/stories/topics/proc-aap-gcp-restore-process.adoc b/stories/topics/proc-aap-gcp-restore-process.adoc index 2e28af45b..9167b9739 100644 --- a/stories/topics/proc-aap-gcp-restore-process.adoc +++ b/stories/topics/proc-aap-gcp-restore-process.adoc @@ -75,7 +75,15 @@ For example, if your foundation deployment version is 2.2.1, pull the `ansible-o + [source,bash] ---- -$ export IMAGE=quay.io/ansible-on-clouds/ansible-on-clouds-ops:2.2.1 +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-rhel8:2.2.20230215 +$ docker pull $IMAGE +---- + +For EMEA regions (Europe, Middle East, Africa) run the following command instead: + +[source, bash] +---- +$ export IMAGE=registry.redhat.io/ansible-on-clouds/ansible-on-clouds-ops-emea-rhel8:2.2.20230215 $ docker pull $IMAGE ----