You are reading an unmaintained version of the Ansible documentation. Unmaintained Ansible versions can contain unfixed security vulnerabilities (CVE). Please upgrade to a maintained version. See the latest Ansible documentation.

infinidat.infinibox.infini_fs – Create, Delete or Modify filesystems on Infinibox

Note

This plugin is part of the infinidat.infinibox collection (version 1.3.0).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install infinidat.infinibox.

To use it in a playbook, specify: infinidat.infinibox.infini_fs.

New in version 2.3: of infinidat.infinibox

Synopsis

• This module creates, deletes or modifies filesystems on Infinibox.

Requirements

The below requirements are needed on the host that executes this module.

• capacity

• infinisdk (https://infinisdk.readthedocs.io/en/latest/)

• python2 >= 2.7 or python3 >= 3.6

Parameters

Parameter	Comments
name string / required	File system name.
password string	Infinibox User password.
pool string / required	Pool that will host file system.
size string	File system size in MB, GB or TB units. See examples.
state string	Creates/Modifies file system when present or removes when absent. Choices: present ← (default) absent
system string / required	Infinibox Hostname or IPv4 Address.
user string	Infinibox User username with sufficient priveledges ( see notes ).

Notes

Note

• This module requires infinisdk python library

• You must set INFINIBOX_USER and INFINIBOX_PASSWORD environment variables if user and password arguments are not passed to the module directly

• Ansible uses the infinisdk configuration file ~/.infinidat/infinisdk.ini if no credentials are provided. See http://infinisdk.readthedocs.io/en/latest/getting_started.html

• All Infinidat modules support check mode (–check). However, a dryrun that creates resources may fail if the resource dependencies are not met for a task. For example, consider a task that creates a volume in a pool. If the pool does not exist, the volume creation task will fail. It will fail even if there was a previous task in the playbook that would have created the pool but did not because the pool creation was also part of the dry run.

Examples

- name: Create new file system named foo under pool named bar
  infini_fs:
    name: foo
    size: 1TB
    pool: bar
    state: present
    user: admin
    password: secret
    system: ibox001

Authors

• Gregory Shulov (@GR360RY)