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 keywords that are used with each of the installation-related modules.

yum/InstallPackages

The yum/InstallPackages module is used to install or uninstall InfoScale products using yum/zypper. Use the following keywords while referencing the module in your playbook.

Table: Yum module keywords / InstallPackages module keywords

Name

Description

Mandatory/optional

repository_name

Name of the yum/zypper repository used to install InfoScale rpms.

Example:

repo-InfoScale742

Mandatory

If the Base URL is provided, the system will create a repository with the specified repository name.

repository_baseurl

Specifies the URL to the directory where the repodata of a repository is located.

Example:

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

Optional

This keyword is not required if you are using a yum/zypper repository already configured on the system, and are providing the repository name.

gpgcheck

Specify whether to check the integrity of the yum/zypper packages by using the gpgkey provided with the InfoScale installation media. This is a boolean variable and must be specified using 0 or 1. By default the value is set to 0.

Optional

gpgkey

Specifies the location of the gpgkey (typically located in the rpms directory of the installation media).

Example:

http://xx.xxx.xxx.xx/rpms/
RPM-GPG-KEY-veritas-infoscale7

Mandatory if gpgcheck is 1, otherwise optional

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: 7.4.2

Mandatory

state

Specifies what state the package should be 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

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

licensing

The licensing module is used to apply licenses in InfoScale. Use the following keywords while referencing the module in your playbook.

Table: Licensing module keywords

Name

Description

Mandatory/optional

state

Specifies what state the package should be 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

product_version

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

Example: 7.4.2

Mandatory

license

Specifies the path to the slf license file to be registered on the system. Ensure that the license file is accessible. The license file must be available on each node.

Perpetual key is not applicable for InfoScale 8.0.2 onwards.

If you are performing a keyless installation or upgrade you can simply enter the product name.

Examples:

  • /license_key/Unix/perpetual/
    xxxxxxxxxxxxxxxxx.slf
  • ENTERPRISE

  • AVAILABILITY

Optional