(upbeat music) >> Hey everyone and welcome back to The Cube. We are covering VMware Explore live in San Francisco. This is our third day of wall to wall coverage. And John Furrier is here with me, Lisa Martin. We are excited to welcome two guests from Kasten by Veeam, please welcome Tom Laden, VP of marketing and Matt LeBlanc, not Joey from friends, Matt LeBlanc, the systems engineer from North America at Kasten by Veeam. Welcome guys, great to have you. >> Thank you. >> Thank you for having us. >> Tom-- >> Great, go ahead. >> Oh, I was going to say, Tom, talk to us about some of the key challenges customers are coming to you with. >> Key challenges that they have at this point is getting up to speed with Kubernetes. So everybody has it on their list. We want to do Kubernetes, but where are they going to start? Back when VMware came on the market, I was switching from Windows to Mac and I needed to run a Windows application on my Mac and someone told me, "Run a VM." Went to the internet, I downloaded it. And in a half hour I was done. That's not how it works with Kubernetes. So that's a bit of a challenge. >> I mean, Kubernetes, Lisa, remember the early days of The Cube Open Stack was kind of transitioning, Cloud was booming and then Kubernetes was the paper that became the thing that pulled everybody together. It's now de facto in my mind. So that's clear, but there's a lot of different versions of it and you hear VMware, they call it the dial tone. Usually, remember, Pat Gelter, it's a dial tone. Turns out that came from Kit Colbert or no, I think AJ kind of coined the term here, but it's since been there, it's been adopted by everyone. There's different versions. It's open source. AWS is involved. How do you guys look at the relationship with Kubernetes here and VMware Explore with Kubernetes and the customers because they have choices. They can go do it on their own. They can add a little bit with Lambda, Serverless. They can do more here. It's not easy. It's not as easy as people think it is. And then this is a skill gaps problem too. We're seeing a lot of these problems out there. What's your take? >> I'll let Matt talk to that. But what I want to say first is this is also the power of the cloud native ecosystem. The days are gone where companies were selecting one enterprise application and they were building their stack with that. Today they're building applications using dozens, if not hundreds of different components from different vendors or open source platforms. And that is really what creates opportunities for those cloud native developers. So maybe you want to... >> Yeah, we're seeing a lot of hybrid solutions out there. So it's not just choosing one vendor, AKS, EKS, or Tanzu. We're seeing all the above. I had a call this morning with a large healthcare provider and they have a hundred clusters and that's spread across AKS, EKS and GKE. So it is covering everything. Plus the need to have a on-prem solution manage it all. >> I got a stat, I got to share that I want to get your reactions and you can laugh or comment, whatever you want to say. Talk to big CSO, CXO, executive, big company, I won't say the name. We got a thousand developers, a hundred of them have heard of Kubernetes, okay. 10 have touched it and used it and one's good at it. And so his point is that there's a lot of Kubernetes need that people are getting aware. So it shows that there's more and more adoption around. You see a lot of managed services out there. So it's clear it's happening and I'm over exaggerating the ratio probably. But the point is the numbers kind of make sense as a thousand developers. You start to see people getting adoption to it. They're aware of the value, but being good at it is what we're hearing is one of those things. Can you guys share your reaction to that? Is that, I mean, it's hyperbole at some level, but it does point to the fact of adoption trends. You got to get good at it, you got to know how to use it. >> It's very accurate, actually. It's what we're seeing in the market. We've been doing some research of our own, and we have some interesting numbers that we're going to be sharing soon. Analysts don't have a whole lot of numbers these days. So where we're trying to run our own surveys to get a grasp of the market. One simple survey or research element that I've done myself is I used Google trends. And in Google trends, if you go back to 2004 and you compare VMware against Kubernetes, you get a very interesting graph. What you're going to see is that VMware, the adoption curve is practically complete and Kubernetes is clearly taking off. And the volume of searches for Kubernetes today is almost as big as VMware. So that's a big sign that this is starting to happen. But in this process, we have to get those companies to have all of their engineers to be up to speed on Kubernetes. And that's one of the community efforts that we're helping with. We built a website called learning.kasten.io We're going to rebrand it soon at CubeCon, so stay tuned, but we're offering hands on labs there for people to actually come learn Kubernetes with us. Because for us, the faster the adoption goes, the better for our business. >> I was just going to ask you about the learning. So there's a big focus here on educating customers to help dial down the complexity and really get them, these numbers up as John was mentioning. >> And we're really breaking it down to the very beginning. So at this point we have almost 10 labs as we call them up and they start really from install a Kubernetes Cluster and people really hands on are going to install a Kubernetes Cluster. They learn to build an application. They learn obviously to back up the application in the safest way. And then there is how to tune storage, how to implement security, and we're really building it up so that people can step by step in a hands on way learn Kubernetes. >> It's interesting, this VMware Explore, their first new name change, but VMWorld prior, big community, a lot of customers, loyal customers, but they're classic and they're foundational in enterprises and let's face it. Some of 'em aren't going to rip out VMware anytime soon because the workloads are running on it. So in Broadcom we'll have some good action to maybe increase prices or whatnot. So we'll see how that goes. But the personas here are definitely going cloud native. They did with Tanzu, was a great thing. Some stuff was coming off, the fruit's coming off the tree now, you're starting to see it. CNCF has been on this for a long, long time, CubeCon's coming up in Detroit. And so that's just always been great, 'cause you had the day zero event and you got all kinds of community activity, tons of developer action. So here they're talking, let's connect to the developer. There the developers are at CubeCon. So the personas are kind of connecting or overlapping. I'd love to get your thoughts, Matt on? >> So from the personnel that we're talking to, there really is a split between the traditional IT ops and a lot of the people that are here today at VMWare Explore, but we're also talking with the SREs and the dev ops folks. What really needs to happen is we need to get a little bit more experience, some more training and we need to get these two groups to really start to coordinate and work together 'cause you're basically moving from that traditional on-prem environment to a lot of these traditional workloads and the only way to get that experience is to get your hands dirty. >> Right. >> So how would you describe the persona specifically here versus say CubeCon? IT ops? >> Very, very different, well-- >> They still go ahead. Explain. >> Well, I mean, from this perspective, this is all about VMware and everything that they have to offer. So we're dealing with a lot of administrators from that regard. On the Kubernetes side, we have site reliability engineers and their goal is exactly as their title describes. They want to architect arch applications that are very resilient and reliable and it is a different way of working. >> I was on a Twitter spaces about SREs and dev ops and there was people saying their title's called dev ops. Like, no, no, you do dev ops, you don't really, you're not the dev ops person-- >> Right, right. >> But they become the dev ops person because you're the developer running operations. So it's been weird how dev ops been co-opted as a position. >> And that is really interesting. One person told me earlier when I started Kasten, we have this new persona. It's the dev ops person. That is the person that we're going after. But then talking to a few other people who were like, "They're not falling from space." It's people who used to do other jobs who now have a more dev ops approach to what they're doing. It's not a new-- >> And then the SRE conversation was in site, reliable engineer comes from Google, from one person managing multiple clusters to how that's evolved into being the dev ops. So it's been interesting and this is really the growth of scale, the 10X developer going to more of the cloud native, which is okay, you got to run ops and make the developer go faster. If you look at the stuff we've been covering on The Cube, the trends have been cloud native developers, which I call dev ops like developers. They want to go faster. They want self-service and they don't want to slow down. They don't want to deal with BS, which is go checking security code, wait for the ops team to do something. So data and security seem to be the new ops. Not so much IT ops 'cause that's now cloud. So how do you guys see that in, because Kubernetes is rationalizing this, certainly on the compute side, not so much on storage yet but it seems to be making things better in that grinding area between dev and these complicated ops areas like security data, where it's constantly changing. What do you think about that? >> Well there are still a lot of specialty folks in that area in regards to security operations. The whole idea is be able to script and automate as much as possible and not have to create a ticket to request a VM to be billed or an operating system or an application deployed. They're really empowered to automatically deploy those applications and keep them up. >> And that was the old dev ops role or person. That was what dev ops was called. So again, that is standard. I think at CubeCon, that is something that's expected. >> Yes. >> You would agree with that. >> Yeah. >> Okay. So now translating VM World, VMware Explore to CubeCon, what do you guys see as happening between now and then? Obviously got re:Invent right at the end in that first week of December coming. So that's going to be two major shows coming in now back to back that're going to be super interesting for this ecosystem. >> Quite frankly, if you compare the persona, maybe you have to step away from comparing the personas, but really compare the conversations that we're having. The conversations that you're having at a CubeCon are really deep dives. We will have people coming into our booth and taking 45 minutes, one hour of the time of the people who are supposed to do 10 minute demos because they're asking more and more questions 'cause they want to know every little detail, how things work. The conversations here are more like, why should I learn Kubernetes? Why should I start using Kubernetes? So it's really early day. Now, I'm not saying that in a bad way. This is really exciting 'cause when you hear CNCF say that 97% of enterprises are using Kubernetes, that's obviously that small part of their world. Those are their members. We now want to see that grow to the entire ecosystem, the larger ecosystem. >> Well, it's actually a great thing, actually. It's not a bad thing, but I will counter that by saying I am hearing the conversation here, you guys'll like this on the Veeam side, the other side of the Veeam, there's deep dives on ransomware and air gap and configuration errors on backup and recovery and it's all about Veeam on the other side. Those are the guys here talking deep dive on, making sure that they don't get screwed up on ransomware, not Kubernete, but they're going to Kub, but they're now leaning into Kubernetes. They're crossing into the new era because that's the apps'll end up writing the code for that. >> So the funny part is all of those concepts, ransomware and recovery, they're all, there are similar concepts in the world of Kubernetes and both on the Veeam side as well as the Kasten side, we are supporting a lot of those air gap solutions and providing a ransomware recovery solution and from a air gap perspective, there are a many use cases where you do need to live. It's not just the government entity, but we have customers that are cruise lines in Europe, for example, and they're disconnected. So they need to live in that disconnected world or military as well. >> Well, let's talk about the adoption of customers. I mean this is the customer side. What's accelerating their, what's the conversation with the customer at base, not just here but in the industry with Kubernetes, how would you guys categorize that? And how does that get accelerated? What's the customer situation? >> A big drive to Kubernetes is really about the automation, self-service and reliability. We're seeing the drive to and reduction of resources, being able to do more with less, right? This is ongoing the way it's always been. But I was talking to a large university in Western Canada and they're a huge Veeam customer worth 7000 VMs and three months ago, they said, "Over the next few years, we plan on moving all those workloads to Kubernetes." And the reason for it is really to reduce their workload, both from administration side, cost perspective as well as on-prem resources as well. So there's a lot of good business reasons to do that in addition to the technical reliability concerns. >> So what is those specific reasons? This is where now you start to see the rubber hit the road on acceleration. >> So I would say scale and flexibility that ecosystem, that opportunity to choose any application from that or any tool from that cloud native ecosystem is a big driver. I wanted to add to the adoption. Another area where I see a lot of interest is everything AI, machine learning. One example is also a customer coming from Veeam. We're seeing a lot of that and that's a great thing. It's an AI company that is doing software for automated driving. They decided that VMs alone were not going to be good enough for all of their workloads. And then for select workloads, the more scalable one where scalability was more of a topic, would move to Kubernetes. I think at this point they have like 20% of their workloads on Kubernetes and they're not planning to do away with VMs. VMs are always going to be there just like mainframes still exist. >> Yeah, oh yeah. They're accelerating actually. >> We're projecting over the next few years that we're going to go to a 50/50 and eventually lean towards more Kubernetes than VMs, but it was going to be a mix. >> Do you have a favorite customer example, Tom, that you think really articulates the value of what Kubernetes can deliver to customers where you guys are really coming in and help to demystify it? >> I would think SuperStereo is a really great example and you know the details about it. >> I love the SuperStereo story. They were a AWS customer and they're running OpenShift version three and they need to move to OpenShift version four. There is no upgrade in place. You have to migrate all your apps. Now SuperStereo is a large French IT firm. They have over 700 developers in their environment and it was by their estimation that this was going to take a few months to get that migration done. We're able to go in there and help them with the automation of that migration and Kasten was able to help them architect that migration and we did it in the course of a weekend with two people. >> A weekend? >> A weekend. >> That's a hackathon. I mean, that's not real come on. >> Compared to thousands of man hours and a few months not to mention since they were able to retire that old OpenShift cluster, the OpenShift three, they were able to stop paying Jeff Bezos for a couple of those months, which is tens of thousands of dollars per month. >> Don't tell anyone, keep that down low. You're going to get shot when you leave this place. No, seriously. This is why I think the multi-cloud hybrid is interesting because these kinds of examples are going to be more than less coming down the road. You're going to see, you're going to hear more of these stories than not hear them because what containerization now Kubernetes doing, what Dockers doing now and the role of containers not being such a land grab is allowing Kubernetes to be more versatile in its approach. So I got to ask you, you can almost apply that concept to agility, to other scenarios like spanning data across clouds. >> Yes, and that is what we're seeing. So the call I had this morning with a large insurance provider, you may have that insurance provider, healthcare provider, they're across three of the major hyperscalers clouds and they do that for reliability. Last year, AWS went down, I think three times in Q4 and to have a plan of being able to recover somewhere else, you can actually plan your, it's DR, it's a planned migration. You can do that in a few hours. >> It's interesting, just the sidebar here for a second. We had a couple chats earlier today. We had the influences on and all the super cloud conversations and trying to get more data to share with the audience across multiple areas. One of them was Amazon and that super, the hyper clouds like Amazon, as your Google and the rest are out there, Oracle, IBM and everyone else. There's almost a consensus that maybe there's time for some peace amongst the cloud vendors. Like, "Hey, you've already won." (Tom laughs) Everyone's won, now let's just like, we know where everyone is. Let's go peace time and everyone, then 'cause the relationship's not going to change between public cloud and the new world. So there's a consensus, like what does peace look like? I mean, first of all, the pie's getting bigger. You're seeing ecosystems forming around all the big new areas and that's good thing. That's the tides rise and the pie's getting bigger, there's bigger market out there now so people can share and share. >> I've never worked for any of these big players. So I would have to agree with you, but peace would not drive innovation. And in my heart is with tech innovation. I love it when vendors come up with new solutions that will make things better for customers and if that means that we're moving from on-prem to cloud and back to on-prem, I'm fine with that. >> What excites me is really having the flexibility of being able to choose any provider you want because you do have open standards, being cloud native in the world of Kubernetes. I've recently discovered that the Canadian federal government had mandated to their financial institutions that, "Yes, you may have started all of your on cloud presence in Azure, you need to have an option to be elsewhere." So it's not like-- >> Well, the sovereign cloud is one of those big initiatives, but also going back to Java, we heard another guest earlier, we were thinking about Java, right once ran anywhere, right? So you can't do that today in a cloud, but now with containers-- >> You can. >> Again, this is, again, this is the point that's happening. Explain. >> So when you have, Kubernetes is a strict standard and all of the applications are written to that. So whether you are deploying MongoDB or Postgres or Cassandra or any of the other cloud native apps, you can deploy them pretty much the same, whether they're in AKS, EKS or on Tanzu and it makes it much easier. The world became just a lot less for proprietary. >> So that's the story that everybody wants to hear. How does that happen in a way that is, doesn't stall the innovation and the developer growth 'cause the developers are driving a lot of change. I mean, for all the talk in the industry, the developers are doing pretty good right now. They've got a lot of open source, plentiful, open source growing like crazy. You got shifting left in the CICD pipeline. You got tools coming out with Kubernetes. Infrastructure has code is almost a 100% reality right now. So there's a lot of good things going on for developers. That's not an issue. The issue is just underneath. >> It's a skillset and that is really one of the biggest challenges I see in our deployments is a lack of experience. And it's not everyone. There are some folks that have been playing around for the last couple of years with it and they do have that experience, but there are many people that are still young at this. >> Okay, let's do, as we wrap up, let's do a lead into CubeCon, it's coming up and obviously re:Invent's right behind it. Lisa, we're going to have a lot of pre CubeCon interviews. We'll interview all the committee chairs, program chairs. We'll get the scoop on that, we do that every year. But while we got you guys here, let's do a little pre-pre-preview of CubeCon. What can we expect? What do you guys think is going to happen this year? What does CubeCon look? You guys our big sponsor of CubeCon. You guys do a great job there. Thanks for doing that. The community really recognizes that. But as Kubernetes comes in now for this year, you're looking at probably the what third year now that I would say Kubernetes has been on the front burner, where do you see it on the hockey stick growth? Have we kicked the curve yet? What's going to be the level of intensity for Kubernetes this year? How's that going to impact CubeCon in a way that people may or may not think it will? >> So I think first of all, CubeCon is going to be back at the level where it was before the pandemic, because the show, as many other shows, has been suffering from, I mean, virtual events are not like the in-person events. CubeCon LA was super exciting for all the vendors last year, but the attendees were not really there yet. Valencia was a huge bump already and I think Detroit, it's a very exciting city I heard. So it's going to be a blast and it's going to be a huge attendance, that's what I'm expecting. Second I can, so this is going to be my third personally, in-person CubeCon, comparing how vendors evolved between the previous two. There's going to be a lot of interesting stories from vendors, a lot of new innovation coming onto the market. And I think the conversations that we're going to be having will yet, again, be much more about live applications and people using Kubernetes in production rather than those at the first in-person CubeCon for me in LA where it was a lot about learning still, we're going to continue to help people learn 'cause it's really important for us but the exciting part about CubeCon is you're talking to people who are using Kubernetes in production and that's really cool. >> And users contributing projects too. >> Also. >> I mean Lyft is a poster child there and you've got a lot more. Of course you got the stealth recruiting going on there, Apple, all the big guys are there. They have a booth and no one's attending you like, "Oh come on." Matt, what's your take on CubeCon? Going in, what do you see? And obviously a lot of dynamic new projects. >> I'm going to see much, much deeper tech conversations. As experience increases, the more you learn, the more you realize you have to learn more. >> And the sharing's going to increase too. >> And the sharing, yeah. So I see a lot of deep conversations. It's no longer the, "Why do I need Kubernetes?" It's more, "How do I architect this for my solution or for my environment?" And yeah, I think there's a lot more depth involved and the size of CubeCon is going to be much larger than we've seen in the past. >> And to finish off what I think from the vendor's point of view, what we're going to see is a lot of applications that will be a lot more enterprise-ready because that is the part that was missing so far. It was a lot about the what's new and enabling Kubernetes. But now that adoption is going up, a lot of features for different components still need to be added to have them enterprise-ready. >> And what can the audience expect from you guys at CubeCon? Any teasers you can give us from a marketing perspective? >> Yes. We have a rebranding sitting ready for learning website. It's going to be bigger and better. So we're not no longer going to call it, learning.kasten.io but I'll be happy to come back with you guys and present a new name at CubeCon. >> All right. >> All right. That sounds like a deal. Guys, thank you so much for joining John and me breaking down all things Kubernetes, talking about customer adoption, the challenges, but also what you're doing to demystify it. We appreciate your insights and your time. >> Thank you so much. >> Thank you very much. >> Our pleasure. >> Thanks Matt. >> For our guests and John Furrier, I'm Lisa Martin. You've been watching The Cube's live coverage of VMware Explore 2022. Thanks for joining us. Stay safe. (gentle music)

>>Hey, welcome back everyone. Through the cubes coverage of VMware Explorer, 22, I'm John Fett, Dave ante, formerly world, our 12th year extracting the signal from the noise. A lot of great guests. It's very vibrant right here. The floor's great. The expo halls booming, the keynotes went great. We just had a keynote announce. So our next first guest here on day one is car Capor C co-founder and COO min IO. Welcome to the cube. Thanks for joining us. >>Thank you for having >>Me. You're also angel investor of variety of companies of Q alumnis and been in the valley for a long time. Thanks for coming on sharing. What's going on. So, first of all, obviously VMware still on the wave. They've always been relevant and they've always been part of it. Yes. But as that's changing a lot's going on security data's big conversation. Yeah. And now with their multi-cloud we call super cloud. But their multi-cloud it's it's about hyperscaler participation. Yes. Yes. Cloud universal. Yes. It's clear that VMware has to be successful in every cloud. Okay. And that's really important. And storage is one of it. You guys do that? So talk about how you guys relate with min IO, the vision, how that connects with what's happening here. >>Yeah. So like you already said, right? Most of the enterprises are become data enterprises in itself and storage is a foundation layer of how, and you do need a system that is simple, scalable, and high perform it at scale. Right? So that's where min IO fits into the picture. And we are software defined, open source. So, you know, like VMware has traditionally been focused on enterprise it, but that world is fast changing. They are making a move in terms, developer first approach and min IO, because it's open source. It's simple enough to start, get, start deploying object storage and cloud native applications on top. So that's where we come in. We have around 1.3 million DACA downloads a day. So we own the developer market overall. And that is where I feel the partnership with VMware as they are coming into multi-cloud on their own min IO is a foundational layer. >>So just to elaborate on it, whenever you talk about multi-cloud, there are two pieces to it. One is the compute side and one is on the storage side. So compute Kubernetes takes care of the compute sites. Once you containerize an application, you can deploy it any cloud, but the data has gravity and all the clouds that you see AWS, your Google cloud, they're inherently incompatible with each other. So you need a consistent storage layer with industry standard APIs that you can just deploy it around with your application without a single line of code change. So that's what we >>Do. Oh, so you got a great value proposition, love the story. So just kind of connect on something. So we heard the keynote today. We gotta win the developers. They didn't say that, but they said, they said that they have the ops lockdown, but DevOps is now the new developer. Yes. We've been covering a lot of the poop coupon as you know, and shifting left everyone's in the C I C D pipeline. So developers are driving all the action and it has to be self-service. Absolutely. It has to be high velocity. Can't be slow. Yes. Gotta be fast. So that sounds like you're winning that piece. >>Yes. Yes. And I think more than that, what is most important is it needs to be simple. It needs to get your job done in a very simple and efficient way. And I think that is very important to the developers overall. They don't like complex appliances or complex piece of software. They just want to get their job done and move on the next thing in order to build their application and deploy it successfully. So whatever you do, it needs to be very simple. And of course, you know, it needs to be feature rich and high performant and whatnot that comes with the, with the flow in itself. But I think simplicity is what wins, the developers, hearts and minds overall. >>So object storage always been simple, get put right. Pretty simple, you know, paradigm. Yes. But it was sort of the backwater before, you know, Amazon, you know, launched. Yes. You know, it's cloud. How have you seen object evolve? You mentioned performance. So I presume yes. Yes. You're not just for cheap and deep you're for cheap bin performance. So you could describe that a little bit if you would, >>For, for sure. Like you mentioned, right. When AWS was launched, S3 was the foundation layer. They launched S3 first and then came everything else around it. So object storage is the foundation of any cloud that you go with. And over a period of time, when we started the company back in 20 end of 2014, beginning 2015, it was all about cheap and deep storage. You know, you just get, put it into one basket, but over years, if you see, because the scale of data has increased quite a bit, new applications have emerged as well. That require high performance. That is where we partnered very closely with Intel early on. And I have to give it to them. Intel was the one who convinced us that you need to do high performance. You need to optimize your software with all the AVX five, 12 instruction set and so on. >>So we partnered very closely with them and we were the first one to come up with, you know, you need high performance, object storage and that in collaboration with Intel. So that's something that we take a lot of pride in, in terms of being the leader in that direction of bringing high performance object storage to the market, especially for big data workloads, AI ML, workloads, they're all object first, like even, you know, new age applications like snowflake and data bricks, they are not built on sand or file system. Right. They're all built on object storage rates. So that's where the, you need >>Performance. And I think the, I think the data bricks, snowflake examples. Good. And then you mentioned in 2014, when you started yes. At that time, big data was Hudu and you know, data, legs, data swamp. Yes. Yes. But the ones that were successful, the ones who optimize had the right bets, like you guys. Yeah. Now we're in an era. Okay. I gotta deploy this. So you got great downloads and update from developers. Now we see ops struggling to keep up yes. With the velocity of the development cycle. Yes. And with DevOps driving the cloud native yeah. Security data ops becomes important. Okay. Exactly. Security and data. A lot with storage going on there. Yes. How do you guys see that emerging? Cuz that becomes a lot of the conversations now in the architecture of the ops teams. I want to be supportive in enablement of dev. Yes. Yes. Do you guys target that world too? Or >>Yeah, we, we do target that. So the good thing about object storage is that if you look at the architecture in itself, it's very granular in terms of the controls that it can give to the end user. Right? So you can really customize in terms of, you know, what objects need to be accessible to whom what kind of policies you need to implement on the bucket level, what kind of access controls and provisions that you need to do. And especially like with ransomware attacks and what not, you can enable immutability and so on, so forth. So that's an important part of it. Especially I think the ransomware threats have increased quite a bit, especially with, you know, the macro, you know, situation with war and stuff. So we see that come up quite a bit. And that's where I think, you know, the data IU immutability, the data governance and compliance becomes extremely, extremely important for organizations. So we, we are partnering very closely with a lot of big organizations just for this use case itself. >>So how's it work if I want to build some kind of multi-cloud whatever X, right. Okay. I, I can use S three APIs or Azure blah. Okay. And I, and are all different. Yes. But if I want to use min IO, what's the experience like describe how I go about doing >>So if you've had any experience working with AWS, you don't need to even change a single line of code with us. You can just bring your applications directly onto min IO and it just behaves and act same way transparently what you would've experienced in AWS. Now you can just lift and shift that application and deploy it wherever you need it to be. Whether it is Azure, blah, whether it is Google cloud or even on edge. Like what we are seeing is that data is getting generated outside of public cloud. And most of the data that, you know, the emerging trend is that we see that data gets generated on edge quite a bit, whether it is autonomous cars, whether it is IOT, manufacturing units and so on. And you cannot push all that data back in the central cloud, it's extremely expensive for bandwidth and latency reasons. >>So you need to have an environment that looks and feels exactly what you have experienced at the central cloud on the edge itself. So a lot of our use cases are also getting deployed with Mani on the edge itself, whether it is on top of VMware because of the footprint of that VMware has within all these organizations itself. So we see that emerging quite a bit as well. And then you can tier the data off to any cloud, whether it is mid IO cloud, whether it is AWS, Azure, Google cloud, and so on. So you can have like a true multi-cloud environment. >>So you would follow VMware to the edge and be the object store there, or not necessarily if it's not VMware Kubernetes or whatever. >>Exactly. Exactly. Depending on the skill set that the organization has within, within their setup, if their DevOps savvy Kubernetes is becomes a very natural choice. If they are traditional enterprise, it, VMware is an ideal choice. So yeah. >>So you're seeing a lot of edge action you're saying, and we, >>We, we have seen starting it increasing yes. And >>Are customers. So they're persisting data at the edge. Yes. Yes they >>Are. Okay. >>It's not just the femoral and >>No, they are not because what the cost of putting all the data through bandwidth is extremely expansive to push all the data in central cloud and then process it and then store it. So we see that the data gets persisted on edge cloud as well in terms of processing and only the data that you need for, for the processing through whatever application systems that you, whether it is snowflake or data, bricks and whatnot, you know, you choose what applications from compute side, you want to bring on top of storage. And that can just seamlessly and transparently work. Yeah. >>Maria, you were saying that multi-cloud yeah. Games around Kubernetes. You, yes. That Kubernetes is all about multi-cloud that's the game. >>Yes. >>Yes. Can you explain what you mean by that? Why is multi-cloud a Kubernetes game? >>So multi-cloud has two foundations to it. One is the compute side. Another one is the storage side. Compute Kubernetes makes it extremely simple to deploy any application that is containerized. Once you containerize an application, it's no longer tied to the underlying infrastructure. You can actually deploy it no matter where you go. So Kubernetes makes that task extremely easy. And from storage standpoint, you know, the state of applications need to be held somewhere. You know, it's it, people say it's cloud, but it's computer somewhere. Right? So >>Exactly it's the >>Container. It needs, it needs to be stored somewhere. So that's where, you know, storage systems like man IO come into play where you can just take the storage and deploy it wherever you go. So it gets tightly bound with application itself, just like Kubernetes is for compute. Mano is for storage. >>I saw Scott Johnson, the CEO of Docker in Palo Alto last week did yeah. The spring to his step. So to speak Dockers doing pretty well as a result, they got, you know, starting to see certifications. Yes. So people are really rallying around containers in a more open way. Yes. But that's open source, but it's the Kubernetes, that's the action. Absolutely. That the container's really there now Docker's got a great business. Yes. Right now going yes. With how they're handling. I thought they did a great job. Yeah. But the Docker's now lingua Franco, right? Yes. That's the standard. It >>Is. It is. And I think where Kubernetes really makes it easy is in terms of when the scale is involved. Right. If there are, if the scale is small, it's okay. You can, you can work around it. But Kubernetes makes it extremely simple. If you have the right Kubernetes skill, I just need to put a disclaimer around there because not lot of people are Kubernetes expert, at least not yet. So if you have the expertise, Kubernetes makes the task extremely simple, predictable and automate and automated scale. I think that is what is >>The, so take me through a use case, cuz I've talked to a lot of enterprises, multiple versions, we're lifting and shifting to the cloud, that's kind of the, you know, get started, get your feet wet. Yes. Then there's like, okay, now we're refactoring really doing some native development and they're like, we don't have a staff on Kubernetes. We do a managed service. Yeah. So how does, how do you see that evolution piece taking place? Cause that's a critical adoption component as they start figuring out their Kubernetes relationship yes. To compute yes. How they roll it out. Yes. How do you see that playing out as a big part of this growth for a customer? >>Yeah. So we see a mix, you know, we see organizations that are born within cloud. Like they have just been in mono cloud like AWS. Now they are thinking about two things, right. With the economy being, you know, and the state that it is, they're getting hurt on the margin. Some of the SaaS companies that were born in cloud. So they are now actively thinking in terms of what mode they can do to bring the cost down. So they are partnering with min IO either to, you know, be in a colocation at Equinix, like data centers or go to other clouds to optimize for the compute modes and so on. So that's one thing that we see increasingly amongst enterprise. Second thing that we see is that because you know of that whole multi-cloud and cloud does go down, it's not like it, you know, and it's been evident over the last year or so that, you know, we've seen instances where Amazon was down or Google cloud was down. So they want to make sure that the data is available across the clouds in a consistent way. So with man IO, with the active, active application and so on, you can make the data available across the cloud. So your applications, even if one cloud is down for Dr. Purposes and so on, you can, you know, transparently, move the applications to another cloud and make sure that your business is not affected. So from business continuity reasons as well, the customers are partnering with us. So like I said, it's a mix. >>So the Tansu, you know, 1.3, the application development platform that we heard in the keynotes this morning, critical, you have to have that for cross cloud services. If you don't have a consistent experience, absolutely forget it. I mean it's table stake. Absolutely. But there's a lot of chatter on Twitter. A lot of skepticism that VMware can appeal to developers, some folk John as well chimed in saying, well, you know, it's, don't forget about the op side of the equation as well. They need security and consistency. Yes. What are you seeing in the marketplace in terms of VMware, specifically their customers and, and what do you, what do you, how do you rate their chances in terms of them being able to track the developer crowd, your, your peeps? >>Yeah. So VMware has a very strong hold on enterprise. It, you know, you have to give it to them. I don't come across any organization that does not have VMware, you know, for, with 500,000 customers. Right. Right. So they have done something really right for themselves. And if you have such a strong hold on the customers, it's not that hard to make the transition over to the developer mindset as well. And that is where with VMware partnership with partners like us, they can make, make that jump happen. So we partnered with them very closely for the data persistence layer and they wanted to bring Kubernetes the VMware tan natively to the VSAN interface itself. So we partnered with them, you know, we were their design partner and in, I think, 2020 or something, and we were their launch partner for that platform service. So now through the vCenter itself, you can provision object storage as a service for the developers. So I think they are working in terms of bridging the gap and they have the right mindset. It's all about execution like this. Right. >>They gotta get it >>Justed >>And it's the execution and timing. Exactly. And if they overshoot and the, it shifts over here, you know, this comes up a lot in our conversations. I want to get your reaction to this because I think that's a really great point. You guys are a nice foundational element. Yes. For VMware that plugs into them. That makes everything kind of float for them. Yes. Now we would, we were comparing OpenStack back in the day, how that had so much promise. Yes it did. If you remember, and storage was a big part of that conversation. It, it did. But the one thing that a lot of people didn't factor in on those industry discussions was Amazon was just ramping. Yes. So assuming that the hyper scales aren't stopping, innovating. Yeah. How does the multi-cloud fit with the constant struggles? Cuz abs is not rah multi-cloud cause they're there for the cloud, but customers are using Azure for yeah. Say office productivity teams or whatever, and then they have apps over here and then I'll see on private, private. Right. So hybrids there we get hybrid. Yeah. The clouds aren't changing. Yes. How does that change the dynamics in the market? Because it's a moving train. Some say, >>You know, it is, I would not characterize it like that because you know, AWS strength is that it is AWS, but also that it is not outside of AWS. Right. So it comes with the strengths and weaknesses and same goes for Azure. And same goes for Google cloud where VMware strength lies is the enterprise customers that it has. And I think if they can bridge the gap between the developers, enterprise customers and also the cloud, I think they have a really fair shot at, you know, making sure that the organizations and enterprise have the right experiences in terms of, you know, everyone needs to innovate. There is just no nothing that you can just sit back and relax. Everyone needs to innovate. And I think the good part about VMware is the partnership ecosystem that they have developed over the years and also making sure that their partners are successful along with them. And I think that is, that is going to be a key determining factor in terms of how well and how fast they can execute because nobody can do it alone in, in the enterprise world. So I think that that would be the >>Key, well, gua you're a great guest. Thanks for coming on and sharing you for having perspective on the cube. And obviously you've been on a, this from day 1, 20 15. Yes. I mean that's early and you guys made some great moves. Thank you. In a great position with VMware. Thank you. I like how you're the connective tissue and bridge to developers without a lot of disruption. Right? Real enablement. I think the question is can the VMware customers get there? So congratulations. No, thank you. And we got a couple minutes left. Take a minute to explain what's going on with the company that you co-founded, the team what's going on. Any updates funding very well, well funded. Yeah. How many people do you have? What's new. Are you gonna hire where take a minute to give the plug, give the commercial real quick >>For sure. So we started in 24 15, so it has been like seven, eight years now that we are at it. And I think we've been just very focused with the S3 compatible object storage, being AWS S3 for rest of the world. Like we get characterized at and over the years we've been like now we, we are used 60% in fortune 500 companies in some shape or format. So in terms of the scale and growth, we couldn't be more happier. We are about to touch a billion dollar billion Docker downloads in September. So that's something that we, we are very excited about. And in terms of the funding, we closed the, our series B sometime I think end of December last year and it's a billion dollar valuation and we have great partners in Intel capital and Dell ventures and soft bank. So we couldn't be in a more happier >>Spot. You're a unicorn soon to be decor. Right. >>What's next? Yes. I think, I think what is exciting for us is that the market, we could not be more happier with how the market is coming together with our vision, what we saw in 2015 and how everything is coming together nicely with, from the, the organization, realizing that multi-cloud is the core foundation and strategy of whatever they do next and lot has been accelerated due to COVID as well. Yeah. So in those terms, I think from market and product alignment, we just couldn't be more happier. >>Yeah. We think multi-cloud hybrids here. Steady state multi-cloud is gonna be a reality. Yeah. It becomes super cloud with the new dynamics. And again, David and I were talking last night, storage, networking, compute never goes away, never goes the operating. System's still gonna be out there. Just gonna be looked different and that >>Differently. Yes. I mean, yeah. And like, you know, in 10 years from now, Kubernetes might or might not be there as the foundation for, you know, compute, but storage is something that is always going to be there. People still need to persist the data. People still need a performance data store. People still need something that can scale to hundreds and hundreds of petabytes. So we are here. You bet against data >>As indie gross head once, you know, let chaos rain, rain in the chaos. There you go. Chaos cloud is gonna be simplified. Yeah. That's what innovation looks like. That's, >>That's what it is. >>Thanks for coming on the queue. Appreciate thank you for having me more coverage here. I'm John furrier with Dave Alane. Thanks for watching. More coverage. Three days just getting started. We'll be right back.

>>mhm Yes, everyone, welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. Got a great segment here. One of the big supporters and open source amazon web services returning back second year. Dr khan virtual Deepak Singh, vice president of the compute services at AWS Deepak, Great to see you. Thanks for coming back on remotely again soon. We'll be in real life. Reinvent is going to be in person, we'll be there. Good to see you. >>Good to see you too, john it's always good to do these. I don't know how how often I've been at the cube now, but it's great every single time your >>legend and getting on there, a lot of important things to discuss your in one of the most important areas in the technology industry right now and that is at the confluence of cloud scale and modern development applications as they shift towards as Andy Jassy says, the new guard, right. It's been happening. You guys have been a big proponent of open source and enabling open source is a service creating business models for companies. But more importantly, you guys are powering, making it easier for folks to use software. And doctor has been a big relationship for you. Could you take a minute to first talk about the doctor, a W S relationship and your involvement and what you're doing? >>Yeah, actually it goes back a long way. Uh you know, Justin, we announced PCS had reinvented 2014 and PCS at that time was very much managed orchestration service on top of DACA at that time. I think it was the first really big one out there from a cloud provider. And since then, of course, the world has evolved quite a bit and relationship with DR has evolved a lot. The thing I'd like to talk to is something that we announced that Dr last year, I don't remember if I talked about it on the cube at that time. But last year we started working with DR on how can we go from doctor Run, which customers love or DR desktop, which customers love and make it easy for people to run containers on pcs and Fergie. Uh so most new customers running containers and AWS today start with this Yes and party or half of them and we wanted to make it very easy for them to start with where they are on the laptop which is often bucket to stop and have running services the native US. So we started working with DR and that that collaboration has been very successful. We want to keep you look forward to continuing to work on evolving that where you can use Docker compose doctor, desktop, doctor run the fuel that darker customers used and the labour grand production services on the end of your side, which is the part that we've got that on. So I think that's one area where we work really well together. Uh, the other area where I think the two companies continue to work well together. It's open source in general as some of, you know, AWS has a very strong commitment to contain a. D uh, EKS our community service is moving towards community. Forget it actually runs all on community today and uh, we collaborate dr Rhonda on the Ocr specification because, you know, the Oc I am expect is becoming the de facto packaging format idea. W S. This morning we launched yesterday, we launched a service called Opera. And the main expected input for opera is an Ocr image are being in this Atlanta as well, where those ci images now a way of packaging for lambda. And I think the last one I like to call out and it has been an amazing partnership and it's an area where most people don't pay attention is amid signing. Uh, there's a project called Notary. We do the second version of the Notary Spec for remit signing and AWS Docker and a couple of other companies have been working very closely together on bringing that uh, you know, finalizing no tv too, so that at least in our case we can start building services for our customers on top of that. You know, it's it's a great relationship and I expect to see it continue. >>Well, I think one of the themes this year is developer experience. So good. Good call out there in the new announcements on the tools you have and software because that seems to be a great developer integration with Docker question I have for you is how should the customers think about things like E C. S and versus E K. S. App, Runner lambda uh for kind of running their containers. How do they understand the difference is, what's there? What's the, what's the thought process there? What's >>that? It's a good question actually been announced after. And I think there was one of the questions I started getting on twitter. You know, let's start at the very beginning. Anyone can pick up a Docker container and run it on easy to today. You can run it on easy to, we can run a light sail, but doc around works just fine. It's the limits machine. Then people want to do more complex things. They want to run large scale orchestrated services. They won't run their entire business and containers. We have customers will do that today. Uh, you know, you have people like Vanguard who runs a significant portion of the infrastructure on pcs frg or you have to elope with the heavy user of chaos, our community service. So in general, if you're running large scale systems, you're building your platforms, you're most likely to use the csny Chaos. Um, if you come from a community's background, you're, you're running communities on prem or you want the flexibility and control the communities gives you, you're gonna end up with the chaos. That's what we see our customers doing. If you just want to run containers, you want to use AWS to its fullest extent where you want the continue a P I to be part of the W A S A P. I said then you pick is yes. And I think one of the reasons you see so many customers start with the CSN, Forget is with forget to get the significant ease of use from an operational standpoint. And we see many start ups and you know, enterprises, especially security focus enterprises leaning towards farming. But there's a class of customers that doesn't want to think about orchestration that just wants. Here's my code, here's my container image just run my service for me and that's when things like happen, I can come and that's one of the reasons we launched it. Land is a little bit different. Lambda is a unique service. You buy into an event driven architecture. If you do that, then you can figure our application into this. That's they should start its magic. Uh, the container part, there is what land announced agreement where they now support containers, packaging. So instead of zip files, you can package up your functions as containers. Then lambda will run them for you. The advantage it gives you with all the tooling that you built, that you have to build your containers now works the land as well. So I won't call and a container orchestration service in the same sense of the CSC cso Afrin are but it definitely allows the container image format as a standard packaging format. I think that's the sort of universal common theme that you find across AWS at this point of time. >>You know, one of the things that we're observing at this at this event here is a lot of developers Coop con and Lennox foundations. A lot of operators to kubernetes hits that. But here's developers. And the thing is I want to ease of use, simplicity experience, but also I want the innovation. Yeah, I want all of it. When I ask you what is amazon bring to the table for the new equation, what would you say? >>Yeah, I mean for me it's always you've probably heard me say this 100 times. Many 1000 times. It's foggy fog. It's unique to us. It takes a lot of what we have learned about operating infrastructure scale. The question we asked ourselves, you know, in many ways we talk about forget even before belong pcs but we have to learn on what it meant and what customers really wanted. But the idea was when you are running clusters of instances of machines to run containers on, you have to start thinking about a lot of things that in some ways VMS but BMS in the car were taken away capacity. What kind of infrastructure to run it on? Should have been touched. Should have not been back. You know, where is my container running? Those are things. They suddenly started having to think about those kind of backwards almost. So the idea was how can we make your containerized bundles? So TCS task or community is part of the thing that you talk to and that is the main unit that you operate on. That is the unit that you get built on and meet it on. That's where Forget comes in and it allows us to do many interesting things. We've effectively changed the engine of forget since we've launched it. Uh, we run it on ec two instances and we run it on fire cracker. Uh, we have changed the forget agent architecture. We've made a lot of underneath the hood, uh, changes that even take the take advantage of the broader innovation, the rate of us, We did a whole bunch more to launch acronym trans on top of family customers don't have to think about it. They don't have to worry about it. It happens underneath the hood. It's always your engine as as you go along and it takes away all the operational pain of managing clusters of running into picking which instances to use to getting out, trying to figure out how to bend back and get efficiency. That becomes our problem. So, you know, that is an area where you should expect to see a Stuart done more. It's becoming the fabric of so many things that eight of us now. Uh, it's, you know, in some ways we're just talking a lot more to do. >>Yeah. And it's a really good time. A lot more wave of developers coming in. One of the things that we've been reporting on on Silicon England cube with our cute videos is more developers keep on coming on, more people coming in and contributing to the open source community. Even end users, not just the normal awesome hyper scholars you're talking about like classic, I call main street enterprises. So two things I want to ask you on the customer side because you have kind of to customers, you have the community that open source community and you have enterprise customers that want to make it easier. What are you seeing and hearing from customers? I know you guys work backwards from the customer. So I got to ask you work backwards from the community and work backwards from the enterprise customer. What's going on in their environment? What's the key trends that they're riding? What's the big challenges? What's the big opportunities that they're facing and saying for the community? >>Yeah, I start with the enterprise. That's almost an easier answer. Which is, you know, we're seeing increasingly enterprises moving into the cloud wholesale. Like in some ways you could argue that the pandemic has just accelerated it, but we have started seeing that before. Uh they want to move to the cloud and adult modern best practices. Uh If you see my talk agreement last few years, I've talked about modernization and all the aspects of modernization, and that's 90% of our conversation with enterprises, I've walked into a meeting supposedly to talk about containers, whatever half a conversation is spent on. How does an organization modernize? What does an organization need to do to modernize and containers and serverless play a pretty important part in it, because it gives them an opportunity to step away from the shackles of sort of fixed infrastructure and the methods and approaches that built in. But equally, we are talking about C I C. D, you know, fully automated deployments. What does it mean for developers to run their own services? What are the child, how do you monitor and uh, instrument uh, your services? How do you do observe ability in the modern world? So those are the challenges that enterprises are going towards, and you're spending a ton of time helping them there. But many of them are still running infrastructure on premises. So, you know, we have outpost for them. Uh, you know, just last week, you're talking to a bunch of our customers and they have lots of interesting ideas and things that they want to do without both, but many of them also have their own infrastructure and that's where something like UCS anywhere came from, which is hey, you like using Pcs in the cloud, You like having the safety i that just orchestrates containers for you. It does it on on his in an AWS region. It will do it in an outpost. It'll do it on wavelength, it'll do it on local zone. How about we allow you to do it on whatever infrastructure you bring to us. Uh you want to bring a raspberry pi, you can do that. You want to bring your on premises data center infrastructure, we can do that or a point of sale device, as long as you can get the agent running and you can connect to an AWS region, even though it's okay to lose connectivity every now and then. We can orchestrate a container for you over there and, you know, the same customer that likes the ease of use of Vcs. And the simplicity really resonated with that message really resonates with them. So I think where we are today with the enterprise is we've got some really good solutions for you in eight of us and we are now allowing you to take those a. P. I. S and then launch containers wherever you want to run them, whether it's the edge or whether it's your own data center. I think that's a big part of where the enterprise is going. But by and large, I think yes, a lot of them are still making that change from running infrastructure and applications the way they used to do a modern sort of, if you want to use the word cloud native way and we're helping them a lot. We've done, the community is interesting. They want to be more participatory. Uh that's where things like co pilot comes from. God, honestly, the best thing we've ever done in my order is probably are open road maps where the community can go into the road map and engage with us over there, whether it's an open source project or just trying to tell us what the feature is and how they would like to see it. It's a great engagement and you know, it's not us a lot. It's helped us prioritize correctly and think about what we want to do next. So yeah, I think that's, that >>must be very hard to do for opening up the kimono on the road map because normally that's the crown jewels and its secretive and you know, and um, now it's all out in the open. I think that is a really interesting, um, experiment and what's your reaction to that? What's been the feedback on the road map peace? Because I mean, I definitely want to see, uh, >>we do it pretty much for every service in my organization and we've been doing it now for three years. So years forget, I think about three years and it's been great. Now we are very we are very upfront, which is security and availability. Our job 000 and you know, 100 times out of 100 at altitudes between a new feature and helping our customers be available and safe. We'll do that. And this is why we don't put dates in that we just tell you directionally where we are and what we are prioritizing Uh, there every now and then we'll put something in there that, you know, well not choose not to put a feature in there because we want to keep it secret until it launches. But for the most part, 99% of our own myself there and people engaged with it. And it's not proven to be a problem because you've also been very responsible with how we manage and be very transparent on whether we can commit to something or not. And I think that's not. >>I gotta ask you on as a leader uh threaded leader on this group. Open source is super important, as you know, and you continue to do it from under years. How are you investing in the future? What's your plan? Uh plans for your team, the industry actually very inclusive, Which is very cool. It's gonna resonate well, what's the plans? Give us some details on what you're investing in, what your priorities? What's your first principles? >>Yeah, So it goes in many ways, one when I I also have the luxury also on the amazon open source program office. So, you know, I get the chance to my team, rather not me help amazon engineers participate in open source. That that's the team that helps create the tools for them, makes it easy for them to contribute, creates, you know, manages all the licenses, etcetera. I'll give you a simple example, you know, in there, just think of the cr credential helper that was written by one of our engineers and he kind of distorted because he felt it was something that we needed to do. And we made it open source in general, in in many of our teams. The first question we asked is should something the open why is this thing not open source, especially if it's a utility or some piece of software that runs along with services. So they'll step one. But we've done some big things also, I, you know, a couple of years ago we launched Lennox operating system called bottle Rocket. And right from the beginning it was very clear to us that bottle Rocket was two things. It was both in AWS product. But first it was an open source project. We've already learned a little bit from what we've done at Firecracker. But making bottle rocket and open source operating system is very important. Anyone can take part of Rocket the open source to build tooling. You can run it whatever you want. If you want to take part of Rocket and build a version and manage it for another provider. For another provider wants to do it, go for it. There's nothing stopping you from doing that. So you'll see us do a lot there. Obviously there's multiple areas. You've seen WS investing on the open source side. But to me, the winds come from when engineers can participate in small things, released little helpers or get contributions from outside. I think that's where we're still, we can always have that. We're going to continue to strive to make it better and easier. And uh, you know, I said, I have, you know, me and my team, we have an opportunity to help their inside the company and we continue to do so. But that's what gets me excited. >>Yeah, that's great stuff. And congratulations on investing in the community, really enjoys it and I know it moves the needle for the industry. Deepak, I gotta ask you why I got you here. Dr khan obviously, developers, what's the most important story that they should be paying attention to as a developer because of what's going on shift left for security day two operations also known as a I ops getups, whatever you wanna call it, you know, ongoing, you get server lists, you got land. I mean, all kinds of great things are going on. You mentioned Fargate, >>um >>what should they be paying attention to that's going to really help their life, both innovation wise and just the quality of life. >>Yeah, I would say look at, you know, in the end it is very easy developers in particular, I want to build the buildings and it's very easy to get tempted to try and get learn everything about something. You have access to all the bells and whistles and knobs, but in reality, if you want to run things you want to, you want to focus on what's important, the business application, that and you the application. And I think a lot of what I'll tell developers and I think it's a lot of where the industry is going is we have built a really solid foundation, whether it's humanity, so you CSN forget or you know, continue industries out there. We have very solid foundation that, you know, our customers and develop a goal of the world can use to build upon. But increasingly, and you know, they are going to provide tools that sort of take that wrap them up and providing a nice package solution After another great example, our collaboration, the doctor around Dr desktop are a great example where we get all the mark focus on the application and build on top of that and you can get so much done. I think that's one trend. You'll see more and more. Those things are no longer toys, their production grade systems that you can build real world applications on, even though they're so easy to use. The second thing I would add to that is uh, get uh, it is, you know, you can give it whatever name you want. There's uh, there's nuances there, but I actually think get up is the way people should be running the infrastructure, my virus in my personal, you know, it's something that we believe a lot in homicide as hard as you go towards immutable infrastructure, infrastructure, automation, we can get off plays a significant role. I think developers naturally gravitate towards it. And if you want to live in a world where development and operations are tightly linked, I think it after the huge role to play in that it's actually a big part of how we're planning to do things like yes, anywhere, for example, a significant player and that it would be a proton. I think get up will be a significant in the future of proton as well. So I think that's the other trend. If you wanted to pick a trend that people should pay attention. That's what I believe in a lot. >>Well you're an expert. So I want to get you a quick definition. What is get Ops, how would you define it? Because that's a big trend. What does it, what does that mean? >>Electricity will probably shoot me for getting this wrong. I tell you how I think about it. Which is, you know, in many cases, um, you when you're doing deployments are pushing a deployment getups is more of a full deployment. When you are pushing code to get depository, you have a system that knows that the event has happened and then pulls from there and triggers the thing as opposed to you telling it take I have this new piece of code now go deployed everywhere. So to me, the biggest changes that Two parts one is it's more for full mechanism where you're pulling because something has changed. So it needs systems like container orchestrators to keep them, you know, to keep them in sync. And the second part of the natural natural evolution of infrastructure score, which is basically everything is called the figures code. Infrastructure as code, code is code and everything is getting stored in that software repo and the software repo becomes your store of record and drives everything. Uh So for a glass of customers, that's going to be a pretty big deal. >>Yeah, when you're checking in code, that's again, it's like a compiler for the compiler, a container for the container, you've got things for each other. Automation is ultimately what we're talking about here. And that's to me where machine learning kicks in. So again, having this open source foundational fabric, as you said, forget out the muck or the undifferentiated heavy lifting. This is what we're talking about automation, isn't it? Deepak? >>Yes. I mean I said uh one thing where we hang our hat on is there's such good stuff out there in the world which we like to contribute to, but the thing we like to hang our hat on is how do you run this? How do you do it this in ways that you can uniquely bring capabilities to customers where there's things like nitro or things are nitro open stuff. Well, the fact that we have built up this operational infrastructure over the last in a decade plus or in the container space over the last seven years where we really really know how to run these things at scale and have made all the investments to make it easy to do. So that's that's where we have hanger hard keeping people safe, helping them only available applications, their new startup, that just completely takes off in over the weekend. For whatever reason, because, you know, you're the next hot thing on twitter and our goal is to support you whether you are, you know, uh enterprise that's moving from the main train or you are the next hot startup, that's you know, growing virally and uh, you know, we've done a lot to build systems help both sides and yeah, it's >>interesting if you sing about open source where it's come from, I mean I remember that base wouldn't open source wasn't open, I would be peddling software, there's a free copy of Linux, UNIX um in college and now it's all free. But I mean just what's changed now. It used to be just free software, download software. You got it now, it's a service. Service now can be monetized quickly. And what you guys are offering with AWS and cloud scale is you've done all these things as I don't have to have a developer. I get the benefits of the scale, I can bring my open source code to the table, make it a service integrated in with other services and be the next snowflake, be the next, you know, a company that could scale. And that is that's the that's the innovation, right? That's the this is a new phenomenon. So it also changes the business model. >>Yeah, actually you're you're quite right. Actually, I I like one more thing to it. But you look at how a lot of enterprises use containers today. Most of them are using something like this year, Symphony or GS to build an internal developer platform and internal developer portal. And then the question then becomes this hard to scale this modern and development practices to an entire organization. What is your big bank that's been around as thousands and thousands of ID stuff That may not all be experts are running communities running container is when you scale it out different systems that proton come into play. That was actually the inspiration is how do you help an organization where they're building these developer Portholes and developer infrastructure, developer platforms, How do you make it easy for them to build it? Be almost use it as a way to get these modern practices into the hands of all the business units, where they may not have the time to become experts at the modern ways of running infrastructure because they're busy doing other things. And I think you'll see the a lot more happening that space that's not happening in the open source community. There's proton, there's a bunch of interesting things happening here and be interesting to see how that evolves. >>And also, you know, the communal, communal aspect of not just writing code together, but succeeding, right, building something. I mean, that's when you start to see the commercial meets open kind of ethos of communal activity of working together and sharing a big part of this year's. Dakar Con is sharing not just running and shipping code but sharing. >>Yeah, I mean if you think about it uh Dockers original value was you build run and shit right? You use the same code to build it, you use the same code to ship it, the same sort of infrastructure interface and then you run it and that, you know, the fact that the doctor images such a wonderfully shareable entity uh that can run every girl is such a powerful and it's called the Ci Image. Now I still call him Dr images because it's just easier. But that to me like that is a big deal and I think it's becoming and become an even bigger deal over the years. I came from something before, Amazon has to work in The sciences and bioinformatics and you know, the ability to share codeshare dependencies, package all of that up in a container image is a big deal. It's what got me one of the reasons I got fascinated with container 78 years ago. So it will be interesting to see where all of systems. >>It's great, great stuff. Great success. And congratulations. Deepak, Great to always talk to you got a great finger on the pulse. You lead a really important organizations at AWS and you know, doctor has such a huge success with developers, even though the company has gone through kind of a uh change over and a pivot to what they're doing now. They're back to their open source roots, but they have millions and millions of developers use Docker and new developers are coming in dot net developers are coming in. Windows developers are coming in and and so it's no longer about Lennox anymore. It's about just coding. >>Yeah. And it's it's part of this big trend towards infrastructure, automation and and you know development and deployment practices that I think everyone is going to adopt faster than we think they will. But you know, companies like Doctor and opens those projects that they involved are critical in making that a lot easier for them. And then you know, folks like us get to build on top of that orbit them and make it even easier. >>Well, great testimony the doctor that you guys based your E C. S on Docker Doctor has a critical role in developing community. I run composed in their hub with dr desktop and we'll be watching amazon and and the community activity and see what kind of experiences you guys can bring to the table and continue that momentum. Thank you Deepak for coming on the >>cube. Thank you, john. That's always a pleasure. >>Okay. Mr cubes. Dr khan 2021 virtual coverage. I'm john for your host of the cube. Thanks for watching.

>>Hello everybody. And welcome back. Wow. What a Docker con we've been gone all day. There's so many great breakout sessions, live panels. How many you just came off a live panel. >>He did. It was great. It was awesome. >>So I'm Peter McKie, head of developer relations and we have Brett Fisher hammer one on everybody just introduced herself. We have a new guest here. I'm not sure if people know who you are. Uh, Scott, maybe if you can introduce yourself. Hello? Hello. Hello? Is this Mike? All right. Awesome. So I thought, well cool. What a long day. I think we had some really awesome talks. Of course. Um, it was hard to jump around right. And see everything. So, um, so I missed a lot, but I got to see some great talks. I love the Kubernetes talk. The, the, the, the minimal things you need to know from Kubernetes from Elton, which was fantastic. Yeah. I really loved. And the M one talk from tonus man. I'm super excited about my. >>Yeah, I'm super excited, but I didn't get the Mac until I knew that Docker would support containers on it. There you go. >>There you go. Everybody should have one. Yep. Yep. So you said we were running windows. It's just a personal, personal preference. Okay. So I thought, I thought we could talk about maybe reminisce a little bit, but uh, you know, Scott has the shirt on there from 14, but I doubt that's the first DockerCon you have ever been to Scott? Is it the first, first? Yeah, that was the first one we ever held. So first one we ever held was, uh, June, 2014. And so it was about what, 15 months after Docker was opensource. And we had 300 people all crammed in a little room in a hotel in San Francisco. Right. And we had Lego whale schwag and, you know, talks. And it w what's that, that was the first one. Yeah, it was the first one. And then after that, I remember I wasn't there, but in, um, was it an Amsterdam where the video, the great video where the, the, the, the crowd, we got to play a video game and they were kicking around the, the, uh, beach balls and it would move, moved a little arcade character. Brett, do you remember this? And, and you had to move with the crowd. It was, it looked like a nightclub. It was closed. >>That was fantastic. Like those intros were some of the most, it was like being in a nightclub when, uh, a new band debuted or >>All right. Well, how am I, w is this your, this is your first Docker con, correct? >>It is. I'm like, I feel like I'm just a new, but, uh, I had a great time, like I said, before, kid in the candy store, I learned so much, especially the panels, even from our Docker individuals. So that was, it was great. I I'm enthralled, I'm excited. I'm going to watch all the recordings afterwards as everyone else will be able to do too, since we got that question a lot, but yeah. Super exciting for me. >>Yeah. You might have to wait until tomorrow because the adrenaline is just going to just going to drop. You might just sleep, sleep, and then, but then you can watch them watch all the replays tomorrow. I know that's what I'm going to do, catch up on things sleep with. But, um, I have some that talk about, and so some of the highlights that I was interested in, maybe some of them, you know, might not be at the top of everybody's mind, but the verified publisher program. I mean, that, that is it's incredible, right. That's just about all the security, uh, supply chain security problems that are happening. Right. That's a huge, huge win for us. I think Scott of having, uh, partners around, uh, around containers, around software, joining us to, and we verify their content, uh, just building trust, more trust with the community, right? >>Yeah. I mean, I mean, you saw this theme throughout the conference, right? Is that the, the security theme kind of ran deep and you saw a lot of talks and panels. And so this is just kind of playing into that where it's like, how do you, how do you start with content you trust as developers updated or their put their apps on it and then hand it off to ops and then deploy from there. And so, um, the verified publisher program is just another layer if you will, of providing kind of trusted content that, that people want to use and want to use in their application. So yeah, no, I think it's a great ad and it's very consistent with what you see kind of the conversation, the community that we saw throughout the day. Yeah, absolutely. But w what was the highlight for you for today? Put you on the spot a little bit. >>Um, again, hanging out, getting to hang out with my friends again and meet new people like that was basically, you know, at Docker con uh, I have so many memories. In fact, uh, we were earlier today on Twitter. We were throwing up some old pictures of like the original captains, uh, gathering in Seattle. And we actually got to be captains on little boats. They get, they, they put us in boats, we didn't have any training and we got to drive them around in a, in a lake. And it was hilarious. Um, and, and having those memories and then re reliving them with people that were there or people that were, um, a part of that early days of Docker. And that's one of my favorite parts of Docker course, the learning is fantastic, the new features, but yeah, that, that those memories >>Let, let, let me lean into Brett it's point. Like, like, so we're all, we're all nerds and introverts, right? So like, we get excited by the tech and the bits and the bites, but Brett's point about like the community and how, like it's just grown over the years. And it's always been kind of welcoming to newcomers as well as providing forums for cutting edge discussions as well. Like that, that is one of those things. I think we, we often don't fully appreciate no fully celebrate. And so today was a great example of just celebrating that and putting that front and center of the whole conversations for everything. Yeah, yeah. A hundred percent in the, all of the community leaders, the community, the rooms that we had. I mean, they were, we just chatting before we came online about the Brazil, uh, community room there they're just trucking along, keep going. Yeah. Yeah. I mean, they're, they're just, um, yeah, it amazes me every, every time and the captains program. Right. I mean, everybody on there is they're experts in what they do, but not a whole lot of egos. I mean, it just super nice people always willing to help. I mean, the whole community is like that in my opinion, for sure. Yeah. Awesome. >>Just a couple of highlights that I wanted to share if I could, what was your favorite? Um, you know, my favorite, this is going to sound super geeky. It was the people talked about documentation. And so I just wanted to do a call out to OSHA who does such a great job on our documentation and that as a developer, I mean, documentation was a very important part of what I needed to do. It's like a critical tool for me, and that we have that on the program was great, but of course, verified publisher program I've been working closely on that. That has been great. We have some great press releases that have gone out from our partners. So I encourage you to check that out. I wanted to share some stats if that's okay. I think attendees would be very interested. We have over 79,000 people who signed up for DockerCon. >>So, uh, that's a great number that exceeds last year's number, I believe. And, uh, we had the, the sound right. And then we had about 23,000, um, attendees during the, the day today, which is, which is also incredible. And we're still crunching those numbers, but it's wonderful. And then the, GoFund me, we're sitting at about a little over a thousand dollars. So, you know, DockerCon, doesn't end after this. There's still recordings and presentations you can look at and the GoFund me will still be up for a while. So I encourage you to, to donate for that. But those are just some interesting stats. >>Oh, that's awesome. Yeah. It's amazing. The numbers that, that happened. And again, I think it's because of the community for real, there's just so many great folks. Yeah. I mean, the chat is just on fire, right. Everybody wants to engage so much. It just flies by right. When you see it, right. You see folks waking up at 2:00 AM, 3:00 AM to participate, and it's not, you know, part of it's for the content, but, but a lot of it is the community because they know they're going to find folks willing to answer questions, willing to share. And, and you know, how often do you experience that in tech communities? And so I think that's what makes Docker, um, special. There's a lot of great communities out there, but the doc community is really special in that sense of like, like you can wait in, you can be a newbie, you can be an expert and there's a place for you, right. >>There's a place for you to share. There's a place for you to learn. And there's always something to learn. There's always something you can share with someone else. And I think that's something that we all should like celebrate, but also work hard and be deliberate to kind of, kind of preserve right. And, and protect as we grow this to like 80,000 this year, a hundred thousand next year, 200,000 million after that, right? Yeah. Yeah. A hundred percent. Yeah. It's important to stay authentic and true to our roots for sure. And I think that's, I mean, it's one of the biggest reasons I am here at Dockers because of the community. The tools are awesome too. Uh, you know, I'm a big fan for sure. And that's what drew me in, but I stay before the people, one that I work with and to the, the broader community, I think it's one of the best in the industry. >>I possibly could be a little biased, but I truly believe that it's okay to, you're a lot of advice. What do you hear in the chat? Yeah. Yeah. You got one, one 30 in the morning and the UK two 25 in the morning. Where's Tony Switzerland. So yeah. That's great. Philippines. Yeah. Yeah. Jacob Howard was on my, uh, on my panel for, uh, development dev containers. Right. He's in Ukraine and he's like, yeah, Nope, no problem. I'll wake up. I'd love to be on. Right. It's it's amazing. Yeah. Okay. What did we, and this might be, I risk, uh, not thinking too far in the future, but you know, you know, sitting in America, looking at COVID right. I think we're starting to come out of it a little bit. Uh, the rest of the world is, you know, still struggling a bit, but, um, yeah. >>Be interesting. Let's say everything goes well. Right. Hi, some kind of hybrid, um, events seems interesting to me, um, possibly some local events that, you know, these communities are coming together, live to watch and to also do their thing. I don't know. I don't know anybody's thoughts about, um, you know, what a hybrid model looks like next year or maybe a year and a half. I don't, I don't know, but I just, no, Peter, I think you're spot on. And that's, that's the topic of the moment, right? It's like, how do you preserve the, the wonderful reach and accessibility that we're seeing today? Right. And last year with the virtual conferences, but we also know that like the face to face in person, our IRL conferences also have a lot of value. Right. So how do you, how do you blend the two of those and still have a great experience, honestly, like community, like give us your feedback, give us your ideas. >>Like we're, we're right in the middle of figuring out what we do for the next 12 months, once it's safe to meet face to face. Right. That's a great question. Yeah. Yeah. I don't, you can't beat the power of sitting down beside someone, like you mentioned earlier, Scott, where a lot of us are introverts and, um, you know, so the screen in front of us is a little bit hard, but I, those connections you make in the hallways after, after the talks in, in the hotel lobby, I mean, white boarding on a, on a yeah. Like it's, it's invaluable, right? Yeah. Yeah. Well, awesome. Brett time-check we're where are we at? Here? We are at time. Okay. It felt like that. Oh man. Oh, bummer. Well it's okay. What a great day. Goodbye. >>See you later. Goodbye. Yeah. Well, thanks guys for jumping on here at the end and with everybody, I really appreciate it. And uh, thank you to the Docker community, all the speakers, all the panelists, all the keynote speakers, everybody behind the scenes did a phenomenal job. Um, I I'm super excited to be part of this team and I totally look forward to being able to see everybody in person. And, uh, yeah, I'll shut up and let anybody else close out. I don't want to be the last one, but, uh, well, no. Well done Peter. Well done Brett, and look, Dr. Communities is what makes us, makes us strong, makes it work. And through trials like COVID and other challenges of last year, the community held strong, right? And so let's all respect that let's cherish that let's protect that. And like, let's look forward in the next 12 months, have a great 12 months and figure out what DockerCon 20, 22 looks like the conclude, all these great voices have as much interactivity, whether it's on-prem, whether it's virtual, whether it's hybrid and just want to say thank you to community. Thank you. The sponsors. Thank you. The Docker team who went above and beyond to make this happen. Thank you. The Docker, captains and the community behind the scenes. A phenomenal event. And just want to thank everyone so much. Yeah. Yep. All right. Well, that'll wrap it up. Thanks everybody. We'll see you we'll see you soon. Awesome. All right. Thanks everyone, doctor

