>>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 our studios in the heart of Silicon Valley. PALO ALTO, California It is a cute conversation, >> living welcome to this special Cuba conversation in Palo Alto, California We're here with our friends on Twitter and influences in the cloud computing edge and open source game. We have our distinguished power panel here talking about if every tech company, every company should be a tech company. And what does it mean in the air of a modern infrastructure? Police to have my kale with ct of everest dot org's from most Gatto's California Rob Hirschfeld, founder and CEO of Rock n Calling in From Where You Calling in from >> Austin, Texas. >> Austin, Texas. Good to have you and Mark Theo Who's with EJ Gravity brand New opportunity. Congratulations calling in Las Vegas. Thanks for coming in, guys. Thanks for spending the time on this cube power panel from the influencers. Always great to see you guys on Twitter with this morning. I woke up, was very active at a Crouch said earlier this morning. And Mark, you wrote a post that got my attention. So I think you hit a nerve that has been sparking around the Internets around the role of technology as couples, they're starting to rethink and building out there enterprise architectures in their businesses. And we're seeing some signals around cybersecurity. Dev Ops certainly has been kind of banging on this drum with cloud computing, and that is that the role of technology plays as a percentage of the business part of the business. And your tweet was simply put, you said every bit. If every business needs to become a tech business, it business has to decide to own its own infrastructure something of that effect, which which triggered me because it's like That's a good question. It isn't just a part of an organization supporting it. Tech is becoming much more instrumental. So I want to get your reaction. What was the motivation behind that tweet? What's your what's your What was your point around it? >> Yeah, I mean, like many of my tweets, they're poorly worded and rushed out, so you know, it's not as clear as it could have been. But the real point of the message wasn't Thio highlight that a technology company has to be all in the cloud or has to own its infrastructure, but rather as a company makes a change towards becoming a technology company. I mean, if we go back Thio you know, 1995 or 1996 when we wanted a library, we went to the library. But now we have Google. We didn't know that Google was gonna become an online the equivalent of a library. But it became a digital company before anybody asked for that solution or anybody was running that kind of solution in some sort of company format and then changed it over. But, you know, Google Facebook, Microsoft's into it. Adobe PayPal. We could go down the long list there. All I t cos in the end, whether you call the technology that they built to run their businesses engineering with a CTO or I t. Is the material. They are in fact, large giant I t organizations that do what they do to make money. And so, as more companies look to make the change as digital transformation takes hold as more efforts are presented to try to get a closer handle on customers to build loyalty with customers, create new engagement models, maybe at the edge, even in traditional application environments, then companies have to make a decision about how they're going toe oh, nightie and whether they're goingto own any portion of the infrastructure of I T. And if they're going to do that, then I don't think that there's any question that they have to own it. Atleast following a model of the way the large providers and the facebooks, et cetera have provided for us cannot continue. In other words, what I've been known to say before, we can't continue to throw more hardware and people at the problem. >> My mike, I want to get your thoughts on this because one of the things that I know you have been involved a lot with security on dhe I t. As well in security, which which is a canary in the coal mine. For a lot of these architectural decisions are all kind of looking at how they hire and build on premise in house around tech stacks. And one of the things that became apparent to me at Amazon Aws reinforce, which is their Amazons first cloud security conference, was most of the ceases. When I talk privately was saying, we don't really believe in multi cloud. We have multiple clouds, but We're investing in people on certain stacks that fit our guiding principles of what we're building as a company. And they said we then go to the suppliers and saying, Here's the AP eyes we want you to support So you start to see the shift from being hiring the general purpose software vendors to come in and supply them with I t stuff Were hardware. As Mark pointed out, too much more, the customer saying No, no, this is our spec build that we built it. And so the trend that points to the trend of a reinvestment of building tech at the core of the business, which would imply to Mark's point around their tech companies. What's your thoughts on this? >> So a nuance. My answer. I think their tech enabled companies more than tech companies like Tech is enabling, whether it's Google or into it or pay power of the other companies. Mark mentioned technologies the base of their companies stack, um, then to go into your security portion, security has to be architected and embedded into the core solutions not bolted on after the fact with vendor solutions like it is today, and I think we've proven time and time again, including the capital one issue as a day or two ago that the current approaches are not working. And, uh, I agree with whomever See says you've been talking thio like being driving a P I integrations and be consumptive of them and telling what you need to build is a much better approach. Would you want to build a custom house with that actually talking to your builder and finding out later? What? What features and pictures have been installed in your home. But what do you wanna have a hand in that from the ground up? I think that's the mischief. >> Well, I want to come back to the capital. One point that's gonna be a separate talk track. So let's hold that thought. Rob, I want to go to you. Because StarBeat Joel, whose prolific on these threads you know, posting is nice Twitter cards on their um, he said, If you know, talk about leasing out extra capacity in a private data centers question Mark, you know, teasing out the question. And then Ben Haines responded and said, Why the hell would you want to be in that business when you have a real business to run again to what Mark was saying about, You know, Tech is going to be everywhere. Why should I even be in the data center? Because I don't want to be in that business. I gotta figure out Tech for the business. So Ben kind of brings that practitioner perspective. What's your thought? Because you're in the middle of this with the devil's movement. Bare metal, big part of it, Your thoughts. >> Yeah, And that's why we really focus on fixing the bear mental problem. Andi, I want to come back to where a bear metal fits with all this because you really can't get away from bare metal. I think the first question is really is every day to send is every business in I t business. And you know, not every business is a Google and strictly a nighty business. But what we're seeing with machine learning and Internet of things and just extension of what was traditionally siloed I t or data center, I t into everyday operations. You can't get away from the fact that if you're not able to take in the data, work with the data, manipulate and understand what your customers were doing. Then you are going to be behind. That's That's how you're gonna lose. You're gonna be out of business on. So I think that what we're doing is we're redefining business into not just a product that you're selling, but understanding how your customers air interacting with that product, what value they're getting from it. We really redefined supply chain in a very transformative way compared to anything else. And that's an I T enabled transformation. >> Ben brings up a good point, but the Brent wanted Friends Point is essentially teasing out mark and yourself a bare metal. All this stuff is complicated. Cut and make investments. Ben's teasing as What the hell business do you want to be in? I think that becomes a lot of this digital transformation. Conversation is Hey, Cloud is an easy decision. We were start up 10 years ago. We don't have I t. We have 50 plus people on growing. We're all in the cloud. That's fine for us. Dropbox started in the cloud. All these guys started class. It's easy as hell to do it. No, no debate there. But as you start thinking, Maurin Maur integration as a big enterprise which wasn't born in the cloud. This is where the transformations happening is what business? What the hell they doing? What's what's the purpose of their >> visit? Yeah, but the reality of you, a cloud infrastructure and how cloud infrastructure is structured does not really take you away from owning how you operate and run that infrastructure, right Amazons than an amazing marketing job of telling everybody that they're not smart enough to run their own infrastructure. And it's just not true way definitely let operations get very lax. We built up a lot of technical debt that we we need to be able to fix. An Amazon walked in and said, This is too hard for you. Let us take it off your plate. But the reality is people using Amazon still have toe owned their operations of that infrastructure. The capital one didn't doesn't get to just get a pass and say, I used Amazon. Oh, well, Too bad. Talk to them. You still own your infrastructure. >> Technically, it wasn't Amazons fall, so let's get the capital. One is this brings up a good point. Converged infrastructure was the Holy Grail, savior for the I t If you go back when we started doing Cuba interviews, stupidity and I would talk about converged is awesome. You got Nutanix kicked ass and grew like crazy. And so then you have the converge kind of meat's maker. When it sees the cloud, it's like, OK, I got great converged infrastructure, but yet the breach on capital one had nothing to do with a W s. It was basically an s three bucket that the firewall Miss configured. So it was really Amazon was a victim of its simplicity there. I mean, there's a >> I mean, this is this is what we're talking about with. To me with this tweet is that we need to look, we need to be better at operating the infrastructure we have, whether it's Amazon or physical assets on your premises. What we've really done is we've eroded our ability to manage those pieces well and do it in a way that builds on itself. And so as soon as we can get on improvement there, I mean, this this is where I went with this threat is if we can really improve our operational efficiency with the infrastructure we have, whether it's in the cloud on premises. You create benefits there than everything you build on top of that is gonna have a nim prove mint, right. We're gonna change the way we look at infrastructure. Amazons already done that on. We think about infrastructure in cloud terms, but I don't think that what they've done is the end destination. They just taught us how to be better running infrastructure. >> Well, it brings up that it brings up the point, and I have so Mike shaking his head to get his thought and mark on this. If I is that I tease problem our operational technologies problem because the world's not as simple as it used to be. It was not. It wasn't. It's not simple. You got edge. You get externally incest cloud players now multi cloud. So information technology teams and operational technology teams whose fault is it? Who is responsible thing? Could you just had a AI bots managing the the filtering and access to history buckets that could have been automated away? What, Whose problem was it? Operations, technology or I t. >> So that I think, to touch upon what Rob was talking about. There's my chain and technology, uh, from the classic sound byte is people process and technology. The core cause of literally every security breach, including capital one is a lack of sophisticated process and the root cause being people, and there's no amount of a I currently that can fix that. So you have to start focusing on your operational supply chain processes, which has, Rob said. Amazon has really solidified, and the company should look to emulate that forces trying to emulate the cloud infrastructure and some of your processed and your people challenges first. And then you can leverage the technology. >> Great point. Totally agree with you on that one >> market. Yeah, I would agree with everything that both Mike and Rob just said, and I would just add that we we don't have any choice but to face the future. That is, I t. And in order to provide the best possible service to our customers for our applications that even haven't been built yet, we have to look at the service is that are available to us and utilize them the best way possible and then find appropriate management and, like so correctly put it supply chain processes for managing them. So I've talked to people who are building unique cloud platforms internally to solve a specific business problem in ways that the individual clouds offered by the Big Three is an example can't do or can't do as well or can't do is cheaply. And the same thing applies to customers who are just using more than one of the big cloud providers. Even for some in some cases, for workloads. That might seem similar because each of the clouds provide a different opportunity associated with that specific set of requirements. And so we don't have any choice but to manage it better. And whether it's we make a choice to use it in our data center because it's more cost effective long term. And that's our single most important driver. Or whether we decide to leverage every tool in our tool belt, which includes a handful of cloud providers. And some we do our own, um, or we put it all in one cloud. It doesn't change our responsibility for owning it correctly, right? And my simple message really was that you have to figure out how to own and I'll steal from Mike again. You have to figure out how to own that supply chain. But more lower down more base is ifs. Part of that supply chain is delivering compute into a data center or environment that you own. Then you have to find the tools capabilities to ensure that you're not making the kind of mistakes that were made with capital or >> or, if you have tools are networks and tools you don't know and look at the quotes. So called scare with the China hack from Super Micro. That's a silly why chain problems? Well, it's on the silicon. So again, back to the process, people an equation. I think that's right on this brings us kind of through the next talking track. I want to get your thoughts on, which is cloud two point. Oh, I mean, I'm putting that term out there on Lee is a provocative way. Remember, Web to point. It works so well in debating about what it what it was. If one if cloud one data was Amazon Web service is, thank you very much. Public cloud. You could say cloud two point. Oh, our second inning would be just what happens next because you're seeing now a confluence of different dynamics edge, um, security, industrial edge. And then you know this all coming into on premises, which is hybrid and public, all working together. And then you throw multi cloud in there from a complexity standpoint. Do you wanna have support Microsoft's Stack, Azure Stack, Google and Amazon? This is this is the fundamental 2.0 question. Because things are more real time. Things are data specific. This costs involved. There's really network innovation needed what you guys thoughts on cloud to point out. >> I think the basic cloud 2.0, is moving to the shared responsibility model. And we should stop blaming people for teams for breaches as architectures become much more complex, including network computing, storage and in service orchestration layers like kubernetes, no one team or individual, individual or one team and manage all of that. So you're all responsible for infrastructure, scalability, performance and security. So I think it's the cultural movement more than the technology movement at the base of >> Rob. What's your definition? Cloud 2.0, from your perspective. >> Oh boy, I've been calling it Post Cloud Is my feeling on this? Yeah, it to me. It's it's about rethinking the way we automate. Um, you know, we really learned that we had to interact with infrastructure via automation and eliminate the human risk elements of. This doesn't mean that we have an automation is foolproof either It's not, but what? What I think we've seen is that people have really understood that we have to bring the type of automation and power that we're seeing in clouding the benefits because they're very riel. But back into everything that we do. There's no doubt in my mind that infrastructure is moving back into the environment. Where is what? Which is EJ from my perspective, and we'll see computing in a much more distributed way and those benefits and getting that right in the automation. Is this necessary to run autonomous zero touch infrastructure in environmental situations. That is gonna be justice transformative, freighted that that environment makes the cloud look easy. Frankly, >> Mark, what's your take? I want to get because, you know, security houses, one element get self driving cars. You got kind of a new front end of of EJ devices, whether it's a Serie Buy Me a song on iTunes, which has to go out to a traditional system and purchase a song. But that that Siri priest is different than what? The back end? Does this simply database, Get it? Moving over self driving cars, You're seeing all kinds of EJ industrial activity. You know, the debate of moving compute to the data. You got Amazon with ground station, all these new infrastructure physical activities going on that needs software to power it. What, you're in cloud to point. It seems to be a nice place not just for analytics, but for operational thing. Your thoughts on cloud to point out >> Well, I mean you you describe the opportunity relatively well. I could certainly go in. I've spent a lot of time going into detail about what EJ might mean and what might populate edge and why people would use it. But I think from if we just look at it from a cloud 2.0, standpoint, maybe I'm oversimplifying. But I would say, you know, if you add on to what Mike and Rob already so well pointed out is that it's best fit right, it's best fit from compute location, Thio CPU type Thio platform on, and historically, for I t they've always had to make pragmatic choice is that I believe, limit their ability on Helped to create Maur you know, legacy Tech that they have to manage, um on and create overhead tech debt, as they call it on DSO. I think judo. And in my book the best case for two Dato is that I can put best fit work where I need it when I need it for as long as I need it. >> That's that's really kind of gasp originals. Well, people got to get the software stood up. That's where I think Kubernetes has shown a nice position. I want to extend this track to another thought, another topic around networking. So if you look at the three pillars of computing computing mean industry, compute storage and networking, cloud one daughter, you can say pretty much compute storage did a good job. Amazon has a C two as three. Everything went great. Networking always got taken to the wood shed. You know, networking was getting, you know, people were pissing and moaning about networking. But if you look at kind of things were just talking about networking seems to be an area that this cloud 2.0, could innovate on. So wanna get each of your thoughts on? If you could throw the magic wand out there around the network doesn't take the same track as Dev ops that gets abstracted away because you see VM wear now doing deals. All the cloud providers they got they're going after Cisco with the networking PCC Cisco trying to be relevant. The big guys you got edge, which is power and network connection. You need those things. So what is the role of the network? And two point If you guys could wave the magic wand and have something magically happen or innovate, what would it be? >> Oh, wait, it's part complaining. It's your world. You know, it's ironic that I said this Thio competitors to my most previous company. Ericsson Company was away. They asked me after an event in San everything was a cloud expo. I just got off stage and the gentleman came up to me and asked me So mark you the way you talked about Cloud. I appreciate the comments you made yada, yada, yada. But what do you think about networking? And I said Well, network big problem right now is that you can't follow cloud assumptions as faras usage characteristics and deployment characteristics with networking. When that problem is solved, will have moved light years ahead in how people can use and deploy i t. Because it doesn't matter if you can define workload opportunity in 30 minutes on an edge device somewhere or on a new set of data centers belonging to Google or 10 Cent or anybody else. If you can't treat the network with same functionality and flexibility and speed to value that, you can the cloud then, um, it's Unfortunately, you're really reducing your opportunity and needlessly lengthening the time to value for whatever activity it is. You're really >> so network, certainly critical in 2.0, terms have absolutely that Mike any any thoughts there? >> So I think you know, there's there's easy answers to this that are actually the answer. You know, I P v six was the answer from a couple years ago, and that hasn't solved in the fantasy of the solved. All the problems, just like five G is not gonna magically transform our edge infrastructure into this brilliant network. The reality is, networking is hard and it's hard because there's a ton of legacy embedded stuff that still has to keep working. You can't just, you know, install a new container on container system and say, I've now fixed networking. You have to deal with the globally interconnected MASH insistence. I think when we look at networking, we have to do it in a way that respects the legacy and figures out migration strategies. One of the biggest problems I see that a lot of our technology stacks here is that they just assume we're gonna pave over the problems of yesteryear, nor them and with network, when you don't get that benefit, what you described with cloud networking, never living up the potential, it's because cloud networking isn't club networking. It's it's, you know, early days of the Internet. Networking is still what we use today. It's not. It's not something you can just snap your fingers and disrupt. >> Well, I mean, networking had two major things that were big parts of a networking and who build networks knows you provisioned them and you have policy stuff that runs on them, right? You moving paintings from A to B, then you got networks you don't own right so that's kind of pedestrian, old thinking. But if you want to make networks programmable to me, it just seems like they just seem to be so much more there that needs to be developed, not just moving package. Well, >> you just said it's traditional. Networks were built first, and the infrastructure was then built around them or leveraging them, so you need to take like in zero. Trust paper. When Bugsy Siegel built Las Vegas, he built the town first and then put the roads around the infrastructure. So you need to take that approach with networking. You need to have the core infrastructure of first and then lay down the networking around to support it. And, as Mark said, that needs to be much more real time or programmable. So moving from ah, hardware to find to a software to find model, I think, is how you fix networking. It's not gonna be fixed by a new protocol or set of protocols or adding more policies or complexity to it, >> so you see a lot of change then, based on that, I'd take away that you see change coming to networking in a big way because Vegas we're gonna build >> our if it has to happen. The current way is not working. And that's why we need the bottlenecks. Wherever >> Mark you live in is the traffic's brutal. But, you know, still e gotta figure out, You know, they got some more roads. The bill change coming. What are your thoughts on the change coming with this networking paradigm >> show? I mean, there are a few companies in the space already. I'm going to refuse to name anyway at this point because one of them is a partner of my new company, not my new company, but the new company I work for and I don't want to leave them out of the discussion. But there are several companies in the space right now that are attempting to do just then just that from centralized locations, helping customers to more rapidly deploy network services to and from cloud or two and from other data centers in a chain of data centers. Programmatically as we've talked about. But in the long run, your ability to lay down networking from your office without having to create new firewall rules and spend months on on contract language and things like that on being able to take a slice of the network you already have and deploy it on DDE, not have to go through the complex Mpls or Or VPN set ups that are common today on defectively reroute destinations when you want to or make new connections when you need to. Is far as I'm concerned, that's vital to the success of anything we would call a cloud two point. Oh, >> well, we're gonna try tracks when he's hot startups. So you guys see anyone around this area? I love this topic. I think it's worth talking a lot more about love. Love to continue on with you guys on that another. Another time. Final five minutes. I'd love to spend with you guys talking about the the digital transformation paradox. Rob, we're talking before we came on camera. He loved this paradox because it's simply not as easy to saying Kill the old man, bringing the new and everything's gonna be hunky dorey. It's not that simple, but but it also brings up the fact that in all these major waves, the hype outlives the reality, too. So you're seeing so I want to get your thoughts on digital transformation. Each of you share your thoughts on what's come home to be realistic in digital transformation, which what hasn't showed up yet in terms of benefits and capability. >> I mean, this is this to me is one of the things that we see happen in every wave. They people jump on that bandwagon really hard, and then they tell everybody who's doing the current stuff, that they're doing it wrong. Um, and that that to me, actually does a lot more heart. What we what we've seen in places where people said, burn the boats, you know, we don't care. They have actually not managed to get traction and not create the long term sustainability that you would get if you created ways to bring things forward. Networking is a good example for that, right? Automating a firewall configuration and creating a soft firewall or virtual network function is just taking something that people understand and moving it into a much more control perspective in a lot of ways. That's what we saw with Cloud Cloud took working I t infrastructure that people understood added some change but also kept things that people 1% and so the paradox. Is that you? Is it the more you tell people, they just have to completely disrupt and break everything they've done and walk away from their no nighty infrastructure, the less actually you create these long term values. And I know there are people who really know you got totally changed everything that disrupted value. But a lot of the disrupted value comes from creating these incremental changes and then building something on top of that. So what? So >> what did what Indigenous in digital transformation, what has happened? That's positive and what hasn't happened that was supposed to happen. >> So when I look att Dev ops on what people thought we were going to do, just automate all things that turned out to be a much bigger lift than people expected. But when we started looking at pipelines and deployment pipelines and something very concrete for that which let people start in one or two places and then expand, I think I think, uh, pipelines and build deploy pipelines are transformative, right? Going from a continuously integrated system all the way to a continuously integrated data center. Yeah, that's transformative. And it's very concrete just telling people automate everything is not been as effective >> guys. Other thoughts there on the digital >> transformation dream. I agree with everything that Rob just said, and I would just add just because, you know, it's the boarding piece that someone always has to say, and nobody in Tech everyone is he here? But you know, every corporation at one point or another in its Kurt in its life span faces a transformative period of time because of product change or a new competitor that's doing things differently, or has figured out a way to do it cheaper or whatever it is. And they usually make or break that transformation not because of technology, not because of whether they have smart people, not because of whether they implemented the newest solution, but because of culture and organizational motivation and the vast majority of like Everything, Rob said doesn't just apply to I. T. A lot of the best I T frameworks around Agile and Dev ops apply to how the rest of the organization can and should react to opportunity so that if I t can be and should be really time, then it only makes sense that the business should be able to be real time in responding to what is being created through I t systems. And right now I would argue that the vast majority of the 80% of transformations that don't see the benefit that they're looking for have nothing to do with whether they could have gotten the right technology or done the technology correctly. But it has to do with institutional culture and motivation. And if you can fix that, then the only piece all add on to that. That again I vociferously, really agree with Robin is that if you want to lower the barrier to entry and you want to get more people into this market, you won't get more people to buy more of your stuff and grow what they own. Then you have to be able to show them a path to taking, getting the most value out of what they already have. There is no doubt in my mind that that's the only way forward, and that's where some of the tools that we're talking about and what we're talking about today on Twitter or so important >> Mike final stops on the >> docks >> on your thoughts on the transmission paradox, >> so the paradox that Robb describe think is set, the contact is set incorrectly by calling it digital transformation should be digital revolution, where the evolution process doesn't end. Transformation makes people think that there's some end state, which means let's burn the votes. That's let's get rid of all over all on prime infrastructure moved to cloud and we're done. And really, that's only the beginning. Which is why we're talking about Cloud two point. Oh, do you have to take that approach that you want to have continuous evolution and improvements, which Segways into what Rob said about de box and automating all the things you don't automate your tasks and processes and you're done? You want to keep improving upon them. Figuring out how to improve the process is and then change the automation five that the is, Mark said. It's a cultural and mental shift versus trying to get to this Holy Grail and state of transforming transformation. >> Awesome. Well, why I got you guys here first off. Thanks for spending the time and unpacking these big issue. Well, two more of it. I'd >> love to just get >> your thoughts real quick on just your opinion of Capital One. The breach, survivability and impact of the industry. Since it's still in the news, who wants to jump for us? We'll start with Mike. Mike, start with you will go down the line. Mike, Robin Mara. >> I mean, the good news for Capital One is I don't think any personal information was breached that hasn't already been exposed by the various other massive reaches. Like I do my so security number as a throw away at this point which never should have been used for identity. But I want All >> right, So there were Do you think >> it's recoverable is not gonna be as critical, say, Equifax, which was brutal. >> It doesn't sound like there was negligence where Equifax seemed like it was Maura negligent driven than just ah ah, bad process or bad hygiene around a user or roll account and access to a certain subset of data. >> I mean, this was someone who stumbled upon open history bucket and said, >> Well, well, look at this >> bragging about it on Twitter and the user groups. I mean, this >> was like from from what the press said, I think there's other companies that may or may not be affected by this as well, so that it's just capital one, which will probably defuse the attention on them and lessen the severity or backlash. >> Rob your thoughts on Capital One. >> Yeah, I wish it would move the needle. I think that we have become so used to the security of breach of the week or the hardware. Very. You know, it is we We need to really think through what it's really gonna take toe treat security as a primary thing, which means actually treating operations and infrastructure and the human processes piece of this, um, and slowed down a little bit. Um, and I always saw >> 11 lawmaker, one congressman's woman said, More regulation. >> Yeah, they don't want this. I don't think regulation is the right is the right thing. I don't know exactly what it is because I think >> regularly, we don't understand. That's Washington, DC, >> But but we're building a very, very, very fragile I T infrastructure. And so this is not a security problem. It's a It's a fact that we've built this Jenga tower of I t infrastructure, and we don't actually understand how it's built, Um, and that I don't see that slowing down. Unfortunately, >> unlike Las Vegas is, Mike pointed out, it's was built with purpose. They built the roads around the town. Mark, you live there now What's your thoughts on this capital? One piece ends and >> I have been said I would say that what I'm hoping sort of like when you have, ah, a lack of employees for a specific job type. Like right now in United States, it's incredibly difficult to find a truck driver if you're a trucking company, So what does that mean? But that means it's gonna accelerate automation and truck driving because that's the best alternative, right? If you can't solve it the old way, then you find a new way to solve it. And we have an enormous number of opportunity. He's from a process standpoint, but also, from a technology standpoint, did not build on this. Pardon my French crap that we have already >> they were digital. Then, when I ruled by the FCC, >> had build it the right way from the start. >> Well, you know what was soon? How about self driving security? We needed guys. Thanks for spending the time this cube talk. Keep conversation. Appreciate time. Mike, Rob mark. Thanks for kicking it off. Thanks. >> Thank you. >> You're watching Cute conversation with promote guests. Panel discussion Breaking down. How businesses should look at technology as part of their business. Cloud 2.0, security hacks and digital transformation Digital evolution. I'm John free. Thanks for watching.

