 Live from the Julia Morgan Ballroom in San Francisco, extracting the signal from the noise, it's the Cube, covering Structure 2015. Hey, welcome back everybody. Jeff Frick here with the Cube. We are live in downtown San Francisco. It's Structure 15. It's the rebirth of Structure after some issues earlier this year. So everybody's psyched to have Structure back. Great audience here at the Julia Morgan Ballroom. So got the Cube out here and we're really excited to be joined by a former woman of the week from DockerCon, Marianna Tessel, SVP Engineering of Docker. Welcome. Thank you. Well, thank you for having me. Absolutely. So you just got back. We talked a little bit off air from Barcelona and DockerCon Europe. So I wanted to give us an update. How was the vibe over there? How was the show? What's going on on that side of the Atlantic? Yeah, I literally just came back and it was actually amazing. It's our second conference in Europe. And we went, I think we more than tripled the number of attendees. Tickets were completely sold out. The vibe really was outstanding. Obviously for me, it was a big, this adrenaline rush and, you know, seeing how everybody are exciting, use it, being able to demo our products, being able to get responses from customers and users. Amazing. Yeah. So there was probably nothing hotter than Docker this last summer. Last time we saw you was at DockerCon. Everybody's putting container ships on their corporate pages. I mean, Docker was really the hottest, hottest thing going. But, you know, now kind of the buzz has mellowed a little bit. And now you guys are getting into work. So kind of give us an update of what's happened since the summer till now. Right. I mean, we've been really busy building our stack and building our products. And as users use Docker, they evolve in their use. And we want to be ready there with the products they need. We have put a lot of emphasis on orchestration. We just, with 1.9, we released Swarm. And we talked in the conference about the scale you can achieve with it. And we actually, again, at the conference, announced few new products, which has been amazing. And online product, we acquired a company called Tutom. We demoed that. And we also announced a product called the Docker Universal Control Plane, which is kind of your management layer, orchestration layer, that allows you to manage your containers. Docker native, so lots of new products to show. That's what we've been doing. Listening to users and trying to provide what they need. Right. And it's interesting because you came from ViaWare before. So you know a lot about the cloud. You know a lot about virtualization. And one of the things is we keep abstracting away from the hardware, away from things. Then we have to add this kind of management layer. So you kind of have to trade off management and orchestration for this virtualization. How do you see that kind of evolving? What do you see in the marketplace? How are customers really adopting that? Right. I mean, I think the need for orchestration comes from the fact that when you create an app, it's usually complicated apps that has multiple microservices or containers to pick your flavor. But it's not just like, hey, one thing and you run it. It's a bunch of things and you run and you need to orchestrate amongst them. So I think the complexity really comes from the fact that applications tend to be quite complex and contain multiple parts or services. Right. So the other thing, you run engineering, which is great. And it's always an interesting challenge to me. How do you deal with the challenge of kind of supporting open source and having your engineers support open source and be that as a real poor piece of who you are at the same time, they've got to get other work done that's not necessarily the open source component that supports some of your direct stuff. How do you manage that from ahead of engineering to make sure that people are allocating their time in kind of the appropriate ways? Right. It's obviously something that we are trying to do really, really well and we understand we want to be very true to our open source contributors and audience as well as build commercial solutions. And actually in a funny way or in an interesting way even our internal teams, they relate to open source in the way that other companies would. So when we need, when our internal products need something from open source, they will do what an external company would do. So instead of saying, oh I have a dependency, go and do it for me, what it will do they will actually create the code and contribute and wait for the PR to be merged. So sometimes internally we see the same, again we will behave the same way that external companies will behave with the open source. So I think we have a good balance with this and actually recently gave a presentation about it and preparing to that we looked at how much of the contributions are external and 70% of the contributions to the Docker open source are external. So again we have a really good balance with open source and commercial and driving both of these and find a way to relate that it's true to open source. One is such an important part of people's, who they are and how they contribute and kind of the feedback they get back from the community that's so different than just kind of working on your own thing for your own company. Very, very different and very, very powerful. It could be more like, you need a different setup but it's actually very, very powerful to work with the community, get the feedback, get their contributions, being able to interact back with them. Super powerful way to work on a big open source fan. Right and then when you're putting your roadmap out and how you're kind of working down obviously a group of features a way to improve the product. Now you've got this kind of open source contribution. How does that work in? Is it pulling you different directions? Are you using it to augment where you need specific help? How does that interplay with your own kind of product roadmap and direction? Right, so, you know, actually the fact that we get external contribution sometimes take our products to a very interesting and compelling directions that we haven't, you know, thought about. An example would be we work to the community to have this feature called Checkpoint and Restore which is an amazing feature. It's like, you know, from the VM world it's like V-motions for containers. You know, this was a collaboration with the external community and again the community will come up with ideas that will be wow and often yes it does change a little bit our roadmap but we also try to publish like hey at least Docker internally here's what the kind of things we're working on so the community can contribute to that. We also try to explain what is the best way to contribute. You know, like if a company works on a secret project on the side and create this huge, huge change to Docker and they'll submit what we call a PR bomb, you know, then we, we're not sure, then it's going to be harder to merge and the right way to work is again like the same way that we work internally is with like small chunks so we can consume it and review it in time and get it in. But I would say the roadmap is a combination of what we want to do internally and things that the community want and we kind of mid-in the middle. Adjust as you, course correct as you go. Exactly. Kind of like the Odyssey, right? You got a course correct that she... Exactly. Very good. So last thing, so kind of what are your priorities now? What are you guys looking at? What can we expect when we see you at DockerCon in six months or so? You really want me to tell you? You're going to see a lot of amazing surprises. I really know because the community is going to help contribute and we'll work our way there. Exactly. Any top priorities that you're working on? Yeah, I mean, again, we want to continue to evolve the platform, make it more scale. I mean, we see companies really move their use from development to production and we understand Docker is now heavily using production. We understand it comes with needs around quality, stability. So you're going to see more and more investment security. We made huge investment in security. So are you going to see more of that? Kind of the boring but super important things to make it runnable for people? And then you'll see us invest in more and more creative things and understanding how it would make it super easy to use, it's super sophisticated and obviously on the commercial side we're going to introduce more and more products that we believe would be very helpful for users. Yeah, so again, evolving in all areas of orchestration, dev tools, you know, all of that we do, you'll see a lot of evolution there and the surprise effect from the community which is, you know. Which we don't know. Which we don't know. But that's important because there was kind of a little bit of a soft undercurrent at DockerCon, which was, you know, a lot of people are using containers a lot in dev, but you know, not necessarily a huge uptake in the production side. So it sounds like that's really changing quite a bit. Yeah, when we see because we survey and we see also external servers that come back and we see a really big amount of users using it in production. And remember, I think last we spoke, it was a DockerCon US and we had just experimental networking feature. Guess what, it just went GA recently, just a few weeks ago, so it's not fully production. So we kind of understand that we need to get there and we need to kind of provide these solutions. Awesome. Well, Marianna, thanks for stopping by. Hopefully you can catch up on your sleep coming back from Europe. Absolutely. I'm Jeff Freik with Marianna Tesla from Docker. Thanks for watching theCUBE. We are live in downtown San Francisco at Structure 15. We'll be right back after this short break. Thanks for watching.