"Remember kids, the only difference between Science and screwing around is writing it down" -Alex Jason (made popular by Adam Savage)
I’ve been making a lot of updates to my PowerShell module around VVols recently and this was the last “table stakes” cmdlet I wanted to add. There are certainly more to come, but now we definitely have the basics. In 1.2.2.1 release of the PowerShell module I added a cmdlet called Mount-PfaVvolDatastore.
As of today we support a single VVol datastore–though we are working on adding support for more than one.
Registering VASA providers is the first step in setting up VVols for a given vCenter, so automating this process is something that might be of interest to folks. We currently have this process in our vSphere Plugin, as well as in our vRO plugin, and of course you can do it manually. What about PowerShell? Well we have that too!
In our PowerShell Pure/VMware module there are three new cmdlets:
I have written about authenticating with the Pure1 REST API, and my PowerShell module in the past:
https://www.codyhosterman.com/2019/01/using-the-pure1-rest-api-part-i-powershell/
NOTE: This workaround is not really needed anymore with the default behavior of the module. See this post: https://www.codyhosterman.com/2019/12/pure1-rest-api-authentication-made-easy/
One of the issues is that if you followed my default instructions, you would need to run the PowerShell window as an admin to be able to create the connection. The answer–now that I think about it is fairly obvious: non-admin users (or admins not running in admin mode) don’t have security rights to it. Duh!
About 6 months ago, my esteemed colleague Barkz blogged about our path forward with PowerShell. We have an official PowerShell SDK for managing the FlashArray–but it is limited to that: doing stuff to the FlashArray.
So to add value and make managing it within context of the layers you actually manage your infrastructure from (VMware, Microsoft, etc.) we created some value-add PowerShell modules to make it easier. Barkz talks about them here:
I have written a few posts recently on using the Pure1 with PowerShell, like below:
I made a PowerShell module you make it easy for you to use, which can be installed via install-module from the PowerShell gallery. Details here:
https://www.codyhosterman.com/scripts-and-tools/pure1-rest-api/pure1-powershell-module/
Continue reading “Pulling Performance Statistics from Pure1 with PowerShell”Recently I wrote a blog post on how to authenticate and connect to Pure1 via PowerShell. You can find that here:
I have made authentication MUCH easier:
https://www.codyhosterman.com/2019/12/pure1-rest-api-authentication-made-easy/
But it is fairly involved, so I made it easier for you (and me) by writing a PowerShell module and posted in on the PowerShell Gallery.
https://www.powershellgallery.com/packages/Cody.PureStorage.Pure1/
Continue reading “Using the Pure1 PowerShell Module”In my last post, I spoke about the ins and outs of using the Pure1 REST API–but it was a fairly manual process. Which of course is not how you really want to use a REST API. So the first part of this series will be using it with one of my favorite tools: PowerShell!
I will separate this into five parts:
UPDATE!!!! I made this much easier, you can use my module to connect to Pure1 which is on the PowerShell gallery.
You can find more information on it here:
https://www.codyhosterman.com/scripts-and-tools/pure1-rest-api/pure1-powershell-module/h
Continue reading “Using the Pure1 REST API Part I: PowerShell”I have released a new version of the VMware/Pure PowerShell module which can be automatically installed from the PowerShell Gallery.
Pure Storage PowerShell VMware Module
Updates in this release are focused on VVols. Creating VVol snapshots, copying them, creating new disks from them, retrieving them etc.
Version 1.1.0.2
I wrote a blog post below on using some of the new cmdlets:
PowerCLI and VVols Part V: Array Snapshots and VVols
Continue reading “1.1.0.2 Release of the Pure Storage VMware PowerShell Module”
I see a fair amount of requests around how to do different things with VMware PowerCLI and the Pure Storage PowerShell SDK. How do I correlate a VMFS to a volume? How do I create a new VMFS? How do I expand? Etc.
To help our customers I have written a module that includes a lot of the common operations people might need to “connect” PowerCLI to our PowerShell SDK.
The module is called Cody.PureStorage.FlashArray.VMware. Continue reading “Pure Storage and VMware PowerShell Module”
My last post in this series was about getting a VVol UUID and figuring out what volume on a FlashArray it is. But what about the step before that? If I have a guest OS file system how do I even figure out what VMDK it is?
There is a basic option, which can potentially be used, which is correlating the bus ID and the unit ID of the device in the guest and matching it to what VMware displays for the virtual disks.
But that always felt to me as somewhat inexact. What if you accidentally look at the wrong VM object and then do something to a volume you do not mean to? Or the opposite?
Not ideal. Luckily there is a more exact approach. I will focus this particular post on Windows. I will look at Linux in an upcoming one.
Continue reading “PowerCLI and VVols Part IV: Correlating a Windows NTFS to a VMDK”