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

>> Hi I'm Peter Burris and welcome to another Wikibon Action Item. (electronic music) One of the most pressing strategic issues that businesses face is how to get more value out of their data, In our opinion that's the essence of a digital business transformation, is the using of data as an asset to improve your operations and take better advantage of market opportunities. The problem of data though, it's shareable, it's copyable, it's reusable. It's easy to create derivative value out of it. One of the biggest misnomers in the digital business world is the notion that data is the new fuel or the new oil. It's not, You can only use oil once. You can apply it to a purpose and not multiple purposes. Data you can apply to a lot of purposes, which is why you are able to get such interesting and increasing returns to that asset if you use it appropriately. Now, this becomes especially important for technology companies that are attempting to provide digital business technologies or services or other capabilities to their customers. In the consumer world, it started to reach a head. Questions about Facebook's reuse of a person's data through an ad based business model is now starting to lead people to question the degree to which the information asymmetry about what I'm giving and how they're using it is really worth the value that I get out of Facebook, is something that consumers and certainly governments are starting to talk about. it's also one of the bases for GDPR, which is going to start enforcing significant fines in the next month or so. In the B2B world that question is going to become especially acute. Why? Because as we try to add intelligence to the services and the products that we are utilizing within digital business, some of that requires a degree of, or some sort of relationship where some amount of data is passed to improve the models and machine learning and AI that are associated with that intelligence. Now, some companies have come out and said flat out they're not going to reuse a customer's data. IBM being a good example of that. When Ginni Rometty at IBM Think said, we're not going to reuse our customer's data. The question for the panel here is, is that going to be a part of a differentiating value proposition in the marketplace? Are we going to see circumstances in which companies keep products and services low by reusing a client's data and others sustaining their experience and sustaining a trust model say they won't. How is that going to play out in front of customers? So joining me today here in the studio, David Floyer. >> Hi there. >> And on the remote lines we have Neil Raden, Jim Kobielus, George Gilbert, and Ralph Finos. Hey, guys. >> All: Hey. >> All right so... Neil, let me start with you. You've been in the BI world as a user, as a consultant, for many, many number of years. Help us understand the relationship between data, assets, ownership, and strategy. >> Oh, God. Well, I don't know that I've been in the BI world. Anyway, as a consultant when we would do a project for a company, there were very clear lines of what belong to us and what belong to the client. They were paying us generously. They would allow us to come in to their company and do things that they needed and in return we treated them with respect. We wouldn't take their data. We wouldn't take their data models that we built, for example, and sell them to another company. That's just, as far as I'm concerned, that's just theft. So if I'm housing another company's data because I'm a cloud provider or some sort of application provider and I say well, you know, I can use this data too. To me the analogy is, I'm a warehousing company and independently I go into the warehouse and I say, you know, these guys aren't moving their inventory fast enough, I think I'll sell some of it. It just isn't right. >> I think it's a great point. Jim Kobielus. As we think about the role that data, machine learning play, training models, delivering new classes of services, we don't have a clean answer right now. So what's your thought on how this is likely to play out? >> I agree totally with Neil, first of all. If it's somebody else's data, you don't own it, therefore you can't sell and you can't monetize it, clearly. But where you have derivative assets, like machine learning models that are derivative from data, it's the same phenomena, it's the same issue at a higher level. You can build and train, or should, your machine learning models only from data that you have legal access to. You own or you have license and so forth. So as you're building these derivative assets, first and foremost, make sure as you're populating your data lake, to build and to do the training, that you have clear ownership over the data. So with GDPR and so forth, we have to be doubly triply vigilant to make sure that we're not using data that we don't have authorized ownership or access to. That is critically important. And so, I get kind of queasy when I hear some people say we use blockchain to make... the sharing of training data more distributed and federated or whatever. It's like wait a second. That doesn't solve the issues of ownership. That makes it even more problematic. If you get this massive blockchain of data coming from hither and yon, who owns what? How do you know? Do you dare build any models whatsoever from any of that data? That's a huge gray area that nobody's really addressed yet. >> Yeah well, it might mean that the blockchain has been poorly designed. I think that we talked in one of the previous Action Items about the role that blockchain design's going to play. But moving aside from the blockchain, so it seems as though we generally agree that data is owned by somebody typically and that the ownership of it, as Neil said, means that you can't intercept it at some point in time just because it is easily copied and then generate rents on it yourself. David Floyer, what does that mean from a ongoing systems design and development standpoint? How are we going to assure, as Jim said, not only that we know what data is ours but make sure that we have the right protection strategies, in a sense, in place to make sure that the data as it moves, we have some influence and control over it. >> Well, my starting point is that AI and AI infused products are fueled by data. You need that data, and Jim and Neil have already talked about that. In my opinion, the most effective way of improving a company's products, whatever the products are, from manufacturing, agriculture, financial services, is to use AI infused capabilities. That is likely to give you the best return on your money and businesses need to focus on their own products. That's the first place you are trying to protect from anybody coming in. Businesses own that data. They own the data about your products, in use by your customers, use that data to improve your products with AI infused function and use it before your competition eats your lunch. >> But let's build on that. So we're not saying that, for example, if you're a storage system supplier, since that's a relatively easy one. You've got very, very fast SSDs. Very, very fast NVMe over Fabric. Great technology. You can collect data about how that system is working but that doesn't give you rights to then also collect data about how the customer's using the system. >> There is a line which you need to make sure that you are covering. For example, Call Home on a product, any product, whose data is that? You need to make sure that you can use that data. You have some sort of agreement with the customer and that's a win-win because you're using that data to improve the product, prove things about it. But that's very, very clear that you should have a contractual relationship, as Jim and Neil were pointing out. You need the right to use that data. It can't come beyond the hand. But you must get it because if you don't get it, you won't be able to improve your products. >> Now, we're talking here about technology products which have often very concrete and obvious ownership and people who are specifically responsible for administering them. But when we start getting into the IoT domain or in other places where the device is infused with intelligence and it might be collecting data that's not directly associated with its purpose, just by virtue of the nature of sensors that are out there and the whole concept of digital twin introduces some tension in all this. George Gilbert. Take us through what's been happening with the overall suppliers of technology that are related to digital twin building, designing, etc. How are they securing or making promises committing to their customers that they will not cross this data boundary as they improve the quality of their twins? >> Well, as you quoted Ginni Rometty starting out, she's saying IBM, unlike its competitors, will not take advantage and leverage and monetize your data. But it's a little more subtle than that and digital twins are just sort of another manifestation of industry-specific sort of solution development that we've done for decades. The differences, as Jim and David have pointed out, that with machine learning, it's not so much code that's at the heart of these digital twins, it's the machine learning models and the data is what informs those models. Now... So you don't want all your secret sauce to go from Mercedes Benz to BMW but at the same time the economics of industry solutions means that you do want some of the repeatability that we've always gotten from industry solutions. You might have parts that are just company specific. And so in IBM's case, if you really parse what they're saying, they take what they learn in terms of the models from the data when they're working with BMW, and some of that is going to go into the industry specific models that they're going to use when they're working with Mercedes-Benz. If you really, really sort of peel the onion back and ask them, it's not the models, it's not the features of the models, but it's the coefficients that weight the features or variables in the models that they will keep segregated by customer. So in other words, you get some of the benefits, the economic benefits of reuse across customers with similar expertise but you don't actually get all of the secret sauce. >> Now, Ralph Finos-- >> And I agree with George here. I think that's an interesting topic. That's one of the important points. It's not kosher to monetize data that you don't own but conceivably if you can abstract from that data at some higher level, like George's describing, in terms of weights and coefficients and so forth, in a neural network that's derivative from the model. At some point in the abstraction, you should be able to monetize. I mean, it's like a paraphrase of some copyrighted material. A paraphrase, I'm not a lawyer, but you can, you can sell a paraphrase because it's your own original work that's based obviously on your reading of Moby Dick or whatever it is you're paraphrasing. >> Yeah, I think-- >> Jim I-- >> Peter: Go ahead, Neil. >> I agree with that but there's a line. There was a guy who worked at Capital One, this was about ten years ago, and he was their chief statistician or whatever. This was before we had words like machine learning and data science, it was called statistics and predictive analytics. He left the company and formed his own company and rewrote and recoded all of the algorithms he had for about 20 different predictive models. Formed a company and then licensed that stuff to Sybase and Teradata and whatnot. Now, the question I have is, did that cross the line or didn't it? These were algorithms actually developed inside Capital One. Did he have the right to use those, even if he wrote new computer code to make them run in databases? So it's more than just data, I think. It's a, well, it's a marketplace and I think that if you own something someone should not be able to take it and make money on it. But that doesn't mean you can't make an agreement with them to do that, and I think we're going to see a lot of that. IMSN gets data on prescription drugs and IRI and Nielsen gets scanner data and they pay for it and then they add value to it and they resell it. So I think that's really the issue is the use has to be understood by all the parties and the compensation has to be appropriate to the use. >> All right, so Ralph Finos. As a guy who looks at market models and handles a lot of the fundamentals for how we do our forecasting, look at this from the standpoint of how people are going to make money because clearly what we're talking about sounds like is the idea that any derivative use is embedded in algorithms. Seeing how those contracts get set up and I got a comment on that in a second, but the promise, a number of years ago, is that people are going to start selling data willy-nilly as a basis for their economic, a way of capturing value out of their economic activities or their business activities, hasn't matured yet generally. Do we see like this brand new data economy, where everybody's selling data to each other, being the way that this all plays out? >> Yeah, I'm having a hard time imagining this as a marketplace. I think we pointed at the manufacturing industries, technology industries, where some of this makes some sense. But I think from a practitioner perspective, you're looking for variables that are meaningful that are in a form you can actually use to make prediction. That you understand what the the history and the validity of that of that data is. And in a lot of cases there's a lot of garbage out there that you can't use. And the notion of paying for something that ultimately you look at and say, oh crap, it's not, this isn't really helping me, is going to be... maybe not an insurmountable barrier but it's going to create some obstacles in the market for adoption of this kind of thought process. We have to think about the utility of the data that feeds your models. >> Yeah, I think there's going to be a lot, like there's going to be a lot of legal questions raised and I recommend that people go look at a recent SiliconANGLE article written by Mike Wheatley and edited by our Editor In Chief Robert Hof about Microsoft letting technology partners own right to joint innovations. This is a quite a difference. This is quite a change for Microsoft who used to send you, if you sent an email with an idea to them, you'd often get an email back saying oh, just to let you know any correspondence we have here is the property of Microsoft. So there clearly is tension in the model about how we're going to utilize data and enable derivative use and how we're going to share, how we're going to appropriate value and share in the returns of that. I think this is going to be an absolutely central feature of business models, certainly in the digital business world for quite some time. The last thing I'll note and then I'll get to the Action Items, the last thing I'll mention here is that one of the biggest challenges in whenever we start talking about how we set up businesses and institutionalize the work that's done, is to look at the nature of the assets and the scope of the assets and in circumstances where the asset is used by two parties and it's generating a high degree of value, as measured by the transactions against those assets, there's always going to be a tendency for one party to try to take ownership of it. One party that's able to generate greater returns than the other, almost always makes move to try to take more control out of that asset and that's the basis of governance. And so everybody talks about data governance as though it's like something that you worry about with your backup and restore. Well, that's important but this notion of data governance increasingly is going to become a feature of strategy and boardroom conversations about what it really means to create data assets, sustain those data assets, get value out of them, and how we determine whether or not the right balance is being struck between the value that we're getting out of our data and third parties are getting out of our data, including customers. So with that, let's do a quick Action Item. David Floyer, I'm looking at you. Why don't we start here. David Floyer, Action Item. >> So my Action Item is for businesses, you should focus. Focus on data about your products in use by your customers, to improve, help improve the quality of your products and fuse AI into those products as one of the most efficient ways of adding value to it. And do that before your competition has a chance to come in and get data that will stop you from doing that. >> George Gilbert, Action Item. >> I guess mine would be that... in most cases you you want to embrace some amount of reuse because of the economics involved from your joint development with a solution provider. But if others are going to get some benefit from sort of reusing some of the intellectual property that informs models that you build, make sure you negotiate with your vendor that any upgrades to those models, whether they're digital twins or in other forms, that there's a canonical version that can come back and be an upgraded path for you as well. >> Jim Kobielus, Action Item. >> My Action Item is for businesses to regard your data as a product that you monetize yourself. Or if you are unable to monetize it yourself, if there is a partner, like a supplier or a customer who can monetize that data, then negotiate the terms of that monetization in your your relationship and be vigilant on that so you get a piece of that stream. Even if the bulk of the work is done by your partner. >> Neil Raden, Action Item. >> It's all based on transparency. Your data is your data. No one else can take it without your consent. That doesn't mean that you can't get involved in relationships where there's an agreement to do that. But the problem is most agreements, especially when you look at a business consumer, are so onerous that nobody reads them and nobody understands them. So the person providing the data has to have an unequivocal right to sell it to you and the person buying it has to really understand what the limits are that they can do with it. >> Ralph Finos, Action Item. You're muted Ralph. But it was brilliant, whatever it was. >> Well it was and I really can't say much more than that. (Peter laughs) But I think from a practitioner perspective and I understand that from a manufacturing perspective how the value could be there. But as a practitioner if you're fishing for data out there that someone has that might look like something you can use, chances are it's not. And you need to be real careful about spending money to get data that you're not really clear is going to help you. >> Great. All right, thanks very much team. So here's our Action Item conclusion for today. The whole concept of digital business is predicated in the idea of using data assets in a differential way to better serve your markets and improve your operations. It's your data. Increasingly, that is going to be the base for differentiation. And any weak undertaking to allow that data to get out has the potential that someone else can, through their data science and their capabilities, re-engineer much of what you regard as your differentiation. We've had conversations with leading data scientists who say that if someone were to sell customer data into a open marketplace, that it would take about four days for a great data scientist to re-engineer almost everything about your customer base. So as a consequence, we have to tread lightly here as we think about what it means to release data into the wild. Ultimately, the challenge there for any business will be: how do I establish the appropriate governance and protections, not just looking at the technology but rather looking at the overall notion of the data assets. If you don't understand how to monetize your data and nonetheless enter into a partnership with somebody else, by definition that partner is going to generate greater value out of your data than you are. There's significant information asymmetries here. So it's something that, every company must undertake an understanding of how to generate value out of their data. We don't think that there's going to be a general-purpose marketplace for sharing data in a lot of ways. This is going to be a heavily contracted arrangement but it doesn't mean that we should not take great steps or important steps right now to start doing a better job of instrumenting our products and services so that we can start collecting data about our products and services because the path forward is going to demonstrate that we're going to be able to improve, dramatically improve the quality of the goods and services we sell by reducing the assets specificities for our customers by making them more intelligent and more programmable. Finally, is this going to be a feature of a differentiated business relationship through trust? We're open to that. Personally, I'll speak for myself, I think it will. I think that there is going to be an important element, ultimately, of being able to demonstrate to a customer base, to a marketplace, that you take privacy, data ownership, and intellectual property control of data assets seriously and that you are very, very specific, very transparent, in how you're going to use those in derivative business transactions. All right. So once again, David Floyer, thank you very much here in the studio. On the phone: Neil Raden, Ralph Finos, Jim Kobielus, and George Gilbert. This has been another Wikibon Action Item. (electronic music)

