>>all right, We're five minutes after the hour. That's all aboard. Who's coming aboard? Welcome everyone to the tutorial track for our launchpad of them. So for the next couple of hours, we've got a SYRIZA videos and experts on hand to answer questions about our new product, Doctor Enterprise Container Cloud. Before we jump into the videos and the technology, I just want to introduce myself and my other emcee for the session. I'm Bill Milks. I run curriculum development for Mirant us on. And >>I'm Bruce Basil Matthews. I'm the Western regional Solutions architect for Moran Tissue esa and welcome to everyone to this lovely launchpad oven event. >>We're lucky to have you with us proof. At least somebody on the call knows something about your enterprise Computer club. Um, speaking of people that know about Dr Enterprise Container Cloud, make sure that you've got a window open to the chat for this session. We've got a number of our engineers available and on hand to answer your questions live as we go through these videos and disgusting problem. So that's us, I guess, for Dr Enterprise Container Cloud, this is Mirant asses brand new product for bootstrapping Doctor Enterprise Kubernetes clusters at scale Anything. The airport Abu's? >>No, just that I think that we're trying Thio. Uh, let's see. Hold on. I think that we're trying Teoh give you a foundation against which to give this stuff a go yourself. And that's really the key to this thing is to provide some, you know, many training and education in a very condensed period. So, >>yeah, that's exactly what you're going to see. The SYRIZA videos we have today. We're going to focus on your first steps with Dr Enterprise Container Cloud from installing it to bootstrapping your regional child clusters so that by the end of the tutorial content today, you're gonna be prepared to spin up your first documentary prize clusters using documented prize container class. So just a little bit of logistics for the session. We're going to run through these tutorials twice. We're gonna do one run through starting seven minutes ago up until I guess it will be ten fifteen Pacific time. Then we're gonna run through the whole thing again. So if you've got other colleagues that weren't able to join right at the top of the hour and would like to jump in from the beginning, ten. Fifteen Pacific time. We're gonna do the whole thing over again. So if you want to see the videos twice, you got public friends and colleagues that, you know you wanna pull in for a second chance to see this stuff, we're gonna do it all. All twice. Yeah, this session. Any any logistics I should add, Bruce that No, >>I think that's that's pretty much what we had to nail down here. But let's zoom dash into those, uh, feature films. >>Let's do Edmonds. And like I said, don't be shy. Feel free to ask questions in the chat or engineers and boosting myself are standing by to answer your questions. So let me just tee up the first video here and walk their cost. Yeah. Mhm. Yes. Sorry. And here we go. So our first video here is gonna be about installing the Doctor Enterprise Container Club Management cluster. So I like to think of the management cluster as like your mothership, right? This is what you're gonna use to deploy all those little child clusters that you're gonna use is like, Come on it as clusters downstream. So the management costs was always our first step. Let's jump in there >>now. We have to give this brief little pause >>with no good day video. Focus for this demo will be the initial bootstrap of the management cluster in the first regional clusters to support AWS deployments. The management cluster provides the core functionality, including identity management, authentication, infantry release version. The regional cluster provides the specific architecture provided in this case, eight of us and the Elsie um, components on the UCP Cluster Child cluster is the cluster or clusters being deployed and managed. The deployment is broken up into five phases. The first phase is preparing a big strap note on this dependencies on handling with download of the bridge struck tools. The second phase is obtaining America's license file. Third phase. Prepare the AWS credentials instead of the adduce environment. The fourth configuring the deployment, defining things like the machine types on the fifth phase. Run the bootstrap script and wait for the deployment to complete. Okay, so here we're sitting up the strap node, just checking that it's clean and clear and ready to go there. No credentials already set up on that particular note. Now we're just checking through AWS to make sure that the account we want to use we have the correct credentials on the correct roles set up and validating that there are no instances currently set up in easy to instance, not completely necessary, but just helps keep things clean and tidy when I am perspective. Right. So next step, we're just going to check that we can, from the bootstrap note, reach more antis, get to the repositories where the various components of the system are available. They're good. No areas here. Yeah, right now we're going to start sitting at the bootstrap note itself. So we're downloading the cars release, get get cars, script, and then next, we're going to run it. I'm in. Deploy it. Changing into that big struck folder. Just making see what's there. Right now we have no license file, so we're gonna get the license filed. Oh, okay. Get the license file through the more antis downloads site, signing up here, downloading that license file and putting it into the Carisbrook struck folder. Okay, Once we've done that, we can now go ahead with the rest of the deployment. See that the follow is there. Uh, huh? That's again checking that we can now reach E C two, which is extremely important for the deployment. Just validation steps as we move through the process. All right, The next big step is valid in all of our AWS credentials. So the first thing is, we need those route credentials which we're going to export on the command line. This is to create the necessary bootstrap user on AWS credentials for the completion off the deployment we're now running an AWS policy create. So it is part of that is creating our Food trucks script, creating the mystery policy files on top of AWS, Just generally preparing the environment using a cloud formation script you'll see in a second will give a new policy confirmations just waiting for it to complete. Yeah, and there is done. It's gonna have a look at the AWS console. You can see that we're creative completed. Now we can go and get the credentials that we created Today I am console. Go to that new user that's being created. We'll go to the section on security credentials and creating new keys. Download that information media Access key I D and the secret access key. We went, Yeah, usually then exported on the command line. Okay. Couple of things to Notre. Ensure that you're using the correct AWS region on ensure that in the conflict file you put the correct Am I in for that region? I'm sure you have it together in a second. Yes. Okay, that's the key. Secret X key. Right on. Let's kick it off. Yeah, So this process takes between thirty and forty five minutes. Handles all the AWS dependencies for you, and as we go through, the process will show you how you can track it. Andi will start to see things like the running instances being created on the west side. The first phase off this whole process happening in the background is the creation of a local kind based bootstrapped cluster on the bootstrap node that clusters then used to deploy and manage all the various instances and configurations within AWS. At the end of the process, that cluster is copied into the new cluster on AWS and then shut down that local cluster essentially moving itself over. Okay. Local clusters boat just waiting for the various objects to get ready. Standard communities objects here Okay, so we speed up this process a little bit just for demonstration purposes. Yeah. There we go. So first note is being built the best in host. Just jump box that will allow us access to the entire environment. Yeah, In a few seconds, we'll see those instances here in the US console on the right. Um, the failures that you're seeing around failed to get the I. P for Bastian is just the weight state while we wait for a W s to create the instance. Okay. Yes. Here, beauty there. Okay. Mhm. Okay. Yeah, yeah. Okay. On there. We got question. Host has been built on three instances for the management clusters have now been created. We're going through the process of preparing. Those nodes were now copying everything over. See that? The scaling up of controllers in the big Strap cluster? It's indicating that we're starting all of the controllers in the new question. Almost there. Yeah. Yeah, just waiting for key. Clark. Uh huh. Start to finish up. Yeah. No. What? Now we're shutting down control this on the local bootstrap node on preparing our I. D. C. Configuration. Fourth indication, soon as this is completed. Last phase will be to deploy stack light into the new cluster the last time Monitoring tool set way Go stack like to plan It has started. Mhm coming to the end of the deployment Mountain. Yeah, America. Final phase of the deployment. Onda, We are done. Okay, You'll see. At the end they're providing us the details of you. I log in so there's a keeper clogging. You can modify that initial default password is part of the configuration set up with one documentation way. Go Councils up way can log in. Yeah, yeah, thank you very much for watching. >>Excellent. So in that video are wonderful field CTO Shauna Vera bootstrapped up management costume for Dr Enterprise Container Cloud Bruce, where exactly does that leave us? So now we've got this management costume installed like what's next? >>So primarily the foundation for being able to deploy either regional clusters that will then allow you to support child clusters. Uh, comes into play the next piece of what we're going to show, I think with Sean O'Mara doing this is the child cluster capability, which allows you to then deploy your application services on the local cluster. That's being managed by the ah ah management cluster that we just created with the bootstrap. >>Right? So this cluster isn't yet for workloads. This is just for bootstrapping up the downstream clusters. Those or what we're gonna use for workings. >>Exactly. Yeah. And I just wanted to point out, since Sean O'Mara isn't around, toe, actually answer questions. I could listen to that guy. Read the phone book, and it would be interesting, but anyway, you can tell him I said that >>he's watching right now, Crusoe. Good. Um, cool. So and just to make sure I understood what Sean was describing their that bootstrap er knows that you, like, ran document fresh pretender Cloud from to begin with. That's actually creating a kind kubernetes deployment kubernetes and Docker deployment locally. That then hits the AWS a p i in this example that make those e c two instances, and it makes like a three manager kubernetes cluster there, and then it, like, copies itself over toe those communities managers. >>Yeah, and and that's sort of where the transition happens. You can actually see it. The output that when it says I'm pivoting, I'm pivoting from my local kind deployment of cluster AP, I toothy, uh, cluster, that's that's being created inside of AWS or, quite frankly, inside of open stack or inside of bare metal or inside of it. The targeting is, uh, abstracted. Yeah, but >>those air three environments that we're looking at right now, right? Us bare metal in open staff environments. So does that kind cluster on the bootstrap er go away afterwards. You don't need that afterwards. Yeah, that is just temporary. To get things bootstrapped, then you manage things from management cluster on aws in this example? >>Yeah. Yeah. The seed, uh, cloud that post the bootstrap is not required anymore. And there's no, uh, interplay between them after that. So that there's no dependencies on any of the clouds that get created thereafter. >>Yeah, that actually reminds me of how we bootstrapped doctor enterprise back in the day, be a temporary container that would bootstrap all the other containers. Go away. It's, uh, so sort of a similar, similar temporary transient bootstrapping model. Cool. Excellent. What will convict there? It looked like there wasn't a ton, right? It looked like you had to, like, set up some AWS parameters like credentials and region and stuff like that. But other than that, that looked like heavily script herbal like there wasn't a ton of point and click there. >>Yeah, very much so. It's pretty straightforward from a bootstrapping standpoint, The config file that that's generated the template is fairly straightforward and targeted towards of a small medium or large, um, deployment. And by editing that single file and then gathering license file and all of the things that Sean went through, um, that that it makes it fairly easy to script >>this. And if I understood correctly as well that three manager footprint for your management cluster, that's the minimum, right. We always insist on high availability for this management cluster because boy do not wanna see oh, >>right, right. And you know, there's all kinds of persistent data that needs to be available, regardless of whether one of the notes goes down or not. So we're taking care of all of that for you behind the scenes without you having toe worry about it as a developer. >>No, I think there's that's a theme that I think will come back to throughout the rest of this tutorial session today is there's a lot of there's a lot of expertise baked him to Dr Enterprise Container Cloud in terms of implementing best practices for you like the defaulter, just the best practices of how you should be managing these clusters, Miss Seymour. Examples of that is the day goes on. Any interesting questions you want to call out from the chap who's >>well, there was. Yeah, yeah, there was one that we had responded to earlier about the fact that it's a management cluster that then conduce oh, either the the regional cluster or a local child molester. The child clusters, in each case host the application services, >>right? So at this point, we've got, in some sense, like the simplest architectures for our documentary prize Container Cloud. We've got the management cluster, and we're gonna go straight with child cluster. In the next video, there's a more sophisticated architecture, which will also proper today that inserts another layer between those two regional clusters. If you need to manage regions like across a BS, reads across with these documents anything, >>yeah, that that local support for the child cluster makes it a lot easier for you to manage the individual clusters themselves and to take advantage of our observation. I'll support systems a stack light and things like that for each one of clusters locally, as opposed to having to centralize thumb >>eso. It's a couple of good questions. In the chat here, someone was asking for the instructions to do this themselves. I strongly encourage you to do so. That should be in the docks, which I think Dale helpfully thank you. Dale provided links for that's all publicly available right now. So just head on in, head on into the docks like the Dale provided here. You can follow this example yourself. All you need is a Mirante license for this and your AWS credentials. There was a question from many a hear about deploying this toe azure. Not at G. Not at this time. >>Yeah, although that is coming. That's going to be in a very near term release. >>I didn't wanna make promises for product, but I'm not too surprised that she's gonna be targeted. Very bracing. Cool. Okay. Any other thoughts on this one does. >>No, just that the fact that we're running through these individual pieces of the steps Well, I'm sure help you folks. If you go to the link that, uh, the gentleman had put into the chat, um, giving you the step by staff. Um, it makes it fairly straightforward to try this yourselves. >>E strongly encourage that, right? That's when you really start to internalize this stuff. OK, but before we move on to the next video, let's just make sure everyone has a clear picture in your mind of, like, where we are in the life cycle here creating this management cluster. Just stop me if I'm wrong. Who's creating this management cluster is like, you do that once, right? That's when your first setting up your doctor enterprise container cloud environment of system. What we're going to start seeing next is creating child clusters and this is what you're gonna be doing over and over and over again. When you need to create a cluster for this Deb team or, you know, this other team river it is that needs commodity. Doctor Enterprise clusters create these easy on half will. So this was once to set up Dr Enterprise Container Cloud Child clusters, which we're going to see next. We're gonna do over and over and over again. So let's go to that video and see just how straightforward it is to spin up a doctor enterprise cluster for work clothes as a child cluster. Undocumented brands contain >>Hello. In this demo, we will cover the deployment experience of creating a new child cluster, the scaling of the cluster and how to update the cluster. When a new version is available, we begin the process by logging onto the you I as a normal user called Mary. Let's go through the navigation of the U I so you can switch. Project Mary only has access to development. Get a list of the available projects that you have access to. What clusters have been deployed at the moment there. Nan Yes, this H Keys Associate ID for Mary into her team on the cloud credentials that allow you to create access the various clouds that you can deploy clusters to finally different releases that are available to us. We can switch from dark mode to light mode, depending on your preferences, Right? Let's now set up semester search keys for Mary so she can access the notes and machines again. Very simply, had Mississippi key give it a name, we copy and paste our public key into the upload key block. Or we can upload the key if we have the file available on our local machine. A simple process. So to create a new cluster, we define the cluster ad management nodes and add worker nodes to the cluster. Yeah, again, very simply, you go to the clusters tab. We hit the create cluster button. Give the cluster name. Yeah, Andi, select the provider. We only have access to AWS in this particular deployment, so we'll stick to AWS. What's like the region in this case? US West one release version five point seven is the current release Onda Attach. Mary's Key is necessary Key. We can then check the rest of the settings, confirming the provider Any kubernetes c r D r I p address information. We can change this. Should we wish to? We'll leave it default for now on. Then what components? A stack light I would like to deploy into my Custer. For this. I'm enabling stack light on logging on Aiken. Sit up the retention sizes Attention times on. Even at this stage, at any customer alerts for the watchdogs. E consider email alerting which I will need my smart host details and authentication details. Andi Slack Alerts. Now I'm defining the cluster. All that's happened is the cluster's been defined. I now need to add machines to that cluster. I'll begin by clicking the create machine button within the cluster definition. Oh, select manager, Select the number of machines. Three is the minimum. Select the instant size that I'd like to use from AWS and very importantly, ensure correct. Use the correct Am I for the region. I commend side on the route device size. There we go, my three machines obviously creating. I now need to add some workers to this custom. So I go through the same process this time once again, just selecting worker. I'll just add to once again, the AM is extremely important. Will fail if we don't pick the right, Am I for a boon to machine in this case and the deployment has started. We can go and check on the bold status are going back to the clusters screen on clicking on the little three dots on the right. We get the cluster info and the events, so the basic cluster info you'll see pending their listen cluster is still in the process of being built. We kick on, the events will get a list of actions that have been completed This part of the set up of the cluster. So you can see here we've created the VPC. We've created the sub nets on We've created the Internet gateway. It's unnecessary made of us and we have no warnings of the stage. Yeah, this will then run for a while. We have one minute past waken click through. We can check the status of the machine bulls as individuals so we can check the machine info, details of the machines that we've assigned, right? Mhm Onda. See any events pertaining to the machine areas like this one on normal? Yeah. Just watch asked. The community's components are waiting for the machines to start. Go back to Custer's. Okay, right. Because we're moving ahead now. We can see we have it in progress. Five minutes in new Matt Gateway on the stage. The machines have been built on assigned. I pick up the U. S. Thank you. Yeah. There we go. Machine has been created. See the event detail and the AWS. I'd for that machine. Mhm. No speeding things up a little bit. This whole process and to end takes about fifteen minutes. Run the clock forward, you'll notice is the machines continue to bold the in progress. We'll go from in progress to ready. A soon as we got ready on all three machines, the managers on both workers way could go on and we could see that now we reached the point where the cluster itself is being configured. Mhm, mhm. And then we go. Cluster has been deployed. So once the classes deployed, we can now never get around our environment. Okay, Are cooking into configure cluster We could modify their cluster. We could get the end points for alert alert manager on See here The griffon occupying and Prometheus are still building in the background but the cluster is available on you would be able to put workloads on it the stretch to download the cube conflict so that I can put workloads on it. It's again three little dots in the right for that particular cluster. If the download cube conflict give it my password, I now have the Q conflict file necessary so that I can access that cluster Mhm all right Now that the build is fully completed, we can check out cluster info on. We can see that Allow the satellite components have been built. All the storage is there, and we have access to the CPU. I So if we click into the cluster, we can access the UCP dashboard, right? Shit. Click the signing with Detroit button to use the SSO on. We give Mary's possible to use the name once again. Thing is, an unlicensed cluster way could license at this point. Or just skip it on. There. We have the UCP dashboard. You can see that has been up for a little while. We have some data on the dashboard going back to the console. We can now go to the griffon, a data just being automatically pre configured for us. We can switch and utilized a number of different dashboards that have already been instrumented within the cluster. So, for example, communities cluster information, the name spaces, deployments, nodes. Mhm. So we look at nodes. If we could get a view of the resource is utilization of Mrs Custer is very little running in it. Yeah. General dashboard of Cuba navies cluster one of this is configurable. You can modify these for your own needs, or add your own dashboards on de scoped to the cluster. So it is available to all users who have access to this specific cluster, all right to scale the cluster on to add a notice. A simple is the process of adding a mode to the cluster, assuming we've done that in the first place. So we go to the cluster, go into the details for the cluster we select, create machine. Once again, we need to be ensure that we put the correct am I in and any other functions we like. You can create different sized machines so it could be a larger node. Could be bigger disks and you'll see that worker has been added from the provisioning state on shortly. We will see the detail off that worker as a complete to remove a note from a cluster. Once again, we're going to the cluster. We select the node would like to remove. Okay, I just hit delete On that note. Worker nodes will be removed from the cluster using according and drawing method to ensure that your workouts are not affected. Updating a cluster. When an update is available in the menu for that particular cluster, the update button will become available. And it's a simple as clicking the button, validating which release you would like to update to. In this case, the next available releases five point seven point one. Here I'm kicking the update by in the background We will coordinate. Drain each node slowly go through the process of updating it. Andi update will complete depending on what the update is as quickly as possible. Girl, we go. The notes being rebuilt in this case impacted the manager node. So one of the manager nodes is in the process of being rebuilt. In fact, to in this case, one has completed already on In a few minutes we'll see that there are great has been completed. There we go. Great. Done. Yeah. If you work loads of both using proper cloud native community standards, there will be no impact. >>Excellent. So at this point, we've now got a cluster ready to start taking our communities of workloads. He started playing or APs to that costume. So watching that video, the thing that jumped out to me at first Waas like the inputs that go into defining this workload cost of it. All right, so we have to make sure we were using on appropriate am I for that kind of defines the substrate about what we're gonna be deploying our cluster on top of. But there's very little requirements. A so far as I could tell on top of that, am I? Because Docker enterprise Container Cloud is gonna bootstrap all the components that you need. That s all we have is kind of kind of really simple bunch box that we were deploying these things on top of so one thing that didn't get dug into too much in the video. But it's just sort of implied. Bruce, maybe you can comment on this is that release that Shawn had to choose for his, uh, for his cluster in creating it. And that release was also the thing we had to touch. Wanted to upgrade part cluster. So you have really sharp eyes. You could see at the end there that when you're doing the release upgrade enlisted out a stack of components docker, engine, kubernetes, calico, aled, different bits and pieces that go into, uh, go into one of these commodity clusters that deploy. And so, as far as I can tell in that case, that's what we mean by a release. In this sense, right? It's the validated stack off container ization and orchestration components that you know we've tested out and make sure it works well, introduction environments. >>Yeah, and and And that's really the focus of our effort is to ensure that any CVS in any of the stack are taken care of that there is a fixes air documented and up streamed to the open stack community source community, um, and and that, you know, then we test for the scaling ability and the reliability in high availability configuration for the clusters themselves. The hosts of your containers. Right. And I think one of the key, uh, you know, benefits that we provide is that ability to let you know, online, high. We've got an update for you, and it's fixes something that maybe you had asked us to fix. Uh, that all comes to you online as your managing your clusters, so you don't have to think about it. It just comes as part of the product. >>You just have to click on Yes. Please give me that update. Uh, not just the individual components, but again. It's that it's that validated stack, right? Not just, you know, component X, y and Z work. But they all work together effectively Scalable security, reliably cool. Um, yeah. So at that point, once we started creating that workload child cluster, of course, we bootstrapped good old universal control plane. Doctor Enterprise. On top of that, Sean had the classic comment there, you know? Yeah. Yeah. You'll see a little warnings and errors or whatever. When you're setting up, UCP don't handle, right, Just let it do its job, and it will converge all its components, you know, after just just a minute or two. But we saw in that video, we sped things up a little bit there just we didn't wait for, you know, progress fighters to complete. But really, in real life, that whole process is that anything so spend up one of those one of those fosters so quite quite quick. >>Yeah, and and I think the the thoroughness with which it goes through its process and re tries and re tries, uh, as you know, and it was evident when we went through the initial ah video of the bootstrapping as well that the processes themselves are self healing, as they are going through. So they will try and retry and wait for the event to complete properly on. And once it's completed properly, then it will go to the next step. >>Absolutely. And the worst thing you could do is panic at the first warning and start tearing things that don't don't do that. Just don't let it let it heal. Let take care of itself. And that's the beauty of these manage solutions is that they bake in a lot of subject matter expertise, right? The decisions that are getting made by those containers is they're bootstrapping themselves, reflect the expertise of the Mirant ISS crew that has been developing this content in these two is free for years and years now, over recognizing humanities. One cool thing there that I really appreciate it actually that it adds on top of Dr Enterprise is that automatic griffon a deployment as well. So, Dr Enterprises, I think everyone knows has had, like, some very high level of statistics baked into its dashboard for years and years now. But you know our customers always wanted a double click on that right to be able to go a little bit deeper. And Griffon are really addresses that it's built in dashboards. That's what's really nice to see. >>Yeah, uh, and all of the alerts and, uh, data are actually captured in a Prometheus database underlying that you have access to so that you are allowed to add new alerts that then go out to touch slack and say hi, You need to watch your disk space on this machine or those kinds of things. Um, and and this is especially helpful for folks who you know, want to manage the application service layer but don't necessarily want to manage the operations side of the house. So it gives them a tool set that they can easily say here, Can you watch these for us? And Miran tas can actually help do that with you, So >>yeah, yeah, I mean, that's just another example of baking in that expert knowledge, right? So you can leverage that without tons and tons of a long ah, long runway of learning about how to do that sort of thing. Just get out of the box right away. There was the other thing, actually, that you could sleep by really quickly if you weren't paying close attention. But Sean mentioned it on the video. And that was how When you use dark enterprise container cloud to scale your cluster, particularly pulling a worker out, it doesn't just like Territo worker down and forget about it. Right? Is using good communities best practices to cordon and drain the No. So you aren't gonna disrupt your workloads? You're going to just have a bunch of containers instantly. Excellent crash. You could really carefully manage the migration of workloads off that cluster has baked right in tow. How? How? Document? The brass container cloud is his handling cluster scale. >>Right? And And the kubernetes, uh, scaling methodology is is he adhered to with all of the proper techniques that ensure that it will tell you. Wait, you've got a container that actually needs three, uh, three, uh, instances of itself. And you don't want to take that out, because that node, it means you'll only be able to have to. And we can't do that. We can't allow that. >>Okay, Very cool. Further thoughts on this video. So should we go to the questions. >>Let's let's go to the questions >>that people have. Uh, there's one good one here, down near the bottom regarding whether an a p I is available to do this. So in all these demos were clicking through this web. You I Yes, this is all a p. I driven. You could do all of this. You know, automate all this away is part of the CSC change. Absolutely. Um, that's kind of the point, right? We want you to be ableto spin up. Come on. I keep calling them commodity clusters. What I mean by that is clusters that you can create and throw away. You know, easily and automatically. So everything you see in these demos eyes exposed to FBI? >>Yeah. In addition, through the standard Cube cuddle, Uh, cli as well. So if you're not a programmer, but you still want to do some scripting Thio, you know, set up things and deploy your applications and things. You can use this standard tool sets that are available to accomplish that. >>There is a good question on scale here. So, like, just how many clusters and what sort of scale of deployments come this kind of support our engineers report back here that we've done in practice up to a Zeman ia's like two hundred clusters. We've deployed on this with two hundred fifty nodes in a cluster. So were, you know, like like I said, hundreds, hundreds of notes, hundreds of clusters managed by documented press container fall and then those downstream clusters, of course, subject to the usual constraints for kubernetes, right? Like default constraints with something like one hundred pods for no or something like that. There's a few different limitations of how many pods you can run on a given cluster that comes to us not from Dr Enterprise Container Cloud, but just from the underlying kubernetes distribution. >>Yeah, E. I mean, I don't think that we constrain any of the capabilities that are available in the, uh, infrastructure deliveries, uh, service within the goober Netease framework. So were, you know, But we are, uh, adhering to the standards that we would want to set to make sure that we're not overloading a node or those kinds of things, >>right. Absolutely cool. Alright. So at this point, we've got kind of a two layered our protection when we are management cluster, but we deployed in the first video. Then we use that to deploy one child clustering work, classroom, uh, for more sophisticated deployments where we might want to manage child clusters across multiple regions. We're gonna add another layer into our architectural we're gonna add in regional cluster management. So this idea you're gonna have the single management cluster that we started within the first video. On the next video, we're gonna learn how to spin up a regional clusters, each one of which would manage, for example, a different AWS uh, US region. So let me just pull out the video for that bill. We'll check it out for me. Mhm. >>Hello. In this demo, we will cover the deployment of additional regional management. Cluster will include a brief architectures of you how to set up the management environment, prepare for the deployment deployment overview and then just to prove it, to play a regional child cluster. So, looking at the overall architecture, the management cluster provides all the core functionality, including identity management, authentication, inventory and release version. ING Regional Cluster provides the specific architecture provider in this case AWS on the LCN components on the D you speak Cluster for child cluster is the cluster or clusters being deployed and managed? Okay, so why do you need a regional cluster? Different platform architectures, for example aws who have been stack even bare metal to simplify connectivity across multiple regions handle complexities like VPNs or one way connectivity through firewalls, but also help clarify availability zones. Yeah. Here we have a view of the regional cluster and how it connects to the management cluster on their components, including items like the LCN cluster Manager we also Machine Manager were held. Mandel are managed as well as the actual provider logic. Mhm. Okay, we'll begin by logging on Is the default administrative user writer. Okay, once we're in there, we'll have a look at the available clusters making sure we switch to the default project which contains the administration clusters. Here we can see the cars management cluster, which is the master controller. And you see, it only has three nodes, three managers, no workers. Okay, if we look at another regional cluster similar to what we're going to deploy now, also only has three managers once again, no workers. But as a comparison, here's a child cluster This one has three managers, but also has additional workers associate it to the cluster. All right, we need to connect. Tell bootstrap note. Preferably the same note that used to create the original management plaster. It's just on AWS, but I still want to machine. All right. A few things we have to do to make sure the environment is ready. First thing we're going to see go into route. We'll go into our releases folder where we have the kozberg struck on. This was the original bootstrap used to build the original management cluster. Yeah, we're going to double check to make sure our cube con figures there once again, the one created after the original customers created just double check. That cute conflict is the correct one. Does point to the management cluster. We're just checking to make sure that we can reach the images that everything is working. A condom. No damages waken access to a swell. Yeah. Next we're gonna edit the machine definitions. What we're doing here is ensuring that for this cluster we have the right machine definitions, including items like the am I. So that's found under the templates AWS directory. We don't need to edit anything else here. But we could change items like the size of the machines attempts. We want to use that The key items to ensure where you changed the am I reference for the junta image is the one for the region in this case AWS region for utilizing this was no construct deployment. We have to make sure we're pointing in the correct open stack images. Yeah, okay. Set the correct and my save file. Now we need to get up credentials again. When we originally created the bootstrap cluster, we got credentials from eight of the U. S. If we hadn't done this, we would need to go through the u A. W s set up. So we're just exporting the AWS access key and I d. What's important is CAAs aws enabled equals. True. Now we're sitting the region for the new regional cluster. In this case, it's Frankfurt on exporting our cube conflict that we want to use for the management cluster. When we looked at earlier Yeah, now we're exporting that. Want to call the cluster region Is Frank Foods Socrates Frankfurt yet trying to use something descriptive It's easy to identify. Yeah, and then after this, we'll just run the bootstrap script, which will complete the deployment for us. Bootstrap of the regional cluster is quite a bit quicker than the initial management clusters. There are fewer components to be deployed. Um, but to make it watchable, we've spent it up. So we're preparing our bootstrap cluster on the local bootstrap node. Almost ready on. We started preparing the instances at W s and waiting for that bastard and no to get started. Please. The best you nerd Onda. We're also starting to build the actual management machines they're now provisioning on. We've reached the point where they're actually starting to deploy. Dr. Enterprise, this is probably the longest face. Yeah, seeing the second that all the nerds will go from the player deployed. Prepare, prepare. Yeah, You'll see their status changes updates. He was the first night ready. Second, just applying second already. Both my time. No waiting from home control. Let's become ready. Removing cluster the management cluster from the bootstrap instance into the new cluster running the date of the U. S. All my stay. Ah, now we're playing Stockland. Switch over is done on. Done. Now I will build a child cluster in the new region very, very quickly to find the cluster will pick. Our new credential has shown up. We'll just call it Frankfurt for simplicity a key and customs to find. That's the machine. That cluster stop with three managers. Set the correct Am I for the region? Yeah, Do the same to add workers. There we go test the building. Yeah. Total bill of time Should be about fifteen minutes. Concedes in progress. It's going to expect this up a little bit. Check the events. We've created all the dependencies, machine instances, machines, a boat shortly. We should have a working cluster in Frankfurt region. Now almost a one note is ready from management. Two in progress. Yeah, on we're done. Clusters up and running. Yeah. >>Excellent. So at this point, we've now got that three tier structure that we talked about before the video. We got that management cluster that we do strapped in the first video. Now we have in this example to different regional clustering one in Frankfurt, one of one management was two different aws regions. And sitting on that you can do Strap up all those Doctor enterprise costumes that we want for our work clothes. >>Yeah, that's the key to this is to be able to have co resident with your actual application service enabled clusters the management co resident with it so that you can, you know, quickly access that he observation Elson Surfboard services like the graph, Ana and that sort of thing for your particular region. A supposed to having to lug back into the home. What did you call it when we started >>the mothership? >>The mothership. Right. So we don't have to go back to the mother ship. We could get >>it locally. Yeah, when, like to that point of aggregating things under a single pane of glass? That's one thing that again kind of sailed by in the demo really quickly. But you'll notice all your different clusters were on that same cluster. Your pain on your doctor Enterprise Container Cloud management. Uh, court. Right. So both your child clusters for running workload and your regional clusters for bootstrapping. Those child clusters were all listed in the same place there. So it's just one pane of glass to go look for, for all of your clusters, >>right? And, uh, this is kind of an important point. I was, I was realizing, as we were going through this. All of the mechanics are actually identical between the bootstrapped cluster of the original services and the bootstrapped cluster of the regional services. It's the management layer of everything so that you only have managers, you don't have workers and that at the child cluster layer below the regional or the management cluster itself, that's where you have the worker nodes. And those are the ones that host the application services in that three tiered architecture that we've now defined >>and another, you know, detail for those that have sharp eyes. In that video, you'll notice when deploying a child clusters. There's not on Lee. A minimum of three managers for high availability management cluster. You must have at least two workers that's just required for workload failure. It's one of those down get out of work. They could potentially step in there, so your minimum foot point one of these child clusters is fine. Violence and scalable, obviously, from a >>That's right. >>Let's take a quick peek of the questions here, see if there's anything we want to call out, then we move on to our last want to my last video. There's another question here about, like where these clusters can live. So again, I know these examples are very aws heavy. Honestly, it's just easy to set up down on the other us. We could do things on bare metal and, uh, open stack departments on Prem. That's what all of this still works in exactly the same way. >>Yeah, the, uh, key to this, especially for the the, uh, child clusters, is the provision hers? Right? See you establish on AWS provision or you establish a bare metal provision or you establish a open stack provision. Or and eventually that list will include all of the other major players in the cloud arena. But you, by selecting the provision or within your management interface, that's where you decide where it's going to be hosted, where the child cluster is to be hosted. >>Speaking off all through a child clusters. Let's jump into our last video in the Siri's, where we'll see how to spin up a child cluster on bare metal. >>Hello. This demo will cover the process of defining bare metal hosts and then review the steps of defining and deploying a bare metal based doctor enterprise cluster. So why bare metal? Firstly, it eliminates hyper visor overhead with performance boost of up to thirty percent. Provides direct access to GP use, prioritize for high performance wear clothes like machine learning and AI, and supports high performance workloads like network functions, virtualization. It also provides a focus on on Prem workloads, simplifying and ensuring we don't need to create the complexity of adding another opera visor. Lay it between so continue on the theme Why Communities and bare metal again Hyper visor overhead. Well, no virtualization overhead. Direct access to hardware items like F p G A s G p us. We can be much more specific about resource is required on the nodes. No need to cater for additional overhead. Uh, we can handle utilization in the scheduling. Better Onda we increase the performances and simplicity of the entire environment as we don't need another virtualization layer. Yeah, In this section will define the BM hosts will create a new project will add the bare metal hosts, including the host name. I put my credentials I pay my address the Mac address on then provide a machine type label to determine what type of machine it is for later use. Okay, let's get started. So well again. Was the operator thing. We'll go and we'll create a project for our machines to be a member off helps with scoping for later on for security. I begin the process of adding machines to that project. Yeah. So the first thing we had to be in post, Yeah, many of the machine A name. Anything you want, que experimental zero one. Provide the IAP my user name type my password. Okay. On the Mac address for the common interface with the boot interface and then the i p m I i p address These machines will be at the time storage worker manager. He's a manager. Yeah, we're gonna add a number of other machines on will. Speed this up just so you could see what the process looks like in the future. Better discovery will be added to the product. Okay. Okay. Getting back there we have it are Six machines have been added, are busy being inspected, being added to the system. Let's have a look at the details of a single note. Yeah, you can see information on the set up of the node. Its capabilities? Yeah. As well as the inventory information about that particular machine. I see. Okay, let's go and create the cluster. Yeah, So we're going to deploy a bare metal child cluster. The process we're going to go through is pretty much the same as any other child cluster. So we'll credit custom. We'll give it a name, but if it were selecting bare metal on the region, we're going to select the version we want to apply. No way. We're going to add this search keys. If we hope we're going to give the load. Balancer host I p that we'd like to use out of dress range on update the address range that we want to use for the cluster. Check that the sea ideal blocks for the Cuban ladies and tunnels are what we want them to be. Enable disabled stack light. Yeah, and soothe stack light settings to find the cluster. And then, as for any other machine, we need to add machines to the cluster. Here. We're focused on building communities clusters, so we're gonna put the count of machines. You want managers? We're gonna pick the label type manager and create three machines is the manager for the Cuban eighties. Casting Okay thing. We're having workers to the same. It's a process. Just making sure that the worker label host level are I'm sorry. On when Wait for the machines to deploy. Let's go through the process of putting the operating system on the notes validating and operating system deploying doctor identifies Make sure that the cluster is up and running and ready to go. Okay, let's review the bold events waken See the machine info now populated with more information about the specifics of things like storage and of course, details of a cluster etcetera. Yeah, yeah, well, now watch the machines go through the various stages from prepared to deploy on what's the cluster build? And that brings us to the end of this particular demo. You can see the process is identical to that of building a normal child cluster we got our complaint is complete. >>All right, so there we have it, deploying a cluster to bare metal. Much the same is how we did for AWS. I guess maybe the biggest different stepwise there is there is that registration face first, right? So rather than just using AWS financials toe magically create PM's in the cloud. You got a point out all your bare metal servers to Dr Enterprise between the cloud and they really come in, I guess three profiles, right? You got your manager profile with a profile storage profile which has been labeled as allocate. Um, crossword cluster has appropriate, >>right? And And I think that the you know, the key differentiator here is that you have more physical control over what, uh, attributes that love your cat, by the way, uh, where you have the different attributes of a server of physical server. So you can, uh, ensure that the SSD configuration on the storage nodes is gonna be taken advantage of in the best way the GP use on the worker nodes and and that the management layer is going to have sufficient horsepower to, um, spin up to to scale up the the environments, as required. One of the things I wanted to mention, though, um, if I could get this out without the choking much better. Um, is that Ah, hey, mentioned the load balancer and I wanted to make sure in defining the load balancer and the load balancer ranges. Um, that is for the top of the the cluster itself. That's the operations of the management, uh, layer integrating with your systems internally to be able to access the the Cube Can figs. I I p address the, uh, in a centralized way. It's not the load balancer that's working within the kubernetes cluster that you are deploying. That's still cube proxy or service mesh, or however you're intending to do it. So, um, it's kind of an interesting step that your initial step in building this, um and we typically use things like metal L B or in gen X or that kind of thing is to establish that before we deploy this bear mental cluster so that it can ride on top of that for the tips and things. >>Very cool. So any other thoughts on what we've seen so far today? Bruce, we've gone through all the different layers. Doctor enterprise container clouds in these videos from our management are regional to our clusters on aws hand bear amount, Of course, with his dad is still available. Closing thoughts before we take just a very short break and run through these demos again. >>You know, I've been very exciting. Ah, doing the presentation with you. I'm really looking forward to doing it the second time, so that we because we've got a good rhythm going about this kind of thing. So I'm looking forward to doing that. But I think that the key elements of what we're trying to convey to the folks out there in the audience that I hope you've gotten out of it is that will that this is an easy enough process that if you follow the step by steps going through the documentation that's been put out in the chat, um, that you'll be able to give this a go yourself, Um, and you don't have to limit yourself toe having physical hardware on prim to try it. You could do it in a ws as we've shown you today. And if you've got some fancy use cases like, uh, you you need a Hadoop And and, uh, you know, cloud oriented ai stuff that providing a bare metal service helps you to get there very fast. So right. Thank you. It's been a pleasure. >>Yeah, thanks everyone for coming out. So, like I said we're going to take a very short, like, three minute break here. Uh, take the opportunity to let your colleagues know if they were in another session or they didn't quite make it to the beginning of this session. Or if you just want to see these demos again, we're going to kick off this demo. Siri's again in just three minutes at ten. Twenty five a. M. Pacific time where we will see all this great stuff again. Let's take a three minute break. I'll see you all back here in just two minutes now, you know. Okay, folks, that's the end of our extremely short break. We'll give people just maybe, like one more minute to trickle in if folks are interested in coming on in and jumping into our demo. Siri's again. Eso For those of you that are just joining us now I'm Bill Mills. I head up curriculum development for the training team here. Moran Tous on Joining me for this session of demos is Bruce. Don't you go ahead and introduce yourself doors, who is still on break? That's cool. We'll give Bruce a minute or two to get back while everyone else trickles back in. There he is. Hello, Bruce. >>How'd that go for you? Okay, >>Very well. So let's kick off our second session here. I e just interest will feel for you. Thio. Let it run over here. >>Alright. Hi. Bruce Matthews here. I'm the Western Regional Solutions architect for Marantz. Use A I'm the one with the gray hair and the glasses. Uh, the handsome one is Bill. So, uh, Bill, take it away. >>Excellent. So over the next hour or so, we've got a Siris of demos that's gonna walk you through your first steps with Dr Enterprise Container Cloud Doctor Enterprise Container Cloud is, of course, Miranda's brand new offering from bootstrapping kubernetes clusters in AWS bare metal open stack. And for the providers in the very near future. So we we've got, you know, just just over an hour left together on this session, uh, if you joined us at the top of the hour back at nine. A. M. Pacific, we went through these demos once already. Let's do them again for everyone else that was only able to jump in right now. Let's go. Our first video where we're gonna install Dr Enterprise container cloud for the very first time and use it to bootstrap management. Cluster Management Cluster, as I like to describe it, is our mother ship that's going to spin up all the other kubernetes clusters, Doctor Enterprise clusters that we're gonna run our workloads on. So I'm gonna do >>I'm so excited. I can hardly wait. >>Let's do it all right to share my video out here. Yeah, let's do it. >>Good day. The focus for this demo will be the initial bootstrap of the management cluster on the first regional clusters. To support AWS deployments, the management cluster provides the core functionality, including identity management, authentication, infantry release version. The regional cluster provides the specific architecture provided in this case AWS and the Elsom components on the UCP cluster Child cluster is the cluster or clusters being deployed and managed. The deployment is broken up into five phases. The first phase is preparing a bootstrap note on its dependencies on handling the download of the bridge struck tools. The second phase is obtaining America's license file. Third phase. Prepare the AWS credentials instead of the ideas environment, the fourth configuring the deployment, defining things like the machine types on the fifth phase, Run the bootstrap script and wait for the deployment to complete. Okay, so here we're sitting up the strap node. Just checking that it's clean and clear and ready to go there. No credentials already set up on that particular note. Now, we're just checking through aws to make sure that the account we want to use we have the correct credentials on the correct roles set up on validating that there are no instances currently set up in easy to instance, not completely necessary, but just helps keep things clean and tidy when I am perspective. Right. So next step, we're just gonna check that we can from the bootstrap note, reach more antis, get to the repositories where the various components of the system are available. They're good. No areas here. Yeah, right now we're going to start sitting at the bootstrap note itself. So we're downloading the cars release, get get cars, script, and then next we're going to run it. Yeah, I've been deployed changing into that big struck folder, just making see what's there right now we have no license file, so we're gonna get the license filed. Okay? Get the license file through more antis downloads site signing up here, downloading that license file and putting it into the Carisbrook struck folder. Okay, since we've done that, we can now go ahead with the rest of the deployment. Yeah, see what the follow is there? Uh huh. Once again, checking that we can now reach E C two, which is extremely important for the deployment. Just validation steps as we move through the process. Alright. Next big step is violating all of our AWS credentials. So the first thing is, we need those route credentials which we're going to export on the command line. This is to create the necessary bootstrap user on AWS credentials for the completion off the deployment we're now running in AWS policy create. So it is part of that is creating our food trucks script. Creating this through policy files onto the AWS, just generally preparing the environment using a cloud formation script, you'll see in a second, I'll give a new policy confirmations just waiting for it to complete. And there is done. It's gonna have a look at the AWS console. You can see that we're creative completed. Now we can go and get the credentials that we created. Good day. I am console. Go to the new user that's being created. We'll go to the section on security credentials and creating new keys. Download that information media access Key I. D and the secret access key, but usually then exported on the command line. Okay, Couple of things to Notre. Ensure that you're using the correct AWS region on ensure that in the conflict file you put the correct Am I in for that region? I'm sure you have it together in a second. Okay, thanks. Is key. So you could X key Right on. Let's kick it off. So this process takes between thirty and forty five minutes. Handles all the AWS dependencies for you. Um, as we go through, the process will show you how you can track it. Andi will start to see things like the running instances being created on the AWS side. The first phase off this whole process happening in the background is the creation of a local kind based bootstrapped cluster on the bootstrap node that clusters then used to deploy and manage all the various instances and configurations within AWS at the end of the process. That cluster is copied into the new cluster on AWS and then shut down that local cluster essentially moving itself over. Yeah, okay. Local clusters boat. Just waiting for the various objects to get ready. Standard communities objects here. Yeah, you mentioned Yeah. So we've speed up this process a little bit just for demonstration purposes. Okay, there we go. So first note is being built the bastion host just jump box that will allow us access to the entire environment. Yeah, In a few seconds, we'll see those instances here in the US console on the right. Um, the failures that you're seeing around failed to get the I. P for Bastian is just the weight state while we wait for AWS to create the instance. Okay. Yeah. Beauty there. Movies. Okay, sketch. Hello? Yeah, Okay. Okay. On. There we go. Question host has been built on three instances for the management clusters have now been created. Okay, We're going through the process of preparing. Those nodes were now copying everything over. See that scaling up of controllers in the big strapped cluster? It's indicating that we're starting all of the controllers in the new question. Almost there. Right? Okay. Just waiting for key. Clark. Uh huh. So finish up. Yeah. No. Now we're shutting down. Control this on the local bootstrap node on preparing our I. D. C configuration, fourth indication. So once this is completed, the last phase will be to deploy stack light into the new cluster, that glass on monitoring tool set, Then we go stack like deployment has started. Mhm. Coming to the end of the deployment mountain. Yeah, they were cut final phase of the deployment. And we are done. Yeah, you'll see. At the end, they're providing us the details of you. I log in. So there's a key Clark log in. Uh, you can modify that initial default possible is part of the configuration set up where they were in the documentation way. Go Councils up way can log in. Yeah. Yeah. Thank you very much for watching. >>All right, so at this point, what we have we got our management cluster spun up, ready to start creating work clusters. So just a couple of points to clarify there to make sure everyone caught that, uh, as advertised. That's darker. Enterprise container cloud management cluster. That's not rework loans. are gonna go right? That is the tool and you're gonna use to start spinning up downstream commodity documentary prize clusters for bootstrapping record too. >>And the seed host that were, uh, talking about the kind cluster dingy actually doesn't have to exist after the bootstrap succeeds eso It's sort of like, uh, copies head from the seed host Toothy targets in AWS spins it up it then boots the the actual clusters and then it goes away too, because it's no longer necessary >>so that bootstrapping know that there's not really any requirements, Hardly on that, right. It just has to be able to reach aws hit that Hit that a p I to spin up those easy to instances because, as you just said, it's just a kubernetes in docker cluster on that piece. Drop note is just gonna get torn down after the set up finishes on. You no longer need that. Everything you're gonna do, you're gonna drive from the single pane of glass provided to you by your management cluster Doctor enterprise Continue cloud. Another thing that I think is sort of interesting their eyes that the convict is fairly minimal. Really? You just need to provide it like aws regions. Um, am I? And that's what is going to spin up that spending that matter faster. >>Right? There is a mammal file in the bootstrap directory itself, and all of the necessary parameters that you would fill in have default set. But you have the option then of going in and defining a different Am I different for a different region, for example? Oh, are different. Size of instance from AWS. >>One thing that people often ask about is the cluster footprint. And so that example you saw they were spitting up a three manager, um, managing cluster as mandatory, right? No single manager set up at all. We want high availability for doctrine Enterprise Container Cloud management. Like so again, just to make sure everyone sort of on board with the life cycle stage that we're at right now. That's the very first thing you're going to do to set up Dr Enterprise Container Cloud. You're going to do it. Hopefully exactly once. Right now, you've got your management cluster running, and they're gonna use that to spend up all your other work clusters Day today has has needed How do we just have a quick look at the questions and then lets take a look at spinning up some of those child clusters. >>Okay, e think they've actually been answered? >>Yeah, for the most part. One thing I'll point out that came up again in the Dail, helpfully pointed out earlier in surgery, pointed out again, is that if you want to try any of the stuff yourself, it's all of the dogs. And so have a look at the chat. There's a links to instructions, so step by step instructions to do each and every thing we're doing here today yourself. I really encourage you to do that. Taking this out for a drive on your own really helps internalizing communicate these ideas after the after launch pad today, Please give this stuff try on your machines. Okay, So at this point, like I said, we've got our management cluster. We're not gonna run workloads there that we're going to start creating child clusters. That's where all of our work and we're gonna go. That's what we're gonna learn how to do in our next video. Cue that up for us. >>I so love Shawn's voice. >>Wasn't that all day? >>Yeah, I watched him read the phone book. >>All right, here we go. Let's now that we have our management cluster set up, let's create a first child work cluster. >>Hello. In this demo, we will cover the deployment experience of creating a new child cluster the scaling of the cluster on how to update the cluster. When a new version is available, we begin the process by logging onto the you I as a normal user called Mary. Let's go through the navigation of the u I. So you can switch Project Mary only has access to development. Uh huh. Get a list of the available projects that you have access to. What clusters have been deployed at the moment there. Man. Yes, this H keys, Associate ID for Mary into her team on the cloud credentials that allow you to create or access the various clouds that you can deploy clusters to finally different releases that are available to us. We can switch from dark mode to light mode, depending on your preferences. Right. Let's now set up some ssh keys for Mary so she can access the notes and machines again. Very simply, had Mississippi key give it a name. We copy and paste our public key into the upload key block. Or we can upload the key if we have the file available on our machine. A very simple process. So to create a new cluster, we define the cluster ad management nodes and add worker nodes to the cluster. Yeah, again, very simply, we got the clusters tab we had to create cluster button. Give the cluster name. Yeah, Andi, select the provider. We only have access to AWS in this particular deployment, so we'll stick to AWS. What's like the region in this case? US West one released version five point seven is the current release Onda Attach. Mary's Key is necessary key. We can then check the rest of the settings, confirming the provider any kubernetes c r D a r i p address information. We can change this. Should we wish to? We'll leave it default for now and then what components of stack light? I would like to deploy into my custom for this. I'm enabling stack light on logging, and I consider the retention sizes attention times on. Even at this stage, add any custom alerts for the watchdogs. Consider email alerting which I will need my smart host. Details and authentication details. Andi Slack Alerts. Now I'm defining the cluster. All that's happened is the cluster's been defined. I now need to add machines to that cluster. I'll begin by clicking the create machine button within the cluster definition. Oh, select manager, Select the number of machines. Three is the minimum. Select the instant size that I'd like to use from AWS and very importantly, ensure correct. Use the correct Am I for the region. I convinced side on the route. Device size. There we go. My three machines are busy creating. I now need to add some workers to this cluster. So I go through the same process this time once again, just selecting worker. I'll just add to once again the am I is extremely important. Will fail if we don't pick the right. Am I for a Clinton machine? In this case and the deployment has started, we can go and check on the bold status are going back to the clusters screen on clicking on the little three dots on the right. We get the cluster info and the events, so the basic cluster info you'll see pending their listen. Cluster is still in the process of being built. We kick on, the events will get a list of actions that have been completed This part of the set up of the cluster. So you can see here. We've created the VPC. We've created the sub nets on. We've created the Internet Gateway. It's unnecessary made of us. And we have no warnings of the stage. Okay, this will then run for a while. We have one minute past. We can click through. We can check the status of the machine balls as individuals so we can check the machine info, details of the machines that we've assigned mhm and see any events pertaining to the machine areas like this one on normal. Yeah. Just last. The community's components are waiting for the machines to start. Go back to customers. Okay, right. Because we're moving ahead now. We can see we have it in progress. Five minutes in new Matt Gateway. And at this stage, the machines have been built on assigned. I pick up the U S. Yeah, yeah, yeah. There we go. Machine has been created. See the event detail and the AWS. I'd for that machine. No speeding things up a little bit this whole process and to end takes about fifteen minutes. Run the clock forward, you'll notice is the machines continue to bold the in progress. We'll go from in progress to ready. A soon as we got ready on all three machines, the managers on both workers way could go on and we could see that now we reached the point where the cluster itself is being configured mhm and then we go. Cluster has been deployed. So once the classes deployed, we can now never get around. Our environment are looking into configure cluster. We could modify their cluster. We could get the end points for alert Alert Manager See here the griffon occupying and Prometheus are still building in the background but the cluster is available on You would be able to put workloads on it at this stage to download the cube conflict so that I can put workloads on it. It's again the three little dots in the right for that particular cluster. If the download cube conflict give it my password, I now have the Q conflict file necessary so that I can access that cluster. All right, Now that the build is fully completed, we can check out cluster info on. We can see that all the satellite components have been built. All the storage is there, and we have access to the CPU. I. So if we click into the cluster, we can access the UCP dashboard, click the signing with the clock button to use the SSO. We give Mary's possible to use the name once again. Thing is an unlicensed cluster way could license at this point. Or just skip it on. Do we have the UCP dashboard? You could see that has been up for a little while. We have some data on the dashboard going back to the console. We can now go to the griffon. A data just been automatically pre configured for us. We can switch and utilized a number of different dashboards that have already been instrumented within the cluster. So, for example, communities cluster information, the name spaces, deployments, nodes. Um, so we look at nodes. If we could get a view of the resource is utilization of Mrs Custer is very little running in it. Yeah, a general dashboard of Cuba Navies cluster. What If this is configurable, you can modify these for your own needs, or add your own dashboards on de scoped to the cluster. So it is available to all users who have access to this specific cluster. All right to scale the cluster on to add a No. This is simple. Is the process of adding a mode to the cluster, assuming we've done that in the first place. So we go to the cluster, go into the details for the cluster we select, create machine. Once again, we need to be ensure that we put the correct am I in and any other functions we like. You can create different sized machines so it could be a larger node. Could be bigger group disks and you'll see that worker has been added in the provisioning state. On shortly, we will see the detail off that worker as a complete to remove a note from a cluster. Once again, we're going to the cluster. We select the node we would like to remove. Okay, I just hit delete On that note. Worker nodes will be removed from the cluster using according and drawing method to ensure that your workloads are not affected. Updating a cluster. When an update is available in the menu for that particular cluster, the update button will become available. And it's a simple as clicking the button validating which release you would like to update to this case. This available releases five point seven point one give you I'm kicking the update back in the background. We will coordinate. Drain each node slowly, go through the process of updating it. Andi update will complete depending on what the update is as quickly as possible. Who we go. The notes being rebuilt in this case impacted the manager node. So one of the manager nodes is in the process of being rebuilt. In fact, to in this case, one has completed already. Yeah, and in a few minutes, we'll see that the upgrade has been completed. There we go. Great. Done. If you work loads of both using proper cloud native community standards, there will be no impact. >>All right, there. We haven't. We got our first workload cluster spun up and managed by Dr Enterprise Container Cloud. So I I loved Shawn's classic warning there. When you're spinning up an actual doctor enterprise deployment, you see little errors and warnings popping up. Just don't touch it. Just leave it alone and let Dr Enterprises self healing properties take care of all those very transient temporary glitches, resolve themselves and leave you with a functioning workload cluster within victims. >>And now, if you think about it that that video was not very long at all. And that's how long it would take you if someone came into you and said, Hey, can you spend up a kubernetes cluster for development development A. Over here, um, it literally would take you a few minutes to thio Accomplish that. And that was with a W s. Obviously, which is sort of, ah, transient resource in the cloud. But you could do exactly the same thing with resource is on Prem or resource is, um physical resource is and will be going through that later in the process. >>Yeah, absolutely one thing that is present in that demo, but that I like to highlight a little bit more because it just kind of glides by Is this notion of, ah, cluster release? So when Sean was creating that cluster, and also when when he was upgrading that cluster, he had to choose a release. What does that didn't really explain? What does that mean? Well, in Dr Enterprise Container Cloud, we have released numbers that capture the entire staff of container ization tools that will be deploying to that workload costume. So that's your version of kubernetes sed cor DNs calico. Doctor Engineer. All the different bits and pieces that not only work independently but are validated toe work together as a staff appropriate for production, humanities, adopted enterprise environments. >>Yep. From the bottom of the stack to the top, we actually test it for scale. Test it for CVS, test it for all of the various things that would, you know, result in issues with you running the application services. And I've got to tell you from having, you know, managed kubernetes deployments and things like that that if you're the one doing it yourself, it can get rather messy. Eso This makes it easy. >>Bruce, you were staying a second ago. They I'll take you at least fifteen minutes to install your release. Custer. Well, sure, but what would all the other bits and pieces you need toe? Not just It's not just about pressing the button to install it, right? It's making the right decision. About what components work? Well, our best tested toe be successful working together has a staff? Absolutely. We this release mechanism and Dr Enterprise Container Cloud. Let's just kind of package up that expert knowledge and make it available in a really straightforward, fashionable species. Uh, pre Confederate release numbers and Bruce is you're pointing out earlier. He's got delivered to us is updates kind of transparent period. When when? When Sean wanted toe update that cluster, he created little update. Custer Button appeared when an update was available. All you gotta do is click. It tells you what Here's your new stack of communities components. It goes ahead. And the straps those components for you? >>Yeah, it actually even displays at the top of the screen. Ah, little header That says you've got an update available. Do you want me to apply? It s o >>Absolutely. Another couple of cool things. I think that are easy to miss in that demo was I really like the on board Bafana that comes along with this stack. So we've been Prometheus Metrics and Dr Enterprise for years and years now. They're very high level. Maybe in in previous versions of Dr Enterprise having those detailed dashboards that Ravana provides, I think that's a great value out there. People always wanted to be ableto zoom in a little bit on that, uh, on those cluster metrics, you're gonna provides them out of the box for us. Yeah, >>that was Ah, really, uh, you know, the joining of the Miranda's and Dr teams together actually spawned us to be able to take the best of what Morantes had in the open stack environment for monitoring and logging and alerting and to do that integration in in a very short period of time so that now we've got it straight across the board for both the kubernetes world and the open stack world. Using the same tool sets >>warm. One other thing I wanna point out about that demo that I think there was some questions about our last go around was that demo was all about creating a managed workplace cluster. So the doctor enterprise Container Cloud managers were using those aws credentials provisioned it toe actually create new e c two instances installed Docker engine stalled. Doctor Enterprise. Remember all that stuff on top of those fresh new VM created and managed by Dr Enterprise contain the cloud. Nothing unique about that. AWS deployments do that on open staff doing on Parramatta stuff as well. Um, there's another flavor here, though in a way to do this for all of our long time doctor Enterprise customers that have been running Doctor Enterprise for years and years. Now, if you got existing UCP points existing doctor enterprise deployments, you plug those in to Dr Enterprise Container Cloud, uh, and use darker enterprise between the cloud to manage those pre existing Oh, working clusters. You don't always have to be strapping straight from Dr Enterprises. Plug in external clusters is bad. >>Yep, the the Cube config elements of the UCP environment. The bundling capability actually gives us a very straightforward methodology. And there's instructions on our website for exactly how thio, uh, bring in import and you see p cluster. Um so it it makes very convenient for our existing customers to take advantage of this new release. >>Absolutely cool. More thoughts on this wonders if we jump onto the next video. >>I think we should move press on >>time marches on here. So let's Let's carry on. So just to recap where we are right now, first video, we create a management cluster. That's what we're gonna use to create All our downstream were closed clusters, which is what we did in this video. Let's maybe the simplest architectures, because that's doing everything in one region on AWS pretty common use case because we want to be able to spin up workload clusters across many regions. And so to do that, we're gonna add a third layer in between the management and work cluster layers. That's gonna be our regional cluster managers. So this is gonna be, uh, our regional management cluster that exists per region that we're going to manage those regional managers will be than the ones responsible for spending part clusters across all these different regions. Let's see it in action in our next video. >>Hello. In this demo, we will cover the deployment of additional regional management. Cluster will include a brief architectural overview, how to set up the management environment, prepare for the deployment deployment overview, and then just to prove it, to play a regional child cluster. So looking at the overall architecture, the management cluster provides all the core functionality, including identity management, authentication, inventory and release version. ING Regional Cluster provides the specific architecture provider in this case, AWS on the L C M components on the d you speak cluster for child cluster is the cluster or clusters being deployed and managed? Okay, so why do you need original cluster? Different platform architectures, for example AWS open stack, even bare metal to simplify connectivity across multiple regions handle complexities like VPNs or one way connectivity through firewalls, but also help clarify availability zones. Yeah. Here we have a view of the regional cluster and how it connects to the management cluster on their components, including items like the LCN cluster Manager. We also machine manager. We're hell Mandel are managed as well as the actual provider logic. Okay, we'll begin by logging on Is the default administrative user writer. Okay, once we're in there, we'll have a look at the available clusters making sure we switch to the default project which contains the administration clusters. Here we can see the cars management cluster, which is the master controller. When you see it only has three nodes, three managers, no workers. Okay, if we look at another regional cluster, similar to what we're going to deploy now. Also only has three managers once again, no workers. But as a comparison is a child cluster. This one has three managers, but also has additional workers associate it to the cluster. Yeah, all right, we need to connect. Tell bootstrap note, preferably the same note that used to create the original management plaster. It's just on AWS, but I still want to machine Mhm. All right, A few things we have to do to make sure the environment is ready. First thing we're gonna pseudo into route. I mean, we'll go into our releases folder where we have the car's boot strap on. This was the original bootstrap used to build the original management cluster. We're going to double check to make sure our cube con figures there It's again. The one created after the original customers created just double check. That cute conflict is the correct one. Does point to the management cluster. We're just checking to make sure that we can reach the images that everything's working, condone, load our images waken access to a swell. Yeah, Next, we're gonna edit the machine definitions what we're doing here is ensuring that for this cluster we have the right machine definitions, including items like the am I So that's found under the templates AWS directory. We don't need to edit anything else here, but we could change items like the size of the machines attempts we want to use but the key items to ensure where changed the am I reference for the junta image is the one for the region in this case aws region of re utilizing. This was an open stack deployment. We have to make sure we're pointing in the correct open stack images. Yeah, yeah. Okay. Sit the correct Am I save the file? Yeah. We need to get up credentials again. When we originally created the bootstrap cluster, we got credentials made of the U. S. If we hadn't done this, we would need to go through the u A. W s set up. So we just exporting AWS access key and I d. What's important is Kaz aws enabled equals. True. Now we're sitting the region for the new regional cluster. In this case, it's Frankfurt on exporting our Q conflict that we want to use for the management cluster when we looked at earlier. Yeah, now we're exporting that. Want to call? The cluster region is Frankfurt's Socrates Frankfurt yet trying to use something descriptive? It's easy to identify. Yeah, and then after this, we'll just run the bootstrap script, which will complete the deployment for us. Bootstrap of the regional cluster is quite a bit quicker than the initial management clusters. There are fewer components to be deployed, but to make it watchable, we've spent it up. So we're preparing our bootstrap cluster on the local bootstrap node. Almost ready on. We started preparing the instances at us and waiting for the past, you know, to get started. Please the best your node, onda. We're also starting to build the actual management machines they're now provisioning on. We've reached the point where they're actually starting to deploy Dr Enterprise, he says. Probably the longest face we'll see in a second that all the nodes will go from the player deployed. Prepare, prepare Mhm. We'll see. Their status changes updates. It was the first word ready. Second, just applying second. Grady, both my time away from home control that's become ready. Removing cluster the management cluster from the bootstrap instance into the new cluster running a data for us? Yeah, almost a on. Now we're playing Stockland. Thanks. Whichever is done on Done. Now we'll build a child cluster in the new region very, very quickly. Find the cluster will pick our new credential have shown up. We'll just call it Frankfurt for simplicity. A key on customers to find. That's the machine. That cluster stop with three manages set the correct Am I for the region? Yeah, Same to add workers. There we go. That's the building. Yeah. Total bill of time. Should be about fifteen minutes. Concedes in progress. Can we expect this up a little bit? Check the events. We've created all the dependencies, machine instances, machines. A boat? Yeah. Shortly. We should have a working caster in the Frankfurt region. Now almost a one note is ready from management. Two in progress. On we're done. Trust us up and running. >>Excellent. There we have it. We've got our three layered doctor enterprise container cloud structure in place now with our management cluster in which we scrap everything else. Our regional clusters which manage individual aws regions and child clusters sitting over depends. >>Yeah, you can. You know you can actually see in the hierarchy the advantages that that presents for folks who have multiple locations where they'd like a geographic locations where they'd like to distribute their clusters so that you can access them or readily co resident with your development teams. Um and, uh, one of the other things I think that's really unique about it is that we provide that same operational support system capability throughout. So you've got stack light monitoring the stack light that's monitoring the stack light down to the actual child clusters that they have >>all through that single pane of glass that shows you all your different clusters, whether their workload cluster like what the child clusters or usual clusters from managing different regions. Cool. Alright, well, time marches on your folks. We've only got a few minutes left and I got one more video in our last video for the session. We're gonna walk through standing up a child cluster on bare metal. So so far, everything we've seen so far has been aws focus. Just because it's kind of easy to make that was on AWS. We don't want to leave you with the impression that that's all we do, we're covering AWS bare metal and open step deployments as well documented Craftsman Cloud. Let's see it in action with a bare metal child cluster. >>We are on the home stretch, >>right. >>Hello. This demo will cover the process of defining bare metal hosts and then review the steps of defining and deploying a bare metal based doctor enterprise cluster. Yeah, so why bare metal? Firstly, it eliminates hyper visor overhead with performance boost of up to thirty percent provides direct access to GP use, prioritize for high performance wear clothes like machine learning and AI, and support high performance workouts like network functions, virtualization. It also provides a focus on on Prem workloads, simplifying and ensuring we don't need to create the complexity of adding another hyper visor layer in between. So continuing on the theme Why communities and bare metal again Hyper visor overhead. Well, no virtualization overhead. Direct access to hardware items like F p g A s G p, us. We can be much more specific about resource is required on the nodes. No need to cater for additional overhead. We can handle utilization in the scheduling better Onda. We increase the performance and simplicity of the entire environment as we don't need another virtualization layer. Yeah, In this section will define the BM hosts will create a new project. Will add the bare metal hosts, including the host name. I put my credentials. I pay my address, Mac address on, then provide a machine type label to determine what type of machine it is. Related use. Okay, let's get started Certain Blufgan was the operator thing. We'll go and we'll create a project for our machines to be a member off. Helps with scoping for later on for security. I begin the process of adding machines to that project. Yeah. Yeah. So the first thing we had to be in post many of the machine a name. Anything you want? Yeah, in this case by mental zero one. Provide the IAP My user name. Type my password? Yeah. On the Mac address for the active, my interface with boot interface and then the i p m i P address. Yeah, these machines. We have the time storage worker manager. He's a manager. We're gonna add a number of other machines on will speed this up just so you could see what the process. Looks like in the future, better discovery will be added to the product. Okay, Okay. Getting back there. We haven't Are Six machines have been added. Are busy being inspected, being added to the system. Let's have a look at the details of a single note. Mhm. We can see information on the set up of the node. Its capabilities? Yeah. As well as the inventory information about that particular machine. Okay, it's going to create the cluster. Mhm. Okay, so we're going to deploy a bare metal child cluster. The process we're going to go through is pretty much the same as any other child cluster. So credit custom. We'll give it a name. Thank you. But he thought were selecting bare metal on the region. We're going to select the version we want to apply on. We're going to add this search keys. If we hope we're going to give the load. Balancer host I p that we'd like to use out of the dress range update the address range that we want to use for the cluster. Check that the sea idea blocks for the communities and tunnels are what we want them to be. Enable disabled stack light and said the stack light settings to find the cluster. And then, as for any other machine, we need to add machines to the cluster. Here we're focused on building communities clusters. So we're gonna put the count of machines. You want managers? We're gonna pick the label type manager on create three machines. Is a manager for the Cuban a disgusting? Yeah, they were having workers to the same. It's a process. Just making sure that the worker label host like you are so yes, on Duin wait for the machines to deploy. Let's go through the process of putting the operating system on the notes, validating that operating system. Deploying Docker enterprise on making sure that the cluster is up and running ready to go. Okay, let's review the bold events. We can see the machine info now populated with more information about the specifics of things like storage. Yeah, of course. Details of a cluster, etcetera. Yeah, Yeah. Okay. Well, now watch the machines go through the various stages from prepared to deploy on what's the cluster build, and that brings us to the end of this particular do my as you can see the process is identical to that of building a normal child cluster we got our complaint is complete. >>Here we have a child cluster on bare metal for folks that wanted to play the stuff on Prem. >>It's ah been an interesting journey taken from the mothership as we started out building ah management cluster and then populating it with a child cluster and then finally creating a regional cluster to spread the geographically the management of our clusters and finally to provide a platform for supporting, you know, ai needs and and big Data needs, uh, you know, thank goodness we're now able to put things like Hadoop on, uh, bare metal thio in containers were pretty exciting. >>Yeah, absolutely. So with this Doctor Enterprise container cloud platform. Hopefully this commoditized scooping clusters, doctor enterprise clusters that could be spun up and use quickly taking provisioning times. You know, from however many months to get new clusters spun up for our teams. Two minutes, right. We saw those clusters gets better. Just a couple of minutes. Excellent. All right, well, thank you, everyone, for joining us for our demo session for Dr Enterprise Container Cloud. Of course, there's many many more things to discuss about this and all of Miranda's products. If you'd like to learn more, if you'd like to get your hands dirty with all of this content, police see us a training don Miranda's dot com, where we can offer you workshops and a number of different formats on our entire line of products and hands on interactive fashion. Thanks, everyone. Enjoy the rest of the launchpad of that >>thank you all enjoy.

