flasharray – Page 9 – Cody Hosterman

March 25, 2016

vRealize Automation and the FlashArray

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”

March 25, 2016March 25, 2016

Recent ESXi 6 Storage Bugs and the FlashArray

As you might be aware, there have been a few storage-related issues with ESXi 6.0 as of late:

Accidental PDL during dropped paths:

Storage PDL responses may not trigger path failover in vSphere 6.0 (2144657)

Host issues during smartd inquiries:

Issuing a 0x85 SCSI Command from a VMware ESXi 6.0 host results in a PDL error (2133286)

The question that comes up for the Pure Storage FlashArray is are we susceptible? The short answer is no. Let’s explain why. Continue reading “Recent ESXi 6 Storage Bugs and the FlashArray”

February 20, 2016February 20, 2016

Semi-transparent failover with VMFS and Active/Passive Replication

So in a blog series that I started a few weeks back (still working on finishing it), I wrote about managing snapshots and resignaturing of VMFS volumes. One of the posts was dedicated to why I would choose resignaturing over force mounting almost all of the time.

An obvious question after that post is, well when would I want to force mount? There is a situation where i think it is a decent option. A failover situation where the recovery site is the same site as the production site, in terms of compute/vCenter. The storage is what fails over to another array. This is a situation I see increasingly common as network pipes are getting bigger.

Continue reading “Semi-transparent failover with VMFS and Active/Passive Replication”

February 3, 2016

ZeroedThick or EagerZeroedThick? That is the question.

Having a best practices conversation the other day with a customer and the usual topic came up about any recommendations when it comes to virtual disk type. We had the usual conversation thin or thick, the ins and outs of those two. In the end it doesn’t matter too much, especially with some recent improvements in ESXi 6.0. The further question came up, well what about between zeroedthick and eagerzeroedthick? My initial reaction was that it doesn’t matter for the most part. But we had just had a conversation about Space Reclamation (UNMAP) and I realized, actually, I did have a big preference and it was EZT. Let me explain why.

Continue reading “ZeroedThick or EagerZeroedThick? That is the question.”

February 2, 2016February 3, 2016

FlashArray Workflow Package for vRealize Orchestrator

I just put the finishing touches on my workflow packages for the Pure Storage FlashArray for VMware vRealize Orchestrator! Download it here:

https://github.com/codyhosterman/orchestrator

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”

January 25, 2016February 13, 2017

VMFS Snapshots and the FlashArray Part IV: How to correlate a VMFS to a FlashArray volume

This is part 4 of this 7 part series.

The series being:

Continue reading “VMFS Snapshots and the FlashArray Part IV: How to correlate a VMFS to a FlashArray volume”

January 25, 2016February 13, 2017

VMFS Snapshots and the FlashArray Part III: Why might a resignature fail?

This is part 3 of this 7 part series. The series being:

Continue reading “VMFS Snapshots and the FlashArray Part III: Why might a resignature fail?”

January 25, 2016February 13, 2017

VMFS Snapshots and the FlashArray Part II: Why not Force Mount?

This is part 2 of this 7 part series. The series being:

This is a topic that I have looked into years ago, mainly in ESX 4.0 when they changed how it handled unresolved VMFS volumes by allowing it to be done selectively. I have had some customers working with array-based snapshots recently and have run into issues that prevent them from mounting them, or mounting them in the way they want. The problem is that I forgot most of the caveats from that testing because it was way before I started this blog. And as that quote popularized by Mythbusters’ Adam Savage says:

So let’s write it down to so I can’t forget it all again. That show is on its last season right now. I will certainly miss it! But anyways, I digress. Force mounting. Don’t do it and here is why.

Continue reading “VMFS Snapshots and the FlashArray Part II: Why not Force Mount?”

January 18, 2016December 5, 2016

FlashArray UNMAP Script with the Pure Storage PowerShell SDK and PowerActions

I have officially decided to “retire” my UNMAP script that uses direct REST calls to find before and after capacity changes for given volumes. I am only updating the one that uses the Pure Storage PowerShell SDK from this point on–using this is much more robust, not tied to direct API versions and greatly simplifies managing the data in the script.

I have also created a second version for use in the VMware Fling called PowerActions. This allows the script to be executed from the vSphere Web Client.

Continue reading “FlashArray UNMAP Script with the Pure Storage PowerShell SDK and PowerActions”

January 15, 2016January 15, 2016

Updated FlashArray Management Pack for VMware vRealize Operations

Quick post here. An updated version of the Pure Storage FlashArray Management Pack for VMware vRealize Operations (vROPs) has been posted to the VMware Solutions Exchange. No new features, but a variety of internal improvements and bug fixes. Please download the latest version here:

https://solutionexchange.vmware.com/store/products/pure-storage-management-pack-for-vmware-vrealize-operations

I recommend updating your pak to this version.

Notable issues fixed in build 1.0.126 (v1.0.1):

Use correct metric for top 25 volumes by read bandwidth widget.
Fix caching to allow relationships to be refreshed when “filter by vsphere” option is disabled.
Get datastores that are part of a datastore cluster in vCenter.
Minor UI string changes.

For a functional review, please check out this post here:

https://www.codyhosterman.com/2015/06/the-pure-storage-flasharray-vrops-adapter-v1/