>> Narrator: From the SiliconANGLE Media office in Boston, Massachusetts, it's the Cube. Now here's your host, Dave Vellante. >> Hi everybody, welcome to this special Cube conversation with a practitioner, a real-world enterprise journey to the Cloud. I'm here with Jake Burns, who's the Vice President of Cloud Services at Live Nation Entertainment, in from L.A. Jake, thanks for coming in to our Marlborough Studio, appreciate you having in. >> I'm glad to be here. >> So tell me about your role. >> So, I'm head of cloud services for Live Nation, and what that means is, me and my team are in charge of infrastructure for IT, including cloud infrastructure, as well as the move to the cloud, which we completed early 2017, enterprise messaging, which includes e-corporate email, DNS, database services, and storage management. >> So, recent journey. How did it start? Was it a top-down push, did you go to management and say, "Hey, we got to do this," describe that dynamic. >> Yeah, so it started off as kind of a bottom-up push. >> Dave: Really? >> For a number of years I've been really wanting to get us involved in public cloud, at least in some level. But, it really didn't hit critical mass until our CEO, late 2015, had a mandate that we're going to move 100% to cloud, and modernize all of IT. And that's when we really hit the ground running. >> Why did, from a bottom-up standpoint, why did you guys want to do that? Was it because cloud's cool, that's where all the action is, the developers want to be there, or was it something else? >> We spent a lot of time managing infrastructure and data centers, and it's just not part of our core business. We wanted to focus more on satisfying the business, and providing value to the business. And, our time could be better spent really helping solve their problems, rather than deal with hardware and systems. Another thing is just business agility in general. If we want to stand up a new system, the typical lifecycle could be three to six months, just to get an application up and running. With cloud, we can do that in days, weeks, worst case. So, being able to respond quickly to business needs is something that's really important to us, and we saw with public cloud that we could do that a lot more efficiently. >> And when you think about the early cloud days, the rhetoric was all about agility, and it actually, that really was the main business benefit. You guys of course saved a lot of money too, and I want to get into that, but how did you get started? It must have been, kind of a little nervous, like the first time you jumped off a high cliff or something. Right, because you have an existing business to run, and yet you're going to migrate everything. Migrate's like this evil word, so how did you get started? >> For us, we realized very early on that this was a big technology change for us, and it was going to require new skills that we didn't have, so the first thing we did, was we really just got training across the board. We brought trainers from AWS to our offices, and we did every training program that they offered. Got the certifications. And made sure that we really understood what we were dealing with before we got started. So that was really step number one. >> And how did that go? Were they really supportive? Everybody says AWS, really not hands-on, they just send me an email. How did that go? >> In the beginning, there's resistance. Just like all projects like this, people are concerned they're going to lose their jobs. >> Dave: Resistance from your guys. >> Oh, yeah, yeah- >> Not the AWS people, they were- >> Oh, no, of course, right. No no, our guys, before they really understand the situation, it looks like we're being outsourced. We're moving all of our infrastructure. This is our job. We're managing hardware, we're managing servers, we're managing data centers, and all that stuff's going to go away, so what are we going to do, right? So, really, even before the training, the priority for me was to get people to understand that this is not something that's a danger for your career. Quite the contrary. This is going to make you more valuable. You're going to get trained on this technology. You're going to get real world experience, moving a Fortune 500 company to the cloud, and at the end of this, someone is going to need to maintain it. So not only will you have job security, but you're probably not going to care about job security at the end of this, because you're going to be so valuable in the marketplace. >> So, we're all in sales, aren't we? So you had to sell them a little bit on the concept, but then they responded positively, it sounds like. >> Yeah, and part of that is because it's the truth. I was telling them the truth, so it was an easy sell. But it's a very important component of any cloud migration project like this. If you don't have support from your people, it's not going to succeed. >> Okay, so you get through the training. Your guys are onboard, you have alignment there, and then take us through sort of the journey. How long did it take, what were some of the challenges that you faced? >> The target was 12 months to move everything, and we're talking about 668 servers, 118 applications, including Oracle, SAP, some really things that are not trivial to move to the cloud. We were able to move 90% of everything in 12 months, and then the long tail took an additional five months, so that's 17 months in total to move everything. >> And that long tail, was that the Oracle apps? >> Yeah, so our strategy was to move the easy stuff first, as we learned, because we learned along the way. We really didn't know what we were doing when we started. By the end of the project, we knew exactly how to do the project. >> Easy stuff like messaging? >> Like single server applications that are running supported software, where we have a business stakeholder that's cooperative. >> Dave: Web stuff? >> Yeah, like internal stuff, like our monitoring systems, things that we completely control. >> Dave: Things that were under the control of IT, didn't involve a lot of politics, and ... >> Jake: Exactly. >> Learn there, okay. >> Right, so the idea was, get real world experience moving live production systems on the easy stuff, and it kind of builds up our skillset, but at the same time it builds forward momentum, which is critical for a project like this. There's a lot of people that are just waiting for the first failure to kind of put a stop to the whole thing, right? There's a lot of skepticism as to whether this can even be accomplished or not. So, getting, I truly believe a key component for a project like this is to get momentum on your side early on, and the way you do that is by attacking the easy problems first, and then get progressively more difficult as you go along. And so at the end, you end up with the most difficult applications to move, but at that point, you have full buy in from everyone because you've been successful so far, and you and your team are practiced and accomplished, and have the skillsets necessary through moving all the more easy stuff before that. >> Okay, and just a quick aside, I have to ask. So, Oracle is kind of using licensing as a weapon, especially, there's this, I call it urinary Olympics, sorry, with Oracle and AWS. You may not have visibility on it, if you don't we can move on, but was that a concern? >> Absolutely, yeah. So this was a major problem that we've had to deal with, and Oracle doesn't make it easy. They don't necessarily want their customers moving to AWS. So, that was part of the challenge. Part of the challenge was, how do we move this without having to pay more in licensing? And what it really comes down to, is you have to make your Oracle databases run more efficiently in AWS, in order to lower the core count, which is what the licensing is based on, in order to keep your costs neutral, because Oracle will charge you double for your database, per processor, in the cloud in AWS than they will on prem. So, really the only way around that, besides negotiating with Oracle if you're able to do that, if you're not able to do that, then your only option is to make it run twice as efficiently from a processor standpoint. >> Thank you for sharing that with our audience. We've written a lot about ways to reduce your core count. Ways to make IO optimized, and if you can do that, you can actually save a lot of money. Maybe we'll have you back on at Reinvent, and we can talk more about that. But so, back to your story here. You got a huge budget to do this, right? Big bag of money to say, go move to AWS? >> Unfortunately, we didn't have that luxury. So, we run very lean. So we had essentially a flat budget, 2016, when we did the majority of these moves. So we just had to find a way to do it without spending money. And so, it was a bit of a juggling act. We were decommissioning systems in the data center, and canceling support contracts, so we were able to kind of use some of that money and repurpose some of that money for moving to AWS, but we really didn't have a budget for hiring consultants, or to buy expensive software, or anything like that. So, what we had to do was, basically become the consultants, to do the cloud migration. And so, that's where that training comes into play. So by training the team, and getting them up to speed, and essentially creating cloud engineers, we were able to be internal consultants to the business, perform the move internally at a very low cost. >> All within that sort of 12/17 month timeframe, you were able to affect that skills transition. >> Right, so we were simultaneously maintaining the old infrastructure, moving the infrastructure to AWS, and maintaining the infrastructure in AWS. So there were a lot of long hours. >> I'll bet. That's weekends. >> But, we were enthusiastic about doing it. Everyone was very excited once we got going, and so people were willing to do it. You talk about the people challenges. I think we've addressed that a little bit anyway. What were some of the other challenges? You got a reasonably sized application portfolio, you got data, you got your backup systems. What were some of the challenges that you faced, and how did you address them? >> Yeah, so that's a great question. One thing that people don't realize is that AWS isn't necessarily designed for enterprise applications. It's getting a lot better. But, there are some things where it just doesn't fit automatically. So, one area where that's especially true is with storage. AWS has a fantastic storage offering, especially with S3, their object storage. But unfortunately, most enterprise applications, they can't utilize. Legacy enterprise applications won't utilize object stores, they want block storage. >> They don't want get put, they want block storage, okay. >> Yeah exactly. And then the block storage in AWS is different than the block storage than what you're used to in the data center, typically. So, kind of allowing these applications, like Oracle, to work on AWS's block storage can be a challenge. It can be expensive, and there can be some risk there, just because of the way that it works. So, this is where using a third party makes sense. This is one of the rare circumstances where I think using a third party makes sense. We found a company called Actifio that does virtual storage in AWS, and one of the great things about this product is it essentially mimics the way that the old storage worked in our old environment, in our data center. So the application continued to function. So we're able to take snapshots, we're able to clone environments, we're able to do all of these things that we are not able to do in AWS natively, with the Actifio product. And it saved us a lot of money, and allowed us to avoid a lot of having to change our workflows to get around some of the delays with doing snapshots and stuff natively. >> And is your strategy to have this sort of hybrid approach between on prem and public cloud, or multiple public clouds? Is that part of the strategy, and how does this capability fit into that? >> Yeah, it's a great question. Our initial strategy was 100% going all in with AWS, and officially that's still our strategy. I am a proponent of multi-cloud in certain circumstances. For example, disaster recovery and backups, I think it makes sense, if your 100% in the cloud, to have a second cloud provider to hold your backup data, just so you don't have everything in one place. I think, for the same reason, hybrid cloud makes a lot of sense. And I think also hybrid cloud makes a lot of sense, just because not all applications are a good fit for a public cloud, and Oracle, SAP, would be two of those examples. Now we were forced to move everything to AWS, and it was a fun challenge, and we were able to accomplish that. But doing it over again, if we had the option of doing hybrid cloud, there may be a couple applications that I would say keep it on prem, because it just works better that way. >> And, can you double click on the storage virtualization capability that you talked about. Kind of how does that work, and how do you have to ... Were there any kind of things that you had to do to prepare for that? Any sort of out of scope expectations that customers should be aware of? >> With Actifio it's a pretty turnkey solution. So, there's a little bit of a learning curve, but there's a learning curve with using the AWS native tools as well. So I would say probably less of a learning curve if you use a product like Actifio, because it's more familiar to the people that are already working on these systems. So if you have existing staff, and they're used to doing things in the data center, and they're used to doing things with traditional enterprise storage, the Actifio tools is going to look a bit more familiar than the AWS tools. So, there's a learning curve either way, but I would say look at a product like Actifio if you're an enterprise trying to do this. >> So what was the business impact of using Actifio? Then I want to ask you about the whole move to AWS. Did it speed the time to deployment for AWS? Did it help you cut cost? What was the business impact? >> Unfortunately, we didn't become aware of this product until after we had moved. So, we're in the process now of replacing some of our storage devices with virtual storage with Actifio. But I wish we had found this product sooner. I advise anyone who's new at this, anyone who's doing a migration, to leverage something like this to actually move their data, because it's a much more efficient way to do it. So, if I could go back in time, I would do that. >> What would have been the business impact? Is this time and money? >> Yeah, time and money, for sure. So, the moving of the data is one of the biggest challenges that you're going to have moving to cloud. We had a petabyte of data that we had to move, and that's no small task to get that moved in 12 months. So, any tool that you can use that can make that more efficient, is going to shorten the amount of time you're going to be doing the migration. And, consequently, shorten the amount of money that you spend doing the migration. Also it would have saved us a lot of time, because now we're going back and having to change things, and put things under Actifio. If we would have done it like that to begin with, we wouldn't have to spend that effort after the fact. >> Why does Actifio make it more efficient? Is it data reduction? Is it automation? >> So essentially the biggest benefit is that it allows you to not have duplicates of your data. So, if you have a dozen or so copies of your database, for different types of environments, test, UAT, dev, etc., and you're duplicating those, and storing each one of those separately, you're going to pay for each one of those separately, and have to manage each one of those separately. If you're able to use virtual storage, then you really have one copy of the data, or however many copies of data you really need to be protected, and the rest of those can be virtual copies. And those don't cost you anything from a storage point of view. The other benefit is, if you want to clone an environment, or copy an environment, or take a snapshot of an environment, it can happen instantaneously, rather than wait for the hours or days that it would take to copy a large dataset. >> So it becomes the single point of control, with a catalog, and give you visibility over all your data, and your copies, and allows you to manage that, is that correct? >> Yeah, and the management becomes a lot easier, because you have software that's keeping track of your snapshots, and keeping track of all your copies of data, rather than try to track that all manually. >> Okay. Let's bring it back to the big AWS picture. So you move to the cloud. What was the business impact of that? You mentioned agility. Did you save money? How much? Maybe give us some visibility on that. >> Because we're so cost conscious, saving money was a priority. I don't think it's necessarily something to expect, especially initially, if you're an enterprise moving to the cloud. Cost shouldn't be the driver. Agility should be the driver. But, in our case, we were able to achieve 18% reduction in TCO, on year one. And, that's just because we were just very focused on cost. We're very cost sensitive, and it's very important for us to be efficient, and to not spend money unnecessarily. I know that's a priority for everyone, but it's a top priority for us. And so, my point is it can be done. You can move to the cloud. You can move 100% to public cloud if you're an enterprise, and you could make it cost neutral, or even favorable. It is possible. >> So you hear a lot of stuff in the press about how the cloud is very expensive. You could actually do it cheaper on prem. Based on your experience, you don't buy that. >> Well, I wouldn't say that's false. You can, in a lot of circumstances, do it cheaper on prem. It really depends on the workload. So I mentioned earlier that I think hybrid is probably the right approach for most people. So just because we're saving money by going 100% cloud, doesn't mean we wouldn't save more money if we went hybrid cloud, and put the more expensive things that run in cloud, on prem. So, because it's pay for what you use, the things that you very heavily utilize, those are good candidates to keep on prem. The things that are more bursty, those are the things that are better candidates to put in the cloud. The easiest things, candidates to put in the cloud, are disaster recovery and backups, those are no-brainers. DR because that's only something you need to scale up when you use it. So anything that you need to scale up when you use it, or anything that scales up and down, those are the best candidates for cloud. >> Okay, now I understand you're kind of an expert at cutting the AWS utility bill. Maybe you could give us some advice on how to do that, and how'd you learn how to do that? >> Yeah, so that's kind of my area of focus now, is now that we're in the cloud, getting those costs reduced as much as possible. So, there's a lot of ways to do this, but I like to keep it simple, and attack the things that have the biggest impact first. So, people like fancy solutions, but it's really simple. The biggest thing you can do is delete things you're not using. You're paying for consumption, so find things that are not being used, and simply delete them. After that, then find things that are oversized, and right-size them. And then, another big thing is, in the cloud, you have such an easy access to spin things up. To take snapshots of data, to copy data, and it's the classic problem in IT, where everyone requests what they want, and they never tell you when they're done with it. So, it needs to be a full-time effort, to be actively looking for resources that are unused. Snapshots that are no longer needed, volumes that are no longer needed, instances that are no longer needed, and be cleaning those things up on a continuous basis. I find that that's a large percentage of what my team does now, and that's one of the things that keeps our costs in line. >> That's interesting. We always talk here about GRS, getting rid of stuff. Not only did you get rid of a bunch of stuff when you moved in the cloud, you said 600 servers, you got rid of unused capacity, you got rid of a bunch of data, which must have made your general counsel happy, but you're now actively continuing to get rid of stuff. Like you said, it's volumes, it's snaps, and so the things, now you're in the cloud, that GRS mentality is sort of ingrained. >> It has to be. I think that anyone who's in the cloud for some time is going to realize this. You're going to have inflation of costs, simply by doing nothing. So, just to keep your cost neutral, you're going to have to be deleting things on a continuous basis. Now if you want your costs to go down, that's even more difficult. You have to be more aggressive with it. But, just as it's easier to spin things up in the cloud, the good news is it's easier to keep track of what you have, and find things that can be deleted in the cloud, because you don't have to go in the data center and track things down. Everything is virtual. It all can be automated. It's all done, it can be scripted. So, everything's easier. Spinning things up's easier. Cleaning things up is easier, you just have to make it a priority, and make sure it gets done. >> So, some of the financial people in our audience might be listening and saying, "Eh, you know, okay, year one. Roughly 20% savings. It's not that exciting." But we haven't quantified the sort of other business impacts in terms of agility, and that's a harder thing to quantify, but it's early days for you still. Do you expect to get on that S curve, and really start to see a major business impact, beyond that 17, 18%? >> That's a great question. That 18% reduction in TCO, that's just infrastructure costs, so that's not taking into account things like how long does it take for us to spin up an application, and what does that cost the business, that delay? We're not taking that into account. How about the opportunity cost of, we want to try something, but it's too expensive because we've got to buy servers, and we got to hire people to build the application, and install the operating system, all that kind of stuff. Those opportunity costs, they're not captured either. Now, we can try as many things as we want, very inexpensively, and only keep the things that work. So I think there's a lot of hidden cost savings, a lot of hidden value that's very difficult to capture. But, we certainly have those benefits, even if we're not articulating it, and counting it very well, the business feels it, and it's certainly a superior level of service. >> Well it's kind of like when we first got email. Nobody really quantified it, but the productivity impact was enormous. Or the first local area network that you ever installed, and the collaboration that that brought, it's one of those things that's, it's probably telephone numbers, but it's hard to quantify, right? You said the business people see it. Do the finance people see it as well, and are they supportive of this? >> Yeah, it takes a while I think for the non-technical teams to catch up, and really get to where we're at in terms of an understanding of what we're dealing with at this point. So, they're starting to see it. But, all the financial models have to change. All the budgeting needs to change. There's a lot of things that, beyond IT, this kind of transformation affects, and those processes have to change, and those processes generally change more slowly. So procurement needs to change, finance needs to change, security needs to change. Everything really, it's a new world. And once they catch up and kind of really grasp what we're dealing with, I think the whole business is going to be transformed. >> So two last questions. You talked about maybe things you'd do differently. Maybe some advice. But let's focus clearly on advice to your colleagues that are trying to do something similar, get to the cloud, what would you tell them? >> Invest in your people. Focus on cost savings day one. Don't look at doing that after the fact. And don't get too caught up in all the fancy methodologies, and fancy tools. Everybody's going to try to sell you something. Everybody's going to try to tell you they have the best way to do it. But, in general, those things are just going to add complexity to your project. I say keep it simple, keep it lean. Leverage your own people. Because at the end of the day, somebody's going to have to support this environment as well, and if you're relying too much on outside help, then they're not going to be there when it's all said and done. So, consider the endgame. Consider the end state, and how you're going to support that, because it's one thing to be successful migrating to the cloud, but then you have a whole new set of challenges after that. And you're going to have to live with that moving forward. And, I'm not saying it's a bad thing. It's a great thing. But it's something different, and you're going to have to be prepared for that. >> Own it. >> Jake: Own it. >> Yeah, okay. And then, last question, just sort of what's next for you guys? You're just sort of getting started here. You've made a tremendous amount of progress in a year and a half. What's next? Where do you want to take this thing? >> Like I said, right now we're really focused on cost optimization. I think that, like you alluded to earlier, the cloud could be very expensive. The range of how much it can cost is, it's amazing, right? So, this is uncharted territory. We don't know how expensive it should be, how cheap it should be. We just now that we can affect that, to a large degree. So I'm interested in seeing to what degree we can affect that, and I want to see how efficient we can make this. 18% favorable TCO is one thing. Let's see if we can get 30% or 40%. So, really I'm focused on optimizing for cost, security, which is a whole new world in the cloud, and going from there. >> Jake Burns, awesome having you on. Thanks very much for your insights. >> Jake: My pleasure. >> Really appreciate your time. And thank you for watching, everybody. This is Dave Vellante. We'll see you next time. (upbeat music)