>>from the Cube Studios in Palo Alto and Boston. It's the Cube covering empowering the autonomous enterprise brought to you by >>Oracle Consulting. Everybody, this is Dave Vellante. We've been covering the transformation of Oracle consulting and really, it's rebirth. And I'm here with Chris Fox, who's the group vice president for Enterprise Cloud Architects and chief technologist for the North America Tech Cloud at Oracle. Chris, thanks so much for coming on the Cube. >>Thanks too great to be here, >>So I love this title. You know, years ago, this thing is a cloud architect. Certainly there were chief technologist, but so you really that's those are your peeps, Is that right? >>That's right. That's right. That's really in my team. And I That's all we dio. So our focus is really helping our customers take this journey from when they were on premise. You really transforming with cloud? And when we think about Cloud, really, for us, it's a combination. It's it's our hybrid cloud, which happens to be on premise. And then, of course, the true public cloud, like most people, are familiar with so very exciting journey and frankly, of seeing just a lot of success for our customers. You know what I think we're seeing at Oracle, though? Because we're so connected with SAS. And then we're also connected with the traditional applications that have run the business for years. The legacy applications that have been, you know, servicing us for 20 years and then the cloud native developers. So with my team and I are constantly focused on now is things like digital transformation and really wiring up all three of these across. So if we think of, like a customer outcome like I want to have a package delivered to me from a retailer that actual process flow could touch a brand new cognitive site of e commerce it could touch essentially maybe a traditional application that used to be on Prem that's now in the cloud. And then it might even use new SAS application, maybe for maybe Herman process or delivery vehicle and scheduling. So when my team does, we actually connect all three. So what? I was mentioned, too. In my team and all of our customers, we have field service, all three of those constituents. And if you think about process flows, so I take a cloud. Native developer we help them become efficient. We take the person use to run in a traditional application, and we help them become more efficient. And then we have the SAS applications, which are now rolling out new features on a quarterly basis and the whole new delivery model. But the real key is connecting all three of these into your business process flow. That makes the customers life much more vision. >>So I want to get into this cloud conversations that you guys are using this term last mover advantage. I asked you last I was being last, You know, an advantage. But let me start there. >>People always say, You know, of course, we want to get out of the data center. We're going zero data center and how we say, Well, how are you going to handle that back office stuff, right? The stuff that's really big Frankie, um, doesn't handle just, you know, instances dying or things going away too easily. It needs predictable performance in the scale. It absolutely needs security. And ultimately, you know, a lot of these applications truly have relied on Oracle database. The Oracle database has its own specific characteristics that it means to run really well. So we actually looked at the cloud and we said, Let's take the first generation clouds but you're doing great But let's add the features that specifically a lot of times the Oracle workload needed in order to run very well and in a cost effective manner. So that's what we mean when we say last mover advantage, We said, Let's take the best of the clouds that are out there today. Let's look at the workloads that, frankly, Oracle runs and has been running for years. What are customers needed? And then let's build those features right into this, uh, this next version of the cloud we service the Enterprise. So our goal, honestly, which is interesting is even that first discussion we had about cloud, native and legacy applications and also the new SAS applications. We built a cloud that handles all three use cases at scale resiliently in very secure manner, and I don't know of any other cloud that's handling those three use cases all in. We'll call it the same pendency process. Oracle >>Mike witnesses. Why was it important for Oracle? And is it important for Oracle on its customers that have to participate in IAS and Pass and SAS. Why not just the last two layers of that? Um What does that mean from a strategic advantage standpoint? What does that do for >>you? Yeah, great question. So the number one reason why we needed to have all three was that we have so many customers to today are in a data center. They're running a lot of our workloads on premise, and they absolutely are trying to find a better way to deliver lower cost services to their customers. And so we couldn't just say, Let's just everyone needs to just become net new. Everyone just needs to ditch the old and go just a brand new alone. Too hard, too expensive at times. So we said, You know, let's kill us customers the ultimate amount of choice. So let's even go back against that developer conversation and SAS Um, if you didn't have eyes, we couldn't help customers achieve a zero data center strategy with their traditional applications will call it PeopleSoft or JD Edwards, Revisit Suite or even. There's some massive applications that are running on the Oracle cloud right now that are custom applications built on the Oracle database. What they want is, they said, Give me the lowest. Possibly a predictable performance. I as I'll run my app steer on this number two. Give me a platform service for database because, frankly, I don't really want to run your database. Like with all the manual effort. I want someone automate, patching scale up and down and all these types of features like should have given us. And then number three. You know, I do want SAS over time. So we spend a lot of time with our customers really saying, How do I take this traditional application, Run it on eyes and has and the number two Let's modernize it at scale. Maybe I want to start peeling off functionality and running in the cloud Native services right alongside, right? That's something again that we're doing at scale. And other people are having a hard time running these traditional workloads on Prem in the cloud. The second part is they say, you know, I've got this legacy traditional your api been servicing we well, or maybe a supply chain system ultimately want to get out of this. How do I get to SAS? You say Okay, here's the way to do this. First bring into the cloud running on IAS and pass and then selectively, I call it cloud slicing. Take a piece of functionality and put it into SAS. We're helping customers move to the cloud at scale. We're helping them do it at their rate, with whatever level of change they want. And when they're ready for SAS, we're ready for them. >>How does autonomous fit into this whole architecture Wait for that? That that description? I mean, it's a it's nuanced, but it's important. I'm sure you haven't discussed this conversation with a lot of cloud architects and chief technologist. They want to know this stuff. They want to know how it works. Um, you know, we will talk about what the business impact is, but but yeah, it's not about autonomous and where that fits. >>So the autonomous database, what we've done is really big. And look at all the runtime operations of an Oracle database. So tuning, patching, sparing all these different features and what we've done is taken the best of the Oracle database the best of something called Exit Data right, which we run in the cloud which really helps a lot of our customers. And then we wrapped it with a set of automation and security tools to help it. Really, uh, managing self tune itself. Patch itself scale up and down, independent between compute and storage. So why that's important, though, is that it? Really? Our goal is to help people run the Oracle databases they have for years, but with far less effort and then even not letting far less effort. Hopefully, you know a machine. Last man out of the equation we always talk about is your man plus machine is greater than man alone, so being assisted by, um, artificial intelligence and machine learning to perform those database operations, we should provide a better service to our customers. Far less paths are hoping goal is that people have been running Oracle databases, you know, How can we help them do it with far less effort and maybe spend more time on what the data can do for the organization? Right? Improve customer experience at Centra versus maybe like Hana Way. How do I spin up the table? It >>so talk about the business impact. So you go into customers, you talk to the the cloud Architects, the chief technologist. You pass that test now, you got to deliver the business impact. We're is Oracle Consulting fit with regard to that? And maybe you could talk about that where you were You guys want to take this thing? >>Yeah, absolutely. I mean, so you know, the cloud is a great set of technologies, but where Oracle Consulting is really helping us deliver is in, um, you know, one of the things I think that's been fantastic working with the Oracle consulting team is that, you know, Cloud is new for a lot of customers who've been running these environments for a number of years. There's always some fear and a little bit of trepidation saying, How do I learn this new cloud of the workloads? We're talking about David, like tier zero, tier one, tier two and all the way up to Dev and Test and, er, um, Oracle consulting. This really couple things in particular, Number one, they start with the end in mind, and number two that they start to do is they really help implement these systems. And, you know, there's a lot of different assurances that we have that we're going to get it done on time and better be under budget because ultimately, you know, again, that's a something is really paramount for us and then the third part of it. But sometimes a run book, right? We actually don't want to just live in our customer's environments. We want to help them understand how to run this new system. So training and change management. A lot of times, Oracle Consulting is helping with run books. We usually well, after doing it the first time. We'll sit back and say, Let the customer do in the next few times and essentially help them through the process. And our goal at that point is to leave only if the customer wants us to. But ultimately our goal is to implemented, get it to go live on time and then help the customer learn this journey to the cloud and without them. Frankly, uh, you know, I think these systems were sometimes too complex and difficult to do on your own. Maybe the first time, especially cause I could say they're closing the books. They might be running your entire supply chain. They run your entire HR system, whatever they might be, uh, too important, leading a chance. So they really help us with helping a customer become live and become very confident. Skilled. They could do themselves >>of the conversation. We have to leave it right there. But thanks so much for coming on the Cube and sharing your insights. Great stuff. >>Absolutely. Thanks for having me on. >>All right. You're welcome. And thank you for watching everybody. This is Dave Volante for the Cube. We are covering the oracle of North American Consulting. Transformation. And it's rebirth in this digital event. Keep it right there. We'll be right back.