>>Individuals create developers, translate ideas to code, to create great applications and great applications. Touch everyone. A Docker. We know that collaboration is key to your innovation sharing ideas, working together. Launching the most secure applications. Docker is with you wherever your team innovates, whether it be robots or autonomous cars, we're doing research to save lives during a pandemic, revolutionizing, how to buy and sell goods online, or even going into the unknown frontiers of space. Docker is launching innovation everywhere. Join us on the journey to build, share, run the future. >>Hello and welcome to Docker con 2021. We're incredibly excited to have more than 80,000 of you join us today from all over the world. As it was last year, this year at DockerCon is 100% virtual and 100% free. So as to enable as many community members as possible to join us now, 100%. Virtual is also an acknowledgement of the continuing global pandemic in particular, the ongoing tragedies in India and Brazil, the Docker community is a global one. And on behalf of all Dr. Khan attendees, we are donating $10,000 to UNICEF support efforts to fight the virus in those countries. Now, even in those regions of the world where the pandemic is being brought under control, virtual first is the new normal. It's been a challenging transition. This includes our team here at Docker. And we know from talking with many of you that you and your developer teams are challenged by this as well. So to help application development teams better collaborate and ship faster, we've been working on some powerful new features and we thought it would be fun to start off with a demo of those. How about it? Want to have a look? All right. Then no further delay. I'd like to introduce Youi Cal and Ben, gosh, over to you and Ben >>Morning, Ben, thanks for jumping on real quick. >>Have you seen the email from Scott? The one about updates and the docs landing page Smith, the doc combat and more prominence. >>Yeah. I've got something working on my local machine. I haven't committed anything yet. I was thinking we could try, um, that new Docker dev environments feature. >>Yeah, that's cool. So if you hit the share button, what I should do is it will take all of your code and the dependencies and the image you're basing it on and wrap that up as one image for me. And I can then just monitor all my machines that have been one click, like, and then have it side by side, along with the changes I've been looking at as well, because I was also having a bit of a look and then I can really see how it differs to what I'm doing. Maybe I can combine it to do the best of both worlds. >>Sounds good. Uh, let me get that over to you, >>Wilson. Yeah. If you pay with the image name, I'll get that started up. >>All right. Sen send it over >>Cheesy. Okay, great. Let's have a quick look at what you he was doing then. So I've been messing around similar to do with the batter. I've got movie at the top here and I think it looks pretty cool. Let's just grab that image from you. Pick out that started on a dev environment. What this is doing. It's just going to grab the image down, which you can take all of the code, the dependencies only get brunches working on and I'll get that opened up in my idea. Ready to use. It's a here close. We can see our environment as my Molly image, just coming down there and I've got my new idea. >>We'll load this up and it'll just connect to my dev environment. There we go. It's connected to the container. So we're working all in the container here and now give it a moment. What we'll do is we'll see what changes you've been making as well on the code. So it's like she's been working on a landing page as well, and it looks like she's been changing the banner as well. So let's get this running. Let's see what she's actually doing and how it looks. We'll set up our checklist and then we'll see how that works. >>Great. So that's now rolling. So let's just have a look at what you use doing what changes she had made. Compare those to mine just jumped back into my dev container UI, see that I've got both of those running side by side with my changes and news changes. Okay. So she's put Molly up there rather than mobi or somebody had the same idea. So I think in a way I can make us both happy. So if we just jumped back into what we'll do, just add Molly and Moby and here I'll save that. And what we can see is, cause I'm just working within the container rather than having to do sort of rebuild of everything or serve, or just reload my content. No, that's straight the page. So what I can then do is I can come up with my browser here. Once that's all refreshed, refresh the page once hopefully, maybe twice, we should then be able to see your refresh it or should be able to see that we get Malia mobi come up. So there we go, got Molly mobi. So what we'll do now is we'll describe that state. It sends us our image and then we'll just create one of those to share with URI or share. And we'll get a link for that. I guess we'll send that back over to you. >>So I've had a look at what you were doing and I'm actually going to change. I think that might work for both of us. I wondered if you could take a look at it. If I send it over. >>Sounds good. Let me grab the link. >>Yeah, it's a dev environment link again. So if you just open that back in the doc dashboard, it should be able to open up the code that I've changed and then just run it in the same way you normally do. And that shouldn't interrupt what you're already working on because there'll be able to run side by side with your other brunch. You already got, >>Got it. Got it. Loading here. Well, that's great. It's Molly and movie together. I love it. I think we should ship it. >>Awesome. I guess it's chip it and get on with the rest of.com. Wasn't that cool. Thank you Joey. Thanks Ben. Everyone we'll have more of this later in the keynote. So stay tuned. Let's say earlier, we've all been challenged by this past year, whether the COVID pandemic, the complete evaporation of customer demand in many industries, unemployment or business bankruptcies, we all been touched in some way. And yet, even to miss these tragedies last year, we saw multiple sources of hope and inspiration. For example, in response to COVID we saw global communities, including the tech community rapidly innovate solutions for analyzing the spread of the virus, sequencing its genes and visualizing infection rates. In fact, if all in teams collaborating on solutions for COVID have created more than 1,400 publicly shareable images on Docker hub. As another example, we all witnessed the historic landing and exploration of Mars by the perseverance Rover and its ingenuity drone. >>Now what's common in these examples, these innovative and ambitious accomplishments were made possible not by any single individual, but by teams of individuals collaborating together. The power of teams is why we've made development teams central to Docker's mission to build tools and content development teams love to help them get their ideas from code to cloud as quickly as possible. One of the frictions we've seen that can slow down to them in teams is that the path from code to cloud can be a confusing one, riddle with multiple point products, tools, and images that need to be integrated and maintained an automated pipeline in order for teams to be productive. That's why a year and a half ago we refocused Docker on helping development teams make sense of all this specifically, our goal is to provide development teams with the trusted content, the sharing capabilities and the pipeline integrations with best of breed third-party tools to help teams ship faster in short, to provide a collaborative application development platform. >>Everything a team needs to build. Sharon run create applications. Now, as I noted earlier, it's been a challenging year for everyone on our planet and has been similar for us here at Docker. Our team had to adapt to working from home local lockdowns caused by the pandemic and other challenges. And despite all this together with our community and ecosystem partners, we accomplished many exciting milestones. For example, in open source together with the community and our partners, we open sourced or made major contributions to many projects, including OCI distribution and the composed plugins building on these open source projects. We had powerful new capabilities to the Docker product, both free and subscription. For example, support for WSL two and apple, Silicon and Docker, desktop and vulnerability scanning audit logs and image management and Docker hub. >>And finally delivering an easy to use well-integrated development experience with best of breed tools and content is only possible through close collaboration with our ecosystem partners. For example, this last year we had over 100 commercialized fees, join our Docker verified publisher program and over 200 open source projects, join our Docker sponsored open source program. As a result of these efforts, we've seen some exciting growth in the Docker community in the 12 months since last year's Docker con for example, the number of registered developers grew 80% to over 8 million. These developers created many new images increasing the total by 56% to almost 11 million. And the images in all these repositories were pulled by more than 13 million monthly active IP addresses totaling 13 billion pulls a month. Now while the growth is exciting by Docker, we're even more excited about the stories we hear from you and your development teams about how you're using Docker and its impact on your businesses. For example, cancer researchers and their bioinformatics development team at the Washington university school of medicine needed a way to quickly analyze their clinical trial results and then share the models, the data and the analysis with other researchers they use Docker because it gives them the ease of use choice of pipeline tools and speed of sharing so critical to their research. And most importantly to the lives of their patients stay tuned for another powerful customer story later in the keynote from Matt fall, VP of engineering at Oracle insights. >>So with this last year behind us, what's next for Docker, but challenge you this last year of force changes in how development teams work, but we felt for years to come. And what we've learned in our discussions with you will have long lasting impact on our product roadmap. One of the biggest takeaways from those discussions that you and your development team want to be quicker to adapt, to changes in your environment so you can ship faster. So what is DACA doing to help with this first trusted content to own the teams that can focus their energies on what is unique to their businesses and spend as little time as possible on undifferentiated work are able to adapt more quickly and ship faster in order to do so. They need to be able to trust other components that make up their app together with our partners. >>Docker is doubling down and providing development teams with trusted content and the tools they need to use it in their applications. Second, remote collaboration on a development team, asking a coworker to take a look at your code used to be as easy as swiveling their chair around, but given what's happened in the last year, that's no longer the case. So as you even been hinted in the demo at the beginning, you'll see us deliver more capabilities for remote collaboration within a development team. And we're enabling development team to quickly adapt to any team configuration all on prem hybrid, all work from home, helping them remain productive and focused on shipping third ecosystem integrations, those development teams that can quickly take advantage of innovations throughout the ecosystem. Instead of getting locked into a single monolithic pipeline, there'll be the ones able to deliver amps, which impact their businesses faster. >>So together with our ecosystem partners, we are investing in more integrations with best of breed tools, right? Integrated automated app pipelines. Furthermore, we'll be writing more public API APIs and SDKs to enable ecosystem partners and development teams to roll their own integrations. We'll be sharing more details about remote collaboration and ecosystem integrations. Later in the keynote, I'd like to take a moment to share with Docker and our partners are doing for trusted content, providing development teams, access to content. They can trust, allows them to focus their coding efforts on what's unique and differentiated to that end Docker and our partners are bringing more and more trusted content to Docker hub Docker official images are 160 images of popular upstream open source projects that serve as foundational building blocks for any application. These include operating systems, programming, languages, databases, and more. Furthermore, these are updated patch scan and certified frequently. So I said, no image is older than 30 days. >>Docker verified publisher images are published by more than 100 commercialized feeds. The image Rebos are explicitly designated verify. So the developers searching for components for their app know that the ISV is actively maintaining the image. Docker sponsored open source projects announced late last year features images for more than 200 open source communities. Docker sponsors these communities through providing free storage and networking resources and offering their community members unrestricted access repos for businesses allow businesses to update and share their apps privately within their organizations using role-based access control and user authentication. No, and finally, public repos for communities enable community projects to be freely shared with anonymous and authenticated users alike. >>And for all these different types of content, we provide services for both development teams and ISP, for example, vulnerability scanning and digital signing for enhanced security search and filtering for discoverability packaging and updating services and analytics about how these products are being used. All this trusted content, we make available to develop teams for them directly to discover poll and integrate into their applications. Our goal is to meet development teams where they live. So for those organizations that prefer to manage their internal distribution of trusted content, we've collaborated with leading container registry partners. We announced our partnership with J frog late last year. And today we're very pleased to announce our partnerships with Amazon and Miranda's for providing an integrated seamless experience for joint for our joint customers. Lastly, the container images themselves and this end to end flow are built on open industry standards, which provided all the teams with flexibility and choice trusted content enables development teams to rapidly build. >>As I let them focus on their unique differentiated features and use trusted building blocks for the rest. We'll be talking more about trusted content as well as remote collaboration and ecosystem integrations later in the keynote. Now ecosystem partners are not only integral to the Docker experience for development teams. They're also integral to a great DockerCon experience, but please join me in thanking our Dr. Kent on sponsors and checking out their talks throughout the day. I also want to thank some others first up Docker team. Like all of you this last year has been extremely challenging for us, but the Docker team rose to the challenge and worked together to continue shipping great product, the Docker community of captains, community leaders, and contributors with your welcoming newcomers, enthusiasm for Docker and open exchanges of best practices and ideas talker, wouldn't be Docker without you. And finally, our development team customers. >>You trust us to help you build apps. Your businesses rely on. We don't take that trust for granted. Thank you. In closing, we often hear about the tenant's developer capable of great individual feeds that can transform project. But I wonder if we, as an industry have perhaps gotten this wrong by putting so much emphasis on weight, on the individual as discussed at the beginning, great accomplishments like innovative responses to COVID-19 like landing on Mars are more often the results of individuals collaborating together as a team, which is why our mission here at Docker is delivered tools and content developers love to help their team succeed and become 10 X teams. Thanks again for joining us, we look forward to having a great DockerCon with you today, as well as a great year ahead of us. Thanks and be well. >>Hi, I'm Dana Lawson, VP of engineering here at get hub. And my job is to enable this rich interconnected community of builders and makers to build even more and hopefully have a great time doing it in order to enable the best platform for developers, which I know is something we are all passionate about. We need to partner across the ecosystem to ensure that developers can have a great experience across get hub and all the tools that they want to use. No matter what they are. My team works to build the tools and relationships to make that possible. I am so excited to join Scott on this virtual stage to talk about increasing developer velocity. So let's dive in now, I know this may be hard for some of you to believe, but as a former CIS admin, some 21 years ago, working on sense spark workstations, we've come such a long way for random scripts and desperate systems that we've stitched together to this whole inclusive developer workflow experience being a CIS admin. >>Then you were just one piece of the siloed experience, but I didn't want to just push code to production. So I created scripts that did it for me. I taught myself how to code. I was the model lazy CIS admin that got dangerous and having pushed a little too far. I realized that working in production and building features is really a team sport that we had the opportunity, all of us to be customer obsessed today. As developers, we can go beyond the traditional dev ops mindset. We can really focus on adding value to the customer experience by ensuring that we have work that contributes to increasing uptime via and SLS all while being agile and productive. We get there. When we move from a pass the Baton system to now having an interconnected developer workflow that increases velocity in every part of the cycle, we get to work better and smarter. >>And honestly, in a way that is so much more enjoyable because we automate away all the mundane and manual and boring tasks. So we get to focus on what really matters shipping, the things that humans get to use and love. Docker has been a big part of enabling this transformation. 10, 20 years ago, we had Tomcat containers, which are not Docker containers. And for y'all hearing this the first time go Google it. But that was the way we built our applications. We had to segment them on the server and give them resources. Today. We have Docker containers, these little mini Oasys and Docker images. You can do it multiple times in an orchestrated manner with the power of actions enabled and Docker. It's just so incredible what you can do. And by the way, I'm showing you actions in Docker, which I hope you use because both are great and free for open source. >>But the key takeaway is really the workflow and the automation, which you certainly can do with other tools. Okay, I'm going to show you just how easy this is, because believe me, if this is something I can learn and do anybody out there can, and in this demo, I'll show you about the basic components needed to create and use a package, Docker container actions. And like I said, you won't believe how awesome the combination of Docker and actions is because you can enable your workflow to do no matter what you're trying to do in this super baby example. We're so small. You could take like 10 seconds. Like I am here creating an action due to a simple task, like pushing a message to your logs. And the cool thing is you can use it on any the bit on this one. Like I said, we're going to use push. >>You can do, uh, even to order a pizza every time you roll into production, if you wanted, but at get hub, that'd be a lot of pizzas. And the funny thing is somebody out there is actually tried this and written that action. If you haven't used Docker and actions together, check out the docs on either get hub or Docker to get you started. And a huge shout out to all those doc writers out there. I built this demo today using those instructions. And if I can do it, I know you can too, but enough yapping let's get started to save some time. And since a lot of us are Docker and get hub nerds, I've already created a repo with a Docker file. So we're going to skip that step. Next. I'm going to create an action's Yammel file. And if you don't Yammer, you know, actions, the metadata defines my important log stuff to capture and the input and my time out per parameter to pass and puts to the Docker container, get up a build image from your Docker file and run the commands in a new container. >>Using the Sigma image. The cool thing is, is you can use any Docker image in any language for your actions. It doesn't matter if it's go or whatever in today's I'm going to use a shell script and an input variable to print my important log stuff to file. And like I said, you know me, I love me some. So let's see this action in a workflow. When an action is in a private repo, like the one I demonstrating today, the action can only be used in workflows in the same repository, but public actions can be used by workflows in any repository. So unfortunately you won't get access to the super awesome action, but don't worry in the Guild marketplace, there are over 8,000 actions available, especially the most important one, that pizza action. So go try it out. Now you can do this in a couple of ways, whether you're doing it in your preferred ID or for today's demo, I'm just going to use the gooey. I'm going to navigate to my actions tab as I've done here. And I'm going to in my workflow, select new work, hello, probably load some workflows to Claire to get you started, but I'm using the one I've copied. Like I said, the lazy developer I am in. I'm going to replace it with my action. >>That's it. So now we're going to go and we're going to start our commitment new file. Now, if we go over to our actions tab, we can see the workflow in progress in my repository. I just click the actions tab. And because they wrote the actions on push, we can watch the visualization under jobs and click the job to see the important stuff we're logging in the input stamp in the printed log. And we'll just wait for this to run. Hello, Mona and boom. Just like that. It runs automatically within our action. We told it to go run as soon as the files updated because we're doing it on push merge. That's right. Folks in just a few minutes, I built an action that writes an entry to a log file every time I push. So I don't have to do it manually. In essence, with automation, you can be kind to your future self and save time and effort to focus on what really matters. >>Imagine what I could do with even a little more time, probably order all y'all pieces. That is the power of the interconnected workflow. And it's amazing. And I hope you all go try it out, but why do we care about all of that? Just like in the demo, I took a manual task with both tape, which both takes time and it's easy to forget and automated it. So I don't have to think about it. And it's executed every time consistently. That means less time for me to worry about my human errors and mistakes, and more time to focus on actually building the cool stuff that people want. Obviously, automation, developer productivity, but what is even more important to me is the developer happiness tools like BS, code actions, Docker, Heroku, and many others reduce manual work, which allows us to focus on building things that are awesome. >>And to get into that wonderful state that we call flow. According to research by UC Irvine in Humboldt university in Germany, it takes an average of 23 minutes to enter optimal creative state. What we call the flow or to reenter it after distraction like your dog on your office store. So staying in flow is so critical to developer productivity and as a developer, it just feels good to be cranking away at something with deep focus. I certainly know that I love that feeling intuitive collaboration and automation features we built in to get hub help developer, Sam flow, allowing you and your team to do so much more, to bring the benefits of automation into perspective in our annual October's report by Dr. Nicole, Forsgren. One of my buddies here at get hub, took a look at the developer productivity in the stork year. You know what we found? >>We found that public GitHub repositories that use the Automational pull requests, merge those pull requests. 1.2 times faster. And the number of pooled merged pull requests increased by 1.3 times, that is 34% more poor requests merged. And other words, automation can con can dramatically increase, but the speed and quantity of work completed in any role, just like an open source development, you'll work more efficiently with greater impact when you invest the bulk of your time in the work that adds the most value and eliminate or outsource the rest because you don't need to do it, make the machines by elaborate by leveraging automation in their workflows teams, minimize manual work and reclaim that time for innovation and maintain that state of flow with development and collaboration. More importantly, their work is more enjoyable because they're not wasting the time doing the things that the machines or robots can do for them. >>And I remember what I said at the beginning. Many of us want to be efficient, heck even lazy. So why would I spend my time doing something I can automate? Now you can read more about this research behind the art behind this at October set, get hub.com, which also includes a lot of other cool info about the open source ecosystem and how it's evolving. Speaking of the open source ecosystem we at get hub are so honored to be the home of more than 65 million developers who build software together for everywhere across the globe. Today, we're seeing software development taking shape as the world's largest team sport, where development teams collaborate, build and ship products. It's no longer a solo effort like it was for me. You don't have to take my word for it. Check out this globe. This globe shows real data. Every speck of light you see here represents a contribution to an open source project, somewhere on earth. >>These arts reach across continents, cultures, and other divides. It's distributed collaboration at its finest. 20 years ago, we had no concept of dev ops, SecOps and lots, or the new ops that are going to be happening. But today's development and ops teams are connected like ever before. This is only going to continue to evolve at a rapid pace, especially as we continue to empower the next hundred million developers, automation helps us focus on what's important and to greatly accelerate innovation. Just this past year, we saw some of the most groundbreaking technological advancements and achievements I'll say ever, including critical COVID-19 vaccine trials, as well as the first power flight on Mars. This past month, these breakthroughs were only possible because of the interconnected collaborative open source communities on get hub and the amazing tools and workflows that empower us all to create and innovate. Let's continue building, integrating, and automating. So we collectively can give developers the experience. They deserve all of the automation and beautiful eye UIs that we can muster so they can continue to build the things that truly do change the world. Thank you again for having me today, Dr. Khan, it has been a pleasure to be here with all you nerds. >>Hello. I'm Justin. Komack lovely to see you here. Talking to developers, their world is getting much more complex. Developers are being asked to do everything security ops on goal data analysis, all being put on the rockers. Software's eating the world. Of course, and this all make sense in that view, but they need help. One team. I told you it's shifted all our.net apps to run on Linux from windows, but their developers found the complexity of Docker files based on the Linux shell scripts really difficult has helped make these things easier for your teams. Your ones collaborate more in a virtual world, but you've asked us to make this simpler and more lightweight. You, the developers have asked for a paved road experience. You want things to just work with a simple options to be there, but it's not just the paved road. You also want to be able to go off-road and do interesting and different things. >>Use different components, experiments, innovate as well. We'll always offer you both those choices at different times. Different developers want different things. It may shift for ones the other paved road or off road. Sometimes you want reliability, dependability in the zone for day to day work, but sometimes you have to do something new, incorporate new things in your pipeline, build applications for new places. Then you knew those off-road abilities too. So you can really get under the hood and go and build something weird and wonderful and amazing. That gives you new options. Talk as an independent choice. We don't own the roads. We're not pushing you into any technology choices because we own them. We're really supporting and driving open standards, such as ISEI working opensource with the CNCF. We want to help you get your applications from your laptops, the clouds, and beyond, even into space. >>Let's talk about the key focus areas, that frame, what DACA is doing going forward. These are simplicity, sharing, flexibility, trusted content and care supply chain compared to building where the underlying kernel primitives like namespaces and Seagraves the original Docker CLI was just amazing Docker engine. It's a magical experience for everyone. It really brought those innovations and put them in a world where anyone would use that, but that's not enough. We need to continue to innovate. And it was trying to get more done faster all the time. And there's a lot more we can do. We're here to take complexity away from deeply complicated underlying things and give developers tools that are just amazing and magical. One of the area we haven't done enough and make things magical enough that we're really planning around now is that, you know, Docker images, uh, they're the key parts of your application, but you know, how do I do something with an image? How do I, where do I attach volumes with this image? What's the API. Whereas the SDK for this image, how do I find an example or docs in an API driven world? Every bit of software should have an API and an API description. And our vision is that every container should have this API description and the ability for you to understand how to use it. And it's all a seamless thing from, you know, from your code to the cloud local and remote, you can, you can use containers in this amazing and exciting way. >>One thing I really noticed in the last year is that companies that started off remote fast have constant collaboration. They have zoom calls, apron all day terminals, shattering that always working together. Other teams are really trying to learn how to do this style because they didn't start like that. We used to walk around to other people's desks or share services on the local office network. And it's very difficult to do that anymore. You want sharing to be really simple, lightweight, and informal. Let me try your container or just maybe let's collaborate on this together. Um, you know, fast collaboration on the analysts, fast iteration, fast working together, and he wants to share more. You want to share how to develop environments, not just an image. And we all work by seeing something someone else in our team is doing saying, how can I do that too? I can, I want to make that sharing really, really easy. Ben's going to talk about this more in the interest of one minute. >>We know how you're excited by apple. Silicon and gravis are not excited because there's a new architecture, but excited because it's faster, cooler, cheaper, better, and offers new possibilities. The M one support was the most asked for thing on our public roadmap, EFA, and we listened and share that we see really exciting possibilities, usership arm applications, all the way from desktop to production. We know that you all use different clouds and different bases have deployed to, um, you know, we work with AWS and Azure and Google and more, um, and we want to help you ship on prime as well. And we know that you use huge number of languages and the containers help build applications that use different languages for different parts of the application or for different applications, right? You can choose the best tool. You have JavaScript hat or everywhere go. And re-ask Python for data and ML, perhaps getting excited about WebAssembly after hearing about a cube con, you know, there's all sorts of things. >>So we need to make that as easier. We've been running the whole month of Python on the blog, and we're doing a month of JavaScript because we had one specific support about how do I best put this language into production of that language into production. That detail is important for you. GPS have been difficult to use. We've added GPS suppose in desktop for windows, but we know there's a lot more to do to make the, how multi architecture, multi hardware, multi accelerator world work better and also securely. Um, so there's a lot more work to do to support you in all these things you want to do. >>How do we start building a tenor has applications, but it turns out we're using existing images as components. I couldn't assist survey earlier this year, almost half of container image usage was public images rather than private images. And this is growing rapidly. Almost all software has open source components and maybe 85% of the average application is open source code. And what you're doing is taking whole container images as modules in your application. And this was always the model with Docker compose. And it's a model that you're already et cetera, writing you trust Docker, official images. We know that they might go to 25% of poles on Docker hub and Docker hub provides you the widest choice and the best support that trusted content. We're talking to people about how to make this more helpful. We know, for example, that winter 69 four is just showing us as support, but the image doesn't yet tell you that we're working with canonical to improve messaging from specific images about left lifecycle and support. >>We know that you need more images, regularly updated free of vulnerabilities, easy to use and discover, and Donnie and Marie neuro, going to talk about that more this last year, the solar winds attack has been in the, in the news. A lot, the software you're using and trusting could be compromised and might be all over your organization. We need to reduce the risk of using vital open-source components. We're seeing more software supply chain attacks being targeted as the supply chain, because it's often an easier place to attack and production software. We need to be able to use this external code safely. We need to, everyone needs to start from trusted sources like photography images. They need to scan for known vulnerabilities using Docker scan that we built in partnership with sneak and lost DockerCon last year, we need just keep updating base images and dependencies, and we'll, we're going to help you have the control and understanding about your images that you need to do this. >>And there's more, we're also working on the nursery V2 project in the CNCF to revamp container signings, or you can tell way or software comes from we're working on tooling to make updates easier, and to help you understand and manage all the principals carrier you're using security is a growing concern for all of us. It's really important. And we're going to help you work with security. We can't achieve all our dreams, whether that's space travel or amazing developer products ever see without deep partnerships with our community to cloud is RA and the cloud providers aware most of you ship your occasion production and simple routes that take your work and deploy it easily. Reliably and securely are really important. Just get into production simply and easily and securely. And we've done a bunch of work on that. And, um, but we know there's more to do. >>The CNCF on the open source cloud native community are an amazing ecosystem of creators and lovely people creating an amazing strong community and supporting a huge amount of innovation has its roots in the container ecosystem and his dreams beyond that much of the innovation is focused around operate experience so far, but developer experience is really a growing concern in that community as well. And we're really excited to work on that. We also uses appraiser tool. Then we know you do, and we know that you want it to be easier to use in your environment. We just shifted Docker hub to work on, um, Kubernetes fully. And, um, we're also using many of the other projects are Argo from atheists. We're spending a lot of time working with Microsoft, Amazon right now on getting natural UV to ready to ship in the next few. That's a really detailed piece of collaboration we've been working on for a long term. Long time is really important for our community as the scarcity of the container containers and, um, getting content for you, working together makes us stronger. Our community is made up of all of you have. Um, it's always amazing to be reminded of that as a huge open source community that we already proud to work with. It's an amazing amount of innovation that you're all creating and where perhaps it, what with you and share with you as well. Thank you very much. And thank you for being here. >>Really excited to talk to you today and share more about what Docker is doing to help make you faster, make your team faster and turn your application delivery into something that makes you a 10 X team. What we're hearing from you, the developers using Docker everyday fits across three common themes that we hear consistently over and over. We hear that your time is super important. It's critical, and you want to move faster. You want your tools to get out of your way, and instead to enable you to accelerate and focus on the things you want to be doing. And part of that is that finding great content, great application components that you can incorporate into your apps to move faster is really hard. It's hard to discover. It's hard to find high quality content that you can trust that, you know, passes your test and your configuration needs. >>And it's hard to create good content as well. And you're looking for more safety, more guardrails to help guide you along that way so that you can focus on creating value for your company. Secondly, you're telling us that it's a really far to collaborate effectively with your team and you want to do more, to work more effectively together to help your tools become more and more seamless to help you stay in sync, both with yourself across all of your development environments, as well as with your teammates so that you can more effectively collaborate together. Review each other's work, maintain things and keep them in sync. And finally, you want your applications to run consistently in every single environment, whether that's your local development environment, a cloud-based development environment, your CGI pipeline, or the cloud for production, and you want that micro service to provide that consistent experience everywhere you go so that you have similar tools, similar environments, and you don't need to worry about things getting in your way, but instead things make it easy for you to focus on what you wanna do and what Docker is doing to help solve all of these problems for you and your colleagues is creating a collaborative app dev platform. >>And this collaborative application development platform consists of multiple different pieces. I'm not going to walk through all of them today, but the overall view is that we're providing all the tooling you need from the development environment, to the container images, to the collaboration services, to the pipelines and integrations that enable you to focus on making your applications amazing and changing the world. If we start zooming on a one of those aspects, collaboration we hear from developers regularly is that they're challenged in synchronizing their own setups across environments. They want to be able to duplicate the setup of their teammates. Look, then they can easily get up and running with the same applications, the same tooling, the same version of the same libraries, the same frameworks. And they want to know if their applications are good before they're ready to share them in an official space. >>They want to collaborate on things before they're done, rather than feeling like they have to officially published something before they can effectively share it with others to work on it, to solve this. We're thrilled today to announce Docker, dev environments, Docker, dev environments, transform how your team collaborates. They make creating, sharing standardized development environments. As simple as a Docker poll, they make it easy to review your colleagues work without affecting your own work. And they increase the reproducibility of your own work and decreased production issues in doing so because you've got consistent environments all the way through. Now, I'm going to pass it off to our principal product manager, Ben Gotch to walk you through more detail on Docker dev environments. >>Hi, I'm Ben. I work as a principal program manager at DACA. One of the areas that doc has been looking at to see what's hard today for developers is sharing changes that you make from the inner loop where the inner loop is a better development, where you write code, test it, build it, run it, and ultimately get feedback on those changes before you merge them and try and actually ship them out to production. Most amount of us build this flow and get there still leaves a lot of challenges. People need to jump between branches to look at each other's work. Independence. Dependencies can be different when you're doing that and doing this in this new hybrid wall of work. Isn't any easier either the ability to just save someone, Hey, come and check this out. It's become much harder. People can't come and sit down at your desk or take your laptop away for 10 minutes to just grab and look at what you're doing. >>A lot of the reason that development is hard when you're remote, is that looking at changes and what's going on requires more than just code requires all the dependencies and everything you've got set up and that complete context of your development environment, to understand what you're doing and solving this in a remote first world is hard. We wanted to look at how we could make this better. Let's do that in a way that let you keep working the way you do today. Didn't want you to have to use a browser. We didn't want you to have to use a new idea. And we wanted to do this in a way that was application centric. We wanted to let you work with all the rest of the application already using C for all the services and all those dependencies you need as part of that. And with that, we're excited to talk more about docket developer environments, dev environments are new part of the Docker experience that makes it easier you to get started with your whole inner leap, working inside a container, then able to share and collaborate more than just the code. >>We want it to enable you to share your whole modern development environment, your whole setup from DACA, with your team on any operating system, we'll be launching a limited beta of dev environments in the coming month. And a GA dev environments will be ID agnostic and supporting composts. This means you'll be able to use an extend your existing composed files to create your own development environment in whatever idea, working in dev environments designed to be local. First, they work with Docker desktop and say your existing ID, and let you share that whole inner loop, that whole development context, all of your teammates in just one collect. This means if you want to get feedback on the working progress change or the PR it's as simple as opening another idea instance, and looking at what your team is working on because we're using compose. You can just extend your existing oppose file when you're already working with, to actually create this whole application and have it all working in the context of the rest of the services. >>So it's actually the whole environment you're working with module one service that doesn't really understand what it's doing alone. And with that, let's jump into a quick demo. So you can see here, two dev environments up and running. First one here is the same container dev environment. So if I want to go into that, let's see what's going on in the various code button here. If that one open, I can get straight into my application to start making changes inside that dev container. And I've got all my dependencies in here, so I can just run that straight in that second application I have here is one that's opened up in compose, and I can see that I've also got my backend, my front end and my database. So I've got all my services running here. So if I want, I can open one or more of these in a dev environment, meaning that that container has the context that dev environment has the context of the whole application. >>So I can get back into and connect to all the other services that I need to test this application properly, all of them, one unit. And then when I've made my changes and I'm ready to share, I can hit my share button type in the refund them on to share that too. And then give that image to someone to get going, pick that up and just start working with that code and all my dependencies, simple as putting an image, looking ahead, we're going to be expanding development environments, more of your dependencies for the whole developer worst space. We want to look at backing up and letting you share your volumes to make data science and database setups more repeatable and going. I'm still all of this under a single workspace for your team containing images, your dev environments, your volumes, and more we've really want to allow you to create a fully portable Linux development environment. >>So everyone you're working with on any operating system, as I said, our MVP we're coming next month. And that was for vs code using their dev container primitive and more support for other ideas. We'll follow to find out more about what's happening and what's coming up next in the future of this. And to actually get a bit of a deeper dive in the experience. Can we check out the talk I'm doing with Georgie and girl later on today? Thank you, Ben, amazing story about how Docker is helping to make developer teams more collaborative. Now I'd like to talk more about applications while the dev environment is like the workbench around what you're building. The application itself has all the different components, libraries, and frameworks, and other code that make up the application itself. And we hear developers saying all the time things like, how do they know if their images are good? >>How do they know if they're secure? How do they know if they're minimal? How do they make great images and great Docker files and how do they keep their images secure? And up-to-date on every one of those ties into how do I create more trust? How do I know that I'm building high quality applications to enable you to do this even more effectively than today? We are pleased to announce the DACA verified polisher program. This broadens trusted content by extending beyond Docker official images, to give you more and more trusted building blocks that you can incorporate into your applications. It gives you confidence that you're getting what you expect because Docker verifies every single one of these publishers to make sure they are who they say they are. This improves our secure supply chain story. And finally it simplifies your discovery of the best building blocks by making it easy for you to find things that you know, you can trust so that you can incorporate them into your applications and move on and on the right. You can see some examples of the publishers that are involved in Docker, official images and our Docker verified publisher program. Now I'm pleased to introduce you to marina. Kubicki our senior product manager who will walk you through more about what we're doing to create a better experience for you around trust. >>Thank you, Dani, >>Mario Andretti, who is a famous Italian sports car driver. One said that if everything feels under control, you're just not driving. You're not driving fast enough. Maya Andretti is not a software developer and a software developers. We know that no matter how fast we need to go in order to drive the innovation that we're working on, we can never allow our applications to spin out of control and a Docker. As we continue talking to our, to the developers, what we're realizing is that in order to reach that speed, the developers are the, the, the development community is looking for the building blocks and the tools that will, they will enable them to drive at the speed that they need to go and have the trust in those building blocks. And in those tools that they will be able to maintain control over their applications. So as we think about some of the things that we can do to, to address those concerns, uh, we're realizing that we can pursue them in a number of different venues, including creating reliable content, including creating partnerships that expands the options for the reliable content. >>Um, in order to, in a we're looking at creating integrations, no link security tools, talk about the reliable content. The first thing that comes to mind are the Docker official images, which is a program that we launched several years ago. And this is a set of curated, actively maintained, open source images that, uh, include, uh, operating systems and databases and programming languages. And it would become immensely popular for, for, for creating the base layers of, of the images of, of the different images, images, and applications. And would we realizing that, uh, many developers are, instead of creating something from scratch, basically start with one of the official images for their basis, and then build on top of that. And this program has become so popular that it now makes up a quarter of all of the, uh, Docker poles, which essentially ends up being several billion pulse every single month. >>As we look beyond what we can do for the open source. Uh, we're very ability on the open source, uh, spectrum. We are very excited to announce that we're launching the Docker verified publishers program, which is continuing providing the trust around the content, but now working with, uh, some of the industry leaders, uh, in multiple, in multiple verticals across the entire technology technical spec, it costs entire, uh, high tech in order to provide you with more options of the images that you can use for building your applications. And it still comes back to trust that when you are searching for content in Docker hub, and you see the verified publisher badge, you know, that this is, this is the content that, that is part of the, that comes from one of our partners. And you're not running the risk of pulling the malicious image from an employee master source. >>As we look beyond what we can do for, for providing the reliable content, we're also looking at some of the tools and the infrastructure that we can do, uh, to create a security around the content that you're creating. So last year at the last ad, the last year's DockerCon, we announced partnership with sneak. And later on last year, we launched our DACA, desktop and Docker hub vulnerability scans that allow you the options of writing scans in them along multiple points in your dev cycle. And in addition to providing you with information on the vulnerability on, on the vulnerabilities, in, in your code, uh, it also provides you with a guidance on how to re remediate those vulnerabilities. But as we look beyond the vulnerability scans, we're also looking at some of the other things that we can do, you know, to, to, to, uh, further ensure that the integrity and the security around your images, your images, and with that, uh, later on this year, we're looking to, uh, launch the scope, personal access tokens, and instead of talking about them, I will simply show you what they look like. >>So if you can see here, this is my page in Docker hub, where I've created a four, uh, tokens, uh, read-write delete, read, write, read only in public read in public creeper read only. So, uh, earlier today I went in and I, I logged in, uh, with my read only token. And when you see, when I'm going to pull an image, it's going to allow me to pull an image, not a problem success. And then when I do the next step, I'm going to ask to push an image into the same repo. Uh, would you see is that it's going to give me an error message saying that they access is denied, uh, because there is an additional authentication required. So these are the things that we're looking to add to our roadmap. As we continue thinking about the things that we can do to provide, um, to provide additional building blocks, content, building blocks, uh, and, and, and tools to build the trust so that our DACA developer and skinned code faster than Mario Andretti could ever imagine. Uh, thank you to >>Thank you, marina. It's amazing what you can do to improve the trusted content so that you can accelerate your development more and move more quickly, move more collaboratively and build upon the great work of others. Finally, we hear over and over as that developers are working on their applications that they're looking for, environments that are consistent, that are the same as production, and that they want their applications to really run anywhere, any environment, any architecture, any cloud one great example is the recent announcement of apple Silicon. We heard from developers on uproar that they needed Docker to be available for that architecture before they could add those to it and be successful. And we listened. And based on that, we are pleased to share with you Docker, desktop on apple Silicon. This enables you to run your apps consistently anywhere, whether that's developing on your team's latest dev hardware, deploying an ARM-based cloud environments and having a consistent architecture across your development and production or using multi-year architecture support, which enables your whole team to collaborate on its application, using private repositories on Docker hub, and thrilled to introduce you to Hughie cower, senior director for product management, who will walk you through more of what we're doing to create a great developer experience. >>Senior director of product management at Docker. And I'd like to jump straight into a demo. This is the Mac mini with the apple Silicon processor. And I want to show you how you can now do an end-to-end arm workflow from my M one Mac mini to raspberry PI. As you can see, we have vs code and Docker desktop installed on a, my, the Mac mini. I have a small example here, and I have a raspberry PI three with an led strip, and I want to turn those LEDs into a moving rainbow. This Dockerfile here, builds the application. We build the image with the Docker, build X command to make the image compatible for all raspberry pies with the arm. 64. Part of this build is built with the native power of the M one chip. I also add the push option to easily share the image with my team so they can give it a try to now Dr. >>Creates the local image with the application and uploads it to Docker hub after we've built and pushed the image. We can go to Docker hub and see the new image on Docker hub. You can also explore a variety of images that are compatible with arm processors. Now let's go to the raspberry PI. I have Docker already installed and it's running Ubuntu 64 bit with the Docker run command. I can run the application and let's see what will happen from there. You can see Docker is downloading the image automatically from Docker hub and when it's running, if it's works right, there are some nice colors. And with that, if we have an end-to-end workflow for arm, where continuing to invest into providing you a great developer experience, that's easy to install. Easy to get started with. As you saw in the demo, if you're interested in the new Mac, mini are interested in developing for our platforms in general, we've got you covered with the same experience you've come to expect from Docker with over 95,000 arm images on hub, including many Docker official images. >>We think you'll find what you're looking for. Thank you again to the community that helped us to test the tech previews. We're so delighted to hear when folks say that the new Docker desktop for apple Silicon, it just works for them, but that's not all we've been working on. As Dani mentioned, consistency of developer experience across environments is so important. We're introducing composed V2 that makes compose a first-class citizen in the Docker CLI you no longer need to install a separate composed biter in order to use composed, deploying to production is simpler than ever with the new compose integration that enables you to deploy directly to Amazon ECS or Azure ACI with the same methods you use to run your application locally. If you're interested in running slightly different services, when you're debugging versus testing or, um, just general development, you can manage that all in one place with the new composed service to hear more about what's new and Docker desktop, please join me in the three 15 breakout session this afternoon. >>And now I'd love to tell you a bit more about bill decks and convince you to try it. If you haven't already it's our next gen build command, and it's no longer experimental as shown in the demo with built X, you'll be able to do multi architecture builds, share those builds with your team and the community on Docker hub. With build X, you can speed up your build processes with remote caches or build all the targets in your composed file in parallel with build X bake. And there's so much more if you're using Docker, desktop or Docker, CE you can use build X checkout tonus is talk this afternoon at three 45 to learn more about build X. And with that, I hope everyone has a great Dr. Khan and back over to you, Donnie. >>Thank you UA. It's amazing to hear about what we're doing to create a better developer experience and make sure that Docker works everywhere you need to work. Finally, I'd like to wrap up by showing you everything that we've announced today and everything that we've done recently to make your lives better and give you more and more for the single price of your Docker subscription. We've announced the Docker verified publisher program we've announced scoped personal access tokens to make it easier for you to have a secure CCI pipeline. We've announced Docker dev environments to improve your collaboration with your team. Uh, we shared with you Docker, desktop and apple Silicon, to make sure that, you know, Docker runs everywhere. You need it to run. And we've announced Docker compose version two, finally making it a first-class citizen amongst all the other great Docker tools. And we've done so much more recently as well from audit logs to advanced image management, to compose service profiles, to improve where you can run Docker more easily. >>Finally, as we look forward, where we're headed in the upcoming year is continuing to invest in these themes of helping you build, share, and run modern apps more effectively. We're going to be doing more to help you create a secure supply chain with which only grows more and more important as time goes on. We're going to be optimizing your update experience to make sure that you can easily understand the current state of your application, all its components and keep them all current without worrying about breaking everything as you're doing. So we're going to make it easier for you to synchronize your work. Using cloud sync features. We're going to improve collaboration through dev environments and beyond, and we're going to do make it easy for you to run your microservice in your environments without worrying about things like architecture or differences between those environments. Thank you so much. I'm thrilled about what we're able to do to help make your lives better. And now you're going to be hearing from one of our customers about what they're doing to launch their business with Docker >>I'm Matt Falk, I'm the head of engineering and orbital insight. And today I want to talk to you a little bit about data from space. So who am I like many of you, I'm a software developer and a software developer about seven companies so far, and now I'm a head of engineering. So I spend most of my time doing meetings, but occasionally I'll still spend time doing design discussions, doing code reviews. And in my free time, I still like to dabble on things like project oiler. So who's Oberlin site. What do we do? Portal insight is a large data supplier and analytics provider where we take data geospatial data anywhere on the planet, any overhead sensor, and translate that into insights for the end customer. So specifically we have a suite of high performance, artificial intelligence and machine learning analytics that run on this geospatial data. >>And we build them to specifically determine natural and human service level activity anywhere on the planet. What that really means is we take any type of data associated with a latitude and longitude and we identify patterns so that we can, so we can detect anomalies. And that's everything that we do is all about identifying those patterns to detect anomalies. So more specifically, what type of problems do we solve? So supply chain intelligence, this is one of the use cases that we we'd like to talk about a lot. It's one of our main primary verticals that we go after right now. And as Scott mentioned earlier, this had a huge impact last year when COVID hit. So specifically supply chain intelligence is all about identifying movement patterns to and from operating facilities to identify changes in those supply chains. How do we do this? So for us, we can do things where we track the movement of trucks. >>So identifying trucks, moving from one location to another in aggregate, same thing we can do with foot traffic. We can do the same thing for looking at aggregate groups of people moving from one location to another and analyzing their patterns of life. We can look at two different locations to determine how people are moving from one location to another, or going back and forth. All of this is extremely valuable for detecting how a supply chain operates and then identifying the changes to that supply chain. As I said last year with COVID, everything changed in particular supply chains changed incredibly, and it was hugely important for customers to know where their goods or their products are coming from and where they were going, where there were disruptions in their supply chain and how that's affecting their overall supply and demand. So to use our platform, our suite of tools, you can start to gain a much better picture of where your suppliers or your distributors are going from coming from or going to. >>So what's our team look like? So my team is currently about 50 engineers. Um, we're spread into four different teams and the teams are structured like this. So the first team that we have is infrastructure engineering and this team largely deals with deploying our Dockers using Kubernetes. So this team is all about taking Dockers, built by other teams, sometimes building the Dockers themselves and putting them into our production system, our platform engineering team, they produce these microservices. So they produce microservice, Docker images. They develop and test with them locally. Their entire environments are dockerized. They produce these doctors, hand them over to him for infrastructure engineering to be deployed. Similarly, our product engineering team does the same thing. They develop and test with Dr. Locally. They also produce a suite of Docker images that the infrastructure team can then deploy. And lastly, we have our R and D team, and this team specifically produces machine learning algorithms using Nvidia Docker collectively, we've actually built 381 Docker repositories and 14 million. >>We've had 14 million Docker pools over the lifetime of the company, just a few stats about us. Um, but what I'm really getting to here is you can see actually doctors becoming almost a form of communication between these teams. So one of the paradigms in software engineering that you're probably familiar with encapsulation, it's really helpful for a lot of software engineering problems to break the problem down, isolate the different pieces of it and start building interfaces between the code. This allows you to scale different pieces of the platform or different pieces of your code in different ways that allows you to scale up certain pieces and keep others at a smaller level so that you can meet customer demands. And for us, one of the things that we can largely do now is use Dockers as that interface. So instead of having an entire platform where all teams are talking to each other, and everything's kind of, mishmashed in a monolithic application, we can now say this team is only able to talk to this team by passing over a particular Docker image that defines the interface of what needs to be built before it passes to the team and really allows us to scalp our development and be much more efficient. >>Also, I'd like to say we are hiring. Um, so we have a number of open roles. We have about 30 open roles in our engineering team that we're looking to fill by the end of this year. So if any of this sounds really interesting to you, please reach out after the presentation. >>So what does our platform do? Really? Our platform allows you to answer any geospatial question, and we do this at three different inputs. So first off, where do you want to look? So we did this as what we call an AOI or an area of interest larger. You can think of this as a polygon drawn on the map. So we have a curated data set of almost 4 million AOIs, which you can go and you can search and use for your analysis, but you're also free to build your own. Second question is what you want to look for. We do this with the more interesting part of our platform of our machine learning and AI capabilities. So we have a suite of algorithms that automatically allow you to identify trucks, buildings, hundreds of different types of aircraft, different types of land use, how many people are moving from one location to another different locations that people in a particular area are moving to or coming from all of these different analyses or all these different analytics are available at the click of a button, and then determine what you want to look for. >>Lastly, you determine when you want to find what you're looking for. So that's just, uh, you know, do you want to look for the next three hours? Do you want to look for the last week? Do you want to look every month for the past two, whatever the time cadence is, you decide that you hit go and out pops a time series, and that time series tells you specifically where you want it to look what you want it to look for and how many, or what percentage of the thing you're looking for appears in that area. Again, we do all of this to work towards patterns. So we use all this data to produce a time series from there. We can look at it, determine the patterns, and then specifically identify the anomalies. As I mentioned with supply chain, this is extremely valuable to identify where things change. So we can answer these questions, looking at a particular operating facility, looking at particular, what is happening with the level of activity is at that operating facility where people are coming from, where they're going to, after visiting that particular facility and identify when and where that changes here, you can just see it's a picture of our platform. It's actually showing all the devices in Manhattan, um, over a period of time. And it's more of a heat map view. So you can actually see the hotspots in the area. >>So really the, and this is the heart of the talk, but what happened in 2020? So for men, you know, like many of you, 2020 was a difficult year COVID hit. And that changed a lot of what we're doing, not from an engineering perspective, but also from an entire company perspective for us, the motivation really became to make sure that we were lowering our costs and increasing innovation simultaneously. Now those two things often compete with each other. A lot of times you want to increase innovation, that's going to increase your costs, but the challenge last year was how to do both simultaneously. So here's a few stats for you from our team. In Q1 of last year, we were spending almost $600,000 per month on compute costs prior to COVID happening. That wasn't hugely a concern for us. It was a lot of money, but it wasn't as critical as it was last year when we really needed to be much more efficient. >>Second one is flexibility for us. We were deployed on a single cloud environment while we were cloud thought ready, and that was great. We want it to be more flexible. We want it to be on more cloud environments so that we could reach more customers. And also eventually get onto class side networks, extending the base of our customers as well from a custom analytics perspective. This is where we get into our traction. So last year, over the entire year, we computed 54,000 custom analytics for different users. We wanted to make sure that this number was steadily increasing despite us trying to lower our costs. So we didn't want the lowering cost to come as the sacrifice of our user base. Lastly, of particular percentage here that I'll say definitely needs to be improved is 75% of our projects never fail. So this is where we start to get into a bit of stability of our platform. >>Now I'm not saying that 25% of our projects fail the way we measure this is if you have a particular project or computation that runs every day and any one of those runs sale account, that is a failure because from an end-user perspective, that's an issue. So this is something that we know we needed to improve on and we needed to grow and make our platform more stable. I'm going to something that we really focused on last year. So where are we now? So now coming out of the COVID valley, we are starting to soar again. Um, we had, uh, back in April of last year, we had the entire engineering team. We actually paused all development for about four weeks. You had everyone focused on reducing our compute costs in the cloud. We got it down to 200 K over the period of a few months. >>And for the next 12 months, we hit that number every month. This is huge for us. This is extremely important. Like I said, in the COVID time period where costs and operating efficiency was everything. So for us to do that, that was a huge accomplishment last year and something we'll keep going forward. One thing I would actually like to really highlight here, two is what allowed us to do that. So first off, being in the cloud, being able to migrate things like that, that was one thing. And we were able to use there's different cloud services in a more particular, in a more efficient way. We had a very detailed tracking of how we were spending things. We increased our data retention policies. We optimized our processing. However, one additional piece was switching to new technologies on, in particular, we migrated to get lab CICB. >>Um, and this is something that the costs we use Docker was extremely, extremely easy. We didn't have to go build new new code containers or repositories or change our code in order to do this. We were simply able to migrate the containers over and start using a new CIC so much. In fact, that we were able to do that migration with three engineers in just two weeks from a cloud environment and flexibility standpoint, we're now operating in two different clouds. We were able to last night, I've over the last nine months to operate in the second cloud environment. And again, this is something that Docker helped with incredibly. Um, we didn't have to go and build all new interfaces to all new, different services or all different tools in the next cloud provider. All we had to do was build a base cloud infrastructure that ups agnostic the way, all the different details of the cloud provider. >>And then our doctors just worked. We can move them to another environment up and running, and our platform was ready to go from a traction perspective. We're about a third of the way through the year. At this point, we've already exceeded the amount of customer analytics we produce last year. And this is thanks to a ton more albums, that whole suite of new analytics that we've been able to build over the past 12 months and we'll continue to build going forward. So this is really, really great outcome for us because we were able to show that our costs are staying down, but our analytics and our customer traction, honestly, from a stability perspective, we improved from 75% to 86%, not quite yet 99 or three nines or four nines, but we are getting there. Um, and this is actually thanks to really containerizing and modularizing different pieces of our platform so that we could scale up in different areas. This allowed us to increase that stability. This piece of the code works over here, toxin an interface to the rest of the system. We can scale this piece up separately from the rest of the system, and that allows us much more easily identify issues in the system, fix those and then correct the system overall. So basically this is a summary of where we were last year, where we are now and how much more successful we are now because of the issues that we went through last year and largely brought on by COVID. >>But that this is just a screenshot of the, our, our solution actually working on supply chain. So this is in particular, it is showing traceability of a distribution warehouse in salt lake city. It's right in the center of the screen here. You can see the nice kind of orange red center. That's a distribution warehouse and all the lines outside of that, all the dots outside of that are showing where people are, where trucks are moving from that location. So this is really helpful for supply chain companies because they can start to identify where their suppliers are, are coming from or where their distributors are going to. So with that, I want to say, thanks again for following along and enjoy the rest of DockerCon.

