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

>> Announcer: From around the globe, it's the queue with digital coverage of DockerCon live 2020. Brought to you by Docker and its ecosystem partners. >> Welcome, welcome, welcome to DockerCon 2020. We got over 50,000 people registered so there's clearly a ton of interest in the world of Docker and Eddie's as I like to call it. And we've assembled a power panel of Open Source and cloud native experts to talk about where things stand in 2020 and where we're headed. I'm Shawn Conley, I'll be the moderator for today's panel. I'm also a proud alum of JBoss, Red Hat, SpringSource, VMware and Hortonworks and I'm broadcasting from my hometown of Philly. Our panelists include; Michelle Noorali, Senior Software Engineer at Microsoft, joining us from Atlanta, Georgia. We have Kelsey Hightower, Principal developer advocate at Google Cloud, joining us from Washington State and we have Chris Aniszczyk, CTO CIO at the CNCF, joining us from Austin, Texas. So I think we have the country pretty well covered. Thank you all for spending time with us on this power panel. Chris, I'm going to start with you, let's dive right in. You've been in the middle of the Docker netease wave since the beginning with a clear focus on building a better world through open collaboration. What are your thoughts on how the Open Source landscape has evolved over the past few years? Where are we in 2020? And where are we headed from both community and a tech perspective? Just curious to get things sized up? >> Sure, when CNCF started about roughly four, over four years ago, the technology mostly focused on just the things around Kubernetes, monitoring communities with technology like Prometheus, and I think in 2020 and the future, we definitely want to move up the stack. So there's a lot of tools being built on the periphery now. So there's a lot of tools that handle running different types of workloads on Kubernetes. So things like Uvert and Shay runs VMs on Kubernetes, which is crazy, not just containers. You have folks that, Microsoft experimenting with a project called Kruslet which is trying to run web assembly workloads natively on Kubernetes. So I think what we've seen now is more and more tools built around the periphery, while the core of Kubernetes has stabilized. So different technologies and spaces such as security and different ways to run different types of workloads. And at least that's kind of what I've seen. >> So do you have a fair amount of vendors as well as end users still submitting in projects in, is there still a pretty high volume? >> Yeah, we have 48 total projects in CNCF right now and Michelle could speak a little bit more to this being on the DOC, the pipeline for new projects is quite extensive and it covers all sorts of spaces from two service meshes to security projects and so on. So it's ever so expanding and filling in gaps in that cloud native landscape that we have. >> Awesome. Michelle, Let's head to you. But before we actually dive in, let's talk a little glory days. A rumor has it that you are the Fifth Grade Kickball Championship team captain. (Michelle laughs) Are the rumors true? >> They are, my speech at the end of the year was the first talk I ever gave. But yeah, it was really fun. I wasn't captain 'cause I wasn't really great at anything else apart from constantly cheer on the team. >> A little better than my eighth grade Spelling Champ Award so I think I'd rather have the kickball. But you've definitely, spent a lot of time leading an Open Source, you've been across many projects for many years. So how does the art and science of collaboration, inclusivity and teamwork vary? 'Cause you're involved in a variety of efforts, both in the CNCF and even outside of that. And then what are some tips for expanding the tent of Open Source projects? >> That's a good question. I think it's about transparency. Just come in and tell people what you really need to do and clearly articulate your problem, more clearly articulate your problem and why you can't solve it with any other solution, the more people are going to understand what you're trying to do and be able to collaborate with you better. What I love about Open Source is that where I've seen it succeed is where incentives of different perspectives and parties align and you're just transparent about what you want. So you can collaborate where it makes sense, even if you compete as a company with another company in the same area. So I really like that, but I just feel like transparency and honesty is what it comes down to and clearly communicating those objectives. >> Yeah, and the various foundations, I think one of the things that I've seen, particularly Apache Software Foundation and others is the notion of checking your badge at the door. Because the competition might be between companies, but in many respects, you have engineers across many companies that are just kicking butt with the tech they contribute, claiming victory in one way or the other might make for interesting marketing drama. But, I think that's a little bit of the challenge. In some of the, standards-based work you're doing I know with CNI and some other things, are they similar, are they different? How would you compare and contrast into something a little more structured like CNCF? >> Yeah, so most of what I do is in the CNCF, but there's specs and there's projects. I think what CNCF does a great job at is just iterating to make it an easier place for developers to collaborate. You can ask the CNCF for basically whatever you need, and they'll try their best to figure out how to make it happen. And we just continue to work on making the processes are clearer and more transparent. And I think in terms of specs and projects, those are such different collaboration environments. Because if you're in a project, you have to say, "Okay, I want this feature or I want this bug fixed." But when you're in a spec environment, you have to think a little outside of the box and like, what framework do you want to work in? You have to think a little farther ahead in terms of is this solution or this decision we're going to make going to last for the next how many years? You have to get more of a buy in from all of the key stakeholders and maintainers. So it's a little bit of a longer process, I think. But what's so beautiful is that you have this really solid, standard or interface that opens up an ecosystem and allows people to build things that you could never have even imagined or dreamed of so-- >> Gotcha. So I'm Kelsey, we'll head over to you as your focus is on, developer advocate, you've been in the cloud native front lines for many years. Today developers are faced with a ton of moving parts, spanning containers, functions, Cloud Service primitives, including container services, server-less platforms, lots more, right? I mean, there's just a ton of choice. How do you help developers maintain a minimalist mantra in the face of such a wealth of choice? I think minimalism I hear you talk about that periodically, I know you're a fan of that. How do you pass that on and your developer advocacy in your day to day work? >> Yeah, I think, for most developers, most of this is not really the top of mind for them, is something you may see a post on Hacker News, and you might double click into it. Maybe someone on your team brought one of these tools in and maybe it leaks up into your workflow so you're forced to think about it. But for most developers, they just really want to continue writing code like they've been doing. And the best of these projects they'll never see. They just work, they get out of the way, they help them with log in, they help them run their application. But for most people, this isn't the core idea of the job for them. For people in operations, on the other hand, maybe these components fill a gap. So they look at a lot of this stuff that you see in the CNCF and Open Source space as number one, various companies or teams sharing the way that they do things, right? So these are ideas that are put into the Open Source, some of them will turn into products, some of them will just stay as projects that had mutual benefit for multiple people. But for the most part, it's like walking through an ion like Home Depot. You pick the tools that you need, you can safely ignore the ones you don't need, and maybe something looks interesting and maybe you study it to see if that if you have a problem. And for most people, if you don't have that problem that that tool solves, you should be happy. No one needs every project and I think that's where the foundation for confusion. So my main job is to help people not get stuck and confused in LAN and just be pragmatic and just use the tools that work for 'em. >> Yeah, and you've spent the last little while in the server-less space really diving into that area, compare and contrast, I guess, what you found there, minimalist approach, who are you speaking to from a server-less perspective versus that of the broader CNCF? >> The thing that really pushed me over, I was teaching my daughter how to make a website. So she's on her Chromebook, making a website, and she's hitting 127.0.0.1, and it looks like geo cities from the 90s but look, she's making website. And she wanted her friends to take a look. So she copied and paste from her browser 127.0.0.1 and none of her friends could pull it up. So this is the point where every parent has to cross that line and say, "Hey, do I really need to sit down "and teach my daughter about Linux "and Docker and Kubernetes." That isn't her main goal, her goal was to just launch her website in a way that someone else can see it. So we got Firebase installed on her laptop, she ran one command, Firebase deploy. And our site was up in a few minutes, and she sent it over to her friend and there you go, she was off and running. The whole server-less movement has that philosophy as one of the stated goal that needs to be the workflow. So, I think server-less is starting to get closer and closer, you start to see us talk about and Chris mentioned this earlier, we're moving up the stack. Where we're going to up the stack, the North Star there is feel where you get the focus on what you're doing, and not necessarily how to do it underneath. And I think server-less is not quite there yet but every type of workload, stateless web apps check, event driven workflows check, but not necessarily for things like machine learning and some other workloads that more traditional enterprises want to run so there's still work to do there. So server-less for me, serves as the North Star for why all these Projects exists for people that may have to roll their own platform, to provide the experience. >> So, Chris, on a related note, with what we were just talking about with Kelsey, what's your perspective on the explosion of the cloud native landscape? There's, a ton of individual projects, each can be used separately, but in many cases, they're like Lego blocks and used together. So things like the surface mesh interface, standardizing interfaces, so things can snap together more easily, I think, are some of the approaches but are you doing anything specifically to encourage this cross fertilization and collaboration of bug ability, because there's just a ton of projects, not only at the CNCF but outside the CNCF that need to plug in? >> Yeah, I mean, a lot of this happens organically. CNCF really provides of the neutral home where companies, competitors, could trust each other to build interesting technology. We don't force integration or collaboration, it happens on its own. We essentially allow the market to decide what a successful project is long term or what an integration is. We have a great Technical Oversight Committee that helps shepherd the overall technical vision for the organization and sometimes steps in and tries to do the right thing when it comes to potentially integrating a project. Previously, we had this issue where there was a project called Open Tracing, and an effort called Open Census, which is basically trying to standardize how you're going to deal with metrics, on the tree and so on in a cloud native world that we're essentially competing with each other. The CNCF TC and committee came together and merged those projects into one parent ever called Open Elementary and so that to me is a case study of how our committee helps, bridges things. But we don't force things, we essentially want our community of end users and vendors to decide which technology is best in the long term, and we'll support that. >> Okay, awesome. And, Michelle, you've been focused on making distributed systems digestible, which to me is about simplifying things. And so back when Docker arrived on the scene, some people referred to it as developer dopamine, which I love that term, because it's simplified a bunch of crufty stuff for developers and actually helped them focus on doing their job, writing code, delivering code, what's happening in the community to help developers wire together multi-part modern apps in a way that's elegant, digestible, feels like a dopamine rush? >> Yeah, one of the goals of the(mumbles) project was to make it easier to deploy an application on Kubernetes so that you could see what the finished product looks like. And then dig into all of the things that that application is composed of, all the resources. So we're really passionate about this kind of stuff for a while now. And I love seeing projects that come into the space that have this same goal and just iterate and make things easier. I think we have a ways to go still, I think a lot of the iOS developers and JS developers I get to talk to don't really care that much about Kubernetes. They just want to, like Kelsey said, just focus on their code. So one of the projects that I really like working with is Tilt gives you this dashboard in your CLI, aggregates all your logs from your applications, And it kind of watches your application changes, and reconfigures those changes in Kubernetes so you can see what's going on, it'll catch errors, anything with a dashboard I love these days. So Yali is like a metrics dashboard that's integrated with STL, a service graph of your service mesh, and lets you see the metrics running there. I love that, I love that dashboard so much. Linkerd has some really good service graph images, too. So anything that helps me as an end user, which I'm not technically an end user, but me as a person who's just trying to get stuff up and running and working, see the state of the world easily and digest them has been really exciting to see. And I'm seeing more and more dashboards come to light and I'm very excited about that. >> Yeah, as part of the DockerCon just as a person who will be attending some of the sessions, I'm really looking forward to see where DockerCompose is going, I know they opened up the spec to broader input. I think your point, the good one, is there's a bit more work to really embrace the wealth of application artifacts that compose a larger application. So there's definitely work the broader community needs to lean in on, I think. >> I'm glad you brought that up, actually. Compose is something that I should have mentioned and I'm glad you bring that up. I want to see programming language libraries, integrate with the Compose spec. I really want to see what happens with that I think is great that they open that up and made that a spec because obviously people really like using Compose. >> Excellent. So Kelsey, I'd be remiss if I didn't touch on your January post on changelog entitled, "Monoliths are the Future." Your post actually really resonated with me. My son works for a software company in Austin, Texas. So your hometown there, Chris. >> Yeah. >> Shout out to Will and the chorus team. His development work focuses on adding modern features via micro services as extensions to the core monolith that the company was founded on. So just share some thoughts on monoliths, micro services. And also, what's deliverance dopamine from your perspective more broadly, but people usually phrase as monoliths versus micro services, but I get the sense you don't believe it's either or. >> Yeah, I think most companies from the pragmatic so one of their argument is one of pragmatism. Most companies have trouble designing any app, monolith, deployable or microservices architecture. And then these things evolve over time. Unless you're really careful, it's really hard to know how to slice these things. So taking an idea or a problem and just knowing how to perfectly compartmentalize it into individual deployable component, that's hard for even the best people to do. And double down knowing the actual solution to the particular problem. A lot of problems people are solving they're solving for the first time. It's really interesting, our industry in general, a lot of people who work in it have never solved the particular problem that they're trying to solve for the first time. So that's interesting. The other part there is that most of these tools that are here to help are really only at the infrastructure layer. We're talking freeways and bridges and toll bridges, but there's nothing that happens in the actual developer space right there in memory. So the libraries that interface to the structure logging, the libraries that deal with rate limiting, the libraries that deal with authorization, can this person make this query with this user ID? A lot of those things are still left for developers to figure out on their own. So while we have things like the brunettes and fluid D, we have all of these tools to deploy apps into those target, most developers still have the problem of everything you do above that line. And to be honest, the majority of the complexity has to be resolved right there in the app. That's the thing that's taking requests directly from the user. And this is where maybe as an industry, we're over-correcting. So we had, you said you come from the JBoss world, I started a lot of my Cisco administration, there's where we focus a little bit more on the actual application needs, maybe from a router that as well. But now what we're seeing is things like Spring Boot, start to offer a little bit more integration points in the application space itself. So I think the biggest parts that are missing now are what are the frameworks people will use for authorization? So you have projects like OPA, Open Policy Agent for those that are new to that, it gives you this very low level framework, but you still have to understand the concepts around, what does it mean to allow someone to do something and one missed configuration, all your security goes out of the window. So I think for most developers this is where the next set of challenges lie, if not actually the original challenge. So for some people, they were able to solve most of these problems with virtualization, run some scripts, virtualize everything and be fine. And monoliths were okay for that. For some reason, we've thrown pragmatism out of the window and some people are saying the only way to solve these problems is by breaking the app into 1000 pieces. Forget the fact that you had trouble managing one piece, you're going to somehow find the ability to manage 1000 pieces with these tools underneath but still not solving the actual developer problems. So this is where you've seen it already with a couple of popular blog posts from other companies. They cut too deep. They're going from 2000, 3000 microservices back to maybe 100 or 200. So to my world, it's going to be not just one monolith, but end up maybe having 10 or 20 monoliths that maybe reflect the organization that you have versus the architectural pattern that you're at. >> I view it as like a constellation of stars and planets, et cetera. Where you you might have a star that has a variety of, which is a monolith, and you have a variety of sort of planetary microservices that float around it. But that's reality, that's the reality of modern applications, particularly if you're not starting from a clean slate. I mean your points, a good one is, in many respects, I think the infrastructure is code movement has helped automate a bit of the deployment of the platform. I've been personally focused on app development JBoss as well as springsSource. The Spring team I know that tech pretty well over the years 'cause I was involved with that. So I find that James Governor's discussion of progressive delivery really resonates with me, as a developer, not so much as an infrastructure Deployer. So continuous delivery is more of infrastructure notice notion, progressive delivery, feature flags, those types of things, or app level, concepts, minimizing the blast radius of your, the new features you're deploying, that type of stuff, I think begins to speak to the pain of application delivery. So I'll guess I'll put this up. Michelle, I might aim it to you, and then we'll go around the horn, what are your thoughts on the progressive delivery area? How could that potentially begin to impact cloud native over 2020? I'm looking for some rallying cries that move up the stack and give a set of best practices, if you will. And I think James Governor of RedMonk opened on something that's pretty important. >> Yeah, I think it's all about automating all that stuff that you don't really know about. Like Flagger is an awesome progressive delivery tool, you can just deploy something, and people have been asking for so many years, ever since I've been in this space, it's like, "How do I do AB deployment?" "How do I do Canary?" "How do I execute these different deployment strategies?" And Flagger is a really good example, for example, it's a really good way to execute these deployment strategies but then, make sure that everything's happening correctly via observing metrics, rollback if you need to, so you don't just throw your whole system. I think it solves the problem and allows you to take risks but also keeps you safe in that you can be confident as you roll out your changes that it all works, it's metrics driven. So I'm just really looking forward to seeing more tools like that. And dashboards, enable that kind of functionality. >> Chris, what are your thoughts in that progressive delivery area? >> I mean, CNCF alone has a lot of projects in that space, things like Argo that are tackling it. But I want to go back a little bit to your point around developer dopamine, as someone that probably spent about a decade of his career focused on developer tooling and in fact, if you remember the Eclipse IDE and that whole integrated experience, I was blown away recently by a demo from GitHub. They have something called code spaces, which a long time ago, I was trying to build development environments that essentially if you were an engineer that joined a team recently, you could basically get an environment quickly start it with everything configured, source code checked out, environment properly set up. And that was a very hard problem. This was like before container days and so on and to see something like code spaces where you'd go to a repo or project, open it up, behind the scenes they have a container that is set up for the environment that you need to build and just have a VS code ID integrated experience, to me is completely magical. It hits like developer dopamine immediately for me, 'cause a lot of problems when you're going to work with a project attribute, that whole initial bootstrap of, "Oh you need to make sure you have this library, this install," it's so incredibly painful on top of just setting up your developer environment. So as we continue to move up the stack, I think you're going to see an incredible amount of improvements around the developer tooling and developer experience that people have powered by a lot of this cloud native technology behind the scenes that people may not know about. >> Yeah, 'cause I've been talking with the team over at Docker, the work they're doing with that desktop, enable the aim local environment, make sure it matches as closely as possible as your deployed environments that you might be targeting. These are some of the pains, that I see. It's hard for developers to get bootstrapped up, it might take him a day or two to actually just set up their local laptop and development environment, and particularly if they change teams. So that complexity really corralling that down and not necessarily being overly prescriptive as to what tool you use. So if you're visual code, great, it should feel integrated into that environment, use a different environment or if you feel more comfortable at the command line, you should be able to opt into that. That's some of the stuff I get excited to potentially see over 2020 as things progress up the stack, as you said. So, Michelle, just from an innovation train perspective, and we've covered a little bit, what's the best way for people to get started? I think Kelsey covered a little bit of that, being very pragmatic, but all this innovation is pretty intimidating, you can get mowed over by the train, so to speak. So what's your advice for how people get started, how they get involved, et cetera. >> Yeah, it really depends on what you're looking for and what you want to learn. So, if you're someone who's new to the space, honestly, check out the case studies on cncf.io, those are incredible. You might find environments that are similar to your organization's environments, and read about what worked for them, how they set things up, any hiccups they crossed. It'll give you a broad overview of the challenges that people are trying to solve with the technology in this space. And you can use that drill into the areas that you want to learn more about, just depending on where you're coming from. I find myself watching old KubeCon talks on the cloud native computing foundations YouTube channel, so they have like playlists for all of the conferences and the special interest groups in CNCF. And I really enjoy talking, I really enjoy watching excuse me, older talks, just because they explain why things were done, the way they were done, and that helps me build the tools I built. And if you're looking to get involved, if you're building projects or tools or specs and want to contribute, we have special interest groups in the CNCF. So you can find that in the CNCF Technical Oversight Committee, TOC GitHub repo. And so for that, if you want to get involved there, choose a vertical. Do you want to learn about observability? Do you want to drill into networking? Do you care about how to deliver your app? So we have a cig called app delivery, there's a cig for each major vertical, and you can go there to see what is happening on the edge. Really, these are conversations about, okay, what's working, what's not working and what are the next changes we want to see in the next months. So if you want that kind of granularity and discussion on what's happening like that, then definitely join those those meetings. Check out those meeting notes and recordings. >> Gotcha. So on Kelsey, as you look at 2020 and beyond, I know, you've been really involved in some of the earlier emerging tech spaces, what gets you excited when you look forward? What gets your own level of dopamine up versus the broader community? What do you see coming that we should start thinking about now? >> I don't think any of the raw technology pieces get me super excited anymore. Like, I've seen the circle of around three or four times, in five years, there's going to be a new thing, there might be a new foundation, there'll be a new set of conferences, and we'll all rally up and probably do this again. So what's interesting now is what people are actually using the technology for. Some people are launching new things that maybe weren't possible because infrastructure costs were too high. People able to jump into new business segments. You start to see these channels on YouTube where everyone can buy a mic and a B app and have their own podcasts and be broadcast to the globe, just for a few bucks, if not for free. Those revolutionary things are the big deal and they're hard to come by. So I think we've done a good job democratizing these ideas, distributed systems, one company got really good at packaging applications to share with each other, I think that's great, and never going to reset again. And now what's going to be interesting is, what will people build with this stuff? If we end up building the same things we were building before, and then we're talking about another digital transformation 10 years from now because it's going to be funny but Kubernetes will be the new legacy. It's going to be the things that, "Oh, man, I got stuck in this Kubernetes thing," and there'll be some governor on TV, looking for old school Kubernetes engineers to migrate them to some new thing, that's going to happen. You got to know that. So at some point merry go round will stop. And we're going to be focused on what you do with this. So the internet is there, most people have no idea of the complexities of underwater sea cables. It's beyond one or two people, or even one or two companies to comprehend. You're at the point now, where most people that jump on the internet are talking about what you do with the internet. You can have Netflix, you can do meetings like this one, it's about what you do with it. So that's going to be interesting. And we're just not there yet with tech, tech is so, infrastructure stuff. We're so in the weeds, that most people almost burn out what's just getting to the point where you can start to look at what you do with this stuff. So that's what I keep in my eye on, is when do we get to the point when people just ship things and build things? And I think the closest I've seen so far is in the mobile space. If you're iOS developer, Android developer, you use the SDK that they gave you, every year there's some new device that enables some new things speech to text, VR, AR and you import an STK, and it just worked. And you can put it in one place and 100 million people can download it at the same time with no DevOps team, that's amazing. When can we do that for server side applications? That's going to be something I'm going to find really innovative. >> Excellent. Yeah, I mean, I could definitely relate. I was Hortonworks in 2011, so, Hadoop, in many respects, was sort of the precursor to the Kubernetes area, in that it was, as I like to refer to, it was a bunch of animals in the zoo, wasn't just the yellow elephant. And when things mature beyond it's basically talking about what kind of analytics are driving, what type of machine learning algorithms and applications are they delivering? You know that's when things tip over into a real solution space. So I definitely see that. I think the other cool thing even just outside of the container and container space, is there's just such a wealth of data related services. And I think how those two worlds come together, you brought up the fact that, in many respects, server-less is great, it's stateless, but there's just a ton of stateful patterns out there that I think also need to be addressed as these richer applications to be from a data processing and actionable insights perspective. >> I also want to be clear on one thing. So some people confuse two things here, what Michelle said earlier about, for the first time, a whole group of people get to learn about distributed systems and things that were reserved to white papers, PhDs, CF site, this stuff is now super accessible. You go to the CNCF site, all the things that you read about or we used to read about, you can actually download, see how it's implemented and actually change how it work. That is something we should never say is a waste of time. Learning is always good because someone has to build these type of systems and whether they sell it under the guise of server-less or not, this will always be important. Now the other side of this is, that there are people who are not looking to learn that stuff, the majority of the world isn't looking. And in parallel, we should also make this accessible, which should enable people that don't need to learn all of that before they can be productive. So that's two sides of the argument that can be true at the same time, a lot of people get caught up. And everything should just be server-less and everyone learning about distributed systems, and contributing and collaborating is wasting time. We can't have a world where there's only one or two companies providing all infrastructure for everyone else, and then it's a black box. We don't need that. So we need to do both of these things in parallel so I just want to make sure I'm clear that it's not one of these or the other. >> Yeah, makes sense, makes sense. So we'll just hit the final topic. Chris, I think I'll ask you to help close this out. COVID-19 clearly has changed how people work and collaborate. I figured we'd end on how do you see, so DockerCon is going to virtual events, inherently the Open Source community is distributed and is used to not face to face collaboration. But there's a lot of value that comes together by assembling a tent where people can meet, what's the best way? How do you see things playing out? What's the best way for this to evolve in the face of the new normal? >> I think in the short term, you're definitely going to see a lot of virtual events cropping up all over the place. Different themes, verticals, I've already attended a handful of virtual events the last few weeks from Red Hat summit to Open Compute summit to Cloud Native summit, you'll see more and more of these. I think, in the long term, once the world either get past COVID or there's a vaccine or something, I think the innate nature for people to want to get together and meet face to face and deal with all the serendipitous activities you would see in a conference will come back, but I think virtual events will augment these things in the short term. One benefit we've seen, like you mentioned before, DockerCon, can have 50,000 people at it. I don't remember what the last physical DockerCon had but that's definitely an order of magnitude more. So being able to do these virtual events to augment potential of physical events in the future so you can build a more inclusive community so people who cannot travel to your event or weren't lucky enough to win a scholarship could still somehow interact during the course of event to me is awesome and I hope something that we take away when we start all doing these virtual events when we get back to physical events, we find a way to ensure that these things are inclusive for everyone and not just folks that can physically make it there. So those are my thoughts on on the topic. And I wish you the best of luck planning of DockerCon and so on. So I'm excited to see how it turns out. 50,000 is a lot of people and that just terrifies me from a cloud native coupon point of view, because we'll probably be somewhere. >> Yeah, get ready. Excellent, all right. So that is a wrap on the DockerCon 2020 Open Source Power Panel. I think we covered a ton of ground. I'd like to thank Chris, Kelsey and Michelle, for sharing their perspectives on this continuing wave of Docker and cloud native innovation. I'd like to thank the DockerCon attendees for tuning in. And I hope everybody enjoys the rest of the conference. (upbeat music)