>> Narrator: From theCUBE studios in Palo Alto in Boston, it's theCUBE! Covering empowering the autonomous enterprise. Brought to you by ORACLE Consulting. >> Back to theCUBE everybody, this is Dave Vellante. We've been covering the transformation of ORACLE Consulting, and really it's rebirth, and I'm here with Chris Fox, who's the Group Vice President for Enterprise Cloud Architects and Chief Technologist for the North America Tech Cloud at ORACLE. Chris, thanks so much for coming on theCUBE. >> Thanks Dave, glad to be here. >> So, I love this title. I mean, years ago, there was no such thing as a cloud architect. Certainly there were chief technologists, but so, you are really, those are your peeps, is that right? >> That's right, that's right. That's really my team and I, that's all we do. So, our focus is really helping our customers take this journey from when they were on-premise to really transforming with cloud, and when we think about cloud, really, for us, it's a combination. It's our hybrid cloud, which happens to be on-premise, and then, of course, the true public cloud, like most people are familiar with. So, very exciting journey and, frankly, I've seen just a lot of success for our customers. You know, Dave, what I think we're seeing at ORACLE though, because we're so connected with SaaS, and then we're also connected with the traditional applications that have run the business for years, the legacy applications that have been, you know, servicing us for 20 years, and then the cloud needed developers. So, what my team and I are constantly focused on now is things like digital transformation and really wiring up all three of these across. So, if we think of, like, a customer outcome like I want to have a package delivered to me from a retailer, that actual process flow could touch a brand new cloud-native site from eCommerce, it could touch, essentially, maybe a traditional application that used to be on-prem that's now on the cloud, and then it might even use a new SaaS application, maybe, for maybe a permit process or delivery vehicle and scheduling. So, what my team does, we actually connect all three. So, what I always mention to my team and all of our customers, we have to be able to service all three of those constituents and really think about process flows. So, I take the cloud-native developer, we help them become efficient. We take the person who's been running that traditional application and we help them become more efficient, and then we have the SaaS applications, which are now rolling out new features on a quarterly basis and it's a whole new delivery model, but the real key is connecting all three of these into a business process flow that makes the customer's life much more efficient. People always say, you know, Chris, we want to get out of the data center, we're going zero data center, and I always say, well, how are you going to handle that back office stuff? Right? The stuff that's really big, it's cranky, doesn't handle just, you know, instances dying or things going away too easily. It needs predictable performance, it needs scale, it absolutely needs security, and ultimately, you know, a lot of these applications truly have relied on an ORACLE database. The ORACLE database has its own specific characteristics that it needs to run really well. So, we actually looked at the cloud and we said, let's take the first generation clouds, which are doing great, but let's add the features that specifically, a lot of times, the ORACLE workload needed in order to run very well and in a cost effective manner. So, that's what we mean when we say last mover advantage. We said, let's take the best of the clouds that are out there today, let's look at the workloads that, frankly, ORACLE runs and has been running for years, what our customers needed, and then let's build those features right into this next version of the cloud which can service the enterprise. So, our goal, honestly, which is interesting, is even that first discussion we had about cloud-native and legacy applications and also the new SaaS applications, we built a cloud that handles all three use cases at scale, resiliently, in a very secure manner, and I don't know of any other cloud that's handling those three use cases all in, we'll call it the same tendency for us at ORACLE. >> My question is why was it important for ORACLE, and is it important for ORACLE and its customers, to participate in IaaS and PaaS and SaaS? Why not just the last two layers of that? What does that give you from a strategic advantage standpoint and what does that do for your customer? >> Yeah, great question. So, the number one reason why we needed to have all three was that we have so many customers who, today, are in a data center. They're running a lot of our workloads on-premise and they absolutely are trying to find a better way to deliver lower-cost services to their customers and so we couldn't just say, let's just, everyone needs to just become net new, everyone just needs to ditch the old and go just to brand-new alone. Too hard, too expensive, at times. So we said, you know, let's give us customers the ultimate amount of choice. So, let's even go back again to that developer conversation in SaaS. If you didn't have IaaS, we couldn't help customers achieve a zero data center strategy with their traditional application, we'll call it PeopleSoft or JD Edwards or E-Business Suite or even, there's some massive applications that are running on the ORACLE cloud right now that are custom applications built on the ORACLE database. What they want is they said, give me the lowest cost but yet predictable performance IaaS. I'll run my apps tier on this. Number two, give me a platform service for database, 'cause frankly, I don't really want to run your database, like, with all the menial effort. I want someone to automate patching, scale up and down, and all these types of features like the cloud should have given us. And then number three, I do want SaaS over time. So, we spend a lot of time with our customers really saying, how do I take this traditional application, run it on IaaS and PaaS, and then number two, let's modernize it at scale. Maybe I want to start peeling off functionality and running them as cloud-native services right alongside, right? That's something, again, that we're doing at scale and other people are having a hard time running these traditional workloads on-prem in the cloud. The second part is they say, you know, I've got this legacy traditional ERP. It's been servicing me well, or maybe a supply chain system. Ultimately I want to get out of this. How do I get to SaaS? And we say, okay, here's the way to do this. First, bring it to the cloud, run it on IaaS and PaaS, and then selectively, I call it cloud slicing, take a piece of functionality and put it into SaaS. We're helping customers move to the cloud at scale. We're helping 'em do it at their rate, with whatever level of change they want, and when they are ready for SaaS, we're ready for them. >> And how does autonomous fit into this whole architecture? Thank you, by the way, for that description. I mean, it's nuanced but it's important. I'm sure you're having this conversation with a lot of cloud architects and chief technologists. They want to know this stuff, and they want to know how it works. And then, obviously, we'll talk about what the business impact is, but talk about autonomous and where that fit. >> So, the autonomous database, what we've done is really taken a look at all the runtime operations of an ORACLE database, so tuning, patching, securing, all these different features, and what we've done is taken the best of the ORACLE database, the best of something called Exadata, right, which we run on the cloud, which really helps a lot of our customers, and then we've wrapped it with a set of automation and security tools to help it really manage itself, tune itself, patch itself, scale up and down independent between computant storage. So, why that's important though is that it really, our goal is to help people run the ORACLE database as they have for years but with far less effort, and then even not only far less effort, hopefully, you know, a machine plus man, kind of the equation we always talk about is man plus machine is greater than man alone. So, being assisted by artificial intelligence and machine learning to perform those database operations, we should provide a better service to our customers with far less cost. Our hope and goal is that people have been running ORACLE databases. How can we help them do it with far less effort, and maybe spend more time on what the data can do for the organization, right? Improve customer experience, etc. Versus maybe, like, how do I spin up (breaks up). >> So, let's talk about the business impact. So, you go into customers, you talk to the cloud architects, the chief technologists, you pass that test. Now you got to deliver the business impact. Where does ORACLE Consulting fit with regard to that? And maybe you could talk about where you guys want to take this thing. >> Yeah, absolutely. I mean, the cloud is great set of technologies, but where ORACLE Consulting is really helping us deliver is in the outcome. One of the things, I think, that's been fantastic working with the ORACLE Consulting team is that, you know, cloud is new. For a lot of customers who've been running these environments for a number of years, there's always some fear and a little bit of trepidation saying, how do I learn this new cloud? I mean, the workloads we're talking about, Dave, are like tier zero, tier one, tier two and, you know, all the way up to DEV and TEST and DR. ORACLE Consulting does really couple of things in particular. Number one, they start with the end in mind, and number two that they start to do, is they really help implement these systems and there's a lot of different assurances that we have that we're going to get it done on time and better be under budget, 'cause ultimately, again, that's something that's really paramount for us. And then the third part of it, a lot of times it's runbooks, right? We actually don't want to just live in our customers' environments. We want to help them understand how to run this new system, so in training and change management, a lot of times ORACLE Consulting is helping with runbooks. We usually will, after doing it the first time, we'll sit back and let the customer do it the next few times and essentially help them through the process, and our goal at that point is to leave. Only if the customer wants us to, but ultimately our goal is to implement it, get it to go live on time, and then help the customer learn this journey to the cloud. And without them, frankly, I think these systems are sometimes too complex and difficult to do on your own maybe the first time, especially 'cause like I say, they're closing the books. They might be running your entire supply chain. They run your entire HR system or whatever they might be. Too important to leave to chance. So, they really help us with helping the customer become live and become very confident and skilled 'cause they can do it themselves. >> Well Chris, we've covered the gamut. Loved the conversation. We'll have to leave it right there, but thanks so much for coming on theCUBE and sharing your insights. Great stuff. >> Absolutely, thanks Dave, and thanks for having me on. >> All right, you're welcome, and thank you for watching everybody. This is Dave Vellante for theCUBE. We are covering the ORACLE of North America Consulting transformation and its rebirth in this digital event. Keep it right there, we'll be right back.

>> Narrator: From theCUBE studios in Palo Alto in Boston, it's theCUBE! Covering empowering the autonomous enterprise. Brought to you by ORACLE Consulting. >> Back to theCUBE everybody, this is Dave Vellante. We've been covering the transformation of ORACLE Consulting, and really it's rebirth, and I'm here with Chris Fox, who's the Group Vice President for Enterprise Cloud Architects and Chief Technologist for the North America Tech Cloud at ORACLE. Chris, thanks so much for coming on theCUBE. >> Thanks Dave, glad to be here. >> So, I love this title. I mean, years ago, there was no such thing as a cloud architect. Certainly there were chief technologists, but so, you are really, those are your peeps, is that right? >> That's right, that's right. That's really my team and I, that's all we do. So, our focus is really helping our customers take this journey from when they were on-premise to really transforming with cloud, and when we think about cloud, really, for us, it's a combination. It's our hybrid cloud, which happens to be on-premise, and then, of course, the true public cloud, like most people are familiar with. So, very exciting journey and, frankly, I've seen just a lot of success for our customers. You know, Dave, what I think we're seeing at ORACLE though, because we're so connected with SaaS, and then we're also connected with the traditional applications that have run the business for years, the legacy applications that have been, you know, servicing us for 20 years, and then the cloud needed developers. So, what my team and I are constantly focused on now is things like digital transformation and really wiring up all three of these across. So, if we think of, like, a customer outcome like I want to have a package delivered to me from a retailer, that actual process flow could touch a brand new cloud-native site from eCommerce, it could touch, essentially, maybe a traditional application that used to be on-prem that's now on the cloud, and then it might even use a new SaaS application, maybe, for maybe a permit process or delivery vehicle and scheduling. So, what my team does, we actually connect all three. So, what I always mention to my team and all of our customers, we have to be able to service all three of those constituents and really think about process flows. So, I take the cloud-native developer, we help them become efficient. We take the person who's been running that traditional application and we help them become more efficient, and then we have the SaaS applications, which are now rolling out new features on a quarterly basis and it's a whole new delivery model, but the real key is connecting all three of these into a business process flow that makes the customer's life much more efficient. People always say, you know, Chris, we want to get out of the data center, we're going zero data center, and I always say, well, how are you going to handle that back office stuff? Right? The stuff that's really big, it's cranky, doesn't handle just, you know, instances dying or things going away too easily. It needs predictable performance, it needs scale, it absolutely needs security, and ultimately, you know, a lot of these applications truly have relied on an ORACLE database. The ORACLE database has its own specific characteristics that it needs to run really well. So, we actually looked at the cloud and we said, let's take the first generation clouds, which are doing great, but let's add the features that specifically, a lot of times, the ORACLE workload needed in order to run very well and in a cost effective manner. So, that's what we mean when we say last mover advantage. We said, let's take the best of the clouds that are out there today, let's look at the workloads that, frankly, ORACLE runs and has been running for years, what our customers needed, and then let's build those features right into this next version of the cloud which can service the enterprise. So, our goal, honestly, which is interesting, is even that first discussion we had about cloud-native and legacy applications and also the new SaaS applications, we built a cloud that handles all three use cases at scale, resiliently, in a very secure manner, and I don't know of any other cloud that's handling those three use cases all in, we'll call it the same tendency for us at ORACLE. >> My question is why was it important for ORACLE, and is it important for ORACLE and its customers, to participate in IaaS and PaaS and SaaS? Why not just the last two layers of that? What does that give you from a strategic advantage standpoint and what does that do for your customer? >> Yeah, great question. So, the number one reason why we needed to have all three was that we have so many customers who, today, are in a data center. They're running a lot of our workloads on-premise and they absolutely are trying to find a better way to deliver lower-cost services to their customers and so we couldn't just say, let's just, everyone needs to just become net new, everyone just needs to ditch the old and go just to brand-new alone. Too hard, too expensive, at times. So we said, you know, let's give us customers the ultimate amount of choice. So, let's even go back again to that developer conversation in SaaS. If you didn't have IaaS, we couldn't help customers achieve a zero data center strategy with their traditional application, we'll call it PeopleSoft or JD Edwards or E-Business Suite or even, there's some massive applications that are running on the ORACLE cloud right now that are custom applications built on the ORACLE database. What they want is they said, give me the lowest cost but yet predictable performance IaaS. I'll run my apps tier on this. Number two, give me a platform service for database, 'cause frankly, I don't really want to run your database, like, with all the menial effort. I want someone to automate patching, scale up and down, and all these types of features like the cloud should have given us. And then number three, I do want SaaS over time. So, we spend a lot of time with our customers really saying, how do I take this traditional application, run it on IaaS and PaaS, and then number two, let's modernize it at scale. Maybe I want to start peeling off functionality and running them as cloud-native services right alongside, right? That's something, again, that we're doing at scale and other people are having a hard time running these traditional workloads on-prem in the cloud. The second part is they say, you know, I've got this legacy traditional ERP. It's been servicing me well, or maybe a supply chain system. Ultimately I want to get out of this. How do I get to SaaS? And we say, okay, here's the way to do this. First, bring it to the cloud, run it on IaaS and PaaS, and then selectively, I call it cloud slicing, take a piece of functionality and put it into SaaS. We're helping customers move to the cloud at scale. We're helping 'em do it at their rate, with whatever level of change they want, and when they are ready for SaaS, we're ready for them. >> And how does autonomous fit into this whole architecture? Thank you, by the way, for that description. I mean, it's nuanced but it's important. I'm sure you're having this conversation with a lot of cloud architects and chief technologists. They want to know this stuff, and they want to know how it works. And then, obviously, we'll talk about what the business impact is, but talk about autonomous and where that fit. >> So, the autonomous database, what we've done is really taken a look at all the runtime operations of an ORACLE database, so tuning, patching, securing, all these different features, and what we've done is taken the best of the ORACLE database, the best of something called Exadata, right, which we run on the cloud, which really helps a lot of our customers, and then we've wrapped it with a set of automation and security tools to help it really manage itself, tune itself, patch itself, scale up and down independent between computant storage. So, why that's important though is that it really, our goal is to help people run the ORACLE database as they have for years but with far less effort, and then even not only far less effort, hopefully, you know, a machine plus man, kind of the equation we always talk about is man plus machine is greater than man alone. So, being assisted by artificial intelligence and machine learning to perform those database operations, we should provide a better service to our customers with far less cost. Our hope and goal is that people have been running ORACLE databases. How can we help them do it with far less effort, and maybe spend more time on what the data can do for the organization, right? Improve customer experience, etc. Versus maybe, like, how do I spin up (breaks up). >> So, let's talk about the business impact. So, you go into customers, you talk to the cloud architects, the chief technologists, you pass that test. Now you got to deliver the business impact. Where does ORACLE Consulting fit with regard to that? And maybe you could talk about where you guys want to take this thing. >> Yeah, absolutely. I mean, the cloud is great set of technologies, but where ORACLE Consulting is really helping us deliver is in the outcome. One of the things, I think, that's been fantastic working with the ORACLE Consulting team is that, you know, cloud is new. For a lot of customers who've been running these environments for a number of years, there's always some fear and a little bit of trepidation saying, how do I learn this new cloud? I mean, the workloads we're talking about, Dave, are like tier zero, tier one, tier two and, you know, all the way up to DEV and TEST and DR. ORACLE Consulting does really couple of things in particular. Number one, they start with the end in mind, and number two that they start to do, is they really help implement these systems and there's a lot of different assurances that we have that we're going to get it done on time and better be under budget, 'cause ultimately, again, that's something that's really paramount for us. And then the third part of it, a lot of times it's runbooks, right? We actually don't want to just live in our customers' environments. We want to help them understand how to run this new system, so in training and change management, a lot of times ORACLE Consulting is helping with runbooks. We usually will, after doing it the first time, we'll sit back and let the customer do it the next few times and essentially help them through the process, and our goal at that point is to leave. Only if the customer wants us to, but ultimately our goal is to implement it, get it to go live on time, and then help the customer learn this journey to the cloud. And without them, frankly, I think these systems are sometimes too complex and difficult to do on your own maybe the first time, especially 'cause like I say, they're closing the books. They might be running your entire supply chain. They run your entire HR system or whatever they might be. Too important to leave to chance. So, they really help us with helping the customer become live and become very confident and skilled 'cause they can do it themselves. >> Well Chris, we've covered the gamut. Loved the conversation. We'll have to leave it right there, but thanks so much for coming on theCUBE and sharing your insights. Great stuff. >> Absolutely, thanks Dave, and thanks for having me on. >> All right, you're welcome, and thank you for watching everybody. This is Dave Vellante for theCUBE. We are covering the ORACLE of North America Consulting transformation and its rebirth in this digital event. Keep it right there, we'll be right back.

(upbeat jingle) >> The history of Exadata in the platform is really unique. And from my vantage point, it started earlier this century as a skunkworks inside of Oracle called Project Sage back when grid computing was the next big thing. Oracle saw that betting on standard hardware would put it on an industry curve that would rapidly evolve. Last April, for example, Oracle announced the availability of Exadata X9M in OCI, Oracle Cloud Infrastructure. One thing that hasn't been as well publicized is that Exadata on OCI is using AMD's EPYC processors in the database service. EPYC is not Eastern Pacific Yacht Club for all you sailing buffs, rather it stands for Extreme Performance Yield Computing, the enterprise grade version of AMD's Zen architecture which has been a linchpin of AMD's success in terms of penetrating enterprise markets. And to focus on the innovations that AMD and Oracle are bringing to market, we have with us today, Juan Loaiza, who's executive vice president of mission critical technologies at Oracle, and Mark Papermaster, who's the CTO and EVP of technology and engineering at AMD. Juan, welcome back to the show. Mark, great to have you on The Cube in your first appearance, thanks for coming on. Juan, let's start with you. You've been on The Cube a number of times, as I said, and you've talked about how Exadata is a top platform for Oracle database. We've covered that extensively. What's different and unique from your point of view about Exadata Cloud Infrastructure X9M on OCI? >> So as you know, Exadata, it's designed top down to be the best possible platform for database. It has a lot of unique capabilities, like we make extensive use of RDMA, smart storage. We take advantage of everything we can in the leading hardware platforms. X9M is our next generation platform and it does exactly that. We're always wanting to be, to get all the best that we can from the available hardware that our partners like AMD produce. And so that's what X9M in it is, it's faster, more capacity, lower latency, more iOS, pushing the limits of the hardware technology. So we don't want to be the limit, the software database software should not be the limit, it should be the actual physical limits of the hardware. That that's what X9M's all about. >> Why, Juan, AMD chips in X9M? >> We're introducing AMD chips. We think they provide outstanding performance, both for OTP and for analytic workloads. And it's really that simple, we just think the performance is outstanding in the product. >> Mark, your career is quite amazing. I could riff on history for hours but let's focus on the Oracle relationship. Mark, what are the relevant capabilities and key specs of the AMD chips that are used in Exadata X9M on Oracle's cloud? >> Well, thanks. It's really the basis of the great partnership that we have with Oracle on Exadata X9M and that is that the AMD technology uses our third generation of Zen processors. Zen was architected to really bring high performance back to X86, a very strong roadmap that we've executed on schedule to our commitments. And this third generation does all of that, it uses a seven nanometer CPU that is a core that was designed to really bring throughput, bring really high efficiency to computing and just deliver raw capabilities. And so for Exadata X9M, it's really leveraging all of that. It's really a balanced processor and it's implemented in a way to really optimize high performance. That is our whole focus of AMD. It's where we've reset the company focus on years ago. And again, great to see the super smart database team at Oracle really partner with us, understand those capabilities and it's been just great to partner with them to enable Oracle to really leverage the capabilities of the Zen processor. >> Yeah. It's been a pretty amazing 10 or 11 years for both companies. But Mark, how specifically are you working with Oracle at the engineering and product level and what does that mean for your joint customers in terms of what they can expect from the collaboration? >> Well, here's where the collaboration really comes to play. You think about a processor and I'll say, when Juan's team first looked at it, there's general benchmarks and the benchmarks are impressive but they're general benchmarks. And they showed the base processing capability but the partnership comes to bear when it means optimizing for the workloads that Exadata X9M is really delivering to the end customers. And that's where we dive down and as we learn from the Oracle team, we learn to understand where bottlenecks could be, where is there tuning that we could in fact really boost the performance above that baseline that you get in the generic benchmarks. And that's what the teams have done, so for instance, you look at optimizing latency to our DMA, you look at optimizing throughput on oil TP and database processing. When you go through the workloads and you take the traces and you break it down and you find the areas that are bottlenecking and then you can adjust, we have thousands of parameters that can be adjusted for a given workload. And that's the beauty of the partnership. So we have the expertise on the CPU engineering, Oracle Exadata team knows innately what the customers need to get the most out of their platform. And when the teams came together, we actually achieved anywhere from 20% to 50% gains on specific workloads, it is really exciting to see. >> Mark, last question for you is how do you see this relationship evolving in the future? Can you share a little roadmap for the audience? >> You bet. First off, given the deep partnership that we've had on Exadata X9M, it's really allowed us to inform our future design. So in our current third generation, EPYC is that is really what we call our epic server offerings. And it's a 7,003 third gen and Exadara X9M. So what about fourth gen? Well, fourth gen is well underway, ready for the future, but it incorporates learning that we've done in partnership with Oracle. It's going to have even more through capabilities, it's going to have expanded memory capabilities because there's a CXL connect express link that'll expand even more memory opportunities. And I could go on. So that's the beauty of a deep partnership as it enables us to really take that learning going forward. It pays forward and we're very excited to fold all of that into our future generations and provide even a better capabilities to Juan and his team moving forward. >> Yeah, you guys have been obviously very forthcoming. You have to be with Zen and EPYC. Juan, anything you'd like to add as closing comments? >> Yeah. I would say that in the processor market there's been a real acceleration in innovation in the last few years, there was a big move 10, 15 years ago when multicore processors came out. And then we were on that for a while and then things started stagnating, but in the last two or three years, AMD has been leading this, there's been a dramatic acceleration in innovation so it's very exciting to be part of this and customers are getting a big benefit from this. >> All right. Hey, thanks for coming back on The Cube today. Really appreciate your time. >> Thanks. Glad to be here. >> All right and thank you for watching this exclusive Cube conversation. This is Dave Vellante from The Cube and we'll see you next time. (upbeat jingle)