>> Announcer: From the Silicon ANGLE Media office in Boston, Massachusetts, it's The Cube. Now here's your host, Dave Vellante. >> Hi everybody, welcome to this Cube conversation, eliminating barriers to enterprise multi-cloud. Multi-cloud is all the rage, all the buzz, it appears to be here and now David Chang is here, he's the Senior Vice President of Products and Co-Founder of Actifio and AppIQ, welcome back to The Cube, good to see you again. >> It's a pleasure to be here, thank you very much. >> You are very welcome, so eight years ago, you guys started this journey, the cloud was kind of new a little experimental, maybe put some stuff in the cloud and see what happens and then boom, all of a sudden it is become mainstream, your thoughts. >> Yeah it's been quite of a journey, I think when we initially started, we were focused around, all about making enterprise as efficient as possible, right. In the old traditional enterprise IT model, that resulted in net savings in terms of reduction to hardware, software, and so on and so forth. But in the cloud, now you're in a completely brand new category in terms of you're being charged on a per use basis. So all the technology we build out over the years just has a direct correlation to this new model of consumption that the cloud is enabling everybody to do. >> So if you think about when you started, platforms were really all mostly on prim, the definition of those platforms has really changed, it's sort of shifted from whether it's a server manufacturer or a storage type or maybe a networking type to the big cloud players, Amazon, Google, Microsoft Azure, Oracle's got a cloud, IBM's got a cloud, you see the China clouds emerge. How were you able, well first of all is that sort of an accurate view? That you guys had this sort of platform agnostic approach to your business and that platform has shifted. >> No that's absolutely true, I think we kind of walked into this by accident, because of some of the architectural advantages we kind of built into our infrastructure from the beginning. But, over the last eight years or so, our customer initially asked us how could we, Actifio, help them to enable them to go from a traditional IT to a private cloud type implementation. So we had a lot of traction in terms of the MSP's and private cloud implementations and that's where I would say four, five years ago, even now I would say we had a lot of traction and a lot of customers that came to Actifio for us to help them in that endeavor. But within the last four or five years we definitely see an acceleration of extending that infrastructure as a service platform from on-premise traditional IT to private cloud infrastructure now into the public cloud. So all the capability we kind of built, really applied very nicely to this new platform agnostic model regardless of where you want to go. >> Can we dig into that capability a little bit? What is it about your architecture, kind of your secret sauce, that makes you multi-lingual and maybe in this case, allows you to go from a world that is largely on prim, or managed hosted services, to one that's massive public cloud scale? >> If you think about it, the only thing that's constant as you move your application from IT, to private cloud, to public cloud, is the application, right. So from the beginning we had this very tight application focus, everything we do is from an application perspective. That really enabled us to play nicely, in terms of these platform shifts, from these one location to another, and fundamentally decouple the application and its data from the infrastructure. So now this normalization of this infrastructure really enabled our customer to make that switch very easily. >> So talk more about that, how do you do that, is it software code, is it architecture, give us some understanding. >> I think it's the approach that we take in terms of supporting of a lot of these data management and copy data functions. And it's really looking at the application data set as the entity that we want to focus on. And focusing on enabling the application as the entity that we add value. So what I mean by that is, if you look at a traditional Oracle database, say if you want to move that from a traditional, let's say an AIX type of environment into a Linux environment for your private infrastructure, so we really fundamentally decouple that application and enable you to very quickly migrate that information from that AIX infrastructure into a Linux environment. Then once that's done, our capability in terms, it's all software if you really, really enable us to kind of have a very efficient incremental tap to that database, and then move that information incrementally into the cloud. And once you're into the cloud, you can now make multiple virtual copies if you will, all consuming sort of the same amount of resources. So you have a drastic reduction in the capacity needed to do that. >> So it's your ability to essentially jailbreak the data from the siloed infrastructure, is that right? >> That's right, and I think four, five years ago we realized that cloud, the public cloud would be an infrastructure that we need to support in depth. So the engineering group has been looking at, for an application consumed cloud natively you have to understand a lot of new technology and new terminologies and new capability. Things like object storage, for example, is not something that a traditional application can consume readily, if you will, without going back and rewriting a lot of those applications. With Actifio, we enable our customers to not having to go back and retro-fit and rewrite these applications but be able to consume these new cloud technologies natively, so they can reap the value immediately versus having to go back and retro-fit their applications. >> One of the practitioners that we had on, of course very recently, Jake Burns was saying that even in AWS, the block storage really isn't kind of enterprise ready, friendly. I want to ask you a question about, if you think about the on-prim, you know block storage players that you guys eight years ago understood that you had to be compatible with, I'll use that term. Whether it was EMC, or Netapp, or IBM, or HP or whatever it was, were those block storage sort of interfaces, the entries and the exits all very similar and is it harder in the cloud or is it actually easier in the cloud, 'cause it's all sort of the API driven economy? I wonder if you could give us some insight there? >> I would say the foundation layer is much easier on the cloud. So as Jake was mentioning before, you don't have to order the hardware, hardware gets here, so the agility of this picture improves drastically when you move to the cloud. However, some of the cons of that, is a lot of the advanced features that you used to get on premise with these enterprise infrastructures, are no longer available on the public infrastructure. So in many ways, many of our customers, as they move into the cloud, a lot of the IT operational staff have to deal with a reduction in terms of capabilities or availability or time it takes to make that data, in terms of cloning and so on and so forth. So that's sort of, I think the challenges many of our customer are facing and that's where Actifio can help you with. >> Can we talk about this notion of rewriting apps, because in IT, if you have to rewrite the app, you got to freeze the code, if you freeze the code then you're enduring all this risk, you know if you have to freeze the code for N number of months, that's N number of months you can't keep up with your competition. So am I correct that your customers are not having to rewrite their apps, because of your ability to isolate sort of the data model? >> That's right >> And maybe you could talk about that a little bit and what impact it's had on your customer base. >> Yeah as you know, in the cloud, the economic is per use, and in the cloud the type of capacity you have to deal with tend to be in multiple categories, you have the EBS of the world which is relatively expensive compared with the object storage. So if you take just lift and ship, you enterprise the application model into the cloud where a lot, I would say most of your application data, is stored EBS, then you're not really fully utilizing the economics of the cloud. So how do you make effective use, in terms of minimizing the elastic block service on Amazon, versus the object storage capability that you have available. That is I think a difficult topic for a lot of the traditional enterprise applications doing the lift and ship, where you have to essentially go back and rewrite those applications to take advantage of the cloud native capability for you to really drive that availability and cost to the new level that you were expecting. >> So I've been in this storage business a long time, and I'm somewhat embarrassed to ask this question, but I have an architect here, a technologist, I'll ask you. When you think about block storage in the cloud, an EBS in particular, that was not Amazon's first announcement, did they announce that because they realized that they need to accommodate, you know block storage, to get more people from the enterprise or is there something specific about block storage that is here to stay forever? Another way of asking that is, can we run these applications on object storage? Is that the direction, thoughts on that? >> Yeah, I think it's going to be a hybrid model, right. So what Actifio really enables our customer to do, is not really running your production on object storage, but a lot of the secondary sort of data cloning, data analytics, and DR type of use case, you can shift, I would say, reduce your usage of EBS block storage to object storage. So we think that's the low hanging fruit that enable our customer to move to the cloud faster, cheaper, and with better capabilities. I think longer term as our customers start to develop applications that's native to the cloud, it's probably more efficient for you to consume some of these cloud native capability directly, but we're talking about a lot of time and resources that not all organizations will be able to afford to a high percentage of their applications moving to-- >> So new applications might be rewritten to take advantage of object storage and what about things like performance or latency and recovery et cetera, do you see the block storage world being able to get there? To actually compete effectively with, or the object to compete effectively with block or is that? >> We believe so, because if you look at object storage it's now proven over the last, I would say six, seven years, it's the most scalable storage that's available to the industry period, right. That scalability also enable you to reduce any hot spots that you may have from a performance perspective. So what Actifio's engineering group has done, is really leverage that capability, the ability for you to fully utilize the full bandwidth of that entire object storage, and having multi-parallel streams of access into that. So the way we look at object storage, it's just another access protocol, if you think about it, you have block storage, you have iSCSI, Fibre Channel, you have NFS access protocols. Object is simply another protocol that enables you to have persistent storage. And what Actifio has done is really leverage the performance and scalability characteristic of this object storage to have our customers, in terms of realizing value from day one. >> Is it true to your DNA, you don't really care whatever the customer chooses you're going to support it? If the whole world goes object, great no problem. If the world stays mixed. >> I think for the foreseeable future, it's going to be a mix environment, but as Jake was mentioning before, it's all about optimization in terms of capability and cost. And object storage is a key piece of that equation we can really enable you to kind of tweak that knob to exactly what you're looking for. >> When customers make a move to the cloud, it's a migration, any migration is risky, how does Actifio generally, and your product specifically, reduce that risk? >> I think it's all about keeping it simple, right, so the ability for you to kind of lift and ship your applications without having to go back to rewrite, that's a huge value proposition, or a huge reduction in terms of risk that you can achieve in your environment. The ability for us, for Actifio to tap your into your enterprise IT existing production environment without a lot of sort of dangerous or latency effect, is a huge value we can bring to the table as well. Because Actifio from day one, is designed to be very efficient in terms of tapping your applications data while it's running, while it's in production, right. So the ability for us to incrementally do that and move that information into the cloud effectively for you to do that migration process, can drastically reduce your risk if you will. >> Let's talk about cost a little bit. We heard a lot from Jake about cost, in theory anyway, you guys can help optimize, not in theory, in actuality, you can help me get rid of stuff I always say. Talk about the optimization angle, how have your customers taken advantage of that, we heard from Jake, you have some other favorite examples you can maybe share with us David? >> Yeah so I think one of the key things, instead of doing, for example, if on a traditional IT perspective you want to keep data for a long time, you typically employ deduplication technology, right. Dedup technology typically works really well if you own the entire asset and you have sort of big servers, big number of cores, big memories, and so on and so forth. When you actually do a lift and ship of that technology, into the cloud environment, all of a sudden your price tag, in terms of what you charge on a monthly basis goes through the roof, because now every CPU cycle and every IO you generate to do that deduplication, now becomes very expensive, you're essentially charged on a per use basis into the cloud. So what Actifio has done, is really enable our customers to eliminate a lot of the cost in terms in doing that, in doing a lift and ship into the cloud, by enabling you to use leverage object storage directly without having to employ these expensive deduplication technology there as well, so that's one example. >> I want to talk about digital transformation a little bit, it's the buzzword, we go to a lot of conferences and every time you hear, oh digital transformation, Uber, Airbnb, you know blah, blah, blah. We tend to have these detailed storage discussions and product discussions, and it seems like it's really far away, but I want to run something by you and see if you can respond. Digital means data, right, if it's not data it's not digital, you guys are in the data business, we'd observe that the big digital players, the big internet players, their data driven, your conference upcoming, we're going to talk about that, it's called data driven, what does that mean? It means that data is at the heart of your enterprise and humans, human expertise is sort of surrounds that, but it's foundational is the data, most companies in the enterprise, human expertise is at the center and data's in silos and bolted on all over the place. You guys in a big way are a silo buster, you allow me to have sort of a comprehensive view of my virtual data store. Are you seeing that in your customer base, can you help enterprises who are scared to death that they're going to get disrupted, cross that digital divide and close the gap with the disrupters? >> Absolutely, so Actifio does not do AI for example, but what we really do is unlock the data you already have in your environment so it's absolutely free to be, so you can run analytics, you can run analytics on demand whether it's on your primary IT infrastructure, in a private data center, or in a public cloud. So by, if you think about it some of the biggest challenge our customer have in terms of going digital, is how do I fundamentally uncouple or decouple my data from the infrastructure that I'm running, right. Once I have that detachment of that data from my underlying infrastructure, now I'm free to move that information to anywhere I want, in terms of make use of that information, or to run analytics, to actually run a lot of the advanced algorithms that you could monetize that information for your business. So that acceleration or the agility we provide and the reduction of the number of copies for all these use cases, is at the center of what we can do for you for that use case. >> Or even move code, bring code to that data wherever it lives, because I may not want to move petabyte of data around, is that right? >> That's right. >> Okay, so data driven, so you can't be data driven unless you put data at the core of your enterprise, that's part of what you guys do. The conference is June 5th and 6th, it's called Data Driven, it's at the Fontainebleau in Miami. We did a Cube gig there a couple years ago, it was fantastic. Tell us about the event and what people can expect. >> We're very excited about the event, it's a really an industry wide event, we have many customers or many partners within the community coming in and sharing with the entire sort of industry around some of the best practices in terms of monetization of the data you already have, some of the best practices in terms of making the data self-service, some of the best practice in terms of leveraging sort of the best economics in terms of the private or public cloud to make effective use of that information. So we're very excited and like to see everyone there in June. >> Great David thanks so much for coming back in The Cube, really a pleasure, congratulations on all the success and good luck in June. >> Thank you very much, pleasure to be here. >> Thanks for watching everybody, this is Dave Vellante, from our East Coast studios, we'll see you next time.

(innovative music) >> Hi everyone, this is Dave Vallente and welcome to part one of our four part series Conquering Enterprise Cloud co-sponsored by Oracle. You know, Cloud is on everyone's minds these days and for good reason. I'm here with Chuck Hollis of Oracle, good to see you again Chuck. >> Thanks, Dave, you know it's great to be here. You know, I think we both think this is an increasingly important topic for any IT leader these days. I'm looking forward to a deep discussion. >> You know, that's right, Chuck. Our goal here is really to deconstruct Cloud computing and specifically try and address the challenges faced by most IT groups today. We really want to understand how to best utilize Cloud to create business capabilities and really have a frank conversation about Oracle's role in Cloud. So let's dig in. In our initial segment, we're going to start with the big Why. Why is there so much interest in Cloud models and why now? Let me start by sharing some data from a survey of 1,200 respondents that we just finished last month. 33% of the respondents are thinking tactically as Cloud first. 49% are thinking about deploying Cloud selectively and only 8% say Cloud only. Less than 10% say no Cloud. So this data clearly underscores that Cloud is on virtually everyone's mind. We know public Cloud is still small, but it's rapid growth has everybody trying to figure out their own Cloud strategies. >> You know what this tells me is that over 90 percent of your 1,200 respondents are thinking seriously about Cloud in some form these days. If that's not mandate, I don't know what is. >> Well Chuck, how do you think we got here? I mean in the last few years, it looks like we've gone from 90% being skeptical of Cloud, to 90% really taking it quite seriously. Large companies like Microsoft and Oracle have completely reshaped their strategies around Cloud. >> You know, you're right. Maybe we take a step back and figure out why we're having this discussion in the first place. >> I think a good starting point might be how business itself has changed over the last few years and of course when the business changes, IT really has to adapt. Chuck, you talk to a lot of customers and really a lot of IT people. What is driving the shift from your perspective? >> If you really want to talk big picture, I think we've gone from an economy of things to an economy of information. Everything an organization does, or might ever want to do, is entirely grounded in information these days. So it's no surprise to me that IT is starting to matter a lot more than it ever has. Another way of saying the same thing I think IT has become one of the big three ingredients you need for business success. Great people, great financials, now great IT. >> You know, I remember years ago when we felt like the job of IT was to support the business, you know by automating financials or HR or whatever. Now the opposite is true. In many cases, IT has really become the business. >> Right, let me offer a different view. One way to look at any organization is as a collection of business processes. Building stuff, finding customers, making them happy, learning from the experience and doing it better the next time. To do any of these things, at any scale these days, you're going to need serious IT capabilities. >> You know, it's funny, we've both been in this business for a while and it seems like it takes less and less time for the latest buzz word to become main stream reality. I mean look at Cloud, obviously, Mobile, Big Data, IOT, what used to take a decade, or even longer, it's really now happening in a few short years. Now a lot of people feel like it's the consumer of the consumerization of IT that's driven by the likes of Facebook and Google that are really responsible for this shift and of course they're the epitome of Cloud companies my question to you is are traditional enterprises finally tuning in? >> You know, sure, consumerization of IT it's a factor. But what I really think we're seeing is an entire generation of business leaders that want to use information in new ways to thrive and compete. And they're depending on IT to help them do that. You know I find today's business leaders a whole lot more IT savvy than just five or ten years ago. >> Sure, in our survey of 1,200, we asked what the key drivers were to move to Cloud and here's what people said. Number one, scalability. Number two, agility and number three was cost. So I wanted to explore this a little bit with you. People don't typically associate traditional IT and the vendors that serve that space with these attributes, particularly agility and scalability, but even cost as well. Now cost I know can be complicated and somewhat misleading, it's not just the acquisition cost or the published price of the Cloud service, but my question is, why should anyone take seriously the perspectives of someone like yourself, a long time enterprise IT guy working at a company that was founded in the 1970's. >> Ouch. Well I think that's fair enough. Look, I think longevity in this industry isn't necessarily a disadvantage, but failure to adapt sure is. For example, Intel was founded in 1968, Microsoft was founded in 1975, Cisco in 1984 and I don't think you're saying that these guys are somehow irrelevant just because they've been so successful for a long time. As far as me, I spent close to forty years in this industry and I'm still not bored. For some strange reason, I've always been fascinated with Enterprise IT. I've also had the privilege of meeting with thousands of IT leaders over these decades and learning from each and every one of them. And I've also done pretty well at calling the big shifts over the years. So, you can take it or leave it. More to the point. I can't argue with your findings. I would suggest though that there might be a deeper interpretation to some of these. >> What do you mean by that? >> Well, let's take scalability. I think it's more than just getting really big. You know, for some shops, it's also about getting global. Look, if you're going to deliver IT services close to your users, using a public Cloud provider to get global footprint can look pretty attractive. Look how popular contract workers have become in most work places. That makes it really easy for management to dial labor costs up, or down, without too much drama. I think they'd like to be able to do the same thing with their IT costs. Or maybe we consider agility. Most people would think that the ability for IT to move faster is a good thing and yeah, that's true, but there's more to it. We're now getting to the point where there's all sorts of attractive public Cloud services that just aren't practical to attempt to recreate with a traditional IT model. If you think about it, the very best IT stuff these days runs in the Cloud. That's where all the R&D is going. And you know, I agree with you on your point on costs. I think way too often, people focus on the cost of the ingredients instead of the cost of the meal. You'll hear people say it's often cheaper to buy servers instead of rent capacity. But I always wonder, are you forgetting to include things like data center cost, people cost and that sort of thing. >> Sure. >> Public Cloud providers are very good at assembling the ingredients and offering an attractive service. In house IT groups, maybe not so much. And we can't forget opportunity cost either. When those resources are freed up, what higher value activities could they be working on other than just patching infrastructure. You know I don't think this debate will be definitively answered anytime soon. >> For the customers you talk to, let me ask you a question, is Cloud becoming less of an IT thing and more of a business thing and isn't that being driven by the ascendancy of public Cloud? >> I think you're right. Step back bit and think about how virtualization came into the market. I categorize virtualization as more of an IT win than a business win. IT saw most of the benefit, but the business users got pretty much the exact same capabilities they had before and just got them a little faster and a little cheaper. It didn't really change the game for the business users. Now when we think about public Cloud, the business realizes that they can now do things that just aren't practical to attempt to do in house. >> Right. >> So if we think about this, it's quickly becoming a business thing because no business person wants to give up on a competitive advantage. So they've started to get very vocal about IT moving to a Cloud model as quickly as possible. Remember, decades ago, we were all talking about globalization, everybody had to get global. >> Sure. >> I think business leaders realized that they had to either invest in getting global to get in the game or suffer the consequences. And I think the exact same thing is happening with Cloud. >> Well staying on that trend, it's reflected in our forecast when you look at aggregate IT spending. >> Roughly about a trillion dollars are spent on IT infrastructure and related activities. And long term, our forecast show that about a third of that spend is going to go into the public Cloud, a third is going to be On-prem, Cloud like in that organizations will be attempting to operate their own Clouds on premises, and about a third will be Legacy stuff that people are just going to manage in a slowly declining fashion. >> You know that sounds about right to me. I think another way of saying the same thing is that over the long-term, two-thirds of IT spend will shift to some sort of Cloud model. Whether that's a public Cloud, or something cloud-like that lives in the data center. I also think you're seeing that shift reflected in R&D spend for the major IT players. I can't speak for the other vendors, but at Oracle, the vast majority of our R&D spend is now tied to the Cloud in some meaningful way. If you look at our recent acquisitions, they're all in that category. StackEngine, Ravello, NetSuite, Dime, on and on. Here's the point for Enterprise ITlers. It's going to be increasingly difficult to stay current without embracing some sort of Cloud model. It's where most of the industry investment is going these days. >> Okay, let's talk about the looming talent shift you know again, the data shows, in our forecast, that over the next 10 years we'll see about 200 billion dollars coming out of IT staff expense. Shifting to vendor R&D in the form of Cloud, whether that's public Cloud, or On-prem. What does that mean to you? >> You know I think that's a great factoid. And it's not that surprising to me. When you buy a Cloud service, you're not just buying infrastructure, you're also buying the expertise and the automation to run it effectively. If you think about it, that would represent a huge shift in the Enterprise IT labor market. >> Well let's follow that thread, which is the people side of the equation. The joke is you only need two things in IT, you need money and you need people. We've talked about the cost. Talk about how Cloud impacts skill and expertise requirements. How do you see CIO's thinking about this challenge? >> You know, I think you bring up a great point. IT organizations have to compete for talent just like everyone else does. And anytime I'm with a group of CIO's, the talent and staffing discussion always comes up. Because not having the right people on your team is almost worse than not having the budget you need. >> But the real point there is that the best people want to work in a modern environment. >> That's true. >> One where you can keep developing their talents and their skill sets and these days, that means Cloud. My question is, can traditional IT organizations keep up with this change? >> You know, I don't think there's a yes, no answer to that, but I'd say they've got to try really hard. Look, you can already see signs of progress. The application developer community has embraced Cloud models and Tooling in a huge way. I think their far more productive as a result and I don't think they're going back. I'd like to think the infrastructure and operations folks are starting to see the same light. Now, just to be clear, I don't think the IT infrastructure guys are being stubborn about Cloud. It's just that getting there is a lot harder than it looks. So we, as vendors, have to work to come up with strategies and approaches that works the way they do. That being said, I've got IT leaders telling me that it's a lot easier to find key talent when you can offer them a modern environment to work in. And these days, that means Cloud. Look, it's not unusual to go through an IT org chart these days and find a beginning Cloud team working alongside the traditional IT function. I see clear evidence that IT leaders know that they need to start investing in a new way of doing things. >> Okay so Chuck, I think it's time to wrap up this segment with a quick summary. Why don't you start us off? >> I guess the first key point I'd offer is that Cloud has moved from theoretical to inevitable. >> Yeah and so let's remember the findings that I shared earlier. A third of the respondents are thinking tactically as Cloud first. 49% are thinking about Cloud selectively. Only 8% say Cloud only and less than 10% say no Cloud at all. >> Yeah, congratulations, that means 90% of you are out there thinking hard about Cloud going forward. If we look at why that is, I think we can point to the macro trends, for example, every business is trying to compete in the digital economy, and no one wants to be left behind. >> And you know, the data supports that as well based on our survey. The top three motivators were scalability, agility and of course cost is always a factor. >> And the only thing I'd add to that list is that I see Cloud becoming a business strategy issue and not just an IT only discussion. I think the next big point is that Cloud has already started to transform the vendor side of the equation. What were those forecasts? >> Well long-term, we see about a third of IT spend moving to a public Cloud model, a third moving to a Cloud model that's On-prem and about a third being spent to maintain Legacy environments. >> And I think the implication is pretty clear. IT vendors are going to invest where the money is going. And that's Cloud. And I think we need to reiterate the point about how Cloud is transforming the people's side of the equation. >> Dave: Well, that's big, our forecast is that about 200 billion dollars of labor cost is going to come out of the data center and go directly into the Cloud model. >> And if you're going to want to attract the best people, which we all do, you're going to have to give them a modern environment to work in. And that's quickly becoming Cloud. So why don't we take a moment and give people a preview of what we'll be talking about next. >> Well, sure, in this segment we wanted to look at the forces behind Cloud and more importantly, why Enterprise IT can't escape its gravitational pull. In our next segment, we're going to look at why familiar approaches to the Cloud might not always work for all Enterprise organizations and what can be done about it. >> Thanks everyone. See ya next time. (innovative music)