>> Narrator: From around the globe, it's theCUBE with digital coverage of Docker Con Live 2020, brought to you by Docker and its ecosystem partners. >> Okay, welcome back to the DockerCon studio headquarters and your hosts, Jenny Burcio and myself John Furrier. @Furrier on Twitter if you want to tweet me anything and @DockerCon as well share what you're thinking. Great keynote there from Scott CEO, Jenny, demo, DockerCon jobs, some highlights there from Scott. Yeah, lovely intro, sorry about to do the keynote. The little green room comes on makes it human. We're all trying to meet >> Its certainly the reality of what we are all dealing with right now. I had to ask my kids to leave though or they would crash the whole stream. But yes, we have you know, we have a great community, large community gathered here today and we do want to take the opportunity for those that are looking for jobs or hiring to share with the #DockerCon jobs. In addition, we want to support direct health care workers. And Brett Fisher and the captains will be running all day charity stream on the captain's channel. Go there and you'll get the link to donate to directRelief.org, which is a California based nonprofit delivering aid and supporting health care workers globally with response to the COVID-19 crisis. >> Okay, if you're jumping into the stream, I'm John Furrier with Jenny, we'll be your hosts all day today, throughout Docker con, it's a packed house of great content, you have a mainstream, theCUBE, which is the mainstream that will be promoting a lot of cube interviews, but check out the 40 plus sessions underneath in the interactive calendar on Dockercon.com site. Check it out, they're going to be live on a clock. So if you want to participate in real time in the chat, jump into your session on the track of your choice and participate with the folks in their chatting. If you miss it, it's going to go right on demand right after sort of all content will be immediately be available. So make sure you check it out. Docker selfie is a hashtag take a selfie, share it. Docker, #Docker jobs. If you're looking for a job or have openings, please share with the community and of course, give us feedback on what you can do. We got James governor of the keynote coming up next. He's with red monk, not afraid to share his opinion on open source on what companies should be doing. And also the evolution of this Cambrian explosion of apps that are going to be coming as we come out of this post pandemic world. A lot of people are thinking about this the crisis and following through so you know, stay with us, for more and more coverage, Jenny favorite sessions on your mind for people to pay attention to that they should they should look >> First I'm going to address a few things that continue to come up in the chat. Sessions are recorded especially breakout sessions after they play live and the speakers in chat with you. Those go on demand they are recorded, you will be able to access them. Also, if the screen is too small, there is the button to expand full screen and different quality levels for the video that you can choose on your end. All the breakout sessions also have closed captioning. So please, if you would like to read along, turn that on, so you can stay with the sessions. We have some great sessions kicking off right at 10:00 a.m. Getting started with Docker. We have a full track really in the how to enhance on that you should check out devs in action, hear what other people are doing. And then of course, our sponsors are delivering great content to you all day long. >> Tons of content, it's all available, they'll always be up always on a large scale. Thanks for watching. Now we got James Governor, the keynote. He's with red McDonald's firm, he's been tracking open source for many generations. He's been doing amazing work, watch his great keynote. I'm going to be interviewing him live right after so stay with us and enjoy the rest of the day. We'll see you back shortly. (upbeat music)