>>Oracle continues to enhance my sequel Heatwave at a very rapid pace. The company is now in its fourth major release since the original announcement in December 2020. 1 of the main criticisms of my sequel, Heatwave, is that it only runs on O. C I. Oracle Cloud Infrastructure and as a lock in to Oracle's Cloud. Oracle recently announced that heat wave is now going to be available in AWS Cloud and it announced its intent to bring my sequel Heatwave to Azure. So my secret heatwave on AWS is a significant TAM expansion move for Oracle because of the momentum AWS Cloud continues to show. And evidently the Heatwave Engineering team has taken the development effort from O. C I. And is bringing that to A W S with a number of enhancements that we're gonna dig into today is senior vice president. My sequel Heatwave at Oracle is back with me on a cube conversation to discuss the latest heatwave news, and we're eager to hear any benchmarks relative to a W S or any others. Nippon has been leading the Heatwave engineering team for over 10 years and there's over 100 and 85 patents and database technology. Welcome back to the show and good to see you. >>Thank you. Very happy to be back. >>Now for those who might not have kept up with the news, uh, to kick things off, give us an overview of my sequel, Heatwave and its evolution. So far, >>so my sequel, Heat Wave, is a fully managed my secret database service offering from Oracle. Traditionally, my secret has been designed and optimised for transaction processing. So customers of my sequel then they had to run analytics or when they had to run machine learning, they would extract the data out of my sequel into some other database for doing. Unlike processing or machine learning processing my sequel, Heat provides all these capabilities built in to a single database service, which is my sequel. He'd fake So customers of my sequel don't need to move the data out with the same database. They can run transaction processing and predicts mixed workloads, machine learning, all with a very, very good performance in very good price performance. Furthermore, one of the design points of heat wave is is a scale out architecture, so the system continues to scale and performed very well, even when customers have very large late assignments. >>So we've seen some interesting moves by Oracle lately. The collaboration with Azure we've we've covered that pretty extensively. What was the impetus here for bringing my sequel Heatwave onto the AWS cloud? What were the drivers that you considered? >>So one of the observations is that a very large percentage of users of my sequel Heatwave, our AWS users who are migrating of Aurora or so already we see that a good percentage of my secret history of customers are migrating from GWS. However, there are some AWS customers who are still not able to migrate the O. C. I to my secret heat wave. And the reason is because of, um, exorbitant cost, which was charges. So in order to migrate the workload from AWS to go see, I digress. Charges are very high fees which becomes prohibitive for the customer or the second example we have seen is that the latency of practising a database which is outside of AWS is very high. So there's a class of customers who would like to get the benefits of my secret heatwave but were unable to do so and with this support of my secret trip inside of AWS, these customers can now get all the grease of the benefits of my secret he trip without having to pay the high fees or without having to suffer with the poorly agency, which is because of the ws architecture. >>Okay, so you're basically meeting the customer's where they are. So was this a straightforward lifted shift from from Oracle Cloud Infrastructure to AWS? >>No, it is not because one of the design girls we have with my sequel, Heatwave is that we want to provide our customers with the best price performance regardless of the cloud. So when we decided to offer my sequel, he headed west. Um, we have optimised my sequel Heatwave on it as well. So one of the things to point out is that this is a service with the data plane control plane and the console are natively running on AWS. And the benefits of doing so is that now we can optimise my sequel Heatwave for the E. W s architecture. In addition to that, we have also announced a bunch of new capabilities as a part of the service which will also be available to the my secret history of customers and our CI, But we just announced them and we're offering them as a part of my secret history of offering on AWS. >>So I just want to make sure I understand that it's not like you just wrapped your stack in a container and stuck it into a W s to be hosted. You're saying you're actually taking advantage of the capabilities of the AWS cloud natively? And I think you've made some other enhancements as well that you're alluding to. Can you maybe, uh, elucidate on those? Sure. >>So for status, um, we have taken the mind sequel Heatwave code and we have optimised for the It was infrastructure with its computer network. And as a result, customers get very good performance and price performance. Uh, with my secret he trade in AWS. That's one performance. Second thing is, we have designed new interactive counsel for the service, which means that customers can now provision there instances with the council. But in addition, they can also manage their schemas. They can. Then court is directly from the council. Autopilot is integrated. The council we have introduced performance monitoring, so a lot of capabilities which we have introduced as a part of the new counsel. The third thing is that we have added a bunch of new security features, uh, expose some of the security features which were part of the My Secret Enterprise edition as a part of the service, which gives customers now a choice of using these features to build more secure applications. And finally, we have extended my secret autopilot for a number of old gpus cases. In the past, my secret autopilot had a lot of capabilities for Benedict, and now we have augmented my secret autopilot to offer capabilities for elderly people. Includes as well. >>But there was something in your press release called Auto thread. Pooling says it provides higher and sustained throughput. High concerns concerns concurrency by determining Apple number of transactions, which should be executed. Uh, what is that all about? The auto thread pool? It seems pretty interesting. How does it affect performance? Can you help us understand that? >>Yes, and this is one of the capabilities of alluding to which we have added in my secret autopilot for transaction processing. So here is the basic idea. If you have a system where there's a large number of old EP transactions coming into it at a high degrees of concurrency in many of the existing systems of my sequel based systems, it can lead to a state where there are few transactions executing, but a bunch of them can get blocked with or a pilot tried pulling. What we basically do is we do workload aware admission control and what this does is it figures out, what's the right scheduling or all of these algorithms, so that either the transactions are executing or as soon as something frees up, they can start executing, so there's no transaction which is blocked. The advantage to the customer of this capability is twofold. A get significantly better throughput compared to service like Aurora at high levels of concurrency. So at high concurrency, for instance, uh, my secret because of this capability Uh oh, thread pulling offers up to 10 times higher compared to Aurora, that's one first benefit better throughput. The second advantage is that the true part of the system never drops, even at high levels of concurrency, whereas in the case of Aurora, the trooper goes up, but then, at high concurrency is, let's say, starting, uh, level of 500 or something. It depends upon the underlying shit they're using the troopers just dropping where it's with my secret heatwave. The truth will never drops. Now, the ramification for the customer is that if the truth is not gonna drop, the user can start off with a small shape, get the performance and be a show that even the workload increases. They will never get a performance, which is worse than what they're getting with lower levels of concurrency. So this let's leads to customers provisioning a shape which is just right for them. And if they need, they can, uh, go with the largest shape. But they don't like, you know, over pay. So those are the two benefits. Better performance and sustain, uh, regardless of the level of concurrency. >>So how do we quantify that? I know you've got some benchmarks. How can you share comparisons with other cloud databases especially interested in in Amazon's own databases are obviously very popular, and and are you publishing those again and get hub, as you have done in the past? Take us through the benchmarks. >>Sure, So benchmarks are important because that gives customers a sense of what performance to expect and what price performance to expect. So we have run a number of benchmarks. And yes, all these benchmarks are available on guitar for customers to take a look at. So we have performance results on all the three castle workloads, ol DB Analytics and Machine Learning. So let's start with the Rdp for Rdp and primarily because of the auto thread pulling feature. We show that for the IPCC for attended dataset at high levels of concurrency, heatwave offers up to 10 times better throughput and this performance is sustained, whereas in the case of Aurora, the performance really drops. So that's the first thing that, uh, tend to alibi. Sorry, 10 gigabytes. B B C c. I can come and see the performance are the throughput is 10 times better than Aurora for analytics. We have done a comparison of my secret heatwave in AWS and compared with Red Ship Snowflake Googled inquiry, we find that the price performance of my secret heatwave compared to read ship is seven times better. So my sequel, Heat Wave in AWS, provides seven times better price performance than red ship. That's a very, uh, interesting results to us. Which means that customers of Red Shift are really going to take the service seriously because they're gonna get seven times better price performance. And this is all running in a W s so compared. >>Okay, carry on. >>And then I was gonna say, compared to like, Snowflake, uh, in AWS offers 10 times better price performance. And compared to Google, ubiquity offers 12 times better price performance. And this is based on a four terabyte p PCH workload. Results are available on guitar, and then the third category is machine learning and for machine learning, uh, for training, the performance of my secret heatwave is 25 times faster compared to that shit. So all the three workloads we have benchmark's results, and all of these scripts are available on YouTube. >>Okay, so you're comparing, uh, my sequel Heatwave on AWS to Red Shift and snowflake on AWS. And you're comparing my sequel Heatwave on a W s too big query. Obviously running on on Google. Um, you know, one of the things Oracle is done in the past when you get the price performance and I've always tried to call fouls you're, like, double your price for running the oracle database. Uh, not Heatwave, but Oracle Database on a W s. And then you'll show how it's it's so much cheaper on on Oracle will be like Okay, come on. But they're not doing that here. You're basically taking my sequel Heatwave on a W s. I presume you're using the same pricing for whatever you see to whatever else you're using. Storage, um, reserved instances. That's apples to apples on A W s. And you have to obviously do some kind of mapping for for Google, for big query. Can you just verify that for me, >>we are being more than fair on two dimensions. The first thing is, when I'm talking about the price performance for analytics, right for, uh, with my secret heat rape, the cost I'm talking about from my secret heat rape is the cost of running transaction processing, analytics and machine learning. So it's a fully loaded cost for the case of my secret heatwave. There has been I'm talking about red ship when I'm talking about Snowflake. I'm just talking about the cost of these databases for running, and it's only it's not, including the source database, which may be more or some other database, right? So that's the first aspect that far, uh, trip. It's the cost for running all three kinds of workloads, whereas for the competition, it's only for running analytics. The second thing is that for these are those services whether it's like shit or snowflakes, That's right. We're talking about one year, fully paid up front cost, right? So that's what most of the customers would pay for. Many of the customers would pay that they will sign a one year contract and pay all the costs ahead of time because they get a discount. So we're using that price and the case of Snowflake. The costs were using is their standard edition of price, not the Enterprise edition price. So yes, uh, more than in this competitive. >>Yeah, I think that's an important point. I saw an analysis by Marx Tamer on Wiki Bond, where he was doing the TCO comparisons. And I mean, if you have to use two separate databases in two separate licences and you have to do et yelling and all the labour associated with that, that that's that's a big deal and you're not even including that aspect in in your comparison. So that's pretty impressive. To what do you attribute that? You know, given that unlike, oh, ci within the AWS cloud, you don't have as much control over the underlying hardware. >>So look hard, but is one aspect. Okay, so there are three things which give us this advantage. The first thing is, uh, we have designed hateful foreign scale out architecture. So we came up with new algorithms we have come up with, like, uh, one of the design points for heat wave is a massively partitioned architecture, which leads to a very high degree of parallelism. So that's a lot of hype. Each were built, So that's the first part. The second thing is that although we don't have control over the hardware, but the second design point for heat wave is that it is optimised for commodity cloud and the commodity infrastructure so we can have another guys, what to say? The computer we get, how much network bandwidth do we get? How much of, like objects to a brand that we get in here? W s. And we have tuned heat for that. That's the second point And the third thing is my secret autopilot, which provides machine learning based automation. So what it does is that has the users workload is running. It learns from it, it improves, uh, various premieres in the system. So the system keeps getting better as you learn more and more questions. And this is the third thing, uh, as a result of which we get a significant edge over the competition. >>Interesting. I mean, look, any I SV can go on any cloud and take advantage of it. And that's, uh I love it. We live in a new world. How about machine learning workloads? What? What did you see there in terms of performance and benchmarks? >>Right. So machine learning. We offer three capabilities training, which is fully automated, running in France and explanations. So one of the things which many of our customers told us coming from the enterprise is that explanations are very important to them because, uh, customers want to know that. Why did the the system, uh, choose a certain prediction? So we offer explanations for all models which have been derailed by. That's the first thing. Now, one of the interesting things about training is that training is usually the most expensive phase of machine learning. So we have spent a lot of time improving the performance of training. So we have a bunch of techniques which we have developed inside of Oracle to improve the training process. For instance, we have, uh, metal and proxy models, which really give us an advantage. We use adaptive sampling. We have, uh, invented in techniques for paralysing the hyper parameter search. So as a result of a lot of this work, our training is about 25 times faster than that ship them health and all the data is, uh, inside the database. All this processing is being done inside the database, so it's much faster. It is inside the database. And I want to point out that there is no additional charge for the history of customers because we're using the same cluster. You're not working in your service. So all of these machine learning capabilities are being offered at no additional charge inside the database and as a performance, which is significantly faster than that, >>are you taking advantage of or is there any, uh, need not need, but any advantage that you can get if two by exploiting things like gravity. John, we've talked about that a little bit in the past. Or trainee. Um, you just mentioned training so custom silicon that AWS is doing, you're taking advantage of that. Do you need to? Can you give us some insight >>there? So there are two things, right? We're always evaluating What are the choices we have from hybrid perspective? Obviously, for us to leverage is right and like all the things you mention about like we have considered them. But there are two things to consider. One is he is a memory system. So he favours a big is the dominant cost. The processor is a person of the cost, but memory is the dominant cost. So what we have evaluated and found is that the current shape which we are using is going to provide our customers with the best price performance. That's the first thing. The second thing is that there are opportunities at times when we can use a specialised processor for vaccinating the world for a bit. But then it becomes a matter of the cost of the customer. Advantage of our current architecture is on the same hardware. Customers are getting very good performance. Very good, energetic performance in a very good machine learning performance. If you will go with the specialised processor, it may. Actually, it's a machine learning, but then it's an additional cost with the customers we need to pay. So we are very sensitive to the customer's request, which is usually to provide very good performance at a very low cost. And we feel is that the current design we have as providing customers very good performance and very good price performance. >>So part of that is architectural. The memory intensive nature of of heat wave. The other is A W s pricing. If AWS pricing were to flip, it might make more sense for you to take advantage of something like like cranium. Okay, great. Thank you. And welcome back to the benchmarks benchmarks. Sometimes they're artificial right there. A car can go from 0 to 60 in two seconds. But I might not be able to experience that level of performance. Do you? Do you have any real world numbers from customers that have used my sequel Heatwave on A W s. And how they look at performance? >>Yes, absolutely so the my Secret service on the AWS. This has been in Vera for, like, since November, right? So we have a lot of customers who have tried the service. And what actually we have found is that many of these customers, um, planning to migrate from Aurora to my secret heat rape. And what they find is that the performance difference is actually much more pronounced than what I was talking about. Because with Aurora, the performance is actually much poorer compared to uh, like what I've talked about. So in some of these cases, the customers found improvement from 60 times, 240 times, right? So he travels 100 for 240 times faster. It was much less expensive. And the third thing, which is you know, a noteworthy is that customers don't need to change their applications. So if you ask the top three reasons why customers are migrating, it's because of this. No change to the application much faster, and it is cheaper. So in some cases, like Johnny Bites, what they found is that the performance of their applications for the complex storeys was about 60 to 90 times faster. Then we had 60 technologies. What they found is that the performance of heat we have compared to Aurora was 100 and 39 times faster. So, yes, we do have many such examples from real workloads from customers who have tried it. And all across what we find is if it offers better performance, lower cost and a single database such that it is compatible with all existing by sequel based applications and workloads. >>Really impressive. The analysts I talked to, they're all gaga over heatwave, and I can see why. Okay, last question. Maybe maybe two and one. Uh, what's next? In terms of new capabilities that customers are going to be able to leverage and any other clouds that you're thinking about? We talked about that upfront, but >>so in terms of the capabilities you have seen, like they have been, you know, non stop attending to the feedback from the customers in reacting to it. And also, we have been in a wedding like organically. So that's something which is gonna continue. So, yes, you can fully expect that people not dressed and continue to in a way and with respect to the other clouds. Yes, we are planning to support my sequel. He tripped on a show, and this is something that will be announced in the near future. Great. >>All right, Thank you. Really appreciate the the overview. Congratulations on the work. Really exciting news that you're moving my sequel Heatwave into other clouds. It's something that we've been expecting for some time. So it's great to see you guys, uh, making that move, and as always, great to have you on the Cube. >>Thank you for the opportunity. >>All right. And thank you for watching this special cube conversation. I'm Dave Volonte, and we'll see you next time.

>> Welcome back to Supercloud22, #Supercloud22. This is Dave Vellante. In 2019 Oracle and Microsoft announced a collaboration to bring interoperability between OCI, Oracle Cloud Infrastructure and Azure Clouds. It was Oracle's initial foray into so-called multi-cloud and we're joined by Karan Batta, who's the Vice President for Product Management at OCI. And Kris Rice is the Vice President of Software Development at Oracle Database. And we're going to talk about how this technology's evolving and whether it fits our view of what we call supercloud. Welcome gentlemen, thank you. >> Thanks for having us. >> So you recently just last month announced the new service. It extends on the initial partnership with Microsoft Oracle interconnect with Azure, and you refer to this as a secure private link between the two clouds, it cross 11 regions around the world, under two milliseconds data transmission sounds pretty cool. It enables customers to run Microsoft applications against data stored in Oracle databases without any loss in efficiency or presumably performance. So we use this term supercloud to describe a service or sets of services built on hyper scale infrastructure that leverages the core primitives and APIs of an individual cloud platform, but abstracts that underlying complexity to create a continuous experience across more than one cloud. Is that what you've done? >> Absolutely. I think it starts at the top layer in terms of just making things very simple for the customer, right. I think at the end of the day we want to enable true workloads running across two different clouds where you're potentially running maybe the app layer in one and the database layer or the back in another. And the integration I think starts with, you know, making it ease of use. Right. So you can start with things like, okay can you log into your second or your third cloud with the first cloud provider's credentials? Can you make calls against another cloud using another cloud's APIs? Can you peer the networks together? Can you make it seamless? I think those are all the components that are sort of, they're kind of the ingredients to making a multi-cloud or supercloud experience successful. >> Oh, thank you for that, Karan. So I guess there's a question for Chris is I'm trying to understand what you're really solving for? What specific customer problems are you focused on? What's the service optimized for presumably it's database but maybe you could double click on that. >> Sure. So, I mean, of course it's database. So it's a super fast network so that we can split the workload across two different clouds leveraging the best from both, but above the networking, what we had to do do is we had to think about what a true multi-cloud or what you're calling supercloud experience would be it's more than just making the network bites flow. So what we did is we took a look as Karan hinted at right, is where is my identity? Where is my observability? How do I connect these things across how it feels native to that other cloud? >> So what kind of engineering do you have to do to make that work? It's not just plugging stuff together. Maybe you could explain a little bit more detail, the the resources that you had to bring to bear and the technology behind the architecture. >> Sure. I think, it starts with actually, what our goal was, right? Our goal was to actually provide customers with a fully managed experience. What that means is we had to basically create a brand new service. So, we have obviously an Azure like portal and an experience that allows customers to do this but under the covers, we actually have a fully managed service that manages the networking layer, the physical infrastructure, and it actually calls APIs on both sides of the fence. It actually manages your Azure resources, creates them but it also interacts with OCI at the same time. And under the covers this service actually takes Azure primitives as inputs. And then it sort of like essentially translates them to OCI action. So, we actually truly integrated this as a service that's essentially built as a PaaS layer on top of these two clouds. >> So, the customer doesn't really care or know maybe they know cuz they might be coming through, an Azure experience, but you can run work on either Azure and or OCI. And it's a common experience across those clouds. Is that correct? >> That's correct. So like you said, the customer does know that they know there is a relationship with both clouds but thanks to all the things we built there's this thing we invented we created called a multi-cloud control plane. This control plane does operate against both clouds at the same time to make it as seamless as possible so that maybe they don't notice, you know, the power of the interconnect is extremely fast networking, as fast as what we could see inside a single cloud. If you think about how big a data center might be from edge to edge in that cloud, going across the interconnect makes it so that that workload is not important that it's spanning two clouds anymore. >> So you say extremely fast networking. I remember I used to, I wrote a piece a long time ago. Larry Ellison loves InfiniBand. I presume we've moved on from them, but maybe not. What is that interconnect? >> Yeah, so it's funny you mentioned interconnect you know, my previous history comes from Edge PC where we actually inside OCI today, we've moved from Infinite Band as is part of Exadata's core to what we call Rocky V two. So that's just another RDMA network. We actually use it very successfully, not just for Exadata but we use it for our standard computers that we provide to high performance computing customers. >> And the multi-cloud control plane runs. Where does that live? Does it live on OCI? Does it live on Azure? Yes? >> So it does it lives on our side. Our side of the house as part of our Oracle OCI control plane. And it is the veneer that makes these two clouds possible so that we can wire them together. So it knows how to take those Azure primitives and the OCI primitives and wire them at the appropriate levels together. >> Now I want to talk about this PaaS layer. Part of supercloud, we said to actually make it work you're going to have to have a super PaaS. I know we're taking this this term a little far but it's still it's instructive in that, what we surmised was you're probably not going to just use off the shelf, plain old vanilla PaaS, you're actually going to have a purpose built PaaS to solve for the specific problem. So as an example, if you're solving for ultra low latency, which I think you're doing, you're probably no offense to my friends at Red Hat but you're probably not going to develop this on OpenShift, but tell us about that PaaS layer or what we call the super PaaS layer. >> Go ahead, Chris. >> Well, so you're right. We weren't going to build it out on OpenShift. So we have Oracle OCI, you know, the standard is Terraform. So the back end of everything we do is based around Terraform. Today, what we've done is we built that control plane and it will be API drivable, it'll be drivable from the UI and it will let people operate and create primitives across both sides. So you can, you mentioned developers, developers love automation, right, because it makes our lives easy. We will be able to automate a multi-cloud workload from ground up config is code these days. So we can config an entire multi-cloud experience from one place. >> So, double click Chris on that developer experience. What is that like? They're using the same tool set irrespective of, which cloud we're running on is, and it's specific to this service or is it more generic, across other Oracle services? >> There's two parts to that. So one is the, we've only onboarded a portion. So the database portfolio and other services will be coming into this multi-cloud. For the majority of Oracle cloud, the automation, the config layer is based on Terraform. So using Terraform, anyone can configure everything from a mid-tier to an Exadata, all the way soup to nuts from smallest thing possible to the largest. What we've not done yet is integrated truly with the Azure API, from command line drivable. That is coming in the future. It is on the roadmap, it is coming. Then they could get into one tool but right now they would have half their automation for the multi-cloud config on the Azure tool set and half on the OCI tool set. >> But we're not crazy saying from a roadmap standpoint that will provide some benefit to developers and is a reasonable direction for the industry generally but Oracle and Microsoft specifically. >> Absolutely. I'm a developer at heart. And so one of the things we want to make sure is that developers' lives are as easy as possible. >> And is there a metadata management layer or intelligence that you've built in to optimize for performance or low latency or cost across the respective clouds? >> Yeah, definitely. I think, latency's going to be an important factor. The service that we've initially built isn't going to serve, the sort of the tens of microseconds but most applications that are sort of in, running on top of the enterprise applications that are running on top of the database are in the several millisecond range. And we've actually done a lot of work on the networking pairing side to make sure that when we launch these resources across the two clouds we actually picked the right trial site. We picked the right region we pick the right availability zone or domain. So we actually do the due diligence under the cover so the customer doesn't have to do the trial and error and try to find the right latency range. And this is actually one of the big reasons why we only launch the service on the interconnect regions. Even though we have close to, I think close to 40 regions at this point in OCI, this service is only built for the regions that we have an interconnect relationship with Microsoft. >> Okay, so you started with Microsoft in 2019. You're going deeper now in that relationship, is there any reason that you couldn't, I mean technically what would you have to do to go to other clouds? You talked about understanding the primitives and leveraging the primitives of Azure. Presumably if you wanted to do this with AWS or Google or Alibaba, you would have to do similar engineering work, is that correct? Or does what you've developed just kind of poured over to any cloud? >> Yeah, that's absolutely correct Dave. I think Chris talked a lot about the multi-cloud control plane, right? That's essentially the control plane that goes and does stuff on other clouds. We would have to essentially go and build that level of integration into the other clouds. And I think, as we get more popularity and as more products come online through these services I think we'll listen to what customers want. Whether it's, maybe it's the other way around too, Dave maybe it's the fact that they want to use Oracle cloud but they want to use other complimentary services within Oracle cloud. So I think it can go both ways. I think, the market and the customer base will dictate that. >> Yeah. So if I understand that correctly, somebody from another cloud Google cloud could say, Hey we actually want to run this service on OCI cuz we want to expand our market. And if TK gets together with his old friends and figures that out but then we're just, hypothesizing here. But, like you said, it can go both ways. And then, and I have another question related to that. So, multi clouds. Okay, great. Supercloud. How about the Edge? Do you ever see a day where that becomes part of the equation? Certainly the near Edge would, you know, a Home Depot or Lowe's store or a bank, but what about the far Edge, the tiny Edge. Can you talk about the Edge and where that fits in your vision? >> Yeah, absolutely. I think Edge is a interestingly, it's getting fuzzier and fuzzier day by day. I think, the term. Obviously every cloud has their own sort of philosophy in what Edge is, right. We have our own. It starts from, if you do want to do far Edge, we have devices like red devices, which is our ruggedized servers that talk back to our control plane in OCI. You could deploy those things unlike, into war zones and things like that underground. But then we also have things like clouded customer where customers can actually deploy components of our infrastructure like compute or Exadata into a facility where they only need that certain capability. And then a few years ago we launched, what's now called Dedicated Region. And that actually is a different take on Edge in some sense where you get the entire capability of our public commercial region, but within your facility. So imagine if a customer was to essentially point a finger on a commercial map and say, Hey, look, that region is just mine. Essentially that's the capability that we're providing to our customers, where if you have a white space if you have a facility, if you're exiting out of your data center space, you could essentially place an OCI region within your confines behind your firewall. And then you could interconnect that to a cloud provider if you wanted to, and get the same multi-cloud capability that you get in a commercial region. So we have all the spectrums of possibilities here. >> Guys, super interesting discussion. It's very clear to us that the next 10 years of cloud ain't going to be like the last 10. There's a whole new layer. Developing, data is a big key to that. We see industries getting involved. We obviously didn't get into the Oracle Cerner acquisitions. It's a little too early for that but we've actually predicted that companies like Cerner and you're seeing it with Goldman Sachs and Capital One they're actually building services on the cloud. So this is a really exciting new area and really appreciate you guys coming on the Supercloud22 event and sharing your insights. Thanks for your time. >> Thanks for having us. >> Okay. Keep it right there. #Supercloud22. We'll be right back with more great content right after this short break. (lighthearted marimba music)

(upbeat music) >> Welcome back to Supercloud22, #Supercloud22, this is Dave Vellante. In 2019, Oracle and Microsoft announced a collaboration to bring interoperability between OCI, Oracle Cloud Infrastructure and Azure clouds. It was Oracle's initial foray into so-called multi-cloud and we're joined by Karan Batta, who's the vice president for product management at OCI, and Kris Rice, is the vice president of software development at Oracle database. And we're going to talk about how this technology's evolving and whether it fits our view of what we call, Supercloud. Welcome, gentlemen. Thank you. >> Thanks for having us. >> Thanks for having us. >> So you recently just last month announced the new service. It extends on the initial partnership with Microsoft Oracle Interconnect with Azure, and you refer to this as a secure private link between the two clouds across 11 regions around the world. Under two milliseconds data transmission, sounds pretty cool. It enables customers to run Microsoft applications against data stored in Oracle databases without any loss in efficiency or presumably performance. So we use this term Supercloud to describe a service or sets of services built on hyperscale infrastructure that leverages the core primitives and APIs of an individual cloud platform, but abstracts that underlying complexity to create a continuous experience across more than one cloud. Is that what you've done? >> Absolutely. I think, you know, it starts at the, you know, at the top layer in terms of, you know, just making things very simple for the customer, right. I think at the end of the day we want to enable true workloads running across two different clouds, where you're potentially running maybe the app layer in one and the database layer or the back in another, and the integration I think, starts with, you know, making it ease of use. Right? So you can start with things like, okay can you log into your second or your third cloud with the first cloud provider's credentials? Can you make calls against another cloud using another cloud's APIs? Can you peer the networks together? Can you make it seamless? I think those are all the components that are sort of, they're kind of the ingredients to making a multi-cloud or Supercloud experience successful. >> Oh, thank you for that, Karan. So, I guess as a question for Kris is trying to understand what you're really solving for, what specific customer problems are you focused on? What's the service optimized for presumably its database but maybe you could double click on that. >> Sure. So, I mean, of course it's database so it's a super fast network so that we can split the workload across two different clouds leveraging the best from both, but above the networking, what we had to do is we had to think about what a true multi-cloud or what you're calling Supercloud experience would be. It's more than just making the network bytes flow. So what we did is, we took a look as Karan hinted at, right? Is where is my identity? Where is my observability? How do I connect these things across how it feels native to that other cloud? >> So what kind of engineering do you have to do to make that work? It's not just plugging stuff together. Maybe you could explain in a little bit more detail, the resources that you had to bring to bear and the technology behind the architecture? >> Sure. >> I think, you know, it starts with actually, you know, what our goal was, right? Our goal was to actually provide customers with a fully managed experience. What that means is we had to basically create a brand new service. So, you know, we have obviously an Azure like portal and an experience that allows customers to do this but under the covers, we actually have a fully managed service that manages the networking layer that the physical infrastructure, and it actually calls APIs on both sides of the fence. It actually manages your Azure resources, creates them, but it also interacts with OCI at the same time. And under the covers this service actually takes Azure primitives as inputs, and then it sort of like essentially translates them to OCI action. So, so we actually truly integrated this as a service that's essentially built as a PaaS layer on top of these two clouds. >> So, so the customer doesn't really care, or know, maybe they know, coz they might be coming through, you know, an Azure experience, but you can run work on either Azure and or OCI, and it's a common experience across those clouds, is that correct? >> That's correct. So, like you said, the customer does know that they know there is a relationship with both clouds but thanks to all the things we built there's this thing we invented, we created called a multi-cloud control plane. This control plane does operate against both clouds at the same time to make it as seamless as possible so that maybe they don't notice, you know, the power of the interconnect is extremely fast networking, as fast as what we could see inside a single cloud, if you think about how big a data center might be from edge to edge in that cloud. Going across the interconnect makes it so that that workload is not important that it's spanning two clouds anymore. >> So you say extremely fast networking. I remember I used to, I wrote a piece a long time ago. Hey, Larry Ellison loves InfiniBand. I presume we've moved on from them, but maybe not. What is that interconnect? >> Yeah, so it's funny, you mentioned interconnect, you know, my previous history comes from HPC where we actually inside inside OCI today, we've moved from, you know, InfiniBand as its part of Exadata's core, to what we call RoCEv2. So that's just another RDMA network. We actually use it very successfully, not just for Exadata but we use it for our standard computers, you know, that we provide to, you know, high performance computing customers. >> And the multi-cloud control plane, runs... Where does that live? Does it live on OCI? Does it live on Azure? Yes? >> So it does. It lives on our side. >> Yeah. >> Our side of the house, and it is part of our Oracle OCI control plane. And it is the veneer that makes these two clouds possible so that we can wire them together. So it knows how to take those Azure primitives and the OCI primitives and wire them at the appropriate levels together. >> Now I want to talk about this PaaS layer. Part of Supercloud, we said, to actually make it work you're going to have to have a super PaaS. I know, we're taking this term a little far but it's still, it's instructive in that, what we, what we surmised was, you're probably not going to just use off the shelf, plain old vanilla PaaS, you're actually going to have a purpose built PaaS to solve for the specific problem. So, as an example, if you're solving for ultra low latency, which I think you're doing, you're probably, no offense to my friends at Red Hat, but you're probably not going to develop this on OpenShift, but tell us about that, that PaaS layer or what we call the super PaaS layer. >> Go ahead, Kris. >> Well, so you're right. We weren't going to build it out on OpenShift. So we have Oracle OCI, you know, the standard is Terraform. So the back end of everything we do is based around Terraform. Today, what we've done, is we built that control plane and it will be API drivable. It'll be drivable from the UI and it will let people operate and create primitives across both sides. So you can, you, you mentioned developers developers love automation, right? Because it makes our lives easy. We will be able to automate a multi-cloud workload, from ground up, Config is code these days. So we can Config an entire multi-cloud experience from one place. >> So, double click Kris on that developer experience, you know, what is that like? They're using the same tool set irrespective of, you know, which cloud we're running on is, is it and it's specific to this service or is it more generic across other Oracle services? >> There's two parts to that. So one is the, we've only onboarded a portion. So the database portfolio and other services will be coming into this multi-cloud. For the majority of Oracle cloud the automation, the Config layer is based on Terraform. So using Terraform, anyone can configure everything from a mid tier to an Exadata, all the way soup to nuts from smallest thing possible to the largest. What we've not done yet is is integrated truly with the Azure API, from command line drivable, that is coming in the future. It will be, it is on the roadmap. It is coming, then they could get into one tool but right now they would have half their automation for the multi-cloud Config on the Azure tool set and half on the OCI tool set. >> But we're not crazy saying from a roadmap standpoint that will provide some benefit to developers and is a reasonable direction for the industry generally but Oracle and, and, and Microsoft specifically? >> Absolutely. I'm a developer at heart. And so one of the things we want to make sure is that developers' lives are as easy as possible. >> And, and is there a Metadata management layer or intelligence that you've built in to optimize for performance or low latency or cost across the, the respective clouds? >> Yeah, definitely. I think, you know, latency's going to be an important factor. You know, the, the service that we've initially built isn't going to serve, you know, the sort of the tens of microseconds but most applications that are sort of in, you know, running on top of, the enterprise applications that are running on top of the database are in the several millisecond range. And we've actually done a lot of work on the networking pairing side to make sure that when we launch, when we launch these resources across the two clouds we actually pick the right trial site, we pick the right region, we pick the right availability zone or domain. So we actually do the due diligence under the cover, so the customer doesn't have to do the trial and error and try to find the right latency range, you know, and this is actually one of the big reasons why we only launched this service on the interconnect regions. Even though we have close to, I think, close to 40 regions at this point in OCI, this, this, this service is only built for the regions that we have an interconnect relationship with with Microsoft. >> Okay. So, so you've, you started with Microsoft in 2019 you're going deeper now in that relationship, is there is there any reason that you couldn't, I mean technically what would you have to do to go to other clouds? Would you just, you talked about understanding the primitives and leveraging the primitives of Azure. Presumably if you wanted to do this with AWS or Google or Alibaba, you would have to do similar engineering work, is that correct? Or does what you've developed just kind of pour it over to any cloud? >> Yeah, that's, that's absolutely correct, Dave, I think, you know, Kris talked a lot about kind of the multi-cloud control plane, right? That's essentially the, the, the control plane that goes and does stuff on other clouds. We would have to essentially go and build that level of integration into the other clouds. And I think, you know, as we get more popularity and as as more products come online through these services I think we'll listen to what customers want, whether it's you know, maybe it's the other way around too, Dave maybe it's the fact that they want to use Oracle cloud but they want to use other complimentary services within Oracle cloud. So I think it can go both ways. I think, you know, kind of the market and the customer base will dictate that. >> Yeah. So if I understand that correctly, somebody from another cloud Google cloud could say, "Hey, we actually want to run this service on OCI coz we want to expand our market and..." >> Right. >> And if TK gets together with his old friends and figures that out but we're just, you know, hypothesizing here, but but like you said, it can, can go both ways. And then, and I have another question related to that. So you multi-clouds. Okay, great. Supercloud. How about the edge? Do you ever see a day where that becomes part of the equation? Certainly the, the near edge would, you know, a a home Depot or a Lowe's store or a bank, but what about like the far edge, the tiny edge. Do, do you, can you talk about the edge and and where that fits in your vision? >> Yeah, absolutely. I think edge is a interestingly, it's a, it's a it's getting fuzzier and fuzzier day by day. I think there's the term, you know, we, obviously every cloud has their own sort of philosophy in what edge is, right? We have our own, you know, it starts from, you know, if you if you do want to do far edge, you know, we have devices like red devices, which is our ruggedized servers that that talk back to our, our control plane in OCI you could deploy those things in like, you know, into war zones and things like that underground. But then we also have things like Cloud@Customer where customers can actually deploy components of our infrastructure, like Compute or Exadata into a facility where they only need that certain capability. And then a few years ago we launched, you know, what's now called Dedicated Region. And that actually is a, is a different take on edge in some sense where you get the entire capability of our public commercial region, but within your facility. So imagine if, if, if a customer was to essentially point to, you know, point to, point a finger on a commercial map and say, "Hey, look, that region is just mine." Essentially, that's the capability that we're providing to our customers, where if you have a white space if you have a facility if you're exiting out of your data center space you could essentially place an OCI region within your confines behind your firewall. And then you could interconnect that to a cloud provider if you wanted to. and get the same multi-cloud capability that you get in a commercial region. So we have all the spectrums of possibilities there. >> Guys, super interesting discussion. It's very clear to us that the next 10 years of cloud ain't going to be like the last 10. There's a whole new layer developing. Data is a big key to that. We see industries getting involved. We obviously didn't, didn't get into the Oracle Cerner acquisitions a little too early for that but we we've actually predicted that companies like Cerner and you've seen it with Goldman Sachs and Capital One, they're actually building services on the cloud. So this is a really exciting new area and I really appreciate you guys coming on the Supercloud22 event and sharing your insights. Thanks for your time. >> Thank very much. >> Thank very much. >> Okay. Keep it right there. #Supercloud22. We'll be right back with more great content right after this short break. (upbeat music)

