Upgrading RHMAP 4.7 to 4.7 Latest
For Red Hat Mobile Application Platform 4.7
Abstract
Chapter 1. Preparing Infrastructure for Upgrading
You can upgrade RHMAP by either
- Installing Ansible version 2.4 and running the installer scripts.
- Running an installer container image, which has ansible installed, and running the installer scripts in that container.
This guide assumes you have installed Ansible version 2.4 as described in Ansible Installation Guide and configured Ansible for installing RHMAP components.
To prepare for the upgrade:
1.1. Using a Container Image to Upgrade RHMAP (Optional)
An alternative method for upgrading is to use the RHMAP installer container image, which includes Ansible and the templates, so you do not need to install Ansible.
Enter the following command to download the installer container image:
docker pull rhmap47/installer
The procedures in this guide provide example commands for using this container.
Chapter 2. Upgrading the Core Project 4.7.x to 4.7.1
2.1. Overview
Upgrading Red Hat Mobile Application Platform from version 4.7.x to version 4.7.1 includes the following changes:
- Existing images versions are updated to RHMAP 4.7.1 versions by modifying the deployment configurations for all objects in the RHMAP Core, which triggers a redeployment of each component.
Before proceeding with the upgrade:
- Back up all persistent volumes.
- Make sure you have administrator permissions for the OpenShift cluster hosting RHMAP.
2.2. Upgrading to RHMAP Core Version 4.7.1
If you are using the installer container image option, mount an inventory file and a valid SSH key for targeting that inventory, for example:
docker run -it \ -v ~/.ssh/id_rsa:/opt/app-root/src/.ssh/id_rsa:Z \ -v ${HOME}/Desktop/rhmap-ansible/inventories:/opt/app-root/src/inventories \ -e ANSIBLE_PRIVATE_KEY_FILE=/opt/app-root/src/.ssh/id_rsa \ rhmap47/installer bashTo upgrade your existing RHMAP Core from 4.7.x to 4.7.1 you must specify:
- the name of the current project
- an inventory file
project_typewhich must be set tocore.An example command is shown below:
cd /opt/rhmap/4.7/rhmap-ansible ansible-playbook -i my-inventory-file playbooks/upgrade.yml -e project_type=core -e project_name=my-rhmap-core-project
This command reads the current deployment information and chooses the next available upgrade path. A warning message is displayed advising you to back up your data before proceeding. Press Enter to confirm that you have backed up and to continue with the upgrade.
2.3. Verifying RHMAP Core Upgrade
- Review the output to verify there were no failures.
- Verify all Nagios checks are healthy.
- Make sure the component versions match those in the Container Catalog for the erratum.
See the troubleshooting documentation in cases where the upgrade fails.
Chapter 3. Upgrading Each MBaaS Project 4.7.x to 4.7.1
3.1. Overview
Upgrading your deployment of Red Hat Mobile Application Platform from version 4.7.x to version 4.7.1:
- Existing images versions are updated to RHMAP 4.7.1 versions by modifying the deployment configurations for all objects in the RHMAP MBaaS, which triggers a redeployment of each component.
Before proceeding with the upgrade:
- Back up all persistent volumes.
- Ensure you have administrator permissions for the OpenShift cluster hosting RHMAP.
3.2. Upgrading to RHMAP MBaaS Version 4.7.1
If you are using the installer container image option, mount an inventory file and a valid SSH key for targeting that inventory, for example:
docker run -it \ -v ~/.ssh/id_rsa:/opt/app-root/src/.ssh/id_rsa:Z \ -v ${HOME}/Desktop/rhmap-ansible/inventories:/opt/app-root/src/inventories \ -e ANSIBLE_PRIVATE_KEY_FILE=/opt/app-root/src/.ssh/id_rsa \ rhmap47/installer bashTo upgrade your existing RHMAP MBaaS from 4.7.x to 4.7.1 you must specify:
- the name of the current project
- an inventory file
project_typewhich must be set to1-node-mbaasor3-node-mbaas.An example command is shown below:
cd /opt/rhmap/4.7/rhmap-installer ansible-playbook -i my-inventory-file playbooks/upgrade.yml -e project_type=3-node-mbaas -e project_name=my-rhmap-mbaas-project
This command reads the current deployment information and chooses the next available upgrade path. A warning message is displayed advising you to back up your data before proceeding. Press Enter to confirm that you have backed up and to continue with the upgrade.
3.3. Verifying RHMAP MBaaS Upgrade
- Review the output to verify there were no failures.
- Verify all Nagios checks are healthy.
- Make sure the component versions match those in the Container Catalog for the erratum.
See the troubleshooting documentation in cases where the upgrade fails.
