Finally! I know… You have been waiting for this and so have I. Our first release of our vSphere Web Client Plugin that supports the HTML-5 interface is officially released. Let’s walk through what it looks like!
The HTML-5 interface is vastly superior to the flash/flex based one, not only due to more accurate readouts, faster load times, but also the extensibility of the interface and guidelines around integration. Making it a much better platform for integration as compared to prior interfaces for vSphere.
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!
One of the major advantages we have seen with VVols is making a virtual disk a first class citizen on the array. We can restore, copy, replicate them (and their VMs) as storage objects were meant to be restored, copied, replicated etc.
Though one thing about virtual disks is that by default–they are not first class citizens in vSphere, VVols or otherwise. To create one, it has to be associated with a VM.
To retrieve one in PowerCLI (for example) get-harddisk requires a datastore or a VM to return a result:
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:
The first of two long anticipated VMware Site Recovery Manager updates is finally here! (the second being discussed here). A SRM appliance!
Since the dawn of time SRM was a Windows-based application. Requiring you to install, configure, and maintain Windows server and then install SRM on it. Certainly adding to the complexity of getting SRM up and running. Everything else VMware offers is an appliance why not this?
Well a couple reasons–but a primary one though is the ecosystem. SRM, unlike many other offerings relies vary heavily on ecosystem partner’s plugins. With essentially the single exception of vSphere Replication, SRM is useless without those vendor plugins, called Storage Replication Adapters (SRAs).
Today Pure Storage officially released support of NVMe-oF support on the FlashArray. This is another important step forward in the FlashArrays progress with NVMe. Prior to this, we have made a few incremental, but important improvements in the product to add full end-to-end support of NVMe:
Converting our NVRAM devices to use NVMe
Moving off of SSDs and adding custom NVMe-based flash modules in the FlashArray//X chassis
Adding support for drive shelves that are connected via NVMe-oF
Officially release NVMe-oF support for front-end workloads.
This has been a multi-step process that we spent a great deal of effort to make sure we were fully taking advantage of what NVMe in general has to offer.
This post is somewhat specific to Pure Storage–the cmdlets of course are universal, but behaviors may not correlate to your storage array. So if you are using VVols on a non-Pure array, certainly consult your vendor.
Furthermore, this is certainly specific to PowerCLI when it comes to the commands. With that being said, the fundamentals on how this works with Pure is common for all orchestration tools, so you should be able to use this information for other tools. Though of course the cmds/syntax will be different.