>>Welcome back here on the Cube. I'm John Walls. We are in Las Vegas at the Venetian, and this is Reinvent 22 in the Executive Summit sponsored by Accenture. Glad to have you with us here as we continue our conversations. I'm joined by Paul Puckett, who's the former director of the Enterprise Cloud Management Services at the US Army. Paul, good to see you sir. Hey, you as well, John. Thank you. And Justin, she who is managing director and cloud go to market lead at Accenture Federal Services. Justin, good morning to you. Good morning, John. Yeah, glad to have you both here on the cube. First time too, I believe, right? Yes sir. Well, welcome. I wish we had some kind of baptism or indoctrination, but I'll see what I can come up with in the next 10 minutes for you. Let's talk about the Army, Paul. So enterprise cloud management, US Army. You know, I can't imagine the scale we're talking about here. I can't imagine the solutions we're talking about. I can't imagine the users we're talking about. Just for our folks at home, paint the picture a little bit of what kind of landscape it is that you have to cover with that kind of title. >>Sure. The United States Army, about 1.4 million people. Obviously a global organization responsible for protecting and defending the United States as part of our sister services in the Department of Defense. And scale often comes up a lot, right? And we talk about any capability to your solution for the United States Army scale is the, the number one thing, but oftentimes people overlook quality first. And actually when you think of the partnership between the Army and Accenture Federal, we thought a lot when it came to establishing the enterprise Cloud management agency that we wanted to deliver quality first when it came to adopting cloud computing and then scale that quality and not so much be afraid of the, the scale of the army and the size that forces us to make bad decisions. Cuz we wanted to make sure that we proved that there was opportunity and value in the cloud first, and then we wanted to truly scale that. And so no doubt, an immense challenge. The organization's been around for now three years, but I think that we've established irreversible momentum when it comes to modernization, leveraging cloud computing >>For the army. So let's back up. You kind of threw it in there, the ecma. So this agency was, was your a collaboration, right? To create from the ground up and it's in three years in existence. So let's just talk about that. What went into that thinking? What went into the planning and then how did you actually get it up and run into the extent that it is today? >>Sure. Well, it was once the enterprise cloud management office. It was a directorate within the, the CIO G six of the United States Army. So at the headquarters, the army, the chief information Officer, and the G six, which is essentially the military arm for all IT capability were once a joint's organization and the ECMO was created to catalyze the adoption of cloud computing. The army had actually been on a, a cloud adoption journey for many years, but there wasn't a lot of value that was actually derived. And so they created the ecma, well, the ECMO at the time brought me in as the director. And so we were responsible for establishing the new strategy for the adoption of cloud. One of the components of that strategy was essentially we needed an opportunity to be able to buy cloud services at scale. And this was part of our buy secure and build model that we had in place. And so part of the buy piece, we put an acquisition strategy together around how we wanted to buy cloud at scale. We called it the cloud account management optimization. OTA >>Just rolls right off the >>Tongue, it just rolls right off the tongue. And for those that love acronyms, camo, >>Which I liked it when I was say cama, I loved that. That was, that was, >>You always have to have like a tundra, a little >>Piece of that. Very good. It was good. >>But at the time it was novetta, no, Nevada's been bought up by afs, but Novea won that agreement. And so we've had this partnership in place now for just about a year and a half for buying cloud computing net scale. >>So let's talk about, about what you deal with on, on the federal services side here, Justin, in terms of the army. So obviously governance, a major issue, compliance, a major issue, security, you know, paramount importance and all that STEM leads up to quality that Paul was talking about. So when you were looking at this and keeping all those factors in, in your mind, right? I mean, how many, like, oh my God, what kind of days did you have? Oh, well, because this was a handful. >>Well, it was, but you could see when we were responding to the acquisition that it was really, you know, forward thinking and forward leaning in terms of how they thought about cloud acquisition and cloud governance and cloud management. And it's really kind of a sleepy area like cloud account acquisition. Everyone's like, oh, it's easy to get in the cloud, you know, run your credit card on Amazon and you're in, in 30 seconds or less. That's really not the case inside the federal government, whether it's the army, the Air Force or whoever, right? Those, those are, they're real challenges in procuring and acquiring cloud. And so it was clear from, you know, Paul's office that they understood those challenges and we were excited to really meet them with them. >>And, and how, I guess from an institutional perspective, before this was right, I I assume very protective, very tight cloistered, right? You, you, in terms of being open to or, or a more open environment, there might have been some pushback was they're not. Right? So dealing with that, what did you find that to be the case? Well, so >>There's kind of a few pieces to unpacking that. There's a lot of fear in trepidation around something you don't understand, right? And so part of it is the teaching and training and the, and the capability and the opportunity in the cloud and the ability to be exceptionally secure when it comes to no doubt, the sensitivity of the information of the Department of Defense, but also from an action acquisition strategy perspective, more from a financial perspective, the DOD is accustomed to buying hardware. We make these big bets of these big things to, to live in today's centers. And so when we talk about consuming cloud as a utility, there's a lot of fear there as well, because they don't really understand how to kind of pay for something by the drink, if you will, because it incentivizes them to be more efficient with their utilization of resources. >>But when you look at the budgeting process of the d od, there really is not that much of incentive for efficiency. The p PPE process, the planning program, budgeting, execution, they care about execution, which is spending money and you can spend a lot of money in the cloud, right? But how are you actually utilizing that? And so what we wanted to do is create that feedback loop and so the utilization is actually fed into our financial systems that help us then estimate into the future. And that's the capability that we partnered with AFS on is establishing the closing of that feedback loop. So now we can actually optimize our utilization of the cloud. And that's actually driving better incentives in the PPE >>Process. You know, when you think about these keywords here, modernized, digitized, data driven, so on, so forth, I, I don't think a lot of people might connect that to the US government in general just because of, you know, it's a large intentionally slow moving bureaucratic machine, right? Is that fair to characterize it that way? It >>Is, but not in this case. Right? So what we done, >>You you totally juxtapose that. Yeah. >>Yeah. So what we've done is we've really enabled data driven decision making as it relates to cloud accounts and cloud governance. And so we have a, a tool called Cloud Tracker. We deployed for the army at a number of different classifications, and you get a full 360 view of all of your cloud utilization and cloud spend, you know, really up to date within 24 hours of it occurring, right? And there a lot of folks, you know, they didn't never went into the console, they never looked at what they were spending in cloud previously. And so now you just go to a simple web portal and see the entire entirety of the army cloud spend right there at your fingertips. So that really enables like better decision making in terms of like purchasing savings plans and reserved instances and other sorts of AWS specific tools to help you save money. >>So Paul, tell me about Cloud Tracker then. Yeah, I mean from the client side then, can you just say this dashboard lays it out for you right? In great detail about what kind of usage, what kind of efficiencies I assume Yeah. What's working, what's not? >>Absolutely. Well, and, and I think a few things to unpack that's really important here is listen, any cloud service provider has a concept. You can see what you're actually spending. But when it comes to money in the United States government, there are different colors of money. There's regulations when it comes to how money is identified for different capabilities or incentives. And you've gotta be very explicit in how you track and how you spend that money from an auditability perspective. Beyond that, there is a move when it comes to the technology business management, which is the actual labeling of what we actually spend money on for different services or labor or software. And what Cloud Tracker allows us to do is speak the language of the different colors of money. It allows us to also get very fine grain in the actual analysis of, from a TBM perspective, what we're spending on. >>But then also it has real time hooks into our financial systems for execution. And so what that really does for us is it allows us to complete the picture, not just be able to see our spend in the cloud, but also be able to able to see that spending context of all things in the P P P E process as well as the execution process that then really empowers the government to make better investments. And all we're seeing is either cost avoidance or cost savings simply because we're able to close that loop, like I said. Yep. And then we're able to redirect those funds, retag them, remove them through our actual financial office within the headquarters of the army, and be able to repurpose that to other modernization efforts that Congress is essentially asking us to invest >>In. Right. So you know how much money you have, basically. Exactly. Right. You know how much you've already spent, you know how you're spending it, and now you how much you have left, >>You can provide a reliable forecast for your spend. >>Right. You know, hey, we're, we're halfway through this quarter, we're halfway through the, the fiscal year, whatever the case might be. >>Exactly. And the focus on expenditures, you know, the government rates you on, you know, how much have you spent, right? So you have a clear total transparency into what you're going to spend through the rest of the fiscal. Sure. >>All right. Let's just talk about the relationship quickly then about going forward then in terms of federal services and then what on, on the, the US Army side. I mean, what now you've laid this great groundwork, right? You have a really solid foundation where now what next? >>We wanna be all things cloud to the army. I mean, we think there's tremendous opportunity to really aid the modernization efforts and governance across the holistic part of the army. So, you know, we just, we want to, we wanna do it all with the Army as much as we can. It's, it's, it's a fantastic >>Opportunity. Yeah. AFS is, is in a very kind of a strategic role. So as part of the ecma, we own the greater strategy and execution for adoption of cloud on behalf of the entire army. Now, when it comes to delivery of individual capabilities for mission here and there, that's all specific to system owners and different organizations. AFS plays a different role in this instance where they're able to more facilitate the greater strategy on the financial side of the house. And what we've done is we've proven the ability to adopt cloud as a utility rather than this fixed thing, kind of predict the future, spend a whole bunch of money and never use the resource. We're seeing the efficiency for the actual utilization of cloud as a utility. This actually came out as one of the previous NDAs. And so how we actually address nda, I believe it was 2018 in the adoption of cloud as a utility, really is now cornerstone of modernization across all of the do d and really feeds into the Jo Warfighting cloud capability, major acquisition on behalf of all of the D O D to establish buying cloud as just a common service for everyone. >>And so we've been fortunate to inform that team of some of our lessons learned, but when it comes to the partnership, we just see camo moving into production. We've been live for now a year and a half. And so there's another two and a half years of runway there. And then AFS also plays a strategic role at part of our cloud enablement division, which is essentially back to that teaching part, helping the Army understand the opportunity of cloud computing, align the architectures to actually leverage those resources and then deliver capabilities that save soldier's >>Lives. Well, you know, we've, we've always known that the Army does its best work on the ground, and you've done all this groundwork for the military, so I'm not surprised, right? It's, it's a winning formula. Thanks to both of you for being with us here in the executive summit. Great conversation. Awesome. Thanks for having us. A good deal. All right. Thank you. All right. You are watching the executive summit sponsored by Accenture here at Reinvent 22, and you're catching it all on the cube, the leader in high tech coverage.

(gentle music) >> Hello, welcome to theCUBE's presentation of the AWS Showcase season one, episode two with the ISV Startups partners. I'm John Furrier, your host of theCUBE. We're joined by Morgan McLean, director of product management at Splunk, and Danielle Greshock, who is the director of ISVs solution architects at AWS. Welcome to the show. Thanks for coming on. >> Thanks for having us. >> And great. Thanks for having us. >> Great to see both of you, both theCUBE alumni, but the Splunk-AWS relationship has been going very, very well. You guys are doing great business enabling this app revolution. And cloud scale has been going extremely well. So let's get into it. You guys are involved in a lot of action around application revolution, around OpenTelemetry and open source. So let's get into it. What's the latest? >> Danielle, you go ahead. >> Well, I'll just jump in first. Obviously last year, not last year, but in 2020, we launched the AWS Distro for OpenTelemetry. The idea being essentially, we're able to bring in data from partners, from infrastructure running on AWS, from apps running on AWS, to really be able to increase observability across all cloud assets at your entire cloud platform. So, Morgan, if you want to chime in on how Splunk >> Morgan: Certainly. >> has worked out OpenTelemetry. >> Yeah. I mean, OpenTelemetry is super exciting. Obviously, there's a lot of partnership points between Amazon and Splunk, but OpenTelemetry is probably one of them that's the most visible to people who aren't already maybe using these two products together. And so, as Danielle mentioned, Amazon has their own distribution of OpenTelemetry, Splunk has their own, as well, and of course there's the main open source distribution that everybody knows and loves. Just for our viewers, just for clarity's sake, the separate distributions are fundamentally very similar to, almost identical to what's offered in the open source space, but they come preconfigured and they come with support guarantees from each company, meaning that you can actually get paid full support for an open source project, which is really fantastic for customers. And as Danielle mentioned, it's a great demonstration of the alliance between Splunk and Amazon Web Services. For example, the AWS Distro, when you use it, can export data to Amazon CloudWatch, various Amazon backed open source initiatives like Prometheus and others, and to Splunk Observability Cloud and to Splunk Enterprise. So it's a place that we've worked very closely together, and it's something that we're very excited about. >> So, Morgan, I want to get your take on the on the product management side and also how product are built these days. >> One of the big things we're seeing in cloud is that open source has been the big enabler for a lot of refactoring. And you got multiple distributions, but the innovations on top of that, can you talk about how you see the productization of new innovations with open source as you guys go into this market, because this is the new dynamic with cloud. We're seeing examples all over the place. Obviously, Amazon's going next level with what they're doing, and that open source, it's not a one game for all of it. You can have mix and match. Take us through the product angle. >> And in many ways, this is just another wave of the same thing, right? Like, if you think back in time, we all used and still use in many cases, virtual machines, most of those are based on Linux, right? Another large open source project. And so, open source software has been accelerating innovation in the cloud space and in the computing space generally for a very long time, which is fantastic. Our excitement with something like OpenTelemetry comes from both the project's capabilities but also what we can do with it. So for those who aren't already familiar with OpenTelemetry, OpenTelemetry allows you to extract really critical system telemetry, application signals and everything else you need from your own applications, from new services, from your infrastructure, from everything that you're running in a cloud environment. You can then send that data to another location for processing. And so John, you ask like, how does this accelerate innovation? What does it unlock? Well, the insight you can gain from this data means you can become so much more efficient as a development organization. You can make your applications so much more effective because when you send that data to something like Splunk Observability Cloud, to something like Amazon CloudWatch, to various other solutions on the market, they can give you deep, deep insight into your application's performance, to its structure, they can help you reduce outages. And so, it's very, very powerful because it allows organizations to use tools like Splunk, like Amazon, like other things to innovate so much more effectively. >> Danielle, can you comment >> If I could... >> on the AWS side because this is again on the big point. You guys are going next level, and you're starting to see patterns in the ISV world, certainly on the architecture side of partners doing things differently now on top of what they've already done. Could you share how AWS is helping customers accelerate? >> Well, just as Morgan was talking about what OpenTelemetry provides, you can see how from a partnership perspective, this is so valuable, right? What the partner team here at AWS is in the business of doing, is really enabling customer choice, right? And having that ability to plug in and pull data from different sources, post it to different sources, make it available for visibility across all of your resources is very powerful and it's something from the partner community that we really value because we want customers to be able to select best of breed solutions, what works for their business, which businesses are different and they may have different needs, and that also fosters that true innovation. A small company is going to develop and release software a lot differently than a large enterprise. And so, being able to support something like OpenTelemetry just enables that for all different kinds of customers. >> Morgan, add to that because the velocity of releases, certainly operational, stability, is key every predominant security, uptime, these are top concerns. And, you mention data too, >> And you mention challenges. >> You got the data in here. So you got a lot of data moving around, a lot of value. What's your take? >> Yeah. So, I'll speak with some specifics. So a challenge that developers have had for years when you're developing large services, which you can now do with platforms like AWS. So, it's very easy to go develop huge deployments. But a challenge they have is you go and build a mess, right? And like, I've worked earlier in my career in Web Services. And I remember in one of the first orgs I was in, I was one of the five people who really understood our ecommerce stack. Right? And so like, I would get dragged into all these meetings and I'd have to go draw like the 50 services we had, and how they interacted, and the changes that were made in the last week. And without observability tools like Splunk Observability Cloud, like the ones offered by Amazon, like the ones that are backed by the data that comes with OpenTelemetry, organizations basically rely on people like this, to go draw out their deployments so they understand what it is they've built. Well, as you can imagine, this crimps your development velocity, because most of your engineers, most of your tech leads, most of everyone else don't actually understand what it is they've built what it is they're running, because they need that global context. You get something like OpenTelemetry and the solutions that consume the data from it, and suddenly now, all your developers have that context, all of them when they're adding functionality to a service or they're updating their infrastructure, can actually understand how it interacts with the rest of the broader application. This lets you speed up your time to development, this lets you ship more safely, more securely. And finally, when things do go wrong, which will be less frequent, but when they do go wrong, you can fix them super rapidly. >> If I'm a customer, let me ask a question. I'm a customer and I say, "Okay, I love AWS, I love Splunk, I love OpenTelemetry. I got to have open sources, technology innovation is happening." What's the integration? What are some of the standards? Can you take us through how that's working together with you guys as a shared platform? >> Yeah. So let's take the Amazon distribution for OpenTelemetry or even the Splunk one. One of the first things they do is they include all of the receivers, all of the sort of data capture components that you need, out of box for platforms like AWS, right? And so, right away, you get that power and flexibility where you're getting access to all of these data sources, right? And so, that's part of that partnership. And additionally, once the data comes into OpenTelemetry, you can now send that to various different data sources, including, as Danielle mentioned, to multiple at the same time. So you can use whatever tools you want. And so when you talk about like what the partnership is actually providing to you as a customer and still, this is just within the context of OpenTelemetry, obviously there's a much broader partnership between these two companies than just that. But within the context of OpenTelemetry means you can download one of these distributions. It's fully supported. It works with both solutions and everything is just great, right? You don't need to go fiddle with that out of the box. To be clear, OpenTelemetry is a batteries included project, right? This means that even the standard distributions of OpenTelemetry include the components you need. You have to go directly, reference them and ensure that they're packaged in there, but they exist, right. But the nice thing about these distributions is that it's done, it's out of the box, you don't even have to worry about is something missing or do I need to include new exporters or new receivers? It's all there. It's preconfigured. It just works. And if something goes wrong and you have a support contact, you pick up the phone, you talk to someone to get it fixed. >> Danielle, what's the Amazon side 'cause agility and scale is one of the highlights you guys are seeing. How does this tie into that and how are you guys working backwards from the customers to support the partners? >> Well, I think just to add on essentially to what Morgan said, I think that AWS is a cloud platform, has always really had a focus on developers. And, we talk a lot about how AWS and Amazon as a whole really embraces this continuous integration and continuous deployment methods inside of our organization. And we talk about services, and observability is a huge part of that. The only way that you're actually able to release hundreds, thousands of times a day like Amazon does, is by having an observability platform, to be able to measure metrics, see changes in the environment, to be able to roll back if you need to, and to be able to quickly mitigate any challenges or anything that goes wrong at any part of the process. And so, when we preach that to our customers, I think it's something that we do that because we live it and breathe it. And so, things such as OpenTelemetry and such as the products that Splunk builds, those are also ways in which we believe our customers can achieve that. >> Yeah. And we can... I mean, as I mentioned before, this partnership goes well beyond OpenTelemetry, right? And so, if you go use like Splunk Enterprise, Enterprise Cloud, Splunk Observability Cloud, and you're running on AWS, you have excellent support and excellent visibility into your Amazon infrastructure, into the services and applications you've deployed on top of that infrastructure. We try and give you, and I think we do succeed in this. We give you the best possible experience, the deepest possible visibility, into what it is you've deployed on AWS, so that you can be even more successful as a business, and so that you can be even more successful on AWS as a platform. >> Yeah. This is a great conversation, Morgan. You mentioned the early days of Web Services. AWS stands for Amazon Web Services built on web services. So interesting throwback there, but made me think about the days of the early days of web services. And if you look at data, what's going on now, the top partners in AWS, you're seeing a lot of people thinking about data differently, they're refactoring, a lot of machine learning, a lot of AI going on at scale. So then, you got cloud native, things like Kubernetes and these new services being stood up and teared down with automation. A whole new operating model's coming. And so when you think about observability, the importance of it, I mean, can you share your perspective on this whole 'nother level? I mean, I always say that whole another level sounds cliche, but it is next level. I mean, this is completely different. What's your reaction? >> Yeah. There there's a ton of factors here, right? So as you point out, companies are totally shifting how they use their cloud infrastructure. And part of this you see during their cloud migrations, a part of it you see after, and they're shifting from their sort of stateful VMs that they may have had in the past to infrastructure that they tear down and put up regularly. And there's a lot more automation. With this, comes as I mentioned before, complexity, right? And also, with this comes more and more businesses becoming even more reliant on their digital infrastructure. And so, not having observability into your applications, into your services, into your infrastructure, to me, is akin to running a business, say running a large warehousing or distribution company, but not having any idea where you're shipping products or where things are, or not having any accounting or CFO, right? Like, business has become so digital. Business is so reliant on technology, and that's unlocked a ton of new things. It's great. But not having visibility into how that technology works or what it is that's deployed or how to fix it is akin to having no visibility to anything else in your business. It's nuts. And so, observability is super, super critical, particularly for customers who are adopting this new wave of cloud technologies on platforms like AWS. >> Danielle, on your side too, you're enabling this new capability so that businesses can do it, the partners do it, we're calling it super cloud. We've been calling it super cloud kind of dynamic where new things are happening with the data. And you guys are evolving with that. Can you share what you're seeing on your side as your partners start to go to the next level? What are you guys doing? How does it all come together? >> Well, we always talk about what has happened with data in the last couple of years, which the cloud has really enabled around, you know, variety and velocity and there's one other "V" that's escaping me right now, but essentially, all of this data is coming in and providing the ability for us to make better decisions, to build better products, to provide better experiences for customers. And so, I just think, the OpenTelemetry project, as well as what Splunk is doing is just another example of how we're taking this massive amount of data and being able to provide better experiences and outcomes for customers. >> And you guys have been working along together for long time, Splunk, and, it's been a great partners, if we're going back with that been covering it on theCUBE and SiliconANGLE. So, we know that, the change is key observability. Can you imagine a company without a CFO, Morgan? That's just boggles your mind, but that's what it's like right now. So... >> It is, yeah. >> And the people who take advantage of that are winning, right? So it's like, that's the key. >> Yeah, I know. I mean, even in my own career, right, I've moved between different companies. And I remember, when I joined Google in particular, which is where I worked at previously, I was very impressed with their internal observability tools. And I'm certain, I haven't worked at Amazon. I'm certainly, I just assume inside of Amazon they're excellent as well, so a lot of the large cloud firms these days. But it was so refreshing going from an organization where if we had some outage or something went wrong, there were like a very small set of people who could actually understand what was going on. And then you would just have to manually dive through logs and correlate requests manually between services. It's very challenging. And so, when things went wrong, they went wrong for a long, long time. And so, the companies that understood this even in the past are already very successful as a result. I think now, the rest of the industry is really in the midst of adopting these observability practices and the tools that are required to implement them, because you're right. Otherwise your development velocity slows down. Now you're getting out competed by your competition. And then, when you have a problem, it blows up for ages. And once again, your competition can take advantage of it. >> And, can you just summarize the observability piece relative to the OpenTelemetry? Where is that going to go? Where do you see that evolving? >> Sure. >> I see open source is growing like crazy, we all know that. >> Of course. >> But OpenTelemetry in particular and open source, 'cause this is a big hot area. >> Yes. So to set the stage for people, OpenTelemetry, unlocks observability in many ways. As I mentioned earlier, OpenTelemetry is how you capture data out of your application. It doesn't process it. It's not a replacement for something like Amazon CloudWatch or any Splunk's products, but it's how we get the data out of your system, which is a remarkably difficult problem. I won't dive into it today, but, those who work in this space are very aware. That's why this project exists and it's so big, that actually extracting information, metrics, logs, distributed traces, profiles, everything else, from your applications and from your infrastructure is very, very difficult. So for OpenTelemetry, where it's going is just continually getting better at extracting more types of data from more sources, and doing that more effectively for people in a more standardized way. That will unlock firms like Splunk, firms, like Amazon and others to better process this data. In terms of where that's going, the sky's the limit, right? Like, everyone's familiar with APM, people are familiar with infrastructure monitoring, but there's a lot more capabilities coming there for security analytics, for network performance monitoring, for getting down all the way to single lines of coding your application, how they impact everything. There's just so much power that's coming to the industry right now. I'm really excited to see where things go in the next few years. >> And Danielle, you're in the middle of all the action as a solution architect, really set the stage for their companies and the ISVs, and this is a big, hot area. What are the patterns you're seeing and what are some of the best practices that you're doing will help companies? >> Right. So I think, summarizing our entire conversation, the big things that we're seeing in the market is essentially more and more companies are looking to move to a continuous deployment and a continuous integration environment. And they're looking to innovate faster and spend less time hot patching or hot fixing their environments and they want to spend more time innovating. And so, that you know, the patterns that we're seeing is... What I see and what I actually experience firsthand at re:Invent when I talk to probably over 40 or 50 ISVs, is customers want to know in their environment, where are their changes? Where are their security vulnerabilities? Where are their data changes, and what are customers really experiencing, whether it's latency, poor experience throughout their products, those types of things? So security, data, and observability are just key to all of that experience and that's what we're definitely seeing as patterns, what we're seeing with our customers and also what value our ISVs are providing in that space. >> That's awesome. And the other thing I would observe is that there's more of an integration story going on around joint projects, whether it's open source. >> Absolutely. >> Because this is where we want to get that services connected. And it's mutual beneficial. I mean, this is really >> Exactly. >> whole 'nother, new kind of interoperable cloud scale. >> Yeah, if I could say one thing else there, I think that, a lot of the customers who are trying to move into the cloud now are, maybe not technology forward companies and they really need that solution. And that's very important. I think COVID has pushed a lot of companies into the cloud maybe very quickly. And, that has been something else we've observed in the market. So, solutions and full solutions between ISVs and ISVs, or ISVs and AWS is just becoming more and more common thing that we see. >> And, you mentioned John, in the open source space as well. Like, we're certainly from Amazon to Splunk. So we're talking a lot about those, but there's a lot of other firms involved in projects like OpenTelemetry. And I think it's very endearing, very heartening to see how well they cooperate in this community and how, when their interests are aligned, how effective they can be. And it's been very exciting to work in the space and very pleasant, honestly, to see everything come together with this huge set of customers and partners. >> Yeah. The pleasant surprise of the pandemic has been that people come into the cloud and they like it and they, "Hey, this works," and they double down on it. Then they realize, there's more there and they refactor. So, you're seeing real examples of that. So, this is a great discussion, great success story. Congratulations Morgan, Danielle. >> Thank you. >> Great partnership between Splunk and AWS. We've been following for a long time. And again, this highlights this whole another level of integrating super cloud kind of experience where people are getting more capabilities and doing more together, so great stuff. >> And this is just one facet of that, right? Like, there's all the other connections of Splunk Enterprise, Splunk security analytics products, and others. It's a deep, deep partnership between these firms. >> Yeah. And the companies that innovate and get that new capability are going to have an advantage. And you're seeing... >> Yes. >> Right? >> Agreed. >> And this is awesome, and great stuff, thank you for coming on and sharing that insight. >> Thank you. >> Congratulations Morgan over there at Splunk, great stuff. And Danielle, thanks for coming on and sharing the AWS perspective. >> Thanks for having me. >> And you guys are going to the next level. You moving up to stack as they say, all good stuff for customers. Thanks. >> Thank you. >> Okay. >> Thank you. >> This is season one, episode two of the AWS Partner Showcase. I'm John Furrier with theCUBE. Thanks for watching. (gentle music)

