IBM Maximo Application Suite installation with Ansible collection
The IBM® Maximo Application Suite development team maintains a public Ansible collection that automates the installation and configuration of Maximo Application Suite and its dependencies. The Maximo Application Suite DevOps Ansible collection includes a number of automated tasks, referred to as roles and playbooks. These automated tasks can be used to streamline processes from having a simple Red Hat® OpenShift® cluster, to having Maximo Application Suite including multiple applications and its required dependencies.
It also provides a docker container, which contains all the prerequisites to run the Ansible automation on any local machine.
For example, from Maximo Application Suite 8.9, you can use the role variable mas_annotations
to install the Maximo Application Suite in production or nonproduction mode. The
mas_annotations is an optional variable, which accepts a comma-separated list of
annotations that need to be added to the Maximo Application Suite CR. To deploy your
Maximo Application Suite in nonproduction mode, set this variable to
mas.ibm.com/operationalMode=nonproduction
. For more information, see Maximo Application Suite Ansible collection examples.
For more information about how to help with the development of new roles and collections or improvements to the existing ones, see Contributing.
- Ansible® role documentation contains terms and
variables, prefixed by
W3
orARTIFACTORY
that are intended for internal IBM use only. Ignore these variables if they do not apply to your role, use-case, environment, or scenario.
Mapping documentation tasks to Ansible roles
Each documentation task that contains an Ansible role begins with a Tip that links to the Ansible role that applies to the task.
For reference, the following documentation tasks map to Ansible roles: