Now that the latest Pure Storage vSphere Client Plugin is available as a remote plugin is is now deployed as an OVA. I have put together this quick script to automate deploying of the Pure Storage VMware Appliance.
On July 28, 2021 Pure Storage released the latest version of their plugin version 5.0.0. Not only is this a new version, but it also runs on the new remote plugin architecture that VMware has released in vSphere 6.7U3 and vSphere 7.0+. This post will explore how to deploy and manage version 5.0.0 as well as discuss the latest features in this release! (Some are long awaited!)
In previous posts I have covered use cases on how to utilize Pure Cloud Block Store (CBS), but if we look back I haven’t explained how it can be deployed. This blog will cover how to quickly launch CBS with the pre-requisites in AWS.
In previous posts I have covered use cases on how to utilize Pure Cloud Block Store (CBS), but if we look back I haven’t explained how it can be deployed. This blog will cover how to quickly launch the pre-requisites and get your Pure Cloud Block Store deployed in Azure.
Did you know that Equinix has a Bare Metal as a Service (BMaaS) offering? Back in March Pure Storage also announced their Pure Storage® on Equinix Metal™ offering. This allows users to not only procure the Pure Storage FlashArray as an op-ex based purchase, but it also lets you spin up physical servers in Equinix Metal DC’s and connect them to a physical dedicated FlashArray. In this series I will cover how to deploy a vSphere environment on Equinix Metal with Terraform.
The Pure Storage OVA is a single OVA deployment that can be configured for different roles. Today VM Analytics is the only available role, with more coming. Version 3.1.0 includes some new features and fixes, lets dive in and take a look.
Ever wanted to update a Terraform Provider and not use the hosted Registry? Here at Pure Storage we have a Terraform Provider for Cloud Block Store and I wanted to do some testing myself. I started to pull my hair out trying to get Terraform to use my locally built provider instead of the registry. Check out this blog for a few simple steps to use a local in-house provider instead of the registry!
In a previous role I have used Avi Networks and I love their load balancing solution. If you do not pay attention to the default settings, the Service Engines that handle load balancing deploy at 1 cpu and 2 gb of ram. With this blog I will cover how to change that if you have already deployed the NSX ALB and vSphere with Tanzu or any other Virtual Services.
In my previous post we covered how to deploy the NSX Advanced Load Balancer for use with vSphere with Tanzu. This post will go over the vSphere with Tanzu configuration to use that NSX Advanced Load Balancer