(gentle music) >> Hello, welcome to theCUBE's presentation of the AWS Showcase season one, episode two with the ISV Startups partners. I'm John Furrier, your host of theCUBE. We're joined by Morgan McLean, director of product management at Splunk, and Danielle Greshock, who is the director of ISVs solution architects at AWS. Welcome to the show. Thanks for coming on. >> Thanks for having us. >> And great. Thanks for having us. >> Great to see both of you, both theCUBE alumni, but the Splunk-AWS relationship has been going very, very well. You guys are doing great business enabling this app revolution. And cloud scale has been going extremely well. So let's get into it. You guys are involved in a lot of action around application revolution, around OpenTelemetry and open source. So let's get into it. What's the latest? >> Danielle, you go ahead. >> Well, I'll just jump in first. Obviously last year, not last year, but in 2020, we launched the AWS Distro for OpenTelemetry. The idea being essentially, we're able to bring in data from partners, from infrastructure running on AWS, from apps running on AWS, to really be able to increase observability across all cloud assets at your entire cloud platform. So, Morgan, if you want to chime in on how Splunk >> Morgan: Certainly. >> has worked out OpenTelemetry. >> Yeah. I mean, OpenTelemetry is super exciting. Obviously, there's a lot of partnership points between Amazon and Splunk, but OpenTelemetry is probably one of them that's the most visible to people who aren't already maybe using these two products together. And so, as Danielle mentioned, Amazon has their own distribution of OpenTelemetry, Splunk has their own, as well, and of course there's the main open source distribution that everybody knows and loves. Just for our viewers, just for clarity's sake, the separate distributions are fundamentally very similar to, almost identical to what's offered in the open source space, but they come preconfigured and they come with support guarantees from each company, meaning that you can actually get paid full support for an open source project, which is really fantastic for customers. And as Danielle mentioned, it's a great demonstration of the alliance between Splunk and Amazon Web Services. For example, the AWS Distro, when you use it, can export data to Amazon CloudWatch, various Amazon backed open source initiatives like Prometheus and others, and to Splunk Observability Cloud and to Splunk Enterprise. So it's a place that we've worked very closely together, and it's something that we're very excited about. >> So, Morgan, I want to get your take on the on the product management side and also how product are built these days. >> One of the big things we're seeing in cloud is that open source has been the big enabler for a lot of refactoring. And you got multiple distributions, but the innovations on top of that, can you talk about how you see the productization of new innovations with open source as you guys go into this market, because this is the new dynamic with cloud. We're seeing examples all over the place. Obviously, Amazon's going next level with what they're doing, and that open source, it's not a one game for all of it. You can have mix and match. Take us through the product angle. >> And in many ways, this is just another wave of the same thing, right? Like, if you think back in time, we all used and still use in many cases, virtual machines, most of those are based on Linux, right? Another large open source project. And so, open source software has been accelerating innovation in the cloud space and in the computing space generally for a very long time, which is fantastic. Our excitement with something like OpenTelemetry comes from both the project's capabilities but also what we can do with it. So for those who aren't already familiar with OpenTelemetry, OpenTelemetry allows you to extract really critical system telemetry, application signals and everything else you need from your own applications, from new services, from your infrastructure, from everything that you're running in a cloud environment. You can then send that data to another location for processing. And so John, you ask like, how does this accelerate innovation? What does it unlock? Well, the insight you can gain from this data means you can become so much more efficient as a development organization. You can make your applications so much more effective because when you send that data to something like Splunk Observability Cloud, to something like Amazon CloudWatch, to various other solutions on the market, they can give you deep, deep insight into your application's performance, to its structure, they can help you reduce outages. And so, it's very, very powerful because it allows organizations to use tools like Splunk, like Amazon, like other things to innovate so much more effectively. >> Danielle, can you comment >> If I could... >> on the AWS side because this is again on the big point. You guys are going next level, and you're starting to see patterns in the ISV world, certainly on the architecture side of partners doing things differently now on top of what they've already done. Could you share how AWS is helping customers accelerate? >> Well, just as Morgan was talking about what OpenTelemetry provides, you can see how from a partnership perspective, this is so valuable, right? What the partner team here at AWS is in the business of doing, is really enabling customer choice, right? And having that ability to plug in and pull data from different sources, post it to different sources, make it available for visibility across all of your resources is very powerful and it's something from the partner community that we really value because we want customers to be able to select best of breed solutions, what works for their business, which businesses are different and they may have different needs, and that also fosters that true innovation. A small company is going to develop and release software a lot differently than a large enterprise. And so, being able to support something like OpenTelemetry just enables that for all different kinds of customers. >> Morgan, add to that because the velocity of releases, certainly operational, stability, is key every predominant security, uptime, these are top concerns. And, you mention data too, >> And you mention challenges. >> You got the data in here. So you got a lot of data moving around, a lot of value. What's your take? >> Yeah. So, I'll speak with some specifics. So a challenge that developers have had for years when you're developing large services, which you can now do with platforms like AWS. So, it's very easy to go develop huge deployments. But a challenge they have is you go and build a mess, right? And like, I've worked earlier in my career in Web Services. And I remember in one of the first orgs I was in, I was one of the five people who really understood our ecommerce stack. Right? And so like, I would get dragged into all these meetings and I'd have to go draw like the 50 services we had, and how they interacted, and the changes that were made in the last week. And without observability tools like Splunk Observability Cloud, like the ones offered by Amazon, like the ones that are backed by the data that comes with OpenTelemetry, organizations basically rely on people like this, to go draw out their deployments so they understand what it is they've built. Well, as you can imagine, this crimps your development velocity, because most of your engineers, most of your tech leads, most of everyone else don't actually understand what it is they've built what it is they're running, because they need that global context. You get something like OpenTelemetry and the solutions that consume the data from it, and suddenly now, all your developers have that context, all of them when they're adding functionality to a service or they're updating their infrastructure, can actually understand how it interacts with the rest of the broader application. This lets you speed up your time to development, this lets you ship more safely, more securely. And finally, when things do go wrong, which will be less frequent, but when they do go wrong, you can fix them super rapidly. >> If I'm a customer, let me ask a question. I'm a customer and I say, "Okay, I love AWS, I love Splunk, I love OpenTelemetry. I got to have open sources, technology innovation is happening." What's the integration? What are some of the standards? Can you take us through how that's working together with you guys as a shared platform? >> Yeah. So let's take the Amazon distribution for OpenTelemetry or even the Splunk one. One of the first things they do is they include all of the receivers, all of the sort of data capture components that you need, out of box for platforms like AWS, right? And so, right away, you get that power and flexibility where you're getting access to all of these data sources, right? And so, that's part of that partnership. And additionally, once the data comes into OpenTelemetry, you can now send that to various different data sources, including, as Danielle mentioned, to multiple at the same time. So you can use whatever tools you want. And so when you talk about like what the partnership is actually providing to you as a customer and still, this is just within the context of OpenTelemetry, obviously there's a much broader partnership between these two companies than just that. But within the context of OpenTelemetry means you can download one of these distributions. It's fully supported. It works with both solutions and everything is just great, right? You don't need to go fiddle with that out of the box. To be clear, OpenTelemetry is a batteries included project, right? This means that even the standard distributions of OpenTelemetry include the components you need. You have to go directly, reference them and ensure that they're packaged in there, but they exist, right. But the nice thing about these distributions is that it's done, it's out of the box, you don't even have to worry about is something missing or do I need to include new exporters or new receivers? It's all there. It's preconfigured. It just works. And if something goes wrong and you have a support contact, you pick up the phone, you talk to someone to get it fixed. >> Danielle, what's the Amazon side 'cause agility and scale is one of the highlights you guys are seeing. How does this tie into that and how are you guys working backwards from the customers to support the partners? >> Well, I think just to add on essentially to what Morgan said, I think that AWS is a cloud platform, has always really had a focus on developers. And, we talk a lot about how AWS and Amazon as a whole really embraces this continuous integration and continuous deployment methods inside of our organization. And we talk about services, and observability is a huge part of that. The only way that you're actually able to release hundreds, thousands of times a day like Amazon does, is by having an observability platform, to be able to measure metrics, see changes in the environment, to be able to roll back if you need to, and to be able to quickly mitigate any challenges or anything that goes wrong at any part of the process. And so, when we preach that to our customers, I think it's something that we do that because we live it and breathe it. And so, things such as OpenTelemetry and such as the products that Splunk builds, those are also ways in which we believe our customers can achieve that. >> Yeah. And we can... I mean, as I mentioned before, this partnership goes well beyond OpenTelemetry, right? And so, if you go use like Splunk Enterprise, Enterprise Cloud, Splunk Observability Cloud, and you're running on AWS, you have excellent support and excellent visibility into your Amazon infrastructure, into the services and applications you've deployed on top of that infrastructure. We try and give you, and I think we do succeed in this. We give you the best possible experience, the deepest possible visibility, into what it is you've deployed on AWS, so that you can be even more successful as a business, and so that you can be even more successful on AWS as a platform. >> Yeah. This is a great conversation, Morgan. You mentioned the early days of Web Services. AWS stands for Amazon Web Services built on web services. So interesting throwback there, but made me think about the days of the early days of web services. And if you look at data, what's going on now, the top partners in AWS, you're seeing a lot of people thinking about data differently, they're refactoring, a lot of machine learning, a lot of AI going on at scale. So then, you got cloud native, things like Kubernetes and these new services being stood up and teared down with automation. A whole new operating model's coming. And so when you think about observability, the importance of it, I mean, can you share your perspective on this whole 'nother level? I mean, I always say that whole another level sounds cliche, but it is next level. I mean, this is completely different. What's your reaction? >> Yeah. There there's a ton of factors here, right? So as you point out, companies are totally shifting how they use their cloud infrastructure. And part of this you see during their cloud migrations, a part of it you see after, and they're shifting from their sort of stateful VMs that they may have had in the past to infrastructure that they tear down and put up regularly. And there's a lot more automation. With this, comes as I mentioned before, complexity, right? And also, with this comes more and more businesses becoming even more reliant on their digital infrastructure. And so, not having observability into your applications, into your services, into your infrastructure, to me, is akin to running a business, say running a large warehousing or distribution company, but not having any idea where you're shipping products or where things are, or not having any accounting or CFO, right? Like, business has become so digital. Business is so reliant on technology, and that's unlocked a ton of new things. It's great. But not having visibility into how that technology works or what it is that's deployed or how to fix it is akin to having no visibility to anything else in your business. It's nuts. And so, observability is super, super critical, particularly for customers who are adopting this new wave of cloud technologies on platforms like AWS. >> Danielle, on your side too, you're enabling this new capability so that businesses can do it, the partners do it, we're calling it super cloud. We've been calling it super cloud kind of dynamic where new things are happening with the data. And you guys are evolving with that. Can you share what you're seeing on your side as your partners start to go to the next level? What are you guys doing? How does it all come together? >> Well, we always talk about what has happened with data in the last couple of years, which the cloud has really enabled around, you know, variety and velocity and there's one other "V" that's escaping me right now, but essentially, all of this data is coming in and providing the ability for us to make better decisions, to build better products, to provide better experiences for customers. And so, I just think, the OpenTelemetry project, as well as what Splunk is doing is just another example of how we're taking this massive amount of data and being able to provide better experiences and outcomes for customers. >> And you guys have been working along together for long time, Splunk, and, it's been a great partners, if we're going back with that been covering it on theCUBE and SiliconANGLE. So, we know that, the change is key observability. Can you imagine a company without a CFO, Morgan? That's just boggles your mind, but that's what it's like right now. So... >> It is, yeah. >> And the people who take advantage of that are winning, right? So it's like, that's the key. >> Yeah, I know. I mean, even in my own career, right, I've moved between different companies. And I remember, when I joined Google in particular, which is where I worked at previously, I was very impressed with their internal observability tools. And I'm certain, I haven't worked at Amazon. I'm certainly, I just assume inside of Amazon they're excellent as well, so a lot of the large cloud firms these days. But it was so refreshing going from an organization where if we had some outage or something went wrong, there were like a very small set of people who could actually understand what was going on. And then you would just have to manually dive through logs and correlate requests manually between services. It's very challenging. And so, when things went wrong, they went wrong for a long, long time. And so, the companies that understood this even in the past are already very successful as a result. I think now, the rest of the industry is really in the midst of adopting these observability practices and the tools that are required to implement them, because you're right. Otherwise your development velocity slows down. Now you're getting out competed by your competition. And then, when you have a problem, it blows up for ages. And once again, your competition can take advantage of it. >> And, can you just summarize the observability piece relative to the OpenTelemetry? Where is that going to go? Where do you see that evolving? >> Sure. >> I see open source is growing like crazy, we all know that. >> Of course. >> But OpenTelemetry in particular and open source, 'cause this is a big hot area. >> Yes. So to set the stage for people, OpenTelemetry, unlocks observability in many ways. As I mentioned earlier, OpenTelemetry is how you capture data out of your application. It doesn't process it. It's not a replacement for something like Amazon CloudWatch or any Splunk's products, but it's how we get the data out of your system, which is a remarkably difficult problem. I won't dive into it today, but, those who work in this space are very aware. That's why this project exists and it's so big, that actually extracting information, metrics, logs, distributed traces, profiles, everything else, from your applications and from your infrastructure is very, very difficult. So for OpenTelemetry, where it's going is just continually getting better at extracting more types of data from more sources, and doing that more effectively for people in a more standardized way. That will unlock firms like Splunk, firms, like Amazon and others to better process this data. In terms of where that's going, the sky's the limit, right? Like, everyone's familiar with APM, people are familiar with infrastructure monitoring, but there's a lot more capabilities coming there for security analytics, for network performance monitoring, for getting down all the way to single lines of coding your application, how they impact everything. There's just so much power that's coming to the industry right now. I'm really excited to see where things go in the next few years. >> And Danielle, you're in the middle of all the action as a solution architect, really set the stage for their companies and the ISVs, and this is a big, hot area. What are the patterns you're seeing and what are some of the best practices that you're doing will help companies? >> Right. So I think, summarizing our entire conversation, the big things that we're seeing in the market is essentially more and more companies are looking to move to a continuous deployment and a continuous integration environment. And they're looking to innovate faster and spend less time hot patching or hot fixing their environments and they want to spend more time innovating. And so, that you know, the patterns that we're seeing is... What I see and what I actually experience firsthand at re:Invent when I talk to probably over 40 or 50 ISVs, is customers want to know in their environment, where are their changes? Where are their security vulnerabilities? Where are their data changes, and what are customers really experiencing, whether it's latency, poor experience throughout their products, those types of things? So security, data, and observability are just key to all of that experience and that's what we're definitely seeing as patterns, what we're seeing with our customers and also what value our ISVs are providing in that space. >> That's awesome. And the other thing I would observe is that there's more of an integration story going on around joint projects, whether it's open source. >> Absolutely. >> Because this is where we want to get that services connected. And it's mutual beneficial. I mean, this is really >> Exactly. >> whole 'nother, new kind of interoperable cloud scale. >> Yeah, if I could say one thing else there, I think that, a lot of the customers who are trying to move into the cloud now are, maybe not technology forward companies and they really need that solution. And that's very important. I think COVID has pushed a lot of companies into the cloud maybe very quickly. And, that has been something else we've observed in the market. So, solutions and full solutions between ISVs and ISVs, or ISVs and AWS is just becoming more and more common thing that we see. >> And, you mentioned John, in the open source space as well. Like, we're certainly from Amazon to Splunk. So we're talking a lot about those, but there's a lot of other firms involved in projects like OpenTelemetry. And I think it's very endearing, very heartening to see how well they cooperate in this community and how, when their interests are aligned, how effective they can be. And it's been very exciting to work in the space and very pleasant, honestly, to see everything come together with this huge set of customers and partners. >> Yeah. The pleasant surprise of the pandemic has been that people come into the cloud and they like it and they, "Hey, this works," and they double down on it. Then they realize, there's more there and they refactor. So, you're seeing real examples of that. So, this is a great discussion, great success story. Congratulations Morgan, Danielle. >> Thank you. >> Great partnership between Splunk and AWS. We've been following for a long time. And again, this highlights this whole another level of integrating super cloud kind of experience where people are getting more capabilities and doing more together, so great stuff. >> And this is just one facet of that, right? Like, there's all the other connections of Splunk Enterprise, Splunk security analytics products, and others. It's a deep, deep partnership between these firms. >> Yeah. And the companies that innovate and get that new capability are going to have an advantage. And you're seeing... >> Yes. >> Right? >> Agreed. >> And this is awesome, and great stuff, thank you for coming on and sharing that insight. >> Thank you. >> Congratulations Morgan over there at Splunk, great stuff. And Danielle, thanks for coming on and sharing the AWS perspective. >> Thanks for having me. >> And you guys are going to the next level. You moving up to stack as they say, all good stuff for customers. Thanks. >> Thank you. >> Okay. >> Thank you. >> This is season one, episode two of the AWS Partner Showcase. I'm John Furrier with theCUBE. Thanks for watching. (gentle music)

>>Hi and thanks for joining us today. I'm Arwa Qadoura, vice president of Goto Market for HP Green Lake. In this session, we're going to explore a few of the ways we're bringing the cloud to your data center and co locations, especially for your most demanding workloads. We'll show a few examples of how we do this and how we can help you with HP. Green Lake with HP Green Lake were leading the market for on premises and hybrid cloud. With a decade of experience and over 1000 customers, we've been able to continue enriching our portfolio of services, leveraging the vast input from our customers. And what we're hearing now is they want us to take on the apse and data that are most critical to run their business on our customers. Love the cloud experience and wanted available everywhere, including their data center and Coehlo H. P E. Green Lake is the cloud that comes to you. We deliver a cloud experience for your >>infrastructure and workloads in your data center or co location and at the edge. HP Greenlee Cloud Services offer consumption based economics and scalability for a wide range of platforms. All managed for you by HP or by a rich ecosystem of partners. In June, we brought the Self service point and click experience of the cloud to our new services for containers, virtual machines and ml apps, and dramatically sped up the delivery of our infrastructure services with standardized building blocks T shirt sized that you can get in ASL. It'll us 14 days and a few weeks ago we added V. D. I as a service to meet the strong demand to help your employees around the globe work securely wherever they may be. Today we will look at four examples of how we provide the cloud experience for the workloads that are most critical to run your business, and we'll give a few industry examples. First, we'll talk about helping financial institutions manage risk and compliance. We'll talk about improving health care with a secure, flexible electronic health records platform, optimizing production and delivery for manufacturing with S A P Hana and answering your biggest questions with high performance computing. When we talk about thes demanding workloads, whether we're talking about inventory management, payment processing, medical imaging or any additional ones you see here, two things typically hold true. First, they're very difficult to move to the public cloud due to the challenges around Leighton See and Performance data Gravity I P. And Privacy Protection and the data entanglement with many other APS. And secondly, they require app specific expertise to implement and integrate continual performance optimization, strong resiliency, security and compliance management. And container is a shin to achieve mobility. These air tough to meet but essential toe have. If you're betting your business on these workloads, we've helped our customers meet these challenges and requirements in the data center. Let's start our discussion about these workloads with managing risk and compliance. Risk and compliance management require analyzing huge amounts of data streaming in real time through the organization, and Splunk is widely used for this as the scales. We have found that often infrastructure is the bottleneck and organizations develop blind spots. Due to this, this means they could only see some of the data. Scaling and making changes is also a slow process with such a complex set of infrastructure, and I T resources often don't have the skills to manage new platforms such as container based implementations. We've looked at the situation and built a differentiated architecture er to solve this challenge. The solution is container based, using the HP as moral container platform. It's an infrastructure that is tuned for Splunk and resulted in a big reduction in the total servers needed. It's delivered as a service through HP Green Lake on premises fully managed to make adoption fast and to cover the skill gaps, I t may have the outcomes. We tested our approach and found the dramatic improvements you see here. Infrastructure efficiency improved dramatically, with 17 times increase in throughput and 12 Splunk indexers per host, up from one. Compliance and insights into risks improved from removing the blind spots with a 10 times reduction and infrastructure needed to ingest up to 8.7 terabytes per host per day. And customers have a greatly simplified I T operating model by moving to HP Green Lake fully managed so that HP takes care of the container and infrastructure management. Next, let's talk about improving health >>care with a secure, flexible e HR platform. The global pandemic is putting an extraordinary burden on an industry whose budgets and resources are already stretched to the limits and H P can help health systems in medical research institutions around the globe recognize the value of HP Green Lake for our infrastructure as a service needs scalable storage for high resolution medical imaging, high performance compute for medical research and v. D. I. For the digital workplace. Today we are pleased to introduce the platform for epics E H R System. This is a full platform. As a service offering for Elektronik Health Records, the service supports the epic software stack with validated HP infrastructure and epic certified expertise to run the full environment for you. This enables health care institutions toe offload the complexities of moving to and operating a modern epic platform, reducing cost risk and time with a fully managed paper use cloud service in their own data center or cola facility. Now our customers could focus on delivering life affecting healthcare outcomes and not on the nuances of daily technical operations and upgrades. So how is HP qualified? Think back to the requirements we talked about for expertise. We have a 25 year partnership with EPIC, and over 65% of epic customers use RHP infrastructure, including storage servers, software and networking. We know epic and are trusted by epic customers. We have a dedicated program management office with focused epic resources to help health care systems make the most of their epic platform improving their quality of care, financial performance, work, low efficiency and, most importantly, their patient outcomes. The next workload I'd like to cover is S a P Hana s A P Hannah runs many if not most manufacturing organizations, including our very own. Here in h P s A P finds that 70% of customers are looking to remain on premises with S A P Hana as they migrate toe s four For the reasons we discussed earlier performance, resiliency, security, I protection and control. And we're proud to be one of Aesop's most critical technology partners, running approximately 40% of the on Prem s a p customer base. Thes customers trust HP infrastructure to run their critical s a p environment and we're excited to extend the value into a fully managed on Prem Cloud service. Today we bring the cloud benefits of HP Green Lake toe s a P Hannah customers on premises in two ways. Standard hp Green Lake uses S a P certified technology from HP with the scalable paper use model with H P's outstanding support and management services ready to meet the demanding requirements of S A P. Hana. And now we are working with S a P for the S A P Hana Enterprise Cloud Customer Edition which is powered by HP Green Lake and fully managed by S A P for you, which is the sap cloud in your data center. HPD point next services are essential to our customers. One of the reasons that customers choose HP for workloads such as SAP is our expertise from strategy all the way to operation with advisory and professional services specific to your application. We help you succeed. HP understands migration toe s A. P s four hana and as the leading technology vendor of S a P Hannah Infrastructure and a large s a p Hannah customer ourself, we have the expertise within our advisory and professional services. To ensure your success as you move to s four, HP has delivered over 1500 s, a p Hana consulting projects and HP point Next services has the expertise globally to accelerate time to value and mitigate your risk. And lastly, HP offers a center of excellence Experience for S a P. Hannah providing specialized support from our experts Toe optimize operations for S a p environments The last and maybe the most demanding workload that will cover today is HPC high performance computing. Today we are announcing H p e Green Lake for HPC. This is an exciting time as we bring our cloud services to HPC wherever you need it. As the leader in HPC, we have significant i p To give HPC customers. We offer the speed and scalability that you need with components such as high speed interconnect, high density compute platforms and software to manage HPC operations and performance. And unlike other technology companies, thes are all from HP, fully integrated, fully supported and can be fully managed by HP. And we've built an ecosystem of I S V applications that we closely collaborate with to make HPC run seamlessly high. Performance computing can get complex with HP. Green Lake for HPC will simplify the approach without taking away any of the power. Pick the starting point that fits your use case small, medium or large, and get started. These building blocks are HPC optimized, meaning you could bring the technology that we use to predict weather or decode the human genome to your everyday APS. No capital up front, pay for what you use and the implementation is managed for you. With our building block approach, we can eliminate the long design and implementation phase, which could take months or even a year over time as your clusters grow, modernize and change H p e Green Lake Capacity management helps you always have capacity ready ahead of your needs. What is the experience with H. P Green Lake for HPC, you order, we deliver in as little as 14 days. We install your systems and you can quickly deploy your HPC APS. With the new point and click service experience, researchers and analysts can get access to their HPC cluster resources from the self service portal without putting. I t in the middle of every request we manage the clusters for you. Take care of upgrades, performance and growth, and you pay based on what you use. Simplifying HPC economics and operations. This is how we bring a cloud to your most demanding workloads. So we've covered a lot, and the big question is, so what? How do you benefit analysts have found that with HP Green Lake, you save 30 to 40% on total cost of ownership by eliminating over provisioning, which on its own is huge. But the additional benefits are equally important to our customers. You can speed deployments of projects by 75% cut your risk with 85% less unplanned downtime and improve ICTY productivity by 40% due to the services, including that greatly simplify I t operations. What's next? If you want to learn more about how we bring cloud services for your most demanding workloads, whether they're for risk management, E H. R s, a, p or HPC, or for other workloads you depend on us for Please engage your HP account team or your HP partner. If you're already are a customer for HP Green Lake, thank you. And we're ready to globally help you with your next project. And, of course, please visit us at p e dot com. Backslash Green Lake Thanks for joining me today.

>>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.

(upbeat music) >> Narrator: From around the globe it's theCUBE, with coverage of SUSECON Digital. Brought to you by SUSE. >> Stu: Welcome back, I'm Stu Miniman and this is theCUBE's coverage of SUSECON Digital '20. Apeda Welcome to the program Vincente Moranta, who is the Vice President of Offer Management of Enterprise Linux Workloads on Power. Vincente, pleasure to see you, thanks for joining us. >> Vincente: Hey Stu and thank you for having me. >> All right, so we know that SUSE lives on a lot of platforms. We're going to talk a bit about applications specifically, primarily SAP. Give us a little bit, Vincente, about what you're working on, and the relevance to the partnership with SUSE. >> Sure, absolutely. So, the last five years I've been responsible for offering management at IBM. Focused on solutions that live on IBM powered systems. In particular, we started with SAP HANA, and obviously SAP and SUSE, with their fantastic relationship, was a big part of that and continues to be as we have grown the platform for the last five years. >> Excellent. So, SAP of course, critical workload, we've been seeing SAP go through those transformation. So, help us understand what work needs to be done to integrate these things? Make sure that companies can run their business. >> Yeah, I think primarily as clients are making their transition from a traditional type of an ERP, CRM, and even BW type workloads, they're looking for a way to make those transitions. Really get in to the whole digital transformation and all of the spaces of being able to leverage technology in a way that creates value to the client, in almost real time. But they want to do it with technology partners that are going to enable the client to do it with minimal risk, with high flexibility and with partners who are there for them to, in some cases, do things that are not necessarily all too forwarded or ready to go yet. But really giving the customer the ability to adapt to things. And when we started with SAP HANA, as I mentioned, the customers in the market who were doing HANA on X86 platforms were limited to certain set of capabilities, certain set of support statements, and things like that. And a big part of that was bare metal implementations which still to this day remain the most popular way to deploy HANA in an X86 environment. But when we got together with SUSE and with SAP and we started the partnership around HANA, the thing that became very clear was that customers needed flexibility. They needed to be able to adapt to changing environments, very interesting challenges that they were trying to tackle with these HANA projects. But the capabilities of the servers that they were using, were not allowing them to have that flexibility. And then, even if SUSE was trying to do certain things and give some flexibility to those clients, if the infrastructure cannot handle it, or vice verse, it really just is a one-party trick and it doesn't work. So the focus with SUSE, almost from the beginning, has been on tool innovation. And we've been able to accomplish really amazing things together with them and SAP. Things that could not have been possible without that very strong collaboration. And one of them that is very recent, is shared processor pool. Right? In a world where HANA is deployed bare-metal systems, IBM Power is always doing virtualization, and together with SUSE, we were able to come up with a solution. And with SAP, obviously. That allowed customers to share source in a virtual way across many HANA instances. So completely revolutionizing the DCO and the ROI for clients working with HANA. Without trading out any of the resiliency, any of the performance, and everything else. So, that's the balance that a lot of these customers are looking for is flexibility, and better returns, especially now more than ever. Without trading out all of the things that they need for an S/4 HANA project or an ERP or a BW project. >> You talked about the flexibility and the returns that customers get on this. I wonder if you step back for a second, where is this hitting on a CIO's priority list? What has changed in today's Cloud era? Couple weeks ago, IBM Think was going on, heard a lot about customers, how they're going through their journey in the cloud. We know there's a lot of options there so. SAP solutions specifically, there's a lot of ways that we can do this. So how does a CIO figure out what the best solution for their skill-set and the technology partner that they work with. >> Yeah, I think at a high-level where the CIO's are basing nowadays, is kind of, it's a good time to be a CIO, I think, because you get a chance to have a broad range of deployment options. Without having to trade out from the features. I'm sure some CIO's will disagree and will say there's plenty of other challenges that are making their lives complicated. But if we just focus on the fact that you can deploy HANA - you can deploy it in the cloud, you can deploy it in hybrid, you can deploy it on premises. And the largest then, and especially with our capabilities, and together with SUSE, the CIO doesn't have to make a choice on trade out of things that they have to lose if they make one of the other. I think that is what helps them to feel comfortable to go in to SAP and being able to adapt. If a project becomes too large or the data transfer requirements become too complicated or too expensive, it's easy enough to bring it back and to maybe leave dev test in a cloud and move the rest of the production environment to on premise. Through a number of partnerships that we have done over the last few years, there's a number of very large MSP's and CSP's including SAP HANA Enterprise Crowd - HEC - and very soon IBM cloud as well. Who can provide all of these capabilities that SUSE and Empower allow for a HANA deployment to be done in a Cloud. So from our perspective, even though I'm a hardware guy, and some people may think I only care about on premises business, the reality is when a customer says, or a CIO as you were asking. When a CIO is trying to make a decision we don't want that CIO to be thinking they have to make a decision between IBM supporting them only if it's on premises or only if it's on Cloud. We can do both. And they don't have to do, it's not a hard trade off to decide. You can start with one, you can go to the other one. We can have capacity for them like we're doing with SAP HEC today, SAP HANA Enterprise Cloud. They're using Power9 technology. The customers benefit in regardless of which deployment option they choose. Both with SUSE underneath it. I think we're trying to make it simpler for them to make those choices without infrastructure becoming the sticky point. >> Yeah, and you talked about the support that users can get, of course, from IBM. At SUSECON, a lot of the discussion about the community there. >> Absolutely. >> So, what can you tell us about, you've got thousands of customers that are running SAP HANA on Power, how do you help them rally together and be part of (muted). >> Yeah, so, you and I have known each other for a while and I think when we started working together at a prior company it was around communities practice. And the organizational network and social network. A big part of what we have done is just going to that same approach. Of just connecting people with people. Right? Connecting people from SUSE with people from IBM, with clients and trying to foster valuable interaction between those clients. Whether it's TechU, IBM TechU Conferences, SAP TechEd, SUSECON, you name it. We're always kind of looking for ways to bring people together. And I'll put in a plug for a client entity, a client council called the SAP Power Customer Council, which is a group of clients that decided on their own to get together and bring other customers who are doing SAP deployments on AIX, on Linux, obviously with SUSE and HANA, and come together once a year. We also have almost monthly interlock and workshops with them. But that is one way where the SUSE folks, IBM Power, SAP Development, all come together with a whole bunch of clients and they're giving us feedback. But also identifying things for us to work on next. From a support perspective, as you said, we have thousands of clients nowadays, and the really fantastic thing has been very few issues and the issues that we have had, SUSE, SAP and IBM, all three of us together, have been able to resolve them to the customers satisfaction. So it just kind of demonstrates that regardless of where something is invented SUSE with SLES, SAP with HANA, us with our hardware and our hypervisors, when it comes to the clients we all work very closely together for their success. >> Great. Those feedback loops are so critically important to everyone involved. I guess last thing, maybe if you've got a customer example that might highlight the partnership between IBM and SUSE? >> Yeah, there's a number of them and we have, I think it's over 60 public references together with SUSE of clients who are doing an SAP HANA with SUSE Empower. But a couple that come to mind, obviously Robert Bosch is a fantastic client for all of us. A fantastic partner. And they've been with us almost from the very beginning, together with SUSE and together with us. And they helped us to identify early on some things that they would like to be able to see supported. Some capabilities that they expected to be able to have, especially given that Bosch had a strong knowledge of IBM technology, IBM product. And they wanted to be able to apply some of the same capabilities around Live Partition Mobility and large size L-bars for HANA and things like that. And they worked very closely with SUSE and with us, and with SAP, to not just give us the requirement, but really help us to identify okay, how should this work? Right, it's not just creating the technology and adding more and more features but how do we integrate it, how do we integrate it in to Bosch, who had created a fantastic self-provisioning type of a portal for all of their clients, all of their internal entities around the world. That was really cool and it really kind of helped us to highlight how we could integrate into tools, monetary, and reporting, etc that our clients have. Another example if I can, is Richemont. Richemont International is based in Geneva. Luxury brand. And Helga Delterad who was the Director of Idea at the time, kind of came to me and gave me a challenge. He said, "Look, I love HANA Power. I love that we can do all of these things with it. But I really would like be able to share processors across multiple HANA instances. That would really reduce the bill. It would really reduce the cost. And Richemont would be able to achieve a much quicker return on investment than we had anticipated." So, he gave us a challenge. The challenge went to everybody. It went to SUSE, to us and to SAP, we all got together and again with Helga being the executive sponsor on the client side, he really kind of worked with all of us. Brought us together and it was a power of the possible type of situation that now is generally available to all clients. And it's thanks to Helga, thanks to Richemont, who brought us together and gave us that challenge. >> Excellent. Well Vincenta Morante, great to catch up with you. Thanks so much for sharing the update on IBM Power and the partnership with SUSE. >> Thanks Stu. >> All right, we'll be back with more coverage from SUSECON Digital '20. I'm Stu Miniman and as always, thank you for watching theCUBE. (upbeat music plays)

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum, World 2019 brought to you by IBM Wear and its ecosystem partners. >> Welcome back. This is The Cube. Live at VM World, 2019 times. Too many men with my co host Justin Warren, David Dante, John Ferrier. John Wall's John Troyer. Like a certain founding fonder, Alexander Hamilton, the Cube is going non stop coverage for the three days Habito. Welcome back to our program. Two of our Cube alumni's Lynn Lucas, who is the chief marketing officer of Cohee City. And she's brought along John White, who is the chief innovation officer at Expedient. Thank you both for joining us. >> Happy to be here. Happy 10 year anniversary to the cute >> Well, thank you so much. And you know, so many people we've known over the years. Actually, the first time I met John wait was I believe in this whole, you know, at VM World, you know, talk about what's going on. Eso You know, I always love talking to the service riders because it's been going through just a massive transformation, you know, all along on you, John, you've got a different title Since the last time I interviewed you, You been involved in the strategy You and I have gone toe cloud shows together and some of the other things they're so bring us up to speed as to, you know, expedient here at the show. And, uh, what brings you here with cohesive? >> Yes. Oh, yeah, thanks to your right. But I think it's probably five or six years ago. Maybe I asked too. You said, Hey, what do you know about the service provider community? Cause I wanted to kind of educate you because it was something that's been fairly new and expedience been in that industry for a long time. We were mainly in infrastructure of the service provider, man. The service providers are rounding on all that I t. Stuff that people need and ah, this VM world is a huge one for us. Last year we launched Enterprise Cloud, which is a product based on VM. Where's full softer to find stack And that was something we wanted to go to market with to give an alternative people, When you say Hey, I need to go to the cloud and you realize that okay. I really can't just take my APS and lift and shift and go there. There's another place for you that's a little a little more familiar. And as we see 20,000 people know VM were obviously that air here. So that's usually what what's usually happening in the Enterprise. So we're talking with those folks, and so we would launch that platform. We thought about everything differently. We were running virtualization since, 06 of seven, and we wanted to change everything back up platforms as well as needing things like scale out now, as were necessity at that point. So this VM worlds are coming out because we had, ah, release that last year. And now we have a lot of good customers to talk about on that platform. 12 months later. >> Yeah, well, Lynn, first of all, congratulations because, you know, I know John sits on customer counsels for some of these events. I've dug into a bunch of the networking pieces with him and actually was, you know, we spent a bunch of years. We went to a bunch of shows together and he was looking at the some of the various vendors and a bunch of the new startups and cohesive E is the one that you know really stepped up provided the solution that he was looking for. So it's been interesting to hear service fighters. You were usually the first ones that companies were talking to. But bring brings the cohesive story there. >> Yeah, and so were a super pleased and honored to have expedient working with Cohee City. And John has been instrumental in really providing a lot of direction to us on what his needs are and how to make the product even better for for him and the service provider community, it's a huge part of our go to market strategy. We believe that with the massive growth in the interest in hybrid and Justus John was saying, There's so many customers that really aren't equipped to deal with How do I move to ah hybrid cloud strategy, whether that before compliance reasons, whether that be geographical reasons under you've seen them all. And so this is something where we feel really thrilled to have the, um, where's cloud partner of the Year working with us and to help serve customers with the expedient enterprise Cloud platform. >> Congratulations on that team. And right when we first met five years ago Public cloud for VM wear And for most of the service bodies, it was the enemy, all right. It's like, Oh, my gosh. There, you know, you went toe Amazon reinvent and create a little bit of partnership. So give us the update on hybrid. What that means and how solutions like, Oh, he city, you know, help you provide services to your customer. >> Yeah, it's funny you mentioned. I mean, that's you would ask me, What are you doing here? What are you doing here? Because it was going out doing this research, seeing where the market was on containers on adoption of Claude practices. So we wanted to make sure that we were very open with all the different solutions that are out there. And that's been our strategy from the from the start. So building enterprise cloud was one thing we need to do to come to market with a platform like everybody else. But multi cloud is really where we have focused. And it's funny. I mean, when I when I first started coming to the M world, it was very product centric, you know, you had this product, you could do X with it. And here's the return that you would get at it. And when you're coming to the emerald now it's more about platforms. And that's really what I found most interesting with Cohee City when I first met Mohit, probably two and 1/2 3 years ago, was that he was focusing on the platform of data management. And that's really what the problem was. It wasn't now, specifically, it wasn't data protection. Specifically, it was What all can you do with that with that data management? And we're You know, we're spending a ton of time with Cohee City on. We were building multi Tennessee with them to them, be able to support that. And that's what we're delivering on now. So it's it's it's the scale out now's it's ah, data protection. And then we're taking those service is and then putting him in eight of us in azure or wherever it might be because it doesn't matter to us, because long term we want to care about the long term I t care and feeding and focus on that as our value prop instead of just actually which silo >> it lives in. Yeah, and right from the very beginning, I remember speaking to Kohei City very, very early on when it just sort of come out of stealth. And it was baked into into the product the idea of data management that it was going to be much more, much more than just data protection. So, what are you seeing now that we have a lot of years of product development has clearly gone into it since we first looked at it then. But what are you seeing? Customers using the platform for here in 2019? >> Well, we started a little bit more unique than most other customers. I think we talked about this, you know, throughout CO e city. And we actually started on a scale out now's platform s. So we have one of our clients homes dot com who? They're with us this week because they have a really interesting you. No need for this type of enterprise. Cloud there with us and they're talking about all the different benefits they received out. And they started actually with on the file side of things homes dot com, real estate, online real estate. So I think you know about how many images and how many fouls you have out there. We have 2.6 billion images right now running on the cohesive platform. That was 2.6 billion and a 30% annual growth rate. Yes. So the numbers are crazy. You can't put those on any other traditional now, as that's out there. Uh, so we used a he city first to get started there, and then the backups really were the icing on the cake. So last October, we built We started going out the Nats platform to handle those images. And if you actually go to homes dot com right now, it's being served fully out Enterprise cloud from a container and virtual machine layer and then on the back end from Cohee City. And they were using that to protect it as well. >> And I think that if I add on to that is really a testament to the, you know, the foundation that mo it built, which is a true distributed file system, Google like, in that sense. And I think correct me if I'm wrong, John. But you know, you then also saw while that benefit of a platform approach and not another silo for the backup and having co he city help solve the challenges for both files as well as data protection and then maybe one day in the future. Looking at some of the things that we're doing now that we're doing more security on running APS and things like that on the platform as that may be an extension for you, >> Yeah, that's that's definitely a big focus of our effort, the global d duplication that you get with CO he city. When you add all those files in all the different customers, we have all the different virtue machines. Ah, the ratios were hitting or just insane. And it's something we decided as a service provider that we we said, OK, this technology, we actually want to give that benefit back to the customer. And so when somebody buys data stores from us on the data production, they buy what they're actually consuming on the disk. So you could have 100 terabytes in all of your V EMS. If you only need one terabyte, that's all you're buying from us. And that's a lot of the power of that platform that we get with cohesive. >> Yeah. So, John, wanna help? They want you to help us understand the nuance of something. We're platform? Yeah. Has a little bit of new Monsanto. Little bit, a little loaded thing. GM was the platform. Cohesive is a platform. You use both of them. So just help us understand how cohesive Ian Veum wear and all those things that they go together. They're not, you know, competing against each other in as your architectural Or are they? They're >> not competing there two layers, In my opinion, where you have your primary stores really living in and the M R and secondary storage is everything else on Cohee City. Ah, what? The nice thing is, they did a lot of cool things to kind of marry the two together. Um, one of the one of the tools that we're using Aesthetic ahi city is called Instant on or instant Restore a Virtue machines so we can actually spin up a virtual machine almost instantaneously. It lives on the Coast City platform. Once it's rehydrated, then does a storage the emotion automatically into the V, m or environment. So we're able to do migration or if we had, You know, we have a bad ransomware attack and we need to restore 100 V EMS within a few minutes. We can instantly bring those back up in the cohesive platform and then move them to a production virtual environment once it's done. And that's something that we weren't able to do with our existing vendor. And that was something we needed to actually go and focus on because being in the healthcare space being in the compliance space, that's that's a big problem for us. >> Yeah, just add, I think that, um Vienna, where is clearly one of our most important partners. The very first area that mo it developed was data protection, for I am where, I would say, well north of 70 75% of our customers are protecting their Veum, where environments We have a very large customer that's protecting over 18,000 V EMS on Cohee City. So with the certifications that we have with V. C. D. And with the integrations, as you've mentioned with of you realize it's it's really it's a partnership. Andi think we're adding a lot of value to the customers that are building on V. M. where is >> very complimentary for sure. >> Yeah, it's been interesting that to see how customers choosing to go with a platform like like expedient because, as you mentioned earlier, stewed like five years ago, Cloud was the enemy. And but we're being told that on a public card is gonna take everything, and it's just gonna own all of the environment where is now? In 2019 we found that the story is actually much more complicated than that. Some of us probably believe that at the time I put my hand up is one of those that customers actually needed to live in multiple places. It's not a story of or it's a story of end, so you do need to be ableto have something which can work well with others on the same way we've got. We've got co, he's ity and V M. Where is it? Well, they're not really competing with each other. They work better together and particularly as customers scale, we find my any any kind of enterprise customer is header a genius, so you have to have solutions that give them options and that work together well with you have to play nicely with others. >> I think that's exactly right. And part of what we've done is built a software to find solution and to also give John expedient flexibility. How do you want to deploy for your customers? The solution. Is it in the, uh, the hyper scaler? Is it Hello, somewhere? Is that your own cloud? And so that's part of the advantage. I think all in one solution that then you can give your customers some flexibility as well as to how they want to consume the service as well. >> Absolutely meaning the flexibility And you mentioned software only, and are, you know, software or suffer to find that was something that was big for us. When we're looking for partnerships, we have a standardized hardware build that we want to use. And that was all built on Del. And it was something that, you know, we were able to work with obesity to get that standardized so we can continue to roll out. Excuse that we were most comfortable with. And they could just have the software layer on top. >> Yeah. So you've managed to do this successfully. You're going really well. Yeah. What's next? >> Well, um you know we have, you know, So in we ordered in October of last year. Right now we have six petabytes online enrolling. So that's that's great. You know, that's that's good to see. That's going to continue to grow at a pretty rapid rate. Data is something that obviously, we all know is never gonna shrink on. We're gonna continue to grow that with new customer acquisitions, and that's everything where we want to continue to go with this, Uh, this product specifically is on the data management side. The things that they're doing in Helios to start to get understanding and awareness in value out of that data that's sitting there is really, really important and exciting for us in the future. We deal what tonic compliance PC idea says hip. And we want to make sure that the data that we're storing inside of there will be compliant by those. So being able to write an application to see if the credit card numbers in a file or in a database by using the cozy platform that we brought us value. Same thing goes with a lot of the ransomware protection they're doing. So if you see a foul that gets encrypted, then I know. Okay, I have a problem. I better go look at that and give me a time stamped, Actually. Go on, restore from instead of actually trying toe, you know, pick around. And hopefully I find it when it before it was encrypted. So we're really excited about those opportunities is the future and seeing what data management can just bring to it. >> Well, Lynn, always a pleasure to catch up with you. Thank you so much for joining us again. And John, my friend, this is your six time on the program, actually gonna have a celebration in New England in a little over unveil for, ah, six s o right in New England. So for Justin Warren, I'm stupid him in. We love talking about sports here, and, uh, yeah, the Cuban way have the Niners and the Patriots for the team there. But as always, Thank you for watching the cue