(upbeat music) >> Oracle continues to pursue a multi-mode converged database strategy. The premise of this all in one approach is to make life easier for practitioners and developers. And the most recent example is the Oracle database API for MongoDB, which was announced today. Now, Oracle, they're not the first to come out with a MongoDB compatible API, but Oracle hopes to use its autonomous database as a differentiator and further build a moat around OCI, Oracle Cloud Infrastructure. And with us to talk about Oracle's MongoDB compatible API is Gerald Venzl, who's a distinguished Product Manager at Oracle. Gerald was a guest along with Maria Colgan on the CUBE a while back, and we talked about Oracle's converge database and the kind of Swiss army knife strategy, I called it, of databases. This is dramatically different. It's an approach that we see at the opposite end of the the spectrum, for instance, from AWS, who, for example, goes after the world of developers with a different database for every use case. So, kind of picking up from there, Gerald, I wonder if you could talk about how this new MongoDB API adds to your converged model and the whole strategy there. Where does it fit? >> Yeah, thank you very much, Dave and, by the way, thanks for having me on the CUBE again. A pleasure to be here. So, essentially the MongoDB API to build the compatibility that we used with this API is a continuation of the converge database story, as you said before. Which is essentially bringing the many features of the many single purpose databases that people often like and use, together into one technology so that everybody can benefit from it. So as such, this is just a continuation that we have from so many other APIs or standards that we support. Since a long time, we already, of course to SQL because we are relational database from the get go. Also other standard like GraphQL, Sparkle, et cetera that we have. And the MongoDB API, is now essentially just the next step forward to give the developers this API that they've gotten to love and use. >> I wonder if you could talk about from the developer angle, what do they get out of it? Obviously you're appealing to the Mongo developers out there, but you've got this Mongo compatible API you're pouting the autonomous database on OCI. Why aren't they just going to use MongoDB Atlas on whatever cloud, Azure or AWS or Google Cloud platform? >> That's a very good question. We believe that the majority of developers want to just worry about their application, writing the application, and not so much about the database backend that they're using. And especially in cloud with cloud services, the reason why developers choose these services is so that they don't have to manage them. Now, autonomous database brings many topnotch advanced capabilities to database cloud services. We firmly believe that autonomous database is essentially the next generation of cloud services with all the self-driving features built in, and MongoDB developers writing applications against the MongoDB API, should not have to hold out on these capabilities either. It's like no developer likes to tune the database. No developer likes to take a downtime when they have to rescale their database to accommodate a bigger workload. And this is really where we see the benefit here, so for the developer, ideally nothing will change. You have MongoDB compatible API so they can keep on using their tools. They can build the applications the way that they do, but the benefit from the best cloud database service out there not having to worry about any of these package things anymore, that even MongoDB Atlas has a lot of shortcomings still today, as we find. >> Of cos, this is always a moving target The technology business, that's why we love it. So everybody's moving fast and investing and shaking and jiving. But, I want to ask you about, well, by the way, that's so you're hiding the underlying complexity, That's really the big takeaway there. So that's you huge for developers. But take, I was talking before about, the Amazon's approach, right tool for the right job. You got document DB, you got Microsoft with Cosmos, they compete with Mongo and they've been doing so for some time. How does Oracle's API for Mongo different from those offerings and how you going to attract their users to your JSON offering. >> So, you know, for first of all we have to kind of separate slightly document DB and AWS and Cosmos DB in Azure, they have slightly different approaches there. Document DB essentially is, a document store owned by and built by AWS, nothing different to Mongo DB, it's a head to head comparison. It's like use my document store versus the other document store. So you don't get any of the benefits of a converge database. If you ever want to do a different data model, run analytics over, etc. You still have to use the many other services that AWS provides you to. You cannot all do it into one database. Now Cosmos DB it's more in interesting because they claim to be a multi-model database. And I say claim because what we understand as multi-model database is different to what they understand as multimodel database. And also one of the reasons why we start differentiating with converge database. So what we mean is you should be able to regardless what data format you want to store in the database leverage all the functionality of the database over that data format, with no trade offs. Cosmos DB when you look at it, it essentially gives you mode of operation. When you connect as the application or the user, you have to decide at connection time, how you want, how this database should be treated. Should it be a document store? Should it be a graph store? Should it be a relational store? Once you make that choice, you are locked into that. As long as you establish that connection. So it's like, if you say, I want a document store, all you get is a document store. There's no way for you to crossly analyze with the relational data sitting in the same service. There's no for you to break these boundaries. If you ever want to add some graph data and graph analytics, you essentially have to disconnect and now treat it as a graph store. So you get multiple data models in it, but really you still get, one trick pony the moment you connect to it that you have to choose to. And that is where we see a huge differentiation again with our converge database, because we essentially say, look, one database cloud service on Oracle cloud, where it allows you to do anything, if you wish to do so. You can start as a document store if you wish to do so. If you want to write some SQL queries on top, you can do so. If you want to add some graph data, you can do so. But there's no way for you to have to rewrite your application, use different libraries and frameworks now to connect et cetera, et cetera. >> Got it. Thank you for that. Do you have any data when you talk to customers? Like I'm interested in the diversity of deployments, like for instance, how many customers are using more than one data model? Do for instance, do JSON users need support for other data types or are they happy to stay kind of in their own little sandbox? Do you have any data on that? >> So what we see from the majority of our customers, there is no such thing as one data model fits everything. So, and it's like, there again we have to differentiate the developer that builds a certain microservice, that makes happy to stay in the JSON world or relational world, or the company that's trying to derive value from the data. So it's like the relational model has not gone away since 40 years of it existence. It's still kicking strong. It's still really good at what it does. The JSON data model is really good in what it does. The graph model is really good at what it does. But all these models have been built for different purposes. Try to do graph analytics on relational or JSON data. It's like, it's really tricky, but that's why you use a graph model to begin with. Try to shield yourself from the organization of the data, how it's structured, that's really easy in the relational world, not so much when you get into a document store world. And so what we see about our customers is like as they accumulate more data, is they have many different applications to run their enterprises. The question always comes back, as we have predicted since about six, seven years now, where they say, hey, we have all this different data and different data formats. We want to bring it all together, analyze it together, get value out of the data together. We have seen a whole trend of big data emerge and disappear to answer the question and didn't quite do the trick. And we are basically now back to where we were in the early 2000's when XML databases have faded away, because everybody just allowed you to store XML in the database. >> Got it. So let's make this real for people. So maybe you could give us some examples. You got this new API from Mongo, you have your multi model database. How, take a, paint a picture of how customers are going to benefit in real world use cases. How does it kind of change the customer's world before and after if you will? >> Yeah, absolutely. So, you know the API essentially we are going to use it to accept before, you know, make the lives of the developers easier, but also of course to assist our customers with migrations from Mongo DB over to Oracle Autonomous Database. One customer that we have, for example, that would've benefited of the API several a couple of years ago, two, three years ago, it's one of the largest logistics company on the planet. They track every package that is being sent in JSON documents. So every track package is entries resembled in a JSON document, and they very early on came in with the next question of like, hey, we track all these packages and document in JSON documents. It will be really nice to know actually which packages are stuck, or anywhere where we have to intervene. It's like, can we do this? Can we analyze just how many packages get stuck, didn't get delivered on, the end of a day or whatever. And they found this struggle with this question a lot, they found this was really tricky to do back then, in that case in MongoDB. So they actually approached Oracle, they came over, they migrated over and they rewrote their applications to accommodate that. And there are happy JSON users in Oracle database, but if we were having this API already for them then they wouldn't have had to rewrite their applications or would we often see like worry about the rewriting the application later on. Usually migration use cases, we want to get kind of the migration done, get the data over be running, and then worry about everything else. So this would be one where they would've greatly benefited to shorten this migration time window. If we had already demo the Mongo API back then or this compatibility layer. >> That's a good use case. I mean, it's, one of the most prominent and painful, so anything you could do to help that is key. I remember like the early days of big data, NoSQL, of course was the big thing. There was a lot of confusion. No, people thought was none or not only SQL, which is kind of the more widely accepted interpretation today. But really, it's talking about data that's stored in a non-relational format. So, some people, again they thought that SQL was going to fade away, some people probably still believe that. And, we saw the rise of NoSQL and document databases, but if I understand it correctly, a premise for your Mongo DB API is you really see SQL as a main contributor over Mongo DB's document collections for analytics for example. Can you make, add some color here? Are you seeing, what are you seeing in terms of resurgence of SQL or the momentum in SQL? Has it ever really waned? What's your take? >> Yeah, no, it's a very good point. So I think there as well, we see to some extent history repeating itself from, this all has been tried beforehand with object databases, XML database, et cetera. But if we stay with the NoSQL databases, I think it speaks at length that every NoSQL database that as you write for the sensor you started with NoSQL, and then while actually we always meant, not only SQL, everybody has introduced a SQL like engine or interface. The last two actually join this family is MongoDB. Now they have just recently introduced a SQL compatibility for the aggregation pipelines, something where you can put in a SQL statement and that essentially will then work with aggregation pipeline. So they all acknowledge that SQL is powerful, for us this was always clear. SQL is a declarative language. Some argue it's the only true 4GL language out there. You don't have to code how to get the data, but you just ask the question and the rest is done for you. And, we think that as we, basically, has SQL ever diminished as you said before, if you look out there? SQL has always been a demand. Look at the various developer surveys, etc. The various top skills that are asked for SQL has never gone away. Everybody loves and likes and you wants to use SQL. And so, yeah, we don't think this has ever been, going away. It has maybe just been, put in the shadow by some hypes. But again, we had the same discussion in the 2000's with XML databases, with the same discussions in the 90's with object databases. And we have just frankly, all forgotten about it. >> I love when you guys come on and and let me do my thing and I can pretty much ask any question I want, because, I got to say, when Oracle starts talking about another company I know that company's doing well. So I like, I see Mongo in the marketplace and I love that you guys are calling it out and making some moves there. So here's the thing, you guys have a large install base and that can be an advantage, but it can also be a weight in your shoulder. These specialized cloud databases they don't have that legacy. So they can just kind of move freely about, less friction. Now, all the cloud database services they're going to have more and more automation. I mean, I think that's pretty clear and inevitable. And most if not all of the database vendors they're going to provide support for these kind of converged data models. However they choose to do that. They might do it through the ecosystem, like what Snowflake's trying to do, or bring it in the house themselves, like a watch maker that brings an in-house movement, if you will. But it's like death and taxes, you can't avoid it. It's got to happen. That's what customers want. So with all that being said, how do you see the capabilities that you have today with automation and converge capabilities, How do you see that, that playing out? What's, do you think it gives you enough of an advantage? And obviously it's an advantage, but is it enough of an advantage over the specialized cloud database vendors, where there's clearly a lot of momentum today? >> I mean, honestly yes, absolutely. I mean, we are with some of these databases 20 years ahead. And I give you concrete examples. It's like Oracle had transaction support asset transactions since forever. NoSQL players all said, oh, we don't need assets transactions, base transactions is fine. Yada, yada, yada. Mongo DB started introducing some transaction support. It comes with some limits, cannot be longer than 60 seconds, cannot touch more than a thousand documents as well, et cetera. They still will have to do some catching up there. I mean, it took us a while to get there, let's be honest. Glad We have been around for a long time. Same thing, now that happened with version five, is like we started some simple version of multi version concurrency control that comes along with asset transactions. The interesting part here is like, we've introduced this also an Oracle five, which was somewhere in the 80's before I even started using Oracle Database. So there's a lot of catching up to do. And then you look at the cloud services as well, there's actually certain, a lot of things that we kind of gotten take, we've kind of, we Oracle people have taken for granted and we kind of keep forgetting. For example, our elastic scale, you want to add one CPU, you add one CPU. Should you take downtime for that? Absolutely not. It's like, this is ridiculous. Why would you, you cannot take it downtime in a 24/7 backend system that runs the world. Take any of our customers. If you look at most of these cloud services or you want to reshape, you want to scale your cloud service, that's fine. It's just the VM under the covers, we just shut everything down, give you a VM with more CPU, and you boot it up again, downtown right there. So it's like, there's a lot of these things where we go like, well, we solved this frankly decades ago, that these cloud vendors will run into. And just to add one more point here, so it's like one thing that we see with all these migrations happening is exactly in that field. It's like people essentially started building on whether it's Mongo DB or other of these NoSQL databases or cloud databases. And eventually as these systems grow, as they ask more difficult questions, their use cases expand, they find shortcomings. Whether it's the scalability, whether it's the security aspects, the functionalities that we have, and this is essentially what drives them back to Oracle. And this is why we see essentially this popularity now of pendulum swimming towards our direction again, where people actually happily come over back and they come over to us, to get their workloads enterprise grade if you like. >> Well, It's true. I mean, I just reported on this recently, the momentum that you guys have in cloud because it is, 'cause you got the best mission critical database. You're all about maps. I got to tell you a quick story. I was at a vertical conference one time, I was on stage with Kurt Monash. I don't know if you know Kurt, but he knows this space really well. He's probably forgot and more about database than I'll ever know. But, and I was kind of busting his chops. He was talking about asset transactions. I'm like, well with NoSQL, who needs asset transactions, just to poke him. And he was like, "Are you out of your mind?" And, and he said, look it's everybody is going to head in this direction. It turned out, it's true. So I got to give him props for that. And so, my last question, if you had a message for, let's say there's a skeptical developer out there that's using Mongo DB and Atlas, what would you say to them? >> I would say go try it for yourself. If you don't believe us, we have an always free cloud tier out there. You just go to oracle.com/cloud/free. You sign up for an always free tier, spin up an autonomous database, go try it for yourself. See what's actually possible today. Don't just follow your trends on Hackernews and use a set study here or there. Go try it for yourself and see what's capable of >> All right, Gerald. Hey, thanks for coming into my firing line today. I really appreciate your time. >> Thank you for having me again. >> Good luck with the announcement. You're very welcome, and thank you for watching this CUBE conversation. This is Dave Vellante, We'll see you next time. (gentle music)

(upbeat intro jingle) >> 'Kay, welcome back everyone to theCUBE's coverage of AWS re:Invent, 2021. I'm John Furrier, your host of theCUBE, with your Matt Morgan, Vice President of Cloud Infrastructure Business Group of VMware, CUBE alumni. Matt, great to see you. Can't wait to see you in person, but thanks for coming in remotely for the virtual now hybrid CUBE for re:Invent. >> It's good to see you too, John. Thanks for having us. You know, it's our ninth year covering re:Invented, Remember the first year we went there, it was all developers, right? >> Right. >> And reminds me of the story that you guys have with AWS, you know, VMware Cloud, and VMware with vSphere pioneered operations in IT, you know, vSphere workloads, but now you move that all in the cloud. I remember Ragu when he announced that deal with Pat Gelsinger and Andy Jassy, we covered it extensively. People were like "What are they doing here? This is interesting". Boy- >> Yeah, you- >> The pundits all get it wrong. Their relationship has been blossoming. It's been really powerful, take us through the history here. >> Thanks, John, I mean, you're absolutely right. We have a phenomenal relationship with Amazon Web Services. The value of our partnership has been realized by customers all over the world, in every industry, as they embrace the seamless hybrid cloud experience powered by VMware, vSphere, and of course VM-ware Cloud Stack. Of course, we've recently expanded our operations here, including Japan and the launch of the Soccer Regions. And we're fully open for business with the U.S. Federal Government with VMware Cloud on AWS Gov Cloud. There's strong alignment across the field with new go-to-market teams on both sides and a powerful resell agreement that enables AWS sellers to take VMware Cloud on AWS and all the associated VMware services, such as VMware cloud disaster recovery, NSX vRealize Cloud Management, to their enterprise customers. And we couldn't be doing better. >> Yeah, and you brought up a lot of things there. You mentioned Outpost, mentioned Gov Cloud, you mentioned Marketplace, which means you mentioned the acronym, which is basically, I think it's called EDP Credits, which essentially the enterprise, Amazon's Salesforce working together. So, essentially full business model and technical integrations with Amazon. So, success certainly being demonstrated there. So congratulations, that being said, there's still more to do. We got this whole big wave coming on, you see the edge, you seeing multicloud, you seeing hybrid becoming the operational model, both on premises and in the cloud. And so, customers really are asking themselves "Okay, I got VMware, I got AWS Cloud, I got to secure these clouds now. I got to start putting the business model together on top of the technical architecture". You know, microservices, Kubernetes, Tansu, all the things you guys are doing, but customers want to ask you "What about securing the cloud?", this is the number one question, what's your reaction to that? >> Yeah, it's a great topic, John, at the end of the day, this is about evolving the hybrid cloud. And if you think about it, originally, the hybrid cloud was about unifying both infrastructure and operations between the on-premises world, and the public cloud world. And now what's happening, is we are seeing people embrace that in spades, and as a result of that, their Tier 1 applications are running both on-premises and in the public cloud. And with our new announced local cloud capabilities with VMware Cloud on AWS Outpost, it's leading to this whole new enterprise architecture, which we call the distributed cloud. When you look at deploying enterprise applications in a distributed cloud environment, the conversation starts with consistent networking and importantly security. So, let's talk about that for a moment. Customers are asking us "How do we secure our data when we start having infrastructure in a variety of locations? Are our applications and networks... Are they really secure when they run in these completely different environments? And importantly, when we move an application, we take it from our on-premise data center, we move it to the public cloud are the security policies... Are they moving with it? Do I need to re-architect for that?". And the real question, all of this boils down to "Are we expanding that attack surface when we move to VMware Cloud on AWS?". And so we have to come back to what do we do here to really alleviate these concerns? With data security, it's all about encryption, universal insights. We have the super root capability within our platform to ensure that everything is measured, every message from an application, every data, it's great for Chain Of Custody, Audit. Of course we have backup DR Ransomware. On the application side, of course, segmentation is super important with application centric firewalls, VPNs, tunneling, EDR, IDS, IPS. And of course, none of that matters if you have to reset everything up every time an application moves. And this is a real unique value proposition for us, it's about portability. We deliver portable security. We can move an application, the APIs are standard. You can move it up to the public cloud, your policies, your integrations, even if it's third-party integrations, they're maintained. And that really delivers the ability to say "Look, we can make sure your attack surface is not expanding, it's a controlled environment for you". And that really shrinks the risk factors associated with moving to this distributed cloud environment. >> You know, that's the really, I think the key point, I think that you brought up this infrastructure, kind of, table stakes. Which keeps rising because security's, honestly is now there's no... There's a huge... There's no perimeter. It's huge surface area. Everything has to be secured and locked down. And the big theme at re:Invent this year is data, right? So, you know, data and security all go hand in hand. And so that brings up the aspect of the edge. The edge is now booming, you seeing 5G again, you're here hearing it here at reinvent again, more and more 5G. You mentioned local services, Outpost is evolving. This is kind of the new area, and certainly, attack factor as well. So, you mentioned this whole local services. Take me through that because this becomes interesting because this is an architectural issue for enterprises to figure out, "Okay, I got to distribute a computing architecture, it's called The Cloud and multiple clouds. Now, I've got this edge, whole 'nother opening opens up the case for the architecture conversation". What's the strategy? How do you guys view the case? How do you make the case for local services? >> So, we were super excited to announce VMware Cloud on AWS Outpost. This is a local cloud as a service offering. So, let me break that down a little bit. Of course, compute at the edge is nothing new, but the problem with traditional approaches is typically edge locations may lack IT excellence. Which means there's no one there to manage the service. VMware Cloud on AWS outposts is that local cloud as a service, meaning it's fully managed and at the edge, that's a perfect fit. It's hand in glove for those types of workloads that are out, pushed all the way out, whether it's part of an agricultural deployment or an energy production facility or retail store, where there isn't that typical IT excellence. VMware cloud on AWS outposts enables customers to deploy the same Cloud instance as they're running VMware Cloud on AWS, but be able to do it out at that edge environment. And when you look at the overall value of VMware Cloud on AWS Outpost, it's about delivering a simpler, cost effective, consistent cloud experience for those on-prem environments that matches the operating model of the public cloud. Think of the places that you really want to have cloud infrastructure, where it's critical. Going back to your point on data, getting real time insights on that data, to be able to process that, we call those perishable insights. The value is the immediacy understanding that value specific to the moment it's being captured. Think about the different types of sensor environments, where data's coming off expensive equipment, that's measuring temperature and speed. Understanding that value back to the operator - really, really important. You don't have time to pipe that data up to a cloud process and send the results back down. Edge environments require that real-time stuff. So, together with AWS, we jointly deliver a fully managed service right down to the AWS hardware on which we built the VMware cloud instance. We think about where we're seeing the most interest here. You can look across all kinds of industries and use cases, and we're seeing it specifically in healthcare, out of the hospital, manufacturing for equipment monitoring, government, higher education, where those end points are typically virtualized. There are others, but these are the big ones so far. >> You know, I was just talking to an AMD executive or product marketing person on the gaming side. And they're living this right now because they're putting all the virtual collaboration in the cloud, all the data, because they have so much data and they have so much need for these special instances, whether it's GPUs, and CPUs, a mix and match. So, as instances become more special purposed, that's going to enable them to have more productivity. But then, when you have that baseline in the cloud, the edge also has processing power. So, I think people are starting to see this notion of "Okay, I'm in the cloud, but I can also have that cloud edge without moving data back to the centralized cloud and processing it at the edge with software". >> Yeah, that's true. >> This is real. >> It's super real. And the one that really resonates with customers, is one that we all understand and that's healthcare. Anytime you're in a regional environment where you're at a hospital, think of an ICU, the criticality of that data being processed, providing the insights, this is more mission critical than any other environment, because we're dealing with human lives, think about the complex compute requirements of that environment. And then look at the beauty and elegance of this system, a cloud-based system on premises, doing that compute, providing those insights, giving reality back to the clinician, so they can make those decisions. Healthcare is super, super important. And we see customers across the spectrum, looking at what's happening at the edge and embracing it, whether it's healthcare or other industries. And again, it's a perfect fit for them. >> Yeah, real quick, before we move on to what's new, I'm want to get to that, the Tansu stuff as well. What other industries are popping out? Obviously, manufacturing. What can you talk with some industries and some verticals that are really primed for this local cloud service? >> So, let's talk about manufacturing for a moment. Manufacturing is another facility oriented compute requirement that is perfectly fit, from a system and solution way like VMware cloud on AWS Outposts. Within the manufacturing environment, there's tons of very critical machines. There's inventory management, there's a combination of time management, people management, bringing it all together to ensure that process lines are moving as required, that inventory is provided at the specific moment it's needed, and to make sure that everything, especially in today's supply chain world is provided when is required. This type of capability allows an organization to bring in that sensor data, bring in that inventory data, produce applications that manage that in real time, delivering that compute. And in the manufacturing floor, again, limited IT excellence. So, this provides that capability. Another one is energy production. Think about energy production that's out in the field in North Dakota, or out on an oil rig that might be in the Gulf of Mexico. Not only are you dealing with lack of IT excellence, you're also dealing with limited connectivity. This equipment needs to be monitored and censored and the data from those sensors help drive critical decisions. And with limited connectivity, I mean, you may not even have an LTE signal, the need to do that real time is paramount, local cloud provides that. >> Yeah, and I'd also just add, because we're going to move on, but higher ED is going to be completely transformed. Well, I think that's going to be kind of like a pleat revamp. Let's get into what's new on VMware Cloud on AWS give us the update on the new things that people should know about. That's important that they should review, take us through that, what's new? >> Yeah, absolutely. So, the first is the integration with the AWS console. This is a big thing that we're delivering because VMware Cloud on AWS is a native service of AWS. I have to kind of say that twice, it's a native service of AWS. And because of that, we get the same operational and commerce experience for VMware Cloud instances as customers do with traditional AWS services. This means customers now have a choice between AWS centric operating model, which is highly relevant to DevOps and developers, or VMware centric operating model, which is very relevant to traditional operators, and IT users. VMware Cloud on AWS Gov Cloud is expanded to the U.S., East Virginia Region, and achieved aisle five certification. This new region will make the service more relevant for the Eastern Seaboard where much of the Federal Government resides. And of course with aisle five, it opens up VMware Cloud on AWS to the U.S. military and defense contractors, which is huge because there's massive cloud transformation contracts currently in play. And of course, VMware Cloud on AWS Gov Cloud provides the most secure enterprise cloud for those DOD customers, especially when they focus on those critical Tier 1 workloads. >> It's been three years since the GA of the VMware cloud on AWS, has been earlier, since you announced it> You're pumping on all cylinders, as we had predicted, others didn't, just FYI for the folks watching. What's the final vibe? End the segment with your view of what's going on with VMware Cloud on AWS? What's the bumper sticker? >> So, at the end of the day, every customer is looking to migrate and modernize their workloads. And VMWare cloud gives them that capability to do it faster than anyone else. Customers take their applications, tier 1 applications, move it to that secure distributed cloud construct, that idea of having VMware Cloud on AWS, sharing all those security policies, all of that consistent infrastructure and operations. And then they can modernize those applications, using all of those cloud services and the ability to use Tansu to containerize where applicable. We're excited about these capabilities, and our customers are adopting it faster each and every year. And we're thrilled about the traction we're had. And we're thrilled about the partnership we have with Amazon Web Services. So, lots more to come in this space. >> Lot of great stuff, people moving up the stack on the cloud, you're seeing more refactoring in the cloud. Matt Morgan, great to see you. We've been talking 'about this for years on theCUBE. Great to come on and give some insights. All happening. Infrastructure is code. And everyone's winning with containers and microservices. So, great stuff. Thanks for coming on. >> Thanks a lot, John, take care. >> Okay, Matt Morgan, the VP of Cloud Infrastructure Business Group of VMware. This theCUBE's coverage of AWS re:Invent, 2021. I'm John Furrier, your host. Thanks for watching. (upbeat outro jingle)

