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

Stop InfoScale services

This documentation explains how Ansible role can be used for stopping InfoScale services on the cluster nodes.

The goals of this guide is to stop services on the cluster nodes of InfoScale.

Pre-requisites

  • Ansible control node is properly set to run Ansible playbooks.

  • The role is installed or copied as per your environment

Role information

The role can be used like this:

```yaml
---
- name: My playbook for InfoScale tasks
  hosts: cluster_nodes

  roles:
    - stop_processes

This role should be used when the user wants to stop the services on the cluster nodes of InfoScale.

Variables

  • vtas_component: Name of the component configured on the InfoScale nodes: (Such as SF, SFHA, SFCFSHA, and more.)

  • vtas_product: Name of the product installed on the InfoScale nodes. (FOUNDATION, AVAILABILITY, STORAGE, ENTERPRISE)

  • vtas_product_version: Product version installed on the InfoScale nodes. (Such as 8.0, 7.4.2, and more.)

Using variables in Ansible

There are several ways of modifying the default variables. You can check the Ansible documentation for more information.

Command line

This role can be included in the playbook as per the user's environment workflow or requirements. The playbook can be run as below:

From the command line, it can be done with the -e EXTRA_VARS or --extra-vars EXTRA_VARS flag:

```cli
ansible-playbook -i hosts playbooks/myinfoscale.yml -e "vtas_component='sfha'" -e "
vtas_product='ENTERPRISE'" -e "vtas_product_version='sfha'"

Role usage

This role can be used in the playbooks in all the ways Ansible supports. The following is the example of how to import this role.

```yml 

 - name: Stopping processes 
    import_role:
      name: stop_processes