58:30 Webinar
From CSI to Snapshots: Seamless VM Management on Red Hat OpenShift
Join this webinar for a set of short demos of Everpure FlashArray™ with Red Hat OpenShift. We'll go from the ground up: connecting the Container Storage Interface (CSI) to storage, spinning up a virtual machine (VM) from a template, and protecting the VM with instant, array-based snapshots.
This webinar first aired on 22 September 2026
The first 5 minute(s) of our recorded Webinars are open; however, if you are enjoying them, we’ll ask for a little information to finish watching.
Click to View Transcript
Hello, everybody, and happy Tuesday if you're joining in real time, and if you're joining us in the future or watching this recording, happy whatever day of the week it is for you. And welcome to another episode of Expert-Led Demos. I am your host, Jason Langer, and I'm joined today by my good friend, Matt Webb. Hello, Matt. Hello.
Hello, hello. Happy Tuesday to you, my friend. How are you? You know, you know what's special about today? Let's talk about Tuesday. Can I give a shout-out? It's my, son's 13th birthday. I now have a teenager.
Oh. So, congratulations and I'm sorry is in order. Yeah. Well- having a teenager, good luck, have fun, Andrew. Yes. Uh- that probably makes this topic a lot easier, quite honestly. Like before I'm like, "Oh, no, Red Hat, VMs." Yeah.
Like talk- I could handle YAML and, uh- Yeah. Descheduling all the time, but, uh- Yeah a teenager is not so much. No, that's, that's, that's, that's Well, congratulations. Happy birthday. Hope he's having a great one. But anyways, welcome, everybody.
As we just hinted at, we are doing an expert-led demo and we're gonna do From CSI to Snapshots: Seamless VM Management on Red Hat OpenShift. Obviously, there's a lot of talk in the marketplace these days about hypervisor options, and of course, we wanna kinda show you what Pure can- Everpure can do for you regardless of which hypervisor you choose.
And Matt, like, kind of did a s- soft introduction welcoming, but what, for those that might not know, give us a quick blurb on who you are and why you might be here today. You're saying, w- what do you do here? Um- That's pretty much what I'm saying. I, 'cause I haven't figured it out yet.
So I'm a field solutions architect. And if you're not familiar with what a field solutions architect is, it's kinda like subject matter experts in the field for, for Everpure. So I'm customer-facing. I work with clients adopting our virtualization solutions.
My team consists of guys that do virtualization, FlashStack solutions, and databases, and so we're kind of, like, aligned with these certain vertical areas. Yeah. Previous to this I was at VMware for seven years, actually with you, Langer. Oh. So we obviously had some great times, over there.
And then, was at a, a hardware manufacturer for about, nine years. Yeah. Yeah. No, Matt and I, for f- for those that might not know, we go back a long way, like babies and pacifiers, so if we get a little, little loose, that's why. Yeah. We don't have to be as serious all the time.
But, thank you for joining us, Matt. I know we've get a lot of interest in this, this topic around Red Hat, OpenShift, and what we- Yeah can do for that. Before we get in, I do wanna do a little bit of housecleaning for those, joining us. Obviously throw some stuff in the chat.
You know, we try to keep this interactive. I always say, you know, nobody wants to hear a monologue. But also throw stuff in the Q&A. I'll be monitoring that real time, so if Matt, you know, says something wrong or he brings something up that we wanna dive in a little deeper, throw it into the chat and then I'll
make sure I'll do my best. That's why I'm always kinda looking off to the other side of the screen to see what pops in, to make sure we don't miss anything. But with that out of the way, let's talk about the agenda quickly. You know, we have to level set between, you know, various folks, so we're gonna g- talk
about what is OpenShift. Maybe you already know, maybe you don't know, or maybe you're just kind of an inkling, so we're gonna cover that quickly. Matt's gonna give us a kind of a, a, a quick deep dive on VMs on Kubernetes. And then dissecting CSI on FlashArray, and that's kinda when the demos are gonna start.
So we've got We're gonna set a little groundwork, so we are gonna do a little slide where I have to be up front about that, even though we kind of try to lead with demos here. But we wanna make sure we're all at a level set for when Matt starts getting into, the demos. We kinda I know it well, maybe for myself, speak for myself, I understand what he's
actually doing. Maybe it's for me, maybe it's not for anybody else, but- How's that sound, Matt? Is that about right? No, that's good. And e- even to add to it, you know, we do have a VMware background. Yes. That's what we're gonna kinda take it from.
And that's what, you know, where a lot of people in virtualization are coming from. So we got a Rosetta Stone. You know, w- and hopefully we have something for everyone, right? Yeah. Like, a little bit beginner stuff, obviously here in the slides, then some more advanced stuff around Snapshot.
So, it should be good. Should be good. Yeah. I'll be the, I'll be the guy that goes, "So that means this in vCenter when you..." So b- that way I'm like, I can, I can simp- Yeah you know, connect the dots. Yeah. So, 'cause that's where, I mean, like you said, that's my background for way too long.
I don't even wanna- Yeah. Say how many decades at this point. So all right, Matt, well, let's just, let's get into it. We've bantered long enough. G- give me the- Yeah what's OpenShift? Like, just give me the, you know, the high level glance. Yeah.
You know, the 10,000 view. And I probably won't do Red Hat justice, but what I'll, what I will say, this is what Red Hat's really good at, is taking these open source technologies and adding, you know, enterprise governance control and automation around an open source technology. And that may be in the form of just front-end UIs.
That could be in the, the form of different tools to manage these systems, and that is what OpenShift is, is their wrapper, their enterprise wrapper around Kubernetes, right? And so when you talk about OpenShift, you know, obviously there's a lot that go or even just Kubernetes, there's a lot that goes into that. You know, we could be talking about pods and containers, which we always are, but we could
talk about, you know, cube vert VMs on top of those containers, GitOps operations. We're focusing mostly on the VMware portion, not the VMware, but the VM portion, the virtual machine portion of this, for those, that are, you know, wanting to get into OpenShift. And I think the one thing that's super exciting is the, the thought of, like, you
know, Kubernetes is where a lot of modern applications are going. Mm-hmm. Some customers are already 50% through that journey, but they still have They know that a lot of things will still be in VMs. Like, we know that there's going to be a lot of containers and VMs that sit side by side, for a long time.
And so one platform to run both native pods in Kubernetes and then VMs in there is actually very attractive, and I think that's why this is a hot topic. What's also really cool about OpenShift is that they do have a very flexible licensing model, right? So, like, you know, I do get some customers that come to me and say, "Well, we looked at OpenShift and it was really expensive." And I
usually ask the follow-up question is what version did you look at, right? Because- Yeah There is, you know, a SKU called OVE, or this OpenShift Virtualization Engine. And now, don't quote me on this 'cause prices change, but the last I checked it was, like, three grand a bare metal node, and that's unlimited VMs on that node.
It's not per CPU. It's not, you know, per core. It is, per- Or like amount of RAM or anything like that. Yeah. Right. Is that- Yeah, exactly. So, like, you know, there's blast radius and things you have to take into consideration.
You're not gonna shove 1,000 VMs into three nodes, because of- Sure of, of architecture things, but it's something worth considering, and this is why I think this is coming up more often. And then of course, the more, Like, that only gives you virtualization. You have these other additions, that we won't go quite deep into because that's more on the
Kubernetes side of the world. We're mostly focusing on virtual machines here. But if you need more enterprise, you know, containers, a comprehensive app platform, and, you know, some more GitOps operations, that's what these other versions are for. But that's, I think, what's, what's really drawn a lot of, attention to,
to OpenShift for virtualization. Yeah. Just real quick on that though, Matt. And I'm assuming, and again, we're not the Red Hat OpenShift experts when it comes to licensing or anything, but, like, I'm assuming it's like you can start with one and you could gradually move further to the right with license- Yeah keys or whatever.
I mean, there's no rip and replace or anything. It's just like put in a new key- Yeah and you're from just VM only to VM and Kubernetes, and then as you kind of shift to the right. Yeah. My understanding is that it's the same binary that you install. Okay.
It's just what's roped off and what's not roped off, so that's really nice to be able to, okay, I start with OVE and maybe I start with three nodes. I scale, I'm, adding more OVE SKUs, and then maybe I want some of these, these GitOps o- you know, skill, capabilities, that OpenShift can provide, and then I just upgrade my license across those nodes.
So that's, you know, a great call-out, something you can grow into. Yeah. So where, where does Everpure, you know, fit into this? So our Kubernetes, you know, strategy starts with Portworx, okay? Just plain and simple.
Portworx, has been around since the GA of Kubernetes. Someone's gonna correct me on this. I think that was like 2015, ish. Um- Just say it with confidence. Yes. 2015. 20- 2015.
You know, so, you know, Portworx has been working with Kubernetes since, you know, since GA. Portworx we acquired in 2020. And Portworx specifically has a software-defined storage capability of, you know, an SCS layer in Kubernetes that provides these enterprise class services
on any storage backend. Very powerful. A lot of people find a lot of value in that. That's what we refer to as Portworx Enterprise. Now, we're talking about the CSI today. That is primarily what we're getting into today, is how do I leverage FlashArray, with
my, current assets, within a Kubernetes ecosystem, which OpenShift is, and it's still Portworx. So if you install the Portworx Operator, you do not have to pay for that operator, and you can still use PX-CSI within that operator at no additional charge, okay? So you have access to that.
If you want the hybrid cloud capabilities and that software-defined storage plan that Kubernet, that, Portworx gives, which is very powerful, that is an additional, cost. It's not included in your FlashArray licensing. But the CSI in the Portworx Operator is, of no charge. So, we're gonna dive into the CSI today, but just to call out, people hear Portworx and
they're like, "Well, you know, I looked at Portworx Enterprise. We're not quite ready for it yet." Even if you're look- you're looking at using FlashArray with OpenShift, you're still using the Portworx Operator. You'll just be using the CSI storage, cluster. Yeah, so I Just pause there, Matt.
Like, and I know you're gonna I mean, this is obviously a deeper dive, but really it's, it's you have a journey choice is what I'm hearing from that. Yes. If we use Portworx as kind of like this umbrella, I mean, you had it on the slide where it covers everything, and then it's like, okay, that's the, you know, that's the top level of, like, don't think that as the product.
That's the, you know, that's the, the, the solution and then it's like, okay, that solution has two options for you, and depending on where you're at on your journey or where you're at, maybe you're an existing FlashArray customer, maybe you're not, right? Which could be the audience here today, right? Mm-hmm. Like, some people might be existing Everpure customers, some might not be,
so they're doing research. So you've got a kind of a, a fork in the road that also can come back together based off your journey and where you're going- Yeah just to be clear. And for some it's an and. Yeah. 'cause we're not gonna dive into w- why Portworx Enterprise or why FlashArray Direct Access or the CSI, you know, too deep today.
But we have many customers that are doing an and, not an or, right? Yeah. They'll use what we refer to as, in the CSI we refer to them as FADA volumes, FlashArray Direct Access. That is a acronym you're going to hear quite often. And, there's customers that have FADA volumes for certain workloads.
And then there's, customers that have Portworx Enterprise volumes for other workloads, right? And sometimes they'll split it, like my kube-virt VMs maybe are on FADA, and then my pods, my native pods are on Portworx Enterprise. Or maybe it's a mix of, you know, Portworx Enterprise is on more, kube-virt VMs, but certain ones are only on FADA.
So this is very much an and. Yeah. And, and that's what this slide, even though it's busy, this is not Langer's favorite slide. You know, I mean, I mean- Yeah just called it out. But it's, it, it's sort of like trying to depict how both of these can stand up in the same environment. So you have your OpenShift worker node, right?
That is the host layer at the top with the dotted lines. And we're gonna j- jump into more Kubernetes stuff. There's a pr- a PVC, a storage class. The Portworx Operator sits, within the host, installed as a certified operator in OpenShift, and it calls a storage class for a given resource.
That storage class defines if you use a Portworx Enterprise volume, you know, PVC, or it's a FlashArray Direct Access. And again, the benefit of the Portworx side of it is- It can be local disk, it could be a competitor's array, or it could be FlashArray, and that includes, like, virtual disks that are in the cloud, like in, AKS or EKS, right?
So, like, Portworx Enterprise has a very flexible deployment model across, commodity backend storage devices, and we've got some customers that came over and they're like, "Hey, I was HCI on this one platform before, and I've already got these drives. I really wanna leverage them." That's Portworx Enterprise. That's what gives you. It's like an HCI product for Kubernetes.
Then we have some customers that are like, "We're not quite ready for Portworx Enterprise yet, and we're an all-flash FlashArray fleet. We're just gonna go CSI first, and maybe we'll go into Portworx Enterprise for some hybrid cloud capability." So, you know, again, a lot of different use cases. Kind of a busy slide, but the biggest thing is this, this capability in Portworx Enterprise.
We're here to talk about what, what's capable in the CSI today. So KubeVirt. What is this KubeVirt thing? You know, it has been, a whirlwind of change when it comes to Kubernetes running virtual machines. And even on the OpenShift platform, it's
amazing how much just 4.18 to 4.22 has changed and what it looks like. So if you haven't seen it in a while, we're gonna look at it in the demo. It's pretty powerful. But this, the te- underlying technologies are not necessarily new, right? What we're doing is we're running a Kubernetes pod that has a KVM process, and KVM is good
enough for AWS and GCP, right? This is a known hypervisor, a very, robust hypervisor. Red Hat themselves ran a project, called oVirt, to do virtualization and then, you know, has really adopted the, this OpenShift virtualization engine as, like, the new VM, virtual machine stack, that they wanna use.
And so y- even though KubeVirt itself is a newer project, the underlying technologies have been around for a long time, right? That's, that's really the basis of this. So you heard VMs on Kubernetes. So all sorts of questions for people that haven't necessarily done KubeVirt yet are
usually like, "So the VM is a, a pod now?" yeah, it, it is. It's a container, and it's just like a typical, typical Kubernetes pod, but when you do, like, a, a, you know, show all pods or OC get pods in a namespace, you'll see, virt launcher pods, and those are KubeVirt VMs. So again, it's taking a container, and it's, isolating the KVM process for each of those
virtual machines. You'll see those in there. The common question is, this is my question when I was like, "Where's vCenter," right? Like, that's- Yeah, where's my GUI? Yeah. I'm not- Like, where do I click on stuff? You better not tell me I'm going all CLI and not going to each individual host running this.
It's a browser tab. It's always been a browser tab, right? I mean, the actual services run on what are called master nodes. So it's a little bit different than just, like, a monolithic vCenter like we're used to in VMware. But at the end of the day, it's a browser tab that manages all these systems.
We're gonna see that. We're gonna be in that browser tab. And I guess at one point, you guys remember we're, if there's VMware users in here, we all said, "You take the C# client away from my- Yeah my cold, dead hands." Yeah, I remember those days. Yeah, that was- Yeah. Yeah. The fat client versus the web client, for sure. Yeah.
Then it was Java before it was HTML5. Yes. That was, that was an ordeal. That was a change. So and, and, you know, this is a change too. You have to push through it. I have to write YAML to power on a VM.
You could Listen, if you're comfortable with YAML and you like YAML and that's what you wanna spend your day, yes, absolutely, Kubernetes and YAML are a, a married, duo that is always there. There's always YAML under the hood. But the UI wraparound, that OpenShift has is very powerful, and they have very much focused on click ops. So if you're used to just clicking around
vCenter and you're not a power CLI person, you don't do any ESX CLI, OpenShift can work for you, and you're gonna see that. Mo- most everything we do is outside of the CLI. Yeah, it's like, just think of, like, the VMX file. Like, there was always a file you could edit.
Yeah. Right? There was always a text file or whatever you wanna call it somewhere, right? I, that's kinda how I've always processed. I mean, I get, you know, yeah, you know, for f- but I just think of it that way, right? We've got a GUI now. If you need to edit stuff, you go into YAML.
It's no different than editing a VMX file or something. And having worked for this platform for a little bit over a year now, you start getting comfortable with it. Sure. Like, it's just like anything else. Just like anything else. Yeah, for sure. You know, DRS is, is there.
It's called scheduling deschedule or I'll kinda, like, you know, kinda wrap up this, this section. The data store is, is different. This is not VMFS, and that is one of the big things we'll talk about in this, platform, and it only takes about 40 minutes to become a Kubernetes expert. Do you believe me? I don't know.
It takes time. I mean, I do because I've known you for so I mean, I always default to believing you, Matt. It takes time, but you know, more you work with the platform, the more of an expert you become, and, you know, the more you know about Kubernetes, sorry and congratulations are also in order. Yeah.
This is sort of the Rosetta Stone. Maybe this is great opportunity to s- screen snap this 'cause I'm not gonna go, word by word. I'm sure there's actually good Git- GitHub repos out there that show this, conversion. But, you know, basically, like, if I were to take one of each category, your ESXi host is a
worker node, and it runs a Red Hat Core operating system. That's where the KVM pr- pod's gonna be ran, and that's kinda, like, your host layer. Your data store is, is This is gonna sound really familiar for, for VMware people. The You define a storage class, and that defines the storage services, right? I came from VMware. I was, a VCNSC.
We called this storage policy-based management. And this is very much a, you know, a driven policy-based approach that's defined, and it's, very vVol-esque, where every object has its own vDisk on the backend. We'll look at that in the demo. Networking is a beast in this.
It's on the, you know, the open virtual networking. It's a, overlay, and end multis with, things called network attachment definitions. And of course, you've got things like vMotion. We'll demonstrate that today, and HA capabilities. So all these things do exist.
Feel free to screen snap. This is sort of like your Rosetta Stone. All right. So, again, to just kind of reiterate because this is what really helps me- Hey, Matt, this is the last slide before we actually get to demos, right? Because- Yeah.
Well, there's, there's one more, but yes. Okay. Just wanna make sure. Really close. You got a storage class, you got a PVC, the CSI driver, and you have a running disk, right? You declare something within the storage class. What you stop doing is really this individual VMFS LUN management that you're used to if you
come from a VMware ecosystem where you create a LUN and then you, you, you provide it up. So, you're not doing logins and re-scans. You are configuring some of the multi-path out of the gate, but once things are configured and up and running, everything else is automated where the two systems work together, the two systems being the OpenShift platform and the Purity, you know,
Enterprise Data Cloud. They're communicating over APIs and creating these volumes and attaching them. And then the last thing I'll, I'll leave here is, you know, MTV means different things to different people, right? Like, if you're '80s and '90s, it's where Beavis and Butt-Head was watching, you know, music videos.
Yeah. It was the first reaction video before YouTube had reaction videos, right? That, that's right. That's right. If you're, if you're, you know, an OpenShift guru, it's migration toolkit for virtualization, you've probably heard the VDDK has been taken offline for, certain uses.
And so one thing to know if you are on the same FlashArray, the You do not need the VDDK to do an xCopy storage offload migration. Okay. So we've got, we've got documentation on how to set this up. We're not gonna demonstrate this today, but know that it's out there.
We do have integrations in MTV that do not leverage the VDDK, and they are super fast 'cause they're basically, using an iSCSI xCopy command. So it doesn't need to be on iSCSI protocol. That could be fiber channel or, or ethernet, but, you know, worth knowing there. So with that, let's finally get into demo.
I appreciate you guys sticking, sticking through. Yeah. Hopefully, guys, like we wanted to do some ground level. Like I said, that was a lot of slides, but we do have demos. We weren't like Yeah. This wasn't, it wasn't a bait and switch.
But here we go. Um- So Matt, I'm gonna stop sharing and I'll let you go ahead and take- Yep show up your screen here. And let's make sure that you can see my, my RDP session. I don't see anything yet. There we go. It took a second.
Yep, now I see it, Matt. Cool. All right. So we have this fancy little checklist, to keep us, on track because, Langer and I tend to start rambling, 'cause we're good friends. We got, we gotta have something to, to keep us kids in order. Yeah. Um- Producer Laura's always in the background going, "Speed it up.
Speed it up. Speed it up." Yes. Come on. Come on. Get so we're gonna ch- tick these off, but just to review what we're gonna do today. We're gonna view what a CSI storage, configuration in OpenShift looks like, right? So we're gonna do that. We're gonna perform a compute vMotion so you get a feel for that, 'cause that's one of the things that is a standard, you know,
virtualization te- technology- Yeah that you would expect. So we're gonna just experience it to experience it. We'll create a VM from OpenShift, which I love their template, creation screens and how templates work. We'll talk about that. And then we'll do a snapshot and a restore.
So if you haven't seen the Red Hat OpenShift, platform, this is what it is. Again, it's a browser tab. It's a modern UI. Now where a lot of the enhancements have been made, I made a comment about, like, 418 to, you know, the newer versions, is in this virtual machine.
Hey, Matt. J- I'm sorry to interrupt you, bro. Can you- Yeah. It's a little hard for me. Can you zoom in just a little bit? I don't know if the For the audience, if that's- Yeah. And if somebody can give me a thumb up if that's good enough, or if you want him to zoom
in a little more, that would be great. It was just a little hard for my, my aging eyes to see. Yeah. So. And I'll have to zoom out for a couple things. But, yes, you know, definitely let us know in the chat if you can see it or if I need to make it any larger. So you can see it's, you know, a very, you
know, vCenter style, UI. Like, you've got, basically these are namespaces, or they call them projects within OpenShift, and they're kind of structured like folders, so you can attach different RBAC controls to different organizations just like you would do in a vCenter environment if you were giving vCenter access to different BUs to deploy virtual machines, and you would like,
you know, do, LDAP integration to give them certain, you know, permissions to certain folders or certain hosts or certain clusters. So, you know, you'll, you Again, it's come such a long way if you haven't seen it in a while. But to get a feel for what a configuration looks like in, in OpenShift for FlashArray,
you have to start at the inst- installing operators, and I've already got the Portworx Operator installed. Like I said, this would be if you're using the CSI or the paid-for version of Portworx Enterprise. And you can see I already have, a storage cluster defined, right? So basically, this is what defines the configuration, of what
resources I'm using in Portworx. And you can see here I'm using FlashArray. And I've got iSCSI configured for these, and these are my allowed host interfaces on the iSCSI network. And that's, kinda defines, like, you know, how it connects. There's also something that we won't look at
here in the UI- 'cause this, it's defined as a secret, is the, is the pure JSON file, which has basically your FlashArray management interface and a API token. That is how it connects and provisions these resources. That also has to be created to stand that up. So I've got those two things configured.
The last thing I need to get started to make sure that we're actually leveraging FlashArray for the CSI provision volumes is I have to make a storage class. And you can see right here I've got this SN1X90R2F0533FSA lab. That's the default storage class. If I go look at its configuration, like we said, we warned there's some YAML here, but
not all YAML. Is this, the- we got the Portworx, provisioner, right? That makes sure that uses the Portworx operator, pxe.portworx.com, and you got this parameter of backend pure block. And then I, I'm calling out a pod name in this.
I don't necessarily need to do this here. Why would you do this? If you've got, multiple FlashArrays and you wanna, say, use multiple FlashArrays and add different storage classes to consume those different FlashArrays, y- the way you would do that is you would, define a pod in each of them and call them out in this YAML file.
And so this would use this pod, but say I had another FlashArray I wanted to use, I'd have another storage class that would define another pod. And so that way users, when they're deploying, they could have, like, maybe you have a storage class that's a premium tier and then, like, a standard tier. Like, we have an XL1 and then we have a C, a series array.
That's how you could call different Flash Arrays, and that's how you can define policy through these storage classes, which is really cool. So Langer, we finished our first, you know, overview of just our first demo. Mostly show and tell. But we should celebrate.
We'll tick it off. Hooray. You're the winner. We're the winners. We got one of four done. All right. So let's hop in. Let's see what a standard techn- you know, standard feature, like,
like vMotion looks like. And it's, it's really pretty basic, but it's, it's worth seeing. So here's all my virtual machines that I've got created. It's in this, p- specific project. Let me go actually show you the nodes, 'cause that, that also does help, help you understand
the lay of the land. So here we've got, a total of six nodes, but what I've, actually have is three nodes that are running the control plane, like the master node. So that's actually running, again, the control plane, like the vCenter services is kind of way to think of it if you're a VMware user.
The worker nodes are the actual nodes that house the, the workloads. Okay. Right? Now, you can run consolidate. You don't need six nodes to start this. You could start with, three nodes. They even have a two-node arbiter configuration, so you can get even smaller.
But I've got mine split, and in a production, enterprise, class system, I'd probably split those two, so you have the control plane on certain resources and then the worker nodes on other resources. So my VMs are running on these nodes. How would I know that? Well, I go into my, virtual machine section, and I will have to, like, take a step out, so I know it'll be small.
But right here, this VM is running on I know people can't see it, but worker04 is what we're sitting on today. And so I, maybe I just need to move it over 'cause I wanna balance some things, or maybe, maybe I just wanna do it in preparation for, like, maintenance mode. Now, if you, deschedule a node, right, like you're, you're going to, you know, do some
maintenance on it, there's, there's services to move that off. So it's not like you have to manually do this. But let's just say I wanted to move this node. I go to Migration. I've got the two options, like I would expect, Compute and Storage. We're just gonna do a compute.
I can do automatically select a node, so there is DRS-like functionality- where it chooses which node to put on. But we just wanna go and put it on worker05. We migrate the virtual machine. Runs in the background.
Does what we expect. It looks very similar, Matt. Yes. I mean, if you've done one of these platforms- As a non-OpenShift guy or whatever, like this looks very- Yes. Exactly. So now you can see it's already over on, worker05, and it's up and running. And you know, again, same thing.
Maybe a dropped, ping but, you know, essentially alive and online. Yeah, you gotta do the thing when you first did vMotion where you had both the consoles open, and you, like, you move the mouse. Yep. That's right. I just remember the first time I did a vMotion, I'm like, I was showing my boss, I'm like, "Look, and now it's gonna drop one
ping," and you know. Yeah. Yeah. So well, guess what? We get another celebration. We just- Oh, wow. Sweet completed the vMotion, Kubervm. This one's the easiest one, but everyone wants to see it, you know, just get a feel for it.
We can celebrate. Yeah, it's more of just saying it's there, right? Like- It's there. It's there, and now- You- you've gotta have a live migration. I mean, that's table stakes- Yeah right? So. And, and now I've proven it, right?
Right. So now, now the proof is in the pudding. Um- You've proven the literature is accurate. So, let's, let's, before we clone, we make a template deployment, I do wanna explain something real quick. So, this array back here is housing these virtual machines.
How do I know? I, like I'd mentioned, we have a pod. Let's go look at it. I think I've got, oh, CP and it's FSA. Right here. So this is the pod that houses all these PVCs, and as soon as I log in here you can see all these Px PVCs created here. Because, again, for each vDisk in a KubeVirt VM, a individual volume is
created and mapped automatically. Like, once you set this up, that is what the CSI does, is there's these little, like, sidecar pods that run these, the code to automate the creation and attachment of these PVCs, right? So one of the common questions is, like, how do I figure out, what volume makes up a
certain KubeVirt vDisk? And a great way to do that is you can just sc- scroll on down to Storage. Let's say we wanna look for this, Scarlet Tyrannosaurus. These are auto-named from the, the, template generator. But I can go to Persistent Volume Claims, and I can do Scarlet- And I can see that this is
the PVC name. I just grabbed this last couple, characters of the ID, and I pop it in here, and that's what makes up that vdisk. It only has one vdisk. I can see its reduction, you know, ratio. I can see the size and how much is actually used, and I can see if there's any snapshots
on it. So y- it's not your job to create these volumes and to do a bunch of the backend. It's all automated, which makes this a very powerful platform. I mean, it works as one cohesive unit. But you can still see and monitor and look at these objects on the backend.
Now- And I think- Yeah as, as a guy that spent a lot of time in his career, as you know, Matt, troubleshooting storage and performance, like, I, I feel like that can't be understated that in this regard, you know, there's not this like, how many VMs do I put on a, a LUN-type conversation. Oh, man. Right? You know, yeah, if
I I'm gonna be this guy. If I literally had a dollar, you know, for every time I was asked, "Well, how many VMs?" I'm just like It, it was always, "Well, it depends." Yeah. So- And then- just, like, the kind of, vvol's like behavior here of like where you don't have to worry about that.
I mean, like, to me, I mean, that's one thing that's just standing out, is you're I know it's not the point of what you're showing, but it's like, that's like immediately where my mind wanders. Like, I can, I manage these individually from a, a performance, and I can kinda see what's going on as opposed to like, all right, this, this LUN's got, or volume has got 20 VMs.
Which one of these is stepping on the other guy- Right or gal? So. Yeah, so and I know Cody Hosterman's ears are burning. You know, the, the vvol's, value proposition of no more VMFS LUN management. You know, I think the thing that, all of us are coming to understand, And I'm not saying it's go- good or bad, right?
There are two different ways to do this, but VMFS came with pluses and minuses, right? Yeah. And one of those was LUN management. It is a terrific clustered file system, and a clustered file system, again, can have some pluses and some minuses, and one of them was that LUN management. You're not doing LUN management here.
You configure that basic stuff I showed you at the beginning of the demonstration, and then it's off to the races. And since they are independent volumes, you're not worrying about metadata contention or LUN locking or any of those things that we, that we have experienced that have w- used VMFS for decades, right? Yeah.
So to- And that's why I started- Great call- my career on file in VMware. Yeah. Like NFS, so. Yeah. So again, simplicity is the key here, and, very vvol-esque- Mm-hmm is, is sort of this, this, this methodology. Okay, so, hopping into templates.
I, like I said, this is one of my favorite features of, OpenShift, and this is not a knock on VMware. They had some really cool template, catalog capabilities. And but this is some of the benefits of building a modern system on modern, technology, is you can go create a virtual machine, and you've got this template catalog.
And you can make instance types too, which is really cool. Again, you define users can only access a certain namespace/uh, project like we were seeing in the folder tree before. And then you could define certain, VM sizes with their operating systems like a cloud would, all right here within this, this, this template creation.
I'm just gonna use the template catalog. You'll notice these blue bubbles above each of these, or certain ones here. What those are is once you've created the FlashArray configuration, if you define the default storage class, it pulls down the images for those, virtual machines and stores them as a PVC on the FlashArray.
Which is really cool 'cause what that means is that it's actually going to make these deployments really fast. So I'm gonna do a Fedora VM. Let's just say it's Fedora. Let's give it a name. Let's say, you know, expert-led demo.
And this, y- this screen you can configure the CPU, the memory. I'm just gonna do the default. And the disk source is default because that's using the default storage class. Because what that means, when I click this Quick Create, it's gonna go find that PVC on the FlashArray that has that image, and it's not going to copy the data over the network.
It's actually going to do a vol clone off the FlashArray API- Oh, nice and then give it to the virtual machine and start it up. So you'll notice this provisioning process is very quick. We're already in a starting mode. So, again, I really like this template system, and this is a great example of how the
OpenShift platform with the CSI driver and FlashArray acts as one cohesive unit using the technologies of both platforms, right? And you know, there's obviously things like xcopy and other things that are used on VMware, and you could set up other things that get similar output, but this is, like, out of the box. Once you get this all configured, you d- it's,
once you define a default storage class, it starts pulling down those images onto PVCs and storing them on your FlashArray. Some of them you're gonna have to custom make. Like, you'll notice I had some Windows, VM ones. But that's, that's what that looks like.
And also, you know, it'll maybe still th- going through the boot process. One other common question I get is, does it even have, like, a console? It definitely does. It's right here. I like this console in the sense of, you know, you can actually, you know, see the user's Fedora.
But it's gonna be a semi-complex password maybe. Yeah, I don't wanna type that in. Thank God for this paste to console. Oh, I got I didn't hit enter on the- Yeah. Uh- Be smarter than the console.
Yeah, be smarter than the console. Paste console. Let's see. Got it in. There we go. Yeah, there we go. So, again, this is what the console looks like. This is a cloned, VM from template.
Really cool, and we get to party afterwards because we get to tick off another item off the checklist. Hooray. Hooray. We're on our last one. Um- Yeah, man, I'm gonna pau- I'm gonna pause you- Yeah really quick 'cause we, we got a question. I wanna make sure, you know, we're level
setting and keeping folks, um- So we got the question, I'm just gonna read it verbatim. Mm-hmm. And it says, "So all the volumes under the pod in the pure interface, because you specified a pod name in the storage class YAML." Mm-hmm. "So all the volumes are under that pod in the pure interface because you specified a pod name in the storage class," right?
So it's- That, that's correct, yeah. Okay. Yeah, so since, since we have in our storage class Let's go over here. So literally, like this is the, this is like the foundation. Is it- This is the ground floor. Like, you've gotta build this and set this up.
Exactly. Like, and that, you know, again, is, storage policy-based management is the best comparison to it. And I know not everyone used storage policy-based management in vCenter, but the idea is you have a policy as, like, a storage class, and that defines where it goes. And so I could have multiple storage classes.
So for example, like that was a great question. This storage class has that pod right here called. And you'll notice, I'll just Control-C it, and then, I mean, we're already in it here, but if I click pods and I paste it in here, it's here, and all the volumes that have that storage class will be in that pod.
Now, I actually have multiple storage classes for testing. This thing's kind of a mess. It's a lab. You'll see there's some that have a pod and some don't, and I've been doing different types of configurations. But the real use case for a customer is, like, maybe I've got two FlashArrays.
The way I call those two FlashArrays is via storage class in the pod name. So I'd have pod A on FlashArray A and pod B on FlashArray B, and I'd have storage class A for FA, A and then storage class B for FA-B go into their respective pods. Yeah. And so I could have KubeVMs calling those different ones. Maybe you call the storage class something like premium, you know, FlashArray versus
standard, which would be like our TLC, DFMs versus our, you know, high-end XL line, right? Yeah. That's a, a, a real use case. Or you just got multiple FlashArray assets and you're trying to fill them up appropriately. Big call-out here, of, of, of those things.
Yeah. And Cabaldev, I hope that answers your question. If not, please throw something in the chat and we- we can follow up because kinda what I took from all that as well, Matt, is, and I, I'm sorry to always draw these correlations, but that's just how my mind works 'cause of, you know, muscle memory. It's like with that storage class, when you
created those VMs, and notice we didn't pick anywhere to s- like, really land it, right? Like, you didn't say, "Pick volume one, volume two, volume three-" Yeah or, you know, volume two, production or whatever, like, 'cause you've already predefined all that stuff. So it's just gonna land based off these p- these policies and, you know, and like you said, Matt, there's probably a reason why you would have multiple policies based off where
you want those VMs to land. So you're, you're doing a little bit of the pre s- subscription of where you want things to land even before you start building out or cloning out your first virtual machines is kinda what- Yeah I took that. Exactly. Okay. Exactly. I got one other question.
Maybe we can, if it's too long and save it to the end, we can totally do that, but, Jeft asked, "You've talked about block access for storage. What about NAS or NFS as an option?" yeah, so you can, you can do FlashArray direct access with, with file pods, and that's for, FA and FB. So that would be set up, I believe that is set up in the storage cluster.
And you have to, instead of pure_block, it's pure_file in that parameter of the storage class. So that, that's, that's where you'd make those changes. So file, a- and block are supported. Okay. Good, good question.
Excellent question. And we got a couple more, but I'm gonna let you get into this, and then I'll spring them on you at the, towards the end. Yeah. A matter of fact, when we're waiting for the restore, I think that would be, a good o- opportunity- Okay to take another question. All right, so snapshots. I just wanna be mindful of time, so- Yeah,
absolutely don't wanna take everybody's time. So snapshots. I've got this, VM here that I wanna perform a snapshot on, but first we gotta create some unique data. So let's jump into the Red Hat, console and, hop into, this VM. I need to double-check.
This is CentOS. No, I wanna see you type it this time, not click it. Oh, it's not gonna happen because when people are watching me, it takes- Right, right. Oh, actually we're already in, so I didn't even have to worry about that. So let's make a, let's If I LS this directory, we're in the home directory.
You can see it's a blank output. There's no files. Let's make one, called experts, expert demo. Just make it a TXT file. I'm a VI guy. Let's say Jason loves Red Hat OpenShift.
Hooray. Hooray. Hooray. We LS. We now have that. Let's just clear it so it's at the top. So we can see that we get that file in this, directory. If I cat it, it's got, the data in there.
So we've got data here. How do I take a snapshot? Again, this is We could almost do everything here. We were talking about this, Linger, outside a FlashArray system, right? Like that's the benefit- of this.
That's the, the power of this platform. But we wanna keep things, you know, tracked so we understand the storage people, how it's working on the back end. I've identified this, the volume that this VM is sitting on while, Linger is talking, and so this is that volume right now.
So you can see there's no snap- snapshots on this VM as we speak. I go into, these are some older ones that were removed. But if I go and I hit take snapshot, I'll just leave this default one, hit save. You'll see it's succeeded. If I go into this, right here and I refresh, you can see that now
shows up. So again, another example, and this one's even, like, more trackable of a, an integrated system. They're calling these APIs where the hypervisor/uh, cloud platform plane is working with the storage underneath in a unified fashion. So now I have this snapshot.
Let's go, you know, accidentally remove- our data And so now we can see it's no longer there. Now, this workflow, you may have different workflows for how you'd, recover from snapshots. Let me be very clear about that. But this workflow, the way it's integrated in this, is you do have to power off the VM
before you revert to that- Okay snapshot. So we're gonna hit stop on this virtual machine. So it's more of an over- 'cause it's an overwrite, I mean, basically. E- exactly. Yeah, okay. This is an overwrite operation. You absolutely can create kind of your own workflows.
You can even create some scripts to, essentially maybe make a clone of, off of a, a snapshot. So I- That was gonna be my next follow-up question . Yeah. Yeah. 'Cause I think that's, you know, it's worth calling out, like with our vSphere plugin for example, that is kinda the output on VMFS, is we basically take a VMFS, snap, mount it,
resig it, ta- register the VMX file, and then move it over until it's in an off state, and people like that kinda workflow. This just happens to be how this workflow works, so it's worth calling out. All right, so this is our snapshot down here. This is the one that we were, wanting to revert to to get that data back.
All we have to do is go to Since it is in off state, it's hard to see, but there's a little red, you know, stop next to the VM. You hit restore virtual m- machine from snapshot, click restore, and it just succeeded just now. And so now I can power this guy on, and it'll take a second to, to come up, but we'll see our data in there once we
reconnect, and do that. Maybe this is a great time, we can take a couple more questions as it's going through. Yeah. A- and actually, I've got a question on this, Matt, because, like, I've always I've been raised that, that there's two types of snapshots.
Like, there's the virtual machine snapshot, and then there's- like, the array snapshot, of which is kinda what you showed. In my mind, that's kinda what you showed there. Does that context exist in OpenShift, you know, or is it, is it always an ar- I'm just gonna say an array-based snapshot as opposed to, like, a hypervisor-based snapshot?
When you are, you know, set up with the storage class and you've got, the CSI configured, it's always an array-based snapshot- Okay which is very powerful. And that's what you want because it, you see how fast this is, right? Right. And how efficient they're going to be. And that's what we really wanted to demonstrate here is this is not a
hypervisor-based snapshot, which can lead You know, again, it's, they're typically slower. They have to keep so much extra data 'cause they don't know where the blocks are. Right. And this is the benefit of a tightly integrated system that acts as one unit. Okay. I just wanted to, wanted to ask that.
Um- Yeah we did get a couple other questions. We, you still got time, or are we still waiting? Looks like we're logged in here. Let's- Okay, why don't you go through this and then- look at this and, and then we get to tick off the last one and do a celebration. Yeah. So let's log into, this virtual machine.
And if I LS and cat it, it's there. So again, just, uh- it is an overwrite, you know, operation, but tightly integrated, easy to use, a fantastic, way to, to just quickly restore a virtual machine. Or maybe you're about to perform an OS update, and you wanna do a quick rollback, that's a great way to do it. Guess what?
We got it all. Nice. This is, this is it. This is a big celebration. We finished. And I knew that was a serious file because you used my first name. 'Cause I could probably count on one hand how many times you've used-
first names in a decade. But- Yeah no, no- It's usually when you're in trouble, right? Right. Us- it usually is the full name. You get the middle one in there. No, thanks for all that, Matt.
That was, that was great, and I know I'm checking my clock here. We're, we got a little time, so, but we did get some really good questions, and I wanna- Okay. Yeah. Some of them I think you might know, I'll be honest. Some of them I don't know for sure.
Yeah. Um- And we can follow up if we- Yeah if we don't have the answers offhand. But let's, let's have at 'em. Yeah. And then the, so the first one is from Alyssa, I know Alyssa, I hope I'm saying that right, is, "Does OpenShift work with Cohesity for
backups?" Now, I know that's not really our realm, like, you know, but I just didn't know- Yeah in your travels, like, what's our backup integration? Because obviously, you know, we work closely with Cohesity, Commvault- Yeah VM and these other guys, so. This is a great point, and this is where, you know, we have to acknowledge some of the gaps.
So right now in the 4.x release, there is no change block tracking natively on this platform. It is a big pain point for customers. So people that are backing up, cube vert VMs, they are putting in guest agents right now. However, there is a beta for this new change block tracking.
I think that they're trying to look for it in the 5.x release. Don't quote me on that. I think that's what they've talked about in some public roadmaps. But you know, that is, that is Red Hat's roadmap. I just wanna be, cognizant that that is a futures.
But today, no CBT, so noth- nothing natively on the OpenShift platform for Rubrik, Cohesity, Commvault, et cetera. But stay tuned. That is something Red Hat is working towards. Yeah. And also, I would also say, you know, that's
not, like I told you, not in the Slack or whatever in the message, it's I would also follow up with Cohesity. Don't use You know, that's what our understanding of it is. They probably know more about it. But, just double-check with them as well. So I, I would, I would say what Matt said was a trust but verify sta- statement.
So, hopefully that helps. So thank you for that. Here we go. Here's another one. It says, "Can you clean up that snapshot after reverting to it?" So the actual backend process is it clones the volume and then maps it to the pod, so it's already technically, cleaned up.
And if you have a storage class that's, delete on, on reclaim policy, it will delete it on the backend when it's unused. So, a little bit of nuance there. Depends on how your storage class is configured. But the workflow itself clones a snapshot as a volume, then maps it to the restored volume so
that snapshot's already removed because the, the volume gets, deleted. Now, it, it will go and if you have an eradication bin, it'll stay in there for however long the eradication bin is. So it'll be kept around for a little while, but it gets cleaned up on the backend if dictated by the storage class.
Got it. Okay. Hopefully that answers the question. If not, again, throw it in the chat and we can follow up or find something maybe. Let's see. Oh, good. Elisa, thank you for confirming that. Okay, here- there's a question from Wes that says, "Does that snapshot then act as a
crash-consistent versus application-consistent since it has to shut down to restore?" Yes. It would be a crash-consistent. It's not queuing the, the memory state, so it would be a crash-consistent, uh- Yeah restore. Okay. G- great question. Yeah, right? Like, so thanks for that, Wes.
Mm-hmm. I think there was one more. Where's my Oh, yeah. This one's not related to that, but more, I think, to your, our, our I want my MTV slide, I'm guessing. Yeah. It says, "Is there any mechanism to migrate from a vCenter environment to OSVM?
Cold migrations would suffice if Pure can see both vCenter storage and OpenShift storage. I would s- I would I assume it would need to convert the type." And I'm assuming this is where- Yeah maybe MTV comes in a little bit. I don't- No, yeah. So, on, what we were talking about around MTV and X Copy, so you, you do have two available options to you even though the VDK has been
taken down. Cold migration is one of them. So you can do- Can I bring up that slide, Matt, real quick? Would that help at all, or just- Yeah, absolutely. Okay. Here, let me stop my share. Yeah. Maybe- but that's, that's a great question.
So you'd be installing MTV, and what MTV does is you, you configure a source and a destination environment with, with an MTV. And so in this example, you have a vCenter environment. Your source would be a vCenter, and then the destination would be OpenShift or an OCP, platform.
And, the VDK was taken down, right? So that's how you would do what's called warm migrations, where it would basically read that VMDK file and put it in, and that's agnostic to whatever storage type you're going to. That could be Portworx Enterprise, FlashArray, ex- you know, other, platforms, et cetera. Cold migrations also are the same.
The only pain there is that you have to literally turn off the VM and migrate the data, and since, you know, VM tools is not on, it's a full, copy of the entire vDisk. So, you'll have downtime there, right? The, the optimal one, in my opinion, but it is comes with caveats is if you have a source VMware environment and OpenShift on the same FlashArray, you can use this MTV with storage
offload migration. It requires configuration. We have some guides on our support site. There's also some, some good, documentation just online in general on how to set this up. But basically, you, additionally to the standard MTV setup, you set up what's called a,
a storage map, and it's a offload migration map. And what it does is it basically SSHs into the ESXi host, uses VMKFS tools to find the VMDK that you're trying to migrate and then uses a, a SCSI X copy command to make a new volume. What does that all mean?
One, the VDK is not required, so it works. It does need to be on the same FlashArray, but since it's on the same FlashArray and it's a SCSI X copy command, that means that it will be very fast. So literally, I've done this in the lab. Doesn't matter if it's five terabytes or 50 terabytes, that thing will go in about five
minutes because there's no data transferring the network. It's basically the time of just making the virtual machine at the destination environment mapping the PVC. Okay. So really, really cool capability. I think we answered Joe.
He said he's gotta drop. Joe, enjoy the rest of your day. Thank you for attending. Hopefully, that gave you what you needed. If not, it sounds like our support site's got some more further details. And reach out to your account team. Yeah. You know- Others- happy
to, to talk to you guys. Um- Your VAR of choice, all those things. Yeah. Mm-hmm. Let's see. How are we doing on time? Are we We've got a couple more minutes. I wanna be respectful here.
I know there was another one. I thought it was a good question from Yeah, from Jonathan. Sorry, it was further up in the, the chat. Mm-hmm. 'Cause it's something we didn't really talk about. He's asking about a specific feature.
But he's asking, "Is there any limitations with an ActiveCluster setup?" And I think that opens the door to other like about other Purity futures, fe- fe- f- ugh, features as well, like, you know, SafeMode. Obviously, snapshots work, but what about ADR and these other things? So can you talk about ActiveCluster first specifically to Jonathan's question and maybe
expand that to the other features or- Yeah I might put you on the spot on that one, Matt, a little bit. Active cluster is in works, for some support, on different protocols. Asynchronous can definitely send the data, so ADR and async, replication does work. But ActiveCluster needs, some further validation, so not quite there on
ActiveCluster depending on, you know, the, the protocol type. But the asynchronous features, do get the data over there and you, you can recover them. Yeah. What about, like, SafeMode? SafeMode, as long as you have the eradication, you know, you get that ratcheted up- Yeah Safe mode does absolutely work, since it's already just integrated inside that- Yeah machine.
I, I figured that was the case, but I just wanted to- Yeah. It's not- I wanted to put you on a record- Yeah. You don't- on a recording, so. That would be a great example of where you would be, adding those P groups to like a pod, for example, to make sure that, you know, all those are meeting your SafeMode requirements. So. Yeah. yeah, thanks, John,
and thanks for the question. Maybe, maybe producer Laura can put in the chat. I can't remember. Do we have the support link? In the resources, 'cause I'm sure some of that is in there, Laura. If not, I can f- we can follow up with folks the link, 'cause I'm assuming some of that's
covered in these support guides, right, Matt? Yes. That's my guess. Exactly. And this is, again, another area to keep, you know, keep refreshing those pages, 'cause we have been making, big efforts into getting more documentation around the OpenShift platform on our support site. There's obviously a lot of documentation on
the Portworx side for the CSI configuration, but these things are on ActiveCluster usage. Even things like host configuration on what's an ideal, what are called machine configs that configure the host level, are constantly being updated. Like, we have a version, one that's out now that's gonna be updated to an even better version here within the next week or two.
So, you know, go, go to both, you know, support.portworx.com, but also support.everpuredata.com, to stay up to, to find the best practices guides. Yeah. How do you You know, quick start guides, how to use with ADR and Async, and ActiveCluster when we get there. Okay, cool. And I'm just looking at the clock. We've got only a couple minutes, so I see one
last question. And actually, Matt, this, I can actually answer this one, so you're off the hook for now. Okay. Paul, we do have similar presentations coming up for other hypervisors. You mentioned, you know, HPE and XCP. Those are coming. I don't know, sadly, the exact dates.
I just know they're coming. So I hate to say this, but watch this space for further updates. Probably within the next couple months you're gonna see at least one of those. So can't give you exact dates, but just, you know, maybe watch our website or your email, depending on how you got notified of this one.
They are coming. I do wanna Like I said, it's almost time, so I do wanna thank everybody for coming. Thank you for the questions. These questions were great. Also makes it so Matt and I are not monologuing, you know? You c- you sly dog, you caught me monologuing.
But if you wanted to hear more about Everpure Data in general or what we're doing with OpenShift or maybe even see Matt, I don't know if he's coming to these, we're doing a traveling roadshow here. We got d- dates coming up in Dallas, Chicago, and Boston. Scan this QR code or take a look at it if you're interested. You, you know, we'll have all of our, not all
of our ex- experts, but experts from various things there. You can learn more, ask folks questions. Matt, I don't know, are you joining any of these? Are you gonna be on any of those? Um- I know you just got back from New York, so. Yeah.
I, I don't think I'll be at any of these, but definitely, like, the EBC's on the road or some of the boot camps. Okay. But, yeah. Yeah, it looks like Producer Laura did put the support link in, so thank you, Laura. You're so kind. And then she put for those that are like, "A QR code on a web screen doesn't do me any good," she did put the link in the chat.
Finally, also, if you haven't, make sure you join our Pure Community. It's, we got a community site, it's growing, where you can go in and ask questions. Like some of the stuff we've seen here today, maybe it's a configuration question or kind of some best practice stuff, you can talk with Matt or our PMs or even other customers, right? It's help- people helping other people.
You know, the help me help you meme here. So if you're not a member there, go check it out. Great resource. By my caveat I always say, so if you've joined these before, is just remember this is not a replacement for support. Any mission critical situation, obviously please leverage your support contract or your
support phone numbers for that, but go check it out. But also, thank you all for joining us. I hope you, enjoyed this. I hope you got something out of it. Hopefully it was somewhat entertaining and educational both at the same time.
You know, thank you to staying till the end of almost a full hour. Of course, my good friend, Matt, thank you for always being willing to- Absolutely. Any time jump on and do these with me. I really appreciate it. Yeah. But with that, I'll just say hope everybody
enjoys the rest of your day and the rest of your week, and we'll see you next time. Thanks, Matt, and thanks everybody. Thank you.
Jason Langer
Senior Technical Evangelist, Everpure
Matt Webb
Field Solutions Architect, Everpure
Red Hat OpenShift Virtualisation is an increasingly popular option for organisations migrating workloads to a new hypervisor. Rather than being an afterthought, storage is actually a critical element of any OpenShift Virtualisation deployment.
Join this webinar for a set of short demos of Everpure FlashArray™ with Red Hat OpenShift. We'll go from the ground up: connecting the Container Storage Interface (CSI) to storage, spinning up a virtual machine (VM) from a template, and protecting the VM with instant, array-based snapshots.
These demos will show how naturally FlashArray fits into an OpenShift environment.
- Get connected: See how to set up the CSI with the Portworx® operator and define both the StorageCluster and the StorageClass.
- Run and protect: We’ll demonstrate both VM provisioning in OpenShift Virtualisation plus how to create instant, space-efficient snapshots.
We Also Recommend...
Personalize for Me
My Updates
No updates at this time.