infinidat.infinibox.infini_event module – Create custom events on Infinibox

Note

This module is part of the infinidat.infinibox collection (version 1.4.5).

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_event.

New in infinidat.infinibox 2.16.0

Synopsis

  • This module creates events on Infinibox.

Requirements

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

Parameters

Parameter

Comments

description_template

string / required

The content of the custom event

level

string / required

The level of the custom event

Choices:

  • "INFO"

  • "WARNING"

  • "ERROR"

  • "CRITICAL"

password

string / required

Infinibox User password.

state

string

Creates a custom event when present. Stat is not yet implemented. There is no way to remove events once posted, so abent is also not implemented.

Choices:

  • "present" ← (default)

system

string / required

Infinibox Hostname or IPv4 Address.

user

string / required

Infinibox User username with sufficient priveledges ( see notes ).

visibility

string

The event’s visibility

Choices:

  • "CUSTOMER" ← (default)

  • "INFINIDAT"

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 custom info event
  infini_event:
    description_template: Message content
    level: INFO
    state: present
    user: admin
    password: secret
    system: ibox001

Authors

  • David Ohlemacher (@ohlemacher)