>> Announcer: From around the globe, it's theCUBE with digital coverage of DockerCon Live 2020. Brought to you by Docker and its ecosystem partners. >> Okay Jenny, great to see you again. >> Good to see you. >> James Governor, nail on the Keynote there. Chat was phenomenal. That was pre-recorded but James is also in the chat stream. A lot of good conversations. That hit home for me that keynote. One, because memory lane was going down right into the 80s when it was a revolution. And we got him in the green room here. James Governor, welcome. >> James is here, hi James. >> Here we go. >> Fresh off the keynote. >> It's always a revolution. (John laughs) >> Well, in the 80s, I used to love your talk. A couple of key points I want to share and get your thoughts on was just to some highlights for the crowd is one, you walk through. Some of the key inflection points that I think were instrumental and probably some other ones depending on your perspective of where you were in the industry at that time. Whether you were a systems programmer or a networking guy, there was a proprietary world and it was a revolution back then. And UNIX was owned by AT&T if no one remembers. You couldn't even use the word. You had to trade market. So we actually had to call it XINU which is UNIX spelled backwards in all the text and whatnot. And even open source software freeware was kind of illegal. MIT did some work, Northeastern and Berkeley and other schools. It was radical back then so-- >> Yeah, we've come a long way for sure. I think that for me that was one of the things that I wanted to really point to in the keynote was that yes we have definitely come a long way and development culture is about open culture. >> I think the thing that I like to point out especially hate to sound like I'm old but I am. But I lived through that and the younger generation coming and have all these new tools. And I got to say not that I walked through to school in the snow with no shoes on but it's a pretty cool developer environment now. But remember things were proprietary back then. If you start to see the tea leaves now, I look at the world, you see these silos. You see silos that's kind of, they're not nestle proprietary but they might necessarily be open. So you kind of have a glimpse of open source on these projects and these companies. Whether they're tech companies, it feels open but it might not be. It could be walled garden. It could be data being hoarded. So as data opens up, this is interesting to me because I want to get your thoughts on this because in a way it feels proprietary but technically it's not proprietary. What's your thoughts on this? Because this is going to be the next 20 years of evolution. What's your thoughts? >> I think the productivity wins. Whoever packages technology in a way that makes it most productive for people. That's what wins. And open source, what's productive. It is very accessible. It enabled new waves. Get installed and you've got a package from... You got access to just a world of open-source. A world of software that was a big revolution. And I guess the cloud sort of came next and I think that's been one of the big shifts. You talk about proprietary. What matters is how easy you make things to people to do their work. And in that regard, obviously Amazon is in fact a bigger distribution network. Makes technology super consumable by so many people. I guess I would say that open is good and important but it's not the only thing. As you say, data is a lock-in and it's right and people are choosing services that make them productive. Nobody worries about whether Amazon Lambda is proprietary. They just know that they can build companies or businesses or business processes on it. >> You know it's interesting back in the day just to kind of segue with the next topic. We were fighting proprietary operating systems, UNIX and others. We're also fighting for proprietary Network protocol stacks. SNA was owned by IBM. DECnet was digital, the number one network. And then TCP/IP and OpenSan's interconnect came out. That's the OSI model for us old ones. That set the table. That changed the face of everything. It really enabled a lot. So when I see containers, what Docker did early on the pioneering phases of Docker containers, it unleashed a new reality of coolness and scale and capabilities. And then in comes Kubernetes and in comes micro services. So this path is showing some real strength for new kinds of capabilities. So how does a developer navigate all this because data lock-in does it a data plane seems to be a control point. What are we fighting now in your opinion? shouldn't say we're fighting but what are we trying to avoid if operating systems was for closing opportunities and network protocol stacks before closing in the past? What do you see as barriers that need to be broken down in the open source world around going down this great path of micro services, decomposed applications, highly cohesive architectures? >> Honestly there's enough work to be getting on with without like fighting someone in that regard. I mean we're fighting against technical debt. I just don't think that people are serrated about fighting against proprietary anymore. I think that's less than a concern. Open-source technology is great. It's how most work gets done in our industry today. So you mentioned Kubernetes and certainly Docker. Though we did a phenomenal job of packaging up and experience that map to see CICD. That map to the developer workplace people like do. Phenomenal job and I think that for me at least when I look at where we are as an industry, it's all about productivity. So there are plenty of interesting new platforms. I think in my keynote, that's my question. I'm less interested in microservices than I am in distributed work. I'm interested in one of the tools that are going to enable us to become more productive, solve more problems, build more applications and get better at building software. So I think that's my sort of focus. There will always be lock-in. And I think you will also have technologies mitigate against that. I mean clear messages today from Docker about supporting multiple clouds. For a while at least multiclouds seem like something only the kind waivers were interested in but increasingly we're seeing organizations where that is definitely part of how they're using the cloud. And again I think very often it's within specific areas. And so we see organizations that are using particular clouds for different things. And we'll see more of that. >> And the productivity. I love the passion, love that in the keynote. That was loud and clear. Two key points I want to get your reaction on that. You mentioned one was inclusion. Including more people, not seeing news. It's kind of imperative. And also virtual work environments, virtual events. You kind of made a highlight there. So again people are distributed remote first. It's an opportunity to be productive. Can you share your thoughts on those two points? One is, as we're distributed, that's going to open the aperture of more engagement. More people coming in. So code of conduct not as a file you must read or some rule. Culturally embracing a code of conduct. And then also, virtual events, virtual groups convening like we're doing here. >> Yeah I mean for me at least Allison McMillan from github and she just gave such a great demo at the recent sunlight event where she finished and she was like, it was all about, I want to be able to put the kids to bed for a nap and then go code. And I think that's sort of thinking people band around the phrase ruling this together but I mean certainly parenting is a team sport. But I think it's interesting we're not welcome. It was interesting that was looking at the chat, going through, I was being accused of being woke. I was being accused of being a social justice warrior. But look at the math. The graph is pretty clear. Women are not welcomed in tech. And that means we're wasting 50% of available resource to us. And we're treating people like shit. So I thought I underplayed that in the talk actually. Something like, "Oh, why is he complaining about Linus?" Well, the fact is that Linus himself admitted he needed to change his persona in order to just be more modern and welcoming in terms of building software and building communities. So look we've got people from around the world. Different cultural norms. All of the women I know who work in tech suffer so much from effectively daily harassment. Their bonafides are challenged. These are things that we need to change because women are brilliant. I'm not letting you signaling or maybe I am. The fact is that women are amazing at software and we do a terrible job of supporting them. So women of other nationalities, we're not going to be traveling as much. I think you can also grow. No we can't keep flying around as much. Make an industry where single parents can participate more effectively. Where we could take advantage of that. There're 200 million people in Nigeria. That hunger to engage. We won't even give them a visa and then we may not be treating them right. I just think we need an industry reset. I think from a we need to travel less. We need to do better work. And we need to be more welcoming in order that that could be the case. >> Yeah, there's no doubt a reset is here and you look at the COVID crisis is forcing that function there because one, people are resetting and reinventing and trying to figure out a growth strategy. Whether it's a business or teams. And what's interesting is new roles and new responsibilities is going to emerge and I think you're right about the women in tech. I completely agree and have evidence myself and reported on it ad nauseam. But the thing is data trumps opinion. And the data is clear on this issue. So if anyone will call you a social justice warrior I just say pound sand and tell them that go on their way. And just look at the data and clear. And also the field is getting wider. When I was in computer science major back in the day, it was male-dominated yes but it was very narrow. Wasn't as broad as it is now. You can do things so much more and in fact in Kelsey Hightower's talk, he talks to persona developers. The ones that love to learn and ones that don't want to learn anything. Just want to code and do their thing. And ones that care about just app development and ones that just want to get in and sling k-8 around like it's nobody's business or work with APIs, work with infrastructure. Some just want to write code. So there's more and more surface area in computer science and coding. Or not even computer science, it's just coding, developing. >> Well, I mean it's a bigger industry. We've got clearly all sorts of challenges that need to be solved. And the services that we've got available are incredible. I mean if you look at the work of companies like Netlify in terms of developer experience. You look at the emergence of JamStack and the productivity that we're seeing there, it's a really exciting time in the industry. >> No doubt about that. >> And as I say I mean it's an exciting time. It's a scary time. But I think that we're moving to a world of more distributed work. And that's my point about open source and working on code bases from different places and what the CapCloud can enable. We can work in a different way and we don't all need to be in San Francisco, London, or Berlin as I said in the Keynote. >> I love the vision there and the passion. I totally agree with it. I think that's a whole another distributed paradigm that's going to move up the stack if you will and software. I think it's going to be codified in cloud native and cloud scale creates new services. I mean it's the virtual world. You mentioned virtual events. Groups convening like the 67,000 people coming together virtually here at DockerCon. Large, small one-on-ones group dynamics are a piece of it. So share your thoughts on virtual events and certainly it's people are now just kicking the tires, learning. You do a zoom, you do a livestream. You do some chat. It's going to evolve and I think it's going to look more like a CICD pipeline and anything else. As you start to bring media together, we get 43 sessions here. Why not make it a hundred sessions? So I think this is going to be one of those learning environments where it's not linear, it's different. What's your vision of all this if you had to give advice for the folks out there? Not event plans, with people who want to gather groups and be productive. What's your thinking on this? >> Well, it sort of has to happen. I mean there are a lot of people doing good work in this regard. Patrick Dubois, founder of DevOps days. He's doing some brilliant work delineating. Just what are all the different platforms? What does the streaming platform look like that you can use? Obviously you've got one here with theCUBE. Yeah, I mean I think the numbers are pretty clear. I mean Microsoft Build had 245,000 registered attendees and I think something that might have been to begin. The patterns are slightly different. It's not like they're going to be there the whole time but the opportunity to meet people where they are, I think is something that we shouldn't ignore. Particularly in a world not everyone again has the privilege of being able to travel. You're in a different country or as I say perhaps your life circumstances mean you can't travel. From an accessibility perspective, clearly virtual events offer an opportunity that we haven't fully nailed. I think Microsoft performance in this regard has been super interesting. They were already moving that way and Kobe just slammed it up to another level. What they did with Build recently was actually, I mean they're a media company, right? But certainly developed a focused media company. So I think you'll be okay. You're about the business of software John. Don't worry Microsoft don't give you some space there. (John and James laughing) We're under the radar at theCUBE 365 for the folks who are watching this. This is our site that we built with our software. So we're open and Docker was instrumental and I think the Docker captains were also very instrumental and trying to help us figure out the best way to preserve the content value. I personally think we're in this early stage of, content and community are clearly go hand in hand and I think as you look at the chat, some of the names that are on there. Some of the comments, really there's a new flywheel of production and this to me is the ultimate collaboration when you have these distinct groups coming together. And I think it's going to just be a data dream where people aren't the product, they're actually a contributor. And I think this open source framework that you're talking about is going to be certainly just going to evolve rapidly. I think it's just not even scratching the surface. I just think this is going to be pretty massive. And services whatever you want to define that. It could be an API to anything. It's going to be essentially the scale point. I mean why have a monolith piece of software running something. Something Microsoft teams will work well here. Zoom will work well there but ultimately what's in it for me the person? This is the key question. Developers just want to develop. You're going to hear that throughout the day. Kelsey Hightower brings up some great points in his session and Amanda silver at Microsoft, she had a quote on one of her videos. She said, "App developers are the first responders "in this crisis." And that's the first time I've heard someone say that out loud and that hits home for me because it's true. And right now app developers are one of the front lines. They're providing the app support. They're providing to the practitioners in the field. This is something that's not really written about in the press. What's your reaction to app developers are the first responders in this crisis. >> Well I mean first I think it's important to pay tribute to people that actually are first responders. Writing code can make us responsive but let's not forget there are people that are lacking PPE and they are on the frontline. So not precise manner but I might frame it slightly differently. But certainly what the current situation has shown us is productivity is super important. Target has made huge investments in building out its own software development capabilities. So they used to be like 70% external 30% internal and they turn that round to like 80% internal 20 external. And they've been turning on a dime and well there's so much going on at the moment. I'm like talking about target then I'm remembering what's happening in Minneapolis today. But anyway we'll talk about that. But yeah organizations are responding quickly. Look at the numbers that Shopify is happening because all sorts of business is something like we need to be an online business. What's the quickest way to do that. And Shopify was able to package something up in a way that they they could respond to challenges. Huge social challenges. I'm a big believer the future's unwritten at this point and I think there's a lot of problems out there you point out and the first responders are there I agree. I'm just thinking that there's got to be a better path for all of us. And this brings up the whole new roles and responsibilities around this new environment and I know you're doing a lot of research. Can you share some thoughts on what you're kind of working on now James? That's important, I'll see what's trending here at DockerCon is. Compose the relationship with Microsoft, we've got security, Dockers now, multicloud approach, making it easier, that's their bread and butter. That's what they're known for. They kind of going back to that roots of why they pioneered in the first place. So as that continues ease-of-use, what's your focus area right now that you're researching that you could share with the audience? >> Well, I mean I'd say this year for me I've got probably three key areas. One is what's called GitOps. So it's the notion that you're using Git as a system of record. So that started off randomly making changes, you have an audit trail. You begin to have some sort of sense of compliance in software changes. I think the idea of everything has to be by a sort of a pull request. That automation model is super thing to me. So I've been looking at that. A lot of development teams are using those approaches. Observability is a huge trend. We're moving to the idea of testing and production. The kind of stuff that's been evangelized so successfully by charity majors honeycomb. It's super exciting to me and it's true because in effect, you're always testing in production, your dev environment. I mean we used to have this idea that you'd have a Dev and a Dev stage. You're have a staging environment. The only environment that really matters is where the rubber meets the road. And that is deployment. So I think that having having better tools for that is one of the areas I'm looking at. So how are tools innovating that area? And it won't be the thing that this is my own personal thing. I've been talking about progressive delivery which is asking a question about reducing risk by really understanding the blast radius of the service to be able to roll it out to specific use of populations first. Understanding who they are and enrolling it up so it's the idea that like maybe you brought something out to your employees first. Maybe you are in California and you roll something out in Tokyo knowing that not many people are using that service. It is a live environment but people are not going to be adversely affected if it happens. So Canary's Blue-Green deployments and also experimentation. This is sort of one of the areas I'm being sort of pulled towards. It's sort of product management and how that's really converging with software development. I feel like that's one of the things I haven't fully, I mean I think it's when they have research focused but you have to respond to new information. Anyhow, I'm spending a lot of time thinking about the world of product management. It's those companies to be most respect in terms of companies that are crushing it in the digital economy. They have such a strong product management focused. Everything is driven by product managers that understand technology and that's an exciting shift. The one that I'm paying greater attention. >> You do some great work and I love the focus on productivity software development. Getting those app developers out there and it's interesting. I just think that it's such an exciting time. It's almost intoxicating. Some people drinking on Twitter online and having beers because they're in different time zone. But if you look up and down the action that's going on, you got at the application developers side, all the things you were mentioning services. But when you look at the cloud side, you got almost this operating system reset. It's a systems architecture. So you have the hall and that's up and down. The middle of the stack to the bottom, you have this operating systems thinking and evolution. And then you got at the top, the pure software developers. And this is again to me the big aha moment. For the industry there's a true opportunity to scale that in unbelievable ways. And you don't have to pick a side. You can do a top of the stack bottom stack. So I think kubernetes and micro services really bring this whole enablement piece to the table. And that fascinates me and I think that's going to change what the apps will look like. It'll give more productivity and then making the internet programmable unit, that's new systems. So that seems to be the trend. You're a systems guy, your girl or you're a developer. How do you see that evolving? Do you get to that level? >> Developer experience is not necessarily the key value of Kubernetes. It's supremely flexible sort of system. It does offer you that portability. But I think what I'm seeing now is how people are taking Kubernetes and kind of thinking, so you've got VMware, acquires Heptio, brings Pivotal into the fold, starting about what that platform looks like. I think Pivotal with cloud foundry did a great job of thinking through operator experience. Operator experience is not the same as developer experience. I think we're going to see a bit more specialization of roles. Meanwhile at that point, you've got the cloud players all doing pretty awesome job supporting Kubernetes. But it gives that portability promise. So I think for me, one of the things is not expecting everyone to do everything. It's like Kelsey said, some people just want to come into work and do their job and they're super important. And so VMware I think a history of certification of application environments. So of them it's sort of quite--and certification of humans. It's quite natural that they would be somebody that would think about how do we make Kurbenetes more consumable and packaged in a way that more people take advantage of it. Docker was such a phenomenon and now seeing how that sort of evolving into that promise of portability is beginning to be realized. So I think the specialization, the pendulum is going to swing back just a little bit. >> I think it's just great timing and congratulations on all the work and thanks for taking the time for participating in DockerCon with the Keynote. Taking time out of your day and coming in and doing this live interview. The chat looks good. Hit some great, get some fans in there. It's a great opportunity and I think Docker as the pioneers, pivoting in a new direction, it's all about developer productivity and James you've been on it. @monkchips is his Twitter handle, follow him, hit him up. I'm John Furrier here in the studio for DockerCon 2020. Ginebra CEO and you got Brett Fisher on the captain's channel. If you go to the site, you'll see the calendar. Jump into any session you want. They'll be live on the time or on-demand instantly. TheCUBE track has a series of enemies. You've got Amazon, we got Microsoft, get some great guests, great practitioners that are literally having an impact on society. So thanks for watching. James, thanks for spending the time. >> Thank you very much John. >> Okay James Governor, founder of Monkchips, great firm, great person-- >> RedMonk, RedMonk is the company. Monkchips is the Twitter. >> Redmonk, Monkchips. RedMonk, RedMonk. >> RedMonk is the company. >> RedMonk, RedMonk. >> @monkchips is his Twitter handle and RedMonk is the firm, thank you for the correction. Okay more coverage DockerCon after this short break. Stay with us. The next segment is coming up. Stay with us here at theCUBE DockerCon. (gentle music)

