A future suggestion for this, is to pass the necessary auth required to curl the files directly from IBM Support, rather than requiring the files to be present the control node, and copied to workers.
The AIX download route may need to be tested. I believe the ansible_architecture fact should report ppc64le on the AIX systems (assuming that MQ Ansible only supports PPC on AIX, due to the file referenced in the existing codebase). If this is not the case, then the playbook may need to be renamed to whatever the AIX PPC architecture reports to ansible for this fact.
This PR contains the following work for https://github.com/ibm-messaging/mq-ansible/issues/63:
downloadmq
role.common
file, as there was code duplication.Notes:
As I was unable to locate an 'mq for developers' release for s390x/PPC architectures hosted under the DHE repository for MQ. There was a 'non-install' release, but I am unsure as to the differences between these and the standard 'mq for developers' releases. THerefore, I resorted to using the MQ trial 9.3 release from IBM Support. This is the same as how MQ Ansible currently obtains the relevant files for AIX, as this utilises the trial version of MQ Ansible. Ref: https://github.com/ibm-messaging/mq-ansible/blob/47e52625c82c1771c65fe4e6f6b950890aff1de9/ansible_collections/ibm/ibmmq/roles/downloadmq/tasks/Linux_s390x_downloadmq.yml#L1-L6
curl
the files directly from IBM Support, rather than requiring the files to be present the control node, and copied to workers.The AIX download route may need to be tested. I believe the
ansible_architecture
fact should reportppc64le
on the AIX systems (assuming that MQ Ansible only supports PPC on AIX, due to the file referenced in the existing codebase). If this is not the case, then the playbook may need to be renamed to whatever the AIX PPC architecture reports to ansible for this fact.