(upbeat intro jingle) >> 'Kay, welcome back everyone to theCUBE's coverage of AWS re:Invent, 2021. I'm John Furrier, your host of theCUBE, with your Matt Morgan, Vice President of Cloud Infrastructure Business Group of VMware, CUBE alumni. Matt, great to see you. Can't wait to see you in person, but thanks for coming in remotely for the virtual now hybrid CUBE for re:Invent. >> It's good to see you too, John. Thanks for having us. You know, it's our ninth year covering re:Invented, Remember the first year we went there, it was all developers, right? >> Right. >> And reminds me of the story that you guys have with AWS, you know, VMware Cloud, and VMware with vSphere pioneered operations in IT, you know, vSphere workloads, but now you move that all in the cloud. I remember Ragu when he announced that deal with Pat Gelsinger and Andy Jassy, we covered it extensively. People were like "What are they doing here? This is interesting". Boy- >> Yeah, you- >> The pundits all get it wrong. Their relationship has been blossoming. It's been really powerful, take us through the history here. >> Thanks, John, I mean, you're absolutely right. We have a phenomenal relationship with Amazon Web Services. The value of our partnership has been realized by customers all over the world, in every industry, as they embrace the seamless hybrid cloud experience powered by VMware, vSphere, and of course VM-ware Cloud Stack. Of course, we've recently expanded our operations here, including Japan and the launch of the Soccer Regions. And we're fully open for business with the U.S. Federal Government with VMware Cloud on AWS Gov Cloud. There's strong alignment across the field with new go-to-market teams on both sides and a powerful resell agreement that enables AWS sellers to take VMware Cloud on AWS and all the associated VMware services, such as VMware cloud disaster recovery, NSX vRealize Cloud Management, to their enterprise customers. And we couldn't be doing better. >> Yeah, and you brought up a lot of things there. You mentioned Outpost, mentioned Gov Cloud, you mentioned Marketplace, which means you mentioned the acronym, which is basically, I think it's called EDP Credits, which essentially the enterprise, Amazon's Salesforce working together. So, essentially full business model and technical integrations with Amazon. So, success certainly being demonstrated there. So congratulations, that being said, there's still more to do. We got this whole big wave coming on, you see the edge, you seeing multicloud, you seeing hybrid becoming the operational model, both on premises and in the cloud. And so, customers really are asking themselves "Okay, I got VMware, I got AWS Cloud, I got to secure these clouds now. I got to start putting the business model together on top of the technical architecture". You know, microservices, Kubernetes, Tansu, all the things you guys are doing, but customers want to ask you "What about securing the cloud?", this is the number one question, what's your reaction to that? >> Yeah, it's a great topic, John, at the end of the day, this is about evolving the hybrid cloud. And if you think about it, originally, the hybrid cloud was about unifying both infrastructure and operations between the on-premises world, and the public cloud world. And now what's happening, is we are seeing people embrace that in spades, and as a result of that, their Tier 1 applications are running both on-premises and in the public cloud. And with our new announced local cloud capabilities with VMware Cloud on AWS Outpost, it's leading to this whole new enterprise architecture, which we call the distributed cloud. When you look at deploying enterprise applications in a distributed cloud environment, the conversation starts with consistent networking and importantly security. So, let's talk about that for a moment. Customers are asking us "How do we secure our data when we start having infrastructure in a variety of locations? Are our applications and networks... Are they really secure when they run in these completely different environments? And importantly, when we move an application, we take it from our on-premise data center, we move it to the public cloud are the security policies... Are they moving with it? Do I need to re-architect for that?". And the real question, all of this boils down to "Are we expanding that attack surface when we move to VMware Cloud on AWS?". And so we have to come back to what do we do here to really alleviate these concerns? With data security, it's all about encryption, universal insights. We have the super root capability within our platform to ensure that everything is measured, every message from an application, every data, it's great for Chain Of Custody, Audit. Of course we have backup DR Ransomware. On the application side, of course, segmentation is super important with application centric firewalls, VPNs, tunneling, EDR, IDS, IPS. And of course, none of that matters if you have to reset everything up every time an application moves. And this is a real unique value proposition for us, it's about portability. We deliver portable security. We can move an application, the APIs are standard. You can move it up to the public cloud, your policies, your integrations, even if it's third-party integrations, they're maintained. And that really delivers the ability to say "Look, we can make sure your attack surface is not expanding, it's a controlled environment for you". And that really shrinks the risk factors associated with moving to this distributed cloud environment. >> You know, that's the really, I think the key point, I think that you brought up this infrastructure, kind of, table stakes. Which keeps rising because security's, honestly is now there's no... There's a huge... There's no perimeter. It's huge surface area. Everything has to be secured and locked down. And the big theme at re:Invent this year is data, right? So, you know, data and security all go hand in hand. And so that brings up the aspect of the edge. The edge is now booming, you seeing 5G again, you're here hearing it here at reinvent again, more and more 5G. You mentioned local services, Outpost is evolving. This is kind of the new area, and certainly, attack factor as well. So, you mentioned this whole local services. Take me through that because this becomes interesting because this is an architectural issue for enterprises to figure out, "Okay, I got to distribute a computing architecture, it's called The Cloud and multiple clouds. Now, I've got this edge, whole 'nother opening opens up the case for the architecture conversation". What's the strategy? How do you guys view the case? How do you make the case for local services? >> So, we were super excited to announce VMware Cloud on AWS Outpost. This is a local cloud as a service offering. So, let me break that down a little bit. Of course, compute at the edge is nothing new, but the problem with traditional approaches is typically edge locations may lack IT excellence. Which means there's no one there to manage the service. VMware Cloud on AWS outposts is that local cloud as a service, meaning it's fully managed and at the edge, that's a perfect fit. It's hand in glove for those types of workloads that are out, pushed all the way out, whether it's part of an agricultural deployment or an energy production facility or retail store, where there isn't that typical IT excellence. VMware cloud on AWS outposts enables customers to deploy the same Cloud instance as they're running VMware Cloud on AWS, but be able to do it out at that edge environment. And when you look at the overall value of VMware Cloud on AWS Outpost, it's about delivering a simpler, cost effective, consistent cloud experience for those on-prem environments that matches the operating model of the public cloud. Think of the places that you really want to have cloud infrastructure, where it's critical. Going back to your point on data, getting real time insights on that data, to be able to process that, we call those perishable insights. The value is the immediacy understanding that value specific to the moment it's being captured. Think about the different types of sensor environments, where data's coming off expensive equipment, that's measuring temperature and speed. Understanding that value back to the operator - really, really important. You don't have time to pipe that data up to a cloud process and send the results back down. Edge environments require that real-time stuff. So, together with AWS, we jointly deliver a fully managed service right down to the AWS hardware on which we built the VMware cloud instance. We think about where we're seeing the most interest here. You can look across all kinds of industries and use cases, and we're seeing it specifically in healthcare, out of the hospital, manufacturing for equipment monitoring, government, higher education, where those end points are typically virtualized. There are others, but these are the big ones so far. >> You know, I was just talking to an AMD executive or product marketing person on the gaming side. And they're living this right now because they're putting all the virtual collaboration in the cloud, all the data, because they have so much data and they have so much need for these special instances, whether it's GPUs, and CPUs, a mix and match. So, as instances become more special purposed, that's going to enable them to have more productivity. But then, when you have that baseline in the cloud, the edge also has processing power. So, I think people are starting to see this notion of "Okay, I'm in the cloud, but I can also have that cloud edge without moving data back to the centralized cloud and processing it at the edge with software". >> Yeah, that's true. >> This is real. >> It's super real. And the one that really resonates with customers, is one that we all understand and that's healthcare. Anytime you're in a regional environment where you're at a hospital, think of an ICU, the criticality of that data being processed, providing the insights, this is more mission critical than any other environment, because we're dealing with human lives, think about the complex compute requirements of that environment. And then look at the beauty and elegance of this system, a cloud-based system on premises, doing that compute, providing those insights, giving reality back to the clinician, so they can make those decisions. Healthcare is super, super important. And we see customers across the spectrum, looking at what's happening at the edge and embracing it, whether it's healthcare or other industries. And again, it's a perfect fit for them. >> Yeah, real quick, before we move on to what's new, I'm want to get to that, the Tansu stuff as well. What other industries are popping out? Obviously, manufacturing. What can you talk with some industries and some verticals that are really primed for this local cloud service? >> So, let's talk about manufacturing for a moment. Manufacturing is another facility oriented compute requirement that is perfectly fit, from a system and solution way like VMware cloud on AWS Outposts. Within the manufacturing environment, there's tons of very critical machines. There's inventory management, there's a combination of time management, people management, bringing it all together to ensure that process lines are moving as required, that inventory is provided at the specific moment it's needed, and to make sure that everything, especially in today's supply chain world is provided when is required. This type of capability allows an organization to bring in that sensor data, bring in that inventory data, produce applications that manage that in real time, delivering that compute. And in the manufacturing floor, again, limited IT excellence. So, this provides that capability. Another one is energy production. Think about energy production that's out in the field in North Dakota, or out on an oil rig that might be in the Gulf of Mexico. Not only are you dealing with lack of IT excellence, you're also dealing with limited connectivity. This equipment needs to be monitored and censored and the data from those sensors help drive critical decisions. And with limited connectivity, I mean, you may not even have an LTE signal, the need to do that real time is paramount, local cloud provides that. >> Yeah, and I'd also just add, because we're going to move on, but higher ED is going to be completely transformed. Well, I think that's going to be kind of like a pleat revamp. Let's get into what's new on VMware Cloud on AWS give us the update on the new things that people should know about. That's important that they should review, take us through that, what's new? >> Yeah, absolutely. So, the first is the integration with the AWS console. This is a big thing that we're delivering because VMware Cloud on AWS is a native service of AWS. I have to kind of say that twice, it's a native service of AWS. And because of that, we get the same operational and commerce experience for VMware Cloud instances as customers do with traditional AWS services. This means customers now have a choice between AWS centric operating model, which is highly relevant to DevOps and developers, or VMware centric operating model, which is very relevant to traditional operators, and IT users. VMware Cloud on AWS Gov Cloud is expanded to the U.S., East Virginia Region, and achieved aisle five certification. This new region will make the service more relevant for the Eastern Seaboard where much of the Federal Government resides. And of course with aisle five, it opens up VMware Cloud on AWS to the U.S. military and defense contractors, which is huge because there's massive cloud transformation contracts currently in play. And of course, VMware Cloud on AWS Gov Cloud provides the most secure enterprise cloud for those DOD customers, especially when they focus on those critical Tier 1 workloads. >> It's been three years since the GA of the VMware cloud on AWS, has been earlier, since you announced it> You're pumping on all cylinders, as we had predicted, others didn't, just FYI for the folks watching. What's the final vibe? End the segment with your view of what's going on with VMware Cloud on AWS? What's the bumper sticker? >> So, at the end of the day, every customer is looking to migrate and modernize their workloads. And VMWare cloud gives them that capability to do it faster than anyone else. Customers take their applications, tier 1 applications, move it to that secure distributed cloud construct, that idea of having VMware Cloud on AWS, sharing all those security policies, all of that consistent infrastructure and operations. And then they can modernize those applications, using all of those cloud services and the ability to use Tansu to containerize where applicable. We're excited about these capabilities, and our customers are adopting it faster each and every year. And we're thrilled about the traction we're had. And we're thrilled about the partnership we have with Amazon Web Services. So, lots more to come in this space. >> Lot of great stuff, people moving up the stack on the cloud, you're seeing more refactoring in the cloud. Matt Morgan, great to see you. We've been talking 'about this for years on theCUBE. Great to come on and give some insights. All happening. Infrastructure is code. And everyone's winning with containers and microservices. So, great stuff. Thanks for coming on. >> Thanks a lot, John, take care. >> Okay, Matt Morgan, the VP of Cloud Infrastructure Business Group of VMware. This theCUBE's coverage of AWS re:Invent, 2021. I'm John Furrier, your host. Thanks for watching. (upbeat outro jingle)

(upbeat music) >> On February 19th of this year, Barron's dropped an article declaring Oracle, a cloud giant and the article explained why the stock was a buy. Investors took notice and the stock ran up 18% over the next nine trading days and it peaked on March 9th, the day before Oracle announced its latest earnings. The company beat consensus earnings on both top-line and EPS last quarter, but investors, they did not like Oracle's tepid guidance and the stock pulled back. But it's still, as you can see, well above its pre-Barron's article price. What does all this mean? Is Oracle a cloud giant? What are its growth prospects? Now many parts of Oracle's business are growing including Fusion ERP, Fusion HCM, NetSuite, we're talking deep into the double digits, 20 plus percent growth. It's OnPrem legacy licensed business however, continues to decline and that moderates, the overall company growth because that OnPrem business is so large. So the overall Oracle's growing in the low single digits. Now what stands out about Oracle is it's recurring revenue model. That figure, the company says now it represents 73% of its revenue and that's going to continue to grow. Now two other things stood out on the earnings call to us. First, Oracle plans on increasing its CapEX by 50% in the coming quarter, that's a lot. Now it's still far less than AWS Google or Microsoft Spend on capital but it's a meaningful data point. Second Oracle's consumption revenue for Autonomous Database and Cloud Infrastructure, OCI or Oracle Cloud Infrastructure grew at 64% and 139% respectively and these two factors combined with the CapEX Spend suggest that the company has real momentum. I mean look, it's possible that the CapEx announcements maybe just optics in they're front loading, some spend to show the street that it's a player in cloud but I don't think so. Oracle's Safra Catz's usually pretty disciplined when it comes to it's spending. Now today on March 17th, Oracle announced updates towards Autonomous Data Warehouse and with me is David Floyer who has extensively researched Oracle over the years and today we're going to unpack the Oracle Autonomous Data Warehouse, ADW announcement. What it means to customers but we also want to dig into Oracle's strategy. We want to compare it to some other prominent database vendors specifically, AWS and Snowflake. David Floyer, Welcome back to The Cube, thanks for making some time for me. >> Thank you Vellante, great pleasure to be here. >> All right, I want to get into the news but I want to start with this idea of the autonomous database which Oracle's announcement today is building on. Oracle uses the analogy of a self-driving car. It's obviously powerful metaphor as they call it the self-driving database and my takeaway is that, this means that the system automatically provisions, it upgrades, it does all the patching for you, it tunes itself. Oracle claims that all reduces labor costs or admin costs by 90%. So I ask you, is this the right interpretation of what Oracle means by autonomous database? And is it real? >> Is that the right interpretation? It's a nice analogy. It's a test to that analogy, isn't it? I would put it as the first stage of the Autonomous Data Warehouse was to do the things that you talked about, which was the tuning, the provisioning, all of that sort of thing. The second stage is actually, I think more interesting in that what they're focusing on is making it easy to use for the end user. Eliminating the requirement for IT, staff to be there to help in the actual using of it and that is a very big step for them but an absolutely vital step because all of the competition focusing on ease of use, ease of use, ease of use and cheapness of being able to manage and deploy. But, so I think that is the really important area that Oracle has focused on and it seemed to have done so very well. >> So in your view, is this, I mean you don't really hear a lot of other companies talking about this analogy of the self-driving database, is this unique? Is it differentiable for Oracle? If so, why, or maybe you could help us understand that a little bit better. >> Well, the whole strategy is unique in its breadth. It has really brought together a whole number of things together and made it of its type the best. So it has a single, whole number of data sources and database types. So it's got a very broad range of different ways that you can look at the data and the second thing that is also excellent is it's a platform. It is fully self provisioned and its functionality is very, very broad indeed. The quality of the original SQL and the query languages, etc, is very, very good indeed and it's a better agent to do joints for example, is excellent. So all of the building blocks are there and together with it's sharing of the same data with OLTP and inference and in memory data paces as well. All together the breadth of what they have is unique and very, very powerful. >> I want to come back to this but let's get into the news a little bit and the announcement. I mean, it seems like what's new in the autonomous data warehouse piece for Oracle's new tooling around four areas that so Andy Mendelsohn, the head of this group instead of the guy who releases his baby, he talked about four things. My takeaway, faster simpler loads, simplified transforms, autonomous machine learning models which are facilitating, What do you call it? Citizen data science and then faster time to insights. So tooling to make those four things happen. What's your take and takeaways on the news? >> I think those are all correct. I would add the ease of use in terms of being able to drag and drop, the user interface has been dramatically improved. Again, I think those, strategically are actually more important that the others are all useful and good components of it but strategically, I think is more important. There's ease of use, the use of apex for example, are more important. And, >> Why are they more important strategically? >> Because they focus on the end users capability. For example, one of other things that they've started to introduce is Python together with their spatial databases, for example. That is really important that you reach out to the developer as they are and what tools they want to use. So those type of ease of use things, those types of things are respecting what the end users use. For example, they haven't come out with anything like click or Tableau. They've left that there for that marketplace for the end user to use what they like best. >> Do you mean, they're not trying to compete with those two tools. They indeed had a laundry list of stuff that they supported, Talend, Tableau, Looker, click, Informatica, IBM, I had IBM there. So their claim was, hey, we're open. But so that's smart. That's just, hey, they realized that people use these tools. >> I'm trying to exclude other people, be a platform and be an ecosystem for the end users. >> Okay, so Mendelsohn who made the announcement said that Oracle's the smartphone of databases and I think, I actually think Alison kind of used that or maybe that was us planing to have, I thought he did like the iPhone of when he announced the exit data way back when the integrated hardware and software but is that how you see it, is Oracle, the smartphone of databases? >> It is, I mean, they are trying to own the complete stack, the hardware with the exit data all the way up to the databases at the data warehouses and the OLTP databases, the inference databases. They're trying to own the complete stack from top to bottom and that's what makes autonomy process possible. You can make it autonomous when you control all of that. Take away all of the requirements for IT in the business itself. So it's democratizing the use of data warehouses. It is pushing it out to the lines of business and it's simplifying it and making it possible to push out so that they can own their own data. They can manage their own data and they do not need an IT person from headquarters to help them. >> Let's stay in this a little bit more and then I want to go into some of the competitive stuff because Mendelsohn mentioned AWS several times. One of the things that struck me, he said, hey, we're basically one API 'cause we're doing analytics in the cloud, we're doing data in the cloud, we're doing integration in the cloud and that's sort of a big part of the value proposition. He made some comparisons to Redshift. Of course, I would say, if you can't find a workload where you beat your big competitor then you shouldn't be in this business. So I take those things with a grain of salt but one of the other things that caught me is that migrating from OnPrem to Oracle, Oracle Cloud was very simple and I think he might've made some comparisons to other platforms. And this to me is important because he also brought in that Gartner data. We looked at that Gardner data when they came out with it in the operational database class, Oracle smoked everybody. They were like way ahead and the reason why I think that's important is because let's face it, the Mission Critical Workloads, when you look at what's moving into AWS, the Mission Critical Workloads, the high performance, high criticality OLTP stuff. That's not moving in droves and you've made the point often that companies with their own cloud particularly, Oracle you've mentioned this about IBM for certain, DB2 for instance, customers are going to, there should be a lower risk environment moving from OnPrem to their cloud, because you could do, I don't think you could get Oracle RAC on AWS. For example, I don't think EXIF data is running in AWS data centers and so that like component is going to facilitate migration. What's your take on all that spiel? >> I think that's absolutely right. You all crown Jewels, the most expensive and the most valuable applications, the mission-critical applications. The ones that have got to take a beating, keep on taking. So those types of applications are where Oracle really shines. They own a very large high percentage of those Mission Critical Workloads and you have the choice if you're going to AWS, for example of either migrating to Oracle on AWS and that is frankly not a good fit at all. There're a lot of constraints to running large systems on AWS, large mission critical systems. So that's not an option and then the option, of course, that AWS will push is move to a Roller, change your way of writing applications, make them tiny little pieces and stitch them all together with microservices and that's okay if you're a small organization but that has got a lot of problems in its own, right? Because then you, the user have to stitch all those pieces together and you're responsible for testing it and you're responsible for looking after it. And that as you grow becomes a bigger and bigger overhead. So AWS, in my opinion needs to have a move towards a tier-one database of it's own and it's not in that position at the moment. >> Interesting, okay. So, let's talk about the competitive landscape and the choices that customers have. As I said, Mendelssohn mentioned AWS many times, Larry on the calls often take shy, it's a compliment to me. When Larry Ellison calls you out, that means you've made it, you're doing well. We've seen it over the years, whether it's IBM or Workday or Salesforce, even though Salesforce's big Oracle customer 'cause AWS, as we know are Oracle customer as well, even though AWS tells us they've off called when you peel the onion >> Five years should be great, some of the workers >> Well, as I said, I believe they're still using Oracle in certain workloads. Way, way, we digress. So AWS though, they take a different approach and I want to push on this a little bit with database. It's got more than a dozen, I think purpose-built databases. They take this kind of right tool for the right job approach was Oracle there converging all this function into a single database. SQL JSON graph databases, machine learning, blockchain. I'd love to talk about more about blockchain if we have time but seems to me that the right tool for the right job purpose-built, very granular down to the primitives and APIs. That seems to me to be a pretty viable approach versus kind of a Swiss Army approach. How do you compare the two? >> Yes, and it is to many initial programmers who are very interested for example, in graph databases or in time series databases. They are looking for a cheap database that will do the job for a particular project and that makes, for the program or for that individual piece of work is making a very sensible way of doing it and they pay for ads on it's clear cloud dynamics. The challenge as you have more and more data and as you're building up your data warehouse in your data lakes is that you do not want to have to move data from one place to another place. So for example, if you've got a Roller,, you have to move the database and it's a pretty complicated thing to do it, to move it to Redshift. It's a five or six steps to do that and each of those costs money and each of those take time. More importantly, they take time. The Oracle approach is a single database in terms of all the pieces that obviously you have multiple databases you have different OLTP databases and data warehouse databases but as a single architecture and a single design which means that all of the work in terms of moving stuff from one place to another place is within Oracle itself. It's Oracle that's doing that work for you and as you grow, that becomes very, very important. To me, very, very important, cost saving. The overhead of all those different ones and the databases themselves originate with all as open source and they've done very well with it and then there's a large revenue stream behind the, >> The AWS, you mean? >> Yes, the original database is in AWS and they've done a lot of work in terms of making it set with the panels, etc. But if a larger organization, especially very large ones and certainly if they want to combine, for example data warehouse with the OLTP and the inference which is in my opinion, a very good thing that they should be trying to do then that is incredibly difficult to do with AWS and in my opinion, AWS has to invest enormously in to make the whole ecosystem much better. >> Okay, so innovation required there maybe is part of the TAM expansion strategy but just to sort of digress for a second. So it seems like, and by the way, there are others that are doing, they're taking this converged approach. It seems like that is a trend. I mean, you certainly see it with single store. I mean, the name sort of implies that formerly MemSQL I think Monte Zweben of splice machine is probably headed in a similar direction, embedding AI in Microsoft's, kind of interesting. It seems like Microsoft is willing to build this abstraction layer that hides that complexity of the different tooling. AWS thus far has not taken that approach and then sort of looking at Snowflake, Snowflake's got a completely different, I think Snowflake's trying to do something completely different. I don't think they're necessarily trying to take Oracle head-on. I mean, they're certainly trying to just, I guess, let's talk about this. Snowflake simplified EDW, that's clear. Zero to snowflake in 90 minutes. It's got this data cloud vision. So you sign on to this Snowflake, speaking of layers they're abstracting the complexity of the underlying cloud. That's what the data cloud vision is all about. They, talk about this Global Mesh but they've not done a good job of explaining what the heck it is. We've been pushing them on that, but we got, >> Aspiration of moment >> Well, I guess, yeah, it seems that way. And so, but conceptually, it's I think very powerful but in reality, what snowflake is doing with data sharing, a lot of reading it's probably mostly read-only and I say, mostly read-only, oh, there you go. You'll get better but it's mostly read and so you're able to share the data, it's governed. I mean, it's exactly, quite genius how they've implemented this with its simplicity. It is a caching architecture. We've talked about that, we can geek out about that. There's good, there's bad, there's ugly but generally speaking, I guess my premise here I would love your thoughts. Is snowflakes trying to do something different? It's trying to be not just another data warehouse. It's not just trying to compete with data lakes. It's trying to create this data cloud to facilitate data sharing, put data in the hands of business owners in terms of a product build, data product builders. That's a different vision than anything I've seen thus far, your thoughts. >> I agree and even more going further, being a place where people can sell data. Put it up and make it available to whoever needs it and making it so simple that it can be shared across the country and across the world. I think it's a very powerful vision indeed. The challenge they have is that the pieces at the moment are very, very easy to use but the quality in terms of the, for example, joints, I mentioned, the joints were very powerful in Oracle. They don't try and do joints. They, they say >> They being Snowflake, snowflake. Yeah, they don't even write it. They would say use another Postgres >> Yeah. >> Database to do that. >> Yeah, so then they have a long way to go. >> Complex joints anyway, maybe simple joints, yeah. >> Complex joints, so they have a long way to go in terms of the functionality of their product and also in my opinion, they sure be going to have more types of databases inside it, including OLTP and they can do that. They have obviously got a great market gap and they can do that by acquisition as well as they can >> They've started. I think, I think they support JSON, right. >> Do they support JSON? And graph, I think there's a graph database that's either coming or it's there, I can't keep all that stuff in my head but there's no reason they can't go in that direction. I mean, in speaking to the founders in Snowflake they were like, look, we're kind of new. We would focus on simple. A lot of them came from Oracle so they know all database and they know how hard it is to do things like facilitate complex joints and do complex workload management and so they said, let's just simplify, we'll put it in the cloud and it will spin up a separate data warehouse. It's a virtual data warehouse every time you want one to. So that's how they handle those things. So different philosophy but again, coming back to some of the mission critical work and some of the larger Oracle customers, they said they have a thousand autonomous database customers. I think it was autonomous database, not ADW but anyway, a few stood out AON, lift, I think Deloitte stood out and as obviously, hundreds more. So we have people who misunderstand Oracle, I think. They got a big install base. They invest in R and D and they talk about lock-in sure but the CIO that I talked to and you talked to David, they're looking for business value. I would say that 75 to 80% of them will gravitate toward business value over the fear of lock-in and I think at the end of the day, they feel like, you know what? If our business is performing, it's a better business decision, it's a better business case. >> I fully agree, they've been very difficult to do business with in the past. Everybody's in dread of the >> The audit. >> The knock on the door from the auditor. >> Right. >> And that from a purchasing point of view has been really bad experience for many, many customers. The users of the database itself are very happy indeed. I mean, you talk to them and they understand why, what they're paying for. They understand the value and in terms of availability and all of the tools for complex multi-dimensional types of applications. It's pretty well, the only game in town. It's only DB2 and SQL that had any hope of doing >> Doing Microsoft, Microsoft SQL, right. >> Okay, SQL >> Which, okay, yeah, definitely competitive for sure. DB2, no IBM look, IBM lost its dominant position in database. They kind of seeded that. Oracle had to fight hard to win it. It wasn't obvious in the 80s who was going to be the database King and all had to fight. And to me, I always tell people the difference is that the chairman of Oracle is also the CTO. They spend money on R and D and they throw off a ton of cash. I want to say something about, >> I was just going to make one extra point. The simplicity and the capability of their cloud versions of all of this is incredibly good. They are better in terms of spending what you need or what you use much better than AWS, for example or anybody else. So they have really come full circle in terms of attractiveness in a cloud environment. >> You mean charging you for what you consume. Yeah, Mendelsohn talked about that. He made a big point about the granularity, you pay for only what you need. If you need 33 CPUs or the other databases you've got to shape, if you need 33, you've got to go to 64. I know that's true for everyone. I'm not sure if that's true too for snowflake. It may be, I got to dig into that a little bit, but maybe >> Yes, Snowflake has got a front end to hiding behind. >> Right, but I didn't want to push it that a little bit because I want to go look at their pricing strategies because I still think they make you buy, I may be wrong. I thought they make you still do a one-year or two-year or three-year term. I don't know if you can just turn it off at any time. They might allow, I should hold off. I'll do some more research on that but I wanted to make a point about the audits, you mentioned audits before. A big mistake that a lot of Oracle customers have made many times and we've written about this, negotiating with Oracle, you've got to bring your best and your brightest when you negotiate with Oracle. Some of the things that people didn't pay attention to and I think they've sort of caught onto this is that Oracle's SOW is adjudicate over the MSA, a lot of legal departments and procurement department. Oh, do we have an MSA? With all, Yes, you do, okay, great and because they think the MSA, they then can run. If they have an MSA, they can rubber stamp it but the SOW really dictateS and Oracle's gotcha there and they're really smart about that. So you got to bring your best and the brightest and you've got to really negotiate hard with Oracle, you get trouble. >> Sure. >> So it is what it is but coming back to Oracle, let's sort of wrap on this. Dominant position in mission critical, we saw that from the Gartner research, especially for operational, giant customer base, there's cloud-first notion, there's investing in R and D, open, we'll put a question Mark around that but hey, they're doing some cool stuff with Michael stuff. >> Ecosystem, I put that, ecosystem they're promoting their ecosystem. >> Yeah, and look, I mean, for a lot of their customers, we've talked to many, they say, look, there's actually, a tail at the tail way, this saves us money and we don't have to migrate. >> Yeah. So interesting, so I'll give you the last word. We started sort of focusing on the announcement. So what do you want to leave us with? >> My last word is that there are platforms with a certain key application or key parts of the infrastructure, which I think can differentiate themselves from the Azures or the AWS. and Oracle owns one of those, SAP might be another one but there are certain platforms which are big enough and important enough that they will, in my opinion will succeed in that cloud strategy for this. >> Great, David, thanks so much, appreciate your insights. >> Good to be here. Thank you for watching everybody, this is Dave Vellante for The Cube. We'll see you next time. (upbeat music)

>> Narrator: From the Cube Studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> Hi, and welcome to this CUBE conversation, I'm Stu Min and I'm coming to you from our Boston area studio, we've been digging in with the Pensando team, understand how they're fitting into the cloud, multi-cloud, edge discussion, really thrilled to welcome to the program, first time guest, Silvano Gai, he's a fellow with Pensando. Silvano, really nice to see you again, thanks so much for joining us on theCUBE. >> Stuart, it's so nice to see you, we used to work together many years ago and that was really good and is really nice to come to you from Oregon, from Bend, Oregon. A beautiful town in the high desert of Oregon. >> I do love the Pacific North West, I miss the planes and the hotels, I should say, I don't miss the planes and the hotels, but going to see some of the beautiful places is something I do miss and getting to see people in the industry I do like. As you mentioned, you and I crossed paths back through some of the spin-ins, back when I was working for a very large storage company, you were working for SISCO, you were known for writing the book, you were a professor in Italy, many of the people that worked on some of those technologies were your students. But Silvano, my understanding is you retired so, maybe share for our audience, what brought you out of that retirement and into working once again with some of your former colleagues and on the Pensando opportunity. >> I did retire for a while, I retired in 2011 from Cisco if I remember correctly. But at the end of 2016, beginning of 2017, some old friend that you may remember and know called me to discuss some interesting idea, which was basically the seed idea that is behind the Pensando product and their idea were interesting, what we built, of course, is not exactly the original idea because you know product evolve over time, but I think we have something interesting that is adequate and probably superb for the new way to design the data center network, both for enterprise and cloud. >> All right, and Silvano, I mentioned that you've written a number of books, really the authoritative look on when some new products had been released before. So, you've got a new book, "Building a Future-Proof Cloud Infrastructure," and look at you, you've got the physical copy, I've only gotten the soft version. The title, really interesting. Help us understand how Pensando's platform is meeting that future-proof cloud infrastructure that you discuss. >> Well, network have evolved dramatically in the data center and in the cloud. You know, now the speed of classical server in enterprise is probably 25 gigabits, in the cloud we are talking of 100 gigabit of speed for a server, going to 200 gigabit. Now, the backbone are ridiculously fast. We no longer use Spanning Tree and all the stuff, we no longer use access code aggregation. We switched to closed network, and with closed network, we have huge enormous amount of bandwidth and that is good but it also imply that is not easy to do services in a centralized fashion. If you want to do a service in a centralized fashion, what you end up doing is creating a giant bottleneck. You basically, there is this word that is being used, that is trombone or tromboning. You try to funnel all this traffic through the bottleneck and this is not really going to work. The only place that you can really do services is at the edge, and this is not an invention, I mean, even all the principles of cloud is move everything to the edge and maintain the network as simple as possible. So, we approach services with the same general philosophy. We try to move services to the edge, as close as possible to the server and basically at the border between the sever and the network. And when I mean services I mean three main categories of services. The networking services of course, there is the basic layer, two-layer, three stuff, plus the bonding, you know VAMlog and what is needed to connect a server to a network. But then there is the overlay, overlay like the xLAN or Geneva, very very important, basically to build a cloud infrastructure, and that are basically the network service. We can have others but that, sort of is the core of a network service. Some people want to run BGP layers, some people don't want to run BGP. There may be a VPN or kind of things like that but that is the core of a network service. Then of course, and we go back to the time we worked together, there are storage services. At that time, we were discussing mostly about fiber tunnel, now the BUS world is clearly NVMe, but it's not just the BUS world, it's really a new way of doing storage, and is very very interesting. So, NVMe kind of service are very important and NVMe as a version that is called NVMeOF, over fiber. Which is basically, sort of remote version of NVMe. And then the third, least but not last, most important category probably, is security. And when I say that security is very very important, you know, the fact that security is very important is clear to everybody in our day, and I think security has two main branches in terms of services. There is the classical firewall and micro-segmentation, in which you basically try to enforce the fact that only who is allowed to access something can access something. But you don't, at that point, care too much about the privacy of the data. Then there is the other branch that encryption, in which you are not trying to enforce to decide who can access or not access the resource, but you are basically caring about the privacy of the data, encrypting the data so that if it is hijacked, snooped or whatever, it cannot be decoded. >> Eccellent, so Silvano, absolutely the edge is a huge opportunity. When someone looks at the overall solution and say you're putting something in the edge, you know, they could just say, "This really looks like a NIC." You talked about some of the previous engagement we'd worked on, host bus adapters, smart NICs and the like. There were some things we could build in but there were limits that we had, so, what differentiates the Pensando solution from what we would traditionally think of as an adapter card in the past? >> Well, the Pensando solution has two main, multiple pieces but in term of hardware, has two main pieces, there is an ASIC that we call copper internally. That ASIC is not strictly related to be used only in an adapter form, you can deploy it also in other form factors in another part of the network in other embodiment, et cetera. And then there is a card, the card has a PCI-E interface and sit in a PCI-E slot. So yes, in that sense, somebody can can call it a NIC and since it's a pretty good NIC, somebody can call it a smart NIC. We don't really like that two terms, we prefer to call it DSC, domain specific card, but the real term that I like to use is domain specific hardware, and I like to use domain specific hardware because it's the same term that Hennessy and Patterson use in a beautiful piece of literature that is the Turing Award lecture. It's on the internet, it's public, I really ask everybody to go and try to find it and listen to that beautiful piece of literature, modern literature on computer architecture. The Turing Award lecture of Hennessy and Patterson. And they have introduced the concept of domain specific hardware, and they explain also the justification for why now is important to look at domain specific hardware. And the justification is basically in a nutshell and we can go more deep if you're interested, but in a nutshell is that the specing, that is the single tried performer's measurement of a CPU, is not growing fast at all, is only growing nowadays like a few point percent a year, maybe 4% per year. And with this slow grow, over specing performance of a core, you know the core need to be really used for user application, for customer application, and all what is known as Sentian can be moved to some domain specific hardware that can do that in a much better fashion, and by no mean I imply that the DSC is the best example of domain specific hardware. The best example of domain specific hardware is in front of all of us, and are GPUs. And not GPUs for graphic processing which are also important, but GPU used basically for artificial intelligence, machine learning inference. You know, that is a piece of hardware that has shown that something can be done with performance that the purpose processor can do. >> Yeah, it's interesting right. If you term back the clock 10 or 15 years ago, I used to be in arguments, and you say, "Do you build an offload, "or do you let it happen is software." And I was always like, "Oh, well Moore's law with mean that, "you know, the software solution will always win, "because if you bake it in hardware, it's too slow." It's a very different world today, you talk about how fast things speed up. From your customer standpoint though, often some of those architectural things are something that I've looked for my suppliers to take care of that. Speak to the use case, what does this all mean from a customer stand point, what are some of those early use cases that you're looking at? >> Well, as always, you get a bit surprised by the use cases, in the sense that you start to design a product thinking that some of the most cool thing will be the dominant use cases, and then you discover that something that you have never really fought have the most interesting use case. One that we have fought about since day one, but it's really becoming super interesting is telemetry. Basically, measuring everything in the network, and understanding what is happening in the network. I was speaking with a friend the other day, and the friend was asking me, "Oh, but we have SNMP for many many years, "which is the difference between SNMP and telemetry?" And the difference is to me, the real difference is in SNMP or in many of these management protocol, you involve a management plan, you involve a control plan, and then you go to read something that is in the data plan. But the process is so inefficient that you cannot really get a huge volume of data, and you cannot get it practically enough, with enough performance. Doing telemetry means thinking a data path, building a data path that is capable of not only measuring everything realtime, but also sending out that measurement without involving anything else, without involving the control path and the management path so that the measurement becomes really very efficient and the data that you stream out becomes really usable data, actionable data in realtime. So telemetry is clearly the first one, is important. One that you honestly, we had built but we weren't thinking this was going to have so much success is what we call Bidirectional ERSPAN. And basically, is just the capability of copying data. And sending data that the card see to a station. And that is very very useful for replacing what are called TAP network, Which is just network, but many customer put in parallel to the real network just to observe the real network and to be able to troubleshoot and diagnose problem in the real network. So, this two feature telemetry and ERSPAN that are basically troubleshooting feature are the two features that are beginning are getting more traction. >> You're talking about realtime things like telemetry. You know, the applications and the integrations that you need to deal with are so important, back in some of the previous start-ups that you done was getting ready for, say how do we optimize for virtualization, today you talk cloud-native architectures, streaming, very popular, very modular, often container based solutions and things change constantly. You look at some of these architectures, it's not a single thing that goes on for a long period of time, but it's lots of things that happen over shorter periods of time. So, what integrations do you need to do, and what architecturally, how do you build things to make them as you talk, future-proof for these kind of cloud architectures? >> Yeah, what I mentioned were just the two low hanging fruit, if you want the first two low hanging fruit of this architecture. But basically, the two that come immediately after and where there is a huge amount of radio are distributor's state for firewall, with micro-segmentation support. That is a huge topic in itself. So important nowadays that is absolutely fundamental to be able to build a cloud. That is very important, and the second one is wire rate encryption. There is so much demand for privacy, and so much demand to encrypt the data. Not only between data center but now also inside the data center. And when you look at a large bank for example. A large bank is no longer a single organization. A large bank is multiple organizations that are compartmentalized by law. That need to keep things separate by law, by regulation, by FCC regulation. And if you don't have encryption, and if you don't have distributed firewall, is really very difficult to achieve that. And then you know, there are other applications, we mentioned storage NVME, and is a very nice application, and then we have even more, if you go to look at load balance in between server, doing compression for storage and other possible applications. But I sort of lost your real question. >> So, just part of the pieces, when you look at integrations that Pensando needs to do, for maybe some of the applications that you would tie in to any of those that come to mind? >> Yeah, well for sure. It depends, I see two main branches again. One is the cloud provider, and one are the enterprise. In the cloud provider, basically this cloud provider have a huge management infrastructure that is already built and they want just the card to adapt to this, to be controllable by this huge management infrastructure. They already know which rule they want to send to the card, they already know which feature they want to enable on the card. They already have all that, they just want the card to provide the data plan performers for that particular feature. So they're going to build something particular that is specific for that particular cloud provider that adapt to that cloud provider architecture. We want the flexibility of having an API on the card that is like a rest API or a gRPC which they can easily program, monitor and control that card. When you look at the enterprise, the situation is different. Enterprise is looking to at two things. Two or three things. The first thing is a complete solution. They don't want to, they don't have the management infrastructure that they have built like a cloud provider. They want a complete solution that has the card and the management station and there's all what is required to make from day one, a working solution, which is absolutely correct in an enterprise environment. They also want integration, and integration is the tool that they already have. If you look at main enterprise, one of a dominant presence is clearly VMware virtualization in terms of ESX and vSphere and NSX. And so most of the customer are asking us to integrate with VMware, which is a very reasonable demand. And then of course, there are other player, not so much in the virtualization's space, but for example, in the data collections space, and the data analysis space, and for sure Pensando doesn't want to reinvent the wheel there, doesn't want to build a data collector or data analysis engine and whatever, there is a lot of work, and there are a lot out there, so integration with things like Splunk for example are kind of natural for Pensando. >> Eccellent, so wait, you talked about some of the places where Pensando doesn't need to reinvent the wheel, you talk through a lot of the different technology pieces. If I had to have you pull out one, what would you say is the biggest innovation that Pensando has built into the platform. >> Well, the biggest innovation is this P4 architecture. And the P4 architecture was a sort of gift that was given us in the sense that it was not invented for what we use it. P4 was basically invented to have programmable switches. The first big P4 company was clearly Barefoot that then was acquired by Intel and Barefoot built a programmable switch. But if you look at the reality of today, the network, most of the people want the network to be super easy. They don't want to program anything into the network. They want to program everything at the edge, they want to put all the intelligence and the programmability of the edge, so we borrowed the P4 architecture, which is fantastic programmable architecture and we implemented that yet. It's also easier because the bandwidth is clearly more limited at the edge compared to being in the core of a network. And that P4 architecture give us a huge advantage. If you, tomorrow come up with the Stuart Encapsulation Super Duper Technology, I can implement in the copper The Stuart, whatever it was called, Super Duper Encapsulation Technology, even when I design the ASIC I didn't know that encapsulation exists. Is the data plan programmability, is the capability to program the data plan and programming the data plan while maintaining wire-speed performance, which I think is the biggest benefit of Pensando. >> All right, well Silvano, thank you so much for sharing, your journey with Pensando so far, really interesting to dig into it and absolutely look forward to following progress as it goes. >> Stuart, it's been really a pleasure to talk with you, I hope to talk with you again in the near future. Thank you so much. >> All right, and thank you for watching theCUBE, I'm Stu Miniman, thanks for watching. (upbeat music)

