Update Blog “how-to-use-dscc-api-and-ansible-to-collect-the-storage-configuration”

thomasbeha · thomasbeha · commit 3686f3cad64f · 2025-01-09T16:06:45.000Z
diff --git a/content/blog/how-to-use-dscc-api-and-ansible-to-collect-the-storage-configuration.md b/content/blog/how-to-use-dscc-api-and-ansible-to-collect-the-storage-configuration.md
@@ -6,4 +6,4 @@ author: Thomas Beha
 authorimage: /img/thomasbeha.jpg
 disable: false
 ---
-Capturing the current storage configuration in order to verify it against the best practices or configuration rules is a task that is requested regularly.
+Capturing the current storage configuration in order to verify it against best practices or configuration rules is a task that customer requested regularly. If the customer is using Ansible as the automation platform, then there is on one hand the [HPE 3PAR Ansible module](https://github.com/HewlettPackard/hpe3par_ansible_module?tab=readme-ov-file), that is  used to create and delete hosts, volumes etc, but it is not really a solution for gathering the complete current configuration. Furthermore, this module uses the WSAPI of individual Alletra storage systems, while the HPE Data Services Cloud Console (DSCC) would be the better option to collect storage configuration data of multiple systems that might even be distributed across multiple sites. The DSCC would over a central, single location to get the data of all storage systems.