>> from our studios in the heart of Silicon Valley, Palo Alto, California It is a cute conversation >> lover on Welcome to this cube conversation here in Palo Alto, California. The Cube Studio. I'm John for the co host of the Cube Weird Sylvan shop. Who's the head of solution Architecture and open systems securing Esti win of right of other cloud to point out like capabilities. Very successful. 20 plus years. Operation Civil was the one of the first folks are coming over to the US to expand their operation from Europe into New York. Now here in Silicon Valley. Welcome to the Cube conversation. Thank you. So instituting trivia. You were part of the original team of three to move to the U. S. From Switzerland. You guys had phenomenal success in Europe. You've come to the U. S. Having phenomenal success in the US Now you moving west out here to California on that team, you're opening things up at the market. >> It's been a chance, Mikey. Things can presented themselves step by step, and I jumped on the trains and it's been a good right. >> Awesome. You guys have had great success. We interviewed your CEO a variety of your top people. One of the things that's interesting story is that you guys have been around for a long time. Been there, done that, riding this next next wave of digital transformation. What we call a cloud two point. Oh, but really is about enterprise. Full cloud scale, securing it. You have a lot of organic growth with customers, great word of mouth. So that's not a lot of big marketing budgets, riel. Real success there. You guys now are in the US doing the same thing here. What's been the key to success for open systems wide such good customers? Why the success formula is it you guys are on the right wave. What is it? The product? All the above. What's the What's the secret formula? >> So multiple things I say. And we started as a privately owned company like broad banks to, um, to the Internet email into one back in the nineties. And, um, yeah, we started to grow organically, as he said were by mouth, and Indiana is we put heavy focus on operations, so we wanted to make our customers happy and successful, and, um, yeah, that's how we got there like it was slow organic growth. But we always kind of kept the core and we tried to be unconventional, tried to do things differently than others do. And that's what brought us to where we are today and now capabilities Being here in the Valley, um, opens up a lot of more doors. >> It's got a nice office and we would see I saw the video so props for that. Congratulations. But the real to me, the meat on the bone and story is, is that and I've been really ranting on this whole SD win is changing. SD Win used to be around for a long, long time. It's been known industries known market. It's got a total addressable market, but really, what has really talks to is the the cloud. The cloud is a wide area network. Why do we never used to be locked down? He had the old way permitted based security. Now everything is a wide area. That multi cloud in hybrid club. This is essentially networking. It's a networking paradigms. It's not lately rocket science technically, but the cloud 2.0 shift is about, you know, data. It's about applications, different architectures you have everything kind of coming together, which creates a security problem, an opportunity for new people to come in. That's what you guys? One of them. This is the big wave. What? It explain the new s t win with, you know, the old way and the new way. What is the what? What should people know about the new S D win marketplace? >> Yeah. So let me start. Where do Owen has come from and how digital transformation has impacted that. So typically corporate wider networks were centered around the Clear Data Center where all applications were hosted, storage and everything and all traffic was back holding to the data center. Typically, one single provider that Broady, Mpls links on dhe. It was all good. You had a central location where you could manage it. You had always ability security stack was there. So you had full control. Now new requirements from natural transformation broad as users are on the road, they're on their phones ipads on the in, restaurants in ah, hotels, Starbucks. Wherever we have applications moved to the cloud. So their access directly You wanna have or be as close as possible Unify Communications. I OT It's all things deposed. Different requirements now in the network and the traditional architecture didn't were wasn't able to respond to that. It's just that the links they were filled up. You couldn't invest enough thio blow up your Nampula slings to handle the band with You lost visibility because users were under road. You lost control, and that's where new architectures had to be found. That's where Ston step them and say, Hey, look now we're not centered around the headquarter anymore were sent around where the applications are, your scent around, where the data is, and we need to find means to connected a data as quickly as possible. And so you can use the Internet. Internet has become a commodity. It's become more performance more stable, so we can leverage that we can route traffic according to our policies. We can include the cloud, and that's where Ston actually benefits from the clown. As much as the club benefits from SD went because they go hand in hand and that's also what we really drive to say, Hey, look, now the cloud can be directly brought into your network, no matter where, where data and where applications. >> Yeah, and this is the thing. You know, Although you've been critical of S t when I still see it as the path of the future because it's networking. And the end of the day networking is networking. You moving packets from point A to point B and you're moving somebody story you moving from point A to store the point C. It's hard. And you brought this up about Mpls. It's hard to, like rip and replace You can't just do a wholesale change on the network has the networks are running businesses. So this is where the trick is, in my opinion. So I want to get your thoughts on how companies were dealing with this because, I mean, if you want to move, change something in the network, it takes a huge task. How did you guys discover this new opportunity? How did you implement it? What was the and how should customers think about not disrupting their operations at the same time bringing in the new capabilities of this SD win two point? Oh, >> yeah, that's it's a perfect sweet spot, because in the end is, um, nobody starts at a green field. If you could start with a green field. It's easy. You just take on the new technology and you're happy. But, um, customers that we look up large enterprises, they have a brownfield. They haven't existing that work. They have business critical applications running 24 7 And if you look at what options large enterprises have to implement and manage a nasty when is typically three approaches, they either do it themselves, meaning they need a major investment in on boarding people having the talent validating technology and making the project work already. Look at a conventional managers provider. In the end, that is just the same as doing yourself. It's just done by somebody else, and you have the the challenge that those providers typically, um, have a lot of portfolio that they manage. And they do not have enough expertise in Nasty Wen. And so you just end up with the same problems and a lot of service, Janey. So even then you do not get the expertise that you need. >> I think what's interesting about what you guys have done? I want to get your reaction to this is that the manage service piece of it makes it easier to get in without a lot of tinkering with existing infrastructure. Exact. And that's been one of that tail winds for you guys and success wise. Talk about that dynamic of why they managed service is a good approach because you put your toe in the water, so to speak, and you can kind of get involved, get as much as you need to go and go further. Talk about that dynamic and why that's important. >> Yeah, technology Jane is very quickly. So you need people that are able to manage that and open systems as a pure play provider. We build purposely build our platform for us, he went. So we integrated feature sets. We we know how to monitor it, how to configure it, how to manage it. Lifecycle management, technology, risk technology management. All this is purposely purposely built into it, so we strongly believe that to be successful, you need people that are experts in what they do to help you so that you and your I t people can focus in enabling the business. And that's kind of our sweet spot where we don't say we have experts. Our experts operating the network for you as a customer and therefore our experts are your experts. And that's kind of where we believe that a manage service on the right way ends up in Yeah, the best customer. >> And I think the human capital pieces interesting people can level up faster when you when you're not just deploying here. Here's the software load. It is the collaborations important. They're good. They're all right. While you're on this topic, I want to get your thoughts. Since you're an expert, we've been really evaluating this cloud 2.0, for lack of a better description. Cloud 2.0, implying that the cloud 1.0 was Amazon miss on The success of Amazon Web service is really shows Dev Ops in Action Agility The Lean startup Although all that stuff we read reading about for the past 10 plus years great compute storage at scale, amazing use of data like you, said Greenfield. Why not use the cloud? Great. Now all the talk about hybrid cloud even going back to 2013 We were of'em world at that time start 10th year their hybrid cloud was just introduced. Now it's mainstream now multi cloud is around the corner. This teases out cloud 2.0, Enterprise Cloud Enterprise Scale Enterprise Security Cloud Security monitoring 2.0, is observe ability. Got Cooper All these new things air coming on. This is the new clout to point out what is your definition of cloud two point? Oh, if you had to describe it to a customer or a friend, >> it is really ah, some of hybrid cloud or multi cloud, as you want to name it, because in the end, probably nobody can say I just select one cloud, and that's going to make me successful because in the end, cloud is it's not everywhere, as we kind of used to believe in the beginning, but in the end, it's somebody else's computer in a somebody else's data center. So the cloud is you selectively pick the location where you want to for your cloud instances and asked if Cloud Service providers opened up more locations that are closer to your users in the or data you actually can leverage more possibilities. So what we see emerging now is that while for a long time everything has moved to the cloud, the cloud is again coming back to us at the sietch. So a lot of compute stuff is done close to where data is generated. Um, it's where the users are. I mean, Data's generated with with us. Yeah, phones and touch and feel and vision and everything. So we can leverage these technologies to really compute closer to the data. But everything controlled out of central cloud instances. >> So this brings up a good point. You essentially kind of agreeing with cloud one detto being moved to the cloud. But now you mentioned something that's really interesting around cloud to point out, which is moving having cloud, certainly public clouds. Great. But now moving technology to the edge edge being a data center edge being, you know, industrial I ot other things wind farms, whatever users running around remotely you mentioned. So the edges now becomes a critical component of this cloud. Two point. Oh, okay. So I gotta ask the question, How does the networking and what's the complexity? And I'm just imagining massive complexity from this. What are some of the complexities and challenges and opportunities will arise out of this new dynamic of club two point. Oh, >> So the traditional approaches does just don't work anymore. So we need new ways to not only on the networking side, but obviously also the security side. So we need to make sure that not on Lee the network follows in the footsteps of the business of what it needs. But actually, the network can drive business innovation and that the network is ready to handle those new leaps and technologies. And that's what we see is kind of being able to tightly integrate whatever pops up, being able to quickly connect to a sass provider, quickly integrate a new cloud location into your network and have the strong security posture there. Directly integrated is what you need because if you always have to think about weight, if I add this, it's gonna break something else, and I have to. To change is here. Then you lose all the speed that your business needs. >> I mean, the ripple effect of it's like throwing a stone in the lake and seeing the ripple effect with cloud to point. You mentioned a few of them. Network and Security won't get to that in a second, but doesn't change every aspect of computing categories. Backup monitoring. I mean all the sectors that were traditional siloed on premise that moves with the cloud are now being disrupted again for the third time. Yeah, you agree with that? >> It's true. And I mean your club 0.1 point. Oh, you say a lot of things will be seen his lift and shift and that still works like there is a lot of work loads where it's not worth it to re factor everything. But then, for your core applications, the business where the business makes money, you want a leverage, the latest instead of technologies to really drive, drive your business there. >> I got to get your take on this because you're the head of architecture solutions at Open Systems. Um, is a marketing tagline that I saw that you guys promote, which I live. I want to get your thoughts on. It says, Stop treating your network like a network little marketing. I love it, but it's kind of like stop trying your network like a network implying that the networks changing may be inadequate. Antiquated needs to modernize. I'm kind of feeling the vibe there on that. What do you mean by that? Slow Stop treating your network like a network. What's what's the purpose >> behind that? But yeah, in the end, it to be a little flaw provoking. But I mean, even est even in its pure forms, where you have a softer controller that steers your traffic along different path. Already. For me, as an engineer, I'm gonna lose my mind because I want to know where routing is going. I want deterministic. Lee defined my policy, so I always have things under control. But now it's a softer agent that takes care. Furred takes care of it for me so that already I lose control in favor off. Yeah, more capabilities. And I think that's cloud just kind of accelerate. >> So you guys really put security kind of in between the network and application? Is that the way you're thinking about it? It used to be Network was at the bottom. You built the application, had security. Now you're thinking differently. Explain that the the architectural thinking around this because this is a modern approach you guys were taking, and I want to get this on the record. Applications have serving users and machines network delivers packets, and then you're saying security's wrapping up between them explain. >> So when we go back again to the traditional model Central Data Center, you had a security stack full rack of appliances that the care of your security was easy to manage. Now, if you wanna go ask you when connect every brand side to the Internet, you cannot replicate such an infrastructure to every branch. Location just doesn't skill. So what do you do? Why do you say I cannot benefit of this where I use new methods? And that's where we say we integrate security directly into our networking stack. So to be able to not rely on the service training but have everything compiled into one platform and be able to leverage that data is passing through our network. You've eyes. But then why not apply the same security functions that we used to do in our headquarter directly at the edge and therefore every branch benefits of the same security posture that I typically were traditionally only had in my data center? >> You guys so but also weighing as a strategic infrastructure critical infrastructure opponent. I would agree with that. That's obvious, but as we get into hybrid cloud and multi cloud infrastructures of service support. Seamless integration is critical. This has become a topic, will certainly be talking about for the rest of the year Of'em world and reinvented other conferences like Marcel that night as well. This is the big challenge for customers. Do I invest in Azure A. W as Google in another cloud? Who knows how many clouds coming be another cloud potentially around the corner? I don't want to fork my development team. I want to do one of the great different code bases. This has become kind of like the challenge. How do you see this playing out? Because again, the applications want to run on the best cloud possible. I'm a big believer in that. I think that the cloud should dictate the AP should dictate which cloud runs. That's why I'm a believer in the single cloud for the workload, not a single cloud for all workloads. So your thoughts, >> I think, from an application point of view. As you say, the application guys have to determine more cloud is best for them, I think from a networking point of view, as a network architect, we need to we can't work against this but enable them and be able to find ways that the network can seamlessly connect to whatever cloud the business wants to use. And there's plenty of opportunity to do that today and to integrate or partner with other providers that actually have partnered with dozens of cloud providers. And as we now can architect, we have solutions to directly bring you as a customer within milliseconds, to each cloud, premise is a huge advantage. It takes a few clicks in a portal. You have a new clouds instance up and running, and now you're connected. And the good thing is, we have different ways to do that. Either. We spin up our virtual instance virtual esti one appliance in cloud environments so we can leverage the Internet to go. They're still all secured, all encrypted, ordering me again. Use different cloud connect interconnections to access the clouds. Depending on the business requirements, >> you guys have been very successful. A lot of comfort from financial service is the U. N. With NGOs, variety of industries. So I want to get your thoughts on this. I've been we've been covering the Department of Defense is joining and Chet I joint and the presentation of defense initiative where the debate was soul single purpose Cloud. Now the reality is and we've covered this on silicon angle that D O D is going multi cloud as an organization because they're gonna have Microsoft Cloud for collaboration and other contracts. They're gonna win $8,000,000,000. So that a Friday cloud opportunities, but for the particular workload for the military, they have unique requirements. Their workload has chosen one cloud. That was the controversy. Want to get your thoughts on this? Should the workloads dictate the cloud? And is that okay? And certainly multi cloud is preferred Narada instances. But is it okay to have a single cloud for a workload? >> Yeah, again, from if the business is okay with that, that's fine from our side of you. We see a lot of lot of business that have global presence, so they're spread across the globe. So for them, it's beneficial to done distribute workloads again across different regions, and it could still be the same provider, but across different regions. And then already, question is How do you now we're out traffic between those workloads? Do we? Do you love right? Your esteem and infrastructure or do you actually use, for example, the backbone that the cloud provider provides you in case of Microsoft? They guarantee you the traffic between regions stay in their backbone. So gifts, asshole, new opportunities to leverage large providers. Backbone. >> And this is an interesting nuance point because multi cloud doesn't have to be. That's workload. Spreading the workload across three different clouds. It's this workload works on saving Amazon. This workload works on Azure. This workload works on another cloud that's multi cloud from a reality standpoint today, so that implies that most every country will be multi cloud for sure. But workloads might have a single cloud for either the routing and the transit security with the data stored. And that's okay, too. >> Yeah, yeah, and keep in mind, Cloud is not only infrastructure or platform is the service. It's also software as a service. So as soon as we have sales forests, work day office 3 65 dropbox or box, then we are multiplied. >> So basically the clouds are fighting it out by the applications that they support and the infrastructure behind. Exactly. All right, well, what's next for you? You're on the road. You guys doing a lot of customer activity. What's the coolest thing that you're seeing in the customer base from open system standpoint that you like to share with the audience? >> Um, so again, it's just cool to see that customers realized that there's plenty of opportunities. And just to see how we go through that evolution with our customers, were they initially or little concerned? But then eventually we see that actually, the network change drives new business project and customers air happy that they launched or collaborate with us. That's what that's what makes me happy and makes me and a continuing down that path >> and securing it is a key. Yeah, he wins in this market Having security? >> Absolutely. Yeah, Sylvia saying mind and not wake up at 2 a.m. Full sweat, because here >> we'll manage. Service is a preferred for my people like to consume and procure product in So congratulations and congressional on your Silicon Valley office looking for chatting more. I'm John for here in the keep studios for cute conversation. Thanks for watching

[Announcer] Live, from Las Vegas, it's theCube. Covering VMworld 2018, brought to you by VMware and its ecosystem partners. >> Welcome back, we're in Las Vegas and you're watching theCube. My cohost is John Trayor, I'm Stu Miniman, happy to welcome back to the program, Bob Madaio. >> Thanks Stu, I'm so glad to be here. >> Alright, so Bob, you're the Vice President of Infrastructure Solutions Marketing, and big difference, last year, you were with, was it, HDS? >> I was with Hitachi Data Systems. >> And now it's Hitachi Vantara and you had a little less facial hair when I talked to you last. >> You know it was around about November, I said, I might do theCube again next year, so I need to look different. >> Yeah, I had a, I had one Cube guy this year, he had got like almost a mountain man beard. And the week before he shaved it because he was coming back on theCube. And he was like, yeah I didn't but beards, no beards, diversity is what we like on theCube. >> Got to make the videos look different right? So next year I'll be beardless again, we'll do it again. It'll be fun. >> Alright, so I guess the follicle discussion's interesting but the Hitachi story is an interesting one you know Hitachi of course, huge company, lot of different technologies there, but bring us up to speed with what came together with Hitachi Vantara. >> Sure for a reminder of what we did, so we were Hitachi Data Systems, that's a part of the company I was with and again Hitachi Limited, out of Japan very large, you know, over 80 billion dollar organization of which Hitachi Data Systems used to be the IT arm that took those solutions to market around the world. What we did is, many might remember we had purchased Pentaho the open source analytics, you know, great a ETL blending capability. We brought them into the family with Hitachi Data Systems. We also had a sister company that was called Hitachi Insight Group. Hitachi Insight Group was really there to kick start our efforts around IoT. And if you've heard us talk about our Lumada Platform, if you look at what strings all this together, we've been having a lot, and I'm sure we'll talk about it here, of conversations about data. How do we help our customers with data? You know of course we've had a history in storage, but how do we bring it together, analyze it, bring new things, make that infrastructure more flexible? So that was what Vantara was. It was the bringing together of those three entities, and we continue to add. So, we're doing more and going to bring more companies into the fold. >> I love that Bob. I mean, we know the trend we've been watching for quite a number of years is, IT is going from that cost center over on the side that said, "No" to, to survive, you'd better be responding to the business, tie closely to the business or the business will go elsewhere. >> Yes indeed. >> For those solutions. And in the same way storage can't just be some growing expense that, you know, is I can't manage it I can't do this, to data is the life blood of business today. >> You know it's, I get to see some customers, not always as many as I'd like, but work closely with our field. And I was at this great customer of ours who's a regional bank and I was talking to, it was fundamentally a very storage-y audience. And I was, let's be honest, I was the corporate guy, I was a bit of the appetizer before the technical team, and I was having a data conversation. And we have this thing that, maybe we'll talk about, we call it the stairway of value and how customers should think of their value getting, you know, more important and how they can help, IT can help expose that value. And I was going through this model and I was worried, man, I might be losing this audience. But the lead person was writing, and I kind of stopped and said, is this relevant to you guys? And he said you know, I'm presenting on data to the organization next week, and I'm taking notes. And so what we're seeing is storage people, they also want to be able to have this conversation. How can what we do to make storage more accessible, move that data more quickly, valuable to the organization, to your point. >> Stairway to value, that's the power ballad for IT of the future, right? >> It does have a nearly built-in theme song, although we haven't gone there yet. For us actually, what it is is, we talk about the base layer sort of storing and protecting, and then it's enriching the data. So if you think of, often that's a meta data conversation. How do we bring more value, explain that data, make it easier to use? Then we get up into activate. That's blending maybe. You have the static systems. You want to build a repository for analytics. How do we help you activate that? And that really puts you on the path for monetization and that's the M. So we call it our SEAM model. >> So Bob, I love Hitachi Vantara and the idea of it. I got to say I understood Hitachi Data Systems better, because it's a storage, it was a you know, very, very smart, super smart storage company and you could compare it to other storage companies. But now, I'm just curious, in your, as you go and talk to customers, does that change who you talk with? And because, Hitachi Vantara as part of Hitachi too is about the industrialization of, of data and everything from oil fields and all the way down to, you know, a box in my office that might store my data. So, you know, but you've got the open source crowd and data scientists, you've got all the industrial and medical and health care stuff. As well as still these super smart storage scientists there. So how do you start that conversation and who do you end up talking with? >> You know it's very interesting. I mean, there are some companies that we approach at a Hitachi level and they're going to be major manufacturing projects or government projects, and we can bring the whole set. But oftentimes we are leveraging where a customer knows us and branching into new areas. So the storage base that we have is the most obvious to leverage. But what we're doing now is things like, we have some IT automation and analytics tools that help our customers know what's going on with the systems in their environment and how to take processes out. Well we can bring Pentaho in and tie in non-storage systems, non-IT systems like security, power and cooling, and really give a whole new dashboard. So that's a new entrance. And then the IT team can be an advocate to help you meet new business people. We also go in and speak to the business of course. We can do that through, we have IT governance go to markets, and data analytics go to market motion. And we're beginning to blend those better and better, but to be fair there are still some silos in how we talk to the customer depending on the audience. But what we see is if we can use data as a bridge, that's when the audiences sometimes meet each other, you know, for the first time it seems. >> Alright, so I love some of where this is going. Let's think down a level. You do the infrastructure solutions group, >> I do, yeah. >> So when you talk about, you know, CI and HCI and all those pieces. We're talking multi-cloud, a lot of this stuff, you know, what's the latest? What are the conversations you're having with customers about that? >> Yeah, very good. And really for us it's all been about agility. You know, data agility sure, but you can't make your data agile if you're infrastructure is very, you know, static. And so it doesn't take much to convince a customer we can build them trusted storage. That's like telling them the sky is blue, if they know Hitachi, they know this. What our conversations are now is about, what about the rest of your applications that surround this? On that trusted storage, how do we cloud enable it? What can we do there? On HCI and converge, obviously here at VMware, we partner deeply with VMware, so we are working with, for instance, how do we run some of our applications in the AWS VMware cloud, as well as be that HCI or that rack scale system on-site that manages it? So we're really having this agility conversation. How do we build the systems to be ready for this onslaught of data? Because it's great to have an IoT conversation, which remains of interest, but the reality is the systems folks need to be ready for that wave that's coming at them, and current process of just, I'm going to add controllers, I mean, that's not the way to think about it anymore. There's new types of systems that are making customer lives easier. >> Right, so from the VMware standpoint, I believe on-site is part of the partnership. >> Yeah, yeah, yeah. >> Anything in particular VMware specific. >> Yeah, across the portfolio. So of course on the storage we work with Vwalls and we do all the protection and integration with SRM and the like but, but really what's of course, hot, is hyper converge and we have our unified compute platform, HC line, that is based on Vsan. And that's doing very well. We actually had a session here with some great customers. So both Kanagra brands and MCL told their stories of picking Hitachi and they've seen some great results. So that business is doing very well. We've also introduced what we call unified compute platform RS for the rack-scale infrastructure. And we do a number of things with that. So we'll do bare metal systems for, you know, analytics workloads, but what's really got people excited is we sell a complete package with VMware cloud foundation. And that gets customers, not only ready to get up6 to hybrid cloud quickly on-site, but really have that hybrid ability. And so we're beginning to do things like certify core applications so they can test. We have a tech preview out on our Hitachi content platform, Object Store, it's actually in the app store for VMware's AWS cloud. Now, it's a tech preview from us because we know it works, but there's a scale thing. And you know Hitachi, right? It's going to work perfectly before we let our customers go crazy. So, we're really getting into those hybrid conversations and also enabling it as a service. I don't know if we talked about the as-a-service cloud that we have on offer too. >> But, no, please do, yeah. >> On top of all that technology, one of the hot offerings we have is called Hitachi Enterprise Cloud. And we have a VMware based offering, which has been doing very well and a much newer container-based platform. So on the VMware offering, really it's all of the VMware tools, but a customer never touches any of it. They don't touch our storage, the servers. It is an as-a-service model that we come in with services, help them bring in their applications, help build the service catalog for that customer and really, all they do is consume the service. So while the hardware might be on-site, it's really, they're largely indifferent to it. We do all the underlying capabilities, upgrades and such and they just provide out services to the business. So it's a really great option that people don't even know we offer. >> Yeah, well absolutely. You've had a number of conversations here at the show, it's, the customers have, the companies that have decades of appearance, you start with that base level of trust and therefore, you can help customers. You might not be the bleeding edge, but when you're there, customers know, oh wait, you're going to be around. I know that this thing's baked and ready when we get there. >> You know, the bleeding edge is fun, and there maybe some things we do, but I think it's fair enough that maybe that isn't always us. But I, but I think I have heard us called the adults in the room from time to time. And over at the booth we hear a lot of these. You know, we've been playing with this but it's going to get real. What do you guys do in this space? And while it is maybe some fun marketing being that bleeding edge, it is great to know that when it really matters, customers always trust us. And that's a huge vote of confidence. >> Alright, yep, Bob, really appreciate the update there. Absolutely, technologies like IoT, rapidly go from, this is super early but I need things we can trust. So absolutely, congrats on the progress. >> Thank you. >> We look forward to seeing, you know, how Hitachi and you know, the beard look next time we see you. >> Look forward to it. >> For John Troyer, I'm Stu Miniman. Back with more coverage from VMworld 2018 soon. Thanks for watching theCube.