>>From around the globe. It's the view with digital coverage of Docker con live 2020 brought to you by Docker and its ecosystem partners. >>LeBron. Welcome back to DockerCon 2020 hashtag Docker 20 this is the cube and Dockers coverage of Docker con 20 I'm Sean for you and the Palo Alto studios with our quarantine crew. We've got a great interview segment here in big news around developer workflow code to cloud. We've got Amanda silver corporate vice president, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott had a great keynote talking about this relationship news has hit about the extension of the Microsoft partnership. So congratulations Amanda. Welcome to the cube. >>Thanks for having me. >>Amanda, tell us a bit about what your role is at Microsoft. You guys are well known in the developer community to develop an ecosystem when even when I was in college going way back, very modern. Now cloud is, is the key code to cloud. That's the theme. Tell us about your role at Microsoft. >>Yeah. So I basically run the product, uh, product design and user research team that works on our developer tools that Microsoft and so that includes the visual studio product as well as visual studio code. Um, that's become pretty popular in the last few years, but it also includes things like the.net runtime and the TypeScript programming language as well as all of our Azure tooling. >>What's your thoughts on the relationship with Docker? I'll show you the news extension of an existing relationship. Microsoft's got a lot of tools. You've got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Donker. >>Yeah, well we're very excited about the partnership for sure. Um, you know, our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. Uh, we really see a unique opportunity to make the experience really great for Docker, for the Docker community by creating more integrated and seamless experience across Docker, desktop windows and visual studio. And we really appreciate how, how Docker is kind of, you know, supported our windows ecosystem to run in Docker as well. >>Scott, this relationship and an extension with Microsoft is really, uh, I think impressive and also notable because Microsoft's got so many, so many tools out there and they have so successful with Azure. You guys have been so successful with your developer community, but this also is reflective of the new Docker. Uh, could you share your thoughts on how this partnership with Microsoft extending the way it is with the growth of the cloud is a reflection of the new Docker? >>Yeah, absolutely. John's great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem. And part of that is just reality. That we're a smaller company now and we can't do it all, nor should we do it all. Part of us. The reality that developers love voice and no one's gonna change their minds on choice. And third is just acknowledging that there's so much creativity and so much energy. The four walls of Docker that we'd be building, not the big advantage of that and welcome it and embrace it and provide that as a phenomenal experience part of Alfred's. So this is a great example of that. The sneak partnership we announced last week is a grant to have that and you're going to see many more of uh, partnerships like this going forward that are reflective of exactly this point. >>You've been a visionary on the product side of the interviewed before. Also deploying is more important than ever. That whole workflow, simplifying, it's not getting complex. People want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in because they got stuff too. You've got stuff, it all works together. What's your thoughts? >>Right? So it needs to work together, right? Because developers want to focus on their app. They don't want to focus on duct taping and springing together different siloed pools, right? So you can see in the demo and you'll see in, uh, demonstrations later throughout the conference. Just the seamless experience that a developer gets in the document man line inter-operating with visual studio code with the Docker command line and then deploying to Azure and what's what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around the figuration around default settings around uh, security, user management, all of that is abstracted out and taken away from the developer so they can focus on applications and getting those applications deployed to the proudest quickly as possible. Getting their app from code to cloud is the wok word or the or the call to action for this partnership. And we think we really hit it out of the park with the integration that you saw, >>Great validation and a critical part of the workflow. You guys have been part of Amanda, we're living in a time we're doing these remote interviews. The coven crisis has shown the productivity gains of working at home and working in sheltering in place, but also as highlighted, the focus of developers mainly who have also worked at home. They've kind of used to this. Do you see the rigs? I saw her at Microsoft build some amazing rigs from the studio. So these guys streaming their code demos. This is, um, a Cambrin explosion of new kinds of productivity. And yet the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? Cause the tooling is more tools than ever, right? So I still gotta deploy code. It's gotta be more agile. It's gotta be faster. It's gotta be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers and the end of the day, don't you still got to do their job? >>Yeah, well, absolutely. And now, even more than ever. I mean, I think we've, we've certainly seen over the past few months, uh, uh, a more rapid acceleration of digital transformation. And it's really happened in the past few years. Uh, you know, paper processes are now becoming digit digital processes. All of a sudden, you know, everybody needs to work and learn from home. And so there's just this rapid acceleration to kind of move everything to support our new remote lifestyle. Um, but even more so, you know, we now have remote development teams actually working from home as well in a variety of different kinds of, uh, environments. Whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. You know, it's more important than ever that developers are productive, but they are productive as a team. Right? Software is a team sport. >>We all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And, uh, what Docker really enables is, uh, with, with containerization is to make the infrastructure consistent and repeatable so that as developers are moving through the life cycle from their local, local dev desktop and developing on their local desktop to a test environment and to staging and to production, it's really, it's infrastructure of or, or developers as well as operations. And so it's that, that infrastructure that's completely customizable for what the developer's operating system of choices, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really, really fast iteration cycle but also to have that consistency across all of their development team. And you know, we, we now need to think about things like how are we actually going to bring on interns for the summer, uh, and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them. And things like Docker really helped with that >>As your container instances and a visual studio cloud that you guys have has had great success. Um, there's a mix and match formula here. At the end of the day, developers want to ship the code. What's the message that you guys are sending here with this? Because I think productivity is one, simplification is the other, but as developers on the front lines and they're shipping in real time, this is a big part of the value proposition that you guys are bringing to the table. >>Yeah, I mean the, the core message is that any developer and their code is welcome, uh, and that we really want to support them and power them and increase their velocity and the impact that they can have. Um, and so, you know, having things like the fact that the Docker CLI is natively integrated into the Azure experience, uh, is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. Um, and now that the Docker CLI tools are, that are part of Docker desktop, have access to native commands that work well with Azure container instances. Uh, Azure container instances, if anybody's on familiar with that, uh, is the simplest and fastest way to kind of set up containers and Azure. And, and so we believe that developers have really been looking for a really simple way to kind of get containers on Azure. And now we that really consistent experience across our service services and our tools and visual studio code and visual studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've, we've integrated these as a design point since very early on in our partnership when we've been partnering with, with Docker for quite a while. >>Amanda, I want to ask you about the, the, the, the tool chain. We've heard about workflows, making it simpler, bottom line, from a developer standpoint, what's the bottom line for me? What does this mean to me? Uh, every day developer out there? >>Um, I, I mean, I really think it means you know, your productivity on your terms. Um, and so, you know, Microsoft has been a developer company since the very, very beginning with, you know, bill Gates and, and, uh, GW basic. Um, and it's actually similar for Docker, right? They really have a developer first point of view, uh, which certainly speaks to my heart. And so one of the things that we're really trying to do with, with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience, no matter which stack they're actually targeting, whether there's targeting node or Python or.net and C-sharp or Java. Uh, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create, you know, Docker container images and use the compose Docker compose files. >>Um, and then, you know, just kind of do that consistently as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure is that that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. Um, so we, we also think about the process of writing the code, but also the process of kind of managing the code and remediating issues that might come up in production. And so, you know, we really want you to be able to look at containers up in the Azure. Uh, up that are deployed into Azure and make sure that they're running and healthy and that if there, if something's wrong, that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect when to see environment variables or other details. >>Yeah, that's awesome. You know, writing code, managing code, and then you've got to deploy, right? So what I've been loving about the, the past generation of agile is deployment's been fast to deploy all the time. Scott, this brings up that the ease of use, but you want to actually leverage automation. This is the trend that you want to get in. You want, you don't want, you want to make it easy to write code, manage code. But during the deployment phase, that's a big innovation. That's the last point. Making that better and stronger. What's your thoughts on simplifying that? >>So that was a big part of this partnership, John, that the Docker in Microsoft embarked on and as you saw from the demo and the keynote, um, all within the man line, the developers able to do in two simple commands, deploy an app, uh, defining compose from the desktop to Azure and there's a whole slew of automation and pre-configured smart defaults or sane defaults that have gone on behind the scenes and that took a lot of hardcore engineering work on part of Docker and Microsoft together to simplify that and make that easy and that, that goes exactly to your point. We just like the simpler you can make it more, you can abstract a way to kind of underlying plumbing and infrastructure. The faster devs can get there. Their application from code to cloud. >>Scott, you've been a product CEO, you've been a product person, a CEO, but you have a product background. You've been involved with the relationship with Microsoft for a long time. What's the state of the market right now? I mean, obviously Microsoft has evolved. Look at just the performance corporate performance. The shift to the cloud has been phenomenal. Now developers getting more empowered, there's more demand for the pressure to put on developers to do more and more, more creativity. So you've seen this evolve, this relationship, what does it mean? >>Yeah, it's honestly a wonderful question, John. And I want to thank Amanda and the entire Microsoft team for being long standing partners with us on this journey. So it's might not be known to everyone on today's, uh, day's event. But Microsoft came to the very first Docker con event, uh, way back in June, 2014 and I had the privilege of, of reading them and welcoming them and they're, they were full on ready to see what all the excitement about Docker was about and really embrace it. And you mentioned kind of openness and Microsoft's growth over that, uh, over time in that dimension. And we think kind of Docker together with Microsoft have really shown what an open developer community can do. And that started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine, bringing that Docker engine from Linux and now moving it to windows applications. And so all of a sudden the promise of right ones and use the same primitives, the same formats, the same fan lines, uh, as you can with Linux onto windows applications. We brought that promise to the market and it's been an ongoing journey together with Microsoft of open standards based, developer facing friendliness, ease of use, fast time to deploy. And this, this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship laser like focused on developer productivity and helping teams build great apps. >>Why do you like Azure in the cloud for Docker? Can you share why? >>Well, it's as Amanda has been sharing, it's super focused on what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud. And Azure, phenomenal job of simplifying and providing sane defaults out of the box. And as we've been talking about, it's also very open to partner like the one we've announced >>Yesterday and highlighted, you know, but >>Uh, make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure. It's possible. So, uh, it's, it's a phenomenal plan, one for developers and we're very excited and proud of partner with Microsoft on it. >>Amanda, on your side, I see DACA has got millions of developers. You guys got millions of developers even more. How do you see the developers in Microsoft side engaging with Docker desktop and Docker hub? Where does it all fit? >>I think it's a great question. I mean, I mentioned earlier how the Docker context can help individuals and teams kind of work in their environments work. Let me try that over. I mentioned earlier how I, how I see Docker context really improving the way that individuals and teams work with their environments and making sure that they're consistent. But I think this really comes together as we work with Docker desktop and Docker hub. Uh, when developers sign into Docker hub from Docker desktop, everything kind of lights up. And so they can see all of the images in their repositories and they can also see the cloud environments they're running them in. And so, you know, once you sign into the hub, you can see all the contexts that map to the logical environments that they have access to like dev and QA and maybe staging. And another use case that's really important is that, you know, we can access the same integration environment. >>So, so I could have, you know, microservices that I've been working on, but I can also see microservices that my, my teammates and their logs, uh, from the services that they've been working on, which I think is really, really great and certainly helps with, with team productivity. The other thing too is that this also really helps with hybrid cloud deployments, right? Where, you know, you might have some on premises, uh, hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things, uh, through your Docker hub. >>Well, I got to say I love the code to cloud tagline. I think that's very relevant and, and catchy. Um, and I think, I guess to me what I'm seeing, and I'd love to get your thoughts, Amanda, on this, as you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tense and anxiety with the covert 19 crisis, but I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this and you've seen these ways before, but now in this time, what are you most excited about? What are you optimist about? What's your view on the opportunities? Can you share your thoughts? Because people are going to get back to work or they're working now remotely, but when we go back to hybrid world, they're going to be jamming on projects. >>Yeah, for sure. But I mean, people are jamming on projects right now. And I think that, you know, in a lot of ways, uh, developers are our first responders in, you know, in that they are, developers are always trying to support somebody else, right? We're trying to somebody else's workflow and you know, so we have examples of people who are, uh, creating new remote systems to be able to, uh, schedule meetings in hospitals or the doctors who are actually the first, first responders taking care of patients. But at the end of the day, it's the developer who's actually creating that solution, right? And so we're being called the duty right now. Um, and so we need to make sure that we're actually there to support the needs of our users and that we're, we're basically cranking on code as fast as we can. Uh, and to be able to do that, we have to make sure that every developer is empowered and they can move quickly, but also that they can collaborate freely. And so, uh, I think that, you know, Docker hub Docker kind of helps you ensure that you have that consistency, but you also have that connection to the infrastructure that's hosted by your, your organization. >>I think you nailed that amazing insight. And I think that's, you know, the current situation in the community matters because there's a lot of um, frontline work being done to your point. But then we've got to rebuild. The modernization is happening as well coming out of this. So there's going to be that and there's a lot of comradery going on and massive community involvement. I'm seeing more of, you know, the empathy, but also now there's going to be the building, the creation, the new creation. So Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. >>Well that's exactly right and it is time to build, right? Um, and we're going to build our way out of this. Um, and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that, that community energy and give them the tools to go. And identify and have an impact as quickly as possible. We have referenced in the keynote, um, completely bottoms up organic adoption of Docker desktop and Docker hub in racing to provide solutions against the COBIT 19 virus. Right? It's a, it's a war against this pandemic that is heavily dependent on applications and data and there's over 200 projects, community projects on Docker hub today where you've got uh, cools and containers and data analysis all in service to the photo at 19 battle that's being fought. And then as you said, John, as we, as we get through this, the other side, there's entire industries that are completely rethinking their approach that were largely offline before that. Now see the imperative and the importance of going online and that tectonic shift nearly overnight of offline to online behavior and commerce and social and go on down the list that requires new application development. And I'm very pleased about this partnership is that together we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. >>Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. You know, I'm a big fan of from day one. I know you guys have pivoted on a new trajectory which is very community oriented, very open source, very open. So congratulations on that Amanda. Thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft. For the folks that know Microsoft, know they have a developer mindset from day one cloud is exploding code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share from some, some, some uh, data for the folks that aren't in the community or might want to join with folks in the community who want to get an update? >>Yeah, it's a, it's a great, great kind of question. I mean, you know, right now I think we are all really focused on making sure that we can empower developers throughout the world and that includes both those who are building solutions for their organizations today. But also I think we're going to end up with a ton of new developers over this next period who are really entering the workforce and uh, and learning to create, you know, digital solutions overall. There's a massive developer shortage across the world. Um, there's so much opportunity for developers to kind of, you know, address a lot of the needs that we're seeing out of organizations again across the world. Um, and so I think it's just a really exciting time to be a developer. Uh, and you know, my, my uh, my only hope is that basically we're, we're building tools that actually enable them to solve problems. >>Awesome insight and thank you so much for your time code to cloud developers are cranking away that the first responders are going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for sharing the Microsoft Docker partnership and the things that you guys are working on together. Thanks for your time. Okay. This is the cubes coverage. We are Docker con 2020 digital is the cube virtual. I'm Sean for bringing all the action. More coverage. Stay with us for more Docker con virtual. After this short break.

