IBM Spectrum Virtualize Collection v1.12.0 (ansible-collections#93)

* IBM Spectrum Virtualize Collection v1.12.0

Author: Shilpi-J

README.md

@@ -100,6 +100,8 @@ Alternatively, you can add a full namepsace and collection name in the `collecti
 - ibm_svctask_command - Runs svctask CLI command(s) on Spectrum Virtualize storage systems over SSH session
 - ibm_sv_manage_awss3_cloudaccount - Manages Amazon S3 cloud account configuration on Spectrum Virtualize storage systems
 - ibm_sv_manage_cloud_backup - Manages cloud backups on Spectrum Virtualize storage systems
+- ibm_sv_manage_fc_partnership - Manages Fibre Channel (FC) partnership on Spectrum Virtualize storage systems
+- ibm_sv_manage_fcportsetmember - Manages addition or removal of ports from the Fibre Channel (FC) portsets on Spectrum Virtualize storage systems
 - ibm_sv_manage_ip_partnership - Manages IP partnership configuration on Spectrum Virtualize storage systems
 - ibm_sv_manage_provisioning_policy - Manages provisioning policy configuration on Spectrum Virtualize storage systems
 - ibm_sv_manage_replication_policy - Manages policy-based replication configuration on Spectrum Virtualize storage systems
@@ -129,7 +131,7 @@ Alternatively, you can add a full namepsace and collection name in the `collecti
 The modules in the IBM Spectrum Virtualize Ansible collection leverage REST APIs to connect to the IBM Spectrum Virtualize storage system. This has following limitations:
 1. Using the REST APIs to list more than 2000 objects may create a loss of service from the API side, as it automatically restarts due to memory constraints.
 2. It is not possible to access REST APIs using an IPv6 address on a cluster.
-3. The Ansible collection can run on all IBM Spectrum Virtualize storage system versions above 8.1.3, except versions 8.3.1.3 and 8.3.1.4.
+3. The Ansible collection can run on all IBM Spectrum Virtualize storage system versions above 8.1.3, except versions 8.3.1.3, 8.3.1.4 and 8.3.1.5.
 4. At time of release of the SV Ansible v1.8.0 collection, no module is available for non LMC systems to automate license agreements acceptance, including EULA.
    User will be presented with a GUI setup wizard upon user-interface login, whether the Ansible modules have been used for initial configuration or not.
 

changelogs/changelog.yaml

@@ -120,3 +120,19 @@ releases:
     - description: Allows user to restore an existing cloud backup on Spectrum Virtualize systems
       name: ibm_sv_restore_cloud_backup
       namespace: ''
+  1.12.0:
+    release_date: '2023-03-15'
+    changes:
+      release_summary: Added new modules for managing FC partnership and FC portsets through Ansible.
+      minor_changes:
+        - ibm_svc_host - Added support for NVMe ROCE host.
+        - ibm_svc_info - Added new options for gather_subset parameter.
+        - ibm_svc_manage_portset - Added support for FC portset and rename functionality.
+        - ibm_svc_mdiskgrp - Added more parameters for storage pool configuration.
+    modules:
+    - description: Manages FC partnership on Spectrum Virtualize systems
+      name: ibm_sv_manage_fc_partnership
+      namespace: ''
+    - description: Manages addition or removal of ports from the Fibre Channel (FC) portsets on Spectrum Virtualize storage systems
+      name: ibm_sv_manage_fcportsetmember
+      namespace: ''

galaxy-importer.cfg

@@ -1,2 +1,2 @@
 [galaxy-importer]
-RUN_FLAKE8 = True
+RUN_FLAKE8 = True

galaxy.yml

@@ -9,7 +9,7 @@ namespace: ibm
 name: spectrum_virtualize
 
 # The version of the collection. Must be compatible with semantic versioning
-version: 1.11.0
+version: 1.12.0
 
 # The path to the Markdown (.md) readme file. This path is relative to the root of the collection
 readme: README.md

playbooks/volume_migration/README.txt

@@ -31,3 +31,6 @@ There are total 3 files used for this use-case.
      - Again rescan the volume on the host to get the updated path details.
      - Delete source volume and migration relationship which was created.
      - Again rescan the volume on the host to get the reduced paths.
+  
+ Authors: Ajinkya Nanavati (ananava1@in.ibm.com)
+          Mohit Chitlange  (mochitla@in.ibm.com)

plugins/modules/ibm_sv_manage_awss3_cloudaccount.py

@@ -182,7 +182,7 @@
 from ansible.module_utils.basic import AnsibleModule
 from ansible_collections.ibm.spectrum_virtualize.plugins.module_utils.ibm_svc_utils import (
     IBMSVCRestApi, svc_argument_spec,
-    get_logger, strtobool
+    get_logger
 )
 from ansible.module_utils._text import to_native
 

plugins/modules/ibm_sv_manage_cloud_backups.py

@@ -136,7 +136,7 @@
 from ansible.module_utils.basic import AnsibleModule
 from ansible_collections.ibm.spectrum_virtualize.plugins.module_utils.ibm_svc_utils import (
     IBMSVCRestApi, svc_argument_spec,
-    get_logger, strtobool
+    get_logger
 )
 from ansible.module_utils._text import to_native