(upbeat music) >> Live from Orlando, Florida it's theCube, covering Cisco Live 2018. Brought to you by Cisco, NetApp, and theCube's Ecosystem partners. >> Hello everyone and welcome back. It's theCube's exclusive coverage here in Orlando, Florida for Cisco Live 2018. It's day three of three days of live coverage. Go to thecube.net, siliconANGLE.com, to get all of the stories. And of course, I'm here with Stu Miniman, analyst at Wikibon, my co-host for the week. Our next guest is Gary Harrison, Head of Technology Services, Metsi Technologies, welcome to theCube. Thanks for joining us. >> Thank you guys, it's good to be here. >> So, you're in the Cisco Ecosystem, so Stu and I have been talking about this all week. A couple of big trends: open, Cisco's opening up, you've got DevNet success with developers. Cloud is a new architecture, okay. Intent driven architectures are huge. Sounds like outcomes to me, so I hear a lot of these conversations about "what's the outcome?", and then building a technology. So I wanted to get your thoughts on that, from your perspective, what does that mean to you? When you hear that, intent networking, developer community, it sounds a lot like a different Cisco. >> It's a different model. It's changing, I think, the way business processors are today, and getting organizations to understand the process of capturing what they want the infrastructure intent, and their application intent look like. And then understanding how that drives different models for deploying services, as well as the operations behind it. >> You guys do a lot of stuff with customer, I want you to take a minute to explain what you guys do, your company. What are some of the things you guys get involved in? Where are you in the ecosystem? What kinds of projects are you engaging on? >> We're a company, so we're a professional services partner, we're a service only integration partner with Cisco. So it's just through, we don't resell, so we get to focus on purely customer success, and we help enable the channel and the partners directly. And the focus is the Enterprise Cloud Suite. So it's really around helping customers understand how to get the most out of those technologies, how to choose the right element of the cloud suite for the job. >> Gary, so you're in an interesting position, to watch some of the transformations going on in Cisco. We said the old way of measuring Cisco was boxes and ports, and the new way is, you know, software, to open and those things. Since you're not one of the, you know, not in a derogatory way, box sellers, you know, give us your viewpoint as to how Cisco's going through that transformation and how your customers are reacting to that. >> So it's definitely a good shift towards those softer elements of it. And we're seeing the strength of the software and the products that come out, and the capabilities, it's rapidly changing. And you're seeing the increase in the product suite recently, the number of, the move towards analytics and other software to support operational life cycles as well as just the provisioning cycles. I think a challenge for the customers is a lot of complexities introduced. A lot of the new tools out of the box out there. And the difficult question is always how to best use each particular tool to get value for the business. >> Yeah, it's one of the big questions is it used to be, I really understood my network because I built it. I racked it, stacked it, wired it, you know. Configured it in the CLI, today a lot of the pieces of the network you're managing, you don't own. They're in the cloud, they're extending beyond. How do your services and solutions help customers get their arms around this, kind of, multi-cloud world? >> It's always the focus on, I guess, is reducing that complexity. There's a lot you can do with the different software that's out there. And really, to try and step back from just the solo tools, and looking at the cloud stack as a whole, and starting small, starting simple. Identifying those early use cases that will help drive cloud adoption in an organization, and then understanding how the software and the tools benefit them to do that. You know as you say, you can't see inside the software easily. If you're going to bare the infrastructures code, you need a way to make sure that as you build that code and those processors that you keep that visibility into what that softwares meant to be doing for you. >> Gary, on that point, I want to just double down on that concept holistically. We hear that, all week we've heard from interviews, from Cisco executives as customers, that it's the systems view almost, it's not the box view. What does that mean to the customer today, and how far along are your customers in that mindset? Are they there, are they kicking the tires? 'Cause you got to engage on real frontline projects where there's outcomes involved and the plumbing's in place. Okay, so how do you get there without disrupting? Right, that's the question we hear. But so how do I get the holistic view without disrupting the business? What's your thoughts on customer's position on that? >> I think to get the holistic view, it's about the business needs I think embrace that. And understanding, though, it's about delivering applications and services now. And the infrastructures there to support that. And not focus on these infrastructure-centric models. So that's the first journey, is understanding, you know, what are the services that are important to the business, and how those services are involved. And then I think the challenge we see from the customers is actually, you know, intend to your organizational and process challenges. The technology itself is not necessarily all the complexities, it's how that aligns to the organization. And so I think those early wins and those early outcomes are a organization that's aware of those challenges. >> Like almost getting a little stepping stone, you get a little success, you know, don't take a big project. What's your take on road-mapping in that? Because that's challenging. What have you seen for success use cases that customers can take right out of the gate to get this intent thing going? What are some of the low-hanging-fruit opportunities? >> So one thing we focus on, I guess, is changing our engagement model with the customers. It's something we sort, I guess, of pride ourselves on. Is we're a lot more flexible and agile, ourselves, as a, in terms of delivering infrastructure services. So again, we try to communicate to our customers find used cases that deliver value and return on investment early. And focus on delivering that, sort of, one use case. It doesn't matter what it is in the cloud-sect, whether it's through automation of network infrastructure, orchestration of services on top of there. We pick a very clear use case and develop that first, and then once you understand how the technology's stitched together end to end, you can then start to grow that inside the organization. >> Is there any use cases that pop out that you can just point to, anecdotally, that seem to be popular? >> So there's a couple different extremes, so ACI is a massive enabler at the moment. You know, it's really, since SDN's come along it's a catalyst to drive the rest of the cloud change infrastructure. So we have some very specific use cases around automating that infrastructure. Not just what ACI does itself, but to create that automation layer on top of that. So, you know, people are deploying lots of infrastructure, so that's one of the specific use cases we see. >> Gary, I really like what you said about it's changing the engagement model, because it used to be "I'm gonna' roll out a new application, "okay, I need to figure out the plumbing." Now when I look at intent based offerings there, it's really more about I'm building new applications and the network is a critical piece of it, it actually helps me drive some of these new, you know, modern micro architectures there. You've got to, I'm sure, be talking to a little bit of a broader, you know, jobs inside the customer. How does that change your engagement? Who are the roles that you're talking to today? >> Well actually this is what we find, is tools like Cloud Sender, and for me one of it's strengths is it's fine ability to tangibly capture intent in a application blueprint. And I find that's a good way to bring organizations together, because now we have a focal point for your network and infrastructure, your platforms teams, and your application teams to come together. And it provides a common language to talk about it. And that's one of the real strengths we find to start having those conversations with those different teams within the organizations. >> Gary talk about the old way and new way. We always like to kind of break things down in a very simplistic way. And Chuck Robbins, the CEO, on stage said "that's the old way", it looked like an architecture, hey, firewall, I get that. And he's like, some people actually have this today. And he's kind of looking at the modern cloud, obviously the circle with all the different services. So kind of Cisco plug. But from your standpoint, when you talk to customers, what was the older conversations, that you could point to saying "we used to do it this way", this is what we would talk about, these are the meetings we would have, now the shift is towards this. What's the old way, and what's it transforming into, when you actually have those conversations, what is it like? >> So the big difference for the infrastructure projects, where they were projects, they're very traditional waterfall model. You work out what you want to buy, where you want to be, you put a project plan around that and deliver that. But the engagement we have today to say to people, all the importance is in the software. It's the services you're delivering on the software, and the capability to develop in the software. And that's not something out of the box. It's very difficult to say: where do I want to be in six months, or where do I want to be in a year? So again the way we encourage and the way we engage with our customers is to put a roadmap together, but to identify something in a much shorter term that you can deliver. Start delivering something, and then take a more agile approach around it, to come back, review, and re-plan again, and look at what your priorities are. >> What's the role of the solution architect on this, 'cause a lot of the things we're seeing and then we're trying to, kind of, connect the dots here. Holistic roadmaps are interesting, because you've got have to have a foundational architecture. What is the preferred kind of consistent theme you're seeing around architectural decisions? Are there table stakes, are there certain things that are always going to be in flux? How do you view the big picture on the solution architect piece of it? Is there certain things that are must-haves, weight on this? What's your reaction to that? >> I think a solution, I think it's a challenging piece. I think it's probably where you see organizations are probably weaker, is having a cloud-solution architecture function. We still see infrastructure architecture, enterprise architecture, but that solution architecture for the cloud model, I think that's actually more a challenging piece. I don't think there's any obvious answer in what, you know, for the customers we see, there's no common answer. >> That's a really hot area right now. >> Gary, one of the biggest challenges we see in multi-cloud, is no two customers are alike. >> No. >> But through the customers that you're talking to, what are some of the common stumbling blocks or hurdles for really getting, you know, full value out of their solutions that you see from customers today? >> I think it's understanding the end to end life cycle of a service. So we can do a lot with a multi-cloud capabilities, in deploying when an internal infrastructure to external. But the processes have to be the same, with security, compliance, these other aspects that come into it add a lot of complexity. And also it's not just the way the applications and the infrastructure are built, patching life cycles, you know, post-deployment of, you know, virtual images. The way people then update and maintain them and that life cycle around it. And I think it's different in a virtualized world, in a containerized world we see a lot more advancements around it, and multi-cloud is easier. I think it's for people to take their legacy applications and try and move them into a cloud-native scenario, which is a real challenge. >> Gary, pretend that I'm a friend of yours and I come to you and say "hey Gary, you know, "I'm new to this whole intent-based networking thing, what is it?", how would you describe it? What's your definition of, what is intent based networking really mean? >> There's two parts of it: one is to identify somewhere to capture what the definition of your applications and services are, and what that means, and the infrastructure that lies underneath. Say cloud centers one part of it, other organizations may have other models, but it's rather than working two traditional high level design, low level design, and we see your requirements analysis, now capturing that intent in somewhere that's both software consumable and can be software defined. You can use software to push intent in there, and you can consume it through software. And the next major bit of the puzzle is to provide that freedom to the infrastructure layers underneath so they get to decide how they implement that intent. And that's what gives you this multi-cloud freedom, you know, how we're implemented in our public cloud can be different to how we're implemented in the private cloud. The tools, the processes, the infrastructure, the software, can be different, but the outcome that's delivered is the same. >> Yeah it's interesting to show, you mentioned SDN earlier, we see a lot of activity on software defined data center, architectural things, and again, it's challenging because not everything looks the same, but it's super important. But then we hear things like Google Cloud on stage, and we hear Kubernetes, we hear ISTIO, which is a service mesh, so you start to see up the stack, the applications taking, kind of, almost a network services-like mindset. I mean, micro services are basically, have the same feel as networking, but it's more up higher in the stacks. So you've got some really interesting dynamics. You've got the SDN thing going on, and then you've got in the middle of the stack, towards the application, these cool Micro services with cloud native. This is an opportunity for network engineers. I mean, how would you describe to the audience out there the opportunity for a network engineer, or someone who's in the network game, to take advantage of that, this new trend that's coming very fast? >> It's a different model of networking. And again, the good thing about containers is they do provide this very application-centric focus. Networking is now about providing a service for the application sit on there. And Container Frameworks make that very obvious. So I'd say network engineer, it's a good place to understand that model and that ecosystem. And then see how that can be applied to what we've done in virtualization. And as SDN comes along in a more traditional private cloud infrastructure, on top of the data center infrastructure we have today, take some of those models that we learned from things like Container Frameworks and how do we apply them to virtualization. >> That's a great point about the virtualization, it's almost a roadmap to how to understand the impact and interplay between the networks. It really is. Okay final question for you is, you know, Cisco Live this year seems to be different, what's the vibe of the show, what's your, if you had to, for someone who didn't come here that's watching, say "hey, I missed it this year, "heard there's a lot of action, DevNet's got 500,000 developers", what's different about this year for Cisco Live, what's the most important story? Can you share your opinion on what's happening? >> I guess for us, being the definite village, it is about the definite zone. The buzz we're seeing, the people, the types of questions we get asked on the stand now, there's definitely a lot more interest in this development side of it. >> What's some of the questions you're getting? What are the hot topics if you stack ranked them? >> People just want to understand, you know, new trends in software, coding, you know, how can I apply my coding skills to coding the network, or where do I learn about that, and we get asked lots of questions as people pass the stands. >> Gary, thanks so much for coming on theCube, great to see you, thanks for coming on and sharing your commentary here. Appreciate it. >> Thank you very much. >> Alright, this is the live Cube cover day three here at Cisco live, I'm John Furrier, Stu Miniman, we're here breaking all the action down, we'll be back with more. Stay with us for day three coverage. We'll be right back after this short break. (upbeat music)

(uplifting music) >> Hi, I'm Stu Miniman and this is a CUBEConversation at SiliconANGLE's, Palo Alto studio, happy to welcome to the program, a first time guest and and new to Nutanix, the Chief Marketing Officer, Ben Gibson. Ben, thank you so much for joining us. >> Stu thanks for having me here. I love the studio and love the chance to chat with you. >> Alright, so our audience know Nutanix really well, so let's introduce them to you first of all. Give our audience a little bit about your background and, you know, we know Nutanix IPO'd not that long ago. Exciting. Growing real fast so, you know, I'm sure it makes sense but why for Ben? >> Yeah. For me, firs and foremost, it's such an exciting company. We're going through a lot of fairly strong growth right now. We've really created a category in the Space Realm Hyperconvergence and now we're really expanding from that position and to be in the middle of that, I think is really exciting. >> So your background is mostly in the networking space and it's one of those things, I'm a networking guy by background. >> Yeah. >> Networking is changing a lot, lately, but not nearly as fast as some of the other parts so, you know, tell us a little bit about your background, where you've been, what your skillset is going to bring to Nutanix, in that ecosystem. >> Yeah, you know, I did, like you, I hailed from the networking industry. I spent a good portion of my career at Sisco, I spent part of my career at Aruba Networks, which is in the Wi-Fi, wireless space, but I think you're right. I think the acceleration of innovation in Nutanix's industry a lot of stuff has changed so quickly in that space, so networking hasn't quite kept up with that level of change of things and for me it's kind of getting on a much faster train and moving forward with it. >> Alright, so we've had theCUBE at every single one of the DotNext conferences >> Ben: Thank you. >> They're fun. Your predecessor Howard Ting had a certain flair so let's talk a little bit about the show and, you know are there things that your going to be putting your stamp on at this show, coming up in New Orleans? >> Yeah, I mean first of all it great to succeed Howard, in the role. I used to be an advisor for the company and so Howard and I used to have periodic pancake breakfasts and I told him what I thought and he shared with me a lot about how exciting things were. What was happening at Nutanix and how they really move forward. And I knew about DotNext, I've seen DotNext I know what an exciting show it is. For a company like Nutanix to draw, this year, over 5000, attendees to this show, that's notable. And, what, to me, that signals is the level of intensity and the level of loyalty that we enjoy in our customer base, they're believers and they're coming to the show to learn from us, to connect with each other and really to accelerate some of their plans on how they continue to innovate. >> Yeah, you know, we travel to so many different shows and absolutely, it is at it's core, it's a user conference, it's users there wanting to learn how to use what they have even better. Learn about the cool net technologies. Dave Valente and I have talked about Nutanix is up there with companies like Service Now, that have, just, people that come and are just, you know, kind of fanatically supported. It reminds me of, you know, Vmware's a great company, doing well today. Many years ago everybody had the I love VMware bumper stickers. Vmware is a great show. We'll be there this year >> Ben: Yeah, so will we. >> And your company will too, so ah, what, what do people what brings them to that show from your standpoint and give us a little insight as to, kind of, some of the special things they'll be seeing this year in New Orleans. >> Yeah, you know, I think one of the biggest attractions of coming to this show is if you think about the role of an infrastructure professional, someone who's looking at hybrid Cloud environments and how do you manage those. Thinking about what applications run on what cloud platform. There's a lot of change and fluidity to that and I think the nature or the role of an IT or an Infrastructure professional is changing. Server Store J-Admin is quickly evolving because that's converging, just like the technology has and so, for me this show is about how do you get ahead of those trends. How do you position yourself to be as strategic as possible, within your own organization? And that's the way I like to think of Dotnext, it's a place that a professional can come to learn and to grow their career and their technology expertise. >> Yeah it's a great point, one of the things I've loved on theCUBE is there are speakers that aren't just from the tech industry, so everyone from Deepak Malhotra, who is from Harvard, um, thought leaders in the space to onstage at one of the shows it was David Blaine doing a magic trick while one of your engineers was configuring stuff. So there's some great speakers that'll be at the event this year to, not only learn the tech but as you said, you're thinking about the persons career and how do they embrace change and how do they help become more valuable to their company. >> Yeah, you know, there's two in particular that are going to be joining this year that I'm very excited about. One is Dr. Brene Brown. If you haven't seen her TED talk on YouTube I highly recommend you go and check it out. It's something different. It's about how do you be vulnerable, with yourself, with your career. How do you take chances? How do you take risk, and that's a lot of what's going on in our in our industry right now. The second one I think is going to be really fun and that's Anthony Bourdain. Known for his show, Parts Unknown and he's going to have colorful language, right, noted, some colorful language but also he's just a riot. He's the one I think is going to bring his special kind of flair to the show and get everyone really excited, laughing and maybe a little bit of gasping, in terms of what he's going to be sharing with us. >> Yeah, absolutely I mean, New Orleans is a great culinary destination and so I know everybody that's going there you'll want to check out the music, the culture and a lot going in there. So, excited about the show. We're going to have theCUBE there for two days. Last thing I want to talk to you about, Ben, just, Nutanix as a company, when I registered for the show there was one of the questions I thought was pretty interesting. They said, "What do you think Nutanix is?" You know, how do you, what's your relationship with Nutanix? And I'm trying to remember, I know one of the options was M: Is Nutanix a hypercovergence infrastructure player? Are they a cloud player? I think storage might even be in there, it's been one of those things as to, who is Nutanix? What are you today and what do you want to be in the next phase of growth? >> You know, it's a great question Stu, "Who is Nutanix?" We are focused on helping our customers build their enterprise cloud. Our taglines could be Your Enterprise Cloud. Enterprise Cloud is not only how you modernize your own data center but it's also, how do you embrace? How do you have a strategy? How do you govern? How do you bring together the right workload, for the right cloud platform at the right time? And that's the direction we're taking with our innovation. This is what more and more of our customers are looking to do. Not every application's going to a public cloud provider. Not every application is staying on premise. We're going to be living in the hybrid world, Enterprise Cloud is about how do you take the ingredients of hyperconvergent infrastructure? Take the ingredients for automation and management, over these different workloads, across these different environments and do so in a way that makes the complexity of infrastructure and multiple cloud management and make that all invisible. So for us that's our mission. It's building that Enterprise Cloud and making all that complexity go away. And that's the vision we're going to be talking about and that's what we think our attendees are really looking to get the guidance and, kind of the vision of how they move their careers forward and flourish in that space >> Ben, it's the barometer that I've been using for probably the last two years. If I spend a lot more time in kind of the Dev/Op Cloud native, you know, worlds these days. We were at an Amazon summit yesterday but, absolutely. It's heterogeneous world. IT has never, you know, let's throw out the old and start the new. Sure there's some new companies that might do that but it's a heterogeneous world, it's a multi-cloud world and big struggle for people is how do they get their arms around it? So if I look at a company that has started mostly on premises, it's like, oh how are you evolving? How are you working with the public Cloud? You know, Nutanix has been working very closely with Google over the last year or so. A new acquisition recently that I know plays into this whole story. Tell us a little bit about the acquisition and, you know, how does Nutanix look at itself, which is now, I mean, if you read the Wall Street reports, Nutanix is a software company. And you're getting great multiples on that and it's helping and you know I've been pretty vocal on this from it's early days, is Nutanix was never a hardware company. It, you know, building an appliance was a go to market choice to simplify and make it easy for customers but as the company matured, >> Yep. >> It made a lot more options and today it makes perfect sense that really software is where it goes, so you talked about a bunch of things there but specifically, kind of the multi-cloud and the acquisition first. >> You know Stu, we're really excited about this recent acquisition we made. It's a company called Minjar and the offering is essentially it's going to be integrated into our broader software platform, that allows customers to be able to assess on a realtime basis. What's the right Cloud platform for a particular workload from a costing perspective? From reliability standpoint. Derish talks about the law of the land. The laws of physics and the like, you need to apply these all to determine what you're going to run where. And what we got with this Minjar acquisition, is a really sophisticated way that our customers can embrace and is part of their enterprise cloud. Because part of this is taking back control over all this disaggregation of workloads running everywhere. You're losing control. Losing governance of your data and your applications if you don't really keep on top of it, this acquisition, I believe, is going to be a really key part of helping IT organizations regain that control. Yet still enjoy all the benefits of hybrid-cloud environments. Whether it be with an AWS an Azure a Google Cloud platform, like we're partnering very closely with, as well as what they're building with their Enterprise Cloud on premise. Whether it be, you know, with Nutanix. >> Yeah, it reminds me of, was it Progressive Insurance, I think has the, you know >> Yeah. >> We're going to give you quote on all of the things there. Cloud is complicated these days. Is there bias towards it, pushing towards, you know, Nutanix closer partners in the technology itself. >> Yeah, I mean it certainly has. There's a lot of complexity around that and to me the industry hasn't solved a lot of new complexity that has come out of the emerging trend of a different line of businesses starting to develop a new application now, on a certain Cloud platform and the like. And as you're seeing this demand for more application mobility between clouds, so all of a sudden the partners that are coming to us and the partners we're seeing and are demanded of that we work with in the market our players are looking at application automation. Players that are looking at dev/ops tools and the like and it both guides how we innovate on our Calm platform, which we introduced last year at DotNext as well it helps us expand our reach. So, we talked to our traditional buyers but there's a lot of new buyers now that are building those apps and managing those environments and we're going to start to see some of those come into the DotNext show. >> Alright. Ben I want to give you the final word. DotNext is one of the many events that I know you do lots of regional shows and the like, what should we expect to see from Nutanix through 2018? >> Yeah, you know the first thing is that the dialogue, the narrative for the company, that we're going out with we've moved to be a software only company and I think our customers tell us and I heard this from one of our largest retail industry customers just a few weeks ago, by moving to a software only model, it's given them freedom to take advantage of Nutanix, regardless of their hardware platforms. And like you said we've never been a hardware company, it's all been about software value and what you're going to see from us is a new narrative. An expansion of the branded Nutanix talking about the freedom we give for customers to build the data center they've always wanted to build. Freedom to run their application or the workload that they've wanted to run, where they choose to run it based on that insight I talked about. And in another realm, the freedom to play. Freedom to get their weekends back. A lot of our value proposition is because of all the complexity we've taken out of the equation, is that we give our customers their weekends back. This is a story that our DotNext attendees, I think, know better than other but we want to spread the word and so part of that is harnessing that freedom concept to build, to run, to play to invent and tell the world. And DotNext, whether is be in New Orleans, which I think is going to be a blast. When we take it to Europe, London and we do this all around the world, to me that's kind of ground zero for that story. For the community of what we've built together with our customers and partners and that what we take out to the world. >> Alright, well Ben Gibson, I'm glad we could introduce you to our community today because we're going to be seeing you at lots of other events, you and your team, of course, theCUBE will be at Nutanix, DotNext in New Orleans. Nutanix and you will be at Dell Technologies World in Las Vegas. Google Cloud Next happening this summer in San Fransisco. Lots of other shows so be sure to tune in to theCUBE.net, get the list of all the upcoming shows, Ben, Nutanix and of course lots of the Cloud and infrastructure ecosystem. Check it all out. I'm Stu Miniman and thanks for watching theCUBE. (uplifting music)

>> Hi, I'm Peter Buris of Wikibon, and this week, we're going to be running a very special teleconference on true private cloud. The Technology Foundation for Enterprise Cloud Strategies. We're going to conduct the teleconference on Thursday, the 12th of October, at 2 p.m. Eastern Daylight, and 11 a.m. Pacific Daylight. What we're going to do is reveal some new research that we've been doing that supports this whole notion that increasingly, the marketplace is going to adopt what we call true private cloud technologies. These are technologies that are intended to provide the cloud experience wherever the data demands, including on presence, including at the edge, and will be easily integratable with the public cloud. Now, when we talk about new research, we're not just talking about the numbers that we've been put forward over the last couple of years. We're actually talking about new and interesting things. So, for example, one of the key things we're going to look at is what's going on in the world of backup and restore. How are we going to handle this need to manage large amounts of data. Dave Vellante, tell us a little about that. >> Dave: Yeah, so one of the things most I'm excited about, Peter, is working with our community, trying to help them understand how this cloud model is evolving, in SAS, obviously driven by applications, public infrastructure is a service in what we call true private cloud, bringing the cloud model to your data on prem, and one of the areas we're looking at is new data protection models. How do you protect data across multiclouds? Are there ways to get more leverage out of that data beyond just insurance and backup? Are there ways to help with governance and data analytics and other dealings with security threats? We see data protection as one of these key binding technologies that are going to bring together cross cloud disciplines. >> When we think about cross cloud disciplines, you always end up thinking about what are developers going to do, and Stu, we've been pretty hard at work at thinking about the impact of hybrid cloud, and some of the new models of development as we go to a more distributed, more multi-ownership orientation of some of these assets. Any quick observations on what we're going to see next week? >> Stu: Yeah, absolutely, Peter. The whole premise that we've talked about with true private cloud is people love the operating model of the public cloud, and nobody more than developers. The developers have been sitting up, building shipping code in the public cloud, so how can I get that same experience really wherever I'm going to live? So whether that be my data center, the public cloud, or even going to edge configurations now, all the kind of latest and greatest stuff like containers and Kubernetes and serverless is not going to all live in one place, so how does this span this hybrid multicloud world? It's super important to focus always on that application and that developer experience because without that, you're going to fail with really moving to this modern type of architecture. >> Now, as we think about the need for data protection, we think about the need for application development creating value out of this that has significant impacts ultimately on IT operations management. We're also going to be spending some time talking about how new technologies are being bought into the whole IT operations management sphere, machine learning, deep learning, cognitive, et cetera, to dramatically improve the productivity of managing all of these new more complex applications and distributive resources. So, that's going to be a crucial feature of what we'll be talking about at the teleconference, but David Floyer, we're also going to be talking about the impact of this trend on future systems design. We call it unigrid. What are we going to tell people? >> Well, one of the most exciting things is the new technologies that are coming in to the architecture, fundamental architecture of systems. Essentially, storage and networking are combining together to allow an any to any connection between lots and lots of nodes, not just the 16 or 32, up to thousands of nodes, to be able to access that data from any node, and do it at very, very low latencies, indeed. And the exciting thing that this is about is that this is the holy grail of what systems have been trying to do for many, many years. What the want to do is combine systems of record, which are database-heavy type applications, with systems of intelligence, AI systems, other systems of that sort, which can come in and add additional value. What is happening in this architecture is that you can get hundreds or thousands of times more data per unit of work, per transaction or whatever, and this is really, really exciting because we can, for the first time, do real time analytics at the same time, and into the same systems of the current systems, of systems of record. >> As we're writing transactions. >> David: As we're writing transactions. >> So this is unigrid. We think it's going to be a major feature of the industry, and have an enormous impact ultimately on how we think about designing this next wave of applications. All right. So, on Thursday, October 12th, special Wikibon teleconference. The Technology Foundation for Enterprise Hybrid Cloud Strategies. Two o'clock Eastern. 11 o'clock Pacific. The key Wikibon team coming together to talk about from the business objectives through software, data protection, systems management, and all the way out to future systems designs. Please join us. We hope to see you there.