(upbeat music) >> Welcome back to theCUBE everybody. This is Dave Vellante. We've been covering the transformation of Oracle Consulting and really its rebirth. And I'm here with Chris Fox, who's the Group Vice President for Enterprise Cloud Architects and Chief Technologist for the North America Tech Cloud at Oracle. Chris, thanks so much for coming on theCUBE. >> Thanks Dave, glad to be here. >> So I love this title. I mean years ago there was no such thing as a Cloud Architect, certainly there were Chief Technologists but so you are really-- Those are your peeps, is that right? >> That's right. That's right. That's really, my team and I, that's all we do. So our focus is really helping our customers take this journey from when they were on premise to really transforming with cloud. And when we think about cloud, really for us, it's a combination. It's our hybrid cloud which happens to be on premise and then of course the true public cloud like most people are familiar with. So, very exciting journey and frankly I've seen just a lot of success for our customers. >> interesting that you hear conversations like, "Oh every company is a software company" which by the way we believe. Everybody's got a some kind of SaaS offering, but it really used to be the application, heads within organizations that had a lot of the power, still do, but of course you have cloud native developers etc. And now you have this new role of Cloud Architects, they've got to align, essentially have to provide infrastructure and capabilities so that you can be agile from a development standpoint. I wonder if you can talk about that dynamic of how the roles have evolved in the last several years. >> Yeah, you know it's very interesting now because as Oracle we spend a lot of our time with those applications owners. As a leader in SaaS right now, SaaS ERP, HCM. You just start walking through the list, they're transforming their organizations. They're trying to make their lives, much more efficient, better for their employees or customers etc. On the other side of the spectrum, we have the cloud native development teams and they're looking at better ways to deploy, develop applications, roll out new features at scale, roll out new pipelines. But Dave, what I think we're seeing at Oracle though, because we're so connected with SaaS and then we're also connected with the traditional applications that have run the business for years, the legacy applications that have been servicing us for 20 years and then the cloud native developers. So what my team and I are constantly focused on now is things like digital transformation and really wiring up all three of these across. So if we think of like a customer outcome, like I want to have a package delivered to me from a retailer, that actual process flow could touch a brand new cloud native site from e-commerce. It could touch essentially, maybe a traditional application that used to be on prem that's now on the cloud and then it might even use some new SaaS application maybe for maybe a procurement process or delivery vehicle and scheduling. So what my team does, we actually connect all three. So, what I always mention to my team and all of our customers, we have to be able to service all three of those constituents and really think about process flows. So I take the cloud native developer, we help them become efficient. We take the person who's been running that traditional application and we help them become more efficient. And then we have the SaaS applications which are now rolling out new features on a quarterly basis and the whole new delivery model. But the real key is connecting all three of these into a business process flow that makes the customer's life much more efficient. >> So what you're saying is that these Cloud Architects and the sort of modern day Chief Technologists, they're multi tool players. It's not just about cloud, it's about connecting that cloud to, whether the system's on prem or other clouds. Is that right? >> It is. You know and one thing that we're seeing too Dave, is that we know it's multi cloud. So it could be Oracle's cloud, hopefully it's always Oracle's cloud, but we don't expect that. So as architects, we certainly have to take a look at what is it that we're trying to optimize? What's the outcome we're looking for? And then be able to work across these teams, and I think what makes it probably most fun and exciting, on one day in one morning, let's say, you could be talking to the cloud native developer team. Talking about Kubernetes, CI/CD pipelines, all the great technologies that help us roll out applications and features faster. Then you'll go to a traditional, maybe Oracle E-Business suite job. This is something that's been running on prem maybe for 20 years, and it's really still servicing the business. And then you have another team that maybe is rolling out a SaaS application from Oracle. And literally all three teams are connected by a process flow. So the question is, how do we optimize all three on behalf of either the customer, the employee, the supplier? And that's really the job for the Oracle Cloud Architect. Which I think, really good, that's different than the other cloud because for the most part, we actually do offer SaaS, we offer platform, we offer infrastructure and we offer the hybrid cloud on prem. So it's a common conversation. How do we optimize all these? >> So I want to get into this cloud conversation a little bit. You guys are used to this term last mover advantage. I got to ask you about it. How is being last an advantage? But let me start there. >> Yeah, that's a great question. I mean, so frankly speaking I think that-- So Oracle has been developing, what's interesting is our SaaS applications for many, many, many years, and where we began this journey is looking at SaaS. And then we started with platform. Right after that we started saying how do we augment SaaS? This OCI for us or Oracle Cloud Infrastructure Gen 2 could be considered a last mover advantage. What does that mean? We join this cloud journey later than the others but because of our heritage, of the workloads we've been running, right? We've been running enterprise scale workloads for years, the cloud itself has been phenomenal, right? It's easier to use, pay for what you use, elastic etc. These are all phenomenal features, fell. And based on our enterprise heritage it wasn't delivering resilience at scale, even for like the traditional applications we've known on prem forever. People always say, "Chris we want to get out of the data center. "We're going zero data center." And I always say, "Well, how are you going to handle that back office stuff?" Right? The stuff that's really big, it's cranky, doesn't handle just, instances dying or things going away too easily. It needs predictable performance. It needs scale. It absolutely needs security and ultimately a lot of these applications truly have relied on an Oracle database. The Oracle database has it's own specific characteristics that it needs to run really well. So we actually looked at the cloud and we said, let's take the first generation clouds, which are doing great, but let's add the features that specifically, a lot of times, the Oracle workload needed in order to run very well and in a cost effective manner. So that's what we mean when we say, last mover advantage. We said, let's take the best of the clouds that are out there today. Let's look at the workloads that, frankly Oracle runs and has been running for years, what our customers needed and then let's build those features right into this next version of the cloud, we can service the enterprise. So our goal, honestly what's interesting is, even that first discussion we had about cloud native, and legacy applications, and also the new SaaS applications, we built a cloud that handles all three use cases, at scale resiliently in a very secure manner, and I don't know of any other cloud that's handling those three use cases, all in, we'll call it the same tendency for us at Oracle. >> Let's unpack that a little bit and get into, sort of, trying to understand the strategy and I want to frame it. So you were the last really to enter the cloud market, let's sort of agree on that. >> Chris: Yup. >> And you kind of built it from the ground up. And it's just too expensive now. The CapEx required to get into cloud is just astronomical. Now, even for a SaaS company, there's no sense. If you're a new SaaS company, you're going to run it in the cloud. Somebody else's cloud. There are some SaaS companies that of course run their own data centers but they're fewer and further between. But so, and I've also said that your advantage relative to the hyper scalers is that you've got this big SaaS estate and it somewhat insulates you, actually more than somewhat. Largely insulates you from the race to the bottom. On compute and storage, cost per bit kind of thing. But my question is, why was it was it important for Oracle, and is it important for Oracle and it's customers, that it had to participate in IaaS and PaaS and SaaS? Why not just the last two layers of that? What does that give you from a strategic advantage standpoint and what does that do for your customer? >> Yeah, great question. So the number one reason why we needed to have all three was that we have so many customers to today that are in a data center. They're running a lot of our workloads on premise and they absolutely are trying to find a better way to deliver a lower cost services to their customers. And, so, we couldn't just say let's just-- everyone needs to just become net new. Everyone just needs to ditch the old and go just to brand new alone. Too hard, too expensive at times. So we said, let's give us customers the ultimate amount of choice. So, let's even go back again to that developer conversation in SaaS. If you didn't have IaaS, we couldn't help customers achieve a zero data center strategy with their traditional application. We'll call it Peoplesoft, or JD Edwards or E-Business suite or even-- there's some massive applications that are running on the Oracle cloud right now that are custom applications built on the Oracle database. What they want is they said, "Give me the lowest ASP to get predictable performance IaaS" I'll run my app's tier on this. Number two, give me a platform service for database 'cause frankly, I don't really want to run your database, like, with all the manual effort, I want someone to automate, patching, scale up and down, and all these types of features like the pilot should have given us. And then number three, I do want SaaS over time. So we spend a lot of time with our customers, really saying, "how do I take this traditional application, run it on IaaS and PaaS?" And then number two, "let's modernize it at scale." Maybe I want to start peeling off functionality and running them as cloud native services right alongside, right? That's something again, that we're doing at scale, and other people are having a hard time running these traditional workloads on prem in the cloud. The second part is they say, "You know, I've got this legacy traditional ERP. Been servicing we well or maybe a supply chain system. Ultimately I want to get out of this. How do I get to SaaS?" And we say, "Okay, here's the way to do this. First, bring into the cloud, run it on IaaS and PaaS. And then selectively, I call it cloud slicing. Take a piece of functionality and put it into SaaS." For ERP, it might be something like start with GL, a new chart of accounts in ERP SaaS. And then slowly over a number of your journey as needed, adopt the next module. So this way, I mean, I'll just say this is the fun part of as an architect, our jobs, we're helping customers move to the cloud at scale, we're helping them do it at their rate, with whatever level of change they want. And when they're ready for SaaS, we're ready for them. And I would just say the other IaaS providers, here's the challenge we're seeing Dave, is that they're getting to the cloud, they're doing a little bit of modernization, but they want PaaS, they also want to ultimately get to SaaS, and frankly, those other clouds don't offer them. So they're kind of in this we're stuck on this lift and shift. But then we want to really move and modernize and go to SaaS. And I would say that's what Oracle is doing right now for enterprises. We're really helping them move these traditional workloads to the cloud IaaS and PaaS. And then number two, they're moving to SaaS when they're ready. And even when you get to SaaS, everyone says, "You know what, leave it as as vanilla as possible, but I want to make myself differentiated." In that case, again, IaaS and PaaS, coupled alongside a SaaS environment, you can build your specific differentiation. And then you leave the ERP pristine, so it can be upgraded constantly with no impact to your specific sidebar applications. So, I would say that the best clouds in the world, I mean, I think you're going to see a lot of the others are trying to, either SaaS providers trying to grow a PaaS, or maybe some of the IaaS players are trying to add SaaS. So, I think you're going to see this blending more and more because customers are asking for the flexibility For either or all three. But I will say that-- >> How can I get PaaS and SaaS-minus. >> Absolutely, I mean, what are you doing there? You're offering choice. There's not a question in my mind that Cisco is a huge customer of ours, they have a product that is one of their SaaS applications running Tetration on the Oracle Cloud. It actually doesn't run any Oracle. It's all cloud native applications. Natively built with a number of open source components. They run just IaaS. That's it, the Tetration product, and it runs fast. The Gen 2 cloud has a great architecture underneath it, flattened fast network. By far, for us, we feel like we really gotten into the guts of IaaS and made it run more efficiently. Other customers say, "I've got a huge Oracle footprint in the data center, help me get it out." So up to the cloud that they go, and they say I don't want just IaaS because that means I'm writing all the automation, like I have to manage all the patching. And this is where for us platform services really help because we give them the automation at scale, which allows their people to do other things, that may be more impactful for the business. >> I want to ask you about, the automation piece. And you guys have made the statement that your Gen 2 cloud is fundamentally different than how other clouds work, Gen 1 clouds. And the Gen 1 clouds which are evolving, the hyper scalars are evolving, but how is Oracle's Gen 2 cloud fundamentally different? >> Yeah. I think that one of the most basic elements of the cloud itself was that for us, we had to start with the security and the network. So if you imagine that those two components really, A, could dictate speed and performance, plus doing it in a secure fashion. The two things that you'll see an awful lot about for us, is that we've embedded not only security at every level. But we've even separated off what we call, every cloud, you have a number of compute instances and then you have storage, right? In the middle, you have a network. However, to become a cloud, and to offer the elastic scale and the multiple sharing of resources, you have to have something called a control plane. What we've done is we've actually extracted the control plane out into its own separate instance of a running machine. Other clouds actually have the control plane inside of there running compute cores. Now, what does that do? Well, the fact of the matter is, we assume that the control plane and the network should be completely separate from what you run on your cloud. So if you run a virtual machine, or if you run a bare metal instance, there's no Oracle software running on it. We actually don't trust customers, and we actually tell the customers don't trust us, either. So by separating out the control plane, and all the code that runs that environment off of the running machine, you get more cores meaning like you have-- There's no Oracle tax for running this environment. It's a separate conmputer for each one, the control plane. Number two, it's more secure. We actually don't have any running code on that machine, if you had a bare metal instance. So therefore, there's no way for one machine in the cloud to infect another machine if the control plane was compromised. The second part of the network, the guys who have been building this cloud, Don Johnson, a lot of the guys came from other clouds before and they said, "yYou know the one thing we have to do is make a we call it Flattened Fast Clause Network that really is never oversubscribed." So you'll constantly see and people always ask me same question, "Dave, why is the performance faster if its the same VM shape? "Like I don't understand why it's going faster, like high performance computing." And the reason again a lot of times is the network itself is that it's just not oversubscribed. It's constantly flowing all the data, there's no such thing as congestion on the network, which can happen. The last part, we actually added 52 terabytes of local storage to every one of those compute nodes. So therefore, there's a possibility you don't even have to traverse the network to do some really serious work on the local machine. So you add these together, the idea is make the network incredibly fast, separate out the control plane and run the software and security layer separate from the entire node where all the customers work is being done. Number three, give the customers more compute, by obviously having us offload it to a separate machine. And the last thing is put local storage and everything is what's called NVMe storage. Whether it's local or remote, everything's NVMe, though the IOPS we get are really off the charts. And again, it shows up in our benchmarks. >> Yeah, so you're getting, atomic access to memory. But in your control plane, you describe that control plane that's running. Sorry to geek out everybody. But I'm kind of curious, you know. You got me started, Chris. So that's control-- >> Yeah, that's good. >> the Oracle cloud or runs. Where's it live? >> It's essentially separated from the compute node. We actually have it in between, there's a compute node that all the work is done from the customer, could be on like a Kubernetes container or VM, whatever it might be. The control plane literally is separate. And it lives right next to the actual compute node the customer is using. So it's actually embedded on a SmartNIC, it's a completely different cores. It's a different chipset, different memory structure, everything. And it does two things. It helps us control what happens up in the customers compute nodes in VMs. And it also helps us virtualize the network down as well. So it literally, the control plane is separate and distinct. It's essentially a couple SmartNICS. >> And then how does Autonomous fit into this whole architecture? I'm speaking by the way for that description, I mean, it's nuanced, but it's important. I'm sure you having this conversation with a lot of cloud architects and chief technologists, they want to know this stuff, and they want to know how it works. And then, obviously, we'll talk about what the business impact is. But talk about Autonomous and where that fit. >> Yeah, so as Larry says that there are two products that really dictate the future of Oracle and our success with our customers. Number one is ERP-SaaS. The second one is Autonomous Database. So the Autonomous Database, what we've done is really taken a look at all the runtime operations of an Oracle database. So tuning, patching, securing all these different features, and what we've done is taken the best of the Oracle database, the best of something called Exadata which we run on the cloud, which really helps a lot of our customers. And then we've wrapped it with a set of automation and security tools to help it really manage itself, tune itself, patch itself, scale up and down, independent between compute and storage. So, why that's important though, is that really our goal is to help people run the Oracle database as they have for years but with far less effort, and then even not only far less effort, hopefully, a machine plus man, out of the equation we always talk about is man plus machine is greater than man alone. So being assisted by artificial intelligence and machine learning to perform those database operations, we should provide a better service to our customers with far less costs. >> Yeah, the greatest chess player in the world is a combination of man and machine, you know that? >> You know what? It makes sense. It makes sense because, there's a number of things that we can do as humans that are just too difficult to program. And then there are other things where machines are just phenomenal, right? I mean, there's no-- Think of Google Maps, you ask it wherever you want to go. And it'll tell you in a fraction of a second, not only the best route, but based on traffic from maybe the last couple of years. right now, we don't have autonomous cars, right, that are allowed to at least drive fully autonomous yet, it's coming. But in the meantime, a human could really work through a lot of different scenarios it was hard to find a way to do that in autonomous driving. So I do believe that it's going to be a great combination. Our hope and goal is that the people who have been running Oracle databases, how can we help them do it with far less effort and maybe spend more time on what the data can do for the organization, right? Improve customer experience, etc. Versus maybe like, how do I spin up a table? One of our customers is a huge consumer. They said, "our goal is how do we reduce the time to first table?" Meaning someone in the business just came up with an idea? How do I reduce the time to first table. For some of our customers, it can take months. I mean, if you were going to put in a new server, find a place in the data center, stand up a database, make the security controls, right and etc. With the autonomous database, I could spin one up right here, for us and, and we could start using it and it would be secure, which is utmost and paramount. It would scale up and down, meaning like just based on workload, as I load data into it, it would tune itself, it would help us with the idea of running more efficiently, which means less cores, which means also less cost. And then the constant security patches that may come up because of different threats or new features. It would do that potentially on its own if you allow it. Obviously some people want to watch you know what exactly it's going to do first. Do regression testing. But it's an exciting product because I've been working with the Oracle database for about 20 years now. And to see it run in this manner, it's just phenomenal. And I think that's the thing, a lot of the database teams have seen. Pretty amazing work. >> So I love this conversation. It's hardcore computer science, architecture, engineering. But now let's end with by up leveling this. We've been talking, a lot about Oracle Consulting. So let's talk about the business impact. So you go into customers, you talk to the cloud architects, the chief technologist, you pass that test. Now you got to deliver the business impact. Where does Oracle consulting fit with regard to that, and maybe you could talk about sort of where you guys want to take this thing. >> Yeah, absolutely. I mean, so, the cloud is great set of technologies, but where Oracle consulting is really helping us deliver is in the outcome. One of the things I think that's been fantastic working with the Oracle consulting team is that cloud is new. For a lot of customers who've been running these environments for a number of years, there's always some fear and a little bit of trepidation saying, "How do I learn this new cloud?" I mean, the workloads, we're talking about deeper, like tier zero, tier one, tier two, and all the way up to Dev and Test and DR, Oracle Consulting does really, a couple of things in particular, number one, they start with the end in mind. And number two, that they start to do is they really help implement these systems. And, there's a lot of different assurances that we have that we're going to get it done on time, and better be under budget, 'cause ultimately, again, that's something that's really paramount for us. And then the third part of it a lot of it a lot of times is run books, right? We actually don't want to just live at our customers environments. We want to help them understand how to run this new system. So training and change management. A lot of times Oracle Consulting is helping with run books. We usually will, after doing it the first time, we'll sit back and let the customer do it the next few times, and essentially help them through the process. And our goal at that point is to leave, only if the customer wants us to but ultimately, our goal is to implement it, get it to go live on time, and then help the customer learn this journey to the cloud. And without them, frankly, I think these systems are sometimes too complex and difficult to do on your own, maybe the first time especially because like I say, they're closing the books, they might be running your entire supply chain. They run your entire HR system or whatever they might be. Too important to leave to chance. So they really help us with helping the customer become live and become very competent and skilled, because they can do it themselves. >> But Chris, we've covered the gamut. We're talking about, architecture, went to NVMe. We're talking about the business impact, all of your automation, run books, loved it. Loved the conversation, but to leave it right there but thanks so much for coming on theCUBE and sharing your insights, great stuff. >> Absolutely, thanks Dave, and thank you for having me on. >> All right, you're welcome. And thank you for watching everybody. This is Dave Vellante for theCUBE. We are covering the Oracle North America Consulting transformation and its rebirth in this digital event. Keep it right there. We'll be right back. (upbeat music)

>>Yeah, yeah, yeah! >>Everybody, welcome back to the special digital presentation where we are tracking the transformation of Oracle consulting. And really, it's rebirth. Aaron Millstone is back. He's the senior vice president of consulting, joined by Jeff Davis. Who's ah, principal at Deloitte. He's the chief commercial officer for Oracle at Deloitte. Gentlemen, good to see you. Welcome. >>Thank you very much. >>Thanks for having me back. >>You're welcome, guys. Jeff, let me start with you. I've got the obvious question is why would Deloitte World Class? Yes, I well known why you partnering with Oracle Consultant? >>We're really It was a perfect match. The fact that we were looking to grow our oracle practice and really new and innovative ways around Oracle's cloud technology. Uh, in discussions with the oil, coal and specifically with Aaron Millstone, we discovered that we really had complementary capabilities and very little overlapping capabilities. So it was natural for us to find a way to work together. And specifically we found that there were strategic assets we had and there were tactical assets that Oracle had the mixture of two made a really unique and compelling value proposition for the customer base >>and Aaron. I mean, we've talked about the shift from from staff augmentation to much more strategic partnering with your customers. But you're not trying to compete with the big size of there's, there's it sounds like there's not a lot of overlap there. Where do you pick up and leave off for Deloitte? You describe that? >>Sure. I mean, we're You're right, right? We're not. We're not ever going to try to compete with the Deloitte. It's not our that's not in our DNA. It's not our intention. We exist to drive Oracle's to drive success for our customers on Oracle's cloud. That's that's our mantra. That's what we focus in on. So for us, right, we're deep technologists. We're We understand our cloud. We understand how cloud works within our various product suites that we migrate to the cloud. We understand how to manage it. We understand how to build paths extensions to it, but we don't have big program management. We don't understand non oracle components that well, you know, we've got some expertise here and there. But if we need to expand, you know, on Oracle solution to coexist with a Microsoft azure solution, we can't do that without going to a partner and as we bigger and the transformation that they're gonna have to change management and big, big transformation journey capabilities. Like again, That's not That's not expertise. >>Yeah, so Jeff will come back to you. So we see a lot of these deals. Sometimes we call them Barney deals. I love you. You love me. There's a press release, and that's it. But so one of the things we look for okay is their teeth behind this. You guys have come out with what you call elevate. What is elevate? How did it get started? And I have some follow up questions. >>Yeah, well, elevate really got started when Aaron and I started to look at the assets that each of the firms possessed on the Deloitte side, as Aaron suggested, We have deep capabilities and a broad range of technologies, some of them competing technologies with Oracle at the same time. Uh, we didn't have a great deal of depth in Oracle's technical products, Oracle Cloud Infrastructure and Oracle Autonomous. Our bench was not as big as Aaron's, and Aaron also had access to your local development at a level that we didn't have access to. So we really found ourselves in a situation where we could put those two capabilities together and we could offer something to our clients and a broad range of customers. Oracle customers in the field. They had access to all of the Lloyds capabilities, which includes great project management, great change management, real skill around the strategic aspects of cloud migration. And Aaron had tools on had resource is trained and developed around the late historical technology. They'd always be a step ahead of any s I So together we felt this was really a differentiation for marketplace, right, Erin? >>Yeah, absolutely right. And if I don't think I would add to it is that if you if you look at Deloitte approaches client conversation from, ah, business value perspective, you know, the work consulting teams tends to focus conversation. It tends to approach conversations with a focus on How do you want to do the technology? Um, both are helpful. But, you know, quite frankly, as we get into the bigger information in place, we need to lead with the Lloyd model of how do we How do we drive your business value and then begin from a technologist perspective, that's when we show up. So it really has been a very logical, very complimentary match. >>So you and I have talked about, you know, data centers and building data centers and investing. It's not just it's just not a good use of capital today. There's so many other things that organizations can do. You guys have identified data center. Consolidation is, is I'll call it Ah, you know, an initiative that you're seeing customers. I wonder if you could talk about that a little bit. Is that kind of a starting point for conversations? >>Yeah, well, it's definitely starting point, right? So we call it a referred to his infrastructure led transformation, Um, and appetite. The appetite for that is certainly high. We were seeing an increased focus on um, you know what customers need to do to take not just a workload here and there. But how do they get out of the data center business full? So it's a foregone conclusion, right? Like you just said, it's not. It's not really a question of should we invest in another data center? Where should we invest in up to in their data centers? The question has changed to Let's move the cloud. How do we get there and let's move in a big way? And that's why we're seeing that dialogue across all of our customers. And we find even for Oracle, it's been a learning for us, right? We started with on Oracle workload conversation, which is, Do you want to move this work? Work loads of oracle? But you want to move that Oracle workload works. And really, what we're finding is it's a wholesale transformation of everything in the data center, too. One or more clouds, right again, often often it's a multi cloud strategy, and that's okay. And we, you know, we were having more bigger conversations. The thing that has been really interesting is these conversations have evolved, and especially as we work with our partners at Deloitte, has been that, you know, we think that the combination of our our cloud technology, the consulting services that Oracle Consulting and Deloitte can bring to bear and then Oracle's ability to finance the whole deal makes the very compelling conversations for customers because you can walk in to a CEO to a CFO and say, Look on day one, you can actually have a lower spend that what you have today in your data center and get a cop transformation underway at the same time. >>So I want to come back to that business case and member Jeff, before we do, I want to ask you. So we heard Erin, you know, talking about the catalyst. You know, that sort of infrastructure transformation. But you're in the outcomes business, right in both. The bush has been deployed especially so So what is that North Star that you're seeing with customers? You know, it's not about the tech. They're not starting there. Um, that will often tell you that's kind of the easy part. But then we see tech coming and going, and it's the It's the business process. That's the people issues lining everybody. So what are you seeing is so the outcomes. What's that conversation like with your customers? >>Yeah, well, really, this conversation starts with business leadership. Um, if you think about it, there's a strong value proposition in infrastructure renewal. It's not at the top of mind, but once you start to understand the value that's created, it does raise two ah, high priority. Now, our experiences that virtually every board is looking for the C suite toe have a cloud strategy of some kind. People recognize the value of cloud in, uh in many of our clients and many of Oracle's customers, so the boards are pressing the C suite for a cloud strategy. Among those things are the value that cloud brings, including virtually unlimited scalability. Is is being tested real time now with a lot of current events. So when you see the scalability when you know you need a cloud strategy of some kind, your business advisors impressing you, the value proposition starts well, how do we get there? And what does it take to be successful? Our perspective is that it's it's fair to believe that the cloud will reduce infrastructure. Spend significantly. It's a great opportunity for consolidation. It also adds a layer of security, resiliency and scalability that you simply couldn't do on your own. So it addresses a lot of business needs Aziz well as a number of technical needs that need to be addressed. >>So let's talk a little bit more about that business cases that generally what you're seeing, where it starts is let's take some costs right out, and then Aaron, you and I talked about maybe investing that in the future of it. But is that really the starting point for the vast majority of customers? Let's let's let's cut some costs right away and get a payback immediately. >>So I'd like to share our perspective, which is, you know, nobody spends money for the sake of spending money on technology. It's got to have meaningful business value. So the conversation starts with really renewal and a path to the cloud. But there's a natural opportunity for savings in consolidation that we take advantage. We're not simply shifting from your hardware to the cloud we're actually modernizing, which will result in significant savings. But it also gives the business something that they don't have today at a level of security and scalability and ability to run a modern technology much faster, much better. Ah, and much more scalable. >>So a lot of people might again I go back to these deals. I think of this as a sales play. One of the things we look for is there. Is there any other integration? Are you doing co engineering in this case, maybe not, co engineering But are there tools that you're developing that you're taking to market, that you're actually leveraging? Eric, can you talk about that a little bit? Convinces. That's not just the sales play. >>Yeah, sure. And Jeff alluded to some of this earlier, too, right? So we definitely each had our respective tool. Angry Deloitte's investments in tools, what was built out of data that we have seen used quite a few times now we've been investing in something we call the Oracle soar. You know, our tools are, as you'd imagine, heavily Oracle focus. It's about moving Oracle technology to Oracle Cloud out of data and some of the tools that Deloitte's invested in our focus more comprehensively on holistically, looking at everything in a data center and everything that's across data centers and start to develop a set of facts around this stuff. But in both cases, we actually looked at these things and we said, You know what? If you combine these together, we get a very comprehensive view of what exactly it is, but we're looking at with a customer so we can tell everything from the types of traffic we see in the network to the specific versions of stuff you start to identify whether there's risk associated with having things, not aster on a supporter and get a very conference of you that's based on facts. And so, you know, we took those tools. We combined them together so that we can go into a customer and give a complete end and view from both on Oracle and Delight Perspective. And quite frankly, it doesn't matter whether the Lloyd leads or whether Oracle leads. We've developed these tools together. We're going to market together. And we've even got you know, the templates you'd expect consultancies tohave, right? So when you look at business cases, we've got joint business case templates that we've created together and that we're using actively with customers and therefore then we're refining them, improving them each time we do it. But, you know, we're at a point now where our tools are combined, templates are combined, and we even at this, you know, we're even Jeff in our poll earlier yesterday actually even got a joint Ah, war room that's constantly engaging with different account teams and making sure that we structurally approach things in a consistent way so that we're driving business value and using the tools appropriately. >>You know, I think, um, migration risk is probably one of the most significant factors in a business case. I mean, many don't understand it, but those in I t. And certainly hopefully in the executive office do you understand it? It sounds like that's a part of your tooling, anyway is designed to mitigate that's significant migration risk. When you talk about that a little bit, >>yeah, so we, you know, we approach migration from, you know, we start with the conversation. I'm almost always some type of log of what? The list of applications, what versions of things running they've been maintained by some might department somewhere, right? Or the collective? It's in varying degrees of accuracy is what we find. We don't rely on that. We go in and our our tools, our combined tooling across oracle, Deloitte interrogate the systems. We come back with actual information from the actual systems themselves. And then we started the plan. And so the funny thing is, with the migration, you know, probably 80% of the effort. 90% of the effort is in the planning stages and making sure that we understand exactly what we're moving exactly. When again, we're not. We're not dealing with the edge applications. Typically, we're dealing with the mission critical applications that are supporting the heart of a supply chain or a finance operation. And you can't. You just can't afford the down time that maybe you could afford on something that might be a consumer facing or a little less mission. Critical. So, yeah, we start finding very early and interrogate aggressively with actual data. >>Jeff, can you give us a sense as to how far you're into this elevate journey? May be thinking about a couple of customers either specifically or generically gonna where you're at with them. How far along? Maybe even some examples that you feel are representative. >>Sure. Um, you know, the the relationship has been probably about six Ah, close to seven months of maturity. In that time, we've had an opportunity to work on several key clients at scale. Uh, we've worked together in collaboration with one of the nation's largest retailers in the grocery business. We've worked collaboratively in aerospace and defense and also in the hospitality industry. In these cases, what we're finding and one is each one is in the various stage of maturity. One is done, one is in midstream on one is at the early stages and current economic conditions or driving a huge pipeline. Right now, I think our challenge right now is making sure that we identify those clients that can best take a value, take advantage of our services and our joint offering to deal with that pipeline. Right now, what we're finding is that the savings are at least as we projected. In some cases, we're finding even more. What people say they have and what people say they do isn't necessarily what you find when you get in there. But almost every case we're finding that there's unused equipment, unused capacity that they currently have redundancy, low utilization of their current assets. We can go a long way and streamlining that. Plus, I can't emphasize enough that ah, these days security is a major concern and we're adding a layer of security that they could never achieve themselves with soft. >>How do you guys on how the customers wanna approach the transaction? Is it a Bixby is a T and M. Is it a situation where you participate in some of the some of the savings of the game. How does the pricing work? >>So we have Go >>ahead. Um, I'll start off by saying each deal is really custom built around what a customer really needs, what they're trying to get out of it right now. As an example, Op X is very important. So we're engineering deals in a way that helps customers deal with their financial challenges, especially around op Ex. There are other structures that we can put in place. We have the backing of Oracle Finance, so we can be very innovative on deals they could be. When value was attained. They could be milestone based. There's just, uh, I think, a wide variety I don't want to say unlimited, but a wide variety of different options that we can offer our clients in order to be able to deal with whatever financial challenge or opportunity that may be looking at >>perfect, perfect. And you want >>to add to that >>and everything looking at other than you know, the there are. There are always things that are discovered during a personal project, and so, you know, we we also we do factor and things that allow some flexibility. Right? So even if we have a fixed price deal will include a bucket of ours to deal with, you know, unanticipated changes or even innovation. It doesn't have to be, You know, contingency could be Hey, we want to go out and spend and invest some money on artificial intelligence machine learning analytics over in this space since we've already moved these applications. All right, so we're approaching it again from a very flexible standpoint, and we're just point right. We can we can custom craft. Ah, deal to match what? The clients. Best business outcome. Okay. >>Yeah, that makes sense. That client might see some adjacent opportunity that they want to pursue, and they want that to be covered in the agreement I'm gonna end. Um, if you start with you, Aaron and then Jeff go to you. How? What do you guys see? A success? What does success look like? You know, when you were, you know, just less than a year in when you're 234 let's say five years and you look back, What does success look like? >>So, to me, successful success is gonna look like we've gotten a number of these big transformation deals in play. It's in motion, naturally between our organizations, not necessarily driven entirely by Jeff and I going out and driving the organization behave the right way. It's more in our DNA. But more importantly, I think we've gone into We've gone beyond the conversation of Let's Move workloads. We've gone into conversations off. Let's really talk about how to reimagine your business on top of Oracle's cloud and have an ongoing dialogue that looks at that transformation. Once we hit that 0.345 years from now, right, that will be a wild success, Jeff. >>But really, it's been around for 135 years. This is our birthday, uh, this year and in that time, what we've learned is there's no substitute for impact and value added to our clients. In our perspective, what this would success looks like his client success find success means improved scalability of their operations, uh, securing their technology and their data at a substantially lower cost, so that they can focus on what their core businesses and focus less on technology. That success to deploy >>right guys, thanks so much. Great session We're not only witnessing the rebirth of Oracle Consulting, but there's clearly a transformation going on. And it's cultural. Gentlemen, congratulations on your partnership. And thanks so much for coming on the Cube. >>Thank you so much >>for having us. >>You're welcome. Alright, Keep right there, everybody. We're back with our next guest covering Oracle Consulting North America. This is Dave Vellante with the Cube. Thanks for watching. >>Yeah, Yeah, yeah, yeah, yeah, >>yeah.

