 Good morning. Good afternoon. Good evening and welcome to a special edition of red hat live streaming I am for short a host with the most of red hat live streaming. I'm joined by two Folks one from nut app one from red hat Andrew Sullivan red hat now. Are you doing yes, sir? I'm doing well the host with the most the producer with the Produceeist produceeist producer you've ever yeah, I don't know. I don't know where I was going with that Anyways, yeah, it's good to see you a little strange to see you on a Friday and not a night But happy to be here and this one is is special. I'm looking forward to this This is the first Partner live streams that I have been on so I'm excited. I'm really happy to be here As you said, we're joined by net apps Adam. Hey, so Adam if you don't mind introducing yourself Morning everybody. How's it going? My name is Adam. Hey, I'm a principal engineer for net app It's early in Colorado. It's eight o'clock. I am on my second cup of coffee, but it's not going out fast enough There's a sun over the mountains yet. It is. Yes. It's just it's the rays are coming through the window. So Kids are off to school. I'm ready. So I'm looking forward to this, too this is gonna be the first time I do a live stream with with a partner and Can't tell you how excited I am. I'm a little nervous. So let's see how this goes. It's all terrifying We are incredibly intimidating and the the audience is they they all brought their pitchforks and rocks to throw at us You know, it's it's only going live to the whole world. It's fine. That's it Yeah, so So I have been as some folks inside of red hat. No So one of my ancillary duties is to work with partners and net app happens to be one of the partners that I work with for a multitude of new reasons Not the least of which is I used to be a net app employee and I want to say that I am Really excited to be here and I know that we've all used that word a few times now because Net app has recently announced something that is incredibly interesting to me It's something that I remember talking about when I worked at net app three plus years ago so seeing all of this come to fruition is It's just it's it makes me happy. Um, so Adam, I don't want to delay any longer I want to to let you talk about What net app and rent hat are doing together specifically around this little thing that we call astra Sure, yeah, let's just jump right into it. So Um, let me start sharing my screen because I have got a couple slides that kind of talk through what it is that we're doing And I will bring up a right slide here, okay So what have we built we have built a Kubernetes workload management system and what that means Especially in regards to net app is that we are able to Handle multiple different Kubernetes clusters and workloads and our target our first target platform is open shift So that's where we support This this application running we're gonna open it up beyond that but coming out of the gate We're partnering with and and and supporting only open shift for this first release So it's been a great partnership so far open shift is a is a fantastic platform and We're excited to show what astra is and what astra can do So I brought this slide to kind of talk through what the ecosystem of astra is And we're gonna focus on the area where you can see the red hat logo So this is what I'll be demoing and playing with today But I want to talk about the entire astra ecosystem just so you get an idea of where net apps going with this thing Okay, so this is my drawing. This is not marketing material This is just what I put together to help convey this for as many people as I can we we have Pardon me. We have astra two different kind of flavors of astra We have the control service and the control center The control service is hosted in the cloud and anyone can sign up through astra.net app comm to get an account and log in to astra posted in the cloud and what it does is connect to Google cloud provider or or Azure and using your credentials So you give us your Google credentials or your Azure credentials and then we'll go query and find your Kubernetes clusters and then what workloads are we're going to do is we're going to go on those clusters. We're going to call those apps and From there on you can back up. You can restore you can clone you can hook up different storage back ends and For the most part just watch your apps watch what your workloads are doing So Where this becomes powerful is the ability to move those workloads from one cluster to another. So maybe you need a different environment a different A different geographical place you need to just create a backup for You know for safety sake and because you might be rolling out an upgrade and you want to Have a way to get back. So what astra does is it it Manages your application and data at the exact same point in time takes a snapshot or a backup of that and then Can move that around based on what you're hooked up to So that's the control service the control center is the exact same thing, but it's in your location It's in a customer on a customer's prem and like I said in the beginning We're only supporting OpenShift right now We definitely have plans to open that up and and we have verified it works on some other platforms But our support right now is for OpenShift versions 4.6 and above So I want to pause you there and I want to take a kind of a step back in a step up of So at the at the portfolio level at the the net app level what what problem are we trying to solve And I think to where does or how does net app in an OpenShift fit together and I'll answer that second one first So and I'm working off of the assumption here that we have some Maybe OpenShift folks who are new to net app that are watching the stream or the inverse right net app folks that are watching the stream for the first time and not familiar with OpenShift So OpenShift is Red Hat's Kubernetes distribution Right our goal is to provide a single platform OpenShift that can be deployed across many different locations So whether that's on-prem to you know physical servers bare metal servers to vSphere to red hat virtualization open stack whether it's to hyperscalers You know AWS Azure Google and a myriad of other places So we we our goal with OpenShift is to have a common Kubernetes platform with a common set of services across all of those And then have that value add of you know not just Kubernetes but all of the things that make OpenShift OpenShift so kind of And in the platform life life cycle management for things like installation updates all of the administrator and developer tools right the administrator console and developer console and code ready workspaces and you know all of that other stuff Chris I think you posted in the link there to go over to yeah yeah so to learn more about that there for you and Adam please correct me if I'm wrong tell me if I need to stick my foot in my mouth So from the NetApp side what we're talking about is providing as you can imagine if you're familiar with NetApp rate persistent storage into those containerized workloads running inside of OpenShift So that's that's only one component though because really that's not what Astra per se is doing that's what Trident does That's what NetApp has been really good at for a long time and Trident has brought into the Kubernetes world what about three three to five years ago and has been maturing so this is yet another evolution of our foray into cloud workloads Yeah yeah exactly so Trident was originally introduced several years ago as a way of hey I have some NetApp storage I want to be able to consume that I want I want to use that persistent storage with my containers and Kubernetes So Astra now takes that beyond just consumption right it's no longer hey create me a PVC that's x gigabytes of size with y storage class which happens to be serviced by Trident it's now going into kind of the data management application management room That's exactly right yeah so not not only can you enable your NetApp storage for your Kubernetes workloads or your apps that's that was already available but now we are going to manage both your app and your data and help you protect your system Yeah and it's something you know for people who watch the stream you know that I have a regular stream live stream ask an open shift admin we regularly this past week or well this week we didn't have a stream because of AnsibleFest but last week last week we literally got asked you know how do I do backup how do I protect you know the data inside of my cluster this is something that comes up all the time Yeah so I hope it is interesting to folks to see you know how NetApp addresses that when you're using the NetApp portfolio with open shift Yeah that's what that's what we're here to do that's what that's exactly what Astra is is to gather your open shift clusters together gather all the apps that are on them and give you an opportunity to manage them and then with the click of a button you can snapshot them or backup them and move them around So this that is our answer to exactly that question I'm looking forward to the moving around part that sounds exciting Yeah and here so let's see how the demo goes I appreciate you backing us up a little Andrew I kind of don't write in and I want to make sure that we've got the context fully set what else should we address before we dive a little deeper I think it's important to bring up that you know because for both companies you know hybrid cloud and you know the the multi cloud and hyperscalers and all of that stuff is really important and you know with Trident you're able to connect What's the new one that that not a FX or FR FSX FSX FSX So with Trident and the various NetApp services you know across those cloud providers even if you're using and and I hope I'm not speaking out of turn here even if you're using like a managed open shift you can still connect into those NetApp storage services If you're deploying you know user managed or what do we call it self managed now instances of open shift into the various clouds you can connect into those NetApp storage NetApp data services across all the various clouds and you can take advantage of things like well Astra So yeah I do I always like to remind people that you know especially we see more and more survey results coming out more and more you know as much as we all love to read CIO magazine and all of those other things you know about hybrid cloud multi cloud. It is a thing and it works across both portfolios both portfolios work together for that so Yeah exactly yeah we have a great relationship here and we're going to continue expanding that so we have lots of plans for how far we can take Astra Except when we accidentally kick you out of Slack you know Alright I'll quit distracting you Okay so I'm going to drive back down into where I was going before and I have a really rough script of what I what I want to do here but for the most part as was set up As our expectations were set as we going into this thing we're just going to kind of roll with it and see see how it goes So first what I want to do is show the the diagram that shows you know Astra is an application after control center is an application that sits on a red hat open shifts cluster and can manage other clusters so it can manage the cluster that's sitting on And you can add others and then when you add clusters to be managed we discover the applications that are there you can also custom define an app well we'll get into all that And then those apps either you've deployed them using whatever OpenShift tools you want or kube config or kube sorry kube cuddle Well however you've deployed your apps is however you want to it that doesn't matter we define we find your apps and as you deploy more or take them off we recognize that and then those apps hopefully are using on tap storage through Trident so that the pvs that are generated are so they're backed by Trident volumes by on tap volumes they are Trident pvs and they are then gathered and recognized together at the exact same time as whatever kubernetes resources make up that app so that's that's what we're going to do So let me recap just to make sure I'm understanding so astra console control center is effectively a control plane where we can connect one or more OpenShift clusters into that astra control center That's right and when you connect in those clusters it effectively does some sort of discovery of applications to include persistent volume claims as you would expect Yes So where an application can be defined as you know kind of any arbitrary thing that you would expect inside of a cluster and I'm because I've I've seen at least some of this before I know that you can define an application through like a label right any object and and this is something that's that's It's not just the pvcs and the pv behind it. It's, it includes things like the deployment definitions and secrets and config maps and all those other things kind of any kubernetes object that has the appropriate label or I think it will even work at the whole namespace level namespace level. Yeah, let's get into it. Let's just let's just show. Yeah, that's probably easiest rather than trying to try. Yeah, let's let me we can talk through and point at those things here with the with the mouse but let's get into So I do have one more slide I want to show but I want to kick off the installation first because it takes you know a few minutes so I'm going to start that now Make sure I have everything I need in place. Can you see the words on the screen or they might want to bump up the font. Yeah. Yeah, it's well I can see it in zoom here on on the stream. It's a little small. All right, let me that's That's probably how's that. There you go. All right, so let me clear my screen off and we'll list the contents of this directory again. Okay, so This is boring. This is just a few yamls that are Describe resources, custom resources. So let me let me just bring up a text editor and we'll take a look at those things. And over here and bump that up to So Much for the mouse go there we go. Okay, so this is our resource document for an astro control center. It's pretty simple. It's got you know custom fields for various things. What are we going to call it what version number are we going to deploy by the way I'm going to for this live stream I'm deploying off of Not the very tip of but our integration branch so this is actually stuff that's even beyond what we released back in August so Kind of a little preview, even though it's it's it's not all the way out yet. It's good enough for the demo I think We're going to tell it that we want it to be a specific URL so I have this set up in my host file my internal DNS routing so that I can route this URL directly to the IP address it's going to install on and some other some other junk here where are the images so when you when you get astro you get a tar ball of images and you need to take those images and load them into your registry. That's because we know that customers who are installing astro control center are putting them are bringing them on prem and usually have some kind of scanning. Requirements some kind of security requirements for images that are about to be launched on prem. We hope to eventually be able to host these images so that you can just click a button and pull them down. We have the capability now but Product direction is every customer is going to want to bring them on prem and install them so I've already done that for this demo but we have to point to that registry so that we can launch it into our internal area. Now are we are we working on an operator for all of this. We have an operator so that's the next thing we're going to show. Well I see that there's a CRD right so I know there's a controller at least but I don't know if there's you know most of us in the open shift side we think of operators we think of operator hub so being able to go into that you know very nice catalog interface and click and say you know deploy me an astro. Yes and actually we're making quite a bit of progress in getting our operator onto your hub so well we don't have it there yet. We have probably people watching right now who are working on getting that operator into your hub so that they can deploy it right into their open shift their cluster and then do the things that are necessary to launch the ACC using that operator. So the good news is this process that will show you might not have to actually do here in a in the not too distant future you'll be able to just go in with to operator hub and and deploy it. Exactly. Yes. So we have a CRD for this just describes Astro Control Center and this is a big long document of this is what the operator puts in so instead of going through all of that let's just launch it so I have these two. These I've called them apply because I want to apply these files. I'm going to apply the operator first make sure I'm on the right cluster here. Okay so I have two clusters open shift is 010 and 014 couldn't I have done I should have done sexier naming but that's that's what I had and we're going to launch Astro Control Center into 010. So let's first launch the the the operator which is something hopefully you would do using operator hub. And it's as easy as apply apply this file which is with operator hub we eventually do. Still get some warning about you know throttling from the from the. The Kubernetes API anyway so that's done so what did that do let's go over take a look. This I have these two tabs here this one is 010 and this second one is 014 so 010 just deployed this namespace net app it's too small. I was going to say I'm going to pause you for a second to get a little bigger. Hopefully it's a little bigger now you can click the hamburger up in the upper left to get rid of that side menu and some of that stuff. All right so it deployed this operator and there is you know nothing really in it other than one pod. It's got a pod in it and that pod has this this container which is just listening for should I deploy an an Astro or not and we haven't applied the CRD yet so it's not doing anything yet. So that's that. So it's back here. Let's clear the screen list out my stuff again and then the next thing I'll do is now I can apply the actual I call it men because it's a minified version of the ACC CRD and I'm going to tell it which namespace I want it to and oh I have to create the name space. OC create namespace net app ACC ACC. So first thing to do get that namespace created get the security context created for that and then let's apply this the CRD and make sure that it's going to go into the net app ACC namespace so ready go. And all of this is if you've used you know CRD is before this is an operators this is pretty standard right of the first thing that we deployed was the operator which is really the controller behind the custom resource definition. And for lack of a better term the automation that implements that CRD instance. So now what you just did was say hey go create a new instance of the application which triggers the operator that controller automation to then go and deploy whatever objects make up and ask for control center instance yeah go do stuff. Okay, so that's what it's doing the operator. If I were to watch the logs here to two controllers the manager is the one doing all the work here is doing lots of things. This log stream is just going to flow because it's installing everything a better way to look at it is to switch to the net app ACC namespace and watch pods. We're not going to watch this the entire time because I do want to show the microservices architecture diagram, but what is happening is the operator is launching these pods and so it starts with a helm. A helm pod because all of our charts are our home charts everything is going to launch all these microservices are launch using helm. So we first we get all of our helm charts just to be serveable into the namespace, and then we start launching the the framework the the bottom layer of the framework so influx Loki Nats console. Let's take a look at the microservices architecture so that you can see, you know, the pictures of these things that are launching right now. It's funny to me how much the Marvel Universe seems to be affecting things like we've got Thanos for the right metrics aggregator we've got Loki we've got. You know what, I'll give you a little preview of my substitutes here of my demo but what one of the things I was going to do is put images of Marvel characters into a blog and then destroy them. So, I can't get any bigger I'm sharing my man, maybe I can do it here. There we go. I can sort of do it here. Okay, I will zoom in on this. As I talk about things. There are two large boxes here the outlined in this dark gray and the largest one is ACC. I'll drive into it and the smaller one is a managed cluster so what services are we going to deploy into the cluster that hosts ACC, or the managed cluster that we just we we chose to manage. So this is a list of both of those environments put together. And let's just start over here on the left hand side of ACC so I'm calling this the 21 q2 Astrid control services diagram because this is what we released in in August in our q2. So over here on the on the left hand side we launched persistence layer vault MongoDB influx Loki. Those are where we store you know that those are the things that are staple. And then we have platform, a core platform of services so the ability to have features turned on and off the feature flags and settings. Credential activity so credential, not acuity credential service which is interacting with vault which is where we store and encrypt usernames and passwords and keep configs and things like that. We have an activity microservice which is just keeping track of things that are happening in ACC. We have some metrics. This gets kind of complicated but for the most part all of our monitored, sorry, managed clusters and apps are sending metrics and logs into our system and we're gathering that here and keeping it for seven days. We are also sending it to our hosted service cloud insights that's down here and let me actually this makes a little bit more sense. We have cloud insights ace up and cloud central which are involved in our ecosystem so we're constantly sending support bundles metrics and logs from your instance of Astrid control center up into our hosted services and we keep those for at least 30 days maybe more depending on how what kind of level of service you've paid for we keep seven days of them on prem, but if you're hooked up to and can send things out to the Internet, you'll have a lot more telemetry. So this is those services that are handling all of that stuff. For our user management our identity management we have local accounts as of right now. So we don't we don't integrate with anyone's OAuth or SSO yet, but you can have local accounts in Astrid control center and use those user names passwords to log into it. We did we disconnected that from cloud central because we need to be able to support air gap sites so our first release was local authentication I can see you have a question. No, I was thinking back to the auto support stuff of all of that data, all makes a lot of sense and it really helps the cloud insights out of things. Cloud insights is not something I'm terrible familiar with I mostly see it during keynotes and stuff like that but the amount of information you can get an intelligence you can get out of that is really impressive. But no the authentication stuff it makes sense, you know supporting disconnected installs which is, you know, of course, we have quite a few you know disconnected OpenShift installs as you would expect. So, no, all of that makes sense it doesn't. Yeah, we definitely are growing into more capabilities, but right out of the gate we needed to make sure that we support air gap sites and local installation. People who are concerned with justice local situation so our authentication and account management while growing is still simple and you have your own accounts you log in. There's some support services that handle gathering the buck the bundles and sending them up to ASAP. There's some licensing services that handle making sure your license is valid and what features are enabled because of that. Then we get into the real you know the meat of what Astrid does and that's app data management so we have Nautilus is basically our core service that's the one that is once you bring a certain cluster on to be managed. Nautilus is the thing that hooks up the watches. It talks to the Kubernetes API of those clusters. And that's where all the discovery happens. The reason it's it's surrounded by what's called composite compute or cloud extension is because we are going to a variety of different clouds we're either going to GCP or AKS we're going to Red Hat we're going to OpenShift we're going to local installations. We've tested out Rancher so we have a various different clouds or Kubernetes worlds that we need to talk to and so we have a abstraction layer for that so the Nautilus just does its job but it can talk to any flavor of Kubernetes. We then have the same thing for volumes so we go and find your volume information and then Nautilus uses those to gather data and application stuff and then it maintains it inside Nautilus. And then we have buckets I'll explain buckets here in a minute and storage provider or storage back end. So who's the back end where what data service is running the volumes with what not data what what storage services running the volumes that are behind everything. So we'll see all that work. Everything else is is involved with talking to Trident or the the operator itself. How does the operator work to install stuff. On a managed cluster or some pretty simple things so Telegraph and Fluent Bit are the main pieces of code that we install and they send data like I said to cloud insights or to the host or and or to the host. In order to get those on and running we have an we have an operator that turns them on and it configures them to send data to the right places and use the right credentials. And then we also have Trident so Trident has to be present on any managed cluster. This is a reconciler essentially for Trident so make sure that Trident is at its latest version and is configured to talk to these the storage providers that we support and right now it's just on tap we're going to be coming out with our Astrid data store support next year to. Alright so I think that I've killed plenty of time and our installation should be done. It's just waiting on the internet right to pull down all those all those container images. It has them all know it had them all so what this is there's a long list of services that are running and you saw the you know the diagram that represents them. So this is this is all of them I should scroll a little slower. What I look for is is traffic traffic is the last thing that we install is the you know the ingress so after everything is up and running then we open up the ingress and we're ready to go. So let's go back to our console and see what's going on so if I get ACC. That is the short code for master patrol center yep use this use the right namespace so there is one cool that's that's nice let's see in order to learn. If it's deployed yet let's pull out the gamble for it and we can look in the status and see that it is currently deployed so in the post install that which is after we deploy it we run a couple post install commands that handle certificate management because we're going to be behind a self signed cert until you give us a cert. Let's let's make sure that's all done and ready so we're done we're installed and the. Remember the URL which that's number one this is the URL URL I installed it on is that a hat dot demo but after that a bad hat dot demo dot com. So let me just try to make sure one more thing is up and running before I attempt to visit that URL so I want to make sure that the the traffic service. Is that URL is that managed through like an open shift routes or is that some other config there know so that we do have instruction for how to change that to an open shift route but because we are going into. Other different flavors of Kubernetes to I know we're supporting open shift but we are putting our own internal load balancer on or we're requiring a load balancer to be present on the host cluster we're going to use that and. Direct traffic after it comes into the cluster. So we brought all of that ingress lower than a open shift route and then we have a knowledge based article that allows you to disconnect that and bring it back up to an open shift route. For for this demo at least while we have time I'm going to keep it the way it was if you'd like to show it transition we could do that. Nope that makes sense. I think the. What I'm interpreting is that essentially it's creates a service with a node port and then that load balancer just points to the node port. Yeah so it creates a service. Yes, exactly so that we we've exposed an external IP. This external IP is routed in on my machine I've routed the URL DNS routed that URL over to this IP address internal DNS routing would be something that a an admin would do. Or you would have the open shift routing it play here. So let me make sure that my. My hosts are aiming at so this is this is the traffic load balancer service and it's currently picked up this IP address and I actually don't think that's the right one so let me take a look at my post file. Oh, I'm still early. So I wanted it to be on 27, and it showed up on 28. So this is the beginning of one bit off. All right. Let's go take a look at our so what we what we use is metal lb load balancer here. Let's go take a look at that system. My hamburger back so you can see big map and 34 and I wanted it when I say I want to go 27 man wonder what would happen if I tried to just pointed at 28. Yeah I'm curious. I think 28 is actually used by a different machine on our network. Oh, okay. That's a good reason to be concerned. The worst that happens. I'm doing this demo and I just crashed a whole lab. I'm sorry. All right. I've done that before. They're done that. Chris, do you remember when I accidentally powered off my whole lab. Yes, brilliant. Oh, it's serving. Wow. Okay. What is it serving? Okay. Wow. Holy cow. There's not some machine that's going to know that part of the labs working at least now. Yeah. Okay. So the part that is important here is I deployed this that remember this is our CRD here. I deployed it with an email of admin.astra.net app.io. So that's the log in. Let me make this bigger. Thank you. Sorry. And the password, the first password is the UID. Although you have to prepend it with. I don't think I can show it. Maybe do it in the text editor here. So eight capital ACC dash and then the UID. So that's the first password that you get. And this is in the documents. So I'll copy that text and put it in here and hit log in. And the first thing that does is say, all right, change, change your password. So I'm going to change it to something that I am, you know, muscle memory can type here. Oops. I'm sure it's not password blur. It's password one, two, three. All right. We're logging in. Wow. Sweet. It's up and running. Zoom in a little bit, please. Yep. If you don't mind. Yeah, no problem. Is that enough? Yeah. It looks good. Yeah. I couldn't read the, the managed Kubernetes Azure applications. Okay. Welcome to live stream admin Astra. So how did it know that it got that off of the CRD too. So if I were to switch back and, you know, here, I told it its name, the account name is live stream. And my first name is admin. So it took all of that stuff off the CRD and now it's, it's deployed. Oh, but big red banner. Oh no. Hey, so what happened is it's been running for a little bit. And some of the first things it does is checks on some stuff and there's no license. So it's not going to let me do anything. You can see that the add button to add a cluster is unavailable because there's no license. So I'll head right into my account and my license tab. And that, well, so it also hit put a notification. So this is that, this is the activity service saying, Hey, not only am I going to, is the you are going to play and display the display a big red banner, but I'm also going to, you know, make sure there's a persistent notification here that says, whatever it is that needs to say. So right now it's just no license. Okay. Got it. All right. I do have a license ready for this demo right here. And I can apply it. And so now I'm up, I can, I can host up to 4,800 CPU units. That means I can manage clusters and however many I bring in up until I've hit 4,800 CPU units. So that's how we do our licensing. Okay. All right. So back to the dashboard and now you can see, well, here's a note about my license. Yes. I'm using any valid license and I could upgrade it. After November 18th. I'm just surprised to see a storage product that isn't licensed by, you know, gigabytes capacity. Wonder if there's any product managers watching this. Why they chose CPU? Okay. So we need to back up our application. So you need at least one object store buckets. So this is where I said I would talk about buckets. So what we do is we take your data and we take the, the resource documents that represent your app. And we, we compressed it all down into a self-contained tar. And then we put that in a bucket and we can put it, we can do it in any bucket. So I have a bucket ready to go here, but when you add buckets, I did that kind of fast. This is a list of, of all the buckets that are available. If you add a bucket, you have a choice for which one do you want? A net app on tap S3. Obviously we're selling our own products here or a storage grid S3 or a generic S3. And so every S3 works. I've prepped an on tap S3 for this. So I'm going to switch over to my on tap system. I'm going to create a bucket and then I'm going to use that bucket. So this is something that, that I appreciate. I've, I've been a storage administrator of various types for the last 20 years. And I constantly remind people snapshots are not backups. So having this very distinct, like, yes, you have to create a bucket. And when you do a backup, it's going to take that data and it's going to put it into this bucket. Like it's, it's separating the two things apart. Snapshots are a point in time recovery. A backup is a separate copy of that data that can be restored. If the primary fully goes away. Absolutely. That's exactly it. So we do support snapshots, snapshots, but you can only recover on the same cluster. But if you want to move an app to a different cluster, we're going to need a backup because we're going to have to go to the bucket and pull it out. And move it over to that next place. So let's add a new bucket. I'm going to call this red hat. And for some reason, it has to be at least 95 gigabytes. So let's put that in there. So that will be done very soon. And in the meantime, let's go back here at the bucket name because I copied and pasted that, put that right there. So I have to go back to my other. This is tiny too. So I have a Confluence page that has what I need for the rest of the bucket adding stuff. So usually you have some information about, I mean, if you know your on tap S3 system, you're going to know what your endpoint is and what your access ID and secret keys are. Yeah, so I keep that standard S3 stuff for connecting it together. Yeah, I mean we have for AWS to like if you, here's our AWS bucket if you wanted to use that one should probably not like advertise secrets to our bucket, it's actually on AWS. But there we go. Let's go back to here. So the IP address. The access key. Oops. And then the secret access key. And that's generally all I need so this will, you have to put a name in here. This is my bucket, whatever. It is a dead app on tap S3. This is the bucket name. All right, all good. I'm just going to add that and it goes into a pending state for just a moment and it's just going to verify there's a good bucket there and it can use that. All right, so that was the dashboard. So it, as you saw it gave me a few prompts of things to do in order to set myself up right so my prompts are now done I've got a license I've got a bucket. Let's get started adding a cluster. So that's the first thing to do. You can provide us with a cube config, essentially, because we're, we're not talking, this is Astro control center so we all the only thing we need is we're on prem, we just need a cube config to your cluster so we can manage you. If we were in Astro control service and we were talking to a cloud provider, we would ask for your credentials for Google for GCP or Azure, but this is a demo of ACC so give me a cube config. I have one for I'm going to bring in 010. That's the one that I installed it on. I installed ACC on. So let's manage that cluster and then let's also manage one other cluster. So the first thing it does is it says, let's pick what your default storage provider is going to be so what it's doing right now is it's querying using that cube config to query the cluster. And it's loading the storage classes. So I only have one on there. It's an on tap gold using the trident storage provider and it's eligible so that's good enough. So it says confirm all of those details. And I assume in the docs it shows how to like how to generate a service account or a custom user to use for connecting all of that and generating the config and everything. So I'm going to add one more. Let's let's click that link here in a second. So this is going to it's in a pending state right now because Nautilus is querying that cluster and sucking down all the information about it. So we'll let that ride while we go. Does it deploy anything into the cluster. It does it deploys a monitoring namespace and then it deploys those telegraph influence agents I was talking about so that we can send logs and metrics back home. In this case it's sending it to itself because it's I'm not I'm managing the same cluster I'm on but now I'm about to add yet another cluster. So what what what would happen if trident wasn't installed to that cluster. It wouldn't it wouldn't let you go any further it would say here's the source classes you have but nothing is eligible to be managed by Astra so it would give you instructions like it's doing here well so first you have adding clusters which opens our docs. That's for adding a cluster. And talks about pre rex. That's really small isn't it. You should ensure that pre rex are met before you add a cluster and then it talks to a bunch of stuff you know what what export policies for on tap and check the trident version. So I won't go through all that but yes we open up the documents and say here's what you need, and you're asking about the service account so that's these instructions here. Where's my service account stuff here, create an admin role cube config. And so then it gives you instructions on how to do that. So I'm just going to put the doc the, the cube config that represents 014. And we're going to add that one, a little move in a little faster now. See I just, I'm now I just need to figure out how to put it in RFP like, can I, can I add a cluster to be managed and have it deploy trident and then tell it to automatically configure trident for the storage systems that it. Anyways, automate the world man. Glue it all together with one command. So I have these two clusters. Last thing last, we checked my my bucket was still pending so okay so bucket is now available. The clusters are coming in. So, look at this I've got some new notifications. A storage back end was added so when I added the cluster the oh one oh cluster it determines that there is a there's a trident storage class and it's connected to a storage back in. So we went into trident and we grabbed information about that back in and now I'm going to display the discovered back in so I have this one here this is the on tap one. I think that we're getting ready to do ADS or ask for data store to so that cluster has ADS added to it, but I'm not going to do that here in the demo because it's it's it's still early in its development but because I'm not doing GA bits we're doing development sorry development bits I do have it shown here, but let's manage the the on tap cluster so I you have to put in your credentials for that on tap cluster. And then import it. It moved then so I was successfully managed go to back ends to manage it I'm in back ends but I'm on the discovered tab so now there's only one in discovered state if I switch to managed I've got this guy here who was my on tap on tap 97 back end and it's available so I can actually go look at it. It's still discovering more information. It'll show me the capacity. And here's all the PBCs that are on it and what what cluster they are hooked up to. There's a lot of stuff going on in here so So what I'm noticing is you haven't had to do anything extra to connect astra to the storage system. Basically it's using trident to get all of that information. So the administrators already configured trident astra is just taking advantage of that. That's exactly right. Yeah, we don't need to tell us your credentials because we're not going to pull that out of trident. But once we have your credentials, we'll go ahead and watch that for you so you can take a look at what's going on. I'll come back and see this if we have time so you can see some of the graphs that get drawn about it. But for now, let's switch to the applications view. One more time. The clusters that I'm managing are 010 and 014. They are both 1.2 20 OpenShift version. I think that's 4.7. Yep. Okay. So then I switched to the applications view and I have a discovered tab and it is discovered it's discovered 46 things. So it's not displaying all of that. Here's what I want to do. I have a WordPress website. This is for the demo. I pre-deployed just the very vanilla WordPress website that I could using Helm onto my 014 cluster and it is not managed yet. So let's manage it so that we can get into it and start considering it a workload I care about. These other workloads are... Well, here's the operator. Right now we're not managing ourself. And we're not managing any OpenShift namespaces. Sorry, go ahead. By default, these applications are namespaces. Like it says, I see 1 to 6 entries, but discovered is 45. Okay. I was thinking it'll just grab all of the namespaces and turn those into apps, but which is sort of true. Yeah. We're also hiding a lot of stuff, a lot of system level namespaces. So let's just... What's in here? So if I open up NetApp ACC, all of these, I told you they're Helm repo, they're Helm apps. So they're in the NetApp ACC namespace, but they're a different Helm label. And so it gives you an opportunity to manage individual things like that. The top level is namespace. You can add a label inside a namespace or outside a namespace, and that would be considered an app. So it tries to predict some things for you, but you could also define your own. You could say, which cluster? Let's pick this one. Let's pick any namespace. I don't think I have anything in default. I don't know what's in there. And then, or you could select a label or type a label. So I don't want to manage anything in CubeSystem. Please don't. We discourage that on this channel. Yeah. So here, I picked the NetApp ACC namespace and I could type out a label and it would narrow this down to deployments that have labels that match that. So right now, everything is selected and or is not. Sorry. These are selected. These are unselected. Anyway, I can start defining custom namespace. Sorry, custom applications based on a label and that's important. It's a single label at this point. We are going to refine that a little further so that you could make an app out of just about anything that crosses namespace. That's coming up soon too. But for now, this is how to define a custom app and this would open the help docs. If you wanted to read more about that, I'm not going to do it, but just wanted to show it's available. All right, so I'm managing WordPress. So let's just narrow my list down to what is managed. I've got a WordPress site. This WordPress is posted on 014. So let's switch over to 014. Move the shirt down the hamburger and let's go into the bottom. There is my WordPress namespace. What's service? My WordPress service. This is what I'm looking for. This IP address is where WordPress is being served. So let's just open up a new browser and put that IP address in and some plain old WordPress website. It's been a while since I installed WordPress. Glad to see it looks exactly the same. So let's go to whatever that hello world post is. Let's edit it. Yeah, WordPress got so fancy. I don't care. But let's add something. Let's insert something after. Always paste those AWS credentials back in. Yeah, let's put the AWS as three bucket credentials in there. No, let's do that's dangerous. Iron man. Iron man images. There we go. Copy that image. Go back. Nice zoom things in the way. Oh yeah, the little share screen box. There we go. Update. Put a picture of Iron Man in our blog. Post is updated. So let's go back and take a look at it. Oh, I have to open. So I have to go into the post. There it is. All right. All right, there's my thing. Okay, so let's go back to Astra and let's back this guy up. So if I go into, first let's inspect, what do I know about this thing? It's healthy. It's unprotected. So no backups or scheduled policy yet. It's running on 014. These are the images that it found about it. So this is where things get kind of cool. It knows every Kubernetes resource that makes up that app. So these are cluster roles. Some of this is OpenShift generated. A whole ton of cluster. 110 things. Cluster role bindings. Thank you. OpenShift. Here's some secrets. And eventually I'll get to the. There's a stateful set. There's the MariaDB or MySQL. There's some services that were created. There's got to be. The WordPress service. Somewhere there's a pod. There we go. Here's some pods. So anyway, Astra knows all of this stuff about your application. And when we take a backup, it's going to go export the resource documents for every single one of these things. And it's going to go pull all the data out of the volumes. There are two volumes. One's an 8 gig and one's a 10 gig for MariaDB and for WordPress. WordPress is storing the files that make up WordPress. And MariaDB is obviously MySQL. So it's going to get all that junk. Press it down. It's going to put it in a bucket. So let's do that. Back up yourself. So. Well, that's it. Which bucket do I want to use? I only have one bucket. It's the default bucket. It's that one I created earlier. And I could name it something if I want, but let's just go ahead and call whatever NetApp or sorry, whatever Astra wants to call it. I think it's important to point out just real quick that because it automatically selects kind of all of those objects. If you're using a route to access this application. That includes the certificate that it's using. So in amongst all of those secrets and other objects there is things like the automatically generated certificates that certificate manager operator creates for those services and all of that other stuff. So it's not just, you know, the deployment, the PVC, you know, the config map that you created when you or Helm created when you deployed the application. It's all of the stuff that OpenShift also creates to go along with those applications, which I think is really important, right? If, you know, you restore back your application in a different cluster and it has a completely different certificate that could break, you know, applications. So yeah. Yeah. There are things to be aware of like, like that. The service as you saw has is using an external load balancer IP of an IP that's assigned to this machine. So when I'm going to do that here in the demo, when I move this thing to another cluster, let's make sure that the IP of the service changed when it stood back up again. All right. So moving on. What happened there? I feel like my data protection screen should have more on it. Maybe refresh the page. That tab isn't loading. Yeah. Sub tab. Boy. This data protection screen. Again, I'm running off the development branch. That's strange. It should list the backup that's being created. And we have last night it did. So I don't know what it's doing here. This is the activity overview. Very strange. Hold on a moment. Let's switch over. Let's switch back to the cluster so I can see if it's still doing a backup. So if I switch to the projects. Close the hamburger menu scrolling to the very bottom. So. When we do a backup, what we create a new namespace in that cluster and we hook up rustic, which is what creates all the backup files or helps us compress everything and put it into a different, put it into the bucket, create all the stuff, put it into the bucket. That created a bucket called WordPress backup. Sorry, no, not a bucket, a namespace. So because that namespace is gone, I know the backup is done. But I am. That's what I was looking for here. You could see the backup being created by now by seeing a new namespace show up for a short amount of time and then go away. So it's done because we talked through that. I'm at that amount of time, but I'm concerned that I'm not seeing it. Well, let's do something with this thing. So if I wanted to move this to cluster 10. Here when I say it says yes. So here, this is my backup. It's done. So I'm in a wizard to clone an app from an existing backup. It shows me snapshots or backups. I did create a backup. The UI for the inside of that app wasn't showing it, but this wizard is showing it. It says, I have this backup already created, which was done a few minutes ago. So essentially there's just some glitch happening with the other section. Yeah. Yeah. Let's, I mean, let me see if I can get. That's never happened before. Everything was going so well. All right. I want to move it to the other clusters. So I'm cloning this app. Before I go any further, I could restore this app somewhere else. I could restore and clone are really the same thing. We use restore because the intent is you're going to restore it right on top of itself. We're on the same cluster and you can restore from a snapshot. You can do it. You can dump it right on top of the same cluster. But clone the nomenclature, the semantics are we're going to move it. We're going to migrate it. We're going to change it's location. So I'm, even though you can do that with restore clones word means to me, move it. So we're still working out some shakes here. So we're shaking through the, the UI here, the UX, what really should we call this? Anyway, I'm going to call it WordPress. Just without anything fancy. And I'm going to clone it from an existing backup that I already took. I'm going to put it on cluster. Oh, one Oh, because it currently only exists. And here's some reminders on 014 and what its name is. And a link to the documents. So let's review that and get it going. All right. So what happened? Well, it automatically has a new managed cluster. I'm sorry, cluster, a new managed app. So WordPress showed up and is in a discovering state on the Oh, one Oh cluster. So it's. There's things going on under the hood. Let's go see what they are. On the Oh, one Oh cluster. It's going to the bottom. Here, here, there's a new WordPress. Name space. On that cluster. And there's nothing going on in it yet. Close the hamburger menu. And you can start to see some activity. So what it's doing is it's. Loading all of the volume information into the new volumes. So that we provisioned volumes. We're loading the data on, we've attached to those volumes. We're loading data onto those volumes. And there's some jobs running in the, in the background. These two pods are there. They are the R means restore. They're restoring these things into the right volumes. And then one, once they're done, they both will finish. They'll go away. And then the resources will be created. And by resources as the pods, the secrets, all that stuff. It's going to show up. So it's a little bit of time here. So just to be clear, we're not, we're not doing, or we are creating a new volume. And then we're loading the data into that volume. Yes. Okay. And then that's effectively what those are, our dash or our hyphen pods are doing. Yeah. So these are pods. Created the volume attached to it. We're loading the data into it. They're going to disappear. And then the, and then Astra will create the other pods that are actually the WordPress, Maria DB, and the WordPress itself. So you see that happening right now. And out of curiosity, does it, does it back up like container images or are those, we expect those to be available externally? Yes. Good question. No, it's going to be available externally. Okay. Just back up the registry. That's all with it. There's a lot of stuff that could be in there. So we expect, because what's going to happen, you, you installed this in your environment and you pointed to an image path and it was able to come up before the exact same image path is in these pods. And we're expecting the registry to have those images. All right. So things are all getting going here. So Maria DB is now up and running. It's ready. And that WordPress will come up and running. Let me bring the hamburger menu back up because I want to take a look at the holes are scrolling fast. So it's doing stuff. It started the container. Yep. I see the config maps are back. The secrets are back. Yep. So it's, I was reminiscing because our last stream was on API applications about way back when stateful sets were called pets sets. Yeah. I didn't even know that. Really? Yeah. Back in the like 1.4 and earlier 1.5, something like that. We've come a long way. Haven't we? What does pet set mean? Cause the, the thought process was a pod that has persistence is more akin to a pet than a, you know, chicken, cattle, bacteria, whatever analogy you want to use. Yeah. So it was, it was a heavy handed Andrew's opinion, heavy handed way of, of saying that, you know, this one is, is special. Stateful sets are not. It is life. All right. So, um, while you were talking, I was bringing up the WordPress service and we wanted to make sure that the IP address. So this, remember my last blog was on 37. Now, because this WordPress service was a, is a load balancer, it looks for, um, some internal load balancer to give it an IP address. And so when it came up on the other cluster, the load balancer on that cluster gave it an IP address, a new IP address, which long tab of 34. So. So it's the reason that if I tried to go to 34. To 4034. My blog should come up. Uh-oh. Here we go with our fun. So what's going on here? I wonder if WordPress is all the way up yet. Good point. Because it does take a little bit of time. Yeah. Where are they? Yeah. All right. Well, so something's going on with my 34. Oh. Hmm. All right. Let's troubleshoot that. But before we troubleshoot that. I'm looking at, sorry. I'm looking at the old one. This is 37. I shouldn't have, shouldn't have switched to that screen. Still waiting for 34 to come up. I'm just going to shut that off. So it's not distracting. And. I'll figure that out in here in a minute. But what I do want to show is that this WordPress app. That's on. Oh. She's actually really should have named that something. So because the only, the only difference here is this four and this zero. Anyway, you can see it's a little newer. It's discovered a little bit more recently. It's not protected because we've taken no backups of it. It's on the cluster. I moved it to. So let's go take a look. This data protection screen still isn't coming up. So I'm a little bummed about that, but let's go. If you will look at all the resources, there are 122 entries. Of resources here. That it loaded it created for us. On the open shift cluster, it moved it to. The storage has two pvcs. They are on tap gold. Eight gigs and 10 gigs. So it basically it cloned the whole thing. It just moved everything over and now here it is. So Adam. Yeah. Is there a way to do. Effectively, you know, manage this application protection application, you know, backup process through an API. Oh, yeah. Yeah. Okay. You're distracting me a little bit, but this is really fun. Oh, by the way, I went to my account. I'm using 48 CPU units because it knows those two clusters have. The each have 24 CPUs. So if you go to your profile in this upper right hand corner, there's an API access link. You click that. It's got the, this is the API documentation, which is a swagger doc. And that loads our entire API for you to play with. You can just click it and start trying it out right now, but you're not authorized. So in order to authorize the swagger to work, you would generate a token. It wants to call it tan pasta. That's weird or broken rhubarb, whatever. I'm going to copy this and close it and it'll tell me I've got this API token. It'll never show me that again. So I copied it into my clipboard and then I can go here and click authorize and paste that in. And now I can use my swagger doc to discover the API. And obviously you can, you can. Yeah. And what I'm curious about here is essentially as, as an app admin as an app team, you know, can I avoid the GUI entirely either for open shift or Astra? And what you're saying is, yes, absolutely. You know, you can deploy an application. You can protect an application. You can restore an application and you can do it all from, you know, all programmatically using whatever tools you're already using today. Yeah. Absolutely. That's, that's, that's the point. So I'm going to call for all the apps. What, what apps does Astra know about in this, in this account account is just the tenant. You only have one in ACC. And here it says it's showing me everything that it thinks is an app. Remember, I haven't custom defined anything. And there's IDs. If I wanted to go learn more about each one, see if it was anything managed going really fast, probably should have. This is, there's a pun. You saw how many things it thought was an app. No, I, I think we get, get the premise. I just wanted to check and make sure that, or check and see if it's possible, you know, to do all of that. Again, I think a lot of, especially application teams, unless they have to don't want to use a GUI. So it's great to see that, that is an option. Yeah. Absolutely. And we have a, we have a whole document on our API. And in addition to the swagger docs, we have regular docs that are published to describe the whole thing. What was I doing? Looking at apps. This one's not protected. Why is. What's going on with my 34. Could be going on. Are the, are the first three octets right in that IP address? Yeah. So yeah. Yeah. Um, Hmm. All right. I need to take a quick bio break. Yeah, we can take a break. If you need to. Yeah, no problem. I'm going to put, um, I don't know if you guys take a quick, I'll be back real soon. I'll put Astor back up. And, uh, Yeah. Sorry. Right back. I mean, the routing is, which it looks like it's set up. That should work. Hey, let's. Yeah. Let's do a rodeo style. Let's figure out if that works. Open actually WordPress might object depending on the WordPress deployment, like, oh no, you're coming from the wrong route. I'm going to redirect you around wrong URL, but. Yeah. Well, there's no URL associated with it. Is there? Well, there's gotta be some kind of. So this is the one. This is the first one that's running on this. Yeah. Well, so something inside of WordPress is like. I would think is providing the URL. Oh, it thinks it's here. I think it's 37. This is the, this is the one we took a backup of. So I don't. Well, it's, I mean, what's creating a route only takes a second. So what's the worst that happens? Let's, let's, let's see what happens here. All right. So create a route on 14. No, 14 was the, where we started. We moved it to 10. And we want to be in the WordPress project. So no routes found. All right. You guys talk me through it. So just hit the create route button. And then call it whatever you want. My route. Yes. Yeah. No, you'll actually have to fill it in. Oh, just call it WordPress. Yeah. Host name you can ignore. Okay. Half should be fine. Service will be the WordPress service. Like the port. And hit create. And then click the location link there. Boom. Hey. Amazing. And then it should have, yep. So. There's that picture of Iron Man that I put in before it took the backup. There you go. Nice. Thank you, Andrew. Yeah. It's all magic. Oh yeah. Okay. So that's. Astra has cloned an app from one to another. And I. Taking a look here. Still don't know why my data protection screen isn't coming up, but I can, I could, I could take a backup of it now. I can move it again. I can do a lot of stuff, but let's kind of kind of take a tour of other parts of Astra. See what else is available. So remember. I showed that we have these. The back, the storage back in. This is the on tap that was hooked up because of trying it. And now I should have a little bit more information about it. So I know what capacity it has. I know what capacity each and every volume is utilizing. So 1.65% of this Maria DB. Volume is being used. That's kind of interesting information. Um, this activity is, is asked. Just that we asked. And there usually is one other graph that's not showing right now. Um, that shows, um, Utilization rates. I'm not sure why that's not coming up, but. It's not. Other stuff that we have here. Um, in the account screen. Um, you can create your users. This is where you create users, by the way. So this is the one that was created when I deployed. Um, it's. Just as simple as this screen right here. First name, last name, email address, temporary password, because the user will have to change it. First thing they log in. And what role. So we have four roles set up right here. So we have four roles set up right here. Um, We have to change it for sending a log in and what role. So we have four roles set up right now in Astro. The owner can, is the owner of the entire thing. Let me pause you for a second, Adam. Oh no. Okay. I was going to. I hit something. It was a mistake. Sorry. Yeah. No worries. I was going to point out like, wait, my stream just disappeared. Now it's back now. So there you are. Sorry. They could still hear us. Okay. So we have four roles. Um, owner and admin are, are, are similar. Um, when it comes to Astro control center, you can create users and, um, and can control their access. A member is a user and a member, uh, is assigned to, um, an account in this case in Astro control center, we only have one account, but that member can then, um, create backups and restore apps and things like that. Um, we just got logged out. Huh. Somebody found your IP. Uh, Astro. And then I believe. That's the password I said too. Yeah. All right. Where was I? I was creating a user. Anyway, uh, or viewer of your is just someone who can, you know, navigate around in here, but they can't create backups or restore apps or anything like that. Credentials is just a display of things we know about. Uh, our world here. So, um, we have a username and password to access the on tap back in. Remember, I typed that in. So it's stored it. Um, we have the cube configs for the 010 and the 014 clusters. And you can do some stuff with those. Like some of them, um, you can't remove this credential unless you unmanage the cluster. But this one. You could remove. I don't know why you'd want to. It's a, it's just a username and password that's used for the storage back in, but we, we intend to expand the capabilities here. So anything that is secure, it's the, the data is actually stored in vaults and it's encrypted, but here we show you a list of those things so that you can see what is, what is in play. Notifications is anything that has been going on here. And those are also available in this, um, little pop up right here and mark them as red, mark them as red in this notifications area. Um, this is the license where to take a look at this. And here's, here's a real interesting one. So connections that we're going to be adding more UI cards to this as, as more functionality comes, but here's what's available now. A proxy. So remember we said we're going to ship, um, ASAP bundles and metrics and logs up to cloud insights. Well, if you have a proxy that we have to go through to exit your, your intranet, you can connect that in right here, you know, for the server name report. And then if you need authentication to do that. So that telemetry works. This is cloud insights. If you want to connect to cloud insights so, so that we're sending the data there, you would go to that tenant URL. Whenever you, you have a cloud insights account, you have your own personal URL and you would put that in here and you would have gone to there previously and generated yourself an API token, one that's capable of reading. And if it's the same one is also capable of writing, you could, you would put that in here, the same one in here, or you could generate two and then you'll hit connect. And then we'll be sending data up to cloud insights. Um, Fluent D. If you'd like us to ship your logs to a fluid D instance in your internal area, then we'll do that. So we already have all of our logs coming in to our own area and we're going to be sending stuff to cloud insights and to ASAP, but most Kubernetes. Systems have a log management area. So you're probably going to put it in elastic search or, or log stash or something like that. So this is how we feed our logs over to that. So if you're internally wanting to manage your stuff as opposed to sending it to cloud insights or both, this is how you turn those things on. Yeah. And that's similar to what we do with open shift, right? With the log forwarding API and all that other stuff. These are going to be more astra concerning logs. Like right now I think we're doing events and notifications. Um, so these are astra logs, but then again, if you astra is an app on an open shift cluster, so you might be able to get some logs that way. So you, you have a variety of options for how you want to manage your Kubernetes ecosystem. Yeah. I appreciate that it was thought ahead of, Hey, you've probably already got some sort of logging and alerting system that you can just hook right into. Um, you know, if you don't want to have, uh, that external system configured or a external meaning cloud insights or, or whatnot. Exactly. Yeah. So we have our own system. You might have your own system. You might be behind a firewall or, you know, behind a proxy. So we're thought of, we thought of. Well, you know, the bare minimum, we definitely have more ideas coming for integration points. Uh, but this is, this is the beginning. There's always more work to do, right? Oh yeah. Actually, yeah. Yeah. I got plenty to do today too. Uh, activity. This is a tab of just, uh, or a list of just everything that you've done so far. So if I, if I backup, when I deployed this, it created a user for me. It added that user, um, and credential. Then I logged in, I created a license. Uh, it's, it noticed that it, um, when I added a, so add credential, I think that's when I added the cluster. Um, it deployed the monitoring agent onto that cluster. I didn't even show that. I should have shown that. So both of the open shift clusters now have another namespace called net app monitoring. And in there, so the pods are the fluent bit and telegraph pods that are shooting metrics across the board. Anyway, I don't have to go through the whole thing, but this basically is a script of the demo I just went through. Um, things the system was doing as I was managing an app, cloning an app, um, yeah, cloning an app. Uh, I logged, somehow it logged me out and I logged myself back in. So anyway, that's about what I had planned for showing. So, um, I'd love to, you know, go further, but we are about an hour and a half into this thing. I do have more time if you guys want to see other things. You know, it was only a little bit of stuff that you showed there. Um, so I think, you know, just to recap, um, pretty impressive in an hour and a half time with a whole bunch of other introduction in there that we literally, you know, deployed Astra protected an application backed up an application and then cloned it over into an entirely different cluster. Um, you know, I, the only thing, not that I think that we, you know, need to show it. Um, but the only thing that like rounds that out is like taking a snapshot. Um, and it kind of encompasses all of that data protection aspect, whether it's point in time recovery with snapshots, whether it's actual backups, you know, to an external and, you know, S three bucket, um, you know, all of those different things. So pretty impressive within the amount of time I'll default to anybody who's on the stream. If you want to ask any questions, uh, if you want to request anything that we can see or that we can show, um, after the stream ends, you are more than welcome to reach out. Uh, so I tweeted about this stream. You can in that tweet, you can find, uh, Adams, uh, Twitter handle, which is at Adam Hade. Mine is at practical Andrew. Uh, you're also welcome to reach out to me. Um, I'm, I'm pretty easy to find a first name dot last name at red hat.com Andrew dot Sullivan red.com. So. Yeah. Same for me. Uh, first name dot last name at net. Um, my, I retweeted this too. So at Adam Hade had also retweeted the exact same thing. And, um, available on Slack through net up in red hat channels usually. Um, okay. So while we're letting people kind of digest that and decide if they want to ask questions, let's take a snapshot because, um, we haven't done that yet. It's the exact same process as backing up, except I don't have to choose a bucket to put it in. I just say take a snapshot. So we're going to call this one. Um, whatever Astro wants to name it, it looks like there's some, um, convention here with dates and then some, um, I bet it's a date and time review and go. So again, I'm a little bummed that my data protection screen is not showing. Oh, there's a. Does that, does that create a. Yeah. Yeah. Yeah. I could. So this is my fault because I wanted to show some of the latest bits that we've got here and I pulled this off the development branch, um, in order to get some of the cooler things that are, that are coming, um, particularly the backup screen when you, when you go to take a backup, you have, um, some new ways of displaying things and, and also the storage back in had some really cool things with the graphs that are being deployed, um, and capacity information. But because of that, there's a, there's an error here in the UI that, uh, I'm not showing data protection. Um, I'd have to, I could in, in deploy a whole new Astro and hook up these exact clusters to be managed again, uh, and show, um, with the GA bits. So I'm a little bummed about this, but, um, I, everything is still accessible to me through other menus. Okay. So that, that snapshot, is that a CSI snapshot as well? Like could we do, uh, like from, from the OpenShift GUI, can you see those snapshots? If we create one, I assume it will also, like if you create one through OpenShift, would it register or would Astro be aware of that? No. Astro knows about the snapshots it took. Okay. Um, but, I'm assuming that's because Astro is snapshotting more than just the PVC. It's probably snapshotting the state of the other Kubernetes objects. Yes. Okay. Yeah. Cause that actually makes a lot of sense. Um, you know, if somebody goes in and, and you know, changes the password for the database on this WordPress site, and you go to restore that back, well, that password is probably in an environment variable or in a secret, hopefully. Um, you know, so you wouldn't capture that just doing a PVC snapshot, whereas an application snapshot would have the state of all of those other objects as well. Exactly. Yeah. So here we're displaying it in OpenShift. These are the snaps, this is the snapshot that was just taken. So we've got, um, the snapshot of the, uh, PVC's and then, um, Astro is has additional information, uh, for point in time for all of the resources at the same, the same moment, uh, that this application snapshot was taken, but it wasn't packaged up and put into a bucket like a backup. It's. Yeah. Yeah. That makes sense. So this is, um, on 010, this was the restored version of the WordPress blog. And then I took a snapshot of it. The original is still over on 014 and there should be snapshots there because like I said, a backup is a snapshot that's been then compressed and moved out to a bucket. And so there should be snapshots on. Oh, no, it was moved. We moved it into a backup and moved it out. So yeah, there we go. Oh, that's interesting. So when you do a backup, it creates a snapshot, backs up that snapshot and then deletes the snapshot. That's, that's, that looks like that's what happened. Okay. I can, I can see and appreciate the decoupling of those things there, right? Cause the snapshot gives it that point in time. Nothing's going to change from here and a decoupling from there. And the backup is portable. You know, you want to be able to restore this thing somewhere else where you don't have a history of snapshots. It's just this, this is everything. So we took a snapshot to turn it into a full blown backup and then moved it into a bucket, which is then movable to another location. All right. Any questions come in or we got something coming in here. Oh, a lot of follows. Yeah, just thank you. Yeah. Thank you for everybody following. We appreciate all the, all the new net app folks. So yeah, a couple of thank yous and good jobs. But yeah, thank you to our audience. Adam, is there anything else that you want to show anything that we can highlight? You've been, you've been extremely thorough. So I feel like the answer there is probably going to be no, no, at this point. Well, what I'm tempted to do is start talking about all the cool stuff that we got coming, but I don't want to make promises or give dates. But as you can see, this is the beginning of a hugely growth capable product. So, you know, not only are we going to be working with OpenShift, we're going to work with all other flavors of Kubernetes, we're going to work across public and private clouds. We have a way for, you know, moving your app up to AWS or back down and we've got, you know, so that bridge is coming into play. We have data, so data protection, data, sorry, DR, disaster recovery. It's all acronyms. So we've got DR coming up so that if an app crashes, Astra can be watching other places where you might want it to stand up and manually at first can stand it up somewhere else because it's already been synchronizing things. We'll be using net apps, core, you know, data, data protection capabilities to be moving app, moving data faster than our current, the current one you just saw. So, you know, we've got a huge list of improvements to make to this system. Yeah, I'm curious about and I'll ask the question for Christian about, like, GitOps and whether or not there's a possibility for GitOps integration around some of the data protection aspects, although that would probably depend on having CRDs for many of those things? Yes, well, so almost everything that we're doing is intended to end up as a CRD. So, like, we have the REST API that can be activated by CRs. And you saw a little bit of that at the beginning. But regarding GitOps, we've been evaluating it or thinking about it. So, we have the list of things we actually are going to tackle and then we have the things that we are considering. And so, that's probably out there in the considering. We have had some conversations about it but haven't made any commitments together. Makes sense. Okay, so I don't have anything. I've been looking at our, you know, our shared doc here that we did a lot of the planning and I think all of the things that I had thought of beforehand, we've addressed in significant details, more than I was expecting. So, thank you. Yeah, there's been a blast, guys. I really like doing this stuff. Yeah, it's funny, you know, we've been streaming now for, what, a year and a half, Chris. And, you know, my stream just crossed a year old and it has been, it's a very different environment, but it's a lot of fun. And, you know, it's not like a conference. You know, I think we're all used to going to conferences and you present and everything is planned months in advance and you rehearse sessions. You know, some people will do it dozens or hundreds of times and, you know, you expect everything to work exactly the way that it always has. Live streams, it's interesting, because things break all the time, you know. Chris, who's on, you know, 90% of the live streams has seen many things go wrong, both in my stream and in others. Here, yeah. Local environment matters too. Yeah, and it's a lot of fun to troubleshoot those things or to kind of, gosh, I'm going to sound old, go with the flow. I guess I am old, right? But it worked. I mean, we did it today. We created a route because the IP address wasn't running properly. So, I mean, it's exciting, but it, you know, it didn't come crashing down too hard. I'm kind of happy about that. Real-time troubleshooting. Always fun. Yeah, good stuff. So, Chris, if you, so next week, my show will be back at its regular time. We'll be talking about bare metal installs with resox and ham. So it's always more official when it has a British accent associated with it. So there's that. Exactly. Yeah. I'm working on that. I'm not going to tell you. No, I'm not. I think that's true. I really want to go with West Australian. It's better for me. But yeah, so Chris, I don't know if there are any other streams you want to highlight. But I mean, the level of powers next week, obviously, same day as your show before it at 9am. We're doing the last call for code for racial justice on Tuesday next week. Dev Nation will have their normal thing on Thursday. We're doing a what's new briefing for OpenShift 49. Oh yeah. Day and morning. That was the one I was trying to think of. Yeah, starting at 10am Eastern 1400 UTC. So it'll be all the PMs will join. You can ask us questions. We'll get them answered for you. It'll be a very interactive session. And you get to see what's coming out. At the same time, everyone else does should be awesome. So I'm just posting into the chat here. A link over to the Astor Control Center landing page over on netapp.com or cloud.netapp.com. We also did. So I along with the product management team over at netapp. We did a webinar. I don't have the link to that. Yeah, I'll have to dig that up and what we can share that. But so we did do a webinar where we talked about many of these things at a high level. You know, Andrew's Andrew's technical as I hope most folks know. So I've really enjoyed getting to see things in action and seeing the low level stuff here. But yeah, if you have any questions, don't feel or don't hesitate to reach out practical Andrew on Twitter or Andrew dot solvent at redhat.com. I will also throw Chris under the bus at Chris short on Twitter or short at redhat.com and Adam, I'll let you volunteer your public contact information. Yeah, absolutely. Anytime anybody wants to talk about this stuff. I love to. So at Adam, Hey on Twitter or Adam dot hate at netapp.com. And I it's been a pleasure guys. This has been a ton of fun and I would love to do more stuff like this. So as it comes along, I obviously let you know and maybe we can do another show and tell. Absolutely. Great. All right. Well, thank you very much to our viewers. I hope you have a great rest of your day. A great weekend for those who don't have to work or continue working over the weekends. If not, stay safe out there everybody. See you soon.