Create a hidden command to allow a change for the number of concurrent SSH connections to SVC/FlashSystem

Below is another way to get this info (by using localhost from ansible controller and REST API) without ssh. If speed/parallelism is required, async/poll can be added. ansible collection version 2.7.4 adjusts the speed based on REST API throlling already.

---
- name: Get volume data from FlashSystem
  hosts: all
  connection: local
  gather_facts: false
 
  tasks:
    - name: Get all volume data for a host
      ibm.storage_virtualize.ibm_svc_info:
        clustername: "{{ src_stg }}"
        username: "{{ flash_username }}"
        password: "{{ flash_password }}"
        log_path: /tmp/ansible.log
        gather_subset: hostvdiskmap
        objectname: "{{ item }}"
      loop: "{{ lpar_list }}"
      register: flash_info
      
Please let me know whether that helps the case.

Having run into this, running any Ansible playbook against an inventory of more than one will cause connection errors when hitting the FlashSystem.  So every play that I have now, that uses ibm.storage_virtualize I add a throttle: 1.

For example, something simple like this:

---
- name: Get volume data from FlashSystem
  hosts: all
  connection: local
  gather_facts: false
 
  tasks:
    - name: Get all volume data for a host
      ibm.storage_virtualize.ibm_svc_info:
        clustername: "{{ src_stg }}"
        username: "{{ flash_username }}"
        password: "{{ flash_password }}"
        log_path: /tmp/ansible.log
        gather_subset: hostvdiskmap
        objectname: "{{ lpar_name }}"
      register: flash_info

Will cause a failure on one host (with an inventory of two):

PLAY [Get volume data from FlashSystem] *******************************************************************************************************************************************************************************
 
TASK [Get all volume data for a host] *********************************************************************************************************************************************************************************
fatal: [aix_test]: UNREACHABLE! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python3"}, "changed": false, "msg": "Failed to obtain access token", "unreachable": true}
ok: [aix_stby]

Adding throttle: 1 does get around this limitation