>>live from Las Vegas. It's the Q covering AWS executive. Something >>brought to you by extension. >>Welcome back, everyone to the cubes. Live coverage of the Ex Censure Executive Summit here in AWS. Reinvent I'm your host, Rebecca Knight. I'm joined by Tristan Moral Laur said. He is the managing director. North America Intelligence Cloud Infrastructure. Thank you so much for coming on the show. >>Thanks for having me, Rebecca. >>So I know that your primary focus is cloud management and optimization. Tell our viewers why. Why those air? Two critical things. >>They're two very important things. That cloud is wonderful. It's full of innovation. It's It involves all the time. It's wonderful for developers. They love to leverage this. There's broad implications for I T departments. I T departments are used to buy in Big, bold Guy T service is every three years they park it and then they renew that five years later. So from how do you constantly consume the clown an innovative way, and additionally, while the developers are enjoying the service is at the enterprise level, there's broad implications on the tools. The skill sets, the load that you're putting on the infrastructure on the network on the security. And so you really have to benefit of the clown to benefit of all the innovation. You have to take a step back and say, What does it mean to run in the clown and to manage and optimize it? And that's why we call it run different because you have to take it completely from the ground up and rethink it. >>Okay, so run different. Describe what this means. What? This what this is >>So we look at run different as five core pillars. First, you have to manage it, of course. And that doesn't go away because you put an application in the clown doesn't mean you don't manage it. So you have to manage it. The tools it, Sandra, you have to optimize it optimization if cloud is all about innovation. And every day in this morning, we heard all source of new innovations come out from quantum computing to contextualized. Aye, aye. Two new types of storage. You now have two on board this into your environment. How do you optimize it? The thirties? You have to consume it so you have to consume differently. It's completely changed. Procurement departments have to adapt to it, the security framework has to evolve. And finally, the governance across all of the cloud that you're consuming at the enterprise level has to change. And those five pillars are critical to what we mean by run different. >>So we're going to get into all of these in just a second. But I'm your premises that the old way of doing I t doesn't work anymore. So when you explain this this approach in this strategy of thinking in this new way, is there any pushback? I mean, so much of technology and new strategies and approaches is not necessarily the technology itself. It's the it's the change management. It's the people. So with the implication that your way is not gonna cut it anymore, it's wrong. How is it? How is it understood in the organization's? It's >>in many cases, not understood, because in many cases people look at the individual technology and how my using this individual technology. And this morning, as of this morning, a lot of clients we're looking at, how do I use these widgets? Better use? That's not the point. The point is, if I'm there, I am the belief of why I'm moving in the clown is not for one particular capability, but the belief that the kid buildings are going to get better over time, better operationally. So developers are going to get new features and, by the way, better financially, because if I'm using the right innovation financially, it gets better over time. So you're moving from very static environment applications that don't move to a very dynamic environment, and that is a complete shift in mindset. It's a shift in mindset for the developers, for the people managing applications for procurement departments who now have to buy something every day. And so the change management of the enterprise is very complex because, by the way, you can't completely over rotate. Just because you're moving A S a P application to the clown doesn't mean you don't manage it anymore. You still have to make sure that your piece system is operating properly. So that's what we mean by a multi mode operating model is across the spectrum. You still have to have the more traditional management, but you have to evolve it on an ongoing basis, and that is a complete shift. Your workforce has to change all the time this morning, Seo should have woken up and said, I'm gonna use ultra warm. I now need skills on that. I now need tools on that, and so that's a complete shift, which is very difficult for enterprise at a large scale to adapt to and embrace. But they have to. If they do not, they won't benefit from the clown. >>So let's let's go through these things. Let's start with Cloud Management Service is tell it. Tell us, Tell our viewers a little bit about that. So, clown >>management, The wonderful thing about the clown is you can automate it, and so you can now automate the resolution of incidents. Frankly, we don't care about incident management anymore. If something fails, we just spend something else up, and it resolves itself. So it's much more about how do you make sure that things are automated so that there's no human intervention from a When something goes really wrong and you need to do problem management, you now need different stead of skills. So instead of having the old network skill and storage skill and operating system skill, I need an AWS platform skill, somebody that can engineer the application from top to bottom, a full stack engineer on that platform. That's a completely different type of skill. Number one and number two has to evolve over time. So how are the engineers at any client or 90 department are going to learn about how to manage the new quantum computing that we heard about this morning or wavelength and enable five G's so those skills normally have to be different and platform enable. But they have to evolve over time and so managing the clown that it still requires skills and tools but that have to evolve and change over time. >>So, as you said, C I ose and CEOs air saying, Wow, I have a lot of work to do to make sure my work versus up to speed um, cloud optimization surfaces, yes, he said. So >>that, to me, is the fundamental shift. If management over time, hopefully if fully is automated and that function shrinks to almost zero, what now becomes his cloud is available to all the developers. The problem is, they're consuming it as much as they want, so you have to shift from fixing your problem to fixing the consumption um I'm making sure that I am I using the right type of service. So instead of having a e c two instance on it in a database, am I using RD s instead of R. D s? Am I using Lambda instead of Lambda? Am I using fargate? So am I using the right type of service for my application and for my business? And that is constant optimization to drive the right service. And when I'm consuming too much of my identifying that consumption event, um, very recent example. Ah, client of mine explained to me how at Christmas one of his developers left a key out in the open. Somebody used that key to spin up a bunch of aws instance to mine. Bitcoin. Now that's not a incident. The system's working fine as advertised, so it's not a incident. The rial idol term. It's an incident in the terms of its a consumption event that I have to catch and identify. That is the shift you have to manage the consumption in real time, not the incident in real time, and that's what optimization is all about. >>But but then there's another consumption element to it. too >>There is because procurement department's used to buy things on an annual basis. Sometimes if every five years, they would pain along with a bunch of hardware and leave it sitting in their data center. Now they're buying things every month. If you take X century, for example, every month we have 900 million lines of bills for our cloud providers like sell only processes. What, 64,000? You have toe have special tools. How do you reconcile this? How do you translate these bills back to the application owner so that they drive the right consumption? How'd you align it back to the business? All of those air new features of the procurement department that has to exist in the i T department to deal with a clown. >>So next is security. And this is, of course, on every ceos mind. Right now. How do you ensure security compliance clients, but also secure, Secure? >>So how is it secure and how do you ensure security compliance? Um, the great things about the clown new kid abilities have security embedded. Unfortunately, clients realize that they can't outsource security. That is always a responsibility. That's a board level responsibility the CEOs are accountable for. So how do you relate the security component that is in the cloud versus the security component that you're still responsible for us, the C. I O. And the default security features and configurations of the cloud service is may or may not be aligned to your own security policies. So as you using the cloud, you have to align their security to your your eye tea estates policies, and you have to monitor it in real time. So it becomes a monitoring of the security feature and how it's complimentary to your policies, as opposed to driving and insecurity individually for every widget it evolves over time. And as your developers consume, news service is you don't have control over that, but you have to monitor it so you can address any shortfalls as they as they calm and as you identify them. >>So the final element of this this approach is cloud governance. How do you define this? >>So cloud governance? What's what's fascinating and one of the big lesson learned from this morning actually is you are not going to go to AWS to be public club. You're going to AWS for the cloud. With outpost now being generally available, you may go to AWS for private or public and now, by the way, for quantum as well. So even if you have one primary cloud provider and let's say, state of us or or another, you have to manage multiple cloud platforms and you have to govern it across the platforms. Developers don't care where they're consuming it. They just want it available. And that governance across all the AWS clowns, in most cases multi clowns, is critical to get that total visibility of your entire estate. And so that's why that fifth pillar is critical in a foundation of all the others. >>So this is this is really interesting. Can you give us some examples of clients that you are already using this approach and and how it's having an impact on their businesses? >>So we're using this approach at all of our clients, so we fundamentally believe that is how you have to manage it. And it's no longer just a fixing the incidents. It truly is about automating and optimizing. I think the best example is Accenture. We've moved 95% of our estate in the cloud >>your own use case. >>We are. And I could name a lot of clients, but centuries our best example. Because we run the risk and being the cloud to completely over consume. And when we spend, you know hundreds of millions in the clown, you have to manage that very, very carefully. Are you using the related skit build these? Are you consuming it properly? And how are we dealing with the bills? In fact, this framework was built on the lessons learned from our clients. But really, from what we did internally to Accenture, >>So other than implementing run differently, stat, What is your best advice for organizations that are really looking to have a more organized and systematic approach to this? >>Yeah, I think clients will have to one every clients on a big clown journey. And I think what we're seeing is clients are accelerating their clown journey. They have to make a real decision. Run different is a framework which way advise client. Either they could do it themselves, and they have to adopt this this concept or they can use 1/3 party. Important concept is if you want to benefit from the cloud it evolves. If you are investing in your tools in your skill sets, we will absolutely support it and encourage it. But you have to understand that that is an ongoing investment. Every year you have to update your platform. Every year you have to update your skills. So some clients air fully committing to that our technology companies at the core and are making those investments. Other clients realize that that is something they would prefer to use 1/3 party for. And they come to a number providers, including ex center. >>Well, Tristan, thank you so much for coming on. The show are really interesting conversation. >>Thank you so much. Rebecca. >>I'm Rebecca. Night. Stay tuned for more of the cubes. Live coverage of the Accenture Executive Summit.

>> from atop the Salesforce Tower in downtown San Francisco. It's the Q covering Accenture Innovation Date brought to you by ex center >> Hey, welcome back Your body jefe Rick here from the Cube were high atop San Francisco in the essential innovation hub. It's in the middle of the Salesforce Tower. It's a beautiful facility. They think you had it. The grand opening about six months ago. We're here for the grand opening. Very cool space. I got maker studios. They've got all kinds of crazy stuff going on. But we're here today to talk about Cloud in this continuing evolution about cloud in the enterprise and hybrid cloud and multi cloud in Public Cloud and Private Cloud. And we're really excited to have a couple of guys who really helping customers make this journey, cause it's really tough to do by yourself. CEOs are super busy. They worry about security and all kinds of other things. So centers, often a trusted partner. We got two of the leaders from center joining us today's Prasad Sankaran. He's the senior managing director of Intelligent Cloud infrastructure for Center Welcome and Larry Soccer, the global managing director. Intelligent cloud infrastructure offering from central gentlemen. Welcome. I love it. It intelligent cloud. What is an intelligent cloud all about? Got it in your title. It must mean something pretty significant. >> Yeah, I think First of all, thank you for having us, but you're absolutely Everything's around becoming more intelligent around using more automation. And the work that, you know we delivered to our clients and cloud, as you know, is the platform to which all of our clients are moving. So it's all about bringing the intelligence not only into infrastructure, but also into cloud generally. And it's all driven by software, >> right? It's just funny to think where we are in this journey. We talked a little bit before we turn the cameras on and there you made an interesting comment when I said, You know, when did this cloud for the Enterprise start? And you took it back to sass based applications, which, >> you know, you were sitting in the sales force builder. >> That's true. It isn't just the tallest building in here, and everyone all right, everyone's >> had a lot of focus on AWS is rise, etcetera. But the real start was really getting into sass. I mean, I remember We used to do a lot of Siebel deployments for CR M, and we started to pivot to sales, for some were moving from remedy into service. Now I mean, we went through on premise collaboration, email todo 360 5 So So we've actually been at it for quite a while in the particularly the SAS world. And it's only more recently that we started to see that kind of push to the, you know, the public pass, and it's starting to cloud native development. But But this journey started, you know, it was that 78 years ago that we really start to see some scale around it >> and tell me if you agree. I think really, what? The sales forces of the world and the service now is of the world off. 3 65 kind of broke down some of those initial barriers which were all really about security and security. Security secure. It's always too here where now security is actually probably an attribute >> and loud can brink Absolutely. In fact, I'm in those barriers took years to bring down. I still saw clients where they were forcing salesforce tor service. Now to put you know instances on Prime, and I think I think they finally woke up toe. You know, these guys invested ton in their security organizations. You know, there's a little of that needle in the haystack. You know, if you breach a data set, you know what you're getting after. But when you happen to sail sports, it's a lot harder. And so you know. So I think that security problems, I've certainly got away. We still have some compliance, regulatory things, data sovereignty. But I think security and not not that it's all by any means that you know, it's always giving an ongoing problem. But I think they're getting more comfortable with their data being up in the public domain, right? Not public. >> I think it also help them with their progress towards getting cloud native. So, you know, you pick certain applications which were obviously hosted by sales force and other companies, and you did some level of custom development around it. And now I think that's paved the way for more complex applications and different workloads now going into, you know, the public cloud and the private cloud. But that's the next part of the journey, >> right? So Let's back up 1/2 a step cause then, as you said, a bunch of stuff then went into Public Cloud, right? Everyone's putting in AWS and Google. Um, IBM has got a public how there was a lot more. They're not quite so many as there used to be. Um, but then we ran into a whole new home, Those of issues, right, Which is kind of opened up this hybrid cloud. This multi cloud world, which is you just can't put everything into a public clouds there certain attributes that you need to think about and yet from the application point of view, before you decide where you deploy that. So I'm just curious. If you can share now, would you guys do with clients? How should they think about applications? How, after they think about what to deploy where I >> think I'll start in the, You know, Larry has a lot of expertise in this area. I think you know, we have to obviously start from an application centric perspectives. You got to take a look at you know where your applications have to live water. What are some of the data implications on the applications or do you have by way of regulatory and compliance issues? Or do you have to do as faras performance because certain applications have to be in a high performance environment? Certain other applications don't think a lot of these factors will then drive where these applications need to recite. And then what we're seeing in today's world is really accomplish. Complex, um, situation where you have a lot of legacy, but you also have private as well as public cloud. So you approach it from an application perspective. >> Yeah. I mean, if you really take a look at Army, you look at it centers clients, and we were totally focused on up into the market Global 2000 savory. You know, clients typically have application portfolios ranging from 520,000 applications. And really, I mean, if you think about the purpose of cloud or even infrastructure for that, they're there to serve the applications. No one cares if your cloud infrastructure is not performing the absolute. So we start off with an application monetization approach and ultimately looking, you know, you know, with our tech advisory guys coming in, there are intelligent engineering service is to do the cloud native and at mod work our platforms. Guys, who do you know everything from sales forward through ASAP. They should drive a strategy on how those applications going to evolve with its 520,000 and determined hey, and usually using some like the six orders methodology. And I'm I am I going to retire this Am I going to retain it? And I'm gonna replace it with sass. Am I gonna re factor in format? And it's ultimately that strategy that's really gonna dictate a multi in and, you know, hybrid cloud story. So it's based on the applications data, gravity issues where they gonna reside on their requirements around regulatory, the requirements for performance, et cetera. That will then dictate the cloud strategies. I'm you know, not a big fan of going in there and just doing a multi hybrid cloud strategy without a really good up front application portfolio approach, right? How we're gonna modernize that >> it hadn't had a you segment. That's a lot of applications. And you know, how do you know the old thing? How do you know that one by that time, how do you help them pray or size? Where they should be focusing on. Yes, >> it. Typically, what we do is work with our clients to do a full application portfolio analysis, and then we're able to then segment the applications based on, you know, important to the business and some of the factors that both of us mentioned. And once we have that, then we come up with an approach where certain sets of applications have moved to sass certain other applications you moved past. So you know, you're basically doing the re factoring and the modernization, and then certain others, you know, you can just, you know, lift and shift. So it's really a combination off both modernization as well as migration. It's a combination off that, but to do that, you have initially look at the entire set of applications and come up with that approach. >> I'm just curious where within that application assessment, where is cost savings? Where is, uh, this is just old and where is opportunities to innovate faster? Because we know a lot of lot of talk really. Days has cost savings, but what the real advantages is execution speed if you can get it. >> If >> you could go back three or four years and we had there was a lot of CEO discussions around cost savings. I'm not really have seen our clients shift. It costs never goes away, obviously right. But there's a lot greater emphasis now on business agility. You know, howto innovate faster, get, get new capabilities, market faster to change my customer experience. So it's really I t is really trying to step up and, you know, enabled the business toe to compete in the marketplace. So we're seeing a huge shift in emphasis or focus at least starting with, you know, how do I get better business agility outta leverage to cloud and cloud native development to get there upper service levels? Actually, we started seeing increase on Hey, you know, these applications need to work. It's actress, So obviously cost still remains a factor, but we seem much more, you know, much more emphasis on agility, you know, enabling the business on giving the right service levels of right experience to the user. Little customers. Big pivot there, >> Okay. And let's get the definitions out because you know a lot of lot of conversation about public clouds. Easy private clouds, easy but hybrid cloud and multi cloud and confusion about what those are. How do you guys define them? How do you help your customers think about the definition? Yes, >> I think it's a really good point. So what we're starting to see is there were a lot of different definitions out there. But I think as I talk to my clients and our partners, I think we're all starting to come toe. You know, the same kind of definition on multi cloud. It's really about using more than one cloud. But hybrid, I think, is a very important concept because hybrid is really all about the placement off the workload or where your application is going to run on. And then again, it goes to all of these points that we talked about data, gravity and performance and other things. Other factors. But it's really all about where do you place the specific workload >> if you look at that, so if you think about public, I mean obviously gives us the innovation of the public providers. You look at how fast Amazon comes out with new versions of Lambda etcetera, so that's the innovations. There obviously agility. You could spend up environments very quickly which is, you know, one of the big benefits of it. The consumption economic models. So that is the number of drivers that are pushing in the direction of public. You know, on the private side, they're still it's quite a few benefits that don't get talked about as much. Um, so you know, if you look at it performance, you know, if you think the public world, you know, although they're scaling up larger T shirts, et cetera, they're still trying to do that for a large array of applications on the private side, you can really Taylor somethingto very high performance characteristics. Whether it's you know, 30 to 64 terabyte Hana, you can get a much more focused precision environment for business critical workloads like that article, article rack. You know, the Duke clusters everything about fraud analysis. So that's a big part of it. Related to that is the data gravity that Prasad just mentioned. You know, if I've got a 64 terrified Hana database, you know, sitting in my private cloud, it may not be that convenient to go and put get that data shared up in red shift or in Google's tensorflow. So So there's some data gravity out. Networks just aren't there. The Laden sea of moving that stuff around is a big issue. And then a lot of people of investments in their data centers. I mean, the other piece, that's interesting. His legacy, you know, You know, as we start to look at the world a lot, there's a ton of Could still living in, You know, whether it's you, Nick system, that IBM mainframes. There's a lot of business value there, and sometimes the business cases aren't aren't necessarily there toe to replace them. Right. And in world of digital, the decoupling where I can start to use micro service is we're seeing a lot of trends. We worked with one hotel to take the reservation system. You know, Rapid and Micro Service is, um, we then didn't you know, open shift couch base, front end. And now when you go against, you know, when you go and browsing properties, you're looking at rates you actually going into distributed database cash on, you know, in using the latest cloud native technologies that could be dropped every two weeks or every three or four days for my mobile application and It's only when it goes, you know, when the transaction goes back, to reserve the room that it goes back there. So we're seeing a lot of power with digital decoupling, but we still need to take advantage of, you know, we've got these legacy applications. So So the data centers air really were trying to evolve them. And really, just, you know, how do we learn everything from the world of public and struck to bring those saints similar type efficiencies to the to the world of private? And really, what we're saying is this emerging approach where I can start to take advantage of the innovation cycles that land is that you know, the red shifts the azure functions of the public world. But then maybe keep some of my more business critical regulated workloads. You know, that's the other side of the private side, right? I've got G X p compliance. If I've got hip data that I need to worry about GDP are you know, the whole set of regular two requirements Over time, we do anticipate the public guys will get much better and more compliant. In fact, they made great headway already, but they're Still not a number of clients are still, you know, not 100% comfortable from rail client's perspective. >> Gotta meet Teresa Carlson. She'll change him. Who runs that AWS Public Sector is doing amazing things, obviously with big government contracts. But but you raise real inching point later. You almost described what I would say is really a hybrid application in this thing. This hotel example that you use because it's is, you know, kind of break in the application and leveraging micro service is to do things around the core that allowed to take advantage of some this agility and hyper fast development, yet still maintain that core stuff that either doesn't need to move Works fine. Be too expensive. Drea Factor. It's a real different weight. Even think about workloads and applications into breaking those things into bits. >> And we see that pattern all over the place. I'm gonna give you the hotel Example Where but finance, you know, look at financial service. Is retail banking so open banking a lot. All those rito applications are on the mainframe. I'm insurance claims and and you look at it, the business value, replicating a lot of like the regulatory stuff, the locality stuff. It doesn't make sense to write it. There's no rule inherent business values of I can wrap it, expose it and you know the micro service's architecture now. D'oh cloud native front end. That's gonna give me a 360 view a customer, Change the customer experience. You know, I've got a much you know, I can still get that agility. The the innovation cycles by public. Bye bye. Wrapping my legacy environment >> in person, you rated jump in and I'll give you something to react to, Which is which is the single glass right now? How do I How did I manage all this stuff now? Not only do I have distributed infrastructure now, I've got distributed applications and the thing that you just described and everyone wants to be that single pane of glass Everybody wants to be the app that's upon everybody. Screen. How are you seeing people deal with the management complexity of these kind of distributed infrastructures? If you will Yeah, >> I think that that's that's an area that's, ah, actually very topical these days because, you know, you're starting to see more and more workers. Goto private cloud and so you've got a hybrid infrastructure you're starting to see move movement from just using the EMS to, you know, the cantinas and Cuban Edie's. And, you know, we talked about Serval s and so on. So all of our clients are looking for a way, and you have different types of users as well. Yeah, developers. You have data scientists. You have, you know, operators and so on. So they're all looking for that control plane that allows them access and a view toe everything that is out there that is being used in the enterprise. And that's where I think you know, a company like Accenture were able to use the best of breed toe provide that visibility to our clients. >> Yeah. I mean, you hit the nail on the head. It's becoming, you know, with all the promise of cloud and all the power. And these new architectures is becoming much more dynamic, ephemeral, with containers and kubernetes with service computing that that one application for the hotel, they're actually started, and they've got some actually, now running a native us of their containers and looking at serverless. So you gonna even a single application can span that and one of things we've seen is is first. You know, a lot of our clients used to look at, you know, application management, you know, different from their their infrastructure. And the lines are now getting very blurry. You need to have very tight alignment. You take that single application. You know, if any my public side goes down or my mid tier with my you know, you know, open shipped on VM where it goes down on my back and mainframe goes down. Or the networks that connected to go down the devices that talked it. It's a very well, despite the power, very complex environment. So what we've been doing is first we've been looking at, you know, how do we get better synergy across what we you know, application service is teams that do the application manager an optimization cloud infrastructure, you know, how do we get better alignment that are embedded security, You know, how do you know what are managed to Security Service's and bringing those together? And then what we did was we looked at, you know, we got very aggressive of cloud for a strategy and, you know, how do we manage the world of public. But when looking at the public providers of hyper scale er's and how they hit incredible degrees of automation, we really looked at, said and said, Hey, look, you gotta operate differently in this new world. What can we learn from how the public guys they're doing that? We came up with this concept We call it running different. You know, how do you operate differently in this new multi speed? You know, you know, hot, very hybrid world across public, private demon, legacy environment and started looking say OK, what is it that they do? You know, first they standardize, and that's one of the big challenges you know, going to almost all of our clients in this a sprawl. And you know, whether it's application sprawl, its infrastructure, sprawl and >> my business is so unique. The Larry no business out there has the same process that we have. So we started make you know how to be >> standardized like center hybrid cloud solution apart with HP. Envy em where we, you know, how do we that was an example. So we can get thio because you can't automate unless you standardise. So that was the first thing you know, standardizing service catalog. Standardizing that, um, you know, the next thing is the operating model. They obviously operate differently. So we've been putting a lot of time and energy and what I call a cloud and agile operating model. And also a big part of that is truly you hear a lot about Dev ops right now, but truly putting the security and and operations into Deb set cops of bringing, you know, the development in the operations much tied together. So spending a lot of time looking at that and transforming operations re skilling the people you know, the operators of the future aren't eyes on glass there. Developers, they're writing the data ingestion, the analytic algorithms, you know, to do predictive operations. They're writing the automation script to take work, you know, test work out. Right. And over time, they'll be tuned in the air. Aye, aye. Engines to really optimize the environment and then finally has presided. Looted thio. Is that the platforms that control planes? That doing that? So, you know, we What we've been doing is we've had a significant investments in the eccentric cloud platform, our infrastructure automation platforms and then the application teams with it with our my wizard framework, and we've been starting to bring that together. You know, it's an integrated control plane that can plug into our clients environments to really manage seamlessly, you know, and provide, you know, automation Analytics. Aye, aye. Across APS, cloud infrastructure and even security. Right. And that, you know, that really is a iob is right. I mean, that's delivering on, you know, as the industry starts toe define and really coalesce around, eh? I ops, that's what we use. >> So just so I'm clear that so it's really your layer your software layer kind of management layer that that integrates all these different systems and provides kind of a unified view. Control, I reporting et cetera. Right >> Exactly. Then can plug in and integrate, you know, third party tools. I had to do some strategic function. >> I'm just I'm just >> curious is one of the themes that we here out in the press right now is this is this kind of pull back of public cloud app. Some of them are coming back. Or maybe it was, you know, kind of a rush. Maybe a little bit too aggressively. What are some of the reasons why people are pulling stuff back out of public clouds, that just with the wrong it was just the wrong application? The costs were not what we anticipated to be. We find it, you know, what are some of the reasons that you see after coming back in house? Yeah, >> I think it's >> a variety of factors. I mean, it's certainly cost, I think is one. So as there are multiple private options and you know, we don't talk about this, but the hyper skills themselves are coming out with their own different private options, like Aunt Ours and out pulls and other stack and on. And Ali Baba has obsessed I and so on. So you see a proliferation of that and you see many more options around private cloud. So I think the cost is certainly a factor. The second is I think data gravity is, I think, a very important point because as you're starting to see how different applications have to work together, then that becomes a very important point. The third is just about compliance, and, you know, the regulatory environment. As we look across the globe, you know, even outside the U. S. We look at Europe and other parts of Asia as clients and moving more to the cloud. You know, that becomes an important factor. So as you start to balance these things, I think you have to take a very application centric view. You see some of those some some maps moving back, and and I think that's the part of the hybrid world is that you know, you can have a nap running on the private cloud and then tomorrow you can move this. Since it's been containerized to run on public and it's, you know, it's all managed that look >> e. I mean, cost is a big factor if you actually look at it. Most of our clients, you know, they typically you were big cap ex businesses, and all of a sudden they're using this consumption consumption model. And they weren't really They didn't have a function to go and look at the thousands or millions of lines of it, right? You know, as your statement, exactly think they misjudged, you know, some of the scale on B e e. I mean, that's one of the reasons we started. It's got to be an application lead modernization that really that will dictate that. And I think in many cases, people didn't may not have thought through which application. What data? There The data, gravity data. Gravity's a conversation I'm having just by with every client right now. You know, I've got a 64 terabyte hana, and that's the core. My crown jewels. That data, you know, how do I get that to tensorflow? How'd I get that >> right? But if Andy was >> here, though, Andy would say, we'll send down the snow. The snow came from which virgin snow plows Snowball snowball. Well, they're snowballs. But we've seen the >> hold of a truck killer >> that comes out and he'd say, Take that and stick it in the cloud. Because if you've got that data in a single source right now, you can apply multitude of applications across that thing. So they you know they're pushing. Get that date end in this single source course than to move it, change it, you know you run it. All these micro lines of billing statement take >> the hotel. I mean, their data stolen the mainframe. So if they may want need to expose it? Yeah, they have a database cash, and they move it out. You know, the particulars of data sets get larger, it becomes, you know, the data. Gravity becomes a big issue. Because no matter how much you know, while Moore's law might be might have elongated from 18 to 24 months, the network will always be the bottle, Mac. So ultimately, we're seeing, you know, a CZ. We proliferate more and more data, all data sets get bigger and better than network becomes more of a bottleneck. Conned. That's a lot of times you gotta look at your applications. They have. I've got some legacy database I need to get. Thio. I need this to be approximately somewhere where I don't have, you know, high bandwith o r. Right Or, you know, highlight and see type or so egress costs a pretty big deals. My date is up in the cloud, and I'm gonna get charged for pulling it off. You know that That's been a big issue. >> You know, it's funny, I think, and I think a lot of the issue, obviously complexity building. It's a totally different building model, but I think to a lot of people will put stuff in a public cloud and then operated as if they bought it. And they're running in the data center in this kind of this. Turn it on, turn it off when you need it. Everyone turns. Everyone loves to talk about the example turning it on when you need it. But nobody ever talks about turning it off when you don't. But but the kind of clothes on our conversation I won't talk about a I and applied a I. CoSine is a lot of talk in the market place, but a time machine learning. But as you guys know pride better than anybody, it's the application of a I and specific applications, which really on unlocks the value. And as we're sitting here talking about this complexity, I can't help but think that, you know, applied a I in a management layer like your run differently, set up to actually know when to turn things on, when to turn things off when you moved in but not moved, it's gonna have to be machines running that right cause the data sets and the complexity of these systems is going to be just overwhelming. Yeah, yeah, >> absolutely completely agree with you in fact. Ah, essential. We actually referred to the Seoul area as Applied intelligence. Ah, and that's our guy, right? And, uh, it is absolutely to add more and more automation Move everything Maur toe where it's being run by the machine rather than, you know, having people really working on these things >> yet, e I mean, if you think you hit the nail on the head, we're gonna a eyes e. I mean, given how things getting complex, more ephemeral, you think about kubernetes et cetera. We're gonna have to leverage a humans or not to be able to get, you know, manage this. The environment is important, right? What's interesting way we've used quite effectively for quite some time. But it's good at some stuff, not good at others. So we find it's very good at, like, ticket triage, like ticket triage, chicken routing, et cetera. You know, any time we take over account, we tune our AI ai engines. We have ticket advisers, etcetera. That's what probably got the most, you know, most bang for the buck. We tried in the network space. Less success to start even with, you know, commercial products that were out there. I think where a I ultimately bails us out of this is if you look at the problem. You know, a lot of times we talked about optimizing around cost, but then performance. I mean, and it's they they're somewhat, you know, you gotta weigh him off each other. So you've got a very multi dimensional problem on howto I optimize my workloads, particularly. I gotta kubernetes cluster and something on Amazon, you know, sums running on my private cloud, etcetera. So we're gonna get some very complex environment. And the only way you're gonna be ableto optimize across multi dimensions that cost performance service levels, you know, and then multiple options don't do it public private, You know, what's my network costs etcetera. Isn't a I engine tuning that ai ai engines? So ultimately, I mean, you heard me earlier on the operators. I think you know, they write the analytic albums, they do the automation scripts, but they're the ultimate ones who then tune the aye aye engines that will manage our environment, right. And I think it kubernetes will be interesting because it becomes a link to the control plane optimize workload placement between >> when the best thing to you. Then you have dynamic optimization can. You might be up to my tanks at us right now, but you might be optimizing for output the next day. So exists really a you know, kind of Ah, never ending >> when you got you got to see them >> together with it. And multi dimension optimization is very difficult. So I mean, you know, humans can't get their head around. Machines can, but they need to be trained. >> Well, Prasad, Larry, Lots of great opportunities for for centuries bring that expertise to the table. So thanks for taking a few minutes to walk through some of these things. Our pleasure. Thank you. Raise Prasad is Larry. I'm Jeff. You're watching the Cube. We are high above San Francisco in the Salesforce Tower. Theis Center. Innovation have in San Francisco. Thanks for watching. We'll see you next time