infinidat.infinibox.infini_network_space module – Create, Delete and Modify network spaces on Infinibox
Note
This module is part of the infinidat.infinibox collection (version 1.3.12).
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
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: infinidat.infinibox.infini_network_space
.
New in infinidat.infinibox 2.12.0
Synopsis
This module creates, deletes or modifies network spaces on Infinibox.
Requirements
The below requirements are needed on the host that executes this module.
python2 >= 2.7 or python3 >= 3.6
infinisdk (https://infinisdk.readthedocs.io/en/latest/)
Parameters
Parameter |
Comments |
---|---|
A list of interfaces for the space. |
|
List of IPs. Default: |
|
Set an MTU. If not specified, defaults to 1500 bytes. |
|
Network space name |
|
Network mask. |
|
Starting IP address. |
|
Infinibox User password. |
|
Specify the throughput limit per node. The limit is specified in Mbps, megabits per second (not megabytes). Note the limit affects NFS, iSCSI and async-replication traffic. It does not affect sync-replication or active-active traffic. |
|
Choose a service. Choices:
|
|
Creates/Modifies network spaces when present. Removes when absent. Shows status when stat. Choices:
|
|
Infinibox Hostname or IPv4 Address. |
|
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.htmlAll 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 network space
infini_network_space:
name: iSCSI
state: present
interfaces:
- 1680
- 1679
- 1678
service: ISCSI_SERVICE
netmask: 19
network: 172.31.32.0
default_gateway: 172.31.63.254
ips:
- 172.31.32.145
- 172.31.32.146
- 172.31.32.147
- 172.31.32.148
- 172.31.32.149
- 172.31.32.150
user: admin
password: secret
system: ibox001