>> Announcer: It's The Cube covering OpenStack Summit 2017 brought to you by the OpenStack Foundation, Red Hat, an additional ecosystem of support. >> Welcome back, I'm Stu Miniman joined by my cohost John Troyer. Happy to welcome back to the program the two Keynote emcees for the first two days, Jonathan Bryce who's the executive director and Mark Collier who's the COO of OpenStack Foundation. Both of you, thanks so much for joining us. >> Jonathan: Yeah, thanks for having us back. >> It's great to be on The Cube. >> Thank you for the foundation. Without your guys' support, we couldn't do this. It's our fifth year doing the show. I remember the first year, John Furrier went. They were like, "Hey, OpenStack has arrived. "The Cube's there!" And now, it's part of our regular rotation. I know our community loves it. Community, opensource, big part of the show. I wish we had two hours to tease out all the pieces, but Mark, I got to start with you. You just did a live Q&A with Edward Snowden. Somebody joked, they said the quality and the sound was too good. He was sitting in the backroom somewhere. Can you just tell us, how did this come about and how do you make that work? >> Yeah. I mean, pinch me. Is this real life? I keep asking myself 'cause it seems kind of surreal. Just briefly, I got a lot of people that ask, "How did we get connected with him?" It's kind of a funny story, but basically, several years ago when the whole story came out about somebody from the government, from NSA had leaked these documents, but nobody knew who it was. I was on vacation, it was in the summer. I forget what year, I was on vacation with family. We were in the lobby of this hotel where we were on vacation and I've been following the story with some interest. All of a sudden, I see on the TV screen in the lobby of the hotel, "Breaking news, we're about to reveal "the name of the leaker." I look up and I'm watching it and it says, "Here it is. It's Edward Snowden." The first thing I did is I pull up my phone. I immediately look and see if edwardsnowden.com was available, so I registered it thinking, "Well, this might come in handy." Some person just became the most famous person in the world, possibly. It was available, so I'm like, I'm furiously typing on my phone trying to register the domain. I register the domain edwardsnowden.com. No idea what I would actually do with it, just thinking, "If it's there, "this name is about to become really famous," so I registered it. Didn't do much with it, I just put some Twitter feeds on there, just thought, "We'll see what comes of this." A little while later as things developed, he ended up in Russia. I was contacted by some of his team that said, "We're putting together a legal defense fund. "It'd be great if we could host it at edwardsnowden.com. "Could we buy the domain from you?" I was like, "You can have it, I'll donate it. "I just grabbed it 'cause I figured "this might come in handy someday, "just was an impulse." They said, "Great, thank you. "Edward thanks you, we're going to really use "this domain for his legal defense fund webpage," and all that stuff. Overtime, I occasionally would ping them and say, "Look, the domain's free. You've got it. "I want you to have it, it's not my name. "I don't have any need, I don't have any right to this. "You guys use it, but it would be great "if he could come on the Summit thing that we do." This was three or four years ago. They were like, "Oh yeah, he would love to do it "to thank you for donating the domain," but each time we talked, it was always like, the schedule didn't lineup. I've been literally asking him for six or seven Summits. This was the first time the schedules lined up. I didn't tell anybody 'cause I thought, this is never going to happen, this is a pipe dream. I don't want to promise anything. It was only just a few weeks ago that we found out the schedule's lined up, it's on. Got connected from there. He's obviously an opensource-person, has a lot of passion behind that. We thought this is pretty interesting for our audience, so it worked out. >> All right, so Jonathan. Let's reset for a second here (Jonathan laughs) and step back. One of the things we'd love to see is the foundation is self-aware. There's always that balance when you get into, you don't want to read the press or things like that because they don't understand what we're doing or where we're going or things like that. In your opening Keynote and throughout the show, we called it, it's a little bit of a reset. If you think about where people thought OpenStack was and where it was going three years ago, it was like, the Amazon this or the cheaper VMware or how that is, where it is, where it's going, who's leading, who's involved, winning-and-losing type stuff, you guys did a good job of laying that out, so congrats on that. Take us in a little bit, and what message did you guys want to get out this week? >> Yeah, I think that you're right, we are very self-aware. I think that some of that comes from our role. At the foundation, we are not selling a product. We don't have anything to sell off the back of a truck, so to speak. What we actually really care about is moving the state of the community and the technology we produce forward. The thing that's great about that is we can look at the portfolio of technologies that we have. We can look at the things that are in the market and if we see a shift there, it's not like we have a $500 million dollar line of business that, "Uh-oh, we need to keep milking this cash cow "and turn a blind eye to these changes over here." I think over the last couple of years, I talked about a shift in what private clouds can do now and how they're built and operated. We seen that and we've sort of been teasing that out a little bit at previous Summits whether it's demos with Kubernetes or different integrations with Cloud Foundry and other things like that. What we decided this time is coming out of last year, there was a lot of news. What we saw really picking up is there would be these rumors or misperceptions that somebody would put out there, you know? Not based on fact, not based on reality. We were like, "You know what? "We can't just try to subtly hint at what's going on. "Let's just go out there and actually address "the state of things," and I think what you mentioned is actually what's at the root of a lot of these misconceptions as people look at opensource now. Because so much technology gets developed that way, they look at it and they expect it to be like the old world of IT where you need to have Microsoft versus Linux, and you need to have Oracle versus MySQL. Actually, what we see is just the cloud overall is growing so quickly. Public cloud, everybody believes that's growing. What we see is, private clouds are growing. We see that servers, there are more servers this year than there were last year. There are more virtual machines this year than there were last year. Far more containers this year than last year. All of these technologies are growing, so it's not a zero-sum game where in order for OpenStack to succeed, AWS has to lose. I think that we feel that way and we see that, but we realize that this is... We need to just go at it directly. >> Mark, I've heard good feedback from people when, you know, core, where it is, how it's matured. People like the component piece. They'd be able to take some digital pieces which, my understanding, they could do that before, it's becoming highlighted a bit. We talked about some of the opensource days and Cloud Foundry, Kubernetes. The piece where we've heard some people poking holes in is what big tent we discussed last year. Big tent, we poked a hole, is it dead? How do we reposition that? >> Yeah, that's a great question. I think first of all, one of the things that this just this strange stroke of luck that maybe turned out to be bad luck was, one of the few times when a handful of developers went off and organized something, gave it a random name and the name really stuck. It actually was almost too good of a name. You heard Big Tent and everyone's just rolling off the tongue all the time, "Big Tent, Big Tent, Big Tent," so everyone had to have an opinion about it and was like, "This is a huge change." It really wasn't meant to be a huge change. It wasn't even meant to be broadcast that widely to everyone who's just observing OpenStack. That's just kind of what happens, people talk about it. I do think that we are entering a point now when we're thinking about composable, open infrastructure, yes, you need to have different components. You need to be able to pick them, but we're also getting more serious about what things need to exist in OpenStack. I talked about that a little bit this morning. Not every single thing that we've launched needs to continue to be an OpenStack project. Whether you call it the Big Tent or not, or if you give it different names, the reality is we need to adopt and integrate technologies from other communities. Any opensource community out there is potentially developing something really powerful. >> Jonathan: Did you mention the FCB thing this morning in your, I can't remember if-- >> Yeah I mentioned it briefly. A perfect example of this is a lot of OpenStack services have said, "You know, we need to distributed lock management function "in order to evolve as a service. "Where should we go build it? "How're we going to write it?" Then, this culture of, "Well, hold on. "There are a lot of them out there, they're proven. "What about Etcd?" So the forum, which is the first time we've really had a dedicated space at the Summit for both developers and operators to be in the same room, not just next door to each other. They had a discussion yesterday on this and they said, "Yes, we're going to go forward with Etcd." That's an opensource project, very proven, it solves this particular function, it's not developed inside of OpenStack, but who cares? It's opensource. We can work, we can be friends with anybody who builds great opensource software. Let's not reinvent the wheels. I think that does represent a bit of a shift in the philosophy and culture at OpenStack of not trying to just build every single thing from scratch 'cause that's not the best thing for our users or the market. >> I think the ecosystem message and the landscape message came through really clearly. This is my first OpenStack Summit. I was very curious about what is the shape of OpenStack? Where does it fit in? Talking about the upper layers and Kubernetes and the app layers, and now talking about the overall landscape, right. Why rewrite that something like Etcd write. The whole ecosystem has grown up around OpenStack. During the 70's, the whole foundation has been working on it, all the members. One thing that impressed me, we are post-hype cycle. There are real customers here. There are people building their first clouds right now on OpenStack. Could you talk a little bit about just the community in general, the composition of it and the actual real use cases that we're seeing that happen. >> We had some new companies that spoke here for the first time, GE was one. The U.S. Army Cyber School is another one. We had some companies that came back as well. I think that you hit on a key point which is the maturity of the software. A company like GE, especially in their healthcare division, this is a highly regulated company. It's probably the most regulated company out there when you consider the things they do with aviation, nuclear power, healthcare, finance and all these things. They don't take those decisions lightly at all. I think that is an indicator of that maturity. What we see in the makeup of the community is a broader set of industries than ever before. We had strong representation among IT companies early on and continued with that, but now we have industrial companies. We have manufacturing companies like Volkswagen, BMW, you know, a number of car manufacturers, and defense companies. I think that kind of plays into that. I think the other thing that we've seen... When we talk about the OpenStack community and the platform overall, we think of it as an ecosystem that has three main parts. There's the users, which, that's why we exist. We create software for it to be used. There are the developers who are doing that, and then there's the ecosystem of companies who create commercial products and services. I think that's actually just as important. Right now, at the phase that we're at is how that is also reaching maturity. In the earlier days of OpenStack, I think that we had a lot of startups and we had a lot of activity, but the market didn't know how to consume it. It didn't understand what it was. I think that actually scared off some companies and it made a little bit of it more confusing, but as you get a few years into that, some of those companies succeed. Some of them don't succeed, but what you arrive at is a clear understanding of what the market wants, how the products should shape up. You get companies that stop trying to build it all themselves, kind of along with the not-invented-here, and they partner with people who know how to do opensource or they come up with new delivery models. I think that, actually, just as important is the maturing that we've seen in the commercial ecosystem because that leads to sustainable business models for these companies like Red Hat and Rackspace and others that then drive the development, but it also leads to clear adoption choices for users. >> One of the things that I think came out of last year at the Austin Summit was just where OpenStack fits in in this hybrid world. I think about GE, Rackspace, Red Hat, all of those companies clearly span both sides of it. Back to that winning-and-losing discussion we had at the beginning, it was always public cloud versus the private and the infrastructure piece. We know it's a multi-cloud, hybrid cloud world. How do you see that fitting in the conversations? The other piece on that, I see a large number, it was a 74% of deployment according to your latest survey, are not U.S. which is the inverse of we see such. North America's where we have a lot of public cloud adoption so does that fit in? What dynamics may be mixed up with you, Mark? >> A couple things, I would say that what we're finding is a few years ago, it was like, are we going to do cloud? Okay, now it's yes. Then it was, which app it's going to be? It's going to be as many as we can get. Then it was, are we going to do public or private? Well, we picked one. Now it's, okay, yes to everything. It's going to be cloud, we're going to put as many apps as we can. We're going to do public and private, so what happens next? Now, it's a question of where. Where do you place each workload? Some of them belong in the public cloud, some of them don't. Economics plays a big factor, performance, compliance, all the things that he said. The three C's, capabilities. I think that's the next discussion point that's happening inside of these boardrooms with CTOs and IT leaders at the major companies. How do we get a sophisticated strategy for where to place the workload? In terms of the geographic dynamic, I think one of the things Jonathan hit on yesterday is that it's just the nature of opensource that you never know where it's going to go. You just have no clue. Really, any new technology development, the market's going to go somewhere you could've never predicted like, the crystal ball is dead. It's really roadmaps or almost obsolete. It's like, you need to create a structure for how you respond and adopt to change 'cause you know it's coming. What's happened with OpenStack 'cause it's been used in all these new and different ways, and part of that's geographic. It's used to power cell phone networks in all these different countries. It's being used to fit within regulatory requirements in certain countries in data locality, both for performance and other reasons. I think that's why you see it, it's a big world out there. More than 74% of the world doesn't live in the United States, so I think we're closer to the real percentage out there. >> I want to jump in with one thing that you said that I might disagree with slightly. >> Mark: Okay, let's have a debate. On the right... >> Well, you said that these are the conversations that CTOs and CIOs are having is the strategy about how to do it. I think it's a conversation they should be having... >> Mark: Okay, fair point. >> But I think that what we see is, we see a lot of companies-- >> After they hear this, maybe they'll start talking about the right thing. >> I think that we see that, but we're kind of on the front edge of cloud adoption >> That's a good point. >> in the OpenStack community. >> Mark: I concede your point, sir. >> And I think that one of the issues that we see still is that people are thinking about it too simplistically, almost. As Larry Ellison famously said, "The IT industry is the most "fashion-driven industry out there." I think that right now, there are a lot of companies that they still think that there's some shiny object that's going to fix it all for them. Right now, it might be public cloud or containers. They've heard this word and they think that's... Never happened. Never happened in the history of IT ever before. There has never been at technology that came along and fixed the stuff before it. They all get edited. So, yes. We were talking with a CEO just this week, and it was real interesting to hear his perspective because he said that he actually thinks that the pendulum is going to shift back towards private cloud for people who run any significant amount of software. He goes, "I know that is not a popular viewpoint right now, "and if I said that to most other "technology C-level execs, "they would probably disagree with me and go, "No, cloud first, containers," but I think that just the fundamentals behind it, over the next few years, I don't know if it will shift all the way back. It may, who knows? But that's definitely something that I think is going to change from where the current fab might be. >> We'll have to have you back later to talk about how public is now moving to edge. Edge, of course, lives. >> Yeah. Oh, yes. >> Edge is the new data center, is what they have. I do have one final question before we let you go. That whole new shiny stuff? The last couple years, I'd been hearing, everybody's like, "Containers are going to subsume and take over. "DockerCon will be the new thing. "Oh wait, Kubernetes is just "going to dominate and take it over," and we have CubeCon and the CNCF. There's lots of Linux Foundation shows that do partnerships with what you do in Cloud Foundry Summit and on all these other pieces. What do you see as the future for the OpenStack Summit? Does it get pulled? This is being pulled into pieces, but for the show itself, for the foundation, and how it fits with that whole broad ecosystem of opensource. >> Well, the OpenStack Summit has always had some specific purposes. Again, this gets back to the fact that we are an opensource community and a foundation built to support that opensource community. The primary purposes of the OpenStack Summit are basically to strengthen those three pillars that I talked about earlier, especially on the software angle. Mark mentioned that this time around, we are doing what we call the forum. We used to have the Design Summit here, and we actually split that into two parts: one that's very technical and it's really gets down into implementation details. That's split out into a separate event. It happened in February, it's going to happen in September. What we did here is we set up time where developers and operators can get together and talk about strategic issues. Instead of talking about, "How do we fix this issue on line X of file Y?" they're talking about, "What should we use for distributed storage "and lock management? "Should we do Etcd? Should we do Zoo?" They're having more strategic conversation. That is a very critical piece for our community and for the people who run on it. We do a lot of education here. I think that what we've seen is that the OpenStack Summit is becoming more focused around users and the strategic needs of them as we build out the technology versus what it used to be. It originally started as a hacking event for 75 software developers. That's where I think it's going. Just to address the other point, all of the other opensource projects, a lot of them are here and we go to their events because, again, like we've been saying, it's not a zero-sum game. What we care about is that there are open alternatives and that they work well together. One of the things that I think we've seen and we've seen it proven over and over again with OpenStack is that getting communities together in person, those high-bandwidth interactions are actually really critical to getting work done and making things happen. I think they're all valuable and we're going to continue to participate in all of them. >> Yeah, well, Jonathan Bryce, Mark Collier. Really appreciate you joining us. I'm sure we'll see you at many of those other shows that The Cube will be covering throughout the years. Stay tuned with us, we've got lots more covered here at OpenStack Summit 2017 in Boston. Thanks for watching The Cube. (minimal electronic music)

