Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simple mapping management with initiator groups #53

Open
TheBlaide opened this issue Jan 10, 2020 · 1 comment
Open

Simple mapping management with initiator groups #53

TheBlaide opened this issue Jan 10, 2020 · 1 comment

Comments

@TheBlaide
Copy link

Hi,

I'm looking for a way to simply map a volume to an existing initiator group without gathering any hosts facts.
the host protocol access is fc and host os is esx.

  • hosts: myarray
    vars:
    nimble_volume: "myvolume"
    nimble_host_name: "mygroup"
    nimble_initiator_group: "mygroup"
    nimble_static_host_facts: True

    roles:

    • { role: nimblestorage.ansinimble,
      nimble_operation: create,
      nimble_object: volume
      }
    • { role: nimblestorage.ansinimble,
      nimble_operation: map,
      nimble_object: volume
      }

The playbook fails :
fatal: [s01r7808.prod.local]: FAILED! => {"changed": false, "msg": "nimble_host_vars unconfigured or unable to lookup dynamically"}

does the map action on volume is able to take a nimble group as input ?

Regards,

Blaise

@TheBlaide TheBlaide changed the title Simple mapping Management with initiators group Simple mapping management with initiator groups Jan 10, 2020
@datamattsson
Copy link
Member

I apologize not seeing this issue earlier. Do you still need help? I think you need to set the WWN in nimble_initiator_group_options. Let me know and I can cook up an example on how to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants