First off, there already is a built-in workflow for adding a new virtual disk so this isn’t exactly groundbreaking knowledge, but I think it is helpful to understand how it is constructed. Furthermore, most of the existing posts and community articles out there assume way too much about ones knowledge of reading the API guide and understanding what is needed.
So let’s boil it down to only what you need to know to create default, commonly used virtual disks. If you want more advanced configurations this should give you a good starting point. Knowing the basics makes it way it is easier to edit and change.
I will write this post on adding a new virtual disk and next I will write one on removing one. Continue reading Creating a new Virtual/Hard Disk with vRealize Orchestrator
Finally starting to catch up on work after VMworld. A lot of blog posts queued up in my head that I want to start getting out. Here is the first. I have completed an update of the FlashArray workflow package with some bug fixes and some new workflows. As always the workflow package can be found here:
Continue reading 1.7 Release of the FlashArray Workflow Package for vRealize Orchestrator
As I have blogged about before, TLS 1.0 and SSL v3 were deprecated in Purity 4.7, requiring all connections to use either TLS 1.1 or TLS 1.2. This affected a variety of integrations, some we updated, some you just had to alter their behavior. A few VMware products do not/did not use TLS 1.1/1.2 by default, so they either need to altered or upgraded. This almost invariably boiled down to the JDK version that was in use. vRealize Orchestrator is no exception.
Continue reading vRealize Orchestrator, TLS 1.2 and Certificate Importing
Let me start out with saying I’m embarrassed I have only been using vRO for 8 months or so. It is AWESOME.
The FlashArray Workflow Package for vRealize Orchestrator has been updated to include two new objects:
- Auto-expand datastore policy template
- Workflow to run UNMAP on a datastore
The creation of the first part is explained in this post. But if you are using the FlashArray it is all built into the package, so you have to do very little work. I’ll explain in a bit.
The UNMAP workflow is generic–it can be used with any VMFS datastore that supports UNMAP. So it is included in the workflow package and it is also standalone for those of you who don’t have a FlashArray. You can get the standalone here:
Continue reading Running UNMAP with vRealize Orchestrator
Virtual disk oversubscription is becoming increasingly common and so is allowing people to provision their own VMs. So increasing a datastore capacity is also an increasingly common operation. Because of the performance of flash, merged with ESXi features like VAAI ATS. Expanding a VMFS is easy. Expanding a storage volume these days is easy. But you still have to actually do it. What if I want to automate the process to respond to datastore capacity threshold limits? There are a variety of ways to achieve this. Let’s look at it via vCenter SNMP alerts and vRealize Orchestrator workflows. Continue reading Automatic VMFS expansion with vCenter SNMP and vRealize Orchestrator
Quick post. I have released the FlashArray Workflow Package for vRealize Orchestrator version 1.3. Not a huge update but a few changes/new features.
Continue reading FlashArray Workflow Package for vRealize Orchestrator version 1.3
I am working on adding some functionality to the FlashArray workflow package for vRealize Orchestrator and one of those features is automating the process to increase the capacity of a VMFS volume. The FlashArray potion of that is pretty straight forward but what of the VMFS portion? Not much on the internet directly about this. Luckily using the vCenter SDK with vRO, this is pretty easy. Continue reading Increasing VMFS capacity with vRealize Orchestrator
I just released the 1.2 version of the Pure Storage FlashArray Workflow Package for vRealize Orchestrator. Like always, you can get this from GitHub:
If you haven’t looked at our vRO workflow package, check out my original post here:
FlashArray Workflow Package for vRealize Orchestrator
While this isn’t a huge release in terms of new features, I think it is an important one because it adds (among others) one particularly important workflow. Translating a VMFS datastore object into a FlashArray volume name. Let’s take a look.
Continue reading Pure Storage vRealize Orchestrator Workflow Package v1.2
I want to say this is the culmination of my last almost two years of creating vRealize integration for Pure Storage, but that isn’t the right word. It is a milestone, because there is still so much more cool stuff to be done. Especially with vRealize Automation. In many ways it is just the beginning! But I can now demonstrate Pure Storage FlashArray integration with the whole vRealize stack: Log Insight, Operations, Orchestrator and Automation.
Log Insight has a Content Pack. Operations has the Management Pack. Orchestrator has the Workflow Package. Automation also uses that Workflow Package. Let’s talk about how.
Continue reading vRealize Automation and the FlashArray
I just put the finishing touches on my workflow packages for the Pure Storage FlashArray for VMware vRealize Orchestrator! Download it here:
Three important notes on this package:
- This is not officially supported by Pure Storage yet, I made this, not our engineering. Treat this like a VMware Fling. We support the underlying REST calls of course, but cannot guarantee support directly on the package (I will supply best effort). We will analyze demand for this though hopefully release a fully supported one in the future. If you like it, or want more, or more frequent updates, please let us know!
- This is open source, when you import it, you can edit it all you want, this is not locked down. Though I advise copying a given workflow to a new one so you can edit it and keeping the originals unchanged. This makes troubleshooting easier.
- Contribute! Please post your own additions and changes on Github or our community. Let’s see what everyone can do.
The workflow has been tested with vRealize Orchestrator 6.0.3 and 7.0. It should work with older versions as long as they have the REST plugin. From the FlashArray perspective, it requires any Purity version that runs the REST API 1.4 or later. Nothing else really matters, it supports both the 400 series and FlashArray//m.
Continue reading FlashArray Workflow Package for vRealize Orchestrator