>> Announcer: Live from Boston, Massachusetts it's the Cube, covering Red Hat Summit 2017. Brought to you by Red Hat. >> Welcome back to Boston, everybody. This is Red Hat Summit and this is the Cube, the leader in live tech coverage. I'm Dave Vellante, with my co-host, Stu Miniman and Matt Hicks is here. Is the Vice President of the software engineering for OpenShift and management, at Red Hat. Matt, welcome to the Cube. >> Thank you very much, good to be here. >> So this is where all the action is, is management and management of Clouds and inter Clouds and intra clouds, and it's the sort of next big battleground and you guys seem to be, doin really well there. Have a lot of momentum. >> It's been a good year. I think it's going to be a great year going forward, cause it, it adds a lot of customer value you know, they're seeing the drive to get applications across all these environments, and I think we've hit a good balance of what we can provide in OpenShift, or middle work portfolio management and you hear a lot of customers talking about it all through summits. >> Well we saw some pretty sick demos this morning. I got to ask ya, it was basically the reference model, was okay, got some web logic, and web sphere apps. You know, wink, wink. And you want to modernize them, and so you guys just showed like a five click modernization process. Is it really that simple? Are people really, really doing that? >> Yeah. We have customers that have moved thousands of applications like that, and they're all different sorts of applications. But going from, a proprietary EE stack to getting on something closer to EAP. To deploying it on OpenShift, that is our bread and butter. And it's great because EAP can take advantage of OpenShift, lets customers re-platform the apps that they have. And like we said on Key Net, it sort of frees up your time then to start building the fun stuff. Building the next apps, and you know we've had a ton of success with that. >> Matt so we had the opportunity to talk to some of the innovation award winners. What we haven't actually gotten to cover too much yet, is all the news. So there were a number of announcements in your space, wonder if you could help us, kind of unpack for our audience. >> Sure thing. So we, You will hear a lot about the, just the enterprise production adoption, of the new technologies. Because one of the things for us, it's easy to come up and talk about new technologies. We like actually bringing customers up that have taken that new technology to production. So that's one of the big themes you'll see here at Summit. We launched OpenShift IO. Which for us actually had great success of OpenShift as Hybrid Net platform, Prod. But as you heard from United Health Group, Optum this morning. They have 10,000 plus developers to roll that out to. And we knew we needed to close the gap on how to get empowered developers. So OpenShift IO was the new Cloud based services for that. We will also announce and talk about our container health index. So when you start really making the bed on containers, how do you know what's inside of em, how do you get a simple grading system to understand like A through F. How well maintained is this. As well as being able to look under the covers and understand what goes into that A or what goes into that F. >> And maybe explain that a little bit more, because I think about like, you know, okay, I remember like in the virtualization world, I understood that. So many of containers live a lot shorter life, so, is there, is this just a dashboard that rolls that up, because I want to know probably the general health of what's going on, because there's no way humans going to be able to keep track of it. And I mean, we're not all Google with two billion containers, being brought up and killed every week. But it tends to be, at least from what I've seen, tell me if you see otherwise, that most containers are still much shorter lived than OS's. Or you know, VM4B4. >> You know I think that's, it's one of the advantages. Is that they can be pretty volatile, like that effect. You know, we have capabilities, like in OpenShift, like Image Streams driven to say, "How do you respond and incorporate this?" At the end of the day, if you can grab a container that in our world has an A rating, no security vulnerabilities today, and in a week, you could have multiple critical CVE's, that have been open that now affect that container. And so the benefit of containers is, you can re-roll em, and you can consume that update, but if you don't know about it, and you stay on that old version, you carry the same risk as if you had an out of date OS, that was very static. >> Yeah, I think that answers back to, you know, Ben Gustav, that golden image. And they would pardon that, and they'd leave it that way for two to five years. Right. And we all laughed because my friends in the security space is like, that's the biggest problem we have, is you're not ready for that. So this is, understanding what you've got out there, being able to address that, remediate, you know, push out changes, or know like hey, if you haven't, this is what you're at risk of. >> Absolutely. And that creates for us, it creates this foundation of, both trust between our customers and Red Hat, with their consuming. But then also between Red Hat and our ISV's. Because most of out ISV's, they're not in the Linux business or they're building specialized middle work capabilities on our products. So it's equally important for them to understand that if they're on an out of date version of RHEL, and they've embedded that into their container, that can cause as many problems, and they need to apply the updates in their stack as our customers. >> But that kind of gets to the business model a little bit. And you're engineering, but so I have an engineering question. But, I think most people in our audience understands that you know, Red Hat is a company built on, open source. And you know people say, "Why buy the cows, the milk is free." Well you've perfected that model, you know, 2.4 billion dollars in revenue. Three billion dollars in bookings. So you're obviously doing something right, although, not many have been able to, actually nobody's been able to create a business model like this. My question is from an engineering stand point. When, you're built on open source, and you're not, driven toward a proprietary mindset of okay, let's lock them in to the next REV. How does that change, sort of the engineering mindset, the culture and the protocol going forward. >> I love it. I have been in Red Hat 11 plus years, and everyday you're not tied into, dropping a new feature and pushing customers to that new version for revenue. And so it changes our mindset of, how do we provide value across the entire range of supported offerings that we have. In the case of RHEL, you could stay on some versions of RHEL for quite a while, and we provide value there in keeping that thing working. But at the same point, we're constantly moving this along, adding new innovation. We're able to provide value there. And it, as an engineer, it is refreshing. Sorry. >> I'll chat for a minute. So you, you know, a lot of companies that are 20 plus years old, are criticized. Oh, they don't, innovate. You hear that all the time. They do incremental R and D. And it's true. They may spend a lot on R and D, but R and D is like a feature here, or another feature there. Design, to just keep putting the crumbs out. And what you're saying is, incremental is not, really fundamental part of your plan. >> Absolutely. We can, you know, we want to provide the same value for our customer if they're on RHEL six, or they're looking towards the next major version of RHEL. And they can move anywhere on that life cycle, and that's what they get as part of their subscription. Same thing with OpenShift. And that choice of customers, of being able to take a product, consume anywhere on the life cycle of it, it's good for customers and it's nice for us, because they're just different ways that you innovate. Of driving like, the next new great feature. Then you have other customers, that you are going to provide value through stability. >> So, when you, we go to a lot of these events, as you can imagine. And when you talk to the traditional, you know, software players, you get this massive dose, of well we do that too. We do containers, and, you know, we do Cloud, and we do Hybrid, and. So help us understand, the difference between how they do it and how you do Cloud. >> I think for us, if we picked containers, you know, I was talking to a group of customers this morning of every upstream technology we pick, that we're going to pull together into our products, We don't just pick em up and re-package em and give em to a customer, because we're a support business. So if it breaks at 3 a.m and I have to re-roll a kernel to be able to fix it, I have to understand every piece in the stack. So we start with, we're going to drive a contributor position in the technologies. We pick our bets and we go all in on those areas. So Cooper Netties will carry you know with Google as you know a great technical partner, we run the majority of the SIGs with them. We have a top contributor position, and that we invest really heavily in understanding that technology inside and out. And I think that's what shows in the customer value of we could certainly take stuff, repackage it and ship it. It doesn't carry the same value as being able to work with a customer, drive new features into the product and keep them running in PROD. >> Matt so you mentioned Cooper Netties. And I was actually a little surprised this morning in the key note, I didn't hear Cooper Netties. And I think the reason was, because I heard a lot about OpenShift, and that's just your mechanism for rolling that out there. I'm assuming your customers kind of understand that maybe you could help, you know, explain that a little bit more. >> Absolutely. And so, OpenShift is our enterprise, distribution Cooper Netties is, and that's sort of the business we're in. We have Linux and RHEL is our enterprise distribution of that. We now have Cooper Netties, this really popular community. OpenShift is our distribution of that, and for our customers. >> I was just saying, I guess you couldn't call it RECK. Which, Red Hat Enterprise, Cooper Nettie, probably wouldn't be a good idea. >> The world changes too fast. You pick names a long time ago. But it's a nice motto, because we know it. It's what we've done for a long time, and it builds on everything we've done with RHEL and it connects our middleware portfolio as well. So I've been on the op side, and I've been on the development side, and I love seeing us address stuff right in the gap there for customers. And I think that's why we're seeing so much customer traction. It's a sweet spot for where they've had pain, and it adds a lot of value for em. >> Could you speak a little bit of your customers. Where are they with containers, Cooper Netties, that whole adoption. >> A lot of them in production. Which is nice. It's nice from a support business, because if you have excitement, or if you have early traction, we're a subscription business, so we want to make sure you know, the more customers use it, the more you know, they're going to grow and actually utilize it. And when you hear customers like UHG saying, the 4000 projects built on OpenShift there. Those are, they have built up significant deployments on that, and Barkways, and I know we have a whole list of em that are here today. And so I like that fact of, it's not just a cool technology. Customers have taken all the way into production. And they're being really successful with it. which as an engineer you love. You want to see people using your products and solving problems with them. >> Absolutely. Matt you talked about the ethos of commitment and committers, to open source projects. One of the challenges for a company like yours, is you got to support a lot of different projects. So though, you saying, you make your bets. We've talked a lot about okay, will there ever be another Red Hat that emerges in the big data space. You see Cloud air, and Hortonworks, and they're always sort of lookin at those guys, as possibility. But they always sight the challenge of having to support so many projects. How do you manage that and did you, you've been with Red Hat for a while, did you hit a tipping point, at some point? Cause I mean certainly you have software margin, 80, 90% you know margins. You got a great operating you know margins. So you've crossed that chasm so to speak to pick a bromide, but, others have had such a challenge. Is it because they have to support those projects and it just takes a long time? And you guys baked over 20 years. I wonder if you can give us some insight there. >> You know, I think it's as much art as it is science, I would love to say. Like this is a you know, cold formula that we apply but, we have a good gut feeling for, if you're going to back a technology, or an upstream project, you want to make sure that it's going to expand beyond your own investment, and we've certainly made a lot of wrong bets that the technology doesn't evolve. But you've got to be able to change, and when we see some of the early indicators like in Cooper Netties. Those are the ones where, we like how it's governed, we like how it's structured, we like the other players that are in there, and that's just been one of the unique aspect of Red Hat, is we pick pretty well. >> So Matt, I'm wondering if you're willing to comment, we were at Dockercon a couple of weeks ago, they've done a shift to, how they're managing kind of, but the Moby project to do the open source stuff, what's your take on that? What's Red Hat's positioning there? It's been an interesting dynamic between Docker and Red Hat to watch the last couple of years. >> Yeah you know, I think Moby for us, it's one of, it's about 16 hundred different upstream projects that we pull in across our portfolios. And so, we're certainly watching it, and we're seeing them evolve. We've been involved for the technology for a while now, but we don't necessarily know where that's going to go right now. But we certainly look a it like we do, you know the whole, breath of open source projects we pull in. >> What else is on your horizon? What's exciting you these days? >> You know, I think just seeing the reality of Hybrid Cloud becoming, it's becoming real for our customers. Where they're able, you know, you probably saw some of the Amazon announcements today where, you're able to take services, that might be in the public Cloud and now pull them on Premise. You heard customers talk about taking OpenShift and running that all the way out to the public Cloud. And we love that aspect, because you know, being able to use infrastructure to power applications, I think it's going to change IT and, then all the pieces that emanate around that, it's exciting for ISV's, it's exciting you know, around our management products from Ansible to Cloud forms. It's just a lot that we can do there. >> On the management products, you know, what Dave said, one of the Bromides out there, when I became an analyst seven years ago, it's like we can say, well it's security and management are the biggest problems we have. I feel like I can go to that well anytime I need to do. How are we doing in industry and management. Obviously you've got your position, but you know, as the surface area of the landscape is just expanding exponentially, every. You talked about how many customers are multi Cloud today. So you know, we know there's not a single thing that can do everything but, how are we doing as an industry, in Red Hot specifically? >> I think form Red hat's position, we've had a lot of success with Ansible. Just becoming a core automation technology, cause I think the one common thread is, you have so many choices, you have so many pieces, you have to start automating them. How we did IT 15 years ago, just will not. It won't scale anymore. I think building up from that stack. How you move to policy based management, that's earlier in the space. But there is a ton of capabilities and we've seen customers using, you know from our perspective, it's combining Cloud forms on orchestration, and satellite for content, Ansible for automation. Because I describe it, so I have the operation teams that run our OpenShift online environments. That's a, a relatively small group of people that manages millions of applications. And they change faster than a human could push a button. And so, as customers get into that world, you know we're certainly not in the Google world yet, but when you get that 4A it changes how you have to manage it. It has to become automated, it has to become policy driven, and then it's fun. I like it. Like doing ops in the 90s versus how you do it today. It is refreshing as an operator to just have these tools are your fingertips. >> High frequency application development. Matt thanks very >> It really is! >> Much for coming on the Cube. It's great to see you, and congratulations and good luck going forward. >> Fantastic, thanks S. >> You're welcome. Alright keep it right there everybody. Stu and I will be right back with our next guest. This is Cube, we're live from Red Hat Summit in Boston. We'll be right back. (upbeat music)

