On November 16, 2020 the latest version of the Pure1 VM Analytics OVA Collector (3.0) was released and with it comes some new Pure1 features! Let’s take a look at how the collector has changed, and what new features we now have within Pure1 VM Analytics.
When it comes to monitoring your Pure Storage environment Pure1 is a great place for that. It is also a great place to use your analytic’s data to your advantage and use it for intelligent VMware provisioning! In this blog post I will cover how to use this data to your advantage to make sure you can easily deploy VM’s to the most optimal array and datastore.
Pure1 VM Analytics is a great tool to have in your environment. You don’t need to even have a Pure Storage array, but it makes it even better! Back in 2019 the collector was converted to an OVA format and has been much simpler to deploy. You can deploy it through the UI or even Powershell. With the latest update to the Terraform vSphere provider we can now deploy OVA’s, so lets jump in to see how we can deploy the VM Analytics collector!
The more I play with our integrations the more I am impressed. My latest project within vRealize Orchestrator had me utilizing our Pure1 integration. This post will cover how to generate the needed pieces to configure the Pure1 Integration within vRO.
Beginning with version 4.2.0 the Pure Storage vSphere Client Plugin had a whole slew of new features added, one of those features was the ability to integrate authentication with Pure1 allowing fleet registration of all your Pure Storage Arrays among other things. This does require a slight change on how you would normally register your arrays in the plugin, so lets take a look at how we can accomplish this!