>> Narrator: Live from Austin, Texas, it's theCUBE, covering KubeCon and CloudNativeCon 2017, brought to you by Red Hat, the Linux Foundation, and theCUBE's ecosystem partners. >> Okay, welcome back, everyone. This is theCUBE's exclusive coverage live here in Austin, Texas for the CNCF's two conferences, CloudNativeCon, which was yesterday, and two days, today and tomorrow, KubeCon for Kubernetes' conference. This is theCUBE, of course, from SiliconANGLE Media. I'm John Furrier with my cohost, Stu Miniman. Our next guest, Dan Kohn, is the executive director of the CNCF, the man who put it all together. Congratulations. Welcome back to theCUBE. Good to see you. >> Oh, absolutely. Thrilled to have you guys back here again. >> So you kind of doing a victory lap here now, high fiving each other? >> Dan: Great hugs. >> John: Great event. >> Laughing: I'm glad it's a good event, and I am hearing fantastic feedback that folks are thrilled to be here. But we sort of describe this moment for the organization and the community as being the end of the beginning. >> John: Yeah. >> Where we now have all the major cloud vendors, all of the biggest enterprise software companies. We have a core group of 14 projects anchored by Kubernetes, but tons and tons of work in front of us. >> And tons of success, so I'm just going to read a couple of highlights from yesterday. There's a lot today. Baidu joins the CNCF, a lot of scaling production application examples, 31 new silver end-user members joined, Alibaba Cloud update to platinum, CoreDNS 1.0, Containerd, Fluentd, Jaeger, tons of news. Obviously, we've been pumping out the coverage. Today, again, more and more great goodness. But really interesting is that you guys have put a frame around this community to allow it to grow, to fertilize the open source vibe, which is all cloud but yet scaled. And you put up a slide I want to get your reaction to that I thought was compelling yesterday during your keynote. It was the flywheel, circle, and it said projects, products, profit. >> Dan: Right. >> And not that you're promoting profit, but you're not hiding the ball, either, saying, hey, you know what? There's a lot of commercial interest in cloud, obviously. We saw AWS' success last week. And that is if you create good products in this community framework, there's profit to be had. >> Right. So first of all, I should admit to plagiarizing that slide from Linux Foundation Executive Director Jim Zemlin. >> And similarly, I think you can look at a lot of aspects... >> It's an open source feature. >> Dan: Yes. >> Free for you to use. >> John: Right. >> Similarly, I think there's a lot of ways in which Kubernetes is trying to build on the success of Linux. And Jim even describes Kubernetes as the Linux of the cloud. >> John: Yeah. >> Stu: Yeah. >> John: That's a good point. >> Dan, one of the things we've been talking around Kubernetes is you talk about scale. >> Dan: Right. >> Talk about scale of the CNCF. You have 4 to 14 projects. People are a little worried when you get all the vendors around here and there's all these projects. It's a foundation thing, it's going to go off the rails. >> Dan: Yeah. >> Customers aren't going to have a voice. How do we make sure we kind of learn from some of the things that other projects have had challenges with in the past? >> And I think that's our advantage, which is the great thing about coming later than some of the other foundations, is we can look at where they had successes and where they had issues. And our aspiration for CNCF is to get to go make entirely new mistakes rather than replicating some of the issues that have come before. And so really from the beginning of CNCF, we had a somewhat unusual and frankly a little bit cumbersome charter where I describe it at times as a three-ring circus. We have a governing board made up of the vendors that are putting a lot of money into the community, but they don't get to run the projects and they don't even get to pick the projects. Instead, they appoint six of the nine members of an independent technical oversight committee, kind of like the Supreme Court. And then we have a third group in the end-user community that I'm thrilled to say is now up to 28 members in it. They appoint one of those folks. We finally got that working. We have Sam Lambert, the director of infrastructure at GitHub, who has just made a huge commitment to Kubernetes and is moving all their infrastructure over into it. Those seven appoint the last two. And so that body, and they just had their public meeting a couple hours ago. They feel very strongly about their independence, about their reputation, that they're trying to make very good judgments based on what they're seeing in the marketplace. >> That's interesting, the three-ring circle. I like how you put it. But let's talk about the end-user piece because I think that's critical. One of the things we were commenting earlier from the Lyft folks was you have a lot of end users who have built some large-scale systems out of their own sheer necessity. >> Dan: Definitely. >> And that is now being donated in. We saw Kubernetes come in with, you shepherded beautifully, went from Google, but you've got Lyft donating an amazing product convoy. >> This first convoy has a huge amount of excitement. And what was fun was, actually, on the same stage that they contributed back in LA in September, Uber contributed a separate project. Now, unlike Uber and Lyft, the two projects are in no way competitive- >> John: Yeah. >> Like Jaeger is really fantastic tracing one. But what they have in common is that they're companies that have had to grow from nothing to extremely high scale and then had problems that they solved. And they wanted to share that expertise with us. >> I want to get your thoughts on this. Because we've been speculating, on theCUBE, we've been kind of thinking, an editorial, but just that this is all good business. Now, that's pretty obvious, right? You're starting to see this kind of contribution, the gifts that keep on giving. These are significant code. >> Dan: Yeah. >> Not like, okay, let's start a little group and huddle and build something organically. You have real goodness coming in from Google, Uber, Lyft, and there's a million others. >> Dan: Right. >> How is that changing the game? Certainly accelerating it. That's really bringing goods to the table. >> Right. I think the whole... >> You have to manage it. >> Well, and for what it's worth, I don't actually manage the projects. And so we do provide a set of services- >> John: The community? >> -to them and we help them, we market them. But one of the unusual aspects of CNCF is that the projects do actually manage themselves. A little bit of guidance from the TOC, but we really are unusual in that sense. And that's one of the reasons the projects have been... >> And what's interesting is, to connect the dots, though, one step further, you're talking about a commercial entity donating massive intellectual property in the open for all the goodness of everyone else. But yet that flywheel is continuing. They're still using it. So it is inherently commercial dynamic. >> Right. And back to that circle, I think really the underlying concept is that companies agree that sharing key parts of their infrastructure has a huge amount of value to the whole ecosystem, to each other. And then they're absolutely eager to compete above that. And so you can look at it with the public clouds where we have now Amazon, Microsoft, Google, Alibaba, IBM, Oracle all at the table. They are absolutely fierce competitors. But they're saying that this specific software infrastructure layer isn't the area that they want to compete. They want to compete on all the value-added services, customer service, et cetera. >> Dan, I wonder if you can speak to how CNCF connects to some of the broader communities out there. Things like Kata containers got announced coming out of the OpenStack group. You've got a serverless track happening here, kind of extends some of where Kubernetes is going. How does CNCF fit into the broader... >> Sure. And it's definitely the case that all the innovation out there cannot happen in CNCF. Most obviously, everything that we do, almost everything depends on Linux. And so that's our parent organization, the Linux Foundation. But we've had a good collaboration with Jonathan Bryce from OverStack. They have two booths on the floor here at the show. And we've spoken to Clear Containers and RunV, the two predecessors in the past. But the part that I'm particularly pleased with for Kata containers is that it is an OCI-compliant runtime, that's another sister organization, and is really designed to work well for Kubernetes. And then they can pitch that and let the market go decide which container runtimes they find the most valuable. >> Obviously a lot of traction here in terms of the sentiment around service meshes and pluggable lock-in textures. That's been very cool. But security came up. So I want to get your thoughts around security, obviously storage and these older models around how to deal with storage and networking. Obviously, always in the action. >> Yeah. >> But security is top of mind for everyone. How is that being addressed? You know, talk is out there... >> Sure. I mean our philosophy on this is that moving to cloud-native and particularly the continuous integration and continuous development that goes along with that is the most important step that you can do to help secure your infrastructure. And Equifax is the example everyone always brings up. But there was a case where they were using known insecure software and they didn't have the processes up to place where instead of doing quarterly updates or monthly updates, you want to be doing dozens of updates per day. And a cloud-native infrastructure allows you to do that. >> What's next for you? Because you've got great traction with both community response, and the community has been absolutely amazing, the quality of people, level has been great, but also at the funding sponsors. You've got a lot of people that are involved. What's next? What happens next? What do you envision happening? What's the plan, and then how do you view that evolving? >> Well, I hate to fall into the buzzword implosion here, but if you go back to the crossing the chasm metaphor, I think we're still very much just in the early adopter phase. 2018 could very well be the moment that we jump over to the early majority. And I do feel like this whole community now has the velocity to do that and that we're on track for it. But as that happens, there's just far, far more people who need to be educated so they understand the projects and the options and how to work with them. And then hopefully they go from just being consumers of these technologies to contributors and that we can welcome them into our community and hopefully get the advantage of their expertise as well. >> I want to get your thoughts on a comment that Stu and I were talking about. Stu, you and I were talking about the notion of value creation above the stack, and then how Kubernetes, although some could say being commoditized, but it's also creating value because with that consistency of Kubernetes, you can now create value. So we believe, and I want to get your reaction to this, because we think a whole new ecosystem dynamic will emerge of a new kind of ecosystem. And if this new app developer combined with software engineering, which is really going on, you're talking about the cloud, the app developers will just build in value, that value creation will be rewarded. That's where monetization will be happening. >> And if I could build off that... >> John: Yeah. >> Dan, I loved one of your opening comments. You quoted, "exciting times for boring infrastructure, "maybe too exciting." So this week we've been teasing out there's a lot of work to make that infrastructure boring. You've got everybody on this floor, the CNCF board, lots of new projects making that. Where the action is and what this is going to create is that application monetization and the speed and agility of being able to create these cool new cloud-native applications out there. So it's interesting dynamic, spans broad pieces of this, layers of the stack there. >> Yeah. Well, I will point out that there was an odd level of unanimity of just a ton of different leaders in the community, in keynotes from Craig McLuckie and Chen Goldberg and others where they all agree that Kubernetes is not by any means the ultimate answer or the final answer. I think everybody now expects to see Kubernetes as a core aspect of the infrastructure for software for the next decade or more. But there's a belief that there's a whole ton of value that needs to be added above it, particularly to try and show for a regular application developer who just has a PHP app or no-GS microservices or anything else what's the easiest way to go from having a piece of software and deploying it effectively. >> Dan, so it's interesting. You watch the people on the outside. They're like, oh, look at Kubernetes. They're all holding hands and saying Kumbaya. We know there's some spirited debates that happen- >> Dan: Definitely. >> In the code, some projects that are sometimes competing up there. Why has the community come together, and where are some of the areas that we still need to work on and improve to help customers going forward? >> And again, I think they have the big advantage of having watched other communities that didn't value community and consensus and the ability to work through their issues. And so thankfully, we just have a ton of really capable engineers who also have some of those social or personal qualities that they care about working these things out. And to date, at least, I think most of those disagreements have been settled pretty amicably and in a positive direction. I think there's still huge swathes of this space that are still up in the air. Storage is an obvious one where there's a ton of work going on in a storage working group of CNCF. Serverless is another where I think everyone agrees that the application deployment model of AWS Lambda is really exciting and has things that people should replicate and should be brought over to Kubernetes. But how that should happen, what the software is, et cetera, there's still, in fact, we have our first serverless track today here at KubeCon where several different competing approaches are all talking about what they'd like to do. >> Awesome stuff. And you also announced some dates for next year, December 11 and 13 in Seattle. >> Dan: Yes. >> Okay. >> Dan: That's a year from now. >> November 14 and 15 in Shanghai. >> Now, you and I met in Hangzhou in the lobby, which was just amazing. But I certainly am hoping to convince you to go back to China with us. This will be our first event... >> I got a three-year visa. >> Good, yeah, that's the exactly right one. But this will be our first event in China, which I think is just a huge opportunity. We now have Baidu, Tencent, Huawai, ZTE, a number of startups. There's just so much excitement for this space over there that we're really excited to satisfy. >> Stu: And Copenhagen in May. >> And that's the last one. Thank you. May 2 to 4 in Copenhagen, and we're really excited for the event, to bring it to Europe and the rest of the world. >> Okay. So you've been working like a dog, you've been working hard. I've seen you in China. It's serendipitous. But it's not without being mentioned that this has been great effort by your team and the Linux Foundation and Jim and the whole team. But congratulations. Are you having a pinch me moment? I know it's too early to do a victory lap. >> But you've got to be pretty excited. >> Yeah. It really has been a great thing for the foundation that we sort of accomplished many of our 2018 and 2019 goals this year. But I'm sure we're going to find plenty of stuff to do next year. >> And your goal for the next 6 to 12 months, what's on your top three to-do's, continue the momentum? Share your API for... >> Yeah. What's great is that we really have plenty of members. We'd always like to add new ones and serve the ones we have better. But right now, the focus is really about providing better services to our projects. All of them feel overworked. They would love help on documentation, on marketing, on messaging about it, and some of them need help with testing development and other things. So that's really what we're buckling down on. >> Great community are going to test them, being here on the ground, personally present at creation. And I was standing there with J.J. and Lew Tucker, OpenStack three years ago, talking about Kubernetes. We were kind of ripping. We couldn't have imagined, then, obviously, they bolted it on last year with your event. Now second year here, huge community... >> But you have 4,100 folks here, is more than the previous four events combined. >> Yeah, awesome. >> So it really is exciting. >> TheCUBE, always on the ground. And sometimes the squirrel finds a nut. We found a cloud-native foundation, part of the Linux Foundation. CNCF, Cloud-Native Compute Foundation, really a new, growing, and relevant community for cloud and a new way to do software and reimagine the future from software engineering to full application development, a new way. This is theCUBE's coverage, and we are here live in Austin. More live coverage after this short break. We'll be right back. [Techno Music]

(energetic music) >> Narrator: Live from Boston, Massachusetts it's the Cube, covering OpenStack Summit 2017 brought to you by the OpenStack Foundation, Red Hat, and additional ecosystem support. >> Hi and welcome back to SiliconANGLE TV's production of the Cube here at OpenStack Summit 2017 in Boston. I'm Stu Miniman joined with my co-host for the week, John Troyer. As you can see behind us, the day 2 keynotes letting out. John, it's always interesting to look at these shows. They had some demos that were awesome, a couple of demos were the demo gods were not smiling on them. They had Edward Snowden live via Q&A. They had Brian Stevens, who we're going to be talking with in a little bit, the CTO of Google, who was on The Early Start. For me, they're a little up and down. There's some of the vendor pitches in there, people are like, "Oh I have a great demo," and then you say, "Come to my booth "and see a bunch of my sessions." So, a little bit uneven and disjointed, which has been a some of the feedback you get about OpenStack in general over the last few years as to all those pieces come together. But yeah, what are your early thoughts coming out of the day 2 keynote? >> Well, it was definitely a keynote focused at the OpenStack community. We started off with open source and talking about the importance of open source, which is a little bit odd, because everyone here know that. I did like the message that OpenStack was composed of different projects, that it was a piece of the puzzle, not the whole puzzle. You and I both noted VMware's Scott Lowe tweeted, "It's good to the OpenStack Foundation talking about being a part of the overall solution, not the overall solution." I mean, as one example, they mentioned using etcd, which is a distributed key value store, instead of writing their own. Etcd powers Kubernetes. Your would be insane in 2017 to rewrite or distribute a key value pair, sorb at this point. Because, it's just out there, it's mature. You know, OpenStack has been around for seven years. There's been a lot of ecosystem grown up around them. >> Yeah, yeah. A couple of pieces on that. One is, there was a message about like, oh I can now take the individual components of OpenStack. I could actually do that before. I've noted, I've talked to a number of software companies, that when you did down into what they're doing, oh what do you know, there's, you know, there's Syndrr. Or, there's, you know, something in there, just as when I use AWS, I can use some of the individual components, same thing with OpenStack. It's not a monolith. There are the individual pieces. But, they're highlighting that a little bit more. They're saying use some of the pieces. The other thing, on the open source in general, they noted that like, in the artificial intelligence machine learning space, like, everyone that you see is using open source. Everything from Google and TensorFlow, is one that gets highlighted a lot. Amazon made a big push at their show about what they're doing with, you know, some of the machine learning. I can't remember right now, the program on there. But, right, in some of these emerging spaces, open source is the defacto way to do that. We had, in one of the conversations we had yesterday with one of the Cysco Distinguished Engineers, you know, it used to be standards. Now, open source really drives a lot of that. I actually got a quick conversation with Martin Casado, who had, you know, worked on a lot of open source things before Vmware acquired him. And, now he's at Andreessen Horowitz looking at all the open source models. So, unfortunately Martin didn't have enough time to come on the program, but we've had him on many times. Yeah, so sometime he's going to do that. >> Stu, I have a question. >> Stu: Yeah. >> The message today of being part of an ecosystem and being a componentized, open source set of projects, does that detract or add to this conversation around OpenStack Core versus Big Tent? >> I think Big Tent is dying. We talked to a number of the participants yesterday and said it was a little overblown. It does not mean that some pieces might still get worked on, but it's the core components. And you know, when dug into the survey, how many of the pieces do we really need? We want to make sure the Core works. I can have that distribution if I want to do what is OpenStack. When they highlighted those components, it wasn't 27 different projects there. You know, I think it was a handful of like six. >> Yeah. >> That were there. So, you know Swift and Syndrr, some interesting, cool little graphics. It was ironic, I tell you. The little graphic there, that was like a scary looking bear. It's like, I wouldn't want to run into him in a cartoon alley. Uh, but (laughs). >> Yeah, I did tweet. Yeah, there was an angry bear, kind of a poisonous spider, and a horse's behind. So, I'm not quite sure about the marketing there. But (laughs). >> What is the message you're sending? But, there's some fun. We've got, you know, Mark Collier and Jonathan Bryce coming on soon. We can ask them, you know, was this the community? And are there just some people that have a funny sense of humor, and this is how they show it? >> I did love the demos in today's talk, Stu. I especially liked, they spun up, live on stage, 15 from scratch, OpenStack clouds. And then, had them all join a CockroachDB cluster. I thought that was kind of cool and amazing. >> Yeah, absolutely. You talk about that hybrid, multi cloud world, showing it, you know, in reality, how that works. Pretty neat, and you know, you can actually see some applicability as to how that would fit into a customer environment. And, kudos to all the people. I mean, these were live, no net demos, not Camtasia, not some prerecorded things. Because like, oh wait, this thing's not quite ready to be able to be bootable, or you know, let me come in. I mean, they're up there on stage doing it. The wifi all seemed to work fine. That wasn't a challenge, but yeah, it was pretty cool. >> Well again, trying to give the message that OpenStack is indeed not a science project. That it's live, that it's configurable, that it's stable, that it's installable. And, I think that kind of message of stability, and configurability, and simplicity maybe is one of the ones they're trying to hit here today. >> Yeah, last thing I want to hit on, John, is I want to get your opinion. We throw out the term "open" a bunch. And, I'm watching some of the other industry things, and they say "open" when they mean "choice," as opposed to "open" as in "open source." So, you know, we see Google here, and Google talks about open. So many things that are now open source, a lot of times started out as a Google white paper or something. As we all say, we're all using open source which Google was using 10 years ago, right? You know, MapReduce, and Borg, and Spanner, and some of those things eventually get their way out. I've got some view points on this, but love to get your take first, yeah. >> Well, I mean, definitely it was an homage to open source this morning. In some ways, it was kind of a dig at AWS and Amazon, which uses a lot of open source tools, but does not share back. You know, OpenStack is clearly open source, and they were emphasizing that. I don't know. What are your thoughts, Stu? >> Yeah, it's, customers now, it used to be if you said open source, you know, go back 10, 15 years, and it was like, ooh, no. Now, open source is, a lot of times, a plus, something that they're asking for. Many companies are contributing and engaging in that. OpenStack is a great example of companies that have participated, you know, in helping to build OpenStack. That being said, you know, I always go to, you know, what's the problem to be solved, what's the solution that solves it. And, if it happens to be a little bit pre standard, or not 100% open source, most companies are fine with that. We were at Red Hat Summit last week with the Cube though, and everything they do is 100% open source. They're building their business. Their customers are really happy. So, you know, open source still has a little bit of a double edged sword as to how you do it. But, you know, open source absolutely, there's no question of if open source, it's how much, and to what extent, and where it fits. >> Sure, there is an ecosystem of providers here. There's always lock-in when you make a technical choice. But, in this case, I think they've successfully were trying to show off that there is a choice of clouds. There is an open, a set of open source components that you can mix and match. And so, that actually ties in very well to the interview with Edward Snowden. >> Yeah, absolutely, yeah. It was, and last point. Edward Snowden, towards the end he said fear is, I think the quote was, "the most powerful weapon in the world today." From a political statement, is what he's doing. Fear in IT is a powerful weapon. We know that, you know, enterprise and inertia, you know, tend to go together. With my background in networking, I used to draw these timelines. And, say, from when the time the standard was done to when, you know, the early majority adopt, is often times a decade. So, the technology adoption, moving the operational, we know the people piece is always tough to do, moving my applications. We think people are definitely moving faster, but fear is definitely something that holds them back. What do you see, john? >> Sure, I think the through line of the whole morning was about choice and diversity. Edward Snowden talked about the centralization of information services like Facebook, Google, and Twitter. And I think, and I think by implication, Amazon. And, I think the message that he was giving to the OpenStack crowd was look, you are enabling a multitude of services and a multitude of clouds, and that actually is a lever, a cultural lever against the over centralization of commercial forces, which are a little bit outside people's control. >> Yeah, so John, thanks for helping me wrap up day one. As always, we welcome our audience to please send us feedback. John and I are both pretty active on Twitter, very easy to get in touch with. We are at so many shows. You can check out SiliconANGLE TV. See where we're at. If we're not at a show that you think we should be at, reach, there's contact information at the top. If there's guests that we should have on our program, we're always looking for feedback. Love to get, especially those end user stories, talking about with interesting startups. So, we've got two more days of live coverage. So, for John and myself, stay with us. And, thanks, as always, for watching The Cube. (exciting music)