>> Voiceover: Live from Austin, Texas, it's the CUBE. Covering DockerCon 2017. Brought to you by Docker in support from its ecosystem partners. >> Hi I'm Stu Miniman here with the final wrap with Jim Kobielus at DockerCon 2017. The CUBE's really excited that we were here for the third year. Have to have a big shout out to our partners and our sponsors that allow us to be here. Of course, Docker's been a great partnership. They talk a lot about ecosystem, really bringing some media people like ourselves giving us some of the great speakers from their company, the partner ecosystem and their customers, and the sponsors for the show, for ourselves, App Lariat, CISCO, Iguazio, Skelety, Cononical, and Red Hat. Without them we couldn't bring you this programming. Really excited to be able to be here. They're starting to tear down the show here, so not a lot of time, so many things to dock to. >> The show itself is containerized. >> We're not even going to be able to talk about the Franklin's barbeque. >> You just did. >> But Jim ... Absolutely. Jim, you've gotten to be on the CUBE here, see some of the show. Give us your quick hits. >> Sure. >> on your takeaways from the show. >> First of all, my first takeaway is this is a vibrant developer ecosystem, clearly. This show is much larger than the year before, and the year before that. It'll probably be twice as large next year. That's my prediction based on the sheer amount of developers migrating into the Docker ecosystem because so many organizations are Dockerizing their applications, containerizing their applications. That's a huge focus for me and Wikibon, as an analyst, is the containerization of application development with microservices and all that, for cloud deployment and multi-clouds, hot, hot, hot across all niches. So, vibrant ecosystem. Docker as the core solution-provider and the centerpiece of this community. Amazing show. The Enterprise Edition, of course, that preceded the announcement of that and the release preceded this show. That's critically important in getting Docker into new accounts that, with a full stack. Clearly it's enterprise ready. Developers, more developers will be exposed to Docker through the EE. Docker, at this show, had a couple of really important announcements for developers. Moby. Project Moby, for customization of container images and so forth, clearly that's going to be a multiplier effect on the ecosystem of developers, ISVs and so forth, Building applications, and customizing containerized Docker applications and images for a wide range of opportunities. >> Yeah, Jim, just want to comment on the Moby piece here 'cause it was really interesting. I think the last couple of years, it's been that pull and tug as to what was the open-source piece, what is the company itself doing, and I think it's clarifying. Kubernetes is a big rising tide in the environment, and all they cared about is they've got the open-source pieces that they need to be able to do Kubernetes. So, with Moby Project it's like okay, now I understand what's out and open. I understand what Docker's doing. I saw some humility from Solomon Hykes, talking, it's like we're listening. We're working, you know, ecosystem, ecosystem, ecosystem. So it was good to see that maturity. I mean, there were some people that I talk to, and they're like, "Oh, will this be the last DockerCon?" I'm like, "I don't think anybody watching this show would say that coming out." As you said, I expect the show to grow; it's doing really well. >> Solomon's totally partner-focused. Look at him. >> Kudos to what they're doing. The partners are excited. It's not just lip service. "Oh yeah. We did some little announcement on the side." No. We're excited. This is there. I know you've got a bunch of pieces, but I want to ask you, are developers excited about taking this legacy ... >> There's lots of news I'm going to analyze. >> Legacy applications, and like helping to move those in, or they only want to work on the cool new stuff? >> Oh, that's a huge theme. MTA. I forget what exactly the acronym stands for, but it's wrapping legacy applications, containerizing them in the Docker ecosystem. That is so important so all of these legacy applications will be Dockerized before long, and refactored, in addition to all the Greenfield development of containerized applications. So the MTA announcement, just as critical as the Moby announcement and so forth in terms, and EE as part of the show, of getting Docker, getting their ecosystem, getting developers working in this environment, more and more developers. This entire Docker, this entire ecosystem has a magnetic force on the developer community, or will. Those are very important. Also I thought the announcements with Microsoft, in terms of containers are going into Windows in a larger way, Linux containers and so forth, that also, 'cause Microsoft has a huge presence obviously in not only enterprise but small to midsize businesses. We're going to see Docker in ever-smaller deployments, hosts and so forth, across the board. More buyers, in other words, more companies will be Dockerizing more applications thanks to, in part, Microsoft as clearly a forerunner. >> Jim, absolutely. I say it at almost every cloud show. I want to follow the data and I want to follow the applications, and you had Microsoft and you had Oracle. You had two of the big players from an application standpoint, Oracle's now in the Docker store. >> Oracle's in the Docker store. That is huge. >> Yeah. >> That has validated containers and Docker for ... >> How about you? From the data standpoint, I heard, we talked to Iguazio about some of the analytics and things ... >> Jim: I'm a data guy, yeah. >> Yeah, you're a data guy. What's a data guy think at a show like this? Is it too infrastructure-focused, or did you see some of the data future here? >> No. It's infrastructure-focused in the sense that it needs to be to harden this technology for enterprise deployment, but it's really dev-ops focused, you know, Kubernetes and everything, and Swarm and whatnot. Look at all these vendors. Here are these tools for the dev-ops life cycle, Kubernetes and everything. That's really, really important. It's all about developers and speeding of development, and putting containerized Docker applications and images into production, and managing them and securing them and so forth. Just the sheer range of dev-ops tools on this show floor that's packing up now was amazing. I'm just uncracking my research here. Very important. So I'm going to wrap up. So, the adoption is amazing. I mean, all these industries, including like Visa. We had a swap-meet, who have adopted Docker into core applications that they're running major businesses on. That's some serious validation in its own right. >> Jim, one of the feedback I got from, it was actually John White from Expedient. >> Okay. >> talked about, and he said he deals with kind of small to mid, to little bit large enterprises, and he said, all that this keynote reminds us of AWS Re:Invent a couple of years ago. >> Oh yeah. >> Big global names. I mean, it's, you know, Visa. You know. Around the globe. Northern Trust. These are not, you know, your regional companies that did a little initiative. It's virtualization started in a lot of small environments. Containerization really started in the likes of Google. I remember the first DockerCon. It was Google and Facebook, and they're the ones that have been doing these projects pre-Docker, and it's slowly moving down. Part of the things I look at is where's the watermark >> Jim: Yeah. >> Where below this you're probably not going to do containers because you're going to go live on a platform that leverages container. The service writers I talked to ... >> Jim: They're going to live in a public cloud like Microsoft, or you know. >> Stu: The cloud guys. I'm going to go to, right, I'm going to go to Microsoft. I'm going to go to Oracle. >> Jim: AWS or IBM. >> Stu: I'm going to go AWS. >> Jim: Whoever it might be. >> Right. Any of them because they're going to just take care of that, and I won't care that it was containerized, so at the end of the day, it's not that tool, it's the wave of that modernization. >> Oh. Yeah, I want to end on a data note because we were talking about data. Okay. I thought Iguazio, I thought Yaron was very, that was very good to have him. There's a lot of storage foundations like Veritas and so forth, so storage in a Docker environment and persistent storage and data protection, pretty important, but also containerizing the new wave of applications that are machine-learning and deep learning and artificial intelligence. We got a fair look at some of that from Solomon yesterday because Solomon mentioned that the open AI consortium is based in their internal test bed training network on Docker, on Swarm and so forth. I, in my prior life, I just joined Wikibon a few weeks ago, I've focused on data science, which is a key development theme, by the way, I'll focus on for Wikibon. I saw a lot of containerization. I saw a fair amount of Docker and a lot of the data science oriented app dev that was going on in the business world. That's going to be a huge theme for me under Wikibon, but also, I mean Solomon sort of alluded to a lot, and so did Yaron, a lot of the work that's going on in the AI community Dockerized their application. Tenser flowing, all that. Huge theme we'll probably see much more of at next year's DockerCon I predict containerizing AI. >> All right. Well. >> For deployment into autonomous vehicles. Whatever. >> Jim, you've long been a CUBE alumn, but now you are a veteran of doing the CUBE. I really appreciate you coming on. >> I'm on this side of the table now. It's amazing. >> Stu: I want to give a shout out to the whole team here. John Furrier, I know, was really disappointed. He loves this show. Usually my co-host. A lot of these open-sourced shows. John, you better be down here in Austin for CUBECon at the end of the year with me. So many shows now through July 4th. The CUBE has so many activities going on. If you go to theCUBE.net, you can see all of our upcoming shows. Always watch us live. If we're not at the show that you think we should be at, go ahead and Ping us. Reach out to us through Twitter or through the website. Jim's research, a lot of it's going to be on Wikibon.com. Siliconangle.com is also where we have some research corner, some of the other pieces there, so check out the whole SiliconANGLE Media for Jim, myself, Ava, Leonard, Brandon, Jay, Sam, who's already heading to the airport. Thank you so much for watching The CUBE. Hope to see you at lots of shows coming around and thank you for sharing.

>> Narrator: From Austin, Texas, it's theCUBE. Covering DockerCon 2017. Brought to you by Docker and support from it's ecosystem partners. >> Hi, I'm Stu Miniman joining with my co-host Jim Kobielus. We're here with theCUBE at DockerCon 2017. When I talked to John Furrier, he said Stu, at DockerCon, we're going to get Solomon Hykes, the founder. We're going to get Ben Golub, the CEO. And we're also, of course, going to get Marianna Tessle, who is the EVP of Strategic Development. Marianna, thank you for having us back again, we've been having a great event. How is everything with you? >> Thank you first of all, it's great. This is the second day of DockerCon. I think we had a great set of announcement yesterday, and an amazing set of announcement today as well. It's really going great. You know I have been roaming the exhibit hall, and actually a couple of people said this is one of the best shows they have been part of, and this very engaged audience is great to hear. >> From the keynote yesterday, the word that stuck out to me is really scaling. We talk about scaling employment, scaling the ecosystem, and the show itself. I was at that first DockerCon when we were wedged into that hotel room, as Ben joked. We had 100 more people than we told the Fire Marshall. Because it was tight. TheCUBE is usually a little bit smaller footprint than we have at some other shows. But, Austin, first of all, you pick great locations. I mean, San Francisco, Seattle, here. I'm looking forward to... Have we announced yet where next year's is? >> I don't think we've announced it yet. Usually it happens in the afternoon. >> Here in Austin. Talk to us a little about some of those announcements and stuff that you're excited about with growing the ecosystem. >> You know, I'm going to continue the theme you started with scale, and obviously like you said, a lot of things are changing, and scaling. One of the things we have noticed more and more are companies and enterprises have really started to use us more in scale and more in production, more apps, more of that going on. One of the trends we've noticed that actually Ben covered on stage today is that there's not just the leading edge of development and all new apps, web apps, but actually, we are starting to see more of traditional apps coming on board as well. More traditions Ops saying, I want those benefits as well. I do not want to go all the way to the extreme of re-writing my code, and going to microservices. But I can reap a lot of the benefits from Docker rising and putting our tools on top. So we're actually seeing more and more of that. And more and more companies. >> The discussion with Solomon, we talked this morning. He said, Oh, I don't know what Lego set we are. And I said, You know that green, flat piece that you can build everything on top of, so you can have your spaceset, your castle, and all the pieces there. You want to be a platform that can build. One of the announcements you guys had today, it's the modernized traditional applications. Maybe you can walk us through a little bit what that means, you know that mix of microservices verses traditional apps. How you guys see yourself participating in a customer's journey. >> Right. So, when we call this program, by the way it has a nickname, MTA. It's like you said, what we've seen is customers and users that want to have benefit across the board was if they write new code as they have more traditional apps with traditional stacks. What we came up with is a way for you to move from a more traditional to the new and Dockerizing really quickly. One of the things we also announced today, is a go-to market and a program helping customers to do that. We have great partners we announced today and I'm sure we're going to have even more, whether it's Microsoft, Avalon, HPE, and Cisco. What we're going to basically provide is a way for you to very quickly start seeing the benefits. Taking the traditional app, and within days, like five days, you should be able to get it in a modern state and start seeing the benefits from that. It's something that we're going to encourage customers to do very quickly and see the benefits. In fact, we had a customer today, Noran Trust, who's already been doing that, talking about the benefits they've been seeing from this program. >> Marianna, in terms of developer enablement, that's everything to getting Dockerizing, a universal phenomenon for wrapping legacy systems, for refactoring existing code, for building greenfield applications. What will Docker do to continue to improve the experience of Project Moby as an enabler of your ISV ecosystem? Going forward, how do you see the experience of front-end in front of Moby evolving to enable very simplicity and speed of development? >> First of all, I have to say that one of the magic, or secret sauces of Docker is our user experience, and the way we made technologies sometimes that were already available super accessible and super useful for developers and ops and users. So I would say that's definitely something that we have the DNA to do. And a project in Moby, we see ISV's and companies, and it doesn't have to be a company, it could be like users, a company that can come in and collaborate and really create a new component, or a new project from what we're going to put there, and hopefully others as well is a whole set of these Lego building blocks they can assemble. >> Are there any plans of Dockers to provide task-oriented skins or experiences on Moby for different roles, different developer roles associated with particular projects, you know, task, or wrapping a legacy system is a different task, obviously, from developing a greenfield containerized application. So to an extend, will you evolve the tool to enable more task oriented role specific interfaces? >> I would say as far as Moby, and across the company, we do have this realization that it could be that developers started to use Docker first, but actually Ops, and even like we talked about, traditional IT, it's pretty prevalent. So our thought is really to cater to all of these audiences, kind of understand, have a conversation with them and understand what exactly they need and what would make them more productive. An example of what I mentioned with the MTA program, the Modernized Traditional Apps, that one is targeted more towards an Ops audience. Different things we do, we try to understand our audience and engage with them, and see what's going to make them most productive. Both in terms of tool sets and in terms of how we bring it to them. >> Right, right. >> Marianna, we had the opportunity to have some of the partner keynote speakers on theCUBE, John Gossman on from Microsoft yesterday, we had Mark Cavage on from Oracle, here. There's a lot going on. Maybe give our audience a little flavor as to some of the other partner activity going on that we might have missed if we weren't watching close. >> I think we had the same conversation last year, just explaining how important it is for us that we work well with our ecosystem. It's a big part of our plan and strategy, and again confirmation that customers want to use choice, different things, that we're not alone in the world, and we really want to engage with a vast ecosystem. So you saw from Cloud providers to a more on-prem infrastructure to ISV's to networking providers, storage providers. Like a whole understanding and way to be a full platform, we really need to understand how to integrate and how to engage with that ecosystem, and how to help customers have benefits of the entire thing combined. So we've been really looking at who are the different leaders; Sometimes customers take us there, they're like, hey please partner with this company or that company. Understanding mapping of what is needed, and starting from Cloud, infrastructure, network, storage, management, monitoring, security, all the way to ISV's. I would, since you brought up that fact that Mark was here, Mark from Oracle. I do want to talk about that because I think that is maybe even a bit new and unique. Another thing that we announced today, the fact that we have Oracle, Dockerizing their apps and putting them in Docker store and that is big, and again, to us that is obviously big, but again, big for user. It's a very easy way to get software you really need. And not only that, we announced several weeks ago, a certification program. The nice thing about that, if something is certified in store, you can really use that with a lot of trust. You know it's been tested, it's secure. That we made sure that it followed best practices. We made sure that our support engagement with the publisher. Again, geared toward enterprises that really want to have that confidence of downloading something from the store and just using it. Again, Oracle is kind of groundbreaking in putting their software there, and we're very excited about that and we think there is going to be more to come. We really are looking forward to this being an amazing service for our users who want to really start from components that exist and the components that they can trust and be productive very quickly. >> I'm curious, how do you think of the Docker store in relation to things like the Amazon Marketplace, or you know, many of your other partners have their own piece. There really is no kind of enterprise app store today so what do you guys want to own? How do you integrate with partners as you look at that develop over time? >> For us, Docker Store started as an enabler as we saw more and more need from users to to basically, Hey, I want.. Let's say since I talked about Oracle I want to use a database. I don't want to go and Dockerize it again. If somebody already did it and they're already prepared, they already went through it, why wouldn't I just re-use it? So the fact that you can put things in this building block and then move them around, it actually enables the idea that you can re-use the same component between different users. So basically you have here something you can do once, and many people can benefit. So that's the benefit we see. It started with official images long ago. We saw unbelievable traction for it. Users really love it, it makes them productive very quickly. We wanted to expand it to a wider set of ISV's, a wider set of components, a wider set of apps, and make them available. We, right now, see it as more of an enabler and again it's one of those things, listening to our users, listening to our customers, we saw that that's one of the things that will make them productive really quickly. >> One of the things we saw in abundance at DockerCon this year is customers of Visa, MetLife, and so forth, up on stage, talking about how they are using Docker in their business for actual live applications. In terms of partners, are you focusing on particular vertical industries in terms of partnership with ISV's and VAR's, particular geographies? Give us a sense for where you're going in terms of diversification of geographies and industries, and in terms of your focus on partnerships. >> Yeah, and again different parts of the stack require different kinds of partnerships. Like on the South end of the stack on the infrastructure, we're looking for partners that either provide on-prem or Cloud infrastructure, or they can provide a set of plug-ins that integrate with us and a set of tools that can be used with Docker to complete and enhance the overall experience of users using Docker. So that's kind of one set of partnerships that started from hardware vendors, to different plug-ins. On the North side of it as we look at it, we just talked about the fact that we have... >> Jim: Top of the application, the application services end of the staff is the North, right? >> Exactly, and all the way to the content. What you actually put inside and what you run. >> Data, so forth and so on. >> Exactly. We'll form a set of partnerships there and making sure that those components are available in store, those components are Dockerized, that companies can really use that, and obviously Microsoft is a huge partner for us in the OS and as your others as well. >> The storage vendors, like Veritask and so forth, there is a fair amount of data inside the ecosystem that really you're going to continue to develop a partnership. >> Absolutely, Adera, Quadera, you've seen a lot, and we continue partner and seeing what's needed there. Understanding we are trying to predict where customers are today, where they're going to maybe, what they will need a year or two from now, and be ready for that. >> Marianna, that leads me to my final question. We know where you're going to be in Europe, you won't tell us yet the location of the North American show for next year, but as you look at the ecosystem, how do you see that developing? When we sit down with you a year from now, what do you hope to have as the progress? >> As I look at the exhibit hall, I am hoping that we're going to see a bigger exhibit hall with every single DockerCon. And, not just for fun, but really, it kind of indicates the collaboration we have with the ecosystem. I would like us to be known as a trusted and productive partner for our ecosystem. And a trusted and productive partner for our customer. That kind of knows to work together with all these contingencies to have amazing results. Like you said, we seen customers on stage, we seen the press releases of people say it took me months to get VM going, it takes me seconds to get this now going. So you see the kind of productivity and we would like to enhance it even more and get there faster. >> Absolutely, Marianna, always a pleasure to catch up with you. We've got a few more interviews left, two days of live coverage, for Jim Kobielus, and I'm Stu Miniman. Thanks for watching theCUBE. [techno music]

