The Norm of Change
In the ever-changing paradigm of infrastructure management, it’s becoming inevitably more important to keep track of changes. As most respectable automation systems today leverage human-readable data serialization formats such as YAML or JSON, using industry standard source control management (SCM), such as Git, is becoming more prominent.
These principles are often referred to as infrastructure-as-code, and allow changes to any system under management to be peer-reviewed and approved before the configuration is applied. It’s the ultimate compromise to allow developers and application owners control their own destiny – but not without operations having the final say, approval, and ultimately taking responsibility for the change. Simply put, a clean cut separation of concerns between business needs is needed while de-risking manual and error-prone system configurations.
Since Ansible Content Collections are a relatively new concept in Ansible, only later versions of Ansible are supported.
Minimum Ansible host requirements for HPE Nimble Storage Content Collection for Ansible version 1.0.0:
- Ansible 2.9 or later
- Python 3.6 or later
- HPE Nimble Storage SDK for Python
NimbleOS 5.0.10 or later is required on the arrays being managed by Ansible.
What Are My Next Steps?
- Rate and follow the content collection on Ansible Galaxy
- Access the documentation on Ansible Automation Hub (Red Hat Ansible customers only) or through the content collection GitHub Pages
- Source code and issue tracking available on GitHub
- Introductory tutorial available on HPE Developer Community blog
- Sign up to the HPE DEV Slack community and meet the team, we’re in #NimbleStorage
Your feedback is always most welcome, and all channels are open. The team is eager to hear about your use cases and success stories as you move your business towards “automate all the things”.
"For an in-depth tutorial on how to use these modules, you can find more information in a few simple Ansible playbooks"