(water running) (upbeat music) (electric buzzing) >> Fuel up! (upbeat music) (audience clapping) (upbeat music) >> Announcer: From around the globe. It's the queue with digital coverage of DockerCon live 2020, brought to you by Docker and its ecosystem partners. >> Hello everyone, welcome to DockerCon 2020. I'm John Furrier with theCUBE I'm in our Palo Alto studios with our quarantine crew. We have a great lineup here for DockerCon 2020. Virtual event, normally it was in person face to face. I'll be with you throughout the day from an amazing lineup of content, over 50 different sessions, cube tracks, keynotes, and we've got two great co-hosts here with Docker, Jenny Burcio and Bret Fisher. We'll be with you all day today, taking you through the program, helping you navigate the sessions. I'm so excited. Jenny, this is a virtual event. We talk about this. Can you believe it? Maybe the internet gods be with us today and hope everyone's having-- >> Yes. >> Easy time getting in. Jenny, Bret, thank you for-- >> Hello. >> Being here. >> Hey. >> Hi everyone, so great to see everyone chatting and telling us where they're from. Welcome to the Docker community. We have a great day planned for you. >> Guys great job getting this all together. I know how hard it is. These virtual events are hard to pull off. I'm blown away by the community at Docker. The amount of sessions that are coming in the sponsor support has been amazing. Just the overall excitement around the brand and the opportunities given this tough times where we're in. It's super exciting again, made the internet gods be with us throughout the day, but there's plenty of content. Bret's got an amazing all day marathon group of people coming in and chatting. Jenny, this has been an amazing journey and it's a great opportunity. Tell us about the virtual event. Why DockerCon virtual. Obviously everyone's canceling their events, but this is special to you guys. Talk about DockerCon virtual this year. >> The Docker community shows up at DockerCon every year, and even though we didn't have the opportunity to do an in person event this year, we didn't want to lose the time that we all come together at DockerCon. The conversations, the amazing content and learning opportunities. So we decided back in December to make DockerCon a virtual event. And of course when we did that, there was no quarantine we didn't expect, you know, I certainly didn't expect to be delivering it from my living room, but we were just, I mean we were completely blown away. There's nearly 70,000 people across the globe that have registered for DockerCon today. And when you look at DockerCon of past right live events, really and we're learning are just the tip of the iceberg and so thrilled to be able to deliver a more inclusive global event today. And we have so much planned I think. Bret, you want to tell us some of the things that you have planned? >> Well, I'm sure I'm going to forget something 'cause there's a lot going on. But, we've obviously got interviews all day today on this channel with John and the crew. Jenny has put together an amazing set of all these speakers, and then you have the captain's on deck, which is essentially the YouTube live hangout where we just basically talk shop. It's all engineers, all day long. Captains and special guests. And we're going to be in chat talking to you about answering your questions. Maybe we'll dig into some stuff based on the problems you're having or the questions you have. Maybe there'll be some random demos, but it's basically not scripted, it's an all day long unscripted event. So I'm sure it's going to be a lot of fun hanging out in there. >> Well guys, I want to just say it's been amazing how you structured this so everyone has a chance to ask questions, whether it's informal laid back in the captain's channel or in the sessions, where the speakers will be there with their presentations. But Jenny, I want to get your thoughts because we have a site out there that's structured a certain way for the folks watching. If you're on your desktop, there's a main stage hero. There's then tracks and Bret's running the captain's tracks. You can click on that link and jump into his session all day long. He's got an amazing set of line of sleet, leaning back, having a good time. And then each of the tracks, you can jump into those sessions. It's on a clock, it'll be available on demand. All that content is available if you're on your desktop. If you're on your mobile, it's the same thing. Look at the calendar, find the session that you want. If you're interested in it, you could watch it live and chat with the participants in real time or watch it on demand. So there's plenty of content to navigate through. We do have it on a clock and we'll be streaming sessions as they happen. So you're in the moment and that's a great time to chat in real time. But there's more, Jenny, getting more out of this event. You guys try to bring together the stimulation of community. How does the participants get more out of the the event besides just consuming some of the content all day today? >> Yes, so first set up your profile, put your picture next to your chat handle and then chat. John said we have various setups today to help you get the most out of your experience are breakout sessions. The content is prerecorded, so you get quality content and the speakers and chat so you can ask questions the whole time. If you're looking for the hallway track, then definitely check out the captain's on deck channel. And then we have some great interviews all day on the queue. So set up your profile, join the conversation and be kind, right? This is a community event. Code of conduct is linked on every page at the top, and just have a great day. >> And Bret, you guys have an amazing lineup on the captain, so you have a great YouTube channel that you have your stream on. So the folks who were familiar with that can get that either on YouTube or on the site. The chat is integrated in, So you're set up, what do you got going on? Give us the highlights. What are you excited about throughout your day? Take us through your program on the captains. That's going to be probably pretty dynamic in the chat too. >> Yeah, so I'm sure we're going to have lots of, stuff going on in chat. So no cLancaerns there about, having crickets in the chat. But we're going to be basically starting the day with two of my good Docker captain friends, (murmurs) and Laura Taco. And we're going to basically start you out and at the end of this keynote, at the end of this hour and we're going to get you going and then you can maybe jump out and go to take some sessions. Maybe there's some stuff you want to check out and other sessions that you want to chat and talk with the instructors, the speakers there, and then you're going to come back to us, right? Or go over, check out the interviews. So the idea is you're hopping back and forth and throughout the day we're basically changing out every hour. We're not just changing out the guests basically, but we're also changing out the topics that we can cover because different guests will have different expertise. We're going to have some special guests in from Microsoft, talk about some of the cool stuff going on there, and basically it's captains all day long. And if you've been on my YouTube live show you've watched that, you've seen a lot of the guests we have on there. I'm lucky to just hang out with all these really awesome people around the world, so it's going to be fun. >> Awesome and the content again has been preserved. You guys had a great session on call for paper sessions. Jenny, this is good stuff. What other things can people do to make it interesting? Obviously we're looking for suggestions. Feel free to chirp on Twitter about ideas that can be new. But you guys got some surprises. There's some selfies, what else? What's going on? Any secret, surprises throughout the day. >> There are secret surprises throughout the day. You'll need to pay attention to the keynotes. Bret will have giveaways. I know our wonderful sponsors have giveaways planned as well in their sessions. Hopefully right you feel conflicted about what you're going to attend. So do know that everything is recorded and will be available on demand afterwards so you can catch anything that you miss. Most of them will be available right after they stream the initial time. >> All right, great stuff, so they've got the Docker selfie. So the Docker selfies, the hashtag is just DockerCon hashtag DockerCon. If you feel like you want to add some of the hashtag no problem, check out the sessions. You can pop in and out of the captains is kind of the cool kids are going to be hanging out with Bret and then all they'll knowledge and learning. Don't miss the keynote, the keynote should be solid. We've got chain Governor from red monk delivering a keynote. I'll be interviewing him live after his keynote. So stay with us. And again, check out the interactive calendar. All you got to do is look at the calendar and click on the session you want. You'll jump right in. Hop around, give us feedback. We're doing our best. Bret, any final thoughts on what you want to share to the community around, what you got going on the virtual event, just random thoughts? >> Yeah, so sorry we can't all be together in the same physical place. But the coolest thing about as business online, is that we actually get to involve everyone, so as long as you have a computer and internet, you can actually attend DockerCon if you've never been to one before. So we're trying to recreate that experience online. Like Jenny said, the code of conduct is important. So, we're all in this together with the chat, so try to be nice in there. These are all real humans that, have feelings just like me. So let's try to keep it cool. And, over in the Catherine's channel we'll be taking your questions and maybe playing some music, playing some games, giving away some free stuff, while you're, in between sessions learning, oh yeah. >> And I got to say props to your rig. You've got an amazing setup there, Bret. I love what your show, you do. It's really bad ass and kick ass. So great stuff. Jenny sponsors ecosystem response to this event has been phenomenal. The attendance 67,000. We're seeing a surge of people hitting the site now. So if you're not getting in, just, Wade's going, we're going to crank through the queue, but the sponsors on the ecosystem really delivered on the content side and also the sport. You want to share a few shout outs on the sponsors who really kind of helped make this happen. >> Yeah, so definitely make sure you check out the sponsor pages and you go, each page is the actual content that they will be delivering. So they are delivering great content to you. So you can learn and a huge thank you to our platinum and gold authors. >> Awesome, well I got to say, I'm super impressed. I'm looking forward to the Microsoft Amazon sessions, which are going to be good. And there's a couple of great customer sessions there. I tweeted this out last night and let them get you guys' reaction to this because there's been a lot of talk around the COVID crisis that we're in, but there's also a positive upshot to this is Cambridge and explosion of developers that are going to be building new apps. And I said, you know, apps aren't going to just change the world, they're going to save the world. So a lot of the theme here is the impact that developers are having right now in the current situation. If we get the goodness of compose and all the things going on in Docker and the relationships, this real impact happening with the developer community. And it's pretty evident in the program and some of the talks and some of the examples. how containers and microservices are certainly changing the world and helping save the world, your thoughts. >> Like you said, a number of sessions and interviews in the program today that really dive into that. And even particularly around COVID, Clement Beyondo is sharing his company's experience, from being able to continue operations in Italy when they were completely shut down beginning of March. We have also in theCUBE channel several interviews about from the national Institute of health and precision cancer medicine at the end of the day. And you just can really see how containerization and developers are moving in industry and really humanity forward because of what they're able to build and create, with advances in technology. >> Yeah and the first responders and these days is developers. Bret compose is getting a lot of traction on Twitter. I can see some buzz already building up. There's huge traction with compose, just the ease of use and almost a call for arms for integrating into all the system language libraries, I mean, what's going on with compose? I mean, what's the captain say about this? I mean, it seems to be really tracking in terms of demand and interest. >> I think we're over 700,000 composed files on GitHub. So it's definitely beyond just the standard Docker run commands. It's definitely the next tool that people use to run containers. Just by having that we just buy, and that's not even counting. I mean that's just counting the files that are named Docker compose YAML. So I'm sure a lot of you out there have created a YAML file to manage your local containers or even on a server with Docker compose. And the nice thing is is Docker is doubling down on that. So we've gotten some news recently, from them about what they want to do with opening the spec up, getting more companies involved because compose is already gathered so much interest from the community. You know, AWS has importers, there's Kubernetes importers for it. So there's more stuff coming and we might just see something here in a few minutes. >> All right, well let's get into the keynote guys, jump into the keynote. If you missing anything, come back to the stream, check out the sessions, check out the calendar. Let's go, let's have a great time. Have some fun, thanks and enjoy the rest of the day we'll see you soon. (upbeat music) (upbeat music) >> Okay, what is the name of that Whale? >> Molly. >> And what is the name of this Whale? >> Mobby. >> That's right, dad's got to go, thanks bud. >> Bye. >> Bye. Hi, I'm Scott Johnson, CEO of Docker and welcome to DockerCon 2020. This year DockerCon is an all virtual event with more than 60,000 members of the Docker Community joining from around the world. And with the global shelter in place policies, we're excited to offer a unifying, inclusive virtual community event in which anyone and everyone can participate from their home. As a company, Docker has been through a lot of changes since our last DockerCon last year. The most important starting last November, is our refocusing 100% on developers and development teams. As part of that refocusing, one of the big challenges we've been working on, is how to help development teams quickly and efficiently get their app from code to cloud And wouldn't it be cool, if developers could quickly deploy to the cloud right from their local environment with the commands and workflow they already know. We're excited to give you a sneak preview of what we've been working on. And rather than slides, we thought we jumped right into the product. And joining me demonstrate some of these cool new features, is enclave your DACA. One of our engineers here at Docker working on Docker compose. Hello Lanca. >> Hello. >> We're going to show how an application development team collaborates using Docker desktop and Docker hub. And then deploys the app directly from the Docker command line to the clouds in just two commands. A development team would use this to quickly share functional changes of their app with the product management team, with beta testers or other development teams. Let's go ahead and take a look at our app. Now, this is a web app, that randomly pulls words from the database, and assembles them into sentences. You can see it's a pretty typical three tier application with each tier implemented in its own container. We have a front end web service, a middle tier, which implements the logic to randomly pull the words from the database and assemble them and a backend database. And here you can see the database uses the Postgres official image from Docker hub. Now let's first run the app locally using Docker command line and the Docker engine in Docker desktop. We'll do a Doc compose up and you can see that it's pulling the containers from our Docker organization account. Wordsmith, inc. Now that it's up. Let's go ahead and look at local host and we'll confirm that the application is functioning as desired. So there's one sentence, let's pull and now you and you can indeed see that we are pulling random words and assembling into sentences. Now you can also see though that the look and feel is a bit dated. And so Lanca is going to show us how easy it is to make changes and share them with the rest of the team. Lanca, over to you. >> Thank you, so I have, the source code of our application on my machine and I have updated it with the latest team from DockerCon 2020. So before committing the code, I'm going to build the application locally and run it, to verify that indeed the changes are good. So I'm going to build with Docker compose the image for the web service. Now that the image has been built, I'm going to deploy it locally. Wait to compose up. We can now check the dashboard in a Docker desktop that indeed our containers are up and running, and we can access, we can open in the web browser, the end point for the web service. So as we can see, we have the latest changes in for our application. So as you can see, the application has been updated successfully. So now, I'm going to push the image that I have just built to my organization's shared repository on Docker hub. So I can do this with Docker compose push web. Now that the image has been updated in the Docker hub repository, or my teammates can access it and check the changes. >> Excellent, well, thank you Lanca. Now of course, in these times, video conferencing is the new normal, and as great as it is, video conferencing does not allow users to actually test the application. And so, to allow us to have our app be accessible by others outside organizations such as beta testers or others, let's go ahead and deploy to the cloud. >> Sure we, can do this by employing a context. A Docker context, is a mechanism that we can use to target different platforms for deploying containers. The context we hold, information as the endpoint for the platform, and also how to authenticate to it. So I'm going to list the context that I have set locally. As you can see, I'm currently using the default context that is pointing to my local Docker engine. So all the commands that I have issued so far, we're targeting my local engine. Now, in order to deploy the application on a cloud. I have an account in the Azure Cloud, where I have no resource running currently, and I have created for this account, dedicated context that will hold the information on how to connect it to it. So now all I need to do, is to switch to this context, with Docker context use, and the name of my cloud context. So all the commands that I'm going to run, from now on, are going to target the cloud platform. So we can also check very, more simpler, in a simpler way we can check the running containers with Docker PS. So as we see no container is running in my cloud account. Now to deploy the application, all I need to do is to run a Docker compose up. And this will trigger the deployment of my application. >> Thanks Lanca. Now notice that Lanca did not have to move the composed file from Docker desktop to Azure. Notice you have to make any changes to the Docker compose file, and nor did she change any of the containers that she and I were using locally in our local environments. So the same composed file, same images, run locally and upon Azure without changes. While the app is deploying to Azure, let's highlight some of the features in Docker hub that helps teams with remote first collaboration. So first, here's our team's account where it (murmurs) and you can see the updated container sentences web that Lanca just pushed a couple of minutes ago. As far as collaboration, we can add members using their Docker ID or their email, and then we can organize them into different teams depending on their role in the application development process. So and then Lancae they're organized into different teams, we can assign them permissions, so that teams can work in parallel without stepping on each other's changes accidentally. For example, we'll give the engineering team full read, write access, whereas the product management team will go ahead and just give read only access. So this role based access controls, is just one of the many features in Docker hub that allows teams to collaboratively and quickly develop applications. Okay Lanca, how's our app doing? >> Our app has been successfully deployed to the cloud. So, we can easily check either the Azure portal to verify the containers running for it or simpler we can run a Docker PS again to get the list with the containers that have been deployed for it. In the output from the Docker PS, we can see an end point that we can use to access our application in the web browser. So we can see the application running in clouds. It's really up to date and now we can take this particular endpoint and share it within our organization such that anybody can have a look at it. >> That's cool Onka. We showed how we can deploy an app to the cloud in minutes and just two commands, and using commands that Docker users already know, thanks so much. In that sneak preview, you saw a team developing an app collaboratively, with a tool chain that includes Docker desktop and Docker hub. And simply by switching Docker context from their local environment to the cloud, deploy that app to the cloud, to Azure without leaving the command line using Docker commands they already know. And in doing so, really simplifying for development team, getting their app from code to cloud. And just as important, what you did not see, was a lot of complexity. You did not see cloud specific interfaces, user management or security. You did not see us having to provision and configure compute networking and storage resources in the cloud. And you did not see infrastructure specific application changes to either the composed file or the Docker images. And by simplifying a way that complexity, these new features help application DevOps teams, quickly iterate and get their ideas, their apps from code to cloud, and helping development teams, build share and run great applications, is what Docker is all about. A Docker is able to simplify for development teams getting their app from code to cloud quickly as a result of standards, products and ecosystem partners. It starts with open standards for applications and application artifacts, and active open source communities around those standards to ensure portability and choice. Then as you saw in the demo, the Docker experience delivered by Docker desktop and Docker hub, simplifies a team's collaborative development of applications, and together with ecosystem partners provides every stage of an application development tool chain. For example, deploying applications to the cloud in two commands. What you saw on the demo, well that's an extension of our strategic partnership with Microsoft, which we announced yesterday. And you can learn more about our partnership from Amanda Silver from Microsoft later today, right here at DockerCon. Another tool chain stage, the capability to scan applications for security and vulnerabilities, as a result of our partnership with Sneak, which we announced last week. You can learn more about that partnership from Peter McKay, CEO Sneak, again later today, right here at DockerCon. A third example, development team can automate the build of container images upon a simple get push, as a result of Docker hub integrations with GitHub and Alaska and Bitbucket. As a final example of Docker and the ecosystem helping teams quickly build applications, together with our ISV partners. We offer in Docker hub over 500 official and verified publisher images of ready to run Dockerized application components such as databases, load balancers, programming languages, and much more. Of course, none of this happens without people. And I would like to take a moment to thank four groups of people in particular. First, the Docker team, past and present. We've had a challenging 12 months including a restructuring and then a global pandemic, and yet their support for each other, and their passion for the product, this community and our customers has never been stronger. We think our community, Docker wouldn't be Docker without you, and whether you're one of the 50 Docker captains, they're almost 400 meetup organizers, the thousands of contributors and maintainers. Every day you show up, you give back, you teach new support. We thank our users, more than six and a half million developers who have built more than 7 million applications and are then sharing those applications through Docker hub at a rate of more than one and a half billion poles per week. Those apps are then run, are more than 44 million Docker engines. And finally, we thank our customers, the over 18,000 docker subscribers, both individual developers and development teams from startups to large organizations, 60% of which are outside the United States. And they spend every industry vertical, from media, to entertainment to manufacturing. healthcare and much more. Thank you. Now looking forward, given these unprecedented times, we would like to offer a challenge. While it would be easy to feel helpless and miss this global pandemic, the challenge is for us as individuals and as a community to instead see and grasp the tremendous opportunities before us to be forces for good. For starters, look no further than the pandemic itself, in the fight against this global disaster, applications and data are playing a critical role, and the Docker Community quickly recognize this and rose to the challenge. There are over 600 COVID-19 related publicly available projects on Docker hub today, from data processing to genome analytics to data visualization folding at home. The distributed computing project for simulating protein dynamics, is also available on Docker hub, and it uses spirit compute capacity to analyze COVID-19 proteins to aid in the design of new therapies. And right here at DockerCon, you can hear how Clemente Biondo and his company engineering in Gagne area Informatica are using Docker in the fight with COVID-19 in Italy every day. Now, in addition to fighting the pandemic directly, as a community, we also have an opportunity to bridge the disruption the pandemic is wreaking. It's impacting us at work and at home in every country around the world and every aspect of our lives. For example, many of you have a student at home, whose world is going to be very different when they returned to school. As employees, all of us have experienced the stresses from working from home as well as many of the benefits and in fact 75% of us say that going forward, we're going to continue to work from home at least occasionally. And of course one of the biggest disruptions has been job losses, over 35 million in the United States alone. And we know that's affected many of you. And yet your skills are in such demand and so important now more than ever. And that's why here at DockerCon, we want to try to do our part to help, and we're promoting this hashtag on Twitter, hashtag DockerCon jobs, where job seekers and those offering jobs can reach out to one another and connect. Now, pandemics disruption is accelerating the shift of more and more of our time, our priorities, our dollars from offline to online to hybrid, and even online only ways of living. We need to find new ways to collaborate, new approaches to engage customers, new modes for education and much more. And what is going to fill the needs created by this acceleration from offline, online? New applications. And it's this need, this demand for all these new applications that represents a great opportunity for the Docker community of developers. The world needs us, needs you developers now more than ever. So let's seize this moment. Let us in our teams, go build share and run great new applications. Thank you for joining today. And let's have a great DockerCon. >> Okay, welcome back to the DockerCon studio headquarters in your hosts, Jenny Burcio and myself John Furrier. u@farrier on Twitter. If you want to tweet me anything @DockerCon as well, share what you're thinking. Great keynote there from Scott CEO. Jenny, demo DockerCon jobs, some highlights there from Scott. Yeah, I love the intro. It's okay I'm about to do the keynote. The little green room comes on, makes it human. We're all trying to survive-- >> Let me answer the reality of what we are all doing with right now. I had to ask my kids to leave though or they would crash the whole stream but yes, we have a great community, a large community gather gathered here today, and we do want to take the opportunity for those that are looking for jobs, are hiring, to share with the hashtag DockerCon jobs. In addition, we want to support direct health care workers, and Bret Fisher and the captains will be running a all day charity stream on the captain's channel. Go there and you'll get the link to donate to directrelief.org which is a California based nonprofit, delivering and aid and supporting health care workers globally response to the COVID-19 crisis. >> Okay, if you jumping into the stream, I'm John Farrie with Jenny Webby, your hosts all day today throughout DockerCon. It's a packed house of great content. You have a main stream, theCUBE which is the mainstream that we'll be promoting a lot of cube interviews. But check out the 40 plus sessions underneath in the interactive calendar on dockercon.com site. Check it out, they're going to be live on a clock. So if you want to participate in real time in the chat, jump into your session on the track of your choice and participate with the folks in there chatting. If you miss it, it's going to go right on demand right after sort of all content will be immediately be available. So make sure you check it out. Docker selfie is a hashtag. Take a selfie, share it. Docker hashtag Docker jobs. If you're looking for a job or have openings, please share with the community and of course give us feedback on what you can do. We got James Governor, the keynote coming up next. He's with Red monk. Not afraid to share his opinion on open source on what companies should be doing, and also the evolution of this Cambrin explosion of apps that are going to be coming as we come out of this post pandemic world. A lot of people are thinking about this, the crisis and following through. So stay with us for more and more coverage. Jenny, favorite sessions on your mind for people to pay attention to that they should (murmurs)? >> I just want to address a few things that continue to come up in the chat sessions, especially breakout sessions after they play live and the speakers in chat with you, those go on demand, they are recorded, you will be able to access them. Also, if the screen is too small, there is the button to expand full screen, and different quality levels for the video that you can choose on your end. All the breakout sessions also have closed captioning, so please if you would like to read along, turn that on so you can, stay with the sessions. We have some great sessions, kicking off right at 10:00 a.m, getting started with Docker. We have a full track really in the how to enhance on that you should check out devs in action, hear what other people are doing and then of course our sponsors are delivering great content to you all day long. >> Tons of content. It's all available. They'll always be up always on at large scale. Thanks for watching. Now we got James Governor, the keynote. He's with Red Monk, the analyst firm and has been tracking open source for many generations. He's been doing amazing work. Watch his great keynote. I'm going to be interviewing him live right after. So stay with us and enjoy the rest of the day. We'll see you back shortly. (upbeat music) >> Hi, I'm James Governor, one of the co-founders of a company called RedMonk. We're an industry research firm focusing on developer led technology adoption. So that's I guess why Docker invited me to DockerCon 2020 to talk about some trends that we're seeing in the world of work and software development. So Monk Chips, that's who I am. I spent a lot of time on Twitter. It's a great research tool. It's a great way to find out what's going on with keep track of, as I say, there's people that we value so highly software developers, engineers and practitioners. So when I started talking to Docker about this event and it was pre Rhona, should we say, the idea of a crowd wasn't a scary thing, but today you see something like this, it makes you feel uncomfortable. This is not a place that I want to be. I'm pretty sure it's a place you don't want to be. And you know, to that end, I think it's interesting quote by Ellen Powell, she says, "Work from home is now just work" And we're going to see more and more of that. Organizations aren't feeling the same way they did about work before. Who all these people? Who is my cLancaern? So GitHub says has 50 million developers right on its network. Now, one of the things I think is most interesting, it's not that it has 50 million developers. Perhaps that's a proxy for number of developers worldwide. But quite frankly, a lot of those accounts, there's all kinds of people there. They're just Selena's. There are data engineers, there are data scientists, there are product managers, there were tech marketers. It's a big, big community and it goes way beyond just software developers itself. Frankly for me, I'd probably be saying there's more like 20 to 25 million developers worldwide, but GitHub knows a lot about the world of code. So what else do they know? One of the things they know is that world of code software and opensource, is becoming increasingly global. I get so excited about this stuff. The idea that there are these different software communities around the planet where we're seeing massive expansions in terms of things like open source. Great example is Nigeria. So Nigeria more than 200 million people, right? The energy there in terms of events, in terms of learning, in terms of teaching, in terms of the desire to code, the desire to launch businesses, desire to be part of a global software community is just so exciting. And you know, these, this sort of energy is not just in Nigeria, it's in other countries in Africa, it's happening in Egypt. It's happening around the world. This energy is something that's super interesting to me. We need to think about that. We've got global that we need to solve. And software is going to be a big part of that. At the moment, we can talk about other countries, but what about frankly the gender gap, the gender issue that, you know, from 1984 onwards, the number of women taking computer science degrees began to, not track but to create in comparison to what men were doing. The tech industry is way too male focused, there are men that are dominant, it's not welcoming, we haven't found ways to have those pathways and frankly to drive inclusion. And the women I know in tech, have to deal with the massively disproportionate amount of stress and things like online networks. But talking about online networks and talking about a better way of living, I was really excited by get up satellite recently, was a fantastic demo by Alison McMillan and she did a demo of a code spaces. So code spaces is Microsoft online ID, new platform that they've built. And online IDs, we're never quite sure, you know, plenty of people still out there just using the max. But, visual studio code has been a big success. And so this idea of moving to one online IDE, it's been around that for awhile. What they did was just make really tight integration. So you're in your GitHub repo and just be able to create a development environment with effectively one click, getting rid of all of the act shaving, making it super easy. And what I loved was it the demo, what Ali's like, yeah cause this is great. One of my kids are having a nap, I can just start (murmurs) and I don't have to sort out all the rest of it. And to me that was amazing. It was like productivity as inclusion. I'm here was a senior director at GitHub. They're doing this amazing work and then making this clear statement about being a parent. And I think that was fantastic. Because that's what, to me, importantly just working from home, which has been so challenging for so many of us, began to open up new possibilities, and frankly exciting possibilities. So Alley's also got a podcast parent-driven development, which I think is super important. Because this is about men and women rule in this together show parenting is a team sport, same as software development. And the idea that we should be thinking about, how to be more productive, is super important to me. So I want to talk a bit about developer culture and how it led to social media. Because you know, your social media, we're in this ad bomb stage now. It's TikTok, it's like exercise, people doing incredible back flips and stuff like that. Doing a bunch of dancing. We've had the world of sharing cat gifts, Facebook, we sort of see social media is I think a phenomenon in its own right. Whereas the me, I think it's interesting because it's its progenitors, where did it come from? So here's (murmurs) So 1971, one of the features in the emergency management information system, that he built, which it's topical, it was for medical tracking medical information as well, medical emergencies, included a bulletin board system. So that it could keep track of what people were doing on a team and make sure that they were collaborating effectively, boom! That was the start of something big, obviously. Another day I think is worth looking at 1983, Sorania Pullman, spanning tree protocol. So at DEC, they were very good at distributed systems. And the idea was that you can have a distributed system and so much of the internet working that we do today was based on radius work. And then it showed that basically, you could span out a huge network so that everyone could collaborate. That is incredibly exciting in terms of the trends, that I'm talking about. So then let's look at 1988, you've got IRC. IRC what developer has not used IRC, right. Well, I guess maybe some of the other ones might not have. But I don't know if we're post IRC yet, but (murmurs) at a finished university, really nailed it with IRC as a platform that people could communicate effectively with. And then we go into like 1991. So we've had IRC, we've had finished universities, doing a lot of really fantastic work about collaboration. And I don't think it was necessarily an accident that this is where the line is twofold, announced Linux. So Linux was a wonderfully packaged, idea in terms of we're going to take this Unix thing. And when I say package, what a package was the idea that we could collaborate on software. So, it may have just been the work of one person, but clearly what made it important, made it interesting, was finding a social networking pattern, for software development so that everybody could work on something at scale. That was really, I think, fundamental and foundational. Now I think it's important, We're going to talk about Linus, to talk about some things that are not good about software culture, not good about open source culture, not good about hacker culture. And that's where I'm going to talk about code of conduct. We have not been welcoming to new people. We got the acronyms, JFTI, We call people news, that's super unhelpful. We've got to find ways to be more welcoming and more self-sustaining in our communities, because otherwise communities will fail. And I'd like to thank everyone that has a code of conduct and has encouraged others to have codes of conduct. We need to have codes of conduct that are enforced to ensure that we have better diversity at our events. And that's what women, underrepresented minorities, all different kinds of people need to be well looked off to and be in safe and inclusive spaces. And that's the online events. But of course it's also for all of our activities offline. So Linus, as I say, I'm not the most charming of characters at all time, but he has done some amazing technology. So we got to like 2005 the creation of GIT. Not necessarily the distributed version control system that would win. But there was some interesting principles there, and they'd come out of the work that he had done in terms of trying to build and sustain the Linux code base. So it was very much based on experience. He had an itch that he needed to scratch and there was a community that was this building, this thing. So what was going to be the option, came up with Git foundational to another huge wave of social change, frankly get to logical awesome. April 20 April, 2008 GitHub, right? GiHub comes up, they've looked at Git, they've packaged it up, they found a way to make it consumable so the teams could use it and really begin to take advantage of the power of that distributed version control model. Now, ironically enough, of course they centralized the service in doing so. So we have a single point of failure on GitHub. But on the other hand, the notion of the poll request, the primitives that they established and made usable by people, that changed everything in terms of software development. I think another one that I'd really like to look at is Slack. So Slack is a huge success used by all different kinds of businesses. But it began specifically as a pivot from a company called Glitch. It was a game company and they still wanted, a tool internally that was better than IRC. So they built out something that later became Slack. So Slack 2014, is established as a company and basically it was this Slack fit software engineering. The focus on automation, the conversational aspects, the asynchronous aspects. It really pulled things together in a way that was interesting to software developers. And I think we've seen this pattern in the world, frankly, of the last few years. Software developers are influences. So Slack first used by the engineering teams, later used by everybody. And arguably you could say the same thing actually happened with Apple. Apple was mainstreamed by developers adopting that platform. Get to 2013, boom again, Solomon Hikes, Docker, right? So Docker was, I mean containers were not new, they were just super hard to use. People found it difficult technology, it was Easter Terek. It wasn't something that they could fully understand. Solomon did an incredible job of understanding how containers could fit into modern developer workflows. So if we think about immutable images, if we think about the ability to have everything required in the package where you are, it really tied into what people were trying to do with CICD, tied into microservices. And certainly the notion of sort of display usability Docker nailed that, and I guess from this conference, at least the rest is history. So I want to talk a little bit about, scratching the itch. And particularly what has become, I call it the developer authentic. So let's go into dark mode now. I've talked about developers laying out these foundations and frameworks that, the mainstream, frankly now my son, he's 14, he (murmurs) at me if I don't have dark mode on in an application. And it's this notion that developers, they have an aesthetic, it does get adopted I mean it's quite often jokey. One of the things we've seen in the really successful platforms like GitHub, Docker, NPM, let's look at GitHub. Let's look at over that Playfulness. I think was really interesting. And that changes the world of work, right? So we've got the world of work which can be buttoned up, which can be somewhat tight. I think both of those companies were really influential, in thinking that software development, which is a profession, it's also something that can and is fun. And I think about how can we make it more fun? How can we develop better applications together? Takes me to, if we think about Docker talking about build, share and run, for me the key word is share, because development has to be a team sport. It needs to be sharing. It needs to be kind and it needs to bring together people to do more effective work. Because that's what it's all about, doing effective work. If you think about zoom, it's a proxy for collaboration in terms of its value. So we've got all of these airlines and frankly, add up that their share that add up their total value. It's currently less than Zoom. So video conferencing has become so much of how we live now on a consumer basis. But certainly from a business to business perspective. I want to talk about how we live now. I want to think about like, what will come out all of this traumatic and it is incredibly traumatic time? I'd like to say I'm very privileged. I can work from home. So thank you to all the frontline workers that are out there that they're not in that position. But overall what I'm really thinking about, there's some things that will come out of this that will benefit us as a culture. Looking at cities like Paris, Milan, London, New York, putting a new cycling infrastructure, so that people can social distance and travel outside because they don't feel comfortable on public transport. I think sort of amazing widening pavements or we can't do that. All these cities have done it literally overnight. This sort of changes is exciting. And what does come off that like, oh there are some positive aspects of the current issues that we face. So I've got a conference or I've got a community that may and some of those, I've been working on. So Katie from HashiCorp and Carla from container solutions basically about, look, what will the world look like in developer relations? Can we have developer relations without the air miles? 'Cause developer advocates, they do too much travel ends up, you know, burning them out, develop relations. People don't like to say no. They may have bosses that say, you know, I was like, Oh that corporates went great. Now we're going to roll it out worldwide to 47 cities. That's stuff is terrible. It's terrible from a personal perspective, it's really terrible from an environmental perspective. We need to travel less. Virtual events are crushing it. Microsoft just at build, right? Normally that'd be just over 10,000 people, they had 245,000 plus registrations. 40,000 of them in the last day, right? Red Hat summit, 80,000 people, IBM think 90,000 people, GitHub Crushed it as well. Like this is a more inclusive way people can dip in. They can be from all around the world. I mentioned Nigeria and how fantastic it is. Very often Nigerian developers and advocates find it hard to get visas. Why should they be shut out of events? Events are going to start to become remote first because frankly, look at it, if you're turning in those kinds of numbers, and Microsoft was already doing great online events, but they absolutely nailed it. They're going to have to ask some serious questions about why everybody should get back on a plane again. So if you're going to do remote, you've got to be intentional about it. It's one thing I've learned some exciting about GitLab. GitLab's culture is amazing. Everything is documented, everything is public, everything is transparent. Think that really clear and if you look at their principles, everything, you can't have implicit collaboration models. Everything needs to be documented and explicit, so that anyone can work anywhere and they can still be part of the team. Remote first is where we're at now, Coinbase, Shopify, even Barkley says the not going to go back to having everybody in offices in the way they used to. This is a fundamental shift. And I think it's got significant implications for all industries, but definitely for software development. Here's the thing, the last 20 years were about distributed computing, microservices, the cloud, we've got pretty good at that. The next 20 years will be about distributed work. We can't have everybody living in San Francisco and London and Berlin. The talent is distributed, the talent is elsewhere. So how are we going to build tools? Who is going to scratch that itch to build tools to make them more effective? Who's building the next generation of apps, you are, thanks.