>> Voiceover: Live from Austin, Texas. It's the Cube, covering DockerCon 2017, brought to you by Docker and support from its Ecosystem partners. >> Hi, I'm Stu Miniman and joining me, my co-host, for the second day of theCube's program, Jim Kobielus. Really excited to have, not only the founder of Docker, Solomon Hykes, he's also the CTO, Chief Product Officer, did some keynotes here, all over the place. So, Solomon, thank you so much, thanks for havin' us. Congratulations on all the progress and welcome back to theCUBE. >> Thanks a lot! It's a lot of fun! >> So many things to talk about, but let's start with you. How ya doin'? I'm sure there's so much that went into this week. What are you most proud of? What are you most excited about these days? >> Where to start? The cool thing, for me, about DockerCon is I focus on the keynote. We just package up the nice story, try to explain what we're doing, where we're going, and that's a pretty massive team effort. I think it's 30 of us for months preparing, deciding what we want to talk about, working on demos, pulling all-nighters. It's just really fun to see a keynote go from nothing to a really nice, fun story. Then I get to show up and discover all the other cool stuff. I'm like everyone else. I just marvel at the organization, the crowd, the energy. I'm a happy camper right now. >> It's interesting some of the dynamics in the industry. Okay, what's the important part? Who contributes to what? What fits where? Two years ago we had the hugging out as to the runtime and had the Open Source Foundation step in. Big thing at the keynote yesterday, two big things: it was Moby project and Linux Kit. Can you, maybe, unpack for our audience a little bit? What is Docker, the company? What's the Open Source? Who are some of the main players? It was the whole keynote, so we don't have time to get into it. What's real, and what was there? >> You're right, that was the big announcement, the Moby Project. Basically, in a nutshell, we launched Docker and we made it a product and an open source project, all rolled into one. We just kind of adopted this hybrid model, building a product that would just help people be more efficient, developers and ops, and at the same time, we would develop that in the open. That really helped us. It participated in the appearance of this huge Ecosystem. It was a big decision for us. Over time, both grew. Docker grew as a product, and it grew as an open source project. So over time we had to adapt to that growth. On the open source side that meant gradually spitting out smaller projects out of the main one. Now we have dozens of projects, literally. We got containerd. We got SwarmKit. We got InfraKit. We got all these components, and each of those is a project. Then we integrate them. What we're doing now, is we're completing that transformation and making sure there's a place for open source collaboration, free-for-all, openness, modularity, try new things, move fast, break things maybe. Then there's the product that integrates, takes the best parts, integrates them together, makes sure they're tested, they're solid, and then ships that to developers and customers. Basically we're saying, Moby is for open source collaboration. It's our project and all of it. And Docker is the product that integrates that open project into something that people can consume that's simple. It's two complementary parts to our platform. >> Could you talk a little bit about, there's kind of that composable nature of what you're building there. There's what Docker will build from it, and I think you've got a couple of examples of some of your partners. What's going to happen in the Cloud? What's going to happen with some of these others? Walk us through one of those. >> Everything about Docker's modular. So really, if you installed Docker for your favorite platform, whether it's the Mac, Windows, your favorite Cloud provider, Linux server, etc., you're actually installing a product that's an assembly of lots of components. Like I said, these components are developed in the open and then they're assembled. Now with the Moby Project, there's a place to assemble in the open, start the assembly in the open, so that other companies, the broader Ecosystem, can collaborate in the assembly, kind of experiment with how things fit together. The really cool thing about that is it makes it way easier to ports the platform, to expand it and customize it. So if you're a Cloud provider and you see all the pieces and you think "Well, I could optimize that. "I could add a little bit of magic "to make it work even better in my Cloud or in my hardware." Then you can do that in the open. You can do that with a community. Then you can partner with Docker to test it, and certify it, and distribute it as an easy-to-use product. Everything can go faster. >> You mentioned open a lot there. Does that mean that Docker is now closed? There's certain people that are very dogmatic when it comes to open source, so maybe you can parse that for us. >> I think it's the same people that were complaining before that we were confusing our product and an open project. We think of ourselves as having a lot to learn, and there's an Ecosystem that's made of a lot of people and companies and projects that have had a lot of experience with openness in the past. We spend most of our time listening, figuring out what the next step should be, and then taking that next step. People told us, "Clarify the relative place, "open source collaboration and your product." That's what we did. Now, I'm sure someone's going to say, "I preferred it before." Well, we just have to, at some point, chose. The key thing to remember is, Docker does everything in the open, and then integrates it into a product that you can use. If you don't like the product, if you want an alternative, then you still have all the pieces in the open right now. I would say, no. Not only is Docker not going closed, we're actually accelerating the rate at which we're opening up stuff. >> Personally, I felt it was a nice maturation of what you've done before, which was batteries are included but swappable. But we've taken the next step. It reminds me of those cool little science kits my kids get. Where it's like, oh okay, I could free build it or I can do it or I could do some other things. >> We use that tagline. It used to be, Docker has batteries included, but swappable. You can make other batteries and we'll swap them in to the product. We'll decide what's in there. Now everyone can do the swapping. It's a big free-for-all. Honestly, it's fun to watch. >> Is there any piece of Docker, the project, outside of core Docker, that Docker the company will refrain from building, will rely on ISVs to build? Or will Docker the company get involved, or reserve for itself the latitude to get involved in development of more peripheral pieces of the overall project going forward? >> We spent a lot of time thinking about that. Honestly, there's so many different constraints, we just decided we're going to follow the users, follow the customers. We just want a platform that works and solves people's problems. That's the starting point. From there, we work out the implementation details, what technology to use, the order in which to build things. Also, what makes more sense in the core platform and what makes more sense as an add-on. It's kind of on a case-by-case basis. >> Is there a grand vision document or functional service layered architecture that all of these components of the project are implementing or enabling? In other words, will Docker, as a project ever be complete or will it always be open-ended, will it constantly evolve and possibly broaden in scope continuously, indefinitely? >> If you look at the Moby Project on the one side, with experimentations and all the building blocks, I think that's going to just continuously expand. Really, openness is all about scale. There's only so much one company can build on their own, but if you really show the Ecosystem you're serious about really welcoming everybody and allowing for different opinions and approaches, then, honestly, I think there's no limit to how large that project can scale. I think Moby can go into tens of thousands of contributors as open source becomes easier and more accessible, which we're really working on, I think it can go into hundreds of thousands. That's going to take a while. That will, I think, never end growing. I think Docker, the product, the company, the reason we've been so successful is that we've been, well at least we've worked really hard to focus and be disciplined in what problems we want to solve, so it's a more iterative approach. We would rather solve less problems, but solve them really, really well, so that if you're using Docker for developing or going to production, you're really delighted Just every detail kind of fits together. There's a roadmap, of course. We're going to do more and more. But we don't want to rush trying to do everything. >> Solomon, great progress on all of these pieces. I've got the tough one for you. In the last year or so, Kubernetes has really exploded out there. Lots of your Ecosystem is heavily using it. Is it that Docker Swarm and Kubernetes will just be options out there? I look at Microsoft Dasher and they're very supportive of both initiatives. Many of your partners are there. How do you guys look at that dynamic and how would you like people to think of that going forward? >> It's a great case study of why we're transitioning to this open project model with Moby. The whole point is that at any given time, Docker, the product, will not be using all of the building blocks out there. It's just not possible. There's too many permutations. So we have to chose. One of these building blocks is orchestration. A year ago when we decided to build an orchestration, we had really specific opinions on what it should look like, as product builders. We looked around and we decided it needs to be a new kind of a building block. So we built Swarm Kits for our own use and we integrated it. Now that there's an open project for elaboration, we're throwing Swarm Kit in there so that everyone can modify it, extend it, and also replace it with something else. I think the big change, now, is that if you look at something like Kubernetes or Rocket as a container on time. Honestly, I could make a super long list of all the components out there that are really cool and we don't use in Docker. Now you can combine them all in Moby in custom assemblies. And we actually demoed that on stage yesterday. We showed taking some pieces from Docker and taking Kubernetes as a piece and plugging it together and saying "Look, there you go! "Weekend project." I think we're going to see a lot of conversions and reuse of ideas and codes, especially in the orchestration piece. I think over time, the differences between Kubernetes, Swarm Kit, and others will really diminish. We'll just integrate the bits and pieces that make the most sense. I don't really think of Kubernetes as a competitor or a problem. I think of it as another cool component in the Moby Ecosystem. Yeah, I think it's a lot of cool stuff. >> I tell ya, the Kubernetes community is just so thrilled that containerd is now open source. It really solves that issue and really it hasn't been something I've heard a lot, coming into the show. It's one of the themes we wanted to look at, and it hasn't been something that is like, Oh boy! Fight, war, anything like that. Hey! Congrats on that! I want to turn back to your root there. I think about dotCloud to Docker. It's a lot about the application modernization. Fast forward to today, Ben's up on stage talking of the journey. How do we take your legacy applications and wrap them in? What do you think about that kind of progression? We like that spectrum out there to help customers, at least partially, and be able to make changes. But I can't imagine that's when you started Docker that that was one of the use cases that you really thought you'd use. What surprised you? What's changed how you built things? What do you see from customers? >> Actually, you'll find this surprising, but this actually was a use case that we had in mind from the very beginning. I think that was lost in the noise for the first few years in the life of Docker because it became this exciting, new thing. >> Come on, Cloud native, Cloud native! >> Yeah, exactly! Docker has a huge developer community now. We spent a lot of time making it great for devs. The truth is, I used to be sysadmin. I used to be on call. I'm an ops guy first and we learned how to help developers. Developers are the customer. The Docker came out of our ops roots and then it evolved to help the developers. That's something that's now lost in the noise of history. It's a really pragmatic tool. It's built to solve real problems. One design opinion we baked in from the beginning is that it has to allow you to do things incrementally. If Docker forces you to throw away what you have, just to get the benefits, then we screwed up. The whole point is that Docker can adapt to what you're doing. For example, you'll see a lot of details in how Docker's designed to allow for stateful applications to run in there, to allow for your own network model to fit. Before Docker, all the containers solutions, all the paths, required you to change your app. Even things like port discovery. You had to change the source code. Docker did not require that. It gives you extra things you can do if you want to go further. But the starting point is incremental. Honestly, I'm really glad that now that's resonating, that we're reaching that point in the community where there's a lot of people using Docker interested in that, because for a few years I was worried that that would be missed in the noise of early adopters that don't mind rewriting everything. From the beginning, Docker was not just for Cloud-Native, microservices, Twelve-Factor, etc. I'm, personally, as a designer of products, as a pragmatist, I'm just happy that we're there. >> How do you see Docker evolving to support more complex orchestrations for data? For hybrid data cloud, environments private and public? You got the likes of Microsoft, Oracle, and IBM as partners and so forth. They have these complex scenarios now, their customers or petabytes scale and so forth. Where do you see that going, the data, the persistence of storage side of the containerization under Docker going? >> I think there's a lot of work to do. I think over time we're going to see specialized solutions for different uses of data. Data has such a big word. It's like computing. Just like computing now is no longer considered one category but it's specialized, I think data will be the same. I think it's a great fit for this modular Lego approach to the Docker Ecosystem. We're going to see different approaches to different data models, and I think we're going to see a lot modularization and a lot of different assemblies. Again, I think a lot of that will happen in Moby and we'll see a lot of cool, open stuff. We, ourselves, are facing a lot of data related questions, in request for customers. There's stuff in there already. You've got data volumes. And I think you're going to see a lot more on the data topic in the next year. >> Like containerization of artificial intelligence and deep learning and all that. Clearly, that's very incognito so far because, yeah. >> We're seeing a lot of really cool machine learning use cases using Docker already. OpenAI is all on Docker. We watch what they're doing with great interest. >> Are you a member of that consortium? >> Let's say friends and family (laughs). So OpenAI came out of the Y Combinator Ecosystem and Docker is a Y Combinator company. We spend a lot of time with them. I think AI on Docker is a really cool use case. I'm a big fan of that. >> Jim: Cool! Us too! >> Solomon, unfortunately, we're runnin' low on time. Last question I have for you is, there is so many things we can do with Docker now. Here's a bunch of the use cases like, "Oh, I can run lots of applications." Everything from Oracles in the store now, things like that. What is the quick win when you're talking to customers and let's get started? What's the thing that gets them the most excited that impacts their business the fastest? >> Ya know, it's-- >> And it never comes down to one thing, but, ya know. >> Honestly, we keep talking about Lego. I think it's like asking, what's your favorite Lego toy? I think we're maturing in the model. I think Lego is just the perfect analogy because it's a lot of building blocks. There's more and more, but there's also the sets. I think we're consolidating around a few different sets. There's maybe a dozen main use cases. We're seeing people identify with one, and then we're helping them see a starting point there. Here's a starter set for your problem, and then it clicks. >> Yeah, I hear that, and I can't help but think back. You're the big green platform that all my Legos build on. I can have my space stuff. I can have my farm set. Maybe the Duplos don't quite fit on it. It's the platform helping me to modernize a lot of what we're doing. Solomon Hykes, always a pleasure to catch up. >> Likewise! Congratulations on all the progress here, and we look forward to catching up with you the next time! We'll be back. Jim and I will be back with lots more coverage here from DockerCon 2017. You're watching theCUBE. (electronic music)

