InfoScale™ Installation, Upgrade, and Configuration Using Ansible - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.2, 8.0, 7.4.3, 7.4.2, 7.4.1)
Platform: Linux

Customizing InfoScale deployment using solution templates

Solution templates are high-level Ansible playbooks that include modular calls to other playbooks or roles for specific InfoScale tasks. These templates give users the flexibility to add more Ansible components - such as playbooks, roles, or tasks - between steps to match their existing InfoScale workflows and environment.

Table: Infoscale_workflow

Operations

Required modules

Playbook

Full upgrade

  • site_facters

  • upgrade

Playbook - YAML full_upgrade.yml

---
##  - import_playbook: <mycustomplaybook>.yml
##  tasks:
##     - name: My custom task
##        module_name:
##         needed_args:
## - name: Start processes
##      import_role:
##        name: upgradestart_processes
##      vars:
##        arguments: "{{ arguments }}"


- import_playbook: fullupgrade_precheck.yml
- import_playbook: fullupgrade_preupgrade.yml
- import_playbook: fullupgrade_stop_services.yml
- import_playbook: fullupgrade_upgrade_rpm.yml
- import_playbook: fullupgrade_start_services.yml

As per the solution template concept, the full upgrade playbook is broken into smaller steps as shown above. The user can add tasks like reboot machine and run their own roles, or call another playbooks in between. You can take reference of the commented part in the playbook to know more about adding more tasks, roles, and playbook. These can be added anywhere in the playbook.

There is no changes in the variables from the full upgrade scenario. To know more about passing variables,See Upgrading InfoScale using Ansible.