Skip to content

Replaced install versions with attribute #1200

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.

Sign up for GitHub

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 1 commit into
base: main
Choose a base branch
from
Open

Replaced install versions with attribute #1200

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions downstream/modules/platform/proc-editing-inventory-file-for-updates.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,16 +10,16 @@ You can keep the same parameters from your existing {PlatformNameShort} deployme
. Navigate to the installation program directory.
Bundled installer::
+
[source,options="nowrap",subs=attributes+]
[source,options="nowrap",subs="+attributes"]
-----
$ cd ansible-automation-platform-setup-bundle-2.4-1-x86_64
$ cd ansible-automation-platform-setup-bundle-{AnsibleInstallVers}-x86_64
-----
+
Online installer::
+
[source,options="nowrap",subs=attributes+]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be subs=+attributes?

-----
$ cd ansible-automation-platform-setup-2.4-1
$ cd ansible-automation-platform-setup-{AnsibleInstallVers}
-----

. Open the `inventory` file for editing.
Expand Down
8 changes: 5 additions & 3 deletions downstream/modules/platform/proc-installing-the-aap-setup-bundle.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,11 @@ The download and installation of the setup bundle needs to be located on the aut

. Untar the bundle
+
[literal, options="nowrap" subs="+attributes"]
----
$ tar xvf \
ansible-automation-platform-setup-bundle-2.4-1.tar.gz
$ cd ansible-automation-platform-setup-bundle-2.4-1
ansible-automation-platform-setup-bundle-{AnsibleInstallVers}.tar.gz
$ cd ansible-automation-platform-setup-bundle-{AnsibleInstallVers}
----
+
. Edit the inventory file to include the required options
Expand Down Expand Up @@ -68,9 +69,10 @@ NOTE: The inventory should be kept intact after installation since it is used fo
+
. Run the AAP setup bundle executable as the root user
+
[literal, options="nowrap" subs="+attributes"]
----
$ sudo -i
# cd /path/to/ansible-automation-platform-setup-bundle-2.4-1
# cd /path/to/ansible-automation-platform-setup-bundle-{AnsibleInstallVers}
# ./setup.sh
----
+
Expand Down
21 changes: 13 additions & 8 deletions downstream/modules/platform/proc-installing-the-ansible-builder-rpm.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,9 @@ This is preferred if a Satellite exists because the EE images can leverage RHEL
. Unarchive the AAP setup bundle.
. Install the ansible-builder RPM and its dependencies from the included content:
+
[source,options="nowrap",subs="+attributes"]
----
$ tar -xzvf ansible-automation-platform-setup-bundle-2.4-1.tar.gz
$ tar -xzvf ansible-automation-platform-setup-bundle-{AnsibleInstallVers}.tar.gz
$ cd ansible-automation-platform-setup-bundle-2.4/bundle/el8/repos/
$ sudo yum install ansible-builder-1.0.1-2.el8ap.noarch.rpm
python38-requirements-parser-0.2.0-3.el8ap.noarch.rpm
Expand Down Expand Up @@ -198,32 +199,36 @@ To upgrade between minor releases of AAP 2, use this general workflow.

. Run `./setup.sh` to upgrade the installation.

For example, to upgrade from version 2.2.0-7 to 2.3-1.2, make sure that both setup bundles are on the initial controller node where the installation occurred:
For example, to upgrade from version 2.2.0-7 to {AnsibleInstallVers}, make sure that both setup bundles are on the initial controller node where the installation occurred:

[literal, options="nowrap" subs="+attributes"]
----
$ ls -1F
ansible-automation-platform-setup-bundle-2.2.0-7/
ansible-automation-platform-setup-bundle-2.2.0-7.tar.gz
ansible-automation-platform-setup-bundle-2.3-1.2/
ansible-automation-platform-setup-bundle-2.3-1.2.tar.gz
ansible-automation-platform-setup-bundle-{AnsibleInstallVers}/
ansible-automation-platform-setup-bundle-{AnsibleInstallVers}.tar.gz
----

Back up the 2.2.0-7 installation:
[literal, options="nowrap" subs="+attributes"]
----
$ cd ansible-automation-platform-setup-bundle-2.2.0-7
$ sudo ./setup.sh -b
$ cd ..
----

Copy the 2.2.0-7 inventory file into the 2.3-1.2 bundle directory:
Copy the 2.2.0-7 inventory file into the {AnsibleInstallVers} bundle directory:
[literal, options="nowrap" subs="+attributes"]
----
$ cd ansible-automation-platform-setup-bundle-2.2.0-7
$ cp inventory ../ansible-automation-platform-setup-bundle-2.3-1.2/
$ cp inventory ../ansible-automation-platform-setup-bundle-{AnsibleInstallVers}/
$ cd ..
----

Upgrade from 2.2.0-7 to 2.3-1.2 with the setup.sh script:
Upgrade from 2.2.0-7 to {AnsibleInstallVers} with the setup.sh script:
[literal, options="nowrap" subs="+attributes"]
----
$ cd ansible-automation-platform-setup-bundle-2.3-1.2
$ cd ansible-automation-platform-setup-bundle-{AnsibleInstallVers}
$ sudo ./setup.sh
----