>> Narrator: Live, from Austin Texas it's the Cube. Covering DockerCon 2017. Brought to you by Docker and support from it's ecosystem partners. >> Hi, and welcome back to the Cube SiliconAngle Media's production of DockerCon 2017. I'm Stew Miniman, and joining me for the rap today I have Jim Kobilus who's been my host for the whole day, part of the Wikibon team. Jim, it's been a long day. Your first full day on the Cube, you've been on many times. >> It's been invigorating, I've learned so much. This is an awesomely substantial show. It's been wonderful. We've had so many great guests, oh my gosh. Ben Golub and everybody who came before. Amazing material. >> Stu: And my other guest for the wrap up is John Troyer who's been on the program many times. He sometimes guest host of the program so Chief Reckoner at TechReckoning. John, thanks for joining us. >> Hey, thanks so much for having me, Stu. >> Alright, so you know, we think right, guests we had some really good guests. It's easy for me at the end of the day when you're like oh it's energy flag oh let's have Ben Golub, the CEO of the company that where Docker's gone, and Jerry Chen who always brings energy, part of the V mafia like yourself, John so really interesting stuff. I want to step back, let's talk about the keynote. So I guess John, I'll start with you. Something we've been talking the last year or so is this Docker, Docker, Docker hype. I felt like a little bit of a hype was let out over the last year with the Docker data center, Docker swarm type activity, some of the ecosystem was a little frustrated with the direction that Docker the company was going, compared to where they wanted the open source part to do. Lot of open source, lot of developer talk today. What's your take on the announcements, the ecosystem, opensource? There's so many things, but let's get us started. >> Sure. Well I didn't quite know what to expect, Stu. We hear about Docker going more enterprise, they just made a big enterprise announcement, so I thought we might come in here and hear 45 minutes on digital transformation. And the standard enterprise keynote that you get at every other keynote. And we did not get that this morning. >> I've seen Michael Dell give that keynote in this building. (laughs) So, totally. >> At least we didn't get that here we've all heard that elsewhere. >> Well, at every conference for the last five years, I think. Ten years. So we talked about the ecosystem, that was the first message this morning. It was about growth of the ecosystem, about growth of the partnership, growth of the projects and so that was definitely playing to their strengths, and then they went straight to the code. This was a developer centered keynote, they did live demos with real code. And so they were really playing to the audience here which I think is still predominately developers. So they were signaling that hey, they weren't going all enterprise. Now, the announcements were also interesting. But I think the signal from the keynote was that we are still here, we're all about developer experience, we're about making things simple. >> Yeah, I don't think there's too many shows where you'd start off and they're like oh, here's how you can build really large containers, easier with this multi-part build and filling all this Docker stuff. It's not the suits, it's not the big customers. Having said, does that mean you won't go to tomorrow's keynote because Ben said it's going to be all the enterprise stuff tomorrow. >> I live for the enterprise stuff. I'm really excited about tomorrow. So hopefully, not too much digital transformation. But I think what Docker has announced the last month, not even talking about what happened today, but the Docker packaging, the Docker data, Docker enterprise edition versus consumer edition, and then not consumer, community addition, sorry. And then the tiers of the Docker, Docker enterprise edition, I think is really kind of brilliant. Docker is at a real turning point in its evolution right now. And there was a lot of confusion around what is Docker the project, what is Docker the engine, what is Docker the company, and I think with this kind of packaging, and then with the announcements today, I really think that they've just cleared up a whole lot of confusion in the ecosystem. >> Yeah, I mean coming in I think I heard a lot of people who were really excited that container D got open sourced. We went to, all three of us went to kubernetes event last night that was over at the Google Fiber Space a couple of blocks from here. And it was oh, cool I get all the opensource like Docker one, that stuff I need, but not all that upper level stuff and advanced things that Docker is building in to it so there's opensource pieces. That goes into the Moby project. Docker's committing, doubling down on a lot of this. We're going to take all these pieces. We're going to work on them, community's going to build it, they can take that compostable view of putting their solutions. And Docker will package and have monetization and things that they'll do there but the partner ecosystem can do different things with that. So what do you guys take on, let's just start with the Moby project first, some of these open source, the whole ecosystem. Positive, you think it's good? >> Yes, very much so. So the maturation of the container ecosystem is in the form of, what you see though the announcements, one of which is customization. So customize containers to the finest degree. They've got that capability now with Moby, exactly. It's all about containers everywhere. Containerization of applications is now the dominant theme in the developer community across all segments. So I think Docker has done the right thing which is doubling down on developers, doubling down on the message and the tooling now for both customization of containers but also for portability with the Linux kit announcement and so forth. Containerization, micro services and so forth across all segments. One of the areas I focus on is artificial intelligence, deep learning. Containerization is coming to that in a big way as well. A lot of it is to drive things like autonomous vehicles and drones and whatnot. But we're going to see containerization come to every other segment of data science, deep learning, machine learning and so forth. It's not just the people at this show, it's other developer communities that are coming to containerization in a big way. And Docker is becoming a premier development tool then for them. Or will be. >> So Jim, Stu, I think even more tactically, there was this confusion about Docker the engine, Docker the container run time, Docker the container specification. Now as pulling that out with container D and now with Linux kit, you always had the thing where Red Hat would say well we have open shift, it's like Docker or it has a piece of Docker or it can work with Docker, you have Cloud Foundry it's like Docker, or has a Docker, or can work with Docker now. And so everybody had to do this dance by saying well, we use some of the technology there. Now, very clean split, very different branding, we use Linux kit, we use container D, we use the Moby framework. And that actually will help again, look, the death of commercial success is confusion. If a buyer does not understand how to get what you want or what you're selling, he's never going to buy anything. >> Yeah, I think we've seen the end of Docker's well, batteries included but removable, cause some confusion in the marketplace. People are like well, but it's not easy, that's kind of what's there, I want to be able to choose the pieces up front. We talked about with Brian Gracely earlier today, what is the pinioned platform because there's certain solutions. Microsoft wants to build what they want. And they've lots of options, but when they want to build an upper level service, they have the pieces underneath that they care about. It's not like oh, okay wait. I have to do this, then I have to uninstall this, that was like in Linux all the time. It's like up, I'm recompiling, I'm recompiling, I have to add things in and remove them it's like no, no, no. I want it in box. In the kernel. And then I can choose and activate what I need. >> My guess is that next year, my prediction is that next year at DockerCon Docker will double down on experience, developer experience. There's not a enough of it yet, here. I think that will be a core theme for them going forward to continue to deepen their mind share in that community. >> I actually, I'll take that and double it. So, one of the reasons that, I think one of the factors, that caused VMWare to come to prominence was its operator experience and its simplicity. VMWare HA high availability was a one check box. VMWare distributed resource schedule which moved virtual machines around, one check box, right? And so with Docker's focus on developer usability and developer experience with today's announcements of Linux kit, that could actually be a huge, huge deal. If in the future, the application development pipeline greatly depends on building a just enough operating system as we used to say back in the day of VMWare with Jerry Chen. >> Stu: Yeah, good 'ol juice. >> Yeah, if that becomes the defining characteristic of building cloud native apps, and it is right? The Docker file is the defining document of our time. If that's the case, and now they've taken it into the Linux distribution world, which could have repercussions for the whole ecosystem, that could be Docker's, you know, again, their magic check box, the developer experience of rolling out a custom stack has just been the level has just been raised. And Linux kit is not new to the world. They just open sourced it today. But it's what they're using to get out their Docker for AWS and Docker for Google cloud. And Docker on public clouds already uses it so it's already in production today. I'm super impressed. >> And I think there was potential that it could have caused more confusion or upset in the ecosystem. But we interviewed Red Hat, and Canonical today and I'm not saying that jumped up and down and embraced and said oh goody, but it wasn't it was like okay, that's fine. It's not there, because there's always got to be that cooptive. I mean Jim, you came most recently from IBM. The company that I most associated with that word co-opetition. So, there's always, there's the swim lanes, there's where you partner together and there's where you sometimes bump heads as to strategy. >> Yeah. And I don't think people should be too alarmed, I mean from a technical level, right there's stuff that runs in containers, there's stuff that runs underneath containers. There's still a role for Ubuntu and there's still a role for Red Hat and there's still a role for CoreOS and Rancher. I don't know enough, I don't have enough of a crystal ball to say what we'll be talking about next year. It could actually have a fairly large dripple effect going out in our ecosystem. >> John, you've also, you've dug into with a couple of vendors here, what about the storage space? It's one we've been digging out of bed. There's still the general consensus is, we still have a little ways to go on the maturity and it's the furthest behind. Big surprise just like VMWare. We spent over a decade doing that. What's your take on storage? Any other comments on just the broad ecosystem, just what needs to work, be worked on and improved over time. >> I think storage is the next area that needs to be worked on. I think that's the next piece that we see as still a little bit fragmented. I've heard from many vendors here at the show that even from Docker itself, that the surprising thing is that containers are not just for cloud native apps. A lot of the enterprise journey, and I imagine we're going to hear about that in tomorrow's keynote, starts with containerizing your big legacy apps. >> Yeah, it's funny. I made a comment at the Google cloud event in San Francisco a month ago. I'm like, hey when did lift and shift all of a sudden become sexy? (laughs) It's of course nuanced on that, and we've had a few interviews Jim, where we've talked about look, there's initiatives that we want to do the cool app modernization and everything there but in the meantime, it is not a bimodal world. We're not going to leave our old stuff there and let it slowly have Larry the engineer keep an eye on it and sleep all the time. The whole world kind of needs to move forward, containers are part of the way to give us the bridge to the future if you will. >> Yeah, how do you containerize the legacy app the mainframe app for example, it's got a petabyte of data in its storage, I mean you just got to work through the data, I mean the deep data issues there, you know. >> Yeah, you can run Docker on a mainframe. I mean, I've done interviews on that. You work with those people, Jim. And it's one of those oh wait, okay, right. So there's pieces that'll be updated and people that are changed. John, you and I have talked. I remember early days of VMWare. It was let me take that horrible 10 year old application that's running on Windows NT which is going into life, and my hardware's going to die, let me shove it into VM and leave it there for another five, ten years. And it was like, please don't do that. >> Sometimes the real world intrudes. I think we are, part of this problem does get smoothed over or confused but we're talking about both on prem apps and public cloud apps. And that can get a little confusing because the storage issues, going back to storage, are a little different. Right? Especially in the public cloud, you've got issues of data locality, you've got issues of latency, even performance and so you see a number of vendors who are approaching it. It's very easy to connect the container to some sort of persistent volume. It is very hard to give something that its performance and is backed up and is, you know is going to be there. People have spent, the storage industry has spent decades on those problems. I don't think we're there yet in terms of the generic container that is floating either in public cloud or on prem. >> And they can handle the hybrid cloud, hybrid data clouds of which there are a myriad in terms of high public private zones within a distributed data architecture with varying degrees of velocity and variety. Managing all that data in a containerized environments with rich orchestration among them, to replication and streaming and so forth. >> You can do it, but it's not, it's cutting edge right now. >> Yeah, it's cutting edge. >> So, John last question I have to ask you is something near and dear to your heart. When you talk about careers and people that are doing, there's a lot of people here, people I used to see in the VMWare community that learning all the cool new stuff. Anything you see is Docker doing evangelism? Program the influencer program type thing? Are you seeing anything in the educational spaces from career space, what can you share? >> Sure, Docker is very rich in community it's kind of been the engine of their growth. They've long had a huge user group program, they have a campus program, they have a mentorship program, and they also have the Docker captains. The Docker captains started, oh I don't know, a year, a year and a half ago and is an advocacy program, I think there's 70 of them now, they work very closely with them. The come from all across the ecosystem which is kind of interesting. Everybody from Dehli MC and many companies. So that's pretty cool that these people, it feels a lot like early days of VMWare, these people have day jobs but yet they spend their nights and weekends hacking on Docker. And Docker takes advantage of that, I mean in the best sort of way. They give them opportunities, they give them platforms to speak, they give them platforms to help others. And I see that's in full force here. They have a track here at the show, so Dockers are leaning heavily on its community. I even saw one person here, Stu from from a mainline storage company said you know what, my company's not here but I am because I have to learn how to do this. I think people who are here have a good next phase of their career. >> That's a smart. A community advocacy program of that sort is actually is even more important than an event like this in terms of deepening the loyalty of the developers to leverage providers and their growing stacks. >> John: Docker the company is very small. There's a very large community and a very small company. >> Stu: Three hundred and some odd people. >> They have to leverage those resources. >> John: Exactly. >> Well, Jim thanks for all your help co-hosting today, John, really appreciate you coming in, especially some of that community ecosystem expertise that you bring. By the way, John's going to be co-hosting open stack summit with me. Another one that will have lost (mumbles) where that ecosystem community is and where it's going in a couple of weeks in my home state of Massachusetts in Boston. So be sure to tune in tomorrow, we've got a full day of coverage. First guest is going to be Solomon Hykes coming off the day two keynote. We're going to talk a little bit more about enterprise. We got a full lineup of guests. So be sure to check out siliconangle.tv for everything there. So for Jim Kobielus, John Troyer and myself Stu Miniman, thank you for watching day one of the Cube's coverage of DockerCon 2017. (upbeat music)

>> Announcer: From Austin, Texas, it's theCUBE covering DockerCon 2017. Brought to you by Docker and support from its ecosystem partners. (techno music) >> Welcome back. Hi, I'm Stu Miniman, joined with Jim Kobielus. You're watching theCUBE's SiliconANGLE Media's production of DockerCon 2017. We're the worldwide leader in live enterprise tech coverage. And we can't finish any DockerCon without having Jerry Chen on. So, Jerry, partner with Greylock, always a pleasure to interview you. We've had you on the Amazon shows a lot, Docker, other ecosystem shows, so, great to see ya. >> Stu, Jim. Hey, thanks for having me, as always. It's great to be here. >> Alright, so first of all, I mean, you invested back in the dotCloud days. Could you imagine, when you were meeting with Solomon and those guys and everything that we'd be here with 5,500 people as to where they'd go? What's your take on the growth? >> Every year just blows my mind, both in open-source community developers, ecosystem partners, and more recently, past year and a half, the enterprise customers that take Docker seriously, or replatformed applications on Docker, amazes me. I think I did an investment in 2013, and there were a few hundred thousand downloads of Docker, now there's billions and billions of containers being pulled. When I talk to CIOs that I deal with frequently, they're like, "Docker containers, what is this thing, pants?" And then, (laughter) three and a half, four years later, I can't have a conversation without a Fortune 500 CIO without talking about their Docker container strategy. >> By the way, I hear if you do send back a belt or something that's broken to the Docker people, they'll fix it for you, and maybe send some whale stickers. >> It's like the old school Nordstroms where they take any return. They're this urban store, with the four tires return to Nordstrom, return some pants, you'll be fine. >> You know, we work on container strategy, but we're also your repair shop for you know, men's apparel. So, it's always interesting to look at-- >> Jim: Integration fabric. >> Brilliant. You know, the maturation of technology, of ecosystem, of monetization. I feel like you talked about the growth of the containers. We've seen the ecosystem. It's gone through some fits and spurts and changes over the last couple of years. I think we're really well-received this week. And then there's the money maturation and how they mature that. What do you see? How does open-source fit into your investment strategy, and any commentary on Docker and beyond? >> I was thinking about this on the flight over here today. Open source today is very different than open source five years ago, 10 years ago, as 15. So what what Red Hat did 20 years ago, is very different than what Xen tried to do 10 years ago. When I was at VMware, very different from what Docker is doing today. And it's different in a couple ways. I think the way you monetize is different. Because you have cloud, and cloud changes things. The ecosystem's very different, because all of a sudden the developers, contributors, are not just kind of your misfits and rebels working on the weekends. They are Fortune 100, Fortune 500 companies. Their jobs are now dedicated to this. And then the business models of the developers' ecosystem, how you work with them is very different. So before, you had maybe one or two models to make money in open source. Or one or two ways to develop a community. We did that at Red Hat, which Greylock was lucky enough to be investors in years ago. I was at VMware around Cloud Foundry, we built that. We had a model mine, we had a spring source as well, and what you've seen Docker in the past three or four years, is they're really pioneering a way to bring open source and community ecosystem into the next 10-20 years. So I think it's one to watch. I think Solomon's probably as good as anybody understanding what developers need. >> So a little broader, what's your thoughts on developers today? You actually made the comment coming over, there's two big developer shows this week. You've got F8 and you've got DockerCon, two very different communities. >> Right, it's kind of funny. There's always this sense of, do you consider yourself a developer? So if I write a line of JavaScript, am I a developer? My two cents is yes. If I'm a developer, from JavaScript to Swift to Docker to cURL hacking, it's all great. But if you look at those two conferences, you have F8 going on right now, and the announcements there around augmented reality and messaging, and it's trying to be a platform, but they're doing many of the same things. You have a distribution platform be it Messenger or Facebook, and they're open sourcing technologies around the camera, the lens, the filters, to have developers a) go through the channel, b) add apps or widgets. It's really beyond my ability to comprehend these filters, but Docker today announced a couple great projects: Moby and Linux Kit, much the same way as trying to give tools to the ecosystem developers to build what they want. I think what you've learned is, if you give developers the building blocks, the "Legos" as they call it today, they're going to build some awesome structures. >> Jim was, we talked about coming in here as the role of how data science fits into the developers, and developer is such a broad term, as to what we have here. >> One of the core themes I have is that the data scientist is the nucleus of next generation developer because much of the IP that's being built in the applications now, is statistical models and machine learning and so forth, driving recommendation, but much of that development is being containerized using new tool kits and so forth. But it needs to be more containerized so you can deploy statistical predictive models, machine learning, deep porting to routing the string ecosystem into a hybrid cloud to perform various functions. >> Right now there's, in most companies, there's a data engineer, there's a data scientist, and the two typically work hand in hand. >> Jim: One manages Hadoop, the other one does the modeling. >> Does the modeling, so one speaks in R and Python and works in Jupyter Notebook, the other person runs on Hadoop or database or Redis. The two need to work together and so what you're seeing now and obviously we're investors of Cloudera, that's another great open source company, what you see now is either a) a set of tools and technologies to either blend the two together in some cases, either enable engineers to be more data scientists, or enable data scientists to be more engineers, but also see a bunch of technology tools that say, no, two different roles, I'm going to create tools purpose-built for the data scientists, create tools purpose-built for the power of a data engineer. And I think there's space for both to the extent that you have applications running from news feed or ads to predicting how my self-driving car should make a left turn, you're going to need tools that are used by both types of populations. >> I think Cloudera now has a collaboration environment in the data science department. IBM has something very similar with what they're doing, so it's a team that has specialties such as coders, such as data modelers and data engineers. Point well taken. Cloudera's made a major entrance into that space of collaborative development, of these rich stacks of IP, essentially, that include deterministic program code, but also probabilistic models in a deepening stack. >> I think you've seen Cloudera definitely follow that path from Hadoop and low-level file system HDFS, to these high-level tools for data scientists that's becoming a platform for machine learning for these next generation applications. I think you see Docker in the infrastructure analogy doing low-level tools like Project Moby and Linux Kit, to high-level services around Docker Datacenter. So you can either have the basic tools for your low-level developer, or for the system admin or administrator who wants to operate or run the cloud, you have tools for him or her, too. >> It's interesting, you look at some of these projects and some of the maturation and pivots you see. We talked about dotCloud went over to Docker. You see a bunch of open stock companies that are now Kubernetes companies. I see companies that were big data, they're now, "Oh, I'm an AI or ML company." It's always like, it's usually not the tool, it's the wave. What is the driver? Is data the driver of our next wave there? Is it the application? Is it some combination of the two? Those are the two that I usually look at. Follow the data, follow the application. >> I would say it's data driving. It's really data application, it's data, and the applications make use of the data. Algorithms, I think, is a component. They're important, but they're a component. So what you see now is, to be on the right side of history, data is outstripping compute and storage, so the amount of videos and center data that we're generating from our phones, our cars, our homes, that is outstripping most of the other charts in compute, networking, whatever. That's definitely kind of a rising tide or a wave, as Stu was saying. Now how do we extract data, or value from this data? And historically, because you didn't have infrastructure, that cloud, or compute capacity to make use of this data, it was kind of stranded, so what you've seen in generation technologies like Hadoop or big data or cloud technologies like Docker did, is distribute your applications across a cloud. That's actually enabling you to now build applications to get value out of this data. And that value can be something like forecasting your sales this quarter. It can be about figuring which shade of brown belt you should wear with your pants, going back to our clothing analogy. Or it could be like, let me build a model around how this car or this drone should drive or fly itself. So you combine the vast amount of data, nearly infinite resource of compute, with these machine-learning or AI techniques. Machine learning is one AI technique, but all these other techniques, you can build another generation application, this new intelligent application to power everything from your home, your car, your watch, or your enterprise app, as wonderful as that is. >> Much of the sea change is less and less coding or programming is actually being done or needs to be done because more of the application logic is being distilled directly from the data in the form of machine learning. There's automated machine learning tools that are coming. Google has been a major investor as is Facebook in automated machine learning. >> I would say application logic from the inside, right. So in my mind, application logic, an application is reflecting business process. Hire to fire, order to cash. You still need a program that does logic. Data in itself, or AI in itself without that context, without that business process, is meaningless, right. Just having a model around Jim or Stu, it doesn't matter unless you're trying to buy something. Google pioneered machine learning in a workflow perfectly. You're searching for something, they knew who you were based upon history, you're searching the right ad and say, "Oh, you really want to buy a car, you want to buy a house." So in the workflow, or in the application logic of a search, they used ML to serve you timely information. Now if you're an enterprise, you're looking at help desk tickets, be it ITSM like ServiceNow, or support tickets like Zendesk supporting B to C support tickets. That's a workflow, there's application logic. They take information on a user or a grumpy customer, and they do things like automatically respond to a help ticket, reset your password, provision a server. So I think when you have AI or have applications using this data in the context of a business process, that's magic. And I think we're seeing some core technologies like TensorFlow out there that are super compelling. But we're seeing a generation of developers and founders take that technology, apply it to a problem, it could be HR or CRM, ITSM, or true vertical. Construction, finance, health care. >> Jim: Streaming media analytics is a core area where that's coming in. >> Media analytics because there's a ton of data. Understand what you watch and what you want to see, and so you apply things to a vertical, like health care, or apply the technology to a problem space like media analytics, and you have a wonderful application and hopefully a great company. >> Jerry, we've talked a lot at the cloud shows about how do the startups maintain relevant and get involved when there's all of these platforms. We talked about what Google does, Amazon of course is eating the entire world in everything. Microsoft is making lot of moves here. How do companies, what do you look for? Has your investment strategy changed at all in the last couple of years? >> It is daunting. I think about this a lot in terms of business models and defensibility, and the question goes, what are the sustainable moats you can build around your business as a startup anymore? 'Cause you feel like economies of scale and ecosystems, network effects, those were historically big defensive moats for a Windows operating system. Now those apply to Facebook's platform, Apple's platform, or AWS. They have scale and they have network effects for the ecosystem, so now your startup is saying, okay, how can I either a) overcome those moats, or b) how can I develop my own IP or my own moats around myself that I can actually sustain and thrive in this generation. I think you got to play a different game. As a startup, you're not going to try to out-scale Google or Microsoft; leave that to Amazon and those three or four players. But you can get scale in a domain, so either a problem space like autonomous vehicles, security is a great one, or vertical construction or health care. You redefine the market that you can dominate, can you build your own moat around that IP. >> It's interesting. did you hear Adrian Cockcroft who went from Battery Ventures over to AWS. He's like, "Well, rather than go startup that business, "come build that next thing at Amazon "and we'll do it there." Is that a viable way for people with the entrepreneurial spirit to go be part of that two-pizza team doing something cool inside a large platform? >> I think Adrian probably has motivation and more developers on Amazon now, but I would say most of our companies, not all, but a lot of them started at Amazon. Some start in ads, some start in Google, some start with their own data centers. I think what they believe is they'll get started in one of these clouds but I don't believe, so we talked about this first, it's not a one-cloud-rules-all world. I think there'll be three or four, if not more, clouds in every different geography from Europe to Asia to Russia to the US, will have different clouds, different players. So I think it's fine to get started in Amazon and be a two-pizza team with the other two-pizza team, but over time I see these applications being cross-cloud, and that's where something like Docker comes into play. Docker wants to be cross-cloud, better than any other technology out there. >> On some level, actually, the moat could be, or increasingly is, the training data that drives the refinement of your AI, like Tesla is a perfect example. The self-driving capabilities that they built into the vehicle, they have now a few years' worth of rich test data, training data I should say, that is a core moat in terms of continuing refinement of those algorithms. So that gives you sort of an example of some startup might come along with some very specialized application that takes the consumer world by storm and then they build up some deep well of training data in some very specialized area that becomes their core asset that their next competitor down the pipe doesn't have. >> It has to be a set of data that's unique or proprietary. You're not going to basically out-train your model on cat photos from Google, right? So it has to be a combination of either proprietary data or a combination of data sources that you can stick together. So it's not just one data source, I believe you have to combine multiple data sources together. >> So Jerry, sitting over Jim's shoulder is VMware's booth. I haven't talked about VMware at all this week. You worked at VMware, I've worked with VMware since pretty early days. What advice would you give VMware in the containerized cloud future? How should they be doing more to be part of more conversations? >> I think it's amazing that they have a presence here in the size and scale. The past couple years they're really done a lot to embrace containers and Docker, so I think that's first and foremost. They've done a couple great moves lately. Embracing Amazon last year, with VMware on Amazon, was a big move. Embracing containers with some of their cloud and data technologies I think was an aggressive move too. So I think they're moving in the right direction. I think what they need to understand is, are they going to revolutionize themselves and push these new technologies aggressively, or are they going to keep hanging onto some of their old businesses? For any company of their size and scale, they have multiple motivations, but I think they're making the right steps. So five years ago, or four years ago, I don't think they would have taken this DockerCon seriously. I don't think they were exhibitors at the first DockerCon. But in the past 24 months they've done some amazing moves, so I would say it makes me smile to see them take these great steps forward. >> Jerry, I want to give you the last word. Any cool companies we should be looking at, or things that are exciting to you without giving away trade secrets? >> I can't broadcast the companies I want because everyone else is going to chase those investments. I don't know, I think I'm going to enjoy spending time, actually less with the companies here but a lot with the developers and customers, because I think by the time they have a booth here, everybody knows the company's investment is probably too far along maybe for me to invest, maybe not. But talking to developers to hear what are their friction points? I think when you hear enough friction either in this ecosystem or another ecosystem or at AWS or VWware, then there's something there, you just got to scratch. >> I was talking to some of the people working the booths and they just said the quality of the attendees here, you learn something with every single person you talk to, and there's only a few shows that say that. Amazon reinvented one, the quality of the attendees always real good, this one and a few others. >> I think people who come here by definition are learners, both the companies and the individuals, and you want to surround yourself with learners, people who are open and honest and always learning. >> Jerry, I think that's a perfect note to end it on. We are always learners here and helping to help our audience in trying to understand these technologies, so Jerry Chen, always a pleasure. And we'll be back with the wrap-up here of day one DockerCon 2017. You're watching theCUBE. (techno music)