>> announcer: From around the globe. It's the theCUBE with digital coverage of DockerCon live 2020. Brought to you by Docker and its ecosystem partners. >> Welcome back to theCUBE coverage here at the DockerCon virtual headquarters, anchor desks here in the Palo Alto Studios were quarantined in this virtual event of DockerCon. I'm John Furrier, host along with Jenny Bertuccio, John Kreisa, Peter McKee, other folks who are moderating and weaving in and out of the sessions. But here we have a live sessions with Justin Graham, Vice President of the Products group at Docker. Justin, thanks for coming in DockerCon virtual '20. >> Absolutely, happy to be here from my home office in Seattle, Washington where it is almost sunny. >> You had a great backdrop traveler saying in the chat you got a bandwidth, a lot of bandwidth there. Looking good, some island. What a day for Docker global event. 77,000 people registered. It's just been an awesome party. >> It's been great, I could hardly sleep last night. I was up at 5:00 this morning. I was telling my son about it at breakfast. I interrupted his Zoom school. And he talked a little bit about it, so it's been awesome. I've been waiting for this interview slot for the most of the day. >> So yeah, I got to tell the kids to get off, download those gigabytes of new game updates and get off Netflix, I hear you. But you got good bandwidth. Let's get into it, I love your position. VP of Product at a company that's super technical, a lot of software, a lot of cloud. You've got a good view of the landscape of what the current situation is relative to the product, the deals that are going on with this new announced here, sneak Microsoft expansion, multiple clouds as well as the roadmap and community interaction. So you got a lot going on, you've got your fingers in all the action. When you get the keys to the kingdom, as we say in the product side of things, what's the story today from your perspective around DockerCon? What's the most important thing people should know about of what's going on with this new Docker? Obviously, ease of use, we've heard a lot about. What's going on? >> So I'll start with people. We are hyper focused on helping developers and development teams build and ship applications. That's what we're focused on. That's what we wake up every day thinking about. And we double click on that a minute in terms of what that means. If you think about where source control ends and having a running application on some production compute in the Cloud on the other end, there's a whole lot that needs to happen in the middle of those two things. And we hear from our development community and we see from those folks, there's a lot of complexity and choices and options and things in the middle there. And we really want to help streamline the creation of those pipelines to get those apps moving to production as fastly, as quickly as possible. >> And you can see it in some of the results and some of the sessions, one session coming up at around four, around how pipelining with Docker help increase the problem solving around curing cancer, really solving, saving people's lives to the front lines with COVID 19 to business value. So you seeing, again Docker coming back into the fold relative to the simple value proposition of making things super easy for developers, but on top of the mega trend of microservices. So, outside of some of these awesome sessions with his learning, the hardcore sessions here at DockerCon around microservices from monitoring, you name it, not a trivial thing cause you've got stateless and state, all kinds of new things are going on with multiple clouds. So not an easy-- >> No. >> road to kind of grok or understand you have to manage that. What are people paying attention to? What is happening? I think, first off I'll say, one of the things that I'm super passionate about is increasing access to technology, so the greatest and best ideas can get bubbled up to the top and expose no matter where they come from, whom they come from, et cetera. And I think one of the things that makes that harder, that makes that complex is just how much developers need to understand or even emerging developers need to understand. Just to even get started. Languages, IDEs, packaging, building where do you ship to? If you pick a certain powder end point, you have to understand networking and storage and identity models are just so much you have to absorb. So we're hyper focused on how can we make that complex super easy. And these are all the things that we get asked questions on. And we get interacted with on our public roadmap in other places to help with. So that's the biggest things that you're going to see coming out of Docker starting now and moving forward. We'll be serving that end. >> Let's talk about some of the new execution successes you guys had. Honestly, Snyk is security shifting left, that's a major, I think a killer win for Snyk. Obviously, getting access to millions of developers use Docker and vice versa. Into the shifting left, you get to security in that workflow piece. Microsoft expanding relationship's interesting as well because Microsoft's got a robust tech developer ecosystem. They have their own tools. So, you see these symbiotic relationship with Docker, again, coming into the fold where there's a lot of working together going on. Explain that meaning, what does that mean? >> So you're on the back of the refocus Docker in our hyperfocus on developers and development teams, one of the core tenants of the how. So before that was the what. This is the how we're going to go do it. Is by partnering with the ecosystem as much as possible and bringing the best of breed in front of developers in a way that they can most easily consume. So if you take the Snyk partnership that was just a match, a match made in developer dopamine as a Sean Connolly, would say. We're hyper focused on developers and development teams and Snyk is also hyperfocused on making it as easy as possible for developers and development teams to stay secure ship, fast and stay secure. So it really just matched up super well. And then if you think, "Well, how do we even get there in the first place?" Well, we launched our public roadmap a few months ago, which was a first that Docker has ever done. And one of the first things that comes onto that public roadmap is image vulnerability scanning. For Docker, at that time it was really just focused on Docker Hub in terms of how it came through the roadmap. It got up voted a bunch, there has been some interaction and then we thought, "Well, why just like checking that box isn't enough," right? It's just checking the box. What can we do that really brings sort of the promise of the Docker experience to something like this? And Sneak was an immediate thought, in that respect. And we just really got in touch with them and we just saw eye to eye almost immediately. And then off off the rest went. The second piece of it was really around, well why just do it in Docker Hub? What about Docker Desktop? It's downloaded 80,000 times a week and it's got 2.2 million active installations on a weekly basis. What about those folks? So we decided to raise the bar again and say, "Hey, let's make sure that this partnership includes "not only Docker Hub but Docker Desktop, so you'll be able, when we launch this, to scan your images locally on Docker Desktop. >> Awesome, I see getting some phone calls and then you got to hit this, hit the end button real quick. I saw that in there. I've got an interesting chat I want to just kind of lighten things up a little bit from Brian Stevenson. He says, "Justin, what glasses are those?" (Justin laughing) So he wants to know what kind of glasses you're wearing. >> They're glasses that I think signal that I turned 40 last year. >> (laughs) I'd say it's for your gaming environments, the blue light glasses. >> But I'm not going to say where they came from because it's probably not going to engender a bunch of positive good. But they're nice glasses. They help me see the computer screen and make sure that I'm not a bad fingering my CLI commands >> Well as old guys need the glasses, certainly I do. Speaking of old and young, this brought up a conversation since that came up, I'll just quickly riff into this cause I think it's interesting, Kelsey Hightower, during the innovation panel talked about how the developers and people want to just do applications, someone to get under the hood, up and down the stack. I was riffing with John Chrysler, around kind of the new generation, the kids coming in, the young guns, they all this goodness at their disposal. They didn't have to load Linux on a desktop and Rack and Stack servers all that good stuff. So it's so much more capable today. And so this speaks to the modern era and the expansion overall of opensource and the expansion of the people involved, new expectations and new experiences are required. So as a product person, how do you think about that? Because you don't want to just build for the old, you got to build for the new as well as the experience changes and expectations are different. What's your thoughts around that? >> Yeah, I think about sort of my start in this industry as a really good answer to that. I mean, I remember as a kid, I think I asked for a computer for every birthday and Christmas from when I was six, until I got one given to me by a friend's parents in 1994, on my way off to boarding school. And so it took that long just for me to get a computer into my hands. And then when I was in school there wasn't any role sort of Computer Science or coding courses until my senior year. And then I had to go to an Engineering School at Rensselaer city to sort of get that experience at the time. I mean, just to even get into this industry and learn how to code was just, I mean, so many things had to go my way. And then Microsoft hired me out of college. Another thing that sort of fell my way. So this work that we're doing is just so important because I worked hard, but I had a lot of luck. But not everybody's going to have some of that, right? Have that luck. So how can we make it just as easy as possible for folks to get started wherever you are. If you have a family and you're working another full time job, can you spend a few hours at night learning Docker? We can help you with that. Download Docker Desktop. We have tutorials, we have great docs, we have great captains who teach courses. So everything we're doing is sort of in service of that vision and that democratization of getting into the ideas. And I love what Kelsey, said in terms of, let's stop talking about the tech and let's stop talking about what folks can do with the tech. And that's very, very poignant. So we're really working on like, we'll take care of all the complexity behind the scenes and all of the VMs and the launching of containers and the network. We'll try to help take care of all that complexity behind the curtain so that you can just focus on getting your idea built as a developer. >> Yeah, and you mentioned Kelsey, again. He got a great story about his daughter and Serverless and I was joking on Twitter that his daughter convinced them that Serverless is great. Of course we know that Kelsey already loves Serverless. But he's pointing out this developer dopamine. He didn't say that's Shawn's word, but that's really what his daughter wanted to do is show her friends a website that she built, not get into, "Hey look, I just did a Kubernetes cluster." I mean it's not like... But pick your swim lane. This is what it's all about now. >> Yeah, I hope my son never has to understand what a service mesh is or proxy is. Right? >> Yeah. >> I just hope he just learn the language and just learns how to bring an idea to life and all the rest of it is just behind me here. >> When he said I had a parenting moment, I thought he's going to say something like that. Like, "Oh my kid did it." No, I had to describe whether it's a low level data structure or (laughs) just use Serverless. Shifting gears on the product roadmap for Docker, can you share how folks can learn about it and can you give some commentary on what you're thinking right now? I know you guys put on GitHub. Is there a link available-- >> Absolutely, available. Github.com/docker/roadmap. We tried to be very, very poignant about how we named that. So it was as easy as possible. We launched it a few months ago. It was a first in terms of Docker publicly sharing it's roadmap and what we're thinking and what we're working on. And you'll find very clear instructions of how to post issues and get started. What our code of conduct is. And then you can just get started and we even have a template for you to get started and submit an issue and talk to us about it. And internally my team and to many of our engineers as well, we triaged what we see changing and coming into the public roadmap two to three times a week. So for a half an hour to 45 minutes at a time. And then we're on Slack, batting around ideas that are coming in and saying how we can improve those. So for everyone out there, we really do pay attention to this very frequently. And we iterate on it and the image vulnerability scannings one of those great examples you can see some other things that we're working on up there. So I will say this though, there has been some continual asks for our Lennox version of Docker Desktop. So I will commit that, if we get 500 up votes, that we will triage and figure out how to get that done over a period of time. >> You heard 500 up votes to triage-- >> 500 >> You as get that. And is there a shipping date on that if they get the 500 up votes? >> No, no, (John laughs) you went to a shipping date yet, but it's on the public roadmap. So you'll know when we're working on it and when we're getting there. >> I want before I get into your session you had with the capital, which is a very geeky session getting under the hood, I'm more on the business side. The tail wind obviously for Docker is the micro services trend. What containers has enabled is just going to continue to get more awesome and complex but also a lot of value and agility and all the things you guys are talking about. So that obviously is going to be a tailwind for you. But as you guys look at that piece of it, specifically the business value, how is Docker positioned? Because a of the use cases are, no one really starts out microservices from a clean sheet of paper that we heard some talks here DockerCon where the financial services company said, "Hey, it's simple stack," and then it became feature creep, which became a monolith. And then they had to move that technical debt into a much more polyglot system where you have multiple tools and there's a lot of things going on, that seems to be the trend that also speaks to the legacy environment that most enterprises have. Could you share your view on how Docker fits into those worlds? Because you're either coming from a simple stack that more often and got successful and you're going to go microservice or you have legacy, then you want to decouple and make it highly cohesive. So your thoughts. >> So the simple answer is, Docker can help on both ends. So I think as these new technologies sort of gain momentum and get talked about a bunch and sort of get rapid adoption and rapid hype, then they're almost conceived to be this wall that builds up where people start to think, "Well, maybe my thing isn't modern enough," or, "Maybe my team's not modern enough," or, "Maybe I'm not moderate enough to use this." So there's too much of a hurdle to get over. And that we don't see that at all. There's always a way to get started. Even thinking about the other thing, and I'd say, one we can help, let us know, ping us, we'll be happy to chat with you, but start small, right? If you're in a large enterprise and you have a long legacy stack and a bunch of legacy apps, think about the smallest thing that you can start with, then you can begin to break off of that. And as a proof of concept even by just downloading Docker Desktop and visual studio code and just getting started with breaking off a small piece, and improve the model. And I think that's where Docker can be really helpful introducing you to this paradigm and pattern shift of containers and containerized packaging and microservices and production run time. >> And certainly any company coming out of his post pandemic is going to need to have a growth strategy that's going to be based on apps that's going to be based on the projects that they're currently working, double down on those and kind of sunset the ones that aren't or fix the legacy seems to be a major Taylor. >> The second bit is, as a company, you're going to also have to start something new or many new things to innovate for your customers and keep up with the times and the latest technology. So start to think about how you can ensure that the new things that you're doing are starting off in a containerized way using Docker to help you get there. If the legacy pieces may not be able to move as quickly or there's more required there, just think about the new things you're going to do and start new in that respect. >> Well, let's bring some customer scenarios to the table. Pretend I'm a customer, we're talking, "Hey Justin, you're looking good. "Hey, I love Docker. I love the polyglot, blah, blah, blah." Hey, you know what? And I want to get your response to this. And I say, "DevOps won't work here where we are, "it's just not a good fit." What do you say when you hear things like that? >> See my previous comment about the wall that builds up. So the answer is, and I remember hearing this by the way, about Agile years ago, when Agile development and Agile processes began to come in and take hold and take over for sort of waterfall processes, right? What I hear customers really saying is, "Man, this is really hard, this is super hard. "I don't know where to start, it's very hard. "How can you help? "Help me figure out where to start." And that is one of the things that we're very very very clearly working on. So first off we just, our docs team who do great work, just made an unbelievable update to the Docker documentation homepage, docs.docker.com. Before you were sort of met with a wall of text in a long left navigation that if you didn't know what you were doing, I would know where to go. Now you can go there and there's six very clear paths for you to follow. Do you want to get started? Are you looking for a product manual, et cetera. So if you're just looking for where to get started, just click on that. That'll give you a great start. when you download Docker Desktop, there's now an onboarding tutorial that will walk you through getting your first application started. So there are ways for you to help and get started. And then we have a great group of Docker captains Bret Fisher, many others who are also instructors, we can absolutely put you in touch with them or some online coursework that they deliver as well. So there's many resources available to you. Let us help you just get over the hump of getting started. >> And Jenny, and on the community side and Peter McKee, we're talking about some libraries are coming out, some educational stuff's coming around the corner as well. So we'll keep an eye out for that. Question for you, a personal question, can you share a proud devOps Docker moment that you could share with the audience? >> Oh wow, so many to go through. So I think a few things come to mind over the past few weeks. So for everyone that has no... we launched some exciting new pricing plans last week for Docker. So you can now get quite a bit of value for $7 a month in our pro plan. But the amount of work that the team had to do to get there was just an incredible thing. And just watching how the team have a team operated and how the team got there and just how they were turning on a dime with decisions that were being made. And I'm seeing the same thing through some of our teams that are building the image vulnerability scanning feature. I won't quote the number, but there's a very small number of people working on that feature that are creating an incredible thing for customers. So it's just how we think every day. Because we're actually almost trying to productize how we work, right? And bring that to the customer. >> Awesome, and your take on DockerCon virtual, obviously, we're all in this situation. The content's been rich on the site. You would just on the captains program earlier in the day. >> Yes. >> Doctor kept Brett's captain taught like a marathon session. Did they grill you hard or what was your experience on the captain's feed? >> I love the captain's feed. We did a run of that for the Docker birthday a few months ago with my co-worker Justin Cormack. So yes, there are two Justin's that work at Docker. I got the internal Justin Slack handle. He got the external, the community Slack Justin handle. So we split the goods there. But lots of questions about how to get started. I mean, I think there was one really good question there. Someone was saying asking for advice on just how to get started as someone who wants to be a new engineer or get into coding. And I think we're seeing a lot of this. I even have a good friend whose wife was a very successful and still is a very successful person in the marketing field. And is learning how to code and wants to do a career switch. Right? >> Yeah. >> So it's really exciting. >> DockerCon is virtual. We heard Kelsey Hightower, we heard James Governor, talk about events going to be more about group conventions getting together, whether they're small, medium, or large. What's your take on DockerCon virtual, or in general, what makes a great conference these days? Cause we'll soon get back to the physical space. But I think the genie's out of the bottle, that digital space has no boundaries. It's limitless and creativity. We're just scratching the surface. What makes a great event in your mind? >> I think so, I go back to thinking, I've probably flown 600,000 miles in the past three years. Lots of time away from my family, lots of time away from my son. And now that we're all in this situation together in terms of being sheltered in place in the global pandemic and we're executing an event that has 10 times more participation from attendees than we had in our in person event. And I sat back in my chair this morning and I was thinking, "Did I really need to fly that 600,000 miles "in the past three years?" And I think James Governor, brought it up earlier. I really think the world has changed underneath us. It's just going to be really hard to... This will all be over eventually. Hopefully we'll get to a vaccine really soon. And then folks will start to feel like world's a little bit more back to "normal" but man, I'm going to really have to ask myself like, "Do I really need to get on this airplane "and fly wherever it is? "Why can't I just do it from my home office "and give my son breakfast and take them to school, "and then see them in the evening?" Plus second, like I mentioned before in terms of access, no in person event will be able to compete ever with the type of access that this type of a platform provides. There just aren't like fairly or unfairly, lots of people just cannot travel to certain places. For lots of different reasons, monetary probably being primary. And it's not their job to figure out how to get to the thing. It's our job to figure out how to get the tech and the access and the learning to them. Right? >> Yeah (murmurs) >> So I'm super committed to that and I'll be asking the question continually. I think my internal colleagues are probably laughing now because I've been beating the drum of like, "Why do we ever have to do anything in person anymore?" Like, "Let's expand the access." >> Yeah, expand the access. And what's great too is the CEO was in multiple chat streams. So you could literally, it's almost beam in there like Star Trek. And just you can be more places that doesn't require that spatial limitations. >> Yeah. >> I think face to face will be good intimate more a party-like environment, more bonding or where social face to face is more impactful. >> We do have to figure out how to have the attendee party virtually. So, we have to figure out how to get some great electronic, or band, or something to play a virtual show, and like what the ship everybody a beverage, I don't now. >> We'll co-create with Dopper theCUBE pub and have beer for everybody if need they at some point (laughs). Justin, great insight. Thank you for coming on and sharing the roadmap update on the product and your insights into the tech as well as events. Appreciate it, thank you. >> Absolutely, thank you so much. And thanks everyone for attending. >> Congratulations, on all the work on the products Docker going to the next level. Microservices is a tailwind, but it's about productivity, simplicity. Justin, the product, head of the product for Docker, VP of product on here theCUBE, DockerCon 2020. I'm John Furrier. Stay with us for more continuous coverage on theCUBE track we're on now, we're streaming live. These sessions are immediately on demand. Check out the calendar. There's 43 sessions submitted by the community. Jump in there, there are own container of content. Get in there, pun intended, and chat, and meet people, and learn. Thanks for watching. Stay with us for more after this break. (upbeat music)