>>From Las Vegas. It's the cube covering Qualis security conference 2019 you buy quality. >>Hey, welcome back. You're ready. Jeff Frick here with the cube. We're in Las Vegas at the Bellagio, at the quality security conference. It's the 19th year they've been doing this. It's our first year here and we're excited to be here and it's great to have a veteran who's been in this space for so long, to give a little bit more of a historical perspective as to what happened in the past and where we are now and what can we look forward to in the future. So coming right off his keynote is Felipe korto, the chairman and CEO of Qualys. Phillip, great to see you. Thank you. Same, same, same for me. Absolutely. So you touched on so many great, um, topics in your conversation about kind of the shifts of, of, of modern computing from the mainframe to the mini. We've heard it over and over and over, but the key message was really about architecture. If you don't have the right architecture, you can't have the right solution. So how has the evolution of architects of architectures impacted your ability to deliver security solutions for your clients? >>So now that's a very good question. And in fact, you know, what happened is that we started in 1999 with a vision that we could use exactly like a salesforce.com this nascent internet technologies and apply that to security. And uh, so, and mod when you have applied that to essentially changing the way CRM was essentially used and deployed in enterprises and with a fantastic success as we know. So for us, the, I can say today that 19 years later the vision was right. It took a significant longer because the security people are not really, uh, warm at the idea of silently, uh, having the data in their view, which was in place that they could not control. And the it people, they didn't really like at all the fact that suddenly they were not in control anymore of the infrastructure. So we had a lot of resistance. >>I, wherever we always, I always believe, absolutely believe that the, the cloud will be the cloud architecture to go back. A lot of people make the confusion. That was part of the confusion that for people it was a cloud, that kind of magical things someplace would you don't know where. And when I were trying to explain, and I've been saying that so many times that well you need to look at the cloud like compute that can architecture which distribute the competing power far more efficiently than the previous one, which was client server, which was distributing the convening power far better than of course the mainframes and the mini computers. And so if you look at their architectures, so the mainframe were essentially big data centers in uh, in Fort Knox, like settings, uh, private lines of communication to a dump terminal. And of course security was not really issue then because it's security was built in by the IBM's and company. >>Same thing with the mini computer, which then was instead of just providing the computing power to the large, very large company, you could afford it. Nelson and the minicomputer through the advanced in semiconductor technology could reduce a foot Frank. And then they'll bring that computing power to the labs and to the departments. And was then the new era of the digital equipment, the prime, the data general, et cetera. Uh, and then kind of server came in. So what client server did, again, if you look at the architecture, different architecture now silently servers, the land or the internal network and the PC, and that was now allowing to distribute the computing power to the people in the company. And so, but then you needed to, so everybody, nobody paid attention to security because then you were inside of the enterprise. So it started inside the walls of the castle if you prefer. >>So nobody paid attention to that. It was more complex because now you have multiple actors. Instead of having one IBM or one digital equipment, et cetera, suddenly you have the people in manufacturing and the servers, the software, the database, the PCs, and on announcer, suddenly there was the complexity, increasing efficiency, but nobody paid attention to security because it wasn't a needed until suddenly we realized that viruses could come in through the front door being installed innocently. You were absolutely, absolutely compromised. And of course that's the era of the antivirus which came in. And then because of the need to communicate more and more now, Senator, you could not stay only in your castle. You needed to go and communicate to your customers, to your suppliers, et cetera, et cetera. And now he was starting to open up your, your castle to the world and hello so now so that the, the bad guy could come in and start to steal your information. >>And that was the new era of the forward. Now you make sure that those who come in, but of course that was a little bit naive because there were so many other doors and windows, uh, that people could come in, you know, create tunnels and create these and all of that trying to ensure your customers because the data was becoming more and more rich and more, more important or more value. So whenever there is a value, of course the bad guys are coming in to try to sell it. And that was that new era of a willing to pay attention to security. The problem has been is because you have so many different actors, there was nothing really central there that was just selling more and more solutions and no, absolutely like 800 vendors bolting on security, right? And boating on anything is short-lived at the end of the day because you put more and more weight and then you also increase the complexity and all these different solutions you need. >>They need to talk together so you have a better context. Uh, but they want the design to talk together. So now you need to put other system where they could communicate that information. So you complicated and complicated and complicated the solution. And that's the problem of today. So now cloud computing comes in and again, if you look at the architecture of cloud computing, it's again data centers, which is not today I've become thanks to the technology having infinite, almost competing power and storage capabilities. And like the previous that I sent her, the are much more fractured because you just one scale and they become essentially a little bit easier to secure. And by the way, it's your fewer vendors now doing that. And then of course the access can be controlled better. Uh, and then of course the second component is not the land and the one, it's now the internet. >>And the internet of course is the web communications extremely cheap and it brings you an every place on the planet and soon in Morris, why not? So and so. Now the issue today is that still the internet needs to be secure. And today, how are we going to secure the internet? Which is very important thing today because you see today that you can spoof your email, you can spoof your website, uh, you can attack the DNS who, yes, there's a lot of things that the bad guys still do. And in fact, they've said that leverage the internet of course, to access everywhere so they take advantage of it. So now this is obviously, you know, I created the, the trustworthy movement many years ago to try to really address that. Unfortunately, the quality's was too small and it was not really our place today. There's all the Google, the Facebook, the big guys, which in fact their business depend on the internet. >>Now need to do that. And I upload or be diabetic, criticized very much so. Google was the first one to essentially have a big initiative, was trying to push SSL, which everybody understand is secret encryption if you prefer. And to everybody. So they did a fantastic job. They really push it. So now today's society is becoming like, okay, as I said, you want to have, as I said it all in your communication, but that's not enough. And now they are pushing and some people criticize them and I absolutely applaud them to say we need to change the internet protocols which were created at a time when security, you were transferring information from universities and so forth. This was the hay days, you know, of everything was fine. There was no bad guys, you know, the, he'd be days, if you like, of the internet. Everybody was free, everybody was up and fantastic. >>Okay. And now of course, today this protocol needs to be upgraded, which is a lot of work. But today I really believe that if you put Google, Amazon, Facebook altogether, and they can fix these internet protocols. So we could forget about the spoofing and who forgot about all these phishing and all these things. But this is their responsibility. So, and then you have now on the other side, you have now very intelligent devices from in a very simple sensors and you know, to sophisticated devices, the phone, that cetera and not more and more and more devices interconnected and for people to understand what is going. So this is the new environment and whether we always believe is that if you adopt an architecture, which is exactly which fits, which is similar, then we could instead of bolting security in, we can now say that the build security in a voting security on, we could build security in. >>And we have been very proud of the work that we've done with Microsoft, which we announced in fact relatively recently, very recently, that in fact our agent technologies now is bundled in Microsoft. So we have built security with Microsoft in. So from a security perspective today, if you go to the Microsoft as your secretly center, you click on the link and now you have the view of your entire Azure environment. Crazier for quality Sagent. You click on a second link and now you have the view of your significant loss posture, crazy of that same quality. Say Sagent and then you click on the third name with us. Nothing to do with quality. It's all Microsoft. You create your playbook and you remediate. So security in this environment has become click, click, click, nothing to install, nothing to update. And the only thing you bring are your policies saying, I don't want to have this kind of measured machine expose on the internet. >>I want, this is what I want. And you can continuously audit in essentially in real time, right? So as you can see, totally different than putting boxes and boxes and so many things and then having to for you. So very big game changer. So the analogy that I want you that I give to people, it's so people don't understand that paradigm shift is already happening in the way we secure our homes. You put sensors everywhere, you have cameras, you have detection for proximity detection. Essentially when somebody tried to enter your home, all that data is continuously pumped up into an incidence restaurant system. And then from your phone, again across the internet, you can change the temperature of your rooms. You can do what you can see the person who knocks on the door. You can see its face, you can open the door, close the door, the garage door, you can do all of that remotely, another medically. >>And then if there's a burglar then in your house to try to raking immediately the incidents or some system called the cops or the far Marsha difficult fire. And that's the new paradigm. So security has to follow that paradigm. And then you have interesting of the problem today that we see with all the current secretly uh, systems, uh, incidents, response system. They have a lot of false positive, false positive and false negative are the enemy really of security. Because if you are forced visited, you cannot automate the response because then you are going to try to respond to something that is not true. So you are, you could create a lot of damage. And the example I give you that today in the, if you leave your dog in your house and if you don't have the ability, the dog will bark, would move. And then the sensors would say intruder alert. >>So that's becomes a false positive. So how do you eliminate that? By having more context, you can eliminate automatically again, this false positives. Like now you take a fingerprint of your dog and of these voice and now the camera and this and the sensors and the voice can pick up and say, Oh, this is my dog. So then of course you eliminate that for solar, right? Right. Now even if another dog managed to enter your home through a window which was open or whatever for soul, you will know her window was up and but you know you cannot necessarily fix it and the dog opens. Then you will know it's a, it's a, it's not sure about, right? So that's what security is evolving such a huge sea of change, which is happening because of all that internet and today companies today, after leveraging new cloud technology, which are coming, there's so much new technology. >>What people understand is where's that technology coming from? How come silently we have, you know, Dockers netics all these solutions today, which are available at almost no cost because it's all open source. So what happened is that, which is unlike the enterprise software, which were more the Oracle et cetera, the manufacturer of that software today is in fact the cloud public cloud vendors, the Amazon, the Google, the Facebook, the Microsoft. We suddenly needed to have to develop new technology so they could scale at the size of the planet. And then very shrewdly realized that effective that technology for me, I'm essentially going to imprison that technology is not going to evolve. And then I need other technologies that are not developing. So they realized that they totally changed that open source movement, which in the early days of opensource was more controlled by people who had more purity. >>If you prefer no commercial interests, it was all for the good of the civilization and humankind. And they say their licensing model was very complex. So they simplified all of that. And then nothing until you had all this technology coming at you extremely fast. And we have leverage that technology, which was not existing in the early days when when socials.com started with the Linux lamp pour called what's called Linux Apache. My SQL and PHP, a little bit limiting, but now suddenly all this technology, that classic search was coming, we today in our backend, 3 trillion data points on elastic search clusters and we return inflammation in a hundred milliseconds. And then onto the calf cabin, which is again something at open source. We, we, we, and now today 5 million messages a day and on and on and on. So the world is changing and of course, if that's what it's called now, the digital transformation. >>So now enterprises to be essentially agile, to reach out to the customers better and more, they need to embrace the cloud as the way they do, retool their entire it infrastructure. And essentially it's a huge sea of change. And that's what we see even the market of security just to finish, uh, now evolving in a totally different ways than the way it has been, which in the past, the market of security was essentially the market for the enterprise. And I'm bringing you my, my board, my board town solutions that you have to go and install and make work, right? And then you had the, the antivirus essentially, uh, for all the consumers and so forth. So today when we see the marketplace, which is fragmenting in four different segments, which is one is the large enterprise which are going to essentially consolidate those stock, move into the digital transformation, leveraging absolutely dev ops, which isn't becoming the new buyer and of course a soak or they could improve, uh, their it for, to reach out to more customers and more effectively than the cloud providers as I mentioned earlier, which are building security in the, no few use them. >>You don't have to worry about infrastructure, about our mini servers. You need, I mean it is, it's all done for you. And same thing about security, right? The third market is going to be an emergence of a new generation of managed security service providers, which are going to take to all these companies. We don't have enough resources. Okay, don't worry, I'm going to help you, you know, do all that digital transformation. And that if you build a security and then there's a totally new market of all these devices, including the phone, et cetera, which connects and that you essentially want to all these like OT and IOT devices that are all now connected, which of course presents security risk. So you need to also secure them, but you also need to be able to also not only check their edits to make sure that, okay, because you cannot send people anymore. >>So you need to automate the same thing on security. If you find that that phone is compromised, you need to make, to be able to make immediate decisions about should I kill that phone, right? Destroyed everything in it. Should I know don't let that phone connect anymore to my networks. What should I do? Should I, by the way detected that they've downloaded the application, which are not allowed? Because what we see is more and more companies now are giving tablets, do the users. And in doing so now today's the company property. So they could say, okay, you use these tablets and uh, you're not allowed to do this app. So you could check all of that and then automatically remote. But that again requires a full visibility on what you are. And that's why just to finish, we make a big decision about a few, three months ago that we have, we build the ability for any company on the planet to automatically build their entire global HSE inventory, which nobody knows what they have in that old networking environment. >>You don't know what connects to have the view of the known and the unknown, totally free of charge, uh, across on premise and pawn cloud containers, uh, uh, uh, whether vacations, uh, OT and IOT devices to come. So now there's the cornerstone of security. So with that totally free. So, and then of course we have all these additional solutions and we're build a very scalable, uh, up in platform where we can take data in, pass out data as well. So we really need to be and want to be good citizen here because security at the end of the day, it's almost like we used to say like the doctors, you have to have that kind of apricot oath that you cannot do no arm. So if you keep, if you try to take the data that you have, keep it with you, that's absolutely not right because it's the data of your customers, right? >>So, and you have to make sure that it's there. So you have to be a good warning of the data, but you have to make sure that the customer can absolutely take that data to whatever he wants with it, whatever he needs to do. So that's the kind of totally new field as a fee. And finally today there is a new Ash culture change, which is, which is happening now in the companies, is that security has become fronted centers, is becoming now because of GDPR, which has a huge of financial could over you challenge an impact on a company. A data breach can have a huge financial impact. Security has become a board level. More and more social security is changing and now it's almost like companies, if they want to be successful in the future, they need to embrace a culture of security. And now what I used to say, and that was the, the conclusion of my talk is that now, today it DevOps, uh, security compliance, people need to unite. Not anymore. The silos. I do that. This is my, my turf, my servers. You do that, you do this. Everybody in the company can work. I have to work together towards that goal. And the vendors need to also start to inter operate as well and working with our customers. So it's a tall, new mindset, which is happening, but the safes are big. That's what I'm very confident that we're now into that. Finally, we thought, I thought it would have happened 10 years ago, quite frankly. And uh, but now today's already happening. >>She touched on a lot, a lot there. And I'll speak for another two hours if we could. We could go for Tara, but I want to, I want to unpack a couple of things. We've had James Hamilton on you to at AWS. Um, CTO, super smart guy and it was, it was at one of his talks where it really was kind of a splash, a wet water in the face when he talked about the amount of resources Amazon could deploy to just networking or the amount of PhD power he could put on, you know, any little tiny sub segment of their infrastructure platform where you just realize that you just can't, you can't compete, you cannot put those kinds of resources as an individual company in any bucket. So the inevitability of the cloud model is just, it's, it's the only way to leverage those resources. But because of that, how has, how has that helped you guys change your market? How nice is it for you to be able to leverage infrastructure partners? Like is your bill for go to market as well as feature sets? And also, you know, because the other piece they didn't talk about is the integration of all these things. Now they all work together. Most apps are collection of API APIs. That's also changed. So when you look at the cloud provider GCP as well, how does that help you deliver value to your customers? >>Yeah, but the, the, the, the club, they, they don't do everything. You know, today what is interesting is that the clubs would start to specialize themselves more and more. So for example, if you look at Amazon, the, the core value of Amazon since the beginning has been elastic computing. Uh, now today we should look at Microsoft. They leverage their position and they really have come up with a more enterprise friendly solution. And now Google is trying to find also their way today. And so then you have Addy Baba, et cetera. So these are the public cloud, but life is not uniform like is by nature. Divers life wants to leave lunch to find better ways. We see that that's what we have so many different species and it just ended up. So I've also the other phenomena of companies also building their own cloud as well. >>So the word is entering into a more hybrid cloud. And the technology is evolving very fast as well. And again, I was selling you all these open source software. There's a bigger phenomenon at play, which I used to say that people don't really understand that much wood, but it's so obvious is if you look at the printing price, that's another example that gives the printing price essentially allowed, as we all know, to distribute the gospel, which has some advantage of, you know, creating more morality, et cetera. But then what people don't know for the most part, it distributed the treaties of the Arabs on technology, the scientif treaties, because the archives, which were very thriving civilization at the time, I'd collected all the, all the, all the information from India, from many other places and from China and from etc. And essentially at the time all of Europe was pretty in the age they really came up and it now certainty that scientific knowledge was distributed and that was in fact the seeds of the industrial revolution, which then you're up cat coats and use that and creating all these different technologies. >>So that confidence of this dimension of electricity and all of that created the industrial revolution seeded by now, today what is happening is that the internet is the new printing press, which now is distributing the knowledge that not to a few millions of people to billions of people. So the rate today of advancing technology is accelerating and it's very difficult. I was mentioning today, we know today that work and working against some quantum computing which are going to totally change things. Of course we don't know exactly how and you have also it's clear that today we could use genetic, uh, the, the, the, if you look at DNA, which stores so much information, so little place that we could have significant more, you know, uh, memory capabilities that lower costs. So we have embarked into absolutely a new world where things are changing. I've got a little girl, which is 12 years old and fundamentally that new generation, especially of girls, not boys, because the boys are still on, you know, at that age. >>Uh, they are very studious. They absorb so much information via YouTube. They are things like a security stream. They are so knowledgeable. And when you look back at history 2000 years plus ago in Greece, you at 95 plus percent of the population slaves. So a few percent could start to think now, today it's totally changed. And the amount of information they can, they learn. And this absolutely amazing. And you know, she, she's, I would tell you the story which has nothing to do with computing, but as a button, the knowledge of, she came to me the few, few weeks ago and she said, Oh daddy, I would like to make my mother more productive. Okay. So I said, Oh, that's her name is Avia, which is the, which is the, the, the either Greece or Zeus weathered here. And so I say, Evie, I, so that's a good idea. >>So how are you going to do it? I mean, our answer, I was flawed, but that is very simple. Just like with, for me, I'm going to ask her to go to YouTube to learn what she needs to learn. Exactly. And she learns, she draws very well. She learns how to draw in YouTube and it's not a gifted, she's a nice, very nice little girl and very small, but all her friends are like that. Right? So we're entering in a word, which thing are changing very, very fast. So the key is adaptation, education and democracy and democratization. Getting more people access to more. Absolutely. It's very, very important. And then kind of this whole dev ops continuous improve that. Not big. That's a very good point that you make because that's exactly today the new buyer today in security and in it is becoming the DevOps shipper. >>Because what? What are these people? There are engineers which suddenly create good code and then they want to of course ship their code and then all these old silos or you need to do these, Oh no, we need to put the new server, we don't have the capacity, et cetera. How is that going to take three months or a month? And then finally they find a way through, again, you know, all the need for scale, which was coming from the Google, from the Facebook and so forth. And by the way, we can shortcut all of that and we can create and we can run out to auto-ship, our code. Guess what are they doing today? They are learning how to secure all of that, right? So again, it's that ability to really learn and move. And today, uh, one of the problem that you alluded to is that, which the Amazon was saying is that their pick there, they have taken a lot of the talent resources in the U S today because of course they pay them extra to me, what? >>Of course they'll attract that talent. And of course there's now people send security. There's not enough people that even in, but guess what? We realized that few years ago in 2007, we'll make a big decision who say, well, never going to be able to attract the right people in the Silicon Valley. And we've started to go to India and we have now 750 people. And Jack Welch used to say, we went to India for the cost and discover the talent. We went to India for the talent and we discover the cost. And there is a huge pool of tenants. So it's like a life wants to continue to leave and now to, there are all these tools to learn, are there, look at the can Academy, which today if you want to go in nuclear physics, you can do that through your phone. So that ability to learn is there. So I think we need just more and more people are coming. So I'm a very optimistic in a way because I think the more we improve our technologies that we look at the progress we're making genetics and so everywhere and that confidence of technology is really creating a new way. >>You know, there's a lot of conversations about a dystopian future and a utopian future with all these technologies and the machines. And you know what? Hollywood has shown us with AI, you're very utopian side, very optimistic on that equation. What gives you, what gives you, you know, kind of that positive feeling insecurity, which traditionally a lot of people would say is just whack a mole. And we're always trying to chase the bad guys. Generally >>speaking, if I'm a topian in in a way. But on the other end, you'd need to realize that unfortunately when you have to technological changes and so forth, it's also create factors. And when you look at this story in Manatee, the same technological advancement that some countries to take to try to take advantage of fathers is not that the word is everything fine and everything peaceful. In fact, Richard Clark was really their kid always saying that, Hey, you know that there is a sinister side to all the internet and so forth. But that's the human evolution. So I believe that we are getting longterm. It's going to. So in the meantime there's a lot of changes and humans don't adapt well to change. And so that's in a way, uh, the big challenge we have. But I think over time we can create a culture of change and that will really help. And I also believe that probably at some point in time we will re-engineer the human race. >>All right, cool. We'll leave it there. That's going to launch a whole nother couple hours. They leave. Congratulations on the event and a great job on your keynote. Thanks for taking a few minutes with us. Alrighty. It's relief. I'm Jeff. You're watching the cube where the Qualice security conference at the Bellagio in Las Vegas. Thanks for watching. We'll see you next time.

>> From the Aria Resort in Las Vegas, it's theCUBE. Covering AWS marketplace. Brought to you by Amazon Web Services. >> Hey, welcome back everybody, Jeff Frick here with theCUBE. We are kicking off three crazy days at AWS re:Invent. It is the place to be the week after Thanksgiving. There's got to be 50,000 people, we haven't got the official word, but it's packed and it kicks off tonight with a reception. We're here at the AWS Marketplace and Service Catalog Experience over at the Aria, in the quad, come check us out. A lot of good stuff going on. A lot of fun stuff going on. And we're excited to have first time to theCUBE, he's Nathan Dyer, Senior Product Manager for Tenable. Great to see you. >> Jeff, great to be here. Thanks for having me. >> Yeah, have the energy the opened the doors the people are streaming in. >> I don't know if it's the food or the drinks or the vendors. >> All of the above. Probably more the food and the drinks. All right. So give us an overview of Tenable for people who aren't familiar with the company. >> Yeah, so Tenable, we are the cyber exposure company. We help organizations assess, manage, and measure their cyber risk across their entire organization, across their monitored tax surface. And so what we try to do is help answer four fundamental questions around security. How exposed are we? How do we prioritize based on risk, how are we doing over time from a measurement standpoint, and then how do we compare with our peers? And so, if you haven't heard of Tenable, chances are you've heard of Nessus, which is one of our flagship brands. Nessus just turned 20 years young earlier this year. If you're pen tester, if you're a consultant if you're a practitioner, you know Nessus. But over the years we've added some other brands as well. Security Center which is now renamed Tenable.sc which is our On-Prem vulnerability management solution. And then tenable.io which was released in 2017 which is our cloud based vulnerability management solution and built on AWS. >> Right. So I was doing some research, I love your guys' little mantra here, it's security for code, for clouds and containers. You got all the C's there. The containers, you know, what's going on with Docker over the last couple of years and now obviously the huge groundswell with Kubernetes, you know this container thing, depending on who you talk to has been around for a long time but it certainly didn't have the momentum. How's the kind of the growth of the container world impacted the securities base? >> Oh, it's massive. Containers are everywhere. In fact there's a strong affinity to cloud and containers. So a lot of our large AWS customers love containers. They've been dabbling with containers for quite some time. They're moving more and more workloads to be containerized and on Kubernetes, Dockers, et cetera. From a securities standpoint that introduces a lot of challenges, right. They're short lived life cycles of docker containers make it very hard for us in security to assess or discover them. They're part of the whole immutable infrastructure phenomenon, so you can't patch it in production, right. Infrastructure is code. You have to tear down the container, fix the image and then redeploy. So from our perspective, we think you have to secure containers by focusing on the container image. Specifically as developers are spinning up new code, compiling new builds, creating new container images, is it running quality assurance checks? Security has to be a critical part of that quality assurance process. As you're doing integration tests, unit testing, API testing, security has to be a critical test looking for vulnerabilities and malwares is part of that process. >> But the rate of change in those images is pretty high. I mean, the rate of deployments is super high, but like you said a lot of them have short life spans, they're up or they're down. So, have people baked that in to their process? I mean, obviously, I hope they are. Or how are you helping them to make sure that security is a really key piece to that image. Because once that image goes out it has access to all kinds of things. >> So, the new news with containers, and then by focusing on the image it forces security teams to talk to their development peers. In order to secure DevOps and secure containers, security has to be embedded into continuous integration, into continuous delivery cycles or systems. And if you're focusing on development, you have a much greater chance of making sure that vulnerable container images are not escaping into the wild. And you guys should get a hold of those vulnerable images and make sure they adhere to policies before they're released into production. So that's the new news. >> Well, it's funny because you reference the DevOps. 'Cause DevOps has now been around for a while and clearly is the way the code gets deployed in a very rapid iteration. So they're some significant lessons from the DevOps security angle that you're now using then on the container side. Yeah, well first thing with secure DevOps and Devops in general, is that you have to get the developers and security teams to talk. You have to have a shared understanding of what makes each other tick. What are the goals, what are the responsibilities, priorities, understand each other and it turns out there's actually a lot of shared understanding and mutual benefit between infosec and application developments. When security is focused on solving for vulnerabilities and looking for security issues, that's improving code quality. That's removing some of the software defects from the development code and developers love that. They love producing high quality code. On the flip side, security teams can learn a lot about agile development. DevOps principles. Bringing DevOps into the security discipline, and help security teams start to leverage automation and continuous testing, continuous delivery, and make them much more scalable and productive in their organizations. So there's a lot of mutual of understanding there. >> Right. So I'd imagine there's a lot of, kind of similarities between classic waterfall and the moat, versus now kind of the DevOps and the continuous and ongoing constant process. >> That's exactly right. >> Yeah. So we're here at the AWS Marketplace. So you guys are selling through the marketplace, how has that been for the company? How has the experience been working with the AWS marketplace team? >> Oh, it's been great. I mean, Amazon is a great partner to work with. Tenable.io which is our cloud based vulnerability management solution is built on Amazon. We have a great relationship with Amazon engineers. Now for the marketplace, we've been selling Nessus for quite some time through the marketplace. So if you're a Nessus subscriber, if you're a tenable.io or securities center or tenable.sc subscriber, you get access to unlimited Nessus scanners and you can provision them very easily through the marketplace. It's super easy. Just recently, we now unveiled tenable.io through the marketplace and so far it's been a great success. Now customers who prefer to buy through Amazon marketplace AWS marketplace, can do so with a couple of clicks and be provisioned and get up and running with tenable.io. It's super easy, you can learn about the product. Kick the tires with a free evaluation, and really provision the product very simply. >> Yeah, I would imagine the touch from your guys side goes down significantly when they're just coming right through the marketplace. >> Exactly. That's the idea. Make it super easy for customers to invest in tenable.io and get a great experience in doing it. >> What about your own sales guys though. Is there a little channel conflict? They're like hey come one, I want to sell hat thing, we don't want to go through Amazon. >> Not at all. Our mantra is we want our customer to purchase through the channel they're comfortable with. And if they want to purchase through the AWS marketplace we have a channel for them, if they want to go through our three chair model we have obviously a great experience there as well. >> And clearly Amazon brings a lot of customer eyeballs to the table. >> They're a great partner. >> So, just before we wrap, you guys came out with the vulnerability intelligence report. I wonder if you can share some of the highlights of the things. You guys are obviously keeping track of this, you talked about benchmarking against your peers. And I know there's also a lot of sharing of information within security companies, to kind of know what the bad guys are and some of the patterns and best practices. So, I'm wondering if you can share some of the current trends. What are you seeing? How's the landscape changing? >> Well first of all, we have phenomenal tenable research team. They're phenomenal in terms of the data science, in terms of the vulnerability intelligence. We have a wealth of data in our hands from various deployments and so there's a lot of great number crunching and analysis we can generate from that. What we discovered in the vulnerability and intelligence report, is that security teams are just bombarded with vulnerabilities, literally, bombarded. Last year in 2017 we saw over 15,000 CVE's and unique vulnerabilities hitting the marketplace or hitting the industry. And by the end of this year we're expected to be between 18,000 and 19,000 vulnerabilities. So the trend is just going up, up, up. I think what makes matters worse though, is that when you start looking at those 19,000 vulnerabilities, over 60% of those vulnerabilities are classified as either high risk or critical. >> 65%? >> Around 60%. >> Of the, what was the numerator? 18,000? >> Of those 18,000 to 19,000 vulnerabilities, are classified as high risk or critical risk. So, that's a lot of fire drills that security teams need to chase. And so, what we're trying to achieve is helping our customers, helping the market at large understand what are the true risks out there, not the theoretical risks. What are the actual cyber risks. Meaning what are the vulnerabilities that could be easily exploitable, that have exploit kits already developed. We have our data science team looking at the characteristics of vulnerabilities and which ones would be leveraged by the bad guys and which ones would not be. And we significantly boil that number down so that organizations can focus on only 5% of the number of vulnerabilities that they otherwise would be chasing without changing their overall security risk to the organization. So, prioritization is super, super critical for those organizations. >> Nathan I think we all that separating the signal from the noise. (laughs) >> Jeff, well thanks for having me. >> Nathan, thank you very much, it's great to see you and have a great show. >> Thanks. You too. >> All right, I'm Jeff he's Nathan, you're watching theCUBE. We are at the AWS marketplace and service catalog experience at the Aria, at the quad. Come on by. We're serving free food and drink. See you next time. (lively music)

(dynamic music) >> Hi, I'm Peter Burris, and welcome to another CUBEConversation. This is another very special CUBEConversation in that it's part of a product launch. Today, BMC has come on to theCUBE to launch Helix, a new approach to thinking about cognitive services management. And we're, over the course of the next 20 minutes or so, gonna present some of the salient features of Helix and how it solves critical business problems. And at the end of the segment, at the end of this video segment, we're gonna then go into a CrowdChat and give you, the community, an opportunity to express your thoughts, ask your questions, and get the information that you need from us analysts, from BMC, and also from your peers about what you need to do to exploit cognitive systems management in your business. Now this is a very real problem, this is not something that's being made up. The reality is we're looking at a lot of data-first technologies that are transforming the way business works. Technologies like AI, and machine learning, and deep learning, technologies like big data, having an enormous impact about how businesses behave. These technologies invoke much greater complexity at the application at the systems level and Wikibon strongly believes that we do not understand how businesses can pursue these technologies and these richer applications without finding ways to apply elements of them directly into the IT service management stack. And the reason why is if you don't have high-quality, lower-cost, speedy automation inside how you run your service management overall platform, then it's going to create uncertainty up hiring stack and that's awful for digital business. So to better understand and take us through this launch today, we've got some great guests. And it starts, obviously, with the esteemed Nayaki Nayyar who is the President of the Digital Services Management business unit at BMC, CUBE alum. Nayaki, thanks very much for being here. >> Thank you, Peter, really excited to be here and look forward to our conversation. We are too excited about the launch of BMC Helix and happy to share the details with you. >> So let's start with the why. Obviously, there's a... You know, I've articulated kind of a generalization of some of the challenges that businesses face but it goes deeper than that. Take us through some of the key issues that your customers are facing as they think about this transition to a new way of running their business. >> So, let's put ourselves in the customers' shoes. Then you look at what their journey looks like. Customers are evolving from the online world into the digital world and what we see is, what we call, cognitive world. And the way their journey looks like, especially as customers are entering into the digital world, there are proliferation of clouds. They don't have just one cloud, they have private clouds, hybrid clouds, managed clouds, we call it multi-cloud. So they're entering into a multi-cloud world. In addition, there's also proliferation of devices. It's not just phones that we have to worry about now. As IoT's getting more and more relevant and prevalent, how you help customers manage all the devices and how you provide the service through not just one channel but channel of our customers' or consumers' preference. It could be a Slack as a channel, SMS as a channel, Skype as a channel. So across this multi-cloud, multi-device, and multi-channel, this explosion of technology that is happening in every customer's landscape, and to address this explosion, is where AIML, chatbots, and virtual agents really play a role for them to handle the complexities. So the automation that AIML, chatbots, and virtual agents bring to help customers address these multi-cloud, multi-channel, multi-device world is what we call how we have them evolve from ITSM to cognitive services management. >> Let's talk about that a little bit. We'll get into exactly what you're announcing in a second but historically when we thought about service management we thought about devices. What you're really describing, this transition is, again that notion of how all of these different elements come together in, sometimes, very unique ways and that's what's driving the need for the cognitive. It's not just, you can do multiple clouds, multi-devices, multiple channels, it's your business can put them together in ways that serve your business' needs the best. And now we need a service management capability that can attend to those resources. >> Absolutely. So if you go 10, 15 years back, BMC had a great portfolio. We had Remedy Service Management Suite. We also had Discovery to help customers discover the on-prem assets and provide its service to remedy service management. That's what we had, we were very successful. ITSM, as a category, was created for that whole space. But in this new world of multi-cloud, right, where customers have private clouds, managed clouds, hybrid clouds, multi-devices where IoT is becoming more and more relevant, and multi-channel, customers now have to discover these assets. We call it Discovery as-a-Service but now they can discover the assets across AWS, Azure, OpenStack, and Cloud Foundry and evolve into providing service from reactive to proactive service, and that's what we call Remedy as-a-Service, and then extend that service beyond IT to also lines of business. Now you wanna also provide that service to HR, and procurement, and also various lines of business. And the most important thing is how you provide that experience to your end-users and your end-customers is what we call Digital Workplace-as-a-Service where now customers can consume that service in channel of their preference. They can consume that service through mobile device, of course through web, but also Slack, SMS, chatbots, and virtual agents. So that's what we are combining all of that, that entire suite, we are containerizing that suite using Dockers and Kubernetes so that now customers can run in their choice of cloud. They can run it in AWS cloud, Azure cloud, or in BMC cloud. This whole suite is what we call BMC Helix and helps our customers evolve from ITSM to what we call cognitive services management. >> So that's what BMC's announcing today. >> Yes. >> It's this notion of BMC Helix. >> Yes. >> And it's predicated on the idea, if I can, also of, not only you're going to use these technologies to manage new stuff, we have to bring the old stuff forward. Additionally, we're gonna see a mix of labor, or people, and automation as companies find the right mix for them. >> Right. >> And so we wanna bring and sustain these practices and these approaches forward. Nobody likes a forced migration, especially not in an IT organization. >> Right. >> So that's how we see Helix. if I got this right. >> Yes. >> Helix is gonna help customers bring their existing assets, existing practices, modernize them using some of the new technologies and that's how we get to this new cognitive vision. >> Absolutely. The investments customers have already made in their on-prem assets, in their managing their IT assets, that same concepts come into this new multi-cloud, multi-device, and multi-channel world but now it extends beyond that. It extends beyond just IT to also lines of business and also all these, what we call, omni-channel experiences that you can provide. And this whole suite is, what we call, 3 C's, Helix stands for 3 C's. Everything as a service, Remedy as-a-Service, Discovery as-a-Service, Business Workplace as-a-Service, containerized so that customers can run this in the choice of their cloud, they can run in AWS cloud, Azure cloud, or our cloud with cognitive capabilities, with AIML, and chatbots. And that's how we help them evolve from that existing implementations to this whole new world as they enter into the cognitive world. >> Exciting stuff. >> Absolutely. We are very excited about it. We've been working with a lot of customers already, and we have made really, really good traction. >> So let's do this, Nayaki, let's take a look at a product video that kinda describes how this all comes together in a relatively simple, straightforward way. >> Absolutely. (upbeat music) >> Hi, Peter Burris again, welcome back. We're talking more about BMC's Helix announcement. Great product video. Once again, we're here with Nayaki Nayyar, but we're also being joined by Vidhya Srinivasan who's in Marketing within the Digital Services Management unit at BMC. Thank you very much for joining us in theCUBE. >> Great to be here, thank you. >> So we've heard a lot about the problems, we've heard a lot about BMC Helix as a solution, but obviously it's more than just the technology. There's things that customers have to think about, about how these technologies, how service management, cognitive service management's going to be impacting the business. As businesses become more digital, technology and related services get dragged more deeply into functions. So, Nayaki, tell us a little bit more about how the outcomes within business, the capabilities of businesses are gonna change as a consequence of applying these technologies. >> Absolutely, Peter. So if you look at, traditionally, IT service management was a very reactive process. Every ticket that came in was manually created, assigned, and routed. That was a very reactive process. But as we enter into this cognitive world and you apply intelligence, AIML, you evolve into what we call a proactive and predictive. Before an issue actually happens, you want to resolve that issue. And that's what we call the cognitive services management. And the real business outcomes, you put yourself in a customer's shoes who's providing this service and evolving into this proactive, predictive, and cognitive world, they wanna provide that service at the highest accuracy, at the highest speed, and the lowest cost. That's what is gonna become competitive advantage for every company indifferent of the industry. They could be in a telco, they could be in high-tech, or pharmaceutical. It doesn't matter which industry they are in, how they provide this service at the highest accuracy, highest speed, and lowest cost is gonna be fundamentally a competitive advantage for these customers. >> And when we talk about accuracy, again we're not just talking about accuracy in a technology context. We're talking about accuracy in terms of a brand promise, perhaps. >> Absolutely. >> Or a service promise, or a product promise. >> Yes. >> That's the context. We wanna make sure that the customer is getting what they expect fast, with accuracy, and at low cost. >> Right, every time you tweet or you're SMS-ing your service provider, you expect that response to be at the highest accuracy, at the speed, and the cost. >> So when we start talking about multi-channel, Vidhya, what we're really saying is that this is not just your, you know, this is not just service management for the traditional technology service desk. We're talking about service management for other personas, other individuals, other consumers as well. Take us through that a little bit. >> Yeah, that's right. So we actually take a very holistic approach, right, across the enterprise. So we have end-users who are, at the end of the day, the key subscribers or consumers of our service and we wanna make sure they're very happy with what we provide. We have the agents which kinda goes to the IT persona that people know about in the service desk. But then, as Nayaki said earlier, it's also about extending to a lines of business so you have HR agents, right, people who support HR requests, people who support facilities or procurement request. So making sure that the agent persona is able to do everything that they need to do at the most efficiency level that they can so that they can meet their SLAs to their end consumers is a big part of what Helix, BMC Helix and cognitive service management can provide. And ultimately, when you think about this transformation and where they wanna go, there's a lot of custom applications and custom needs that businesses have. So really thinking about the developer persona and how you actually embed and build intelligent applications through our cognitive microservices that BMC Helix provides is a big part of that value proposition we provide. So as you navigate through this journey and become a cognitive enterprise, how do you make sure that all of these personas throughout your enterprise is able to deliver and get value out of this is what BMC Helix provides for the whole enterprise. >> So the whole concept of incorporating these cognitive capabilities into a service management stack allows us to not only envision, in a traditional way, more complex applications but actually extend this out to new classes of users because we are masking a lot of the complexity and a lot of the uncertainty associated with how this stuff works from that customer. >> That's correct. >> For end-users, for agents, and for developers, and consumers, and customers too. >> Great. >> That's good. >> So you know what... Great conversation. But let's hear what a customer has to say about it, shall we? >> Absolutely, okay. >> My name is Marco Jongen. I work for a company called DSM. And I'm the Director for Service Management within the Global Business Services department. Royal DSM is a global science-based company active in health, nutrition, and materials. And by connecting our unique competencies in life science and in material sciences, DSM is driving economic prosperity, environmental progress, and social advance to create sustainable value for all stakeholders simultaneously. The Global Business Service department is serving the 20,000 employees of DSM spread over 200 locations globally. We are handling, annually, about 600,000 tickets, and we are supporting four business functions: finance, HR, procurement, and IT. We started together with BMC on a shared services transformation across IT, HR, finance, and procurement. And we created a unified ticketing system and a self-service portal using the Remedy system and the Digital Workplace environment. And with this, we are now able to handle all functions in one unified ticketing tool and giving visibility to all our employees with questions related to finance, HR, purchasing, and IT. We were still have and involved with BMC in bringing this product to the next level and we are very excited in the work we have done with BMC so far. >> That was great to hear Royal DSM is transforming its shared services organization with cognitive services management. But, Nayaki, there's no such thing as an easy transformation especially one of this magnitude. We're talking about digital business which is, we're using data assets differently, it's affecting virtually every feature of business today. And now we've got a technology set that's gonna have potentially an enormous impact on IT but everything that IT is being, or everywhere that IT is being employed. That kind of a transformation is not something that people do lightly. They expect their suppliers to help them out. So what is BMC gonna do to ensure that customers are successful as they go through this transformation to cognitive services management? >> Absolutely, Peter. I always say these transformations are not one-month, two-month transformations. These are multi-year transformations and it's a journey that customers go through. We partner very closely with customers in this journey, assessing their requirements, understanding what their future looks like, and helping them every step of the way. Especially in service management, this change, this transformation that is happening, is gonna be very disruptive to their end-to-end processes. Today, all service desks are manned by individuals. Every ticket that comes in gets manually created, assigned, and routed. But if you fast forward into the future world in the next two to three years, that service desk function, which is especially level zero, level one, level two, service desk function, will completely get replaced by bots or virtual agents. It could be 50-50, 70-30, you can pick what the percentage-- >> Whatever the business needs. >> Right? But it is coming. And it is very important for customers to see that change and that transformation that is happening and to be ready for it. And that's where we are working very closely with them in making sure it's not just a system transformation. It's also the people side and the process that have to change. And companies who can do that, what we call cognitive service management using bots and virtual agents at the highest accuracy, highest speed, and the lowest cost, I keep coming back to that because that is what is gonna give them the highest competitive advantage. >> Lot to think about. >> Absolutely. >> Exciting future, crucial for IT if it's gonna succeed moving forward, but even if the business choose to use cloud, you're going to need to be able to discover and sustain service management at a very, very high level. >> Absolutely. How we discover, how we help them discover, how we help them provide that service proactively, predictively, and provide that experience through omni-channel experiences, what this whole thing brings together for our customers. >> Excellent, this has been a great conversation. Nayaki Nayyar, President of BMC's Digital Services Management business unit. Thank you very much for being here on theCUBE and working with us to help announce Helix. Now don't forget folks, that immediately after this, we'll be running the CrowdChat. And in that CrowdChat, your peers, BMC experts, us analysts will be participating to help answer your questions, share experience, identify simpler ways of doing more complex things. So join us in the CrowdChat. Once again, Nayaki, thank you very much. >> Thank you, Peter, and thank you everyone. Thank you all.