>> Voiceover: Live from Austen, Texas, it's theCUBE. Covering DockerCon 2017, brought to you by Docker, in support from its ecosystem partners. >> And we're back. Hi I'm Stu Miniman joined by Jim Kobielus and this is theCUBE, worldwide leader in live enterprise tech coverage. Happy to have on the program, Scott McCarty, who is technical product marketing for containers with Red Hat, thanks so much for joining us! >> Thanks for having me. >> Alright so, obviously this is the big container show, You know, Red Hat, I saw when you talk about the number of contributors, you're one of the top contributors there, but first tell us a little bit about your role at Red Hat, how long you've been there, some of your passions, what do you work on? >> Yeah for sure. So I've been at Red Hat six years and I started actually as a solutions architect, six-ish years ago, came from a startup before that, and so been in the operations space for a long time, did a lot of programming, background in anthropology computer science. Yeah. >> You're dating yourself, you call it programming >> I know, I know! >> Because it's coding now! >> I know, I know! (laughs) >> I'm like, yeah, I used to program but, uh, what's this, this coding stuff. >> I am dating myself! >> Did you say anthropology? >> I did. >> Well we've got to connect it with Red Hat at some point in our interview now. >> It matters in the culture of things. >> James: Okay, yeah. >> You know, culture is important. (laughing) So did you know, a very wide swath of our portfolio I understand from being a solutions architect and then about two years ago moved into, well when Docker first started off, you know, got into containers and got pretty heavy and that, and was excited about it, and then moved into just doing strictly technical product marketing for only containers. You know, for focusing on containers. >> Okay, so talk to us about how containers fits into the Red Hat portfolio. >> So containers is really something that touches every part of our portfolio, because whether at the lower levels of like the Linux layers you know that's the actual nuts and bolts of, you know, what builds the containers and what the containers really are. But then at the other end of the stack, if you look at our storage and our middleware, containerizing those applications and then figuring out how to package them in a cloud-native way and making them work in a cloud-native way, so that they can operate inside of something like OpenShift, there's a lot of work to be done there. So there's a wide swath of tech across our entire portfolio of work around containers going on. >> Yeah, in the keynote this morning I like there's the maturation of the use cases because it sounds a lot like, you know, remember of the early days of Linux, or the early days of virtualization, once again they've put together a load of use cases and are like, "Oh, we're running applications," >> Scott: Yes. >> In a wide variety of applications in containers, so what are your customers seeing, you know, any kind of cool use cases or things that people are doing and anything new that they're doing that they couldn't do before? >> Well, so, I'll give you a little take on that, so even for the last two years that I've been going out all over the world to talk to customers, I've noticed that there's a little bit of a disconnect between the industry and kind of only focusing on the app dev side of things. I think today, kind of hearing Soloman talk about some of the more traditional use cases, traditional or non-cloud native or, we don't like to say the word legacy but people say it. >> Stu: Kind of wrapping-- >> I would argue those have been a huge portion of what people are experimenting with and playing with, but we don't talk about them. Also I think there's a little bit of a notion of this mode one, mode two kind of mentality, but that limits the way we think about it into only production workloads. So I have some really funny use cases. So I'll give you some examples, network scanning. So, like, there are some vendors that provide network scanning software and I was a couple of months back up in Canada talking to ATTO Co., and they mentioned they they were actually putting a commercial network scanning package in containers because when you think about, you see a production oracle database and, you know, you talk to the oracle DBA, and you say, "Hey I'm going to install "this giant network scanning package on your server." And they're like, "No. You're not doing that." (laughing) So a container makes it very easy to just bring that application down, do this network scanning, troubleshoot something and then delete it, it's gone. That's just a tools use case, right? But it's something that people have been doing for a long time but nobody is really talking about it. Another one is even affecting business more transformationally. So if you think about the way startups hire people, this happened to a friend of mine that's a CTO at a startup. They're interviewing a developer, it's very common to send them home with a homework program, you know? And so they send them home with the Ruby on Rails program, and he comes back with a GitHub Repo that has like a database schema file for Postgres and a working Ruby on Rails application. And there are two hiring managers. The one hiring manager says, "Okay I'm going to," And I'm sorry, also he says, "By the way, I have a Docker Repo, "you can go out and pull it down if you want, "just run my program and see if it works." The one hiring manager decides to try to rebuild it from scratch, takes about two hours messing around trying to get the database schema to work because he used the newer version of Postgres than she had on her laptop, you can imagine the dependency, you know, chaos that is. The other hiring manager literally just said, "Okay, just Docker run this thing." And then, kind of ran the container and looked at the code. The one spent two hours, you know, getting it up on her own, the other one spent five minutes. And so now if I can give you back the most valuable people in your organization, these very, very technical architects that are doing hiring decisions and trying to evaluate really critical core developers for your startup, if I can give you back two hours, and if you have to interview 10 of those, that's 20 hours of your time, that's transformational, that's really digital transformation, essentially, but for a startup, you know. Like, we don't want to have to spend all this analog time doing that. In addition to the traditional applications like databases and even, you know, typical web servers, all of those things, but not just mode two or cloud native, but also just traditional workloads. And we've been seeing that for a long time, I mean, this is similar to the virtualization journey, it's like you said, everyone said it was impossible and even two years ago was saying, "Wait a minute, just wait for this, it'll happen," and we're seeing it happen. >> Yeah. Anything particular? You know, we've made a lot of progress, but we're still working on storage, networking seems to be a little bit more mature than storage you know, what are you guys helping to work on at Red Hat and what do you want to see going forward that we come here a year from now we're going to say, "Oh, cool, we knocked down this barrier, or we're doing something even better." >> So one of the things I'm excited about is kind of if you look at the integration points between cloud infrastructure software like OpenStack and even the cloud providers, and then something like our OpenShift solution or Kubernetes, if you look at the storage and the network interactions, today the networking is pretty mature but the interaction is pretty static, so if you provision OpenStack, you know, say you have an OpenStack environment, you want to run OpenShift on top of it, you would go pre-provision kind of a VLAN, you know a subnet for it, and then you would- we rebuild, actually, key templates to deploy OpenShift inside of it, within that subnet. In the future we're investing in Courier and you know, a year from now I'd like to see some really dynamic interactions happening between OpenShift and OpenStack. I'd like to see an administer say, "Oh, I need to provision a new project "and that project needs its own network isolation." When that happens, OpenShift goes and talks to OpenStack, provisions a subnet that's encrypted with OVS, and actually it already is kind of set up, comes back, says, "Okay cool," and then can provision a project inside that. On the storage side we've actually already got that going, So we have what's called dynamic provisioning, so if you need storage inside of OpenShift and you have a persistent volume claim that needs access to storage, we actually have something called a dynamic provisionary that will actually go create that person's environment and go to talk the the storage and carve off a LUN of exactly the size you want or a NFS share of the exact size that you want. So, so, I'd like to see more and more of that dynamic provisioning happening between the infrastructure in a container environment. >> Is that as capable, uh, should we build into Kubernetes or totally independent of that? You know what I mean-- >> So the current project is kind of neutral but it would be, kind of, think of it as almost like an interface that Kubernetes will be able to use as an interface to all the networking providers. >> James: Right. >> So it's kind of a neutral, third-party thing. Really it could be used by other things other than Kubernetes. >> I want to get your take on project Moby, that was a real interesting announcement today, to what extent, would Red Hat consider possibly using that as a tool to build custom container applications for your own product family? >> Probably the most interesting thing I found about the announcement was kind of a validation of, uh, you know already a kind of strategy that we had around Project Atomic. And if you look at Origin and Project Atomic and Fedora, you know, they mention Fedora, that model. >> James: Yeah, absolutely. >> I think it's a good model, and you'll appreciate that we appreciate it. I think that, you know, there's some validation also around the idea of an immutable host, and having control over the host and honestly I think it kind of validates that the Linux itself is not a commodity, there is something actually very technical there and you do need to actually build a dry features in that kernel to actually support the containers, because I think they made the kernel hot again, you know, in a lot of ways. So I think it's validation of that and I think that's exciting. >> At the beginning we talked about culture a little bit, you know, we've interview Jim Whitehurst, so you know, I've read his book, >> Scott: Yeah. >> You know, the open organization, >> James: The anthropology. (laughs) >> You know, when you come to a show like this where, I mean, today we talked about the developer, we talked lots about open-source and, right, you know there's Linux Kit, there's the Moby Project, you know, all these different things out in open-source, what's your take on this ecosystem and what's going on in the industry? >> I think ecosystems are harder to build than what people first think. I don't think you can just, so if you look at certain, you know if I were to analyze the way open source works, you know there sot of open-core models which are like, "Let's give enough away to get free marketing." Then there's kind of open-source models where we give away all the code but we don't really have a community, we don't really take patches, we just put it out there, use it however you want, that's fine. And then I think there's truly community-driven open-source which is what Red Hat really tries to focus on. So if you're able to get Fedora, it's truly a community. I think building those and maintaining those takes a lot of nurturing and a lot of care and a lot of love and feeding. And I also think it takes a lot of discipline around allowing these best-of-breed ideas to kind of happen the way they're going to happen and then also fail if they don't work. And so that can be tough, you know. If you look at the model of a lot of startups, it's more kind of like unilaterally make decisions and then kind of release it and then if it sticks, and it's fail-fast. The community-driven model is a lot harder to handle because consensus is harder to build and so you've seen Jim talk about this, I mean one of the dangers in an open organization of our size is consensus, finding consensus and not going towards a completely consensus-driven decision model. But that's hard because you have to satisfy everybody in the community and make sure everybody's getting something out and everybody's putting something in. And so it's tough. >> It's funny, I remember in OpenStack for a couple of years, it's like, "Do we need, you know, the fanatical dictator "of this ecosystem?" Red Hat, obviously is not, you know, a fanatical dictator of its community. >> You can't win. Do you think Docker has a fanatical dictator of their community? (laughter) >> I, I, I'm sure the-- >> Or is the person a visionary, I mean, you know they'll put the positive euphemism on it. >> Yeah, yeah. Or the joking word in the community is the benevolent dictator. >> Yeah. >> The benevolent dictator for life, I think some of the communities work that way. >> Yeah. >> I think if you look at Python, you look at Linux, you know, it works that way. But if you've all got bigger projects, and I don't want to date myself, but you think about KDE and Gnome, and some of those, there's no benevolent dictator, they're so big and so wide-reaching again. Such, you know, wide-use case differences between what people do with them, but I think it's hard to have that. There are visionaries, you know, within the group. And even that's true in the kernel, I mean if you look at what's happened, you know, Linus has other generals essentially that kind of, I mean it's become a very big community, a very boisterous community. I think that that takes again, though, a lot of discipline and maintenance to make that happen and keep that alive. >> Alright, Scott, to take us on home, why don't you give us a little view as to what Red Hat has going on this week, of course you guys have your big show Red Hat Summit coming up in a couple of weeks, we'll have theCUBE there, I'm excited to be there, also, but you know, talk a little bit about this week and what you guys are doing. >> So this week, you know, we're excited because we have kind of a bunch of three-five You know, I don't know if you guys, have you guys heard about Atomic Image? We released Atomic Image? >> So it was not discussed in Brian's interview this morning, so. >> Okay! >> We would love to hear a little bit about it. >> So Atomic Image, we've kind of looked at some of the use cases around how people are consuming containers and I've blogged on about this and talked and honestly it's pretty deep technically when you kind of get into it. It's about having, you know, Soloman talked about it today, you know, image size matters, and there is definitely a hunger for smaller images, you don't want to have stuff that you don't want. But that is also a very fine-line balance. So the challenge being that the typical way that enterprises operate is that they have a core build where they will add all the pieces that core build that they think should be everywhere, right? Because you don't, like, say you need a fundamental core library like glibc, you wouldn't add that to all of the different applications, you would add it once and then inherit it in all the, so it's kind of the dry model, do not repeat yourself, right? So when you get into this dry model you got to balance the size of that base image versus, you know and it's flexibility versus conciseness, and you know, how concise it is. Atomic Image, though, is meant for, we essentially released a very minimal image that matters for those very concise applications, so if you look at like a C binary that's very small, maybe all it needs is DNS resolutions, some other services from the OS from the userspace, it doesn't need much, but it's a real small binary, it wants a really small image to live on. So we released something called Atomic Image really targeting those use cases-- >> I don't know if I remember if Atomic is launched, so it sounds a lot like what Docker announced with the Linux Kit today, too. >> So, it's, flip-side of it-- >> Maybe you could compare contrast a little bit. >> Yeah so, so I would compare Linux Kit to Atomic Coast, which we've had for a long time. >> Stu: Okay. >> Which is the Kernel and systemd and kind of what runs the containers, right? But now we've released a different userspace setup that's smaller-- >> Stu: Oh I got that, okay. >> For, to run on top of, you know. >> So like an agile minimum viable product, this is a minimum viable container >> Yes. >> For a particular function. >> Yeah exactly, like BusyBox or some of the smaller images that you want to play with. >> And Scott, do you guys have their website or some documentation that you recommend people starting with on your sites? Yeah absolutely, I swear, I think Project Atomic's a great place to start. >> Stu: And that's in the blogs, I'm assuming, right? >> It is, if you blog for Atomic Image, too, you'll find a REL Blog entry, so REL Blog's a good place to kind of find some of that stuff, so relblog.redhat.com And then also if, if you look on just redhat.com. And also out container catalog is a good place to actually go get started with that. So if you go to access.redhat.com/containers. >> James: We'll get to that. >> Scott McCardy, it's great catching up with you. Next time we have you on we got to get the story behind "fatherlinux" as your-- >> Yes! (laughs) >> Alright, but we'll be back with more coverage here from DockerCon 2017, thank you for watching theCUBE.

>> Narrator: Live from Austin, Texas, it's The Cube covering DockerCon 2017 brought to you by Docker and support from its ecosystem partners. (upbeat tech music) >> Hi, I'm Stu Miniman and this is SiliconANGLE Media's The Cube. We're the worldwide leader in enterprise tech coverage. Happy to be coming to you from DockerCon 2017 here in the Austin Convention Center of course in Austin, Texas. My host for the next few days will be Jim Kobielus, Jim thank you so much for joining us. >> It's great to join the team. >> Alright, so we'll get to you in a second, Jim, but first of all, it is the fourth year of the DockerCon show Docker The Company, just celebrated its fourth year of existence, CEO Ben Golub started off the keynote Founder, CTO, Chief Product Guy, Solomon Heights, introduced a bunch of opensource initiatives, did a bunch of demos, the first DockerCon event back in 2014, I actually had the pleasure of attending, was my favorite show of that year, I got to hear some of these HyperScale guys talk about how they were using containers, how Google spins up and spins down two billion containers in a week and there were about 400 people there and Docker, the company, was 42 people. Fast forward to where we are today in 2017, Docker, the company, I believe is 320 people, there is over 5,500 people here, you can see 'em all streaming in behind me here as the Keynote just let out, so, we've got two full days here of coverage. This morning, we're going to go through a little bit of the news, talk about who we're going to cover, but first of all, I want to introduce you to Jim Kobielus, so John Furrier sends his regards to the community, he's real sorry he couldn't make it out, just had some things came up at the last minute, so he couldn't come, but stepping in for him with lots of knowledge and experience is Jim, so Jim, please, for our audience that hasn't gotten chance to see, you did some intro videos with our crew out in our 4,500 square foot Palo Alto studio at the beginning of the month, but why don't you tell 'em what brought you to the SiliconANGLE Media team, your background, and what you're going to be doing. >> Great, yeah, thanks Stu. Yeah, I've joined just recently in the last few weeks, I am Wikibon's lead analyst for application development as well as data science and deep learning. I create data science and the development of artificial intelligence as a huge and really one of the predominant developer themes now in the business world and really much of that that's going on in business in terms of development of the AI applications is in the form of microservices in containerized format for deployment out to multiclouds and increasingly serverless computing environments. So, I am totally pumped and excited to be at DockerCon and there were some great announcements this morning, I was very impressed that this community is making great progress, both on the sheer complexity and sophistication of the ecosystem, but on just the amount of support for Docker technology, for Kubernetes and so forth for the full range of technologies that enable containerized application development. Hot stuff. >> Yeah, Jim, and you talked about things like community and ecosystem and that was definitely the theme here day one. Docker did some changing in their packaging since we were at the show last year. They now have Docker CE which is the community edition. Focus on the developers and today was developer day. I'm pretty sure everything that was announced today is opensourced, it's in there, it's in the free version. I expect tomorrow we'll probably hear more about EE, it's the Enterprise Edition >> Enterprise, yes. >> A question I know we all have is how is the monetization of what Docker's doing progressing, the press and analyst dinner last night, I heard from a Docker employee and said look, we all understand, we are the early days of the monetization of Docker, but Solomon, this morning, said really, the success of Docker the company is tied directly to the ecosystem. We've got Microsoft coming on today, we've got Sysco, Oracle, lots of partners coming on this week talk about what Docker's doing, what's happened in opensource is going to help a broad ecosystem and all, not just the developers, but enterprises and the companies, so, what are you looking at this week, what are you hoping to come out of, what grabbed you from the Keynotes this morning? >> Well, grabbing from the Keynotes this morning is the maturation of the containerized Docker ecosystem in the form of greater portability, in terms of the LinuxKit announcement, we'll get to that later, as well as great customization capabilities to the Moby project. This is just milestones in the development and maturation of a truly robust ecosystem of innovation, really, what Docker's all about now that it's a real platforms company, is helping its partners to be raving successes in this rapidly expanding marketplace, so, that's what I see, the chief themes so far of this today. >> Yeah and it's interesting, one of the things we've always looked at Docker is like what does the opensource community do, what does the company do, what's the co-opetition play? Two years ago at the show in San Francisco, there was taking the container run time and really making sure that's opensource. You had the CoreOS guys and the Docker guys hugging. I got a picture of Ben Golub and Alex Polvi standing together and it was like oh, okay, that little cold war was over. LinuxKit is something we're going to look at, they lined up some really good partners. We got Intel, Microsoft, HPE, and IBM, but, we're going to talk to Red Hat and Canonical and see what they think about this because from the Linux guys, I've been hearing for the last couple of years, well, Linux really is containers. It's all just something that sits on top and containers, of course, is the Windows variant now, too, but you just buy your Linux and Containers comes with it and now, we say oh, we've got LinuxKit which is, I'm going to have a distribution that's fast, optimized, four containers that Docker and that ecosystem they're building's going to do. >> Same as everywhere, I mean Ben Golub laid it out maybe with Solomon this morning. Containers are really the predominant packaging of applications large and small across increasingly not just traditional enterprise and consumer applications but also the internet of things, so, but internet of things and the development of AI for the IOT is a huge theme that I'm focusing on in my coverage for Wikibon. I see a fair amount of enablers for that here. >> Great, and Jim, and absolutely, there was a big slide with Docker will be where you need to be, so, whether you're in the public cloud, of course, there's container services from, we've got Amazon ECS right here. You've got what's going on with Google and their containers. Microsoft Badger of course, so, there's so many pieces, so, a lot we're going to go through, we've got a full slate of interviews, of course, everybody can watch here at SiliconANGLE TV. If you want to participate in social conversation, John Furrier's actually been banging away, it's CrowdChat.net/DockerCon is where we're having some of the social conversations, of course, you can always reach out, I'm just @Stu on Twitter, Jim is @JamesKobielus which you'll see on the lower third when we put him up here is where he is on Twitter, if you're at the Expo Hall, you'll see the Expo Hall's behind us, we're just in the corner of the Expo Hall, going to be here for two days. Jim, I want to give you the final word on our intro here, come to the end of the day, what do you hope to have walked away with? >> Well, I hope to walk away with a more rich and nuance understanding of this ecosystem and the differentiators among the dozen upon dozens of companies here. Partners of Docker. Really what I see is a huge growth of the Kubernetes segment in terms of orchestration, scaling, of cluster management for all things to do with, not just Docker, but really Container D, which, of course, Docker recently opensourced, it's core container engine. I think this is totally exciting to see just the vast range of specialty vendors in the area providing tools to help you harden your containerized microservices environment for your CloudNative computing environments, that's what I hope to take away. I'm going to walk these halls when I'm not physically on The Cube and talk to these vendors here, exciting stuff, innovation. >> Yeah, absolutely, and you gave us so many pieces there, Jim. You mentioned Kubernetes, of course. There is that little bit of do I use Dockers Forum or do I use Kubernetes? Docker, of course, would like you to use Forum, that's what they're >> And in fact, that was an excellent discussion this morning about swarms advantages as well. I don't want to make it sound like I'm totally shifting towards Kubernetes in terms of my preferences. I mean, clearly, it's a highly innovative and dynamic space, so, Docker is making some serious investments and beefing up their entire enterprise stack including Swarm. >> Where I wanted to go, actually, with that is the Moby project actually is one of those things I saw as a nice maturation of what we hear from Docker. For the first couple of years, Docker said batteries are included but swapable, which means things like Swarm are going to make it in there, but you could use an alternative, so you want to use Kubernetes, go ahead and that's fine and Moby has allowed them to take all the components that are opensource. People inside Docker can work on them, people outside can collaborate them, much more modular. Reminds me of how when we talk about how development teams work, it's those two pizza teams, Docker has them internal, they're pulling more people in, how is that opensource collaboration going to expand? Scalability, I think, is the word that I heard over and over again in the Keynote. Scaling of the company, scaling of the products, scaling of the ecosystem, so something more interesting, say, we've been scaling our operations and we got two full days here of coverage so make sure to stay with The Cube for everything we've got here and thank you for watching The Cube. (upbeat tech music)