>> Announcer: From Austin, Texas it's The Cube covering Pure Storage Accelerate 2019, brought to you by Pure Storage. >> Good morning. From Austin, Texas, Lisa Martin with Dave Vellante at Pure Accelerate 2019. This is our second day. We just came from a very cool, interesting, keynote, Dave whenever there's astronauts my inner NASA geek from the early 2000s. She just comes right back up Leland Melvin was on >> Amazing, right? >> With a phenomenal story. Talking about technology and the feeling of innovation but also a great story of inspiration from a steam perspective science, technology, engineering, arts, math, I loved that and, >> Dave: And fun >> Very fun. But also... >> One of the better talks I've ever seen >> It really was. It had so many elements that I think you didn't have to be a NASA fan or a NASA geek or a space geek to appreciate the all of the lessons that Leland Melvin learned along the way that he really is inspiring, everybody the audience to take note of. It was I thought it was... >> And incredibly accomplished, right? I mean scientist, MIT engineer, played in the NFL, went to space, he had some really fun stuff when they were, you know, messing around with with gravity. >> Lisa: Yes. >> I never knew you could do that. He had like this water. >> Lisa: Water, yeah. >> Bubble. >> I'd never seen that before and they were throwing M&M's inside (laughter) and he, you know consumed it choked on it, which is pretty funny. >> Yeah, well it was near and dear to me. I worked with NASA my first job out of grad school. >> Dave: Really? >> I did, and managed biological pilots that flew on the space shuttle and the mission that the he talked about that didn't land, Colombia. That was the mission that I worked on. So when he talked about that countdown clock going positive. I was there on the runway with that. So for me, it just struck a chord of, >> Dave: so this is of course the 50th anniversary of the moonwalk. And you know I have this thing about watches, kind of like what you have with shoes (chuckles) >> Lisa: Hey, handbags. >> Is that not true? Oh, It's handbags for you? (laughing) >> Dave: I know this really that was a terrible thing for me to say. >> That's okay. >> Dave: You have great shoes so I just I just assumed that not good to make assumptions. So I bought a moon watch this year which was the watch that Neil Armstrong used to not the exact one but similar one, right? >> Lisa: Yeah. And it actually has an acrylic face because they're afraid if it cracked in space you'd have glass all over the place. [Lisa] Right. So that's a little nostalgia there. >> Well one of the main things too as you look at the mission that President John F. Kennedy established in the 60's for getting a man in space in that 10-year period. That being accomplished and kind of a parallel with what Pure Storage has done in its first 10 years of tremendous innovation. This keynote again Day 2, standing room only at least about 3000 people or so here. Storage as James Governor said, your friend and also who keynoted after Leland this morning you know, (mumbles) Software's eating the world storage is eating the world we have to have secure locations to store all this data so that we can extract maximum value from it. So nice parallel between the space program and Pure Storage. >> James is really good, isn't he? I mean he had to follow Leland and I mean again one of the better talks I've ever heard, but James is very strong, he's funny, he's witty he's he cuts to the chase. >> Lisa: Yes. >> He always tells it like it is. He's a very Monkchips is very focused on developers and they do a really good job there, one of the things he talked about was S3 and how Amazon uses this working backwards methodology which maybe a lot of people don't know about but what they do is they write and rewrite and rewrite and vet and rewrite the press release before they announce the product and even before they develop the products they write the press release and then they work backwards from there. So this is the outcome that we are trying to achieve, and it's very disciplined process that they use and as he said they may revise it hundreds and hundreds of times and he put up Andy Jassy's quote from 2004, around S3. That actually surprised me. 2000...Maybe I read it wrong. >> Lisa: No, it was 2004. >> Because S3 came out after EC2 which was 2006 so I don't know. Maybe I'm getting my dates wrong or I think James actually got his dates wrong but who knows, maybe you know what? Maybe he got a copy of that from the internal working document, working backwards doc that could be what it was but again the point being they envisioned this simple storage that developers didn't have to think about >> Lisa: Right. >> That was virtually unlimited in capacity, highly available and you know, dirt cheap which is what people want and so he talked about that and then he gave a little history of the Dell technology families and I tweeted out this in a funny little you know basically pivotal VM ware EMC and Dell and their history Dell was basically IPO 1984 and then today. There was a few things in between I know but he's got a great perspective on things and I think it resonated with the audience then he talked a lot about Kubernetes jokingly tongue-in-cheek how Kubernetes everybody thought was going to kill VMware but his big takeaway was look you got all these skills of (mumbles) Skills, core database skills, I would even add to that you know understanding how storage works and I always joke if your career is based on managing lawns you might want to rethink your career. But his point was which I liked was look all those skills you've learned are valuable but you now have to step up your game and learn new skills. You have to build on top of those skills so the history you have and the knowledge that you've built up is very valuable but it's not going to propel you to the next decade and so I thought that was a good takeaway and it was an excellent talk. >> So looking back at the conversations yesterday the press releases that came out the advancements of what Pure is doing, with AWS, with Nvidia, with the AI data-hub for example, delivering more of their portfolio as a service to allow businesses whether it's a law-firm like we talked to yesterday utility or Mercedes AMG Petronas Motor-sport, to be able to access data securely, incredibly quickly, recover it restore it absolutely critical and really can be game-changing depending on the type of organization. I want to get your perspectives on some of the things you heard anecdotally yesterday after we wrapped in terms of the atmosphere, the vibe, the thoughts on Pure's next 10 years. >> Yeah, so several things, just some commentary so it's always good at night you go around you get a lot of data we sometimes call it metadata. I think one of the more interesting announcements to me was the block-storage on AWS. I don't necessarily think that this is going to be a huge product near term for Pure in terms of meaningful revenue, but I think it's interesting that they're embracing the trend of the Cloud and are actually architecting Cloud solutions using Amazon services and blending in their own super gluing their own, I mean it's not really superglue but blending in their own software for their customers to extend. Now, you know some of the nuances I don't think they are going to have they have better right performance I think they'll have better read performance clearly they have better availability I think it's going to be a little bit more expensive. All these things are TBD that's just my take based on looking at what I've seen and talking to some people but to me the important thing is that Pure's embracing that Cloud model. Historically, companies that are trying to defend an existing business, they retreat. You know, they denigrate they don't embrace. We know that Pure's going to make more money on pram than it does in the Cloud. At least I think. And so it's to their advantage for companies to stay on-prem but at the same time they understand that trend is your friend and they're embracing that so that was kind of one thing. The second thing I learned is Charlie Giancarlo spent a lot of time with them last night as did you. He's a bit of a policy wonk in very certain narrow areas. He shared with me some of the policy work that he's done around IP protection and not necessarily though on the side that you would think. You would think that okay IP protection that's a good thing but a lot of the laws that were trying to be promoted for IP protection were there to help big companies essentially crush small companies so he fought against that. He shared with me some things around net neutrality. You would think you know you think you know which side of net neutrality he'd be on not necessarily so he had some really interesting perspectives on that. We also talked to and I won't share the name of the company but a very large financial institution that's that's betting a lot on Pure was very interesting to me. This is one of the brand names everybody would know it if you heard it. And their head of storage infrastructure was here, at the show. Now I know this individual and this person doesn't go to a lot of shows >> Maybe a couple a year. >> This person chose to come to this show because they're making an investment in Pure. In a fairly big way and they spent a lot of time with Pure management, expressing their desires as part of an executive form that Pure holds they didn't really market that a lot they didn't really tell us too much about it because it was a little private thing but I happen to know this individual and and I learned several things. They like Pure a lot, they use it for a lot of their workloads, but they have a lot of other storage, they can't necessarily get rid of that other storage for a lot of reasons. Inertia, technical debt, good tickets at the baseball game, all kinds of politics going on there. I also asked specifically about some hybrid companies products where the the cost structure's a little bit better so this gets me to flash array C and we talked to Charlie Giancarlo about this about his flash prices come down and it and opens up new markets. I got some other data yesterday and today that you know that flash array C is not going to be quite priced we don't think as well as hybrid arrays closing the gap it's between one and one and a quarter, one and a half dollars per gigabyte whereas hybrid arrays you are seeing half that, 70 cents a gigabyte. Sometimes as low as 60 cents a gigabyte. Sometimes higher, sometimes high as a dollar but the average around 65-70 cents a gigabyte so there's still a gap there. Flash prices have to come down further. Another thing I learned I'm going to just keep going. >> Lisa: Go ahead! >> The other thing I learned is that China is really building a lot of fab capacity in NAND to try to take out the thumb-drive market-place so they are going to go after the low-end. So companies like Samsung and Toshiba, Toshiba just renamed the company, I can't remember the name of the company but Micron and the NAND flash NAND manufacturers are going to have to now go use their capacity and go after the enterprise because China fab is going to crush the low-end and bomb the low-end pricing. Somebody else told me about a third of flash consumption is in China now. So interesting things going on there. So near term, flash array C is not going to just crush spinning disk and hybrid, it's going to get closer and it's going to slowly eat away at that as NAND prices come down it really could more rapidly eat away at that. So I just learned some other stuff too but I'll take a breath. (laughter) >> So one of the things I think we are resounding with it we heard not just yesterday on the program day but even last night at the executive event we were at is that from this large financial services company that you mentioned, Pure storage is a strategic partner to many organizations from small to large that is incredibly valued to your point the Shuttleman only goes to maybe a couple of events a year and this is one of them? >> Dave: Right. >> This is a company that in its first 10 years has embraced competition head on and I loved how you talked about yesterday 10 years ago they just drove a truck through EMC's market and sort of ripping and replacing. They're bold but they're also doing it in a way that's very methodical. They're working on bringing you know changing companies' perspectives of even backup data as becoming an asset to put it on flash. Because if you can't rapidly restore that, if there's an outage whether it is an attack or it's unintentional human related, that data can't be recovered quickly, you're in a big big problem. And so them as a strategic component of this isn't in any industry I think it was a very resounding sentiment that I heard and felt yesterday. >> Yeah, this ties into tam expansion of what we talked to Charlie Giancarlo about new workloads with AI as an example flash or AC lowering prices will open up those some of those new workloads data protection backup is clearly an opportunity and I think it's interesting, you're seeing a lot of companies now announce a lot of vendors announce flash based recovery systems I'll call them recovery systems because I don't even consider them backup anymore it's not about backup, it's about recovery. Oracle was actually one of the first to use that kind of concept with the zero data loss recovery appliance they call it recovery. So it's all about fast and near instantaneous recovery. Why is that important? It's because it's companies move toward a digital transformation and what does that mean? And what is a digital business? Digital business is all about how you use data and leveraging data in new ways to create new value to monetise or cut cost. And so being able to have access to that data and recover from any inaccess to that data in a split-second is crucial. So Pure can participate in that, now Pure's not alone You know, it's no coincidence that Veritas and Veeam and Cohesity and Rubrik they work with Pure, they work with HPE. They work with a lot of the big players and so but so Pure has to you know, has some work to do to win its fair share. Staying on backup for a moment, you know it's interesting to see, behind us, Veritas and Veeam have the biggest sort of presence here. Rubrik has a presence here. I'm sure Cohesity is here maybe someway, somehow but I haven't seen them >> I haven't either. >> Maybe they're not here. I'll have to check that up, but you know Veeam is actually doing very well particularly with lower ASPs we know that about Veeam. They've always come at it from the mid-market and SMB. Whereas Cohesity and Rubrik and Veritas traditionally are coming at it from a higher-end. Certainly Cohesity and Rubrik on higher ASPs. Veeam's doing very well with Pure. They're also doing very well with HPE which is interesting. Cohesity announced a deal with HPE recently I don't know, about six months ago somebody thought "Oh maybe Veeaam's on the outs." No, Veeam's doing very well with HPE. It's different parts of the organization. One works with the server group, one works with the storage group and both companies are actually doing quite well I actually think Veeam is ahead of the curve 'cause they've been working with HPE for quite some time and they're doing very well in the Pure base. By partnering with companies, Pure is able to enter that market much in the same way that NetApp did in the early days. They have a very tight relationship for example with Commvault. So, the other thing I was talking to Keith Townsend last night totally not secretor but he's talking about Outpost and how Amazon is going to be challenged to service Outpost Outpost is the on-prem Amazon stack, that VMware and Amazon announced that they're co-marketing. So who is going to service outpost? It's not going to be Amazon, that's not their game in professional service. It's going to have to be the ecosystem, the large SIs or the Vars the partners, VMware partners 'cause that's not Vmwares play either. So Keith Townsend's premise, I'd love to have him on The Cube to talk about this, is they're going to have trouble scaling Outpost because of that service issue. Believe it or not when we come to these conferences, we talk about other things than just, Pure. There's a lot of stuff going on. New Relic is happening this week. Oracle open world is going on this week. John Furrier just got back from AWS Bahrain, and of course we're here at Pure Accelerate. >> We are and this is our second day of two days of coverage. We've got Coz on next who I think has never been on The Cube. >> Dave: Not to my knowledge. >> We've got Kix on later. A great lineup, more customers Rob Lee is going to be on. So we're going to be digging more into Pure's Cloud strategy, the next ten years, how they're going to accelerate that and pack it into the next couple of years. >> I'll tell you one of the things I want to do, Lisa. I'll just call it out. An individual from Dell EMC wrote a blog ahead of Pure Accelerate I think it was last week, about four or five days ago and this individual called out like one, two, three, four.... five things that we should ask Pure so we should ask them, we should ask Coz we should ask Kix. There was criticism, of course they're biased. These guys they always fight. >> Lisa: Naturally. >> They have these internecine wars. >> Lisa: Yep. >> Sometimes I like to call them... no I won't say it. So scale out, question mark there we want to ask Coz about that and Kix. Pure uses proprietary flash modules. They do that because it allows them to do things that you can't do with off-the-shelf flash. I want to ask and challenge them that. I want to ask about their philosophy on tiering. They don't really believe in tiering, why not? I want to understand that better. They've made some acquisitions, Compuverde is one acquisition, it's a file system. What does that mean for flash play? >> Now we didn't hear anything about that yesterday, so that's a good point that we should dig into that. >> Yeah, so we'll bring that up. And then the Evergreen competitors hate Evergreen because Pure was first with it they caught everybody off guard. I said it yesterday, competitors hate Evergreen because competitors live off of maintenance and if you're not on their maintenance they just keep jacking up the maintenance prices and if you don't move to the new system, maintenance just keeps getting more and more and more and more expensive and so they force you, you're locked in. Force you to move. Pure introduced this different model. You pay for the CapEx up front and then, you know, after three years you get a controller swap. You know, so... >> To your point competitors hate it, customers love it. We heard a lot about that yesterday, we've got a couple more customers on our packed program today, Dave so let's get right to it! >> Great. >> Let's wrap up so we can get Coz on stage. >> Dave: Alright, awesome. >> Alright, for Dave Vellante. I'm Lisa Martin, you're watching The Cube from Pure Accelerate 2019, day two. Stick around 'Coz' John Colgrove, CTO, founder of Pure, will be on next. (upbeat music)