>> Narrator: Live from Chicago Illinois, it's theCUBE! Covering VeammOn 2018. Brought to you by Veamm. >> Welcome back to VeammOn 2018 everybody, and you're watching theCUBE. The leader in live tech coverage. We go out to the events, we extract the signal from the noise. This is day one of our coverage of VeammOn, the second year theCUBE has been here. I'm Dave Vellante with my co-host Stu Miniman. Zeb Ahmed is here, he's the Senior Offering Manager for VMWare, with the IBM Cloud, at IBM of course. Thanks for coming on theCUBE, good to see you Zeb. >> Thank you for having me, very excited to be here. >> Yeah so IBM, Cloud, big part of our business. Obviously VMWare, you've been there for a long time. Partnerships with Veamm. Lay it all out for us, what's going on at IBM, IBM Cloud. >> Yeah so we started the VMWare partnership a couple years ago, and our goal was really to build a practice run VMWare which was automated, take it to the next level essentially, not just be a me too player, what everybody else was doing out there, but rather, make the transition from on premises to the Cloud much easier for those VMWare customers. So we've automated a lot of things on the VMWare platform, you can deploy the inverse stack, in a matter of minutes, instead of days and months. So it's a much easier transition, we also work with a lot of partners, such as Veamm, but customers was using on premises, and we've allowed them to have those capabilities in the Cloud as well, in a very automated fashion. >> Quickly if I remember, I think you guys were first doing something with VMWare in the Cloud, you're kind of a year ahead of most. I mean-- >> Stu: It was a few months ahead, they were the first big partner out there with the VMWare Cloud basically. We got, put in Cloud air and everything. >> But in terms of shipping, actually, you guys-- >> We were the first ones, yeah. So we were the first ones to market with Cloud foundation stack right? Yeah and then the other vendors followed as well, but yeah that's been doing great, right? And again, it's fully automated, matter of minutes you can deploy the whole stack, a lot of value add there. >> Yeah Zeb, maybe help set the picture for us a little bit. 'Cause we talk about this multi-cloud world, IBM owns a lot of applications, IBM partners with a lot, where does IBM see themselves playing in this multi-cloud, multi-app world? >> Great question, I think I, so I refer to it two T's. So the first one being the transition, and then the transformation. So the transition is really where the challenge has been for those customers, the barrier to entry, how do these customers actually make that move seamless to the Cloud, especially the space that IBM is in on the enterprise side, these applications are legacy, very very complicated design, a lot of dependencies, so that was a challenge that we tried to solve for. And I think we're at a state now where we've not only solved for that, we've also, I don't know if you guys have seen HCX that we had with VMWare recently, which was a great migration tool, and helps customer on board Cloud, and adapt to Cloud much much faster. And then also build that ecosystem partner network. So all those tools, that we were using on premises like Veamm, right? Making those available in the Cloud for those customers, and it has been great, and also in the transformation side, right? So not only just move them to the Cloud, but also help them leverage, and go up the stack. So micro-services, blockchain, Watson, containers, all those things are available to our customers. >> I think that's a key point that I wanted to highlight is, people often say, how does IBM compete with some of the big Cloud players? You're not just infrastructure as a service, you've got a giant SAS portfolio, you mentioned Watson so, talk about your strategy in that regard. >> Yeah I mean so, the enterprise customer, typical customer, whether it's financial industry or whether health care or transportation et cetera, nobody is just looking for a partner where they can just move the infrastructure too. They're looking for the next state, they're looking to transform the business, they're trying to utilize all those new capabilities that exist in the Cloud today. And IBM has sought for that exactly because not only just use, move your infrastructure and workloads, but now you can consume all those additional gallywads, in the Cloud like Watson, make it for a more intelligent solution in the end. >> Right, so that's a key differentiator. There's only a couple of companies that have that, well I guess you guys, Oracle, Microsoft obviously has the applications, and IBM talks a lot about the cognitive piece, am I correct you can only get Watson in the IBM Cloud, is that still the case, or are you now have it on prem? >> No no, Watson can be consumed using an API. So it's a PAS platform, and if somebody wanted to consume Watson for the on premises workloads and wanted to bring that intelligence for that on premises environment they can do that. >> Dave: Are you seeing more demand for that? >> Oh yes. >> Or is it primarily in the Cloud? >> We've got huge traction in the healthcare space especially, there's a lot of financial customers that are onboarding that as well. So Watson's doing great in that regard. >> Sort of privacy reasons and-- >> Zeb: That's right. >> Zeb one of the things we've been watching with Veamm for the last few years is how do they penetrate deeper into the enterprise. Of course IBM has a strong position in the enterprise, help connect for us how the Veamm and IBM partnerships go together. >> So I think this was a very easy answer for a lot of our customers, because Veamm has a lot of penetration on the on premises workloads, especially on the back-up and business continuity space. So when we looked at the partners and the products that existed in the space, we really looked at the market space, what the customers were consuming. Veamm had a huge market share, and like I said previously, we wanted to solve for those problems and we wanted to keep the tools at the same tool set that they were using today on the premises, so this was very seamless for us, and it is seamless for the customers, to move to IBM Cloud and leverage those same tools exactly. >> So talk about choice because, I can imagine you're getting a call from Ed Walsh, "Hey, how about using my data protection software instead of Veamm?". How do you manage that? >> Zeb: It is tough, right? It is obviously tough, IBM also has a huge portfolio of products, right? In the end the decision was or it really came down to, what is it the customers are looking for? When it came to the back-up space, especially on the VMWare platform, The answer was there, a lot of the VMWare customers use Veamm. In addition to that, Veamm also checks a lot of other boxes for us. So, not only does VMWare stack, but also, I don't know if it's been announced yet or not, but AIX is something of beta that they're launching, at this event, so that is huge for IBM. >> Dave: Really? >> Oh yes, they're also in the bare metal space, so a consolidated view of all your back-ups, all your bare metal, for AIX, for virtualized platform. >> So the power guys will be happy. >> For those that aren't as familiar anymore, I mean remember AIX back in the day, but this is second week in a row I'm talking about AIX. It was Nutanix last week, and it's Veamm today. How much AIX is there still out in the wild? >> There's quite a bit, I mean IBM, if you guys know the background, right? When software was acquired it was a bare metal shop. So with that a lot of the power stuff came as well. So we have a huge power practice in IBM. >> Right, and well it's still, I remember the Steve Mills charts, which showed the availability of AIX versus, the only more available platform was the mainframe, and then with AIX, and then, and you had all that other stuff that everybody else buys but, it's a volume market so it kind of makes sense though. People will pay up for that. And still, a huge install base, now growing, and Nutanix has a relationship with the power guys, so maybe that's where sort of factored in, right? But Linux, of course, is the hot space, right? I mean sure you see it's powering the web. >> Well I'm a VMWare guy, so (laughs). >> There's Linux sitting on top of some of that. >> That's right, of course, of course. >> You've got Linux of mainframe, right? Okay, alright so, talk a little bit more about what you're seeing from the VMWare customer base, how it's synergistic and not just sort of a one way trip into a hotel California. >> Yeah, so a typical VMWare customer that we're seeing who's on premises today are looking to IBM Cloud, or actually take a leap into the Cloud, especially on the enterprise base, these customers want to transform. I mean, there has been a lot of questions for them, especially the customer base IBM focused on, questions around security, compliance, business continuity and data protection and such. So these customers not only want to just make the leap into the Cloud, but they also want to solve for some of these challenges, and also go up to stack like I was mentioning. So, we're seeing a huge push for containers, for those customers that are moving to VMWare, they want to build up the stack, on the PAS layer, and also want to leverage Watson and services like that. >> Yeah, could you expand on that a little more, things like are you working with PKS, the solution with VMWare and Pivotal, and the Kubernetes stuff, or? >> Yes, Kubernetes, Dockers, we also give the customers ability to do their own stuff, go up the stack. I mean, in the end, you know, they can consume us from an IS standpoint and build their PAS on top, or we can, they can use our own, so Kubernetes, Dockers, et cetera. >> What's the story, Stu, with Cloud foundry these days? There was a big push early on, and I fell like I can, I'm not as close as you are, but there seems to be a, I don't want to say a pull back, but maybe less enthusiasm, what's the lay of the land? >> Sure, I mean IBM was one of the earliest bloomix, I believe, and with IBM Cloud, IBM has a few different offerings, I didn't see as big of a push from IBM at the Cloud foundry summit I was at last month, but IBM, like most of the Cloud providers are giving customers choice. >> Zeb: That's right. >> So I guess the question is what-- >> And heavy in Open Source, I mean I'm seeing IBM heavy push, I'm wondering server-less, if you've got any commentary there. We've been looking at like Open Whisk and some of the pieces there. >> Yeah Open Whisk is there, there's, server-less is a thing that a lot of these customers, back to your own original question, a lot of these customers are looking for those types of services, and they're all available in the catalog. >> It's still pretty early, that hasn't overtaken the discussions of the (mumbles) and the (mumbles) stuff in your world has it? >> It hasn't, but I think the enterprise customers who are looking to move to Cloud, they are thinking about those things. So these are some of the check boxes that need to be checked for them for the future growth, et cetera. >> So you've got VMWare's obviously visualization strategy, you've got containers coming, I remember when we had Pat Gelsinger on theCUBE several years ago, when containers were, docker was rocketing, and everybody was like oh docker's going to kill VMWare. And Pat's response was, "Look, we've got the best containers in the world. We're going to embrace containers". They're like, oh sure. But that's exactly what happened. What's IBM's point of view on it? >> Yeah, here's the thing, we want to give them the option to do whatever they want to do. We're seeing a lot of traction on the micro-services side, on the containerization, but I think it's going hand in hand, a lot of the customers are using VMWare platform still, yet they're also leveraging some of these other micro-services and containers, so I think Pat's right on. I think originally what was people were talking about getting rid of the IS layer of VMWare and just going containers completely. Our take is, give the customers all the functionality and the ability to do whatever they want to do, we are seeing it's more of a mix at the moment. >> And we had Edouard Bugnion on recently, found of, one of the founders of VMWare, and he was talking about the challenges in the data center at scale. And in particular when you introduce virtualization and you reduce some of the hardware resources, how do you deliver predictable, high-performance, at scale, and some of the challenges there. That's even on prem. Now introduce Cloud, and you've got distance and latency and other physics so, what's the discussion like with customers around how to architect the ideal Cloud, on prem, hybrid. >> It's a great question, because that is a question I get asked all the time, because in the enterprise base like I said, these customers in a lot of cases have a hybrid or multi-cloud strategy, so network becomes a key part of that discussion. For us, the answer is very simple. We've laid down the fiber of (mumbles) across all these data centers, so when you're talking about latency, and data transfer, and those types of speeds, or having a multi-cloud strategy across the globe, it's a very simple and easy conversation because not only do we make all that information available to our customers, far as what latency they expect from which data center to another one across the globe, but also it's all private, and it's all secure, and it makes for a very good multi-cloud story. >> I don't know if you saw Jenny Remmetti's talk at IBM Think, but she used the term, a lot of people tongue in cheek, but I kind of like it, "incumbent disruptors". I mean look if you're IBM and you've got the client base that IBM has, you better come up with a term like that because that's exactly what you're trying to help your customers do. So, my question is, where does the Cloud and your offering with VMWare fit into the incumbent disruptive scenario? >> Yeah, so VMWare like I said earlier, we didn't want to be a me too player with VMWare. Not only did we want to have a good story with VMWare because obviously VMWare is a huge market share when it comes to virtualization, but on top of that, we wanted to be more futuristic, and solve for those, some of those questions and concerns that the enterprise customer had. So, tight integration on the enterprise base, on the micro-services, containerization, Watson is a huge part of the VMWare platform, you can seamlessly integrate into Watson and really have intelligent decision making on the VMWare platform. So, we wanted to ensure that we were helping our enterprise customers move to Cloud, yet also solve for the future problems. >> So the incumbent piece, both VMWare and IBM, right, incumbent customers, the disruptor would be I guess Cloud, all the new Cloud services, certainly the machine intelligence cognitive, et cetera, components is the disruptive capability, now it's up to you to figure out, okay, how do you apply all that, presumably IBM and your partners can help. >> Yeah and here's the thing, you mentioned earlier, IBM is one of the only companies in the world that can have an end-to-end, not just infrastructure, but also services wrapped around it. So if you're a customer who's not only looking to move to the Cloud but also have services wrapped around, to go end-to-end, IBM is the company to do that for you. >> Dave: Well that's interesting. Okay, I got to ask him Stu. So we had, we were at Dell Technologies World a couple weeks ago, and we had Jeff Clark on, and we asked him, we said, "Look, companies like IBM, HPE, sort of, IBM selling off its X86 division, and HPE splitting, Dell did the opposite. The mega merger". And his comment was, "Well I don't see how you can do end-to-end without both ends". Now, his definition of end is obviously different to your end definition, and I have to ask you, what do you mean by end-to-end? Is the client sort of just a commodity, we can get that anywhere, it's not really an integration challenge? >> So when I'm saying end-to-end what I'm talking about is a enterprise customer looking to move to the Cloud, solve for the future problems, essentially re-invent themselves, transform their business, leverage the new applications, micro-services that are there, but also have services wrapped around it, right? Somebody who's there to help them end-to-end, whether it's just doing migrations for example, right, from on premises to the Cloud, but also help them onboard and guide them on what is there in the Cloud, or the micro-services, or our PAS layer, and how they can transform really. >> So that to me Stu is, Zeb's talking about not a hardware view, of end-to-end, but a, maybe a systems and a software view of end-to-end, in the Cloud services. Alright, Zeb, thank you very much for, do you have one more? You good? Thanks so much for coming on theCUBE. >> Guys, thank you very much, appreciate it. >> Appreciate it. Alright, keep it right there buddy, Stu and I will be back with our next guest. This is theCUBE, we're live from VeeamOn 2018, in Chi-town, we'll be right back. (electronic music)

>> Commentator: Live from Austin, Texas, it's the Cube. Covering KubeCon and CloudNativeCon 2017. Brought to you by Red Hat, the Linux foundation, and the Cube's ecosystem partners. >> Hey welcome back everyone. Live here in Austin, Texas the Cube's exclusive coverage of KubeCon and CloudNativeCon, its third year, not even third year I think it's second year and not even three years old as a community, growing like crazy. Over 4500 people here. Combined the bulk of the shows it's double than it was before. I'm John Ferrier, co-founder of SiliconANGLE. Stu Miniman, analysts here. Next is Gabe Monroy who was lead p.m. product manager for containers for Microsoft Azure, Gabe welcome to the Cube. >> Thanks, glad to be here. Big fan of the show. >> Great to have you on. I mean obviously container madness we've gotten past that now it's Kubernetes madness which really means that the evolution of the industry is really starting to get some clear lines of sight as a straight and narrow if you will people starting to see a path towards scale, developer acceleration, more developers coming in than ever before, this cloud native world. Microsoft's doing pretty well with the cloud right now. Numbers are great, hiring a bunch of people, give us a quick update big news what's going on? >> Yeah so you know a lot of things going on. I'm just excited to be here, I think for me, I'm new to Microsoft right. I came here about seven months ago by way of a Dais acquisition and I like to think of myself as kind of representing part of this new Microsoft trend. My career was built on open source. I started a company called Dais and we were focused on really Kubernetes based solutions and here at Microsoft I'm really doing a lot of the same thing but with Microsoft's Cloud as sort of the vehicle that we're trying to attract developers to. >> What news do you guys have here, some services? >> Yeah so we got a bunch of things, we're talking about so the first is something I'm especially excited about. So this is the virtual kubelet. Now, tell a little bit of story here, I think it's actually kind of fascinating, so back in July we launched this thing called Azure Container Instances and what ACI was first of its kind service containers in the cloud. Just run a container, runs in the cloud. It's micro build and it is invisible infrastructure, so part of the definition of serverless there. As part of that we want to make it clear that if you were going to do complex things with these containers you really need an orchestrator so we released this thing called the ACI Connector for Kubernetes along with it. And we were excited to see people just were so drawn its idea of serverless Kubernetes, Kubernetes that you know didn't have any VMs associated with it and folks at hyper.sh, who have a similar service container offering, they took our code base and forked it and did a version of theirs and you know Brent and I were thinking together when we were like "oh man there's something here, we should explore this" and so we got some engineers together, we put a lot of work together and we announced now, this in conjunction with hyper and others, this virtual kubelet that bridges the world of Kubernetes with the world of these new serverless container runtimes like ACI. >> Okay, can you explain that a little bit. >> Sure. >> People have been coming in saying wait does serverless replace, how does it work, is Kubernetes underneath still? >> Yeah so I think the best place to start is the definition of serverless and I think serverless is really the conflation of three things: it's invisible infrastructure, it is micro billing, and it is an event based programming model. It's sort of the classical definition right. Now what we did with ACI and serverless containers is we took that last one, the event based programming model, and we said look you don't need to do that. If you want to write a container, anything that runs in that container can work, not just functions and so that is I think a really important distinction that I believe it's really the best of serverless is you know that micro billing and invisible infrastructure. >> Well that's built in isn't it? >> Correct yeah. >> What are the biggest challenges of serverless because first of all its [Inaudible 00:03:58] in the mind of a developer who doesn't want to deal with plumbing. >> Yes. >> Meaning networking plumbing, storage, and a lot of the details around configurating, just program away, be creative, spend their time building. >> Yes. >> What is the big differences between that? What are the issues and challenges that service has for people adopting it or is it frictionless at this point? >> Well you know as far I mean it depends on what you're talking about right. So I think you know for functions you know it's very simple to you know get a function service and add your functions and deploy functions and start chaining those together and people are seeing rapid adoption and that's progressing nicely but there's also a contingent of folks who are represented here at the show who are really interested in containers as the primitive and not functions right. Containers are inclusive of lots of things, functions being one of them, betting on containers as like the compute artifact is actually a lot more flexible and solves a lot more use cases. So we're making sure that we can streamline ease of use for that while also bringing the benefits of serverless, really the way I think of this is marrying our AKS, our Managed Kubernetes Service with ACI, our you know serverless containers so you can get to a place where you can have a Kubernetes environment that has no VMs associated with it like literally zero VMs, you'd scale the thing down to zero and when you want to run a pod or container you just pay for a few seconds of time and then you kill it and you stop paying for it right. >> Alright so talk about customers. >> Yep. >> What's the customer experience you guys are going after, did you have any beta customers, who's adopting your approach, and can highlight some examples of some really cool and you don't have to name names or you can, anecdotal data will be good. >> Yeah well you know I think on the blog post announcement blog post page we have a really great video of Siemens Health and Years, I believe is the name, but basically a health care company that is looking, that is using Kubernetes on Azure, AKS specifically, to disrupt the health care market and to benefit real people and you know to me I think it's important that we remember that we're deep in this technology right but at the end of the day this is about helping developers who are in turn helping real world people and I think that video is a good example of that. >> An what was there impact, speed? Speed of developers? >> Yeah, I mean I think it's really the main thing is agility right, people want to move faster right and so that's the main benefit that we hear. I think cost is obviously a concern for folks but I think in practice the people cost of operating some of these systems is tends to be a lot higher than the infrastructure costs when you stack them up, so people are willing to pay a little bit of a premium to make it easier on people and we see that over and over again. >> Yeah Gabe, want you to speak to kind of the speed of company the size of Microsoft. So you know the Dais acquisition of course was already focused on Kubernetes before inside of Microsoft, see I mean big cloud companies moving really fast on Kubernetes. I've heard complaints from customers like "I can't get a good roadmap because it's moving so fast". >> You know I would say that was one of the biggest surprises for me joining Microsoft, is just how fast things move inside of Azure in particular. And I think it's terrific you know. I think that there's a really good focus of making sure that we're meeting customers where they are and building solutions that meet the market but also just executing and delivering and doing that with speed. One of the things that is most interesting to me is like the geographic spread. Microsoft is in so many different regions more than any other cloud. Compliance certification, we take to all that stuff really seriously and being able to do all those things, be the enterprise friendly cloud while also moving at this breakneck pace in terms of innovation, it's really spectacular to watch from the inside. >> A lot of people don't know that. When they think about Azure they think "oh they're copying Amazon" but Microsoft has tons of data centers. They've had browsers, they're all over the world, so it's not like they're foreign to region areas I mean they're everywhere. >> Microsoft is ever and not only is it not foreign but I mean you got to remember Microsoft is an enterprise software company at its core. We know developers, that is what we do and going into cloud in this way is just it's extremely natural for us. And I think that the same can't really be said for everyone who's trying to move into cloud. Like we've got history of working with developers, building platforms, we've entire division devoted to developer tooling right. >> I want to ask you about two things that comes up a lot, one is very trendy, one is kind of not so trendy but super important, one is AI. >> Yes. >> AI with software units impact disrupt storage and with virtual kubelets this is going to be changing storage game buts going to enhance the machine learning and AI capability. The other one is data warehousing or data analytics. Two very important trends, one is certainly a driver for growth and has a lot of sex appeal as the AI machine learning but all the analytics being done on cloud whether it's an IOT device, this is like a nice use case for containers and orchestration. Your comment and reaction for those two trends. >> Yeah and you know I think that AI and deep learning generally is something that we see driving a ton of demand for container orchestration. I've worked lots of customers including folks like OpenAI on there Kubernetes infrastructure running on a Azure today. Something that Elon Musk actually proudly mention, that was a good moment for the containers (chuckling) >> Get a free Tesla. Brokerage some Teslas and get that new one, goes from 0 to 100 and 4.5 seconds. >> Right yeah. >> So you got a good customer, OpenAI, what was the impact of them? What was the big? >> Well you know this is ultimately about empowering people, in this case they happen to be data scientists, to get their job done in a way where I mean I look at it has we're doing our jobs in the infrastructure space if the infrastructure disappears. The more conceptual overhead we're bringing to developers that means we're not doing our job. >> So question then specifically is deep learning in AI, is it enhanced by containers and Kubernetes? >> Absolutely. >> What order of magnitude? >> I don't know but in order of magnitude in enhancement I would argue. >> Just underlying that the really important piece is we're talking about data here >> Yes. >> and one of the things we've been kind of trying to tackle the last couple years of containers is you know storage and that's carried over to Kubernetes, how's Microsoft involved? What's you're you know prognosis as to where we go with cloud native storage? >> Yeah that's a fascinating question and I actually, so back in the early days when I was still contributing to Docker, I was one of the largest external contributors to the Docker Project earlier in my career. I actually wrote some of the storage stuff and so I've been going around Dockers inception 2013 saying don't run databases in containers. It's not cause you can't, right, you can, but just because you can doesn't mean you should (chuckling) >> Exactly. >> and I think that you know as somebody who has worked in my career as on the operation side things like an SLA mean a lot and so this leads me to another one of our announcements at the show which is the Open Service Broker for Azure. Now what we've done, thanks to the Cloud Foundry Foundation who basically took the service broker concept and spun it out, we now are able to take the world of Kubernetes and bridge it to the world of Azure services, data services being sort of some of the most interesting. Now the demo that I like to show this is WordPress which by the way sounds silly but WordPress powers tons of the web today still. WordPress is a PHP application and a MySQL database. Well if you're going to run WordPress at scale you're going to want to run that MySQL in a container? Probably not, you're probably going to want to use something like Azure database for MySQL which comes with an SLA, backup/restore, DR, ops team by Microsoft to manage the whole thing right. So but then the question is well I want to use Kubernetes right so how do I do that right, well with the Open Service Broker for Azure we actually shipped a helm chart. We can helm install Azure WordPress and it will install in Kubernetes the same way you would a container based system and behind the scenes it uses the broker to go spin up a Postgres, sorry a MySQL and dynamically attach it. Now the coolest thing to me about this yeah is the agility but I think that one of the underrated features is the security. The developer who does that doesn't ever touch credentials, the passwords are automatically generated and automatically injected into the application so you get to do things with rotations without ever touching the app. >> So we're at publisher we use WordPress, we'd love, will this help us with scale if we did Azure? >> Absolutely. After this is over we'll go set it up. (laughing) >> I love WordPress but when it breaks down well this is the whole point of where auto scaling shows a little bit of its capabilities in the world is that, PHP does you'd like to have more instances >> Yeah. >> that would be a use case. Okay Redshift in Amazon wasn't talking about much at re:Invent last week. We don't hear a lot of talk around the data warehouse which is a super important way to think about collecting data in cloud and is that going to be an enhanced feature because people want to do analytics. There's a huge analytics audience out there, they're moving off of tera-data. They're doing you guys have a lot of analytics at Microsoft. They might have moved from Hadoop or Hive or somewhere else so there's a lot of analytics workloads that would be prime or at least potentially prime for Kubernetes. >> Yeah I think >> Or is that not fully integrated. >> No I think it's interesting, I mean for us we look at, I personally think using something like the service broker, Open Service Broker API to bridge to something like a data lake or some of these other Azure hosted services is probably the better way of doing that because if you're going to run it on containers, these massive data warehouses, yes you can do it, but the operational burden is high, >> So your point about the >> its really high. >> database earlier. >> Yeah. Same general point there. Now can you do it? Do we see people doing it? Absolutely right. >> Yeah, they do you things sometimes that they shouldn't be doing. >> Yeah and of course back to the deep learning example those are typically big large training models that have similar characteristics. >> Alright as a newbie inside Azure, not new to the industry and the community, >> Yep. >> share some color. What's it like in there? Obviously a number two to Amazon, you guys have great geography presence, you're adding more and more services every day at Azure, what's the vibe, what's the mojo like over there, and share some inside baseball. >> Yeah I got to say so really I'm just saying it's a really exciting place to work. Things are moving so fast, we're growing so fast, customers really want what we're building. Honestly day to day I'm not spending a lot of time looking out I'm spending a lot of time dealing with enterprises who want to use our cloud products. >> And one of the top things that you have on your p.m. list that are the top stack ranked features people want? >> I think a lot of this comes down, in general I think this whole space is approaching a level of enterprise friendliness and enterprise hardening where we want to start adding governance, and adding security, and adding role based access controls across the board and really making this palatable to high trust environment. So I think a lot that's a lot of our focus. >> Stability, ease of use. >> Stability, ease of use are always there. I think the enterprise hardening and things like v-net support for all of our services, v-net service endpoints, those are some things that are high on the list. >> Gabe Monroy, lead product manager for containers at Microsoft Azure Cloud. Great to have you on and love to talk more about geographies and moving apps around the network and multi-cloud but another time, thanks for the time. >> Another time. >> It's the Cube live coverage I'm John Ferrier co-founder of [Inaudible 00:15:21]. Stu Miniman with Wikibon, back with more live coverage after this short break.

>> Announcer: Live from Las Vegas, it's theCUBE. Covering VMworld 2017. Brought to by VMware and its ecosystem partners. (upbeat techno music) >> Okay, we're live here at VMworld 2017's theCUBE's coverage of VMworld 2017. I'm John Furrier. My hosts, Dave Vellante and Stu Miniman. We've got two sets kicking off live here in Las Vegas for our eighth year of coverage. Boomy, we're in the broadcast booth at the Mandalay Bay. Guys, we're here to kick off the show. Three days of wall-to-wall coverage. Three days of great keynotes. Today, big surprise, Andy Jassy, the CEO of Amazon Web Services joined Pat Gelsinger on stage in a surprise announcement together, hugging each other before they talked and even after they talked. This partnership is going to be big. We're going to have coverage, in-depth analysis of that. Dave, VMWorld is now the cloud show with re:Invent. If you look at what's going on, Stu, you've been to many, many shows. This is our eighth year. This was the show. Great community. Now re:Invent has been called the new VMWorld. You put 'em both together, it's really the only cloud show that matters. Google does not have yet a presence. Microsoft has all these shows that are kind of spread all over the place. All the top people are here in IT and cloud at VMWorld and at re:Invent coming up in December. >> Well, John, eight years ago we talked about is this the last stop for IT before cloud just decimates it? And if you go back two years ago, VMware was not in favor. The stock was half of what it is today. Licensed revenue was down 1%. Fast forward to today, it's growing at 10 to 12% a year. Licenses up 13%. It's throwing off operating cash flow at $3 Billion a year. The market's booming. Wall Street's talking VMware now being and undervalued stock. The big question is, is this a fundamental shift in customer mindsets? In other words, are they saying, "Hey, we want to bring the cloud operating model to the business and not try to force our business into the cloud." Or, is this the last gap of onprem. >> Stu, I want to get your thoughts cause I want, squinting through the announcements and all the hype and all the posturing from the vendors is I was looking for, where's hybrid in all this? Where's the growth? And, my validation point on the keynote was when we heard very few words hybrid. Private, on premise was the focus. You guys put out at Wikibon a report called True Private Cloud, Market Sizing. Kind of lay out, that's where the growth is. But, I tweeted private cloud is the gateway drug to hybrid. We're seeing customers now wanting to do hybrid, but they got to do their homework first. They got to do the building blocks on premise, and that is what your calling True Private Cloud. Do you agree? And your thoughts. >> Yeah, so, really good points, John. And the nuance here, 'cause if I'm VMware, I've got a great position in the data center. 500,000 customers. Absolutely, the growth is the move from legacy to True Private Cloud. The challenge for VMware is they already have 500,000 customers there. Those are the customers that are making that shift. So it does not increase vSphere. One of the key things for me, is Pat said, "What vSphere had done for the last 20 years, is what NSX is going to do for the next 10 years, or more." Because they're betting on networking, security, some of these multi-cloud services that they announced. How do those expand VMware so that as True Private Cloud grows and they also do public cloud, VMware has a bigger seat at the table, not just saying "Wait, my customers are shifting. Where are they going?" >> Dave, I want to get your thoughts. You and I talk about all the time on camera, and also privately, about waves. We've been through many waves in the industry. We've seen a lot of waves. Pat Gelsinger has seen many waves, too. Let's talk about Pat Gelsinger because, interesting little tidbits inside the stage area. One, he said "I want to thank you for being the CEO of this company." Stu, you made a comment that this is the first VMWorld where there's not a rumor that Pat's not going to be the CEO. He's kind of kickin' ass and takin' names right now. Stock's up and he put the wave slide out there. And wave slides to me, you can tell the senior management's kind of mojo by how well laid out the wave slide is. He put up a slide on one side. Mainframe mini computer cloud. And the other side client server, internet, IoT Edge. He nailed it, I think. Pat Gelsinger is going to go down as being one of the most brilliant stroke of genius by looking at either laying down what looked like a data center position, and some say capitulate, to Jassy, who's smiling up there saying, "Bring those customers to Amazon." But this is a real partnership. So, Pat Gelsinger, go big or go home. You can't be any bigger, bold bet that Pat Gelsinger right now with VMware, and it looks like it's paying out. What's your thoughts on Pat Gelsinger, the wave and his bold bet? >> Well, I think that businesses are configuring the cloud, John, to the realities of the data. And the data, most of the data, is on prem. So the big question I have it, how is Amazon going to respond to this? And Stu, you and Furrier have had debates over the years. Furrier has said flat out, Amazon is going to do a True Private Cloud, just like Azure Stack. You have said, no. But if Amazon doesn't do that, I think that Pat Gelsinger's going to look like a genius. If they do do that, it's going to become an increasingly more competitive relationship than it is right now. >> Yeah, just a little bit of the inside baseball. Kudos to VMware for getting this VMware on AW out. I hear it was a sprint to the finish because taking cloud foundation, which is kind of a big piece. It's got the VSAN, the NSX, all that stuff, and putting it in a virtual private data center. Amazon owns the data center. They give them servers. This was a heavy lift. NSX, some of the pieces are still kind of early, but getting this out the door, limited availability. It's one data center. They're going to roll out services, but to Dave's point, right, where does this go down the road? Is this Amazon sticking a straw into 500,000 data centers and saying, "Come on in. You know that we've got great services, and this is awesome." 'Cause, I don't see Amazon re-writing their linux stuff to be all native VMware, So, where will this partnership mature? Andy said, "We're going to listen to our customers." "We're going to do what you're asking us." And absolutely today VMware and Amazon, two of these strongest players in the ecosystem today, they're going to listen to their customers. Google, Oracle, IBM, Microsoft, all in the wings fighting for these customers, so it's battle royale. >> You know the straw is in there, John, what's your take, and where do the developers fit in this? >> Well Stu wrote a good point, inside baseball, the key is that success with Amazon was critical. Jassy said basically, this is not a Barney deal, which he kind of modernized by saying most deals are optical really hitting at Microsoft on this one and Google. I mean, they're groping for relevance. It's clear that they're way behind. Everyone's trying to follow these guys. But, on the heels of Vcloud Air, it was critical that they get stake in the ground with Amazon. They took a lot of heat for the Vcloud Air, Stu. This had to get done. Now, my take on this is that, I think it's a genius move. I think Pat Gelsinger, by betting the ranch on Amazon, will go down in history as being a great move. You heard that here, 2017. He's so smart, he wants to be a component of the Amazon takeover, which will happen. It'll be a two-cloud game, maybe three, maybe four, we'll see, but mainly two. But the ecosystem partners on this phase one is key. DXT, Deloitte, Accenture, Capgemini, and then you start to see the logos coming in. They have so many logos, you have to break them down. But more importantly the white space. devops, migration cost, network security and data protection are all filled in with plenty more room for more players. I think this is where the ecosystem was lagging just a few years ago. You saw the shift in the tide. Now you're seeing the ecosystem going, "Wow, I get what VMware's doing. I'm doubling down." It's an Amazon Web Services, VMWare world. All the other cloud players, in my opinion, are really fumbling the ball. >> So, I can infer from that, you see this as a balanced partnerhip i.e. that's not like one needs more than the other. I mean, clearly, Amazon needs VMWARE to reach those 500,000 customers, and clearly, VMware needs a cloud strategy because Vcloud Air and many other attempts have failed. Yes, we said that. It's failed, we asked Pat about that. So, you see it as a more balanced partnership. Do you see that balance of power shifting over time a that straw gets bigger and bigger and bigger. >> Well the Walking Dead or as the Game of Thrones reference going on is kind of the Gray War is happening in cloud. And it really is going to become Amazon versus whoever they can partner with, and the rest of the legacy world. I think the wave slide was impressive to me because this is such a shift from just distributed computing now decentralized with blockchain and AI looming as massive disrupts, I think this is only going to get more decentralized. So whoever has tech that's legacy, will ultimately be toast. And I think Gelsinger's smart to see that wave, and I'm starting to see the movement. It's super early, so, no big bets. It's just be directionally correct and ride that wave. >> Yeah, so, one of the things that got me is last year, it kind of went under the radar that VMware is starting to launch some cloud services, and were very direct, today, that they said there are seven, basically SaaS offerings. It's security, it's cost management. Now, VMWare on AWS, little expensive. We're starting to get the data on how much it is per month or per year or for three-year. But going to have the SaaS offerings. We know Vcloud Air failed, also Paul Moritz had played the Microsoft game. We're going to get this suite of applications. We're going to give you email. We're going to give you, you know, social. We're going to give you all these things. They're all gone. Kind of cleared the table of all those. Now they've got these SaaS applications, so how will that play. I kind of like Pat, very up front on security, and said, "As an industry, we have failed you." Dave, you've been looking at this for a long time. It's a board-level discussion. It's a do-over for security. Does VMware have the chops to play in this space, Dave? Do you buy them as a, you know, valid SaaS provider? >> Well, two questions there. One is in the security front that great tech is always going to get beat by bad user behavior. So this is a board-level issue. As far as SaaS, to me, it's a business model issue that VMware is migrating its business to a routable business model, which is smart. I don't see it as SaaS as an applications, but I see it as a monthly fee. Better to get ahead of it now, while you're hot, than get crushed by Wall Street as you're trying to make that transition like many other companies have failed to do. >> Guys, one thing I want to note is that VMware also laid out their strategy. You kind of heard it there even though that Jassy came on stage. A look it, Jassy's not an idiot, he's smart. He knows what's going on. He knows that he has to win VMware over because VMware ... he's got to balance it. Got 'em in the back pocket on one hand, got a great relationship, Stu, 500,000 customers. Remember, VMware is also an arms dealer. They got the ops, IT operations locked down with their customers. So they have other clouds they can go to. SO, the big trend that we didn't hear, that's out there kind of hiding in plain site is multi-cloud. Multi-cloud is ultimately VMware's strategy. He laid out, one, make private cloud easy. You guys reported on that. Two, deep partnerships with major cloud providers. And three, expand the ecosystem. >> John, so I mean a little bit of kind of rumors I heard. They were actually looking to make the partnership not with AWS at first, it was going to be Google. And Michael Dell said, "If we're going to start with a cloud deal, it's going to be Amazon." The right move, absolutely, that's where it's going to be. But you remember last year, we were here. John, you and I, the announcement was with IBM. Now, no offense to SoftLayer, great acquisition. It's doing well, but IBM does not play at the level of an Amazon. They might have the revenue of a Google in cloud, but, you know, very different positioning. They were up on stage talking about security today. Great position there with analytics. But, we'll see, there's two more days of keynotes. I expect we'll see another cloud provider making some announcements with VMware. And VMware absolutely an arms dealer. They put out on the slide all of their service providers. We've got people like CenturyLink and OVH and Rackspace on theCUBE this week, as well as how their going to play with the Microsoft Google. You've got Michael Dell on tomorrow. I know you're going to talk to him about how Dell fits with Azure Stack, and how the Dell whole family is going to play across all of these because at the end of the day, Michael Dell, and Pat working for him, they want to keep getting revenue no matter who's the winner out there. >> Okay final question as we wrap up the segment. Customers are that watching here, it's clear to me that, we even heard from one on stage, saying, "Well, we're taking baby steps." That wasn't her exact words, but, their going slow to hybrid cloud. All the actions on private as you guys pointed out in our True Private Cloud report on Wikibon.com If you haven't seen it, go check it out, it's going viral. But, this is classic slowness of most enterprise customers. When there's doubt, they slow down. And, one of the things that concerns me, Stu, about the cloud guys right now, whether it's AWS, Google, and Microsoft, is the market's moving so fast, that if these clouds aren't dead simple easy to use, the customers aren't going to go to hybrid. They're going to go back to their comfort zone, which is the true private cloud, going to build that base. It's just got to get easier to manage. It's got to get easier to multi-cloud. And the bottom line is that Amazon's clearly in the lead. So, Jassy has a window right now to run the table on enterprise. He's got about 18-24 months, but Google's putting the pedal to the metal. I mean they're pedaling as fast as they can. Microsoft's cobbling together their legacy, okay, running as fast as they can. But there's this economies of scale, Stu, for them. Your thoughts and reactions. >> Yeah, so, I always thought enterprise simplicity is actually an oxymoron, does not exist. This VMware community, one of the things people loved about it, they were builders. They were all like get in there, and I tweak that. Harvard Business School calls it the Ikea effect. If I help build it just enough, I actually love it a little bit more. VMware's not simple. NSX, hitting about a billion dollars when you get into it is not easy. Security and networking are never going to be you know dirt simple. Amazon, we thought it was real simple, now thousands of services. Absolutely, we've been at that ecosystem for many years. It gets tougher and tougher the more you get into it. And, John, some of the builders there, the developers there, they get in. There's lot of room for this ecosystem to build around that. Because one of the things we talk about as VMware goes to some of these clouds. Where do they get that ecosystem? You mentioned some of the systems integrators, but the rest of the channel, where can they make money? And trying to help, because it's not simple, how do they help get opinionated, make those choices, build it all together. There's professional services dollars there. There's ways to help consult with companies there. >> Ecosystem is the key point. Watch the ecosystem and how that's forming around cloud, hybrid cloud, true private cloud, whatever you want to call it. And then, again, the technology's maturing. It's all about the people and the process to actually affect so called cloud, hybrid cloud, bringing the cloud model to the data, not forcing your business into cloud. >> We got to wrap up here. We've also got Lisa Martin and Keith Townsend and John Troyer, and we got some community guests as well, joining like we did last year. So this will be great. But I want to put something out there, guys, so we can hit up tomorrow and tease it out. I worry about when you have these fast waves that are coming through and the velocity is phenomenal right now. Is that, what tends to crumble, Dave, to your ecosystem point, are these foundations. When you have these industry consortiums, it's kind of like it's political. They've got boards and multiple fingers in it. That could be the suffering point, in my opinion. And that points directly at Cloud Foundry. Cloud Foundry, OpenStack, some of these consortium groups are at risk, in my opinion, if it goes too fast. Stu, to your point. Kubernetes has got great traction. You've got Containers. Dockers got a new CEO. Uber's got a new CEO. I mean the world is moving so fast. So, rhetorical question, industry consortiums. Do they suffer, or do they win in this environment? >> Depends on what they're doing, right? If they're low-level technical standards that advance the industry, I think they do win. I think if it's posturing, and co-opetition, and trying to cut off the one vendor at the knees, it loses. >> Stu, real quick, consortiums. Win or lose in this environment? >> Yeah, we've seen some that have done quite well, and some that have been horrific. So, absolutely, if it gets way too political. Open source has done some really good things, but the foundations, once they get in there, it's challenging and, I'd say, more times than not, they don't help. >> Well, we're in theCUBE. We're breaking it down. We're going to be squinting through all the announcements looking at where the meat on the bone is, where the action is and the relevance and the impact to enterprises and emerging tech. This is theCUBE. I'm John Furrier with Stu Miniman and Dave Vellante. We're back with more live coverage. Day one, after this short break. (techy music)

>> Red Hat OpenShift Container Platform >> Announcer: Live from Boston, Massachusetts, it's theCube Covering Red Hat Summit 2017. Brought to you by Red Hat. >> Welcome back to theCube's coverage, I'm Rebecca Knight your host, here with Stu Miniman. Our guest now is Andrius Benokraitis, he is the Principle Product Manager at Ansible Red Hat Network Automation, thanks so much Andrius. >> Thanks for having me I appreciate it. >> This is your first time on the program. >> Andrius: First time. >> We're nice, >> Really nervous, so, okay. we don't bite. >> Start a little bit with your new to the company relatively >> Andrius: Relatively. >> networking guy by background, can you give us a little bit about your background. >> Sure, I mean, I actually started at Red Hat in 2003. And then did about four five jobs there for about 11 years. And then jumped, went to a startup named Cumulus Networks for about two years. Great crew, and then, now I'm at Ansible, been there since about December, so working on the Network Automation Use Case for Ansible. >> Alright, so networking, has a little bit of coverage here, I remember, you know, something like the Open Daylight stuff and I have, actually there are a couple of Red Hatters that I interviewed at one show ended up forming a company that got bought by Dockers, so you know, there's definitely networking people, but maybe give us a broad view of where networking fits into this stuff that you're working on specifically. >> Yeah, sure thing. I think it's interesting to point out that as everything started in the compute side, and everything started to get disaggregated, the networking side has come along for the ride per se. It's been a little bit behind. When we talk about networking a lot of people just think automatically that's the end. And we're actually trying to think a little bit lower level, so layer one, layer two, layer three, so switching, routing, firewalls, load balancers, all those things are still required in the data center. And when people started using Ansible, it started five years ago on the compute side, a lot of the people started saying, I need to run the whole rec, and I'm not a CCIE, and I don't really know what to do there but I've been thrown in to do something, I'm a cloud admin, the new title right. I have to run the network, so what do I do. I don't know anything about networking, I'm just trying to be good enough, well, I know Ansible, so why don't I just treat switches like servers, and just treat them like, like what I know, they just have a lot more interfaces, but they just treat it that way. So a lot of the expertise came from the ground up with the opensource model and said this is the new use case. >> Well, Jay Rivers, the founder of Cumulus, it's like networking will just be a Linux operating model, you know, extended to the network, which is always like, hey, sounds like a company like Red Hat should be doing that kind of stuff. >> Exactly, it's interesting to see a Bash prompt in the networking right, it's familiar to a lot of people, in the devop space, absolutely. >> So it's a very rapidly changing time, as we know, in this digital computing age, the theme of this conference is the power of the individual, celebrating that individual, the developer, empowering the developers to take risks, be able to fail, make changes, modify. You're not a developer, but you manage developers, you lead developers, how do you work on creating that context, that Jim Whitehurst talked about today. >> I think it starts with, the true empowerment, you have the majority of the networking platforms are still proprietary and walled off, walled off gardens, they're black boxes you can't really do much with them, but you still have the ability to SSH into them, you have familiar terms and concepts from the server side in the networking side. So as long as you have SSH in the box and you know your CLI commands to make changes, you can utilize that in part of Ansible to generate larger abstractions to use the play books in order to build out your data center, with the terms and the Lexicon of YAML, the language of Ansible, things that you already know and utilizing that and going further. >> Can you speak to us a little bit about customers, you know, what's holding them back, how are you guys moving them forward to the more agile development space? >> Our customers are mostly brownfield, they're trying to extend what they already have. They have all their gear, they have everything they have that they need but they're trying to do things better. >> I don't find greenfield customers when it comes to the network side of the house, I mean we've all got what I have and we knew that IT's always additive, so, I mean that's got to be a challenge. >> It's a huge challenge. >> Something you can help with right? >> It's a huge challenge, and I think from the network operators and network engineers, a lot of them are saying, again, they're looking at their friends on the compute side, and they can spin up VMs and provision hardware instantaneously, but why does it have to take four to six weeks to provision a VLAN or get a VLAN added to a network switch? That sounds ridiculous, so a lot of the network engineers and operators are saying, well I think I can be as agile as you, so we can actually work together, using a common framework, common language with Ansible, and we can get things done, and we can get all of this stuff I hate doing, and we don't have to do that anymore, we can worry about more important things in our network, like designing the next big thing, if you want to do BGP, design your BGP infrastructure, you want to move from a layer two to a layer three or an SDN solution. >> I love that you talk about everybody, kind of the software wave and breaking down silos, network and storage people are like, oh my God, you're taking my job away. >> Exactly, completely, no, we're not taking your job. We are augmenting what you already have. We're giving you more tools in your tool belt to do better at your job, and that's truly it, we don't have to, people can be smarter so, if you want to add a VLAN, that can be a code snippet created by the sys admin, it can be in Git, and then the network engineer can say, oh yeah, that looks good, and then I just say, submit. What we see today with some of the customers is, yeah, I want to automate, I really want to automate, and you say, great, let's automate. But then you start getting, you peel back the onion, and you start seeing that, well, how are you managing your inventory, how are you managing your endpoints. And they're like, I have a spreadsheet? And you're like, as a networking guy I guess you, (excited clamoring) >> Networking is scary for a lot, >> It's super scary, yeah. >> So how, do you break that down? >> You do what you can, you do it in small pieces, we're not trying to change the world, we're not trying to say, you're going to go 100% devops in the network. Start small, start with something, like again, you really hate doing, if you want to change, something really low risk, things you really hate doing, just start small, low risk things. And then you can propagate that, and as you start getting confidence, and you start getting the knowledge, and the teams, and every one starts, everyone has to be bought in by the way. This is not something you just go in and say, go do it. You have to have everyone on board, the entire organization, it can't be bottom up, it can't be top down, everyone has to be on board. >> And Andrius, when I talk to people in the networking space, risk is the number one thing they're worried about. They buy on risk, they build on risk, and the problem we have with the networks, they're too many things that are manual. So if I'm typing in some you know, 16 digit hexadecimal code >> From notepad, manually you're copying and pasting >> from like a spreadsheet. Copying and pasting, or gosh, so things like that, the room for error is too high. So there's the things that we need to be able to automate, so that we don't have somebody that's tired or just, wait, was that a one or an L or an I. I don't know, so we understand that it actually should be able to reduce risk, increase security, all the things that the business is telling you. >> All these network vendors have virtual instances. You can do all your testing and deployment, all your testing and your infrastructure, and you can do everything in Jenkins and have all your networking switches, virtually, you can have your whole data center in a virtual environment if you want. So if you talk about lower risk, instead of just copying and pasting, and oh was that a slash 24 or a slash 16, oops, I mean that looked right, but it was wrong, but did it go through test, it probably didn't. And then someone's going to get paged at three in the morning, and a router's down, an edge router's down and your toast. So enabling the full devops cycle of continuous integration. So bringing in the same concepts that you have on the compute side, testing, changes, in a full cycle, and then doing that. >> You talked about the importance of buy in and also the difficulties of getting buy in. How much of that is an impediment to the innovation process, but one of the things we've been talking about, is can big companies innovate? What are the challenges that you see, and how do you overcome them? >> That is the number one, that is the biggest issue right now in the network space, is getting buy in. Whether it's someone who has done it on their own, someone can just install Ansible and do something, and then deploy a switch, but if they leave the company and there's no remediation, if it's not in the MOP, if it's not in the Method of Procedure, no one knows about it. So it has to be part of your, you want to keep all the things you have, all the good things you have today with your checks and balances in the networking, and the CIOs and the people at the top have to understand, you can keep all that stuff, but you have to buy in to the automation framework, and everyone has to be onboard to understand how it fits in in order to go from where you are today to where you want to be. >> At the show here what's exciting your customers? You know, give us a little bit of a viewpoint for people that are checking out your stuff, what to expect. >> Well I think the one thing is they're not used to seeing, they think it's black magic, they think it's just magic. They're like, I can use the same things for everything? I say, yeah, you can. The development processes, the innovation in the community, you know for example, if you want to assist, go ACI Module, it's in GitHub, it's in Cisco's GitHub, you can just go ahead and do that. Now we're trying, starting to migrate those things into core. So the more that we get innovation in the community, and that we have the vendors and the partners driving it, and you're seeing that today, you know, we have F5 here we have Cisco, we have Juniper we have Avi, all those people, you know, they have certified platforms with Ansible, Ansible Core, which is going to be integrated with Ansible Tower, we have full buy in from them. They want to meet with us and say how can we do better. How can we innovate with you to drive the nexgen data centers with our products. >> You talked about yourself as a boomerang employee, what is the value in that, and are you seeing a lot of colleagues who are bouncing around and then coming back from ... >> Absolutely, I think pre acquisition Ansible, the vast majority of the people, I believe were ex-Red Hatters that went to Ansible. So what's really nice to come back home and understand the people that left, that came back to understand already what the, >> And people feel that way, it's a coming home? >> Yeah, it's a coming home, it really is. They understand, you know, they came back, they understood the values of opensource and the culture, again, I started Red Hat in 2003, I see the great things, I see new people getting hired and I see the same things I saw back then, 2003, 2004, with all the great things that people are doing, and the culture. You know, Jim's done a great job at keeping the culture how it is, even way back then when there was only 400 people when I started. >> Andrius, extend that culture, I think about the network community and opensource and you know, you talk about, there's risk there, and you know, you think about, I grew up with kind of enterprise, infrastructure mentality, it's like, don't touch it, don't play with it. We always joked, I got every thing there, really don't walk by it and definitely, you know, some zip tie or duct tape's going to come apart. Are we getting better, is networking embracing this? >> Yes, for sure. I think the nice thing is you start seeing these communities pop up. You're starting to see network operators and engineers, they've been historically, if they don't know the answer, they won't go find it. They kind of may be shy, shy to ask for help, per se. >> If it wasn't on their certification, >> Exactly. >> They weren't going to do it. >> If it wasn't there I'm not going to go, we're bringing them into, so we have, whether there's slack instance, there are networking communities, networking automation, communities, just for network automation. And there's one, there's an Ansible channel, on the network decode, select channel, has almost 800 people on it. So they're coming and now they have a place, they have a safe place to ask questions. They don't have to kind of guess or say, you know what, I'm not going to do that. And know they have a safe place for network engineers, for network engineers to get into the net devop space. >> Another one of the sort of sub themes of this summit is people's data strategy, and customers and vendors, how they're dealing with the massive amounts of data that they're customers are generating. What is your data strategy, and how are you using data? >> So there's two aspects here. So the data can be the actual playbooks themselves, the actual, the golden master images, so you can pull configs from switches, and you can store them and you can use them for continuous compliance. You can say, you know, a rogue engineer might make a change, you know, configuration drift happens. But you need to be able to make those comparisons to the other versions. So we're utilizing things like Git, so you're data strategy can be in the cloud, it can be similar on your side, you can do Stash locally. For part of the operations piece, you can use that. A second piece is, log aggregation is a big piece of the Ansible. So when you actually want to make sure that a change happens, that it's been successful, and that you want to ensure continuous compliance, all that data has to go somewhere, right? So you can utilize Ansible Tower as an aggregator, you can go off using the integrations like Splunk and some other log aggregation connectors with Ansible Tower to help utilize your data strategy with the partners that are really the driving, the people that know data and data structures, so we can use them. >> And one of the other issues is the building the confidence to make decisions with all the data, are you working on that too with your team? >> Yes, we are working with that, and that's part of the larger tower organization, so it goes beyond networking. So, whatever networking gets, everyone else gets. When we started developing Ansible Core and the community and Ansible Tower in-house, we think about networking and we think about Windows, that's a huge opportunity there, you know, we're talking about AWS in the cloud. So cloud instances, these are all endpoints that Ansible can manage, and it's not just networking, so we have to make sure that all of the pieces, all of the endpoints can be managed directly. Everyone benefits from that. >> Andrius thank you so much for your time we appreciate it. >> Thanks again for having me. >> I'm Rebecca Knight for Stu Miniman, thank you very much for joining us. We'll be back after this.

>> Narrator: Live from Austin, Texas. It's theCUBE. Covering DockerCon 2017, brought to you by Docker and support from its ecosystem partners. >> Hi, welcome back. I'm Stu Miniman and this is Silicon Angle Media's theCUBE, worldwide leader in live, enterprise tech coverage here at DockerCon 2017, Austin, Texas. Happy to have on the program, a guest that's been on before. Mazda Marvasti, he's the CEO of appLariat, and he's brought along a managed service provider of his, also a customer of his, Thomas Chamtie, who is the founder of KMicro Technologies. Gentleman, thanks so much for joining me. >> Thank you for having us. >> Thank you sir. >> Alright, so you're both from Orange County, come down here to Austin, I have some local friends of mine they're like, God all these tech conferences are coming down here. I'm like, this seems to be where open source kind of gathers. There's the OSCON coming in a couple weeks, I'll be back later this year for Cube-con, come there. First time for both of you. Just quick, how's the show been for you so far? >> It's been really well received in terms of our product announcement and our company, and not just open source, enterprise. Enterprise applications are all over the place. For us, doing a launch at DockerCon was very appropriate because our company is all about taking your existing applications, new applications and taking them through the journey of not just into the cloud, but into the container era, running on a modern container environment. So it's been well received so far. >> Mazda, it takes some really interesting stuff this week and even the last few months when I've been hearing the cloud space. We've been talking about micro services and cloud-native and everything like that. But customers have, you talk of the enterprise, they've got hundreds if not thousands of existing applications. Therefore, what about them? Ben Golub got on stage, said, "it's not a bimodal world, we need to give them platform, to be able to move forward." That ties into the vision of your company right? >> Oh absolutely. The real problems and the real opportunities are with the existing applications. How do you get those applications same kinds of capabilities that you're trying to give brand new applications being done with microservices. That's why Thomas with KMicro, they're a managed service provider that they're working with customers along the same journey. >> Thomas, before we get into the solution with appLariat, just give us the thumbnail, your background and your company. >> Basically, KMicro as a company is a three year old company, we do managed services for mid to large sized customers. I, myself have been doing IT for about 20 years. Not the fresh guy on the block. But we were introduced to appLariat, when we were looking to do a little project for a client of ours. They had a specific legacy application that they needed to modernize. We're looking for a solution for them that would help them modernize the application, at the same time stay up to date with the latest technologies. Docker seemed, in addition to containerizing, all their application was the solution, was the way to go for them. That's when we were introduced to appLariat and worked together on that project and we've been working with them since then. We love working with these guys, their solution seems to solve a huge issue for a lot of our clients and we look forward to actually doing that again and again for more clients. >> I mean, the challenge here is how does KMicro repeatably do that across customers? So you have consistency which is the same thing when you look at an enterprise. Yeah, I can hand craft an application so that it's containerized and I can deploy it. But how do I get repeatability and consistency across different teams across my applications? That's the scale issue, that you can't use muscle memory to move your applications into the cloud. >> Mazda you're totally right. I've watched the app modernization environment and when you go say, oh what's the killer app, what's the number one thing, it's custom. And that's not scalable, that's not repeatable. Maybe unpack for us a little bit about what you guys bring, that journey along there and how you fit in that spectrum. >> Again, the key is, not to be reliant upon software artists to sit there and script away per application, how does this thing get containerized? What you want to bring is automation and uniformity across these applications. So that you have the same type of consistency for the applications. Then not only that, but when you deploy it, how does the orchestrator manage those deployed containers? Because if you're not going to run it in on an orchestrator, it becomes really difficult to manage it. We use Kubernetes from the backend to actually orchestrate these containers but then you have to have a policy layer that manages that entire infrastructure. Kubernetes is great at knowing that to do, it just doesn't know when to do it. So we provide that when capability. Again, that's a solution that a managed service provider can essentially say okay, now I can repeatably do this across my customers and manage the environments in a similar manner. Versus having to do one-offs. That's what we're trying to get away from. >> Thomas, could you maybe, if it's possible, walk us through a little bit that project with the customer. How long it took, how many people were involved. Where some of the heavy lifting is there. Anything that you've done this, to say oh okay, here's what we've learned for the next time. >> So one of the clients is a GPS tracking company. And they have the DevOps team that were struggling maintaining their code. They have code all over the place. Mazda was more involved on this project than I might have been, so he'll chime in on that. But what we walked out at the end with this client, is that they had a platform that their DevOp could go to and test their code against without having to spend tremendous amount of time or effort into putting all the pieces together. The application will actually do all of that for you from A to Z. They didn't have to worry about storage or processing or memory or any of that stuff. It was just there for them to use. In a second, or a few seconds, they could just conduct an environment, test their code against it, and all was said, when they're done with it, it just shuts down. And it scales up as well, so if they needed to do some testing against an application or a code, they would do the test and then shut down the environment and they're ready to go. And move on. >> Right, the primary use case was that I'm spending way too much money on AWS for DevTest. Because developers would go spin up the VMs and use it to develop and do some unit testing and then the VMs will just live there. So ongoing, continuous basis. Once we put the AWS under a Kubernetes cluster, we're then able to manage the cluster size based on usage and availability, etc. Not only that but then the IT side of the house is able to govern that environment for the developers. The developers don't care to go provision machines or use iAds or anything like that. They just want to deploy their applications, be able to test it and go back and modify code. That's all they care about while IT cares about where does that code go, who looks at it, how does it get tested, what is the cost infrastructure for that. By using our product to manage that AWS cluster, they were able to save 50% on their AWS costs by just managing that DevTest environment. Now we're moving it into production. Those are the kinds of use cases that really you find containerization can bring. You talk about bringing new capabilities to the apps, but it also really goes to cost savings as well. And that was something that-- >> 50% probably conservative even, I would think. We had one of the keynotes case studies this morning, I think it was Visa, was like, 90% of my environment is being utilized less than 10%. >> Mazda: Underutilized, right. >> We know that, heck, I think back, we had server sprawl, we had vm sprawl, now we have cloud sprawl. Is it the whole API economy that allows your software to be able to plug into this, manage some of these environments? How much of it is just cloud, how much is it containers allowing us to do some of this-- >> So every layer we talk about is another layer of abstraction. Cloud is an abstraction, container is an abstraction. Orchestration is an abstraction. Every time you bring these abstractions, you're introducing inefficiency into the system. It brings efficiency in terms of how you develop, how much more secure your application is, how easily you can bring your applications up and down. It brings inefficiencies in terms of these things living on. In terms of sprawl along the cloud boundaries that your applications are running. We bring the efficiency in terms of policies. That says who gets to have what where? And when does it die? Because nothing should live forever. Unless it's your production app, it should not live forever. And when should it die? Expiring those applications and then reclaiming the environment to a smaller size so that your costs are lower or giving the resource to someone else who may need to use it. >> Mazda, Dockers made a real emphasis this week about the ecosystem. Can you talk about partnering with them, how easy it is to work with them, what you're seeing over the last year or so? >> Yeah, we're primarily using the open source Docker containerization mechanism. Because that's really prevalent in the marketplace. We found the same thing in terms of using Kubernetes. Customers are looking for having a degree of control. Close source at a level where your application is running at this point is becoming really difficult. For customers to be able to manage that ability to be able to say okay, I don't have control over this part of my environment, that doesn't make any sense to me. The open source community is really come along in terms of moving the enterprises into their direction. What we're doing is that we're leveraging those open source elements so at the end of the day, we are not in the interconnect between the customer and their applications. They can always go back to those open source tools to manage the applications however they want. We're providing the orchestration layer that sits on top of those open source tools, really unifying them and bringing them together. >> Thomas, what is this whole containerization, your partnership with appLariat mean to your business? How do you expect it to change what you guys are doing? >> There's a couple of things. One of them is modernizing the applications that we talked about a minute ago. But another thing that we wanted to bring on the table and use their solution for was disaster recovery. No one had thought of real time disaster recovery without the efforts of going through a whole bunch of configuration and maintaining, a whole bunch of things. Just to have disaster recovery for a company, no matter what cloud you're in, no matter what infrastructure you use, it doesn't matter. That's when appLariat, we think, is a really good platform that we're going to build on to actually provide what we call real time disaster recovery services for our clients. I think that'll take us, that'll be pretty good for our clients and it's going to help us grow our business as well. >> Yeah, that's another one of those areas where you see a lot of managed service providers providing disaster recovery services but what that means is that they'll provide you a location in the cloud for you to have your application and then services along the lines of people. In bringing those applications to run over there. Then when there is a disaster, have to go through a lot of manual effort to get that site up and running. So what we're talking about, is that if you have your applications already containerized, you can snap shot it anywhere. Once it's snap shotted, it can come up and go down very quickly. Having that ability in terms of being able to provide disaster recovery services on a containerized application is a whole new set of capabilities that now I think it's viable for our organizations. >> Let alone the cost savings as well. Like you were talking about. The cost savings are huge. I only need to speed up the environment when needed. It doesn't have to sit idle, sitting there, costing us money or costing the client money. >> Do you see passing that savings onto your customers? >> Absolutely, absolutely. That's one of the areas that was untapped in the past and with doctoring, containerizing applications technologies, this is the next thing. This is the future of doing disaster recovery. We see it that way. And then we look for-- >> Mazda, oh sorry. >> Yeah, no worries. >> Mazda, want to give you the final word. When people leave DockerCon 2017, what do you want them to know about appLariat and the solutions you're providing. >> What I want them to know is that you don't need to become a scripting ninja to be able to containerize our applications and bring cloud native capabilities to your existing applications. You don't need to become a scripting magician. You can take your existing applications through a very easy process, get them containerized, deploy it on Kubernetes without having to know anything about the underlying infrastructure that it actually takes for those platforms to run. On an ongoing basis, as newer technologies comes along, we'll be the abstraction layer in front of the application for those customers so that they don't need to bother. Do I need to make a bet on something? Do I need to learn new technologies, do I need to upgrade my people? Keep doing what you're doing, your existing CICD process stays as is, your existing developer work levels and skillset remains as is. Everything else should be abstracted and taken away from you. >> Mazda and Thomas, thank you so much for joining us, we'll be back with lots more programming, thanks for watching theCUBE. (electronic music)