>> Announcer: Live from Austin, Texas. It's theCUBE. Covering DockerCon 2017. Brought to you by Docker, and support from its ecosystem partners. (bright electronic music) >> Welcome to SiliconANGLE Media's coverage of DockerCon 2017. This is theCUBE. I'm Stu Miniman. My cohost for the next two days is Jim Kobielus, and happy to have as our first guest on the program, is Brian Gracely. A year ago, actually, Brian had a beard, and he was one of the hosts on theCUBE. He's now with Red Hat. Brian, welcome back to the program. >> Stu, great to be on this side of the table again. Good to see you guys. >> And Brian, you were at the first CUBE event back in 2010. We've had you on at least once or twice every year. You did a few more when you were on our team, but happy to have you back as a guest. Why don't you bring our audience up to speed? What brought you to Red Hat and what's your role there, and what brings you to DockerCon? >> Yeah, so, been at Red Hat about a year, a little less than a year now, worked on the OpenShift team, so focused on Kubernetes containers, integrated Linux. It was a great opportunity to be in open source, which I've been working on for a year. It was at home, it was in Raleigh, and it's a great team. It's a team that's growing. The Kubernetes space is growing, so, the vendor side of the world drew me back into Red Hat, so it's been good. >> Yeah, open source, big component about what we're talking here at this show. I heard open source mentioned a ton. It was developers, it was contributors. What's your take, did you get a chance to see some of the keynote? Solomon got out there, thanked the 3300-plus contributor. When he put up the name of the companies, I think it was 41% of the contributors for all of this are independent, but then, Red Hat's in the top six companies there. What's your take on that and the ecosystem in general? >> Yeah, I thought it was, I thought the keynote was good. Obviously, the show's doing well, so it's great to see the container space doing really well. We've been part of the Docker ecosystem since sort of day one. We like to say that we're probably the biggest distributor of what used to be Docker is now Moby, within Rail. But yeah, I think we see that, we obviously believe in the open source movement. We're seeing more and more customers, our customers who want to contribute, who want to make it the de facto buying decision as to what they use, so, yeah, it's great to see not only huge open source support, but then seeing it become, to blossom into very viable, commercial offerings around the market. >> Yeah, so, Brian, your team actually wrote a blog leading up to the show that says, "Containers or Linux." After listening to the keynote, with LinuxKit announced, it felt like, oh well, Linux is containers. It seems like, reminds me back, Sun is, the network is the computer, the computer is the network. It's all kind of looking at it. What's your take as to kind of the relationship of containers with Linux, of course Windows fits in the mix, too, but the operating system and the containers. >> Well, I think, the reason we really put that out was if you go back a little bit historically, not to bore people, containers aren't a Docker thing. Containers are a Linux thing. They were created by Google, Red Hat made a huge contribution sort of secondarily around namespaces, Google did cgroups, IBM did LXC, so it's been a core Linux feature for over a decade now. Docker did a great job of making it easier to use, but at the end of the day, even if you look at, like, what LinuxKit and some of these other things are, they're not about sort of Linux versus Windows, it's, they are all Linux, and it's how do I represent Linux in ways of doing that? So we really kind of want to just reinforce this idea that there are things that you expect out of your operating system, containers being one of them, but if you look at every other project that's being built around this space, whether it's Kubernetes, whether it's management tools that are be, they're all being built on Linux. That's the foundation of this, and it's kind of just a reinforcement to people that, remember where your tools come from, what that thing is that drives security for you, things in that space. >> Brian, you wrote a lot about kind of cloud-native and that journey kind of, rewriting applications, containers, for the fits into that a lot. What have you seen changing kind of last 12 to 18 months? Couple of shows I've been to lately, it feels like we're talking about lift-and-shift more than we are about building new applications. What's the application space look like, and I know Jim's going to want to jump in here. He covers the cloud-native stuff. >> So I think there's a couple of big things that, and I wrote about it for a while, and it's, how much has changed in the last two years have been really interesting. So, I think originally, when you went and looked at platforms, whether it was OpenShift or Cloud Foundry or Heroku or whatever, lots of sort of what we used to call opinionated systems. You dictated what developers did, right? And then, we had-- >> Jim: Opinionated systems? >> Very opinionated platforms, right? The opinion of us, the creators, was going to get forced on you, the developer, right? >> Stu: It made a lot of the decisions for you, so. (Jim laughs) >> And again, the idea was make it easier for you. You don't have to think about those things, but you're going to get them in the way that we want them, and what ended up happening was Docker would kind of became a standard way, a standard container format. We ended up having these open source schedulers like Mesos and Kubernetes and other things, and that allowed the platforms to be a little more, what I was calling composable, so, because developers may not want to use the languages that you force on them, they may not want to use them in those ways. So I think what we've seen is this sort of blurring between what used to be heavily opinionated to becoming more composable, modular, and there's always this trade-off between how much do developers want to care, how much do they not? So that's one big trend that we've seen, is this start of back and forth of what that is. The other one we saw was-- >> In terms of compatibility, (mumbles) quickly, do you see any trend in this space, containers, toward visual composition of applications? What I'm seeing in today, and I've seen generally in this space, is mostly coding, command line interfaces, any visual composition tools you guys provide or any partners of yours for-- >> Brian: Yeah, there's-- >> For building containerized applications? >> And so I think there's sort of two pieces there. It's a great question because ultimately, if the coding piece is hard, you only reach a small segment of those developers, right? You want to, it's like when websites came out, they were all hand-coded in HTML and stuff, and then you had things like Dreamweaver and these other visual tools, and then it exploded. We've seen that. To be successful in this, you've got to have tools in the desktop that make it easier for the developers. Red Hat does something that we call the Container Developer Kit, which is really, write your application, a lot of the stuff in the background gets hidden. Docker has Docker for Mac and Docker for Windows. We see some other tools. So that piece is important. The other piece that, to come back to your question about it, is it lift-and-shift? We probably see 75, 80% of the customers we work with who say, "Look, I know I've got to do cloud-native. "I've got digital transformation "and all these sort of things, "but I've got a lot of portfolio "that I'd like to modernize. "Can I do that with containers?" And I think what we've seen is, for the early days, it was containers are only for new. They only work for microservices, they're only for new, and what we're seeing, and this again goes back to the sort of, containers are Linux, is customers say, "I have an application that ran perfectly fine in Linux. "Why wouldn't it run really well in there?" And we've got customers nowadays, and this sort of blows people's minds, like, we've got customers who will pick up things like WebSphere, put them into a container, run them, modernize them somewhat, but, because the platform will give them automation, it gives them high availability, it gives them scalability, and they go, it works, and they get cost-effectiveness. So we're seeing a lot of that because you can address a lot of your portfolio. >> Oh, Brian, it's the typical maturation that we've seen. The use cases that put on stage, keep planes in the air, power the largest infrastructure, monitor fire alarms, websites, it's like, oh, this is same thing we saw in virtualization in every kind of way that's like, oh, containers run applications. (chuckles) >> Right. >> Right? >> Jim: Have you seen a big push by your customers or in the ecosystem to containerize more of the deep learning and artificial intelligence toolkits, like TensorFlow or Theano? Is that, with your customers, is that a big priority rate now or going forward? >> Yeah, so, I think the big data space was always an area that was kind of on the fence if it made sense to, in container, do you need an abstraction layer, do you want to be closer to it? We're starting to see more and more, so for example, Google with TensorFlow. Google, huge proponent of containers and Kubernetes. They're doing a lot of work to make that happen. We've been doing a lot of work with the Spark community to make Spark work really well in containers, and it becomes an issue of can you manage the resources? The container schedulers do that great, and then, can you manage getting access to the data, and we're seeing more and more storage become container-native and people understanding how that works, so yeah, the breadth of what you can do around containers has gotten very, very large. >> Yeah, any difference in how your customers look at it, whether they're doing on-premises or public cloud, or do things like Docker and Kubernetes make that not matter as much? >> I think what they, so, I joke all the time, none of our customers have a container problem. None of them have a, none of them wake up in the morning and say, "That's my problem," right? What they're saying more and more is, "I know I want to, I'd like to start getting away "from maybe owning data centers, "or by destiny, being data centers. "I need to leverage public clouds, multiple, plural," and they're sort of saying, "Look, I get the benefit of what they do, "but there's still operational differences, "what Azure does, what AWS does. "I would like some level of consistency," and so that's where the OpenShift conversation really comes into play. The operational model I can build with OpenShift as a platform is the same thing I can run on top of Azure, on top of AWS, on top of Google, and we're seeing more and more of our deals, our customers who say, "That's what it's going to look like. "Help us make that work," and today, they do it on a basic level. Somebody like Volvo, for example, some in their data center, some in AWS, and then, more and more, they go, "Go contribute upstream in Kubernetes, "and federate this stuff." Make it look more consistent, make it look more operationally consistent, and that's coming in the next version of Kubernetes, and so forth, so, that shift is happening, but what they want is sort of this consistency. The Kubernetes part, the Docker part, they're sort of details under the covers, but it does provide them a level of portability that's really important. >> All right, Brian, want to give you the final word. Red Hat has got Red Hat Summit coming up, OpenStack and Jim Whitehurst is going to be given, I think, the day one keynote there. Talk a little bit of Red Hat's presence here at the show, what we can expect to see in this space from Red Hat throughout the year. >> Yeah, so I think, from us here, and what you'll see at Red Hat Summit, like, containers are front and center. Obviously, it's an extension of Linux, but it's, we're becoming a company that's more about how to do applications faster, how to modernize applications, how to do them across multiple clouds, and it's this whole idea that those things that used to be really hard, you do them in software now, and the community is helping to fix those, so big presence here. Again, we've got a ton of customers who use Docker as a packaging format, run their containers, open, at Red Hat Summit, we're going to have 25-plus production OpenShift customers that you want to talk about running governments, running airplanes, running, like, they're going to talk about that stuff, so that part, we're really excited about. It's fun, it's fun at this point. They don't, our customers don't want to talk about containers. They want to talk about this digital transformation stuff, and that is making the technology industry fun again. >> All right, so that was my last question for Brian Gracely with Red Hat. My last question for Brian Gracely of the Cloudcast is, I haven't heard Serverless mentioned yet this week. What's wrong? >> I know, that's a good, it's a good question. The Serverless stuff's taking off two weeks from now, probably, at the same, no, down the street. Serverlessconf is happening. >> Stu: Is that part of OSCON then, or? >> No, it's its own event now. >> It's own event. >> Serverless complement to their own event. They'll probably get five, 600 people. We're seeing it as another way of looking at applications. It's functions, containerize them, write your own code, and you'll see us, you'll see what we're doing around OpenShift begin to incorporate that, sort of functions as a server, Serverless stuff, very, very soon, and around Boston timeframe. >> All right, well, Brian, always great to talk to you, and glad I can bring it to the audience, so Brian Gracely with Red Hat. We'll be back with lots more coverage here, DockerCon 2017. You're watching theCUBE. (bright electronic music)

live from Las Vegas it's the cute covering knowledge 16 brought to you by service now here your host dave vellante and Jeff Frick we're back this is knowledge 16 this is the cube we go out to the events we extract the signal from the noise Matthias egg allah hafez here he's the program director at siemens AG worldwide conglomerate a US welcome to the cube thank you for inviting me star of the keynote this morning here we had that little snippet and but again you know welcome tell us what you do it siemens exactly so let me start i joined siemens in the crazy ebusiness world in two thousand but the journey i'm on currently is started in 2002 when we had the easy question of how many money is spending siemens on IT and this is an easy question but out in those days it was not to answer so we created a lot of transparency what is seaman spending in IT and we keep on driving that transparency based on the transparency we initiated different measure one was that we are focusing on service management in the infrastructure area for example in application we did a lot of consolidation and then we did several steps in the optimization based on the transparency we made we made some outsourcing deals we did a global IT organization and we managed our providers now since 12 years in service management but we thought what is the next step what is the big shot that is coming ahead of us and then we thought this is about service integration getting rid of the silos like network application data and the voice and having really an integration layer about the different topics as well as ensuring that we have end-to-end responsibility from the customer side and that was the challenge of answering that question was just so many stovepipes and so many systems and so many different systems of record and and is service now that integration layer is that exactly right so service now is our single service integration platform and it spans the word from the demand to the supply side demand of course our Siemens internal employees they were confronted in the old days with several portals my favorite example is always ordering an iPhone in Siemens was quite a difficult task you had to order in one part of the hardware in the other one the SIM card and in the third the messaging service now now we have the one-stop shop portal called my IT in Siemens and there we have a bundle where the customer has not to know which portal which provider we have our portal and the user can just concentrate what he needs and in that portal he can order and manage his IT and products as well as place incident so that's the demand side and then for the IT organization as you said we had a su of products and tools and processes and now with service management we have implemented a typical incident problem change service request config demand contract management's all the nice IT service management processes and rolled that out on a global scale so we have now one process one organization able to get the full transparency and the knowledge where is the status of IT and what is the head state is this so leading up to 2000 y2k we spend spend spend spend spend and then after y2k was a cut cut cut cut then how fast forward you've got visibility on the spend transparency what's the climate like Frank showed a chart today cost you know coming down but people are investing in IT because it's such an important part of the business are you able now to have much better line of sight on how those investments are producing for the business and has that affected your strategy totally and of course to a certain degree we have to go that path but we were able to cut the costs dramatically because we could shut down existing tool sets we could be faster in deploying new services so before we had the service now we had basically 15 tool sets that we had to an able to roll out the global service to Europe North America Latin and Asia 15 tools that now we have one that is of course dramatically faster in the deployment time in the time to customer in just enabling one tools that instead of 50 and you retired those other two sets or absolutely and people were screaming and kicking or was it absolutely they were all complaining about the tools but as soon as you tell them hey we are going shut down those tools they said hey that's the best we ever had and don't take my tool exactly but convincing them is quite easy with the ServiceNow product because it is from a usability standpoint modern integrated so you you catch that can catch them easily that they really can shut down the tools we even helped helped our providers also to shut down tools because they have basically the same environment they have not won cmdb one tool that they also have a fragmented environment and that's why we told all our providers in saying you can either work directly in our two or you have two connected to our tool but it's no longer that you have your own ecosystem so we have really generated an ecosystem from the employee that can order something in the mighty porter then it's going through our IT service management processes directly to our providers fully automated and that's where the providers also had to buy in in saying yeah we also see the benefits of consolidating our to landscape of getting better quality in our cmdb that that is the win-win situation what they don't like currently is that we have a much more transparency on how they perform now we don't have to wait until months end until we get a nice paper of green amber something we have now in our system real-time data anytime now we can really much more efficiently manage our provider can really dig into all the details that are available in our tools that and that's of course a big advantage but unfortunately provider has to get used to that that the customer is telling them how they provide it's a little bit a game changer it was that digit ID back to else la's or just new knowledge new information that you just didn't have before to help you manage that relationship now I mean of course SLA is an important topic but the SLA on a monthly basis speak one language but the experience on a daily basis tells another story so when we got the SAS on a month's end you always get an average ok level but if you then dig down into this as a in that country for this customer you saw some issues but that is now available in our ServiceNow instance and this is of course a great opportunity for us to manage the results of the providers and of course also as we have now our own tool set our own service integration architecture we can black in and out more easily the provider they don't like that as well but that is the advantage because I don't see and that is also a market trend that we get away from the 10 years 15 year outsourcing contracts this will be duration times of one year to year more cloud-based and to be really that or to support that velocity and speed that we can integrate much more easily the providers we have to have our own framework we have to have our own interfaces to the providers to really ensure we can plug in and out very easily one of the new acronyms that we are hearing at knowledge this year's asylum service integration and management it's been described as sort of son of ITIL i tilted Otto what is from your perspective matthias service i am so for me the big difference is i mean we we when we start with I to I think I too was a great achievement in defining the processes get a better maturity on incident problem and change and how this is done and also to generate the same verdict and so that you get a better understanding between the providers and the customers but what we missed in I tell is the integration so that we really if there is an incident and the we we allocate this incident to a provider and he doesn't feel responsible for it then we can transfer this incident to the next provider and hopefully he's then responsible and in charge so really the integration layer is for us very important because the market rent the competition in the different silos like end-user computing data and the application is pretty high so the value add for the customer is for me really in the integration layer getting the transparency across all your providers and of course the customers can you talk more about sort of how that is helped your your business and your providers business for example for the business I mean everybody talks about cloud services and all is fancy about cloud but to really manage cloud services is not that easy because what happened in in the in the old days the Siemens employs many they are cloud services with the credit card meaning if they wanted to have a server they look to Amazon or any other provider gave in the credit card and then this server was out of the IT well but now with the platform we have ensured that we can manage all the cloud services not only the ordering is done by our my IT porter we are getting also the reports not on a monthly basis but really on daily basis what is the usage of the cloud services and then we can either apps care downscale or even decommission those servers that are no longer needed because if they are managed by a credit card just we could to manage and that's why it was a key criteria for this platform to also managed cloud services and do you have a module for people to spin up just little dev instances of Amazon so you've actually brought shadow I tee underneath the ServiceNow platform absolutely and we have to expand that so we are at the beginning of that journey but as cloud is picking up and Siemens is also more addicted to cloud services we made sure that we have two examples of providers that are really working with that platform and that we can manage the whole life cycle of a cloud service so how would you describe sort of your strategy with respect to service now we're hearing a lot about obviously you know started in IT Service Management we're hearing a lot about other parts of the organization where are you guys in that whole journey I mean I could also start with talking about defenses staff outside of IT yeah but I think two topics are really important one is there are still a lot of IT service management processes within Siemens we have to shut down that means migration of existing tool sets is still a key activity for us because then we can fully leverage our investment we made into our ServiceNow platform in bringing in additional tools so this is one key component that we have to follow the second one is as we have a high degree of automation we really have to make sure that the system is mature for example we are exchanging data with our own application provider application for incident problem and change 13 million data sets per month that's quite a big number and if that data is not right if we have mixed up data the whole chain breaks the whole automation doesn't work so we spend also a lot of effort in hardening the system spending a lot of time in cleaning up the data that we are really sure we can also achieve the high degree of automation because it's always nice saying high degree of automation digitalization but getting there is an awful work because this is painful getting the right data cleaning the data and having the right data and as you do one then you just find your next point of failure right as you optimize the one then you move it it's a classic production line kind of band and that's why i say migration maturing the the system is one key then the third topic is of course we will bring in more providers more services more processes we we just downloaded from the ServiceNow App Store an application called Moby cod to manage our telecom expense management that we have also they are more transparency over the world and then of course we are in discussions to expand that platform also to facility management or HR but this will take some time because we still have in the HR facility area let's say Best of Breed applications and then it's hard to compete against the integration layer and saying okay but if it's integrated we have all the incidents in and all the data so that balance is not there but I heavenly believe that this will come as service now is more maturing in the HR facility area what not and then I think the the racial looks different and it's more promising also for Siemens to go beyond i TS so as you build out this integration architecture i have to ask you about security and my question is not one of a technical nature it's one of sort of a philosophical nature how is the conversation shifting right it's free decades we've spent money on the perimeter and protecting and and will keep the bad guys out now we all realize they can't keep the bad guys out it's how you respond to the bad guys and it seems as though ServiceNow could potentially is in some cases solving that problem how has the security conversation changed within your organization yeah i mean the security is high on the agenda with all the burn a little bit wilner abilities you here in the in the news and also did the day-to-day cases so security is a top agenda point and we had also some hard discussions within the siemens because the first reaction of demons was we have to have service now on premise we have to have our own nice server below the table and then we had some good discussions with herb is now we had discussions with other customers where they said no no we trust in this a solution then we did some penetration tests we did some assessment on side and that's where we said okay we will go with the SAS solution also for for semen and I'm pretty happy that we made the decision because now we don't have to focus on the operational topics we can really focus on the content bringing in new services bringing in you providers in rather discussing upgrading servers that you need to have the performance etc so that is also a next step we have on the agenda to bring in the vulnerability infosec topping also to our platform and but and is that the responsibility of sort of one group a group of gurus or is it a shared responsibility across the business or what should it be it is a shared responsibility because we are carefully watching how the ServiceNow cmdb is growing because we are collecting a lot of data we see exactly what is going on Adam and size of what are the customers ordering what in kind of incidents are they opening up we see exactly how our IT s doing and of course the provider data we have all the sea ice in our database and as we grow we grow the data that is in our system and that is of course a huge value but also security wise also a balance you have to make my last question I'll give you the last word we gotta wrap just knowledge you know your your experience here you know things you've learned anything that surprised you haha delighted you hear your you know I think the knowledge is really a great opportunity to meet at our customers to see what they have on the agenda were they working against and also it's a good opportunity to see what are the the hot topics for service now how does that match with our agenda that we have with our pipeline so we have a lot of discussions in the knowledge and that is a great value great Matthias egg will have thanks very much for coming in the cube preciate your time thank you good to have you all right keep right to everybody is the Cuba right back we're live at knowledge 16