>> Narrator: Live from Las Vegas, it's The Cube covering HPE Discover 2017 brought to you by Hewlett-Packard Enterprise. >> Welcome back everyone, live here in Las Vegas, this is the Cube special presentation of Hewlett-Packard Enterprise, HPE Discover 2017. I'm John Furrier with The Cube, my co-host Dave Vellante for the next three days with wall-to-wall coverage here in Las Vegas. Our next guess is Tom Lattin, Vice President and General Manager of HPE Server Options which is all the good stuff that wrap around the servers. And certainly the big news here at HP is the Gen10, the continuation of the, the generation of servers which is all the rage these days. People are talkin' about servers, are we buying more or buying less? Still a lot of private cloud going on. Nothing really changing in the premise world. Welcome to The Cube. >> Thank you, good to be here. >> Alright, so what's the big news? I mean, to me the, the thing that I've always been watching is the Gen8 stuff, Gen10 now is the new announcement platform for servers. >> Certainly. >> A lot of stuff happening around, a lot of innovations. Give us a quick update on the key things happening around Gen10 and the options. >> Well certainly with Gen10, we've got a whole new level of security that is a big part of the Gen10 story. And with the server options in the memory SEP system and the storage SEP system and the networking SEP system, all of those technologies contribute to building up those layers of security in Gen10. So that's a key part of what we're doing this week at discover. The second thing in the options space, the server options space, is persistent memory. So we introduced persistent memory on Gen9 servers last year with the MB DIMM, an eight gigabyte MB DIMM. We're extending that portfolio this year with the Gen10 servers and increasing the MB DIMM capacity to 16 gigabytes. But the really big news in the persistent memory offering is scalable persistent memory. >> I just saw a great article on the CRN, Computer Reseller News or CRN, really giving you guys some props on this. "Persistent memory combines the performance of D RAM with the persistent of traditional SSDs or spinning disk. So, essentially a huge performance gain, and, which is always good, HP has that, always has some good mojo when it comes to, you know, high quality products and performance. But talk about the impact because one of things that's going on right now is storage has to be invisible but applications now have, going beyond virtual machines. You've got containers, you've got all kinds of cloud things happening with the apps. So the data, the state of the data, the performance of the data is really critical to customers. What's the impact of this to that trend? >> This is, persistent memory unleashes an incredible amount of performance for the server, for the application running on the server. At it's most fundamental level, persistent memory and MB DIMM or a scalable persistent memory implementation can replace a layer of flash storage. And we're seein' performance benefits on the order of doubling the performance of the application just by swapping out an SSD for persistent memory or an MB DIMM. When the applications, when the architects actually modify the applications to take advantage of the fact that there's a persistent memory layer in there, we see performance benefits as small as four times improvement, but in many cases we're seeing 20, 25, 27x performance improvements because the architects of the applications now can dive right into the memory sub-system without going through layers and layers of code and moving data around to get to storage. >> Love, love the options comps that you guys are running because I think one of the things that we here is, you know, flexibility is key and it's kind like goin' to the store and, like, getting some accessories for your suit. Not one size fits all, you need to have a lot of options given the environment. So I got to ask you the competitive question. How do you guys compare vis-a-vis the competition with the persistent memory stuff, for instance? You mentioned the performance, how does that compare with some of your competitors? >> I think persistent memory is a good example of where we're way out ahead of where our competition is right now. It's, you can't just drop in a piece of hardware in the server and get all of the benefit out of it. You've got to be able to integrate that piece of hardware with the system software, the bios in the system, and then work with software application partners especially to go modify, or to optimize their applications to work best with that component that you put in there. >> And you guys do that? >> We do that extensively. >> Not the customer, the customer just, what? Just installs it? >> The customer gets it. It just works. >> So, what's the typical sort of anatomy of a life cycle of a server these days? And, and, I mean, it used to be, in the old days it was called peripherals and peripherals made up probably 60 to 70% of the market so it was very huge, you know, quite a huge opportunity. So how does it work from a customer standpoint? Does, do they, what's their starting point? How do they plan this out? Or is it more reactive? I wonder if you could sort of bring us up to date on that dynamic, Tom. >> I think that's, part of what we bring to the market is a set of server platforms that have an incredible breadth of capability and that breadth comes from the configuration choices that customer can make through the server options portfolios. So, generally, they're, a customer will standardize on a few different platform types and then deploy those servers for a variety of different workloads. And so it's through those configuration choices, storage capacity, memory capacity, the performance of different layers in the memory and storage hierarchy that allow them to be able to fine-tune a small set of servers, really, for a much broader set of workloads. >> So we've commented for a number of years now on The Cube that the pendulum is swinging. Storage is, and servers are coming, and computer coming closer together. >> Absolutely. >> You certainly saw that with Flash and PCIe. Sort of, those trends brought storage and compute together and now you're accelerating that even further with, with persistent memory. >> Tom: Yes. >> So, as that happens, one of the big challenges is data sharing, right? Now you hear things like, you know, NVMe over Fabric and other technologies to, to link these capabilities, these nodes if you will. What's, I mean it sounds like The Machine, so. >> Tom: Exactly. >> What's happening there and help us sort of squint through those two big trends. >> Yeah, I think that as we evolve architectures to focus on the data and recognize that the data really is where the value resides, we're moving from a world where, first of all, sharing the data on storage makes a lot of sense to enable that. If you look at some of the demonstrations that we've done recently with the machine and with memory driven computing, it's about taking that shared presence of the data or shared instance of the data to an entirely new level where the processors, processing capability can get directly at it and operate it and work on that really as a shared body of information, shared body of knowledge. So yes, started in the storage sub-system but absolutely where we're headed is a memory-driven computing world where it's in the memory sub-systems. >> And that is The Machine, but, and which is a, you know, big R&D project that's kind of comin' out of HP Labs, and, you know, Martin Fink showing it off a couple years ago and giving us the roadmap, but now we're seein' it sort of evolve. But as well, I would think your ecosystem can kind of build it's own pseudo-machine, you know? With compute power and all this persistent memory and you know, architecting, I mean, do you see those as two separate vectors that, you know, let's see what happens in the channel? Or, or do you see those two worlds coming together? >> Fundamentally, we are a partnering business, right? We work extensively with the ecosystem of software providers, partners in the industry. So what we're demonstrating with The Machine, necessarily we've done a lot of those parts ourselves to show the capability. But absolutely this memory-centric computing vision and that we're beginning to realize with some of the products that we're releasing today, persistent memory is a great example of that, is all about enabling the industry, the ecosystem in the industry to bring that value for, ultimately for all of our customers. >> And has heading up the sort of options business, if you will, how do you, one of the things we've talked about a lot is this notion of true private cloud which is substantially mimicking public cloud on PRIM because the world is hybrid as we all sort of point out. How do you create that experience for customers? That, that cloud-like experience? >> I think it, well with the simplicity and the agility of what we're doing with the HPE compute experience now is very focused on creating that cloud-like experience in a hybrid cloud world, right? On premises for example. And so that's, a lot of that is about being able to scale up and down the computing capability, to incorporate new financial models so that you can buy compute, rent compute at your, kind of, depending on what your strategic corporate objectives are. So the options themselves then give you that ability to, for example, scalable persistent memory uses the base system in the server and one day you may say, "Hey, I need to use a "portion of that as persistent "because of the workload that I'm running." And then later that night, that same system could translate over to run a completely different workload and change the profile of the persistent memory that's being used because it's a configuration setting of the base system memory. So making the system itself very flexible to adapt to the changing needs of workloads, either overtime or very realtime like that in the course of a day. >> Tom I want to get your thoughts on the trends that we're covering, and certainly the industry's covering. So you have an industry scope and you have, obviously, partners which are going to be critical in getting things certified and or working so the customer just plugs, plugs stuff in, like the memory. >> Tom: Yes. >> Obviously the market place says, well, "Oh server ships are down," but the cloud's happening, servers are actually growing no matter how you look at. But there's more realtime stuff goin' on. There's more processing happening. How do you guys look at the marketplace trends because there is more need, at The Edge for instance, we had Bill Philbin on just earlier before you came on talkin' about how storage and compute are comin' together. This is kind of the, the options world you're in. You're in the middle of all this action so people actually cobbling together and composing solutions, whether it's on PRIM or working with similar architectures in the cloud, same code bases moving back and forth. So this whole world is really not declining. Maybe shifting how it was before, that transformation you're in the middle of, how do you guys look at that and how you do talk to the customers who are like, "I was buying servers and options before, "I still got to do that but I got to "transform and be prepared for realtime analytics, "using multiple clouds, all these kinds of, "these, these important items for the future"? >> Yeah, it's a bit of an architectural revolution if you will, right? As we move to a memory-centric computing world, as we move to a world where everything is cloud-based, cloud architecture-based, whether it's out in a public cloud somewhere or on an on-prep as kind of hybrid IT model, it really is a completely different architectural model. And so to capitalize on that, what we work with customers on is things like the composable capability of synergy. Things like persistent memory and making that scalable to move to a memory-driven computing model. Things like our all-Flash array business and our product offerings to be able to accelerate that storage sub-system well beyond what's been done before. >> It's performance driven too, you got to eek out performance more and more. >> Yes. That's kind of the mandate. Another interesting thing I wanted to get your thoughts on, and, you know, I'm old in the industry these days relative to the average age of most people in the big the big companies, like hyper-scalers are like 28 to 30-something. The trend is systems. I mean, you're seeing, if you look at what the cloud ' doing in the revolution at the architectural level, it's almost a complete crossover to a systems mindset. Systems meaning operating systems or, you know, core systems. So a lot of the people that are really doing well in the industry, who are radically transforming it, are older guys. James Gosling was at, just joined Amazon Web Services. You got guys who are in their 50s who are leading major architectural shifts. This kind of puts HP in an interesting position because you guys have so much experience with systems, servers, you know, just on an isolated basis. But now, as that looks out over the landscape, it's even more important to look at it from a holistic perspective. Your thoughts on this trend? >> Well absolutely, it's a huge trend and by taking the expertise that we've got at a systems level and coupling that with our strategic imperative to partner with other industry leaders in the industry revolution, I think those two together position not just HPE well, but the ecosystem of HPE and our software industry partners to really help advance that, that architectural-- >> I was talking to James Governor last who's the, with Red Monk and one of the research firms we like and I said to him, "It's open bar and open source," was my kind of headline story I was tryin', we were collaborating on and what I mean by that is that, you know, as open source evolves, we saw some of the stuff goin' on with The Machine in mem-store, a lot of that stuffs going to be open source at the core at the system level. So open source is growing, but when I say open bar, it's like there is more goodness being contributed to open source than ever before. You're seeing great machine learning libraries being, you know, given in to collaboration. You're seeing open source being a great recruiting environment. So if you're a young gun in the marketplace right now, you're getting all this contribution so with that kind of as a context, what's the open source strategy that you see? 'Cause you're in kind of a glue layer with options. You're kind of creating some flexibility for customers. At the same time, you've got a glue kind of concept goin' on with software. What do you guys do with open source? Is there a trend there that you'd like to share? I mean, I'm interested to know what your position is vis-a-vis contribution programs and whatnot. >> Yeah, I think, certainly at the hardware layers, right, of what we're doing with server options, it's about enabling new capabilities. And so we work with quite a few open source partners to enable those. So say, for example, Red Hat, they're taking our persistent memory offerings and optimizing those so that they get, certainly the immediate benefit of a layer of high-performance storage but the more radical performance improvements that they can get when they address directly a layer of persistent memory. So it's not so much that we're creating a whole new, at least in the option space, kind of a whole new open source plane. >> But you're intersecting. >> Absolutely. >> I mean, one other thing is networking is hot right now. Certainly, SDM we see that. A lot of the open source projects, and even in Linux foundation you're seeing the network stack just kind of being, kind of decomposed. So a very interesting opportunity. >> Yes. >> Well, and the same thing with storage, right? And you mentioned Flash a couple of times right? You're seeing the whole storage stack just completely morphing and changing. >> Tom: Yeah. >> So you guys are in the center of that, how does a customer engage? Does it happen typically through the channel, do they go to hpe.com, how does that happen? >> For server option kind of products, yeah, certainly. Through our direct sales force, through our partners' sales forces, 'cause, as we said, it's an ecosystem that brings us value forward. So in many cases, it's not us in, even in explaining something like persistent memory. It's Microsoft or it's Red Hat or it's SUSE, or partners there, VMware. We've got a, actually a lot of presence with VMware and some interesting things they're going to be talking about in one of our sessions here later today at Discover. So that's one path. Or two paths. Our sales force, their sales force and then, absolutely, the channel. We've got a very rich channel program and a lot of engagement with them to bring them up on networking technologies, storage technologies, memory, persistent memory technologies so that they can-- >> John: So it's ecosystem is really the key. >> They can effectively engage customers, yeah. >> Alright, Tom Lattin is the Vice President and General Manager at HP Server Options. My final question for you to end the segment here is what should customers know about Gen10 and server options if you had a chance to look right into the camera and say, "Hey, new game in town," or, "Think differently around architecture," what would be, what would be your words? In your words, what should customers know about the world you're building? >> Certainly with Gen10, the server options portfolio unleashes or helps support the overall security capabilities of Gen10, number one. But if I can have a second one. >> John: Of course. >> I've got to play persistent memory high because we've got a terabyte-scale persistent memory capability in the Gen10 platforms which is, opens up a whole new world of opportunity for applications, as I said, early on to develop or increase performance, in many cases, 20, 25, 27 times the capabilities today. >> That's awesome, I mean I think the memories awesome. Dave and I have been talkin' for years that memory used to be the resource that was constrained and unlimited storage, now it's the other way around, people want memory, application developers and programmers. This is The Cube bringing you great content you can put to memory, Flash memory. HPE Discover, I'm John Fullier with Dave Vellante, we'll be back with more live coverage after this short break.

