Veritas 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

List of pre-defined keywords

Refer to the following tables for a list of the keywords that are used with each of the configuration-related modules.

sfcfsha_config

The sfcfsha_config module is used configure the component in InfoScale. Use the following keywords while referencing the module in your playbook.

Table: Sfcfsha_config module keywords

Name

Description

Mandatory/optional

cluster_name:

Define a name for the cluster that you want to deploy.

Example: Cluster1

Mandatory

cluster_uuid:

Define a unique alphanumeric ID to assign to the cluster you want to deploy.

Example: c7c2d65e-057f-11e8-a32c-c094107f3b61

Optional

component:

Specify which components you want to configure in your product. Note that the product license acquired must support the required components.

Example: SF, VCS, or SFCFSHA

Optional

method:

Specify the communication protocol that you want to deploy in the cluster.

Example: ethernet, or udp

Mandatory

enable_lgf:

Specify either 0 or 1.

0 creates a single-node cluster on each system provided in the playbook run, without enabling LLT, GAB, or I/O fencing.

1 (default value) creates a multi node cluster of all the servers in the playbook run.

Optional

seednode:

Select any node from the cluster that will be used to run commands related to the operations of that cluster.

Seednode can be set as FQDN, IP Address, and short hostname. Examples:

seednode: objstorer820-1-vm17.veritas.com

seednode: xx.xxx.xxx.xxx

seednode:  objstorer820-1-vm17

Mandatory

reconfig

Specifies whether the component configuration should be reconfigured. The value should be 1 to reconfigure component.

Optional

state:

Specifies what state the configuration should be in after the task is completed. The value for this keyword can be either present or absent.

Mandatory

private_link:

Lists the name of the NICs that the heartbeat link uses on each of the nodes in the cluster.

Mandatory

low_priority_link:

Lists the name of the NICs that the low priority heartbeat link uses on each of the nodes in the cluster.

Optional

udp_link

This attribute is only required if you want to configure LLT over a UDP link (method must be set to udp). Specify information for configuring a UDP link. List the name, IP address, and port number of the NICs that the UDP link uses on each of the nodes in the cluster.

System can be ip/fqdn/nofqdn

Example:

udp_link:
    - system: 'dl380g10-12-kvm-24'
      heartbeat_link:
          - nic: eth1
            ip: 192.xxx.x.x/xx
            port: 50000
          - nic: eth2
            ip: 192.xxx.x.x/xx
            port: 50001
    - system: 'dl380g10-12-kvm-20'
      heartbeat_link:
          - nic: eth1
            ip: 192.xxx.x.x/xx
            port: 50000
          - nic: eth2
            ip: 192.xxx.x.x/xx
            port: 50001

Optional

vcs_clusterid:

Define a unique number to be assigned to the cluster.

Optional

mtu

Define MTU value to be used.

Optional

eo_compliant_logging

Specifies whether EO Logging should be enabled or disabled. Value should be "on" to enable and "off" to disable.

Optional

gendeploy_path

Specifies the absolute path of the gendeploy script from the local node to register InfoScale hosts to the VIOM Management Server.

It is supported on InfoScale 8.0.2 and later.

Example:

gendeploy_path: '/root/script_path.pl'

Optional

process

The process module is used to start and stop component processes. Use the following keywords while referencing the module in your playbook.

Table: Process module keywords

Name

Description

Mandatory/optional

component:

Specify which components you want to configure in your product. Note that the product license acquired must support the required components.

Example: SF, VCS, or SFCHA

Mandatory

product:

Specifies the name of the product you want to install.

Examples: ENTERPRISE, AVAILABILITY, STORAGE, or FOUNDATION.

Mandatory

product_version:

Specifies the version of the product that you want to install or upgrade.

Example: http://xx.xxx.xxx.xx/rpms/

Mandatory

state:

Specifies what state the process should be in after the task is completed. The value for this keyword can be either present or absent. If you do not give any value for this parameter, by default, the state of the package is set to present, and the package will be installed.

Optional

Seednode:

Select any node from the cluster that will be used to run commands related to the operations of that cluster.

Seednode can be set as FQDN, IP Address, and short hostname. Examples:

seednode: objstorer820-1-vm17.veritas.com

seednode: xx.xxx.xxx.xxx

seednode:  objstorer820-1-vm17

Optional

gendeploy_path

Specifies the absolute path of the gendeploy script from the local node to register InfoScale hosts to the VIOM Management Server.

It is supported on InfoScale 8.0.2 and later.

Example:

gendeploy_path: '/root/script_path.pl'

Optional