>> Narrator: Live from San Francisco. It's theCUBE, covering DevNet Create 2017, brought to you by Cisco. >> Welcome back, everyone. We're live in San Francisco for CUBE's special coverage, exclusive coverage, of Cisco Systems DevNet Create. It's an inaugural event for DevNet, a new extension to their developer program. DevNet, which is their classic developer program for the Cisco ecosystem, network guys, so on and so forth, moving packets around, hardware guys. DevNet Create is about developers and dev ops and cloud-native, all the goodness of application developers. Where apps meets infrastructure, certainly with the Cisco acquisition of AppDynamics, a new world order is coming down the pipe. Cisco's moving up the stack. I'm John Furrier, Peter Burris is my co-host, our next guest is Val Bercovici, CUBE alumni and also guest analyst in our studio in Palo Alto, also the cofounder of Peritus.ai, and now you can talk about it. Welcome to theCUBE. >> Thanks, John. We get to talk about it, finally. >> So before we get into your company, and I want to drill into it because the first public CUBE interview, drilling down on what you're working on. What's your take on Cisco's event here, because, I've known Cisco since I moved to Silicon Valley, 18 years, and even before then, and they scaled all the internet connecting networks. There's always been a discussion internally inside Cisco about moving up the stack. And it's always been kind of like a Civil War. Half the company wants to move up the stack, half doesn't, and now, you've been in NetApp, you know this world and its infrastructure, its hardware, its gear, its boxes, network packets. This is a seminal moment for Cisco. They've tried some open source before, but this seems like an all-in bet. Your thoughts? >> It is, and I was just telling Yodi Rahm, before we went live on stage that I think this is like Goldilocks event, right? It's my first. Apparently, it's the first one of its kind here at Cisco, and for me it's not too big. It's not too small. I find it really just the right size, and I find it very well-targeted, in terms of the fellow speakers, panelists that I was on with today in terms of, I see the right amount of laptops, the right amount of code, basically, amongst the attendees on the floor here. So my first impression, 'cause that's all I have so far, is it's a very well-targeted show, and it's not unique anymore. You'll notice Intel kind of pulled back from having one large event, one large annual event, and smaller more targeted events for developers, for operators, for other ISVs, and so forth. >> You're talking about the IDF Intel Developer Forum. >> The IDF, yeah, it's no longer a big, monolithic event. They split it up into more- >> And IBM has also collapsed their shows into one monster show. So little micro-events seem to be the norm. >> Yeah, I wouldn't even call it quite even a micro-event. It's a bit bigger than that, but it's not a VMworld . >> It's not a Dreamforce. >> It's not a COMDEX to VR sales. >> Interesting, I like they did their homework on the panels. So in terms of subject matter, the agenda looks great, but I do agree with you. I like how principals are here. It's not just staff here. It's both people in the trenches at Cisco, and the execs are here. Susie Wee and some other folks, they run Cisco a lot. They're all here. >> And their CTO, this morning, I caught the opening keynote livestream on the way over here. She did a fantastic job describing the role of the infrastructure developer, which is something that is a bit nebulous to nail down, at least it has been in the past, and I'm really glad that Cisco is echoing that, because I think it helps their entire ecosystem, their partner ecosystem, particularly former employers like NetApp of mine. >> I'm usually critical of big companies trying to put their toe in the water with some event that looks like a little cloud washing or you know, here or there, but I think Cisco's got a legit opportunity with programmable infrastructure. And I think, just in general, straight up, they do, because their infrastructure, and Peter and I talked about that. But I think IoT is really the big driver. They could really, that's a network connection. It's at the edge. It requires intelligence. That's a good angle for them. >> It's a great angle. The only beef I have, the gripe I have, is they still call it IoE, I think. If it's going to be Internet of Everything, and it's Internet of nothing, right? I really wish they'd kind of stick to the agreed term, and what they are doing of course is giving- >> But they were first with IoE. They were, you got to give Cisco, when they ran those commercials, what 10 years ago? >> Yeah. >> You know. >> It's a personal in for me. The commercials are fantastic. It's just the term bothers me. >> They got dogma with IoE, come on, get rid of it. Okay, tell me about your company? >> So Peritus.ai, we've realized now there's a chance to go beyond traditional digital disruption of existing industries to cognitive disruption. Let me explain what I mean by that. We're seeing a lot of increasing pace of change in data centers. The conference here, and all the technologies spoken about here, are very foreign to more traditional data center operators, and so the new environments, microservice architectures, or cloud-native apps or so forth. It's a pace of change that we haven't seen before. Agile business and agile software developer models can push code out realistically on a daily basis, whereas the waterfall model and the iCode models in most IT service practitioners practice, that's a manual or quarterly update cycle, with formal change managed practices. >> John: A more settled, structured. >> Yeah, yeah. >> Slow. >> Familiar. >> John: Reliable. >> You know, but it's the past, and the pace of change now is creating stress within IT organizations and stress within the product support organizations of the vendors that they choose to deploy. You couple that with increasing complexity of the environments we have here. We have a lot going on, the ethos of CNCF, which is container packaged, dynamically orchestrated, and micro services architected apps, cloud-native apps. The abstraction layers are masking a lot of complexity there, but the complexity is still there. And you have very good availability if you're able to write to cloud-native principles as a developer, but nevertheless, you still got that .001% of your outages so forth. And the last line of defense towards business continuity is still a human. You still got escalation engineers and support organizations that go through pretty contrived and complicated workflows to triage and diagnose problems, perhaps a case manager to assign a case or subject manager expert, get that back and forth information with the customer and finally resolve the case, and this is what we term cognitive disruption. The maturity of the AI platforms now have reached a point where you can take these complicated workflows that require nuance and inference, and actually apply true machine learning and deep learning to them. And if not entirely automate the resolution of these complex cases, better prepare a scarce resource, an escalation engineer with lots of experience, with more context up front when they encounter the case, so they can close it more quickly, and this has- >> So you're targeting, so if I understand this correctly, you're targeting the personnel in the data center. >> Val: The supportability space. >> Escalation engineers, the human labor, the last mile, if you will, or whatever, first mile, how you look at it. >> Correct. We see APM vendors in this space, we see ITSM vendors in the space. They're partners and even platforms for us. No one really is focused on supportability and automating those workflows using cognitive techniques. >> John: Give an example, give an example. >> The best example I can give actually is firsthand. I'll try and be as generic as I can to protect the innocent, but if you take a look- >> John: NetApp. >> (laughs) It's not even specifically a NetApp case. >> John: Okay, all right. >> If you look at the supply chain upstream, let's talk about electronic supply chain. If a particular manufacturer defect occurs upstream, that defect gets shipped in bundles, purchased by an equipment supplier vendor in bundles, and deployed by customers in bundles. So it's not like one of these one node outage situations is the best case scenario, traditional triple replication, you know. >> John: It's a bad batch basically. >> A bad batch. >> A lot of bad product. >> That can take out not just a node, it can take out a rack. It can take out multiple racks of storage gear, switching gear, server hosts, and so forth. In that case, again, your last line of defense is a human. You basically got to triage and diagnose the problem, could be hardware problem, could be a driver-software problem, could be an upstream OS or database problem. And it's a very stressful environment, a very stressful situation. You can take a look at prior case notes. You can take a look at machine logs and data. You can take a look at product documentation and bill of materials from suppliers, and you can pre-analyze a lot of that, and factor that into your diagnosis, effectively having it almost ready before the case is even opened, so that when the escalation engineer is assigned the case, they don't start from ground zero. They start from third base and almost they're rounding their way to home, and they're able to apply all the prior knowledge, algorithms never sleep. All the prior knowledge in terms of all the cases that have actually been dealt with that match that to a degree. They're never perfect matches, because that's just business process automation. There's a degree of inference required, and using AI techniques, we're able to guess that you know what? I've seen this before. It's very obscure, but it's actually going to be this resolution. >> So AI's technology that you're using in machine learning and data, what problem are you solving specifically? Saving them time, getting them faster resolutions? >> So we're improving the efficiency of support operations. There's always margin pressures within customer support operations. We're fundamentally solving complex system problems. We've reached a point now where business process automation can solve trivial support cases. >> John: Wait a minute, wait a minute, hold on. Expert system's supposed to do this. >> And they did in the past, and now we're evolving beyond the expert. >> Not really. Remember those expert system stays? >> Yeah, I remember LISP and all those early days, so yeah. >> So this kind of sounds like a modern version of an expert system to aid the support engineers to either have a predetermined understanding of options and time to solution. >> So we're able to do so much more than that, right? We're able to create what we call otologies. We're able to categorize all the cases that you've seen in the past, find out whether this new one fits an existing category, if so, if it matches other criteria, if not, defining a category. We're able to orchestrate. Resolution is not just a one-shot deal. Resolution is diagnose the problem, find out if you have some subject matter experts available to resolve the issue, assign it to them, track their progress, close the case, follow up on customer satisfaction. All those things are pretty elaborate workflows that can be highly automated today with cognitive approach-- >> Congratulations on launching. Thanks for spending the time to lay that out. What's next? You've got some seed funding? >> Val: We've got some seed funding. >> You got some in an incubator at the Hive in Palo Alto, which we know quite well. Rob is great, Rob is a great friend. He's done great, he's done great. How many people do have, what are you guys looking to do? What are some of the priorities? >> We are hiring. We're definitely looking to get more data scientists on staff, more full-stack engineers particularly with log experience. We're still looking for a CTO and leadership team. So there's a lot of hiring coming in place. >> John: How many in there now? >> We have about, less than 10 people working right now. >> It's a great opportunity for a classic early-stage opportunity. >> Yeah, early stage opportunity. We're addressing a hot space, and what I love is I personally shifted from being a provider of cloud-native solutions in this market to being a consumer. So I'm seeing exactly how a perfect storm is coming together of machine and deep learning algorithms, running on, orchestrated-- >> John: Both sides of the table. You should talk to Mark Sister. >> Yeah. He's been on both sides. What's it like to be on the other side now? >> It's everything I actually thought it would be, because at the end of the day, I always say, developers are the ultimate pragmatists. So it's not so much about brand loyalty at any particular vendors. What solution, whether it's an open source library, whether it's a commercial library, whether it's a propietary cloud service or something in between. What solution can solve my task, this next task? And composite applications are a very real thing right now. >> So we had a question I posted into the crowd chat, from this social net. I'm going to ask you the same questions. So Burt's watching and maybe you'll find that thread, and I'll add to it later. Here's the question. What challenges still remain as part of implementing DevOps, in your opinion? How did you see the landscape, and how are people addressing them? In your expert opinion, what's the answer to that question? What's your opinion? >> It's a two-faceted answer, at least. The first one, it's not a cliche. It's still a cultural challenge. If you want to actually want to map, it's not even a cultural challenge specifically, it's Conway's Law. Any product output, software output, is a function of your organizational structure that created it. So I find that whether you want to call it culture, whether you want to call it org structure, the org structure's rarely in place to incentivize entire teams to collaborate together throughout a full CICD pipeline process. You've still got incentive structures and org structures in place for people to develop code, unit test it, perhaps even integration test it, but I see more often than I'd like to, isolated or fenced off operations teams that take that and try to make it something real. They might call themselves SREs, and outside recovery engineers, but they're not integrated enough into the development process, in my mind. >> So you're saying the organization structures are also foreclosing their ability be agile, even though they're trying hard, that the incentives are too grounded in there. >> So I still see a lot of skunkworks projects as DevOps projects, and it shouldn't be that way anymore, right? There should be, where there's a legitimate business reason for more agile businesses, there should be a much more formal DevOps structure, as opposed to skunkworks DevOps structure. So that's one challenge, and it's not new, but it's also not resolved. And the other one really is this blind spot for the autonomous data center vision, this blind spot for operations being 100% automated and really just never having to deal with the problem. The blind spot is everything breaks. New technology just happens to break in new ways, but it does fundamentally break, and if your last line of defense is a human or a group of humans, you can expect a very, very different sort of responsiveness and agility as opposed to having something automated. >> Peter and I have been talking all morning the Ford firing of Mark Fields, which was announced yesterday. He quote retired by the Twitter handle of Ford, which is just code words for he got pushed aside. One, we're big fans of Mark Fields, before we covered Ford there in Palo Alto, doing some innovative centers over there, and also a Cloud Foundry customer. So I was actually, took notice of that. We were commenting on not so much the tech, but the guy got fired in less than three years into his journey as chief executive. >> Val: Yeah. >> Now the stock's down 39% so the hammer's coming down from either the family, Ford family, or Wall Street, Peter thinks Wall Street. But this brings up the question, how are you going to be a transformational leader, if you don't have the runway? Back to your org structure. This is, this is-- >> I'm like a broken record. I was thinking that yesterday as I was watching CNBC, and just thinking in my mind, processing what they were announcing. I'm realizing in my head, I bet why, because I don't know, but I bet why, I speculate why he got fired, because he wasn't able to put the org structure and incentives in place to run faster, and that's what the board asked his successor is run faster, and if his successor doesn't put the org structure and the incentives in place to be an agile business. That's the definition of insanity. It's banging your head against the wall. >> If I had to add one more thing to that comment, which by the way I agree with you. If you could configure an asset in a company besides the organizational structure, so you did that, what would your next asset be? More cloud, more data-centric, what would be? >> It might be cliche, but it's totally true, I would have a cloud-first approach to everything. So we don't remember this guy called Obama anymore, but really he did a pretty revolutionary thing, when he brought in a CIO eight, nine years ago, and he made every federal government department defend a capital purchase. And they basically have to go through a multi-hundred page document to defend a capital IT acquisition, but to actually go cloud first or cloud native, didn't require almost any pre-approval at all to get funding. >> So we made it easier incentives to go cloud. >> Created incentives, and I'm a big believer that cloud is not a panacea. >> That helped Amazon, not IBM, as the CIA case now. >> I'm a big believer in life cycles, so it's not like cloud is the rubber stamp solution for every problem, but the beginning innovation phase of every new product line or revenue stream really should be in the cloud right now. The amazing services, forget about IS and all that. Look at the machine language and APIs, IoT APIs, the entire CICD pipelines that are automated and simplistic, the innovation phase for everyone should be in the crowd. Then you got to take a step back, look at that bill, get over your sticker shock, and figure out whether you can afford to stay in a cloud using maybe some of those higher-level proprietary high-margin services and whether you want to re-factor. And that's where professional services kick in, and I think that might be the next great disruption for AI, is re-factoring apps. >> I think one of the things, final question I want to get your thoughts on. Pretend that we're at Cisco and we go back to the ranch, and someone says, "Hey, what's that DevNet Create?" What's our advice to our peers, if we had an opinion that people valued inside Cisco, doubled down on DevNet Create, continue, merge it DevNet? What would your advice be? >> I'm a long time James Governor fan. Developers are the new kingmakers. Actually I think we're in this situation that's not very well understood by business leaders right now, where developers are influencing all the technology infrastructure decisions we're making, but they don't necessarily write the checks. But if you want to run an agile business, a digital business today, you can't do it without happy developers and a good developer experience, so you have to cater to their needs and their biases and so forth, and at shows like this I think, bring Cisco's large ecosystem to bear, where we can figure out how Cisco can maximize the developer experience, how partners, and I'm soon to be a Cisco partner myself at Peritus.ai can maximize their developer experience and just drive more modern business. >> Bring the developer community in with the networking, get those margins connected. Val Bercovici, cofounder of Peritus.ai, this is theCUBE with exclusive coverage of the inaugural event of Cisco's DevNet Create. I'm John Furrier, Peter Burris, returning after this short break. (electric music) >> Hi, I'm April Mitchell, and I'm the senior director.