(upbeat electronic music) >> Narrator: Live, from Santa Clara, California, it's theCube. Covering Open Networking Summit 2017. Brought to you by The Linux Foundation. >> Woman: Sure. Um, so, yeah, as you were saying, OpenDaylight really kind of kicked things off from a open source networking standpoint. I mean, there were certainly other open source controllers earlier, in sort of the market life cycle, but they kind of never really made their way out of the universities. OpenDaylight was the first that really had a lot of commercial participation and uptake, kind of in the real world, so to speak. Um, so with that, I think there was a lot of learning that happened, both on the vendor's side, with regard to open source, as well as on the user side. Um, and as the OpenDaylight platform matured and started coming to fruition, we started seeing a lot of other projects sort of both below at the platform layer as well as further up the stack. So at this point, and we've been talking about this quite a bit here at ONS, um, we've been talking a lot about the whole open networking stack that has sort of come to fruition now. You know, really low level stuff, DPDK was just announced today. Fido, which is sort of big data for networking. Then all the way up the stack to ONAP, which was just announced last month. ONAP is a bringing together of the ECOMP Project that was started by AT&T and then they brought it to The Linux Foundation and Open-O, which actually sort of germinated within The Linux Foundation with a lot of input from, um, a number of small vendors, as well as major carriers, particularly in Asia. So, um, bringing those things together at the orchestration layer, and so now we've got this sort of whole stack. Some of it, a lot of it is Linux Foundation projects, some of it is other projects with other open source foundations. All of which we work with very collaboratively across all those different projects. >> Man: Right, right. >> But at this point, we're really kind of looking at how do we enable people to consume this a little bit more easily from the user side? And then also from the developer side. There are a lot of developers who are involved in multiple different projects. Which of course means that they're spread very thin across all those projects. And we're looking at how do we make it a more feasible and scalable activity for them? >> Right. >> So for example, you know, OpenDaylight is upstream of a lot of other projects. There are a lot of other projects that have a lot of dependencies on OpenDaylight. So how do we streamline the release train in such a way that, you know, everybody gets what they need at the time that they need it, so they can do their releases on a timely basis and so forth and so on. And that just, you know, that makes things a lot easier from a developer standpoint. That also sort of naturally increases the, improves the integration points between those projects which is, of course, better for users. >> Man: Right. >> Um, so those are a lot of the things that we have in motion sort of across the Linux Foundation, um, and I think that the other thing that we've really seen over the last year come to fruition is a lot of the early adopters of OpenDaylight in particular have now spent enough time working with the open source community, either through their vendors or increasingly directly themselves, that they kind of get this open source thing, and they understand kind of what the processes are and why we do things they way they do. >> Right. >> And so they're willing to take a much more active role. AT&T is a prime example of that. They were working on ECOMP themselves internally, and they, very quickly, came to the realization that in order to scale it as quickly as they needed to, I mean, they were putting tens of thousands of their developers through specialized boot camps, right? >> Man: Right, right. >> The networking people to become networking developers. But at the same point, you just can't push people through the system that fast enough, nor can you hire enough people that fast enough. And so that's why this has decided to bring it to the open source community. >> Man: It seems like there's kind of an acceleration of carving out some piece of what was proprietary and putting it out to continue the development in an open source world. >> Any "why", you kind of answered the question just now in terms of there's not enough people. But more interestingly, you talked about some open source stuff just never gets going. What are some of the real secrets that make an open source project run? >> Yeah. >> Versus those that don't, or you know, die on the vine. >> Yeah. Um, there are a lot of different components, of course, like with anything. Some of it is technical, right? Do you have the right architecture? Is it one that can scale? Is it extensible? Are the right kinds of people involved in the project? Is the project being informed by the right kinds of people? So if you go and build something that nobody needs, either because you don't have the right people involved, or because you're not open to that feedback, it's going to die on the vine. So, you know, a successful project really has to have a strong community around it. And it's a-- >> Jeff: Chicken and egg. >> Chicken and egg thing, right? How do you get a strong community? Well, you have the right processes in place, but you also make sure that you have the right people involved so that they can build the right kind of thing. And that they have the skills to do it effectively. >> Right. And then the other interesting trend we're seeing is, The Linux Foundation is becoming kind of the hub where you put these things, um, to grow, and as you said, really to cross-pollinate with the other open source projects that have all these interdependencies. >> And that seems to be an accelerating trend as well, as least from the outside looking in. >> Lisa: Yeah, no, it absolutely is. And I think we learned a lot with, with OpenDaylight and also with OpenStack. You know, when OpenStack started, and OpenStack of course is even older than OpenDaylight, but when OpenStack started, I think there was all kinds of euphoria in the industry because open source was relatively new to infrastructure, and infrastructure people, it was like, "Oh, I can build everything "that I ever wanted to build now!" Um, and so there was this sort of irrational exuberance about feature proliferation. In some ways, kind of at the expense of platform stability initially. And at a certain point, the users, again, started getting involved and said, "That's great. We need the thing to actually work. "At scale, in real world environments. "Please focus on that." And you know, that's the real beauty and strength of open source, is when you have users who care, and see the possibility of a project, they can be actively involved and actively influence where the focus of the project is going to be. And that's how you get to something that's going to be useful to people quickly. >> Thank you. >> Well, it'd be great to hear a little bit more about how you-- on these, I'm always kind of mystified as an analyst or a journalist or whatever, when you see these things. The press release comes out, "ONAP is the new thing", right? There's a new thing every week. How do you ensure the success? How do you get the momentum behind it? I imagine there's a lot of stuff that's been happening behind the scenes for ONAP. >> Lisa: Yep. We try not to keep it too behind the scenes. It has always been part of open source culture and what's proven to be a best practice is openness and transparency of not just the code itself but the processes around it. >> Scott: Mhm. >> Um, if people feel like they understand what's going on, that things aren't being hidden from them, that they can have a voice. >> Scott: Right. >> They're much more actively willing to participate. So that's really kind of the key to building any kind of community. >> And how do you work with a big carrier, like, I mean, the fascinating part about this for me is for our viewers who don't know what ONAP and ONOS and ODL are, it's basically all this carrier software that's becoming open source and they're just putting it out there, saying, "It's no longer our family jewels. "Everybody can use it." I mean, that's a big leap for an AT&T, you know? Tell us how you work with AT&T or Verizon or some of these big, gigantic organizations. Like, they just hand you a thumb drive? (laughter) How do you get the intellectual property? How's that process start? >> In the case of AT&T, they reached out to The Linux Foundation and said, "We want and need to do this. "Help us do it. We don't know how this works. "Help us, teach us." But it's very much a, you know, a big part of the role of The Linux Foundation in all of this project proliferation and so forth is teaching people how to do open source effectively. Because, again, it's not just about throwing coders at a problem, 'cause you can do that inside your own organization as well. It's understanding how to do that in a collaborative manner, how to carve off what parts to open source, 'cause AT&T's ECOMP platform, not all of it has been open source. Some portion of it, the stuff that's really important and proprietary and is considered the crown jewels, that has stayed internal, but they've shared a reasonable, fairly large percentage of the base platform with the open source community. And learning to draw that line is an art. And figuring out what is commodity and really could and should be shared with the rest of the world so we're not all reinventing the same wheel. >> Scott: Right. >> But rather than having ten developers here doing that and ten developers here and duh duh duh dah, we can put 30 developers, all working together, to get the same thing more quickly. That shifted mindset can take a little bit of time, a bit of education, and that's kind of part of what The Linux Foundation brings to that process of onboarding new open source projects. >> Jeff: Right. And then on the other end, I always think of Randy Bias. He's one of our favorite guests, Especially with OpenStack, and he knows a couple OpenStack Silicon Valleys ago, where he was somewhat critical on the other end, saying we also have to kind of reign things in, and you have all this risks of stuff going all over the place, and how do you kind of have some organization at the top end because of successful growth can drive a bunch of different agendas and things can get forked. It's not a simple thing to manage. >> No, and we've tried different models and different approaches within different projects and we've learned a lot from that. OpenDaylight was very much a, you know, you guys figure it out, hands-off kind of model. Other open source projects have been very top-down, from their governant structure to everything else. Others, like Open-O are kind of in-between where they did specifically set up an architecture committee that was composed of the leading members of the project because, again, Open-O in particular is touching the business layer of these carriers. So they really need that architecture to be meeting their specifications. >> Right, right. >> Sort of a lower layer, so it's a little bit less critical. There are lots of different models and sort of a gradation of top-down versus bottom-up and, you know, let a thousand flowers bloom. (chuckling) There are pluses and minuses to all of them. I think that we've been sort of learning as we go through all of these different projects what works. And different--sometimes it's worth shifting the model and starting out one way and shifting as you go along as the project matures, too. >> Jeff: But the net-net, which I think, you said at the beginning, is that big companies are now really learning how to operate effectively in this world, in this open source paradigm. It's matured way, way, way beyond what, we used to always joke, years ago, is a free puppy, you know? (laughing) >> You know, I mean, I think Tokus understand now that it is, yes, it's a free puppy. You still have to do lots of work. I think that understanding is sort of starting to trickle into the enterprise. I still have, every time I do a briefing, people will ask me to tell them about my product, and I say, "I don't have a product. I can't sell you anything." I help bring together a bunch of building blocks that you and your vendors can put together. But I don't have a product. And that, you know, that's a major mind shift for, especially, enterprise IT, where they're used to buying things off the shelf. >> Right. >> So larger enterprises, um, are starting again. They tend to take their cues from the carriers as things get proven out in the carrier world. And so we're starting to see that the same level of understanding and also, drivers in large, especially very distributed types of organizations, where they have 50, a hundred, hundreds of different sites around the world that they need to have a centralized few of in some fashion. And the only way they can get there is with SDN and they have a very strong preference, very clear preference for open source. >> Scott: How big is The Linux Foundation now? >> Lisa: By what metric? >> Uh, people, I guess. >> Lisa: Oh, people. Um... We're a few hundred, no more. But it's not just--we're not the ones doing all the work, right? We organize things. We help things happen. We help teach people. We provide the infrastructure. >> It seems to be growing very fast, like new projects are being added and merged. >> Lisa: But again, it's vendors and it's users. >> Very grassroots. >> Yeah. We help provide the ground, the legal framework, and the technical test facilities and things like that, and kind of the organizational guide rails. But we're here to help, we're not the ones doing the work. >> Right, right. Alright, Lisa, so I'll give you the last word before we sign off here. As you look forward to 2017, what are some of your top priorities for this next year? >> Lisa: Yeah, so, several things. First order is really enabling our users to really be successful with the projects that they already have in hand. In many cases, they're well through the phase of proof of concept and all the way onto production, and we just want to make sure that they're continuing to get everything they want out of the project and supporting them and supporting their vendors. And really building out the commercial ecosystem around it, so that they have a strong base of support. So that's one thing. Certainly on the OpenDaylight side, with some of the newer projects, it's really about figuring out what are the best practices that we can implement for this project, for this project, and for this project in order to make sure that they're successful. And a lot of that, again, is that whole harmonization effort that we have going on. >> Right, right. Alright, Lisa Caywood. She knows all about bringing open source to the enterprise, and thanks for taking a few minutes out of your day. >> Thank you very much for having me. >> Absolutely. I'm Jeff Frick, he's Scott Raynovich. You're watching theCube from Open Networking Summit 2017 in Santa Clara, California. We'll be back after the short break. Thanks for watching. (electronic music)

>> From our studios, in the heart of Silicon Valley, Palo Alto, California, this is a CUBE Conversation. >> Welcome to this CUBE Conversation here in Palo Alto, California. I'm John Furrier, host of theCUBE. We are here with Arpit Joshipura, GM of Networking, Edge, IoT for the Linux Foundation. Arpit, great to see you again, welcome back to theCUBE, thanks for joining us. >> Thank you, thank you. Happy to be here. >> So obviously, we love the Linux Foundation. We've been following all the events; we've chatted in the past about networking. Computer storage and networking just doesn't seem to go away with cloud and on-premise hybrid cloud, multicloud, but open-source software continues to surpass expectations, growth, geographies outside the United States and North America, just overall, just greatness in software. Everything's an abstraction layer now; you've got Kubernetes, Cloud Native- so many good things going on with software, so congratulations. >> Well thank you. No, I think we're excited too. >> So you guys got a big event coming up in China: OSS, Open Source Summit, plus KubeCon. >> Yep. >> A lot of exciting things, I want to talk about that in a second. But I want to get your take on a couple key things. Edge and IoT, deep learning and AI, and networking. I want to kind of drill down with you. Tell us what's the updates on the projects around Linux Foundation. >> Okay. >> The exciting ones. I mean, we know Cloud Native CNCF is going to take up more logos, more members, keeps growing. >> Yep. >> Cloud Native clearly has a lot of opportunity. But the classic in the set, certainly, networking and computer storage is still kicking butt. >> Yeah. So, let me start off by Edge. And the fundamental assumption here is that what happened in the cloud and core is going to move to the Edge. And it's going to be 50, 100, 200 times larger in terms of opportunity, applications, spending, et cetera. And so what LF did was we announced a very exciting project called Linux Foundation Edge, as an umbrella, earlier in January. And it was announced with over 60 founding members, right. It's the largest founding member announcement we've had in quite some time. And the reason for that is very simple- the project aims at unifying the fragmented edge in IoT markets. So today, edge is completely fragmented. If you talk to clouds, they have a view of edge. Azure, Amazon, Baidu, Tencent, you name it. If you talk to the enterprise, they have a view of what edge needs to be. If you talk to the telcos, they are bringing the telecom stack close to the edge. And then if you talk to the IoT vendors, they have a perception of edge. So each of them are solving the edge problems differently. What LF Edge is doing, is it is unifying a framework and set of frameworks, that allow you to create a common life cycle management framework for edge computing. >> Yeah. >> Now the best part of it is, it's built on five exciting technologies. So people ask, "You know, why now?" So, there are five technologies that are converging at the same time. 5G, low latency. NFV, network function virtualization, so on demand. AI, so predictive analytics for machine learning. Container and microservices app development, so you can really write apps really fast. And then, hardware development: TPU, GPU, NPU. Lots of exciting different size and shapes. All five converging; put it close to the apps, and you have a whole new market. >> This is, first of all, complicated in the sense of... cluttered, fragmented, shifting grounds, so it's an opportunity. >> It's an opportunity. >> So, I get that- fragmented, you've got the clouds, you've got the enterprises, and you've got the telcos all doing their own thing. >> Yep. >> So, multiple technologies exploding. 5G, Wi-Fi 6, a bunch of other things you laid out, >> Mhmm. >> all happening. But also, you have all those suppliers, right? >> Yes. >> And, so you have different manufacturers-- >> And different layers. >> So it's multiple dimensions to the complexity. >> Correct, correct. >> What are you guys seeing, in terms of, as a solution, what's motivating the founding members; when you say unifying, what specifically does that mean? >> What that means is, the entire ecosystem from those markets are coming together to solve common problems. And I always sort of joke around, but it's true- the common problems are really the plumbing, right? It's the common life cycle management, how do you start, stop, boot, load, log, you know, things like that. How do you abstract? Now in the Edge, you've 400, 500 interfaces that comes into an IoT or an edge device. You know, Zigbee, Bluetooth, you've got protocols like M2T; things that are legacy and new. Then you have connectivity to the clouds. Devices of various forms and shapes. So there's a lot of end by end problems, as we call it. So, the cloud players. So for LF Edge for example, Tencent and Baidu and the cloud leaders are coming together and saying, "Let's solve it once." The industrial IoT player, like Dynamic, OSIsoft, they're coming in saying, "Let's solve it once." The telcos- AT&T, NTT, they're saying "Let's solve it once. And let's solve this problem in open-source. Because we all don't need to do it, and we'll differentiate on top." And then of course, the classic system vendors that support these markets are all joining hands. >> Talk about the business pressure real quick. I know, you look at, say, Alibaba for instance, and the folks you mentioned, Tencent, in China. They're perfecting the edge. You've got videos at the edge; all kinds of edge devices; people. >> Correct. >> So there's business pressures, as well. >> The business pressure is very simple. The innovation has to speed up. The cost has to go down. And new apps are coming up, so extra revenue, right? So because of these five technologies I mentioned, you've got the top killer apps in edge are anything that is, kind of, video but not YouTube. So, anything that the video comes from 360 venues, or drones, things like that. Plus, anything that moves, but that's not a phone. So things like connected cars, vehicles. All of those are edge applications. So in LF Edge, we are defining edge as an application that requires 20 milliseconds or less latency. >> I can't wait for someone to define- software define- "edge". Or, it probably is defined. A great example- I interviewed an R&D engineer at VMware yesterday in San Francisco, it was at the RADIO event- and we were just riffing on 5G, and talking about software at the edge. And one of the advances >> Yes. >> that's coming is splicing the frequency so that you can put software in the radios at the antennas, >> Correct. Yeah. >> so you can essentially provision, in real time. >> Correct, and that's a telco use case, >> Yeah. >> so our projects at the LF Edge are EdgeX Foundry, Akraino, Edge Virtualization Engine, Open Glossary, Home Edge. There's five and growing. And all of these software projects can allow you to put edge blueprints. And blueprints are really reference solutions for smart cities, manufacturing, telcos, industrial gateways, et cetera et cetera. So, lots of-- >> It's kind of your fertile ground for entrepreneurship, too, if you think about it, >> Correct; startups are huge. >> because, just the radio software that splices the radio spectrum is going to potentially maybe enable a service provider market, and towers, right? >> Correct, correct. >> Own my own land, I can own the tower and rent it out, one radio. >> Yep. >> So, business model innovations also an opportunity, >> It's a huge-- >> not just the business pressure to have an edge, but-- >> Correct. So technology, business, and market pressures. All three are colliding. >> Yeah, perfect storm. >> So edge is very exciting for us, and we had some new announcements come out in May, and more exciting news to come out in June, as well. >> And so, going back to Linux Foundation. If I want to learn more. >> LFEdge.org. >> That's kind of the CNCF of edge, if you will, right? Kind of thing. >> Yeah. It's an umbrella with all the projects, and that's equivalent to the CNCF, right. >> Yeah. >> And of course it's a huge group. >> So it's kind of momentum. 64 founding members-- >> Huge momentum. Yeah, now we are at 70 founding members, and growing. >> And how long has it been around? >> The umbrella has been around for about five months; some of the projects have been around for a couple of years, as they incubate. >> Well let us know when the events start kicking in. We'll get theCUBE down there to cover it. >> Absolutely. >> Super exciting. Again, multiple dimensions of innovation. Alright, next topic, one of my favorites, is AI and deep learning. AI's great. If you don't have data you can't really make AI work; deep learning requires data. So this is a data conversation. What's going on in the Linux Foundation around AI and deep learning? >> Yeah. So we have a foundation called LF Deep Learning, as you know. It was launched last year, and since then we have significantly moved it forward by adding more members, and obviously the key here is adding more projects, right. So our goal in the LF Deep Learning Foundation is to bring the community of data scientists, researchers, entrepreneurs, academia, and users to collaborate. And create frameworks and platforms that don't require a PhD to use. >> So a lot of data ingestion, managing data, so not a lot of coding, >> Platforms. >> more data analyst, and/or applications? >> It's more, I would say, platforms for use, right? >> Yeah. >> So frameworks that you can actually use to get business outcomes. So projects include Acumos, which is a machine learning framework and a marketplace which allows you to, sort of, use a lot of use cases that can be commonly put. And this is across all verticals. But I'll give you a telecom example. For example, there is a use case, which is drones inspecting base stations-- >> Yeah. >> And doing analytics for maintenance. That can be fed into a marketplace, used by other operators worldwide. You don't have to repeat that. And you don't need to understand the details of machine learning algorithms. >> Yeah. >> So we are trying to do that. There are projects that have been contributed from Tencent, Baidu, Uber, et cetera. Angel, Elastic Deep Learning, Pyro. >> Yeah. >> It's a huge investment for us. >> And everybody wins when there's contribution, because data's one of those things where if there's available, it just gets smarter. >> Correct. And if you look at deep learning, and machine learning, right. I mean obviously there's the classic definition; I won't go into that. But from our perspective, we look at data and how you can share the data, and so from an LF perspective, we have something called a CDLA license. So, think of an Apache for data. How do you share data? Because it's a big issue. >> Big deal. >> And we have solved that problem. Then you can say, "Hey, there's all these machine learning algorithms," you know, TensorFlow, and others, right. How can you use it? And have plugins to this framework? Then there's the infrastructure. Where do you run these machine learning? Like if you run it on edge, you can run predictive maintenance before a machine breaks down. If you run it in the core, you can do a lot more, right? So we've done that level of integration. >> So you're treating data like code. You can bring data to the table-- >> And then-- >> Apply some licensing best practices like Apache. >> Yes, and then integrate it with the machine learning, deep learning models, and create platforms and frameworks. Whether it's for cloud services, for sharing across clouds, elastic searching-- >> And Amazon does that in terms of they vertically integrate SageMaker, for instance. >> That's exactly right. >> So it's a similar-- >> And this is the open-source version of it. >> Got it- oh, that's awesome. So, how does someone get involved here, obviously developers are going to love this, but-- >> LF Deep Learning is the place to go, under Linux Foundation, similar to LF Edge, and CNCF. >> So it's not just developers. It's also people who have data, who might want to expose it in. >> Data scientists, databases, algorithmists, machine learning, and obviously, a whole bunch of startups. >> A new kind of developer, data developer. >> Right. Exactly. And a lot of verticals, like the security vertical, telecom vertical, enterprise verticals, finance, et cetera. >> You know, I've always said- you and I talked about this before, and I always rant on theCUBE about this- I believe that there's going to be a data development environment where data is code, kind of like what DevOps did with-- >> It's the new currency, yeah. >> It's the new currency. >> Yeah. Alright, so final area I want to chat with you before we get into the OSS China thing: networking. >> Yeah. >> Near and dear to your heart. >> Near and dear to my-- >> Networking's hot now, because if you bring IoT, edge, AI, networking, you've got to move things around-- >> Move things around, (laughs) right, so-- >> And you still need networking. >> So we're in the second year of the LF Networking journey, and we are really excited at the progress that has happened. So, projects like ONAP, OpenDaylight, Tungsten Fabric, OPNFV, FDio, I mean these are now, I wouldn't say household names, but business enterprise names. And if you've seen, pretty much all the telecom providers- almost 70% of the subscribers covered, enabled by the service providers, are now participating. Vendors are completely behind it. So we are moving into a phase which is really the deployment phase. And we are starting to see, not just PoCs [Proofs of Concept], but real deployments happening, some of the major carriers now. Very excited, you know, Dublin, ONAP's Dublin release is coming up, OPNFV just released the Hunter release. Lots of exciting work in Fido, to sort of connect-- >> Yeah. >> multiple projects together. So, we're looking at it, the big news there is the launch of what's called OVP. It's a compliance and verification program that cuts down the deployment time of a VNF by half. >> You know, it's interesting, Stu and I always talk about this- Stu Miniman, CUBE cohost with me- about networking, you know, virtualization came out and it was like, "Oh networking is going to change." It's actually helped networking. >> It helped networking. >> Now you're seeing programmable networks come out, you see Cisco >> And it's helped. >> doing a lot of things, Juniper as well, and you've got containers in Kubernetes right around the corner, so again, this is not going to change the need, it's going to- It's not going to change >> It's just a-- >> the desire and need of networking, it's going to change what networking is. How do you describe that to people? Someone saying, "Yeah, but tell me what's going on in networking? Virtualization, we got through that wave, now I've got the container, Kubernetes, service mesh wave, how does networking change? >> Yeah, so it's a four step process, right? The first step, as you rightly said, virtualization, moved into VMs. Then came disaggregation, which was enabled by the technology SDN, as we all know. Then came orchestration, which was last year. And that was enabled by projects like ONAP and automation. So now, all of the networks are automated, fully running, self healing, feedback closed control, all that stuff. And networks have to be automated before 5G and IoT and all of these things hit, because you're no longer talking about phones. You're talking about things that get connected, right. So that's where we are today. And that journey continues for another two years, and beyond. But very heavy focused on deployment. And while that's happening, we're looking at the hybrid version of VMs and containers running in the network. How do you make that happen? How do you translate one from the other? So, you know, VNFs, CNFs, everything going at the same time in your network. >> You know what's exciting is with the software abstractions emerging, the hard problems are starting to emerge because as it gets more complicated, end by end problems, as you said, there's a lot of new costs and complexities, for instance, the big conversation at the Edge is, you don't want to move data around. >> No, no. >> So you want to move compute to the edge, >> You can, yeah-- >> But it's still a networking problem, you've still got edge, so edge, AI, deep learning, networking all tied together-- >> They're all tied together, right, and this is where Linux Foundation, by developing these projects, in umbrellas, but then allowing working groups to collaborate between these projects, is a very simple governance mechanism we use. So for example, we have edge working groups in Kubernetes that work with LF Edge. We have Hyperledger syncs that work for telecoms. So LFN and Hyperledger, right? Then we have automotive-grade Linux, that have connected cars working on the edge. Massive collaboration. But, that's how it is. >> Yeah, you connect the dots but you don't, kind of, force any kind of semantic, or syntax >> No. >> into what people can build. >> Each project is autonomous, >> Yeah. >> and independent, but related. >> Yeah, it's smart. You guys have a good view, I'm a big fan of what you guys are doing. Okay, let's talk about the Open Source Summit and KubeCon, happening in China, the week of the 24th of June. >> Correct. >> What's going on, there's a lot of stuff going on beyond Cloud Native and Linux, what are some of the hot areas in China that you guys are going to be talking about? I know you're going over. >> Yeah, so, we're really excited to be there, and this is, again, life beyond Linux and Cloud Native; there's a whole dimension of projects there. Everything from the edge, and the excitement of Iot, cloud edge. We have keynotes from Tencent, and VMware, and all the Chinese- China Mobile and others, that are all focusing on the explosive growth of open-source in China, right. >> Yeah, and they have a lot of use cases; they've been very aggressive on mobility, Netdata, >> Very aggressive on mobility, data, right, and they have been a big contributor to open-source. >> Yeah. >> So all of that is going to happen there. A lot of tracks on AI and deep learning, as a lot more algorithms come out of the Tencents and the Baidus and the Alibabas of the world. So we have tracks there. We have huge tracks on networking, because 5G and implementation of ONAP and network automation is all part of the umbrella. So we're looking at a cross-section of projects in Open Source Summit and KubeCon, all integrated in Shanghai. >> And a lot of use cases are developing, certainly on the edge, in China. >> Correct. >> A lot of cross pollination-- >> Cross pollination. >> A lot of fragmentation has been addressed in China, so they've kind of solved some of those problems. >> Yeah, and I think the good news is, as a global community, which is open-source, whether it's Europe, Asia, China, India, Japan, the developers are coming together very nicely, through a common governance which crosses boundaries. >> Yeah. >> And building on use cases that are relevant to their community. >> And what's great about what you guys have done with Linux Foundation is that you're not taking positions on geographies, because let the clouds do that, because clouds have-- >> Clouds have geographies, >> Clouds, yeah they have agents-- >> Edge may have geography, they have regions. >> But software's software. (laughs) >> Software's software, yeah. (laughs) >> Arpit, thanks for coming in. Great insight, loved talking about networking, the deep learning- congratulations- and obviously the IoT Edge is hot, and-- >> Thank you very much, excited to be here. >> Have a good trip to China. Thanks for coming in. >> Thank you, thank you. >> I'm John Furrier here for CUBE Conversation with the Linux Foundation; big event in China, Open Source Summit, and KubeCon in Shanghai, week of June 24th. It's a CUBE Conversation, thanks for watching.

>> From the SiliconANGLE Media office in Boston, Massachusetts, it's theCUBE. Now here are your hosts, Dave Vellante and Stu Miniman. >> Hi everybody, Dave Vellante here with Stu Miniman. We're here to unpack the recent acquisition that IBM announced of Red Hat. $34 billon acquisition financed with cash and debt. And Stu, let me get us started. Why would IBM spend $34 billion on Red Hat? Its largest acquisition to date of a software company had been Cognos at $5 billion. This is a massive move. IBM's Ginni Rometty called this a game changer. And essentially, my take is that they're pivoting. Their public cloud strategy was not living up to expectations. They're pivoting to hybrid cloud. Their hybrid cloud strategy was limited because they didn't really have strong developer mojo, their Bluemix PaaS layer had really failed. And so they really needed to make a big move here, and this is a big move. And so IBM's intent, and Ginni Rometty laid out the strategy, is to become number one in hybrid cloud, the undisputed leader. And so we'll talk about that. But Stu, from Red Hat's perspective, it's a company you're very close to and you've observed for a number of years, Red Hat was on a path touting a $5 billion revenue plan, what happened? Why would they capitulate? >> Yeah Dave, on the face of it, Red Hat says that IBM will help it further its mission. We just listened to Arvin Krishna from IBM talking with Paul Cormier at Red Hat, and they talked about how they were gonna keep the Red Hat brand alive. IBM has a long history with open source. As you mentioned, I've been working with Red Hat, gosh, almost 20 years now, and we all think back to two decades ago, when IBM put a billion dollars into Linux and really pushed on open source. So these are not strangers, they know each other really well. Part of me looks at these from a cynicism standpoint. Somebody on Twitter said that Red Hat is hitting it at the peak of Kubernetes hype. And therefore, they're gonna get maximum valuation for where the stock is. Red Hat has positioned itself rather well in the hybrid cloud world, really the multicloud world, when you go to AWS, when you go to the Microsoft Azure environment, you talk to Google. Open source fits into that environment and Red Hat products specifically tie into those environments. Remember last year, in Boston, there's a video of Andy Jassy talking about a partnership with Red Hat. This year, up on stage, Microsoft with Azure partnering deeply with Red Hat. So Red Hat has done a nice job of moving beyond Linux. But Linux is still at its core. There definitely is concern that the operating system is less important today than it was in the past. It was actually Red Hat's acquisition of CoreOS for about $250 million earlier this year that really put a fine point on it. CoreOS was launched to be just enough Linux to live in this kind of container and Kubernetes world. And Red Hat, of course, like we've seen often, the company that is saying, "We're going to kill you", well you go and you buy them. So Red Hat wasn't looking to kill IBM, but definitely we've seen this trend of softwares eating the world, and open sources eating software. So IBM, hopefully, is a embracing that open source ethos. I have to say, Dave, for myself, a little sad to see the news. Red Hat being the paragon of open source. The one that we always go to for winning in this space. So we hope that they will be able to keep their culture. We've had a chance, many times, to interview Jim Whitehurst, really respected CEO. One that we think should stay involved in IBM deeply for this. But if they can keep and grow the culture, then it's a win for Red Hat. But still sorting through everything, and it feels like a little bit of a capitulation that Red Hat decides to sell off rather than keep its mission of getting to five billion and beyond, and be the leading company in the space. >> Well I think it is a bit of a capitulation. Because look, Red Hat is roughly a $3 billion company, growing at 20% a year, had that vision of five billion Its stock, in June, had hit $175. So while IBM's paying a 60% premium off of its current price, it's really only about 8 or 9% higher than where Red Hat was just a few months ago. And so I think, there's an old saying on Wall Street, the first disappointment is never the last. And so I think that Red Hat was looking at a long slog. They reduced expectations, they guided lower, and they were looking at the 90-day shot clock. And this probably wasn't going to be a good 'nother couple of years for Red Hat. And they're selling at the peak of the market, or roughly the peak of the market. They probably figured, hey, the window is closing, potentially, to do this deal. Maybe not such a bad time to get out, as opposed to trying to slog it out. Your thoughts. >> Yeah, Dave, I think you're absolutely right. When you look at where Red Hat is winning, they've done great in OpenStack but there's not a lot of excitement around OpenStack. Kubernetes was talked about lots in the announcement, in the briefings, and everything like that. I was actually surprised you didn't hear as much about just the core business. You would think you would be hearing about all the companies using Red Hat Enterprise Linux around the world. That ratable model that Red Hat really has a nice base of their environment. It was talking more about the future and where Kubernetes, and cloud-native, and all of that development will go. IBM has done middling okay with developers. They have a strong history in middleware, which is where a lot of the Red Hat development activity has been heading. It was interesting to hear, on the call, it's like, oh well, what about the customers that are using IBM too say, "Oh well, if customers want that, we'll still do it." What about IBM with Cloud Foundry? Well absolutely, if customers wanna still be doing it, they'll do that. So you don't hear the typical, "Oh well, we're going to take Red Hat technology "and push it through all of IBM's channel." This is in the IBM cloud group, and that's really their focus, as it is. I feel like they're almost limiting the potential for growth for Red Hat. >> Well so IBM's gonna pay for this, as I said, it's an all cash deal. IBM's got about 14 and a half billion dollars on the balance sheet. And so they gotta take out some debt. S&P downgraded IBM's rating from an A+ to an A. And so the ratings agency is going to be watching IBM's growth. IBM said this will add 200 basis points of revenue growth over the five year CAGR. But that means we're really not gonna see that for six, seven years. And Ginni Rometty stressed this is not a backend loaded thing. We're gonna find revenue opportunities through cross-selling and go-to-market. But we have a lot of questions on this deal, Stu. And I wanna sorta get into that. So first of all, again, I think it's the right move for IBM. It's a big move for IBM. Rumors were that Cisco might have been interested. I'm not sure if Microsoft was in the mix. So IBM went for it and, as I said, didn't pay a huge premium over where their stock was back in June. Now of course, back in June, the market was kind of inflated. But nonetheless, the strategy now is to go multi-cloud. The number one in the multi-cloud world. What is that multi-cloud leadership? How are we gonna measure multi-cloud? Is IBM, now, the steward of open source for the industry? To your point earlier, you're sad, Stu, I know. >> You bring up a great point. So I think back to three years ago, with the Wikibon we put together, our true private cloud forecast. And when we built that, we said, "Okay, here's the hardware, and software, "and services in private cloud." And we said, "Well let's try to measure hybrid cloud." And we spent like, six months looking at this. And it's like, well what is hybrid cloud? I've got my public cloud pieces, and I've got my private cloud pieces. Well there's some management layers and things that go in between. Do I count things like PaaS? So do you save people like Pivotal and Red Hat's OpenShift? Are those hybrid cloud? Well but they live either here or there. They're not usually necessarily helping with the migration and moving around. I can live in multiple environments. So Linux and containers live in the public, they live in the private, they don't just fly around in the ether. So measuring hybrid cloud, I think is really tough. Does IBM plus Red Hat make them a top leader in this hybrid multi-cloud world? Absolutely, they should be mentioned a lot more. When I go to the cloud shows, the public cloud shows, IBM isn't one of the first peak companies you think about. Red Hat absolutely is in the conversation. It actually should raise the profile of Red Hat because, while Red Hat plays in a lot of the conversations, they're also not the first company that comes to mind when you talk about them. Microsoft, middle of hybrid cloud. Oracle, positioning their applications in this multi-cloud world. Of course you can't talk about cloud, any cloud, without talking about Amazon's position in the marketplace. And SAS is the real place that it plays. So IBM, one of their biggest strengths is that they have applications. Dave, you know the space really well. What does this mean vis-à-vis Oracle? >> Well let's see, so Oracle, I think, is looking at this, saying, alright. I would say IBM is Oracle's number one competitor in the enterprise. You got SAP, and Amazon obviously in cloud, et cetera, et cetera. But let me put it this way, I think Oracle is IBM's number one competitor. Whether Oracle sees it that way or not. But they're clearly similar companies, in terms of their vertical integration. I think Oracle's looking at this, saying, hey. There's no way Oracle was gonna spend $34 billion on Red Hat. And I don't think they were interested in really spending any money on the alternatives. But does this put Canonical and SUSE in play? I think Oracle's gonna look at this and sort of message to its customers, "We're already number one in our world in hybrid cloud." But I wanna come back to the deal. I'm actually optimistic on the deal, from the standpoint of, I think IBM had to make a big move like this. Because it was largely just bumping along. But I'm not buying the narrative from Jim Whitehurst that, "Well we had to do this to scale." Why couldn't they scale with partners? I just don't understand that. They're open. This is largely, to me, a services deal. This is a big boon for IBM Services business. In fact, Jim Whitehurst, and Ginni even said that today on the financial analyst call, Jim said, "Our big constraint was "services scale and the industry expertise there." So what was that constraint? Why couldn't they partner with Accenture, and Ernie Young, and PwC, and the likes of Deloitte, to scale and preserve greater independence? And I think that the reason is, IBM sees an opportunity and they're going hard after it. So how will, or will, IBM change its posture relative to some of those big services plays? >> Yeah, Dave, I think you're absolutely right there. Because Red Hat should've been able to scale there. I wonder if it's just that all of those big service system integrators, they're working really closely with the public cloud providers. And while Red Hat was a piece of it, it wasn't the big piece of it. And therefore, I'm worried on the application migration. I'm worried about the adoption of infrastructure as a service. And Red Hat might be a piece in the puzzle, but it wasn't the driver for that change, and the move, and the modernization activities that were going on. That being said, OpenShift was a great opportunity. It plays in a lot of these environments. It'll be really interesting to see. And a huge opportunity for IBM to take and accelerate that business. From a services standpoint, do you think it'll change their position with regard to the SIs? >> I don't. I think IBM's gonna try to present, preserve Red Hat as an independent company. I would love to see IBM do what EMC did years ago with VMware, and float some portion of the company, and truly have it at least be quasi-independent. With an independent operating structure, and reporting structure from the standpoint of a public company. That would really signal to the partners that IBM's serious about maintaining independence. >> Yeah now, look Dave, IBM has said they will keep the brand, they will keep the products. Of all the companies that would buy Red Hat, I'm not super worried about kinda polluting open source. It was kinda nice that Jim Whitehurst would say, if it's a Red Hat thing, it is 100% open source. And IBM plays in a lot of these environments. A friend of mine on Twitter was like, "Oh hey, IBM's coming back to OpenDaylight or things like that." Because they'd been part of Cloud Foundry, they'd been part of OpenDaylight. There's certain ones that they are part of it and then they step back. So IBM, credibly open source space, if they can let Red Hat people still do their thing. But the concern is that lots of other companies are gonna be calling up project leads, and contributors in the open source community that might've felt that Red Hat was ideal place to live, and now they might go get their paycheck somewhere else. >> There's rumors that Jim Whitehurst eventually will take over IBM. I don't see it, I just don't think Jim Whitehurst wants to run Z mainframes and Services. That doesn't make any sense to me. Ginni's getting to the age where IBM CEOs typically retire, within the next couple of years. And so I think that it's more likely they'll bring in somebody from internally. Whether it's Arvin or, more likely, Jim Kavanaugh 'cause he's got the relationship with Wall Street. Let's talk about winners and losers. It's just, again, a huge strategic move for IBM. Frankly, I see the big winners is IBM and Red Hat. Because as we described before, IBM was struggling with its execution, and Red Hat was just basically, finally hitting a wall after 60-plus quarters of growth. And so the question is, will its customers win? The big concern I have for the customers is, IBM has this nasty habit of raising prices when it does acquisitions. We've seen it a number of times. And so you keep an eye on it, if I were a Red Hat customer, I'd be locking in some attractive pricing, longterm. And I would also be calling Mark Shuttleworth, and get his take, and get that Amdahl coffee cup on my desk, as it were. Other winners and losers, your thoughts on some of the partners, and the ecosystem. >> Yeah, when I look at this and say, compare it to Microsoft buying GitHub. We're all wondering, is this a real game changer for IBM? And if they embrace the direction. It's not like Red Hat culture is going to just take over IBM. In the Q&A with IBM, they said, "Will there be influence? Absolutely. "Is this a marriage of equals? No. "We're buying Red Hat and we will be "communicating and working together on this" But you can see how this can help IBM, as to the direction. Open source and the multi-cloud world is a huge, important piece. Cisco, I think, could've made a move like this. I would've been a little bit more worried about maintaining open source purity, if it was somebody like Cisco. There's other acquisitions, you mentioned Canonical and SUSE are out there. If somebody wanted to do this, the role of the operating system is much less important than it is today. You wouldn't have seen Microsoft up on stage at Red Hat Summit this year if Windows was the driver for Microsoft going forward. The cloud companies out there, to be honest, it really cements their presence out there. I don't think AWS is sitting there saying, "Oh jeez, we need to worry." They're saying, "Well IBM's capitulated." Realizing that, "Sure they have their own cloud, "and their environment, but they're going to be "successful only when they live in, "and around, and amongst our platform of Amazon." And Azure's gonna feel the same way, and same about Google. So there's that dynamic there. >> What about VMware? >> So I think VMware absolutely is a loser here. When I went back to say one of the biggest strengths of IBM is that they have applications. When you talk about Red Hat, they're really working, not only at the infrastructure layer, but working with developers, and working in that environment. The biggest weakness of VMware, is they don't own the applications. I'm paying licenses to VMware. And in a multi-cloud world, why do I need VMware? As opposed to Red Hat and IBM, or Amazon, or Microsoft, have a much more natural affinity for the applications and the data in the future. >> And what about the arms dealers? HPE and Dell, in particular, and of course, Lenovo. Wouldn't they prefer Red Hat being independent? >> Absolutely, they would prefer that they're gonna stay independent. As long as it doesn't seem to customers that IBM is trying to twist everybody's arms, and get you on to Z, or Power, or something like that. And continues to allow partnerships with the HPEs, Dells, Lenovos of the world. I think they'll be okay. So I'd say middling to impact. But absolutely, Red Hat, as an independent, was really the Switzerland of the marketplace. >> Ginni Rometty had sited three growth areas. One was Red Hat scale and go-to-market. I think there's no question about that. IBM could help with Red Hat's go-to-market. The other growth vector was IBM's products and software on the Red Hat stack. I'm less optimistic there, because I think that it's the strength of IBM's products, in and of themselves, that are largely gonna determine that success. And then the third was Services. I think IBM Services is a huge winner here. Having the bat phone into Red Hat is a big win for IBM Services. They can now differentiate. And this is where I think it's gonna be really interesting to see the posture of Accenture and those other big guys. I think IBM can now somewhat differentiate from those guys, saying, "Well wait, "we have exclusive, or not exclusive, "but inside baseball access to Red Hat." So that's gonna be an interesting dynamic to watch. Your final thoughts here. >> Yeah, yeah, Dave, absolutely. On the product integration piece, the question would be, you're gonna have OpenAPIs. This is all gonna work with the entire ecosystem. Couldn't IBM have done more of this without having to pay $34 billion and put things together? Services, absolutely, will be the measurement as to whether this is successful or not. That's probably gonna be the line out of them in financials, that we're gonna have to look at. Because, Dave, going back to, what is hybrid, and how do we measure it? What is success for this whole acquisition down the line? Any final pieces to what we should watch and how we measure that? >> So I think that, first of all, IBM's really good with acquisitions, so keep an eye on that. I'm not so concerned about the debt. IBM's got strong free cash flow. Red Hat throws off a billion dollars a year in free cash flow. This should be an accretive acquisition. In terms of operating profits, it might take a couple of years. But certainly from a standpoint of free cash flow and revenue growth, I think it's gonna help near-term. If it doesn't, that's something that's really important to watch. And then the last thing is culture. You know a lot of people at these companies. I know a lot of people at these companies. Look, the Red Hat culture drinks the Kool-Aid of open. You know this. Do they see IBM as the steward of open, and are they gonna face a brain drain? That's why it's no coincidence that Whitehurst and Rometty were down in North Carolina today. And Arvin and Paul Cormier were in Boston today. This is where a lot of employees are for Red Hat. And they're messaging. And so that's very, very important. IBM's not foolish. So that, to me, Stu, is a huge thing, is the culture. Dave, IBM is no longer the navy suit with the red tie, and everybody buttoned down. People are concerned about like, oh, IBM's gonna give the Red Hat people a dress code. Sure, the typical IBMer is not in a graphic tee and a hoodie. But, Dave, you've seen such a transformation in IBM over the last couple of decades. >> Yeah, definitely. And I think this really does, in my view, cement, now, the legacy of Ginny Rometty, which was kinda hanging on Watson, and Cognitive, and this sort of bespoke set of capabilities, and the SoftLayer acquisition. It, now, all comes together. This is a major pivot by IBM. I think, strategically, it's the right move for IBM. And I think, if in fact, IBM can maintain Red Hat's independence and that posture, and maintain its culture and employee base, I think it does change the game for IBM. So I would say, smart move, good move. Expensive but probably worth it. >> Yeah, where else would they have put their money, Dave? >> Yeah, right. Alright, Stu, thank you very much for unpacking this announcement. And thank you for watching. We'll see you next time. (mellow electronic music)

(upbeat music) >> Live from Orlando, Florida, it's theCUBE covering Cisco Live 2018, brought to you by Cisco, NetApp, and theCUBE's ecosystem partnership. (upbeat music) >> Hello, welcome back everyone to the live CUBE coverage here in Orlando, Florida for Cisco Live 2018. I'm John Furrier with my co-host Stu Miniman. Three days days of wall-to-wall live coverage, we have Mandy Whaley, senior director of developer experience at Cisco DevNet and Par Merat, who is the senior director of community and ecosystem for DevNet. Mandy, great to see you, CUBE alumni. Every single time we had theCUBE with DevNet team, Par, great to see you. Congratulations, first of all. >> Thank you. >> Thanks for coming on. >> Thank you, we're happy to be here. >> Congratulations, so, really kind of a proud moment for you guys, and I want to give you some mad props on the fact that you guys have built a successful developer program, DevNet and DevNet Create for Cloud Native, over a half a million registered, engaged users, of developers using it. Not just people who come to the site. >> Correct. >> Right. >> Real developers. For an infrastructure enterprise company, that's a big deal, congratulations. >> It is, thank you, thank you. We were just chatting this morning about the really early days of DevNet at Cisco Live, and the first year of DevNet Create. And it's been great to see that community grow. And see, early on we had this vision of bringing the application developers and the infrastructure engineers together, and cross-pollinating those teams, and having them learn about each other's fields, and then build these programmable infrastructure enabled apps, and that's really, that synergy is happening within the community, and it's great to see them exchanging ideas here at events like this. >> And so we love to talk about seminal moments, and obviously DevOps drove a lot of the Cloud, and Chuck Robbins, your CEO said, "Without networking, there'd be no Cloud." True statement, absolutely, but Stu and I have always talked about the role of a network engineer, and that the power that they used to have in the enterprise is still due. It used to be the top people running the networks, mission critical, obviously security, but it's not about a retraining. It's about a path, and I think what you guys have done in success is you've shown a path where it's not about pivoting and being relevant and retraining to get a new job, it's been an extension of what they already know, >> An incentive. and I think that's very refreshing, and I think that's the real discovery. >> And we've been able to grow, because I think in our foundational years, we really spent a lot of time providing the content and the skill training, and what Mandy likes to say is, "We met them where they are." So no question was too novice. Likewise, if they were a little more advanced, we could direct them and point them in that same direction. So those early years, where, Mandy, we were just reminiscing about the first DevNet-- >> Coding 101? >> Yes, exactly, she wrote it over the weekend, and we rolled that whole event out, literally, in three months. >> And what year was that, just to kind of, this is an important seminal moment. >> 2014. >> May of 2014. >> 2014. >> 2014, the seeds of we should do something, and you guys have had certifications. We're looking at CCIEs, you go back to 1993 all the way now to 2018, so it's not like you guys are new to certification and training. It's just taking the IQ of network people, and giving them some insight. So what happened in 2014? Take us through the, obviously you bootstrapped it. >> Yes. (laughs) >> What happened, what happened next? >> We did. >> Everyone's like, whoa, >> So-- >> we can't, we're not, we're staying below the stack here. >> Well, we knew there was a lot of buzz around SDN and programmability, and we both actually, I should even back up further. We were both on the DevNet team when the DevNet program was Powerpoints, so we weren't even there yet. >> Right, when we were just planning what it even could be, like the ideas of having a developer program, and like Par was saying, we knew SDN was coming. We knew Network Controllers were coming. We didn't know what they were gonna be called, we didn't know what those APIs looked like, but we said, "The network engineers are gonna need "to know how to make REST API calls. "They're gonna need to know how to operate in Python." And so we started this program building around that vision before the portfolio is where it is today. Like today, now, we have APIs across the whole portfolio, Data Center, service provider, enterprise, and then up and down from the devices, all the way to controllers, up to the analytics level. So the portfolio's really filled out, and we've been able to bring that community along with it, which has been great. >> I want to dig into the north/south, east/west and that whole, kind of the Cloud paradigm, but I got to ask you, on a personal question, although relevant to the DevNet success. Was there a moment where, actually the seminal moments of 2014, was there a moment where you were like, "Wow, this is working." and like the, you know, (laughs) pinch me moment, or was it more of, "We got to get more resources, this is not just, "this thing's flying." >> Well it's always that. That's always the challenge. >> When was the point where >> We are, >> you said, "This is actually >> We are very-- >> "the best path, it's working, double down." When was that happening? >> I mean, I think after we started teaching those very early coding coding classes, I got this, like, flood of email from people who had attended them that said, "I took this task, I automated it, "it saved my team months of work," and getting that flow of information back from the community was early signs to me, from the technical level of, there's value, this is gonna take off, and then I think we just saw that kind of grow and grow. >> Mushroom, just kept it going. >> The other thing that I heard from a network engineer, which really resonated with me, was, you were saying, the network guy or gal likes to be there and solve the problem, and they're sort of at this deep level of control. And what I heard them say about the programmability skills was that that was another tool that they added to their sort of toolbox that let them be that person in the moment, solving that problem. And they could just solve it in a new way, so hearing the network engineers say that they have adopted programmability in that fashion, that let me know that that was gonna work, I think. >> All right, so let's get into some of the meat and potatoes, because you guys have some really good announcements. We saw you have the code ecosystem that you announced at DevNet Create, which is your emerging Cloud Native worlds coming together. That's available now. >> Yes, it's fully released. >> So take a minute to, so give us the update. >> Yes, so DevNet Code Exchange is developer.cisco.com/codeexchange so you can go there, it's live, and the idea behind this was we wanted to make it easy for the community to contribute, and also to discover code written by the community. So it's on GitHub. You can go and search on GitHub, but you get back a ton of hits if you go search Cisco on GitHub, which is great, but what we wanted to have was a curated list that you can filter by product, by language. I sometimes joke that it's like Zappos for sample code cause you can go on and say, "I want black boots, "you know the two inch heel." You can say, "I want, I want code for DNA Center, "or ACI, and I want it in Python," and then see all of the repositories submitted by the community. And then the community can also share their codes. "Hey, I've been working on this project. "I'm gonna add it to Code Exchange, so that other people "can build off of it and find it." So it's really about this community contribution, which is a strategic initiative for DevNet for this year. >> Mandy, how does that tie into other networking initiatives happening in the industry? I think of OpenDaylight, a lot of stuff happening, Docker comes this week, Kubernetes, and networking's a critical piece of all of these environments. >> Yeah, so some of the projects that you'll find in Code Exchange are things that relate. So we have some really good open-source community projects around YANG models and the tooling to help you deal with YANG models. So those might be in Code Exchange, but those are also part of the OpenDaylight community, and being worked in that. So because it is all open-source, because it is freely shared, and it's really just a way to improve discoverability, we can share easily back and forth between those communities. >> The Code Exchange is designed to really help people peer-to-peer work together and reuse code, but in the classic >> Reuse code within >> open-source ethos. >> the community. Exactly. >> Okay, so Par, you have something going on with Ecosystem Exchange. >> We do. >> Okay, so it sounds like Code Exchange, ecosystem partners, matchmaking service. What is it, take a minute to explain. >> It's kinda the next level up, and what I think we have to understand is, when we've got Code Exchange and Ecosystem Exchange under the umbrella of exchange, because within our 500, half a million community of developers, where they work, what we've found is predominately at SIs, at our VARs, at our ISVs. So these are the builders, so Code Exchange will even help that persona because they can come and see what's already been built. "Is there something that can jumpstart my development?" And if there's not, then they can work with each other, right? So if I am looking for a partner, a VAR in Australia to help me roll out my application, my navigation application, which needs to know and get data from the network, I can partner through this exchange because I can go in, see everyone, and be able to make that connection digitally versus organically. And this really started, you asked earlier what was one of the pinnacle moments? Well at these DevNet Zones, what we found is that an ISV would partner and start talking to an SI or to a VAR, and they'd start doing business planning, because what this is all about is driving those business outcomes for our customer base. And we're finding more and more they're trying to work together. >> So you're enabling people to get, do some work together, but not try and be a marketplace where you're actually charging a transaction. It's really kind of a matchmaking-- >> This is all about discovery right now. >> Community-driven discovery around business. Yeah, it's interesting, a heard a story in the hallway about DevNet, cause I love to get the examples of, we love what we're doing by the way, but want to get the examples, overheard a guy saying, "We were basically "cratering a business, jumped into the DevNet program, "and turned it around," because there was deals happening. So the organic nature of the community allowed for him to get his hands dirty and leverage it, but actually build business value. >> That's exactly right. >> That's a huge, >> That's exactly right. >> at the end of the day, people love to play with code, but they're building something for business purposes or open-source projects. >> And that's what this is about. It's really transitioning from the, "I'm gonna build," to now there's business value associated with it, and that's spectacular. >> I think so much of my career you talk, the poor network administrators, like "Help, help, "I'm gonna lock myself for a month, "and I'm gonna do all this scripting," and then three months later their business comes and asks for something that, "I need to go it again," because it's not repeatable. It's what we say is that the challenge has been that undifferentiated heavy lifting that too many companies do. >> Exactly. >> Well, that's exactly it, and the interesting thing, especially around intent-based networking is that's opening up a whole new opportunity of innovation and services. And one of the things that isn't very much different with our Ecosystem Exchange is it's the whole portfolio, so we have SIs in there as well as ISVs. And most marketplaces or catalogs really look at it in a silo version. >> I have one example of kinda the two coming together that's really interesting. So, Meraki, which is the wireless network, has really great indoor location-based services you can get from the WiFi. And then there's been ISVs who have built indoor wave finding on top of it, they're really great applications. But those software companies don't necessarily know how to go install a Meraki network or sell a Meraki network to something like this. And so it's been a great way to see how some of those wave finding companies can get together with the people who actually go sell and install and admin Meraki networks, and, but come together, cause they would have a hard time finding each other otherwise. >> And the example is actually rolled out here at Cisco Live. We've, Cisco Live partnered with an ISV to embed a Cloud-based service in their app, which is navigation. So you can go into the Cisco Live app, tap on the session that you want to see. A map will come up that will navigate you from where you are here to get there, and this is, I think this is the second largest conference center in the United States, so having that map >> So you need it. >> is really important. >> I've gotten lost twice. >> We've all got the steps to prove that that is, but, yeah, and that actually brings, one of the questions I had was, is it typically some new thing, to do wireless rollouts and SD-WAN on discovery, or is it core networking, or is it kind of across the board as to when people get involved? >> It's definitely both. It's definitely both. I mean, from the Code Exchange piece, I've talked to a lot of customers this week who are saying, "We've got our core networking teams. "We want to move towards more automation. "We're trying to figure out how to get started." And so we give them all the resources to get started, like our video series and then now Code Exchange. And then I heard from some people here, they actually coded up some things and submitted it to Code Exchange while they were here because they had an idea for just a simple, quick automation piece that they needed. And they were like, "I bet somebody else "needs it too," so it was definitely in that. >> I noticed you guys also have your Cisco team I was talking to, some of the folks here have patents are being filed. So internally at Cisco, it's kind of a wind of change happening, where, >> It is exciting times. >> IoT cameras, I just saw a solution behind us here where you plug a Rasberry Pi hardware prototype to an AP, makes the camera a video. Now it looks like facial recognition, saves the metadata, never stores video, so this is kind of the new model. >> Pretty remarkable. So final question I want to ask you is, as you guys continue to build community, you're looking for feedback, the role of integrating is critical. You mentioned this Cisco example about going to market together. It used to be, "Hey, I'm an integrator of our solution, "business planning," okay, and then you gotta go to the Cisco rep, and then there's, they're dislocated. More and more it's coming together. >> It is. >> How are you guys bridging that, those two worlds? How are you tying it together? What's the plan? >> So we're, what we're finding is a lot of those partners are also sort of morphing. So they're not just one thing anymore, and so what we're doing is we're working with them, enabling them on our platforms, providing solid APIs that they can leverage, transitioning or expanding the code, the skillsets of their workers, and then we're partnering them up with our business partners and with our ISVs, and doing a lot of that matchmaking. And with Ecosystem Exchange, again, they'll now be able to take that to a digital format, so we're seeing the whole wave of the market taking them. >> So you guys see it coming. You're on that wave. >> Yes. >> All right, real quick, I know we're short on time, but I would, Mandy, if you could just talk about what Susie Wee, you're leader talked about on stage on the keynote, she mentioned DNA Center. Can you just take a quick second, describe what that is, why it's important, and impact to the community. >> Yes, so we're really excited about DNA Center platform. DNA Center is the controller, kind of at the heart of all of our new enterprise networking software. So it sits on top of the devices, and it exposes a whole library of APIs. It'll let you do Assurance, policy, get device information. It would allow you to build a kind of self-service ops models, so you could give more power to your power users to get access to network resources, on-board new devices, things like that. >> So it sets the services. >> So it's APIs, and then you can build the services on top. And part of that is also the Assurance, which Dave Geckeler showed in his keynote, which we're really excited about. So, in DevNet we've been working to build all the resources around those APIs, and we have many code samples in Code Exchange. We actually have a community contribution sprint going on right now, and that's called Code Intent with DevNet, and it's all around DNA Center. It's asking developers to take a business intent and turn it into code, and close the loop with Assurance, and submit that back to DevNet. >> That's great. It's a real business process >> We're real excited about >> improvement with code, >> that, yeah, so you're enabling that, and slinging APIs around, having fun, are you having fun? >> Definitely having fun. >> Par? >> We always have fun >> Absolutely >> on this team. >> We always have fun, yeah. >> It's a great team. >> I can say working with you guys up close has been fun to work, and congratulations. You guys have worked really hard and built a very successful, growing ecosystem of developers and partners, congratulations. >> Thank you. You guys have helped. >> Thank you. >> Thanks for supporting >> We appreciate it. theCUBE, really appreciate, this is crew of the DevNet team talking about, back in the early days, 2014, when it started, now it's booming. One of the successful developer programs in the enterprise here. Cisco's really showing the path. It's all about the community and the ecosystems, theCUBE, of course, doing our share. Broadcasting here live in Orlando at Cisco Live 2018. Stay with us for more live coverage after this short break. (upbeat music)

>> Narrator: It's The Cube covering Sapphire Now 2017. Brought to you by S.A.P. Cloud Platform and Honna Interprise Cloud. >> Hello there, and welcome to The Cube conversation here in Palo Alto Studios, I'm John Furrier with The Cube, and we have a special guest here. Susie Wee, who's the vice president and CTO of DevNet at Cisco Systems for a Cube conversation around what's happening in cloud, and really some of the most important trends that are generating out of a new event that she's starting called DevNet Creative, which The Cube will be there. Susie, welcome to this Cube conversation. >> Hi, John. Thanks, it's great to be here. >> So, you were a pioneer within Cisco. You know, superstar technologist, CTO. You helped really put the Cisco DevNet Developer program together. Which as been a huge success. Congratulations. >> Thank you. >> And that's been, you know, Cisco has a big community of geeks. They're super smart. They like to surf the web and learn, and develop new stuff on Cisco, but there's also a whole nother world, and you created an event called DevNet Create as a new initiative. A new pioneering effort. >> Absolutely. >> Why a new event? What's the big news here? >> It's really interesting. I think that what's going on is in the world of, kind of, the infrastructure, right? So the infrastructure has our networking, our compute, our storage, and all of that is changing in that it's becoming programmable, and so once it's programmable, you're like, "What?" My infrastructure has APIs. Once it has APIs, you can do things like DevOps, right? You can start to do things like really have good flexibility with how you deploy your applications, you can get much more rapid deployment of apps, and you can get, just, fundamentally, different, and improved applications. So, the big thing that's going on is that there's this huge industry transformation in front of us, and the transformation is in how applications meet infrastructure, and this has happened as applications go to the cloud, then how applications meet the cloud, apps are changing, right? Then as the infrastructure becomes programmable, there's APIs into it, so there's this really kind of fresh ground that's ahead of us, and we can make the most of this, and that's what DevNet Create is all about. >> You know, people always ask me, this is our eighth year doing The Cube, "John, you and Dave do such a good job with The Cube." "You always pick the events that are going to be good." (laughter) We did some when we were first on, I do parole, I mean, with Cloud Air, and nobody had heard of Cloud Air. We can sniff the trends out, and to me, I think you're onto something really big here, and this is why I'm excited to bring The Cube to your event. I know it's small, it's inaugural, and it's very community-oriented, but I think you guys are on fault line of a massive shift, and I think you're on the right side of this, and I think the app dynamics acquisition that Cisco did points to some of the things that going to give Cisco, I think, a big lift, and that is, by looking at the plumbing as being automated, certainly relevant, that's not going away, but as you move up the stack, there's going to be the need for rapid, rapid application deployment. >> Susie Wee: Absolutely. >> Conceive, build, ship in minutes. It could be automated with bots and AI and whatnot, so this is the trend. Talk about that dynamic, 'cause that requires a fundamental rethinking and reimagining of the Cloud, security, how packets move. >> Susie Wee: Absolutely. >> Do you agree with that, and obviously, you're running the event, so you probably have some bias there, but more importantly, this big trend. >> Yeah, absolutely. So, kind of the applications themselves, we take apps for granted these days, and we've had applications forever, right? But the applications are how people interact with the system, with the Cloud, with all the surfaces that they use everyday, so we know that everyone's lives have been transformed with apps, and then we also know that the Cloud has been huge. You know, work loads are moving with the Cloud. The Cloud has instant deployment, global resources, again, big stuff there as well, but that's going to shift again, right? So what happens is now that the Cloud is as awesome as it is, now that applications are great as they are, we're going to go to this next generation where the applications get even better, the Cloud gets even better, the way they meet, and therefore, the surfaces that people use get better. Let's have some examples of like, what could be better? Well, now that you have things like app dynamics, you can start to get information from your applications in the infrastructure that give you business insights, so let's say that you have your application running, and then you know how many times different APIs have been called. You know what parts of your systems, or your applications, are called the most. You know who's using them. You know how often they're being used, by whom, and so on. What order are they being used? All of this can start to give you business insight, so then you say, oh, the infrastructure's not just about delivering, compute, network, and storage, it's also about giving the insights into how people are using my stuff, so I can get business insights all of a sudden, and then it's a whole new world. >> Talk about how you got here, and your journey with Cisco being creating the DevNet and now DevNet Create, 'cause I think there's some trends in the industry, and we're going to be covering Sapphire, which is SAP's big show coming up in Orlando, and Cisco has some announcements, I know, I was brief under NDA on that so I really can't talk about it right now, but I do know for a fact it's going to be some significant innovations that's Cisco's bringing to the table, and they're an app provider. Now, they're older version, they're the big ERP, and the big software and framewares, and they announced Cloud Native with iOS development. This notion of, like a new breed of developers is not a mutually exclusive argument against IT, it's just the continuation. There's a dynamic going on between software developments and apps, and not only just on the business model side, but actually, technically. >> Yeah, absolutely. There's a few different things. So, first of all, an app developers can, so we have something called Meraki. Meraki is our wireless access points, it was a big acquisition we did a few years ago, and you can think of, you know, wireless access points as giving you connectivity, wireless connectivity, but now imagine that it also, you have APIs into it and it tells you how many mobile devices are connected. Where are they connected from? And where are the mobile devices located? If someone comes into your store, how many people have been there before? And how many people is it their first time there? So, this is all stuff that you can get from your wireless access points and you can start to do really interesting stuff. I think any app developer would love to have that information of what can I get? Who's in my store, or who's in my venue? And the infrastructure gives you that. >> And you guys run most, if not all the networks in the world. An IOT device and your other things that's connected to a network, wireless or wired. >> Yeah. >> And packets are moving around, so you have that data. >> We have that data, yes. So, yes, exactly. Cisco infrastructure is everywhere. >> But it's been hard to expose that over the years because Cisco's always had this notion that we play at a certain part of the stack and now it's almost like finally, after decades of conversations, I know from folks I talked to at Cisco, let's move up the stack. There's always been this push that does Cisco move up the stack and how? >> Yes, and basically the way that the way and the reason that Cisco can move up the stack now is because the infrastructure is programmable, so now, our kit, the network, is programmable. Now there's analytics that are being built into the network as things are running around, so like having a programmable network, having analytics, where you can either gather information together on how applications and things are being used, or a key, and then how do we move up the stack is when we work with the ecosystem. We work with the community, is that we have a developer program like DevNet, which is why we founded it, is we're going to enable those app developers to come to the world of the enterprise, so right now, when you have an enterprise, you know, who can write an awesome IOT app for a building, or for a casino, or for a mall, or for a hotel, it's whoever that hotel works with. Whatever system integrator they have, and that's all amazing, 'cause, you know, your building's instrumented, >> Yeah, so you don't have to >> Susie Wee: You know where people are. >> It's a horizontal market of developers versus a specific Cisco community, which you have to nurture in and of itself. >> Exactly. >> In the course of business, guys who know how to handle the packets and the networking gear, and know someone who's, hey, I know Cisco's a network provider, a network supplier, I just don't want to have to go get a training certification to get some data; just give it to me. >> That's right, and so what we can do is say, hey, here's the APIs, go to developer.cisco.com. Everything's there. Everything's free. Here's learning labs on how to use the different APIs. Here's use cases. We actually have kit in the clouds so we have a sandbox that lets people use stuff. If you want to write an app for a contact center, 'cause we sell contacts in our stuff, we have a contact center that you can write and deploy your app on. You don't have to buy one to test it, right? So it's really interesting when these apps hit these places, which is that, you know, you need a contact center, well, we'll have one for you. >> Here's the hard question. I want to put you on the spot and bring the heat, if you will. You guys have been great in your own ecosystem. Dominant for Cisco as a company. As you move into this new ecosystem, because ecosystems are now business-model parts of public companies. Cloud Air just went public. Ortenwer's went public. Viewelsoft. A new class of new kind of open-source companies are going public. You guys are not necessarily an open-source company. You have open-source initiatives. You have to now embrace a new kind of ecosystem. >> Absolutely. >> Where's the progress on this? How early is it? 'Cause I think that's what DevNet created to me, and Cisco is now going into a new market and being proactive. >> Absolutely >> The question is are you ready? Do you have the chops? Where are you in the progress of that? (laughter) >> We're ready. Now, it's going to take work to work with the community to get there, but let me just go back 'cause when we first started DeveNet three years ago, we said, hey, are those networkers and those infrastructure guys, are they really ready for programmability and software? We didn't know, and then we had out first DevNet event, and it was packed. We're like, oh my gosh, these guys are so ready, and we didn't know that at the time, so we've made good progress there, but now that we're sitting there to work with the community, I think that I'm hoping that they're going to be embracing so we're certainly going to be open. We've actually opened up, kind of, the thinking within Cisco. We've done a lot of cultural change within Cisco because people have seen the success of DevNet and of the developers outside in the world who are actually jumping in and ready to embrace programmability. >> So, it's the old data. It started home. What you did. >> It started home. >> You did with your own core. >> And then used that to then build out. >> And you guys have apps, we know, again, we go to a lot of events. I've seen Cisco around in a lot of some of the open-stores events. I was at the Nix Foundation. You guys had some presence, but it seemed like a toe in the water. How are you guys going to go big in this? >> That's what changed, is actually Cisco has had some little developer efforts and a lot of heroics done by people within Cisco. Like, hey, I have this great product, I want to run a hackathon, right? So, we've had all of these heroic attempts, but until DevNet came along, we didn't have one centrally funded program with a mandate from the CEO to go and get that programmability and develop our ecosystem out there. That's what we had now for the last three years with DevNet, so now is we go to the next layer. You're right, we do have the people who are out working with the Cloud Native, working with OpenStock, working with OpenDaylight, working in the SDN, the Lennox foundation, and what we're doing is now bringing that to the next level. Again, adding the DevNet power, now that we have kind of established our base to really embrace this, so we hope that we're going to provide a lot more, kind of, foundation so that we can go big in these cases. >> How big is the cultural change within Cisco, just give some color without giving away too many trade secrets, but I know Cisco have, and a lot of my friends worked there I've known for years, from the beginning, I've been intimate with the company's culture, and they've been a case study of dominance, just the way their competitiveness has been, the products have been great. They run the networks, but now they have to move into this open source and the community world. Talk about some of the cultural changes. Any conversations? The CEO, when you talk to him, what's the conversation like there? >> I just met with our CEO, Chuck Robins, a couple weeks ago, updated him on our progress. He actually, he an John Chambers, together, helped found DevNet, so they understand the need for it, and they helped break down the barriers and create the funding and the organization to do it, and we had to do some re-orgs to get it going originally. >> It's not just lip service, they're putting their muscle behind it. >> They're putting their effort behind it and they're dedicated to it, and they understand it. Chuck is fully behind it. He sees the importance of programmability. He actually understands the applications meet infrastructure and the transformation that can happen there, so he is super supportive all the way. He sent me a text this morning and said, "Yeah, when is DevNet Create again?" >> Great. >> So he's on top of it. He knows what we're doing. >> We'll have him on The Cube for sure. >> Absolutely. >> So applications meets infrastructure is the DevOps ethos, and that really highlights your theme. >> It does. Now, some of the other cultural change that has happened is, for example, we have something called systems engineers in our sales force. So what happens is, in our sales force, we have technical folks. We have 6,000 sales engineers around the world. Systems engineers, and they understand the technical side. They're all taking DevNet training. They're taking DevNet learning labs. They're learning to code. They're learning to use our APIs and now, the other thing is that they're now running DevNet events around the world. These guys are not only getting trained, but they are running their own developer events, and so they've picked it all up. This is a transformation that, you know, we've partnered with them on, and that's really changed what they're doing and they're realizing that, hey, there's a conversation, like, we can finally have the assets to help out app developers, and the app developers, they do need help. People have been rating mobile apps for years. Not that many of them are making money, right? The question is how do you do good to those app developers? How do you bring those app developers into the enterprise? How do you take it and make sure that when you have the newest things, like... >> I've always said: feed it data. >> Feed it data. >> Data is a great life blood of applications. >> Absolutely, and so then the applications have data. Then you start to analyze it, you get the intelligence from it right there, and then all new insight. >> The automation around provisioning all that network plumbing is really, really hard and nuanced. If you can automate that away, developers will just have parade to your door. >> Absolutely. >> Alright, so, personal question. You've been very successful in building DevNet. Building developer programs is everyone's holy grail right now. There are people in companies: "We got to build a developer program." "Throw some money at it." They might have some lip service from the CEO or full commitment. What is the key to success. To get the companies and to actually conceive, to build, and deploy a successful developer program for a company? >> Yeah, that's a good question. I have to say that building the developer program is not as easy as you would think. I would think it should be easy, like get out there, go find some web service that's running free developer community stuff >> Someone creates a free code. >> Give 'em code, and that's it? But it's actually not that at all. There is actually a few things that have been key to what we've done. One of them, and actually, I spoke about this at the Evan's developer relations conference a few weeks back, but one of the keys there is just be entrepreneurial. You actually have to be an entrepreneur even if you're in a big company, then you especially have to be entrepreneurial. >> John: You got to hustle harder. >> And what I mean is you have to hustle hard and, with few resources, you have to show quick wins fast, and you have to make bets, right? What are the kind of things we do? Well, when we first started, we actually didn't have an organization. It was me. It was a couple rebels from different parts of the org who are like, we need this, and we were making proposals. >> Skull and crossbones kind of thing going on, yeah, big time. >> And we pretended that, hey, just pretend that we have a full-blown developer program. What would you do? What we did was, we went out there, we went made developer.cisco.com, we made one site, we brought all of the APIs into one place so that developers could access it, and it was just going through and kind of building that site, which is really hard in a big company like Cisco with APIs all over the place, and we just silently launched it, and then people started discovering it. Like, oh, all of Cisco's stuff is here. Holy Cow. That was one thing. >> Go humble early. Learned from Lennox himself. >> And we actually got kind of blasted on the Twittershpere because actually on our developer page, we had one section that was actually going to just product information and not having APIs in it, and so this guy was like, that's all product stuff. That's not about APIs, so we got blasted. We were like holy crap, he's right. We went, we changed it. Got rid of all that. >> That's agile. >> And fixed it and then he became our biggest fan, right? We changed and we learned from feedback from the community. >> You applied the entrepreneurial hustle. Hustle hard and make bets. >> Susie: Make bets. >> What's your big bet that your hustling now for, and I mean hustle in a good way, DevNet Create. What's your bet? >> Our first bet back then, big bet, was the DevNet's own at Cisco Live, was let's have a developer conference at Cisco Live. We have no idea if people are going to be interested, but let's just do it. So, we got second floor of Mosconi's. >> You're going big or going home. >> Yeah, exactly, so we like boom! Kind of got the same place they have Google IO and Dreamforce. We got the space, kind of created it, didn't know if anybody would come. It was jampacked. We're like, oh my God. John Chambers came by. He told his whole staff, like, you guys have to see what's happening. The DevNet zone's now the busiest part of Cisco Live. That was our big bet then, and fortunately it paid off, and I think that's what made us part of the fabric that let us continue on, but now our big bet is DevNet Create. It's about applications hitting the infrastructure and really ensuring that the infrastructure is giving benefit to app developers. >> John: Real benefit. >> Real benefit. It's not just for the sake of business, it's actually because, to me, there's a real inflection going on in the industry. Apps can just ride on top, and then just do whatever the infrastructure can provide for them, and that'll get us to one place, but once you really think about it, then you say, okay, where does the data for the apps need to sit? Oh my gosh, there's data sovereignty issues, so it can't just sit anywhere. How do we scale out? Like, when we scale out, and you could just say, oh yeah, just go buy it and Amazon, Google, someone else will take care of it for me. Well, some of it will, and you should absolutely use... We're using all of those >> The policy stuff. >> As well, but there's policy, there's, you know, so when you're really working to scale out and understand what's critical for your business, there's more that can be had, and then now you can go to the next level of where apps can get value added business insights from the network like what we were talking about before, and then, a really big thing is just when I kind of think forward to the world of IOT, and you say again, this building is now IOT enabled. This building has APIs. It's the infrastructure, and app developers would love to get access to that. >> Peter Barris and I were talking at The Cube about a new standard we want to see. All data should be presented in less than 100 milliseconds from any database. >> Susie: Nice, nice. >> That's a moon shot, but let's think about that. That's what we want. Okay, so final question. Congratulations on all your success, and I do believe that a trend is there, the question is when will it get there. Upcoming for DevNet Create, what do you hope to bring to the community? What do you want the community to look for and expect? And what will they see? >> Absolutely. What we want is, we hope that DevNet Create is just a catalyst for this to happen. For this transformation that's happening, and we want it to help drive things with the community in a faster way than if we just let it go itself. There's basically going to be two tracks at DevNet Create. One is on Cloud and DevOps, and the other is on IOT and apps. With Cloud, there's all these questions of how are we going to take monolithic legacy apps and turn them into micro surfaces? We have the world of containers. We have the world of container orchestration and everything there. That's all really hot stuff, but the way that we move this together, bring it into full production and get all of the apps really embracing that is key. What we're hoping will happen at DevNet Create is that the world of Cloud developers, the world of app developers, IOT developers will come together with those that are working in DevOps, those in the infrastructure to really understand what are the benefits that can happen across these layers? I'm not saying that every app developer needs to become an infrastructure developer, right? I'm not saying that every developer must be an operator, but there's benefits that can happen in the right way. Really, what we're hoping is that with DevNet Create, we can drive that conversation at the event itself and then continue with the ongoing community. >> And who are you targeting specifically to the event? Non-Cisco developers or Cisco developers with a plus, with a twist, or? >> Non-Cisco developers as well as some Cisco developers as well, but it's really about the industry. Where as when you go to a traditional DevNet event, you're going to be hearing all about Cisco APIs and Cisco products and how they play together in these solutions, but at DevNet Create, 90% or more of the talks are non-Cisco. We had a call for papers. I was really nervous when we had the call for papers and I was super relieved because we had great papers come in. Actually, the only problem is that we didn't have enough slots for the great papers. We even had to turn around some really good ones. Turn away some really good ones. We have a really strong agenda, and we actually said no to more Cisco talks because we wanted it from the ecosystem. We have people from Google, from Amazon, from Howdy. There's just lots of... >> And so will this be a Cisco event going forward? Or an industry event? Because there's a trend in the event world where people are going in for the big DreamForce and the big one show, big tent, zillion people, and then a series of industry shows around open-source communities with governance. Are you guys going to make this a Cisco managed show? Or thinking about opening it up to the community to manage? What's your thoughts on the vision of that? >> We're hoping to catalyze it. We will continue to have our other Cisco DevNet events that are really about the Cisco APIs themselves and really training and bringing along that core community, and we invite all the developers to attend that as well, but we really view DevNet Create to really be an event for the community. We'd be open to doing this with cosponsors and hosting it with others. >> So you're open. >> We're open. We're actually doing this with Lennox Foundation as well, so we have them involved. Many of them are on our advisory board. We are very open. We're actually working with SiliconANGLE and The Cube. We want to do it in the most open way as possible. >> As I said, we like to sniff out all the hot events. This is one inaugural event. I think it's really, really important because it really shows Cisco's commitment to open source in a way that's been toe in the waters in the past, like you said, little rebels in the organization doing their thing trying to get the word inside Cisco, but now with the cultural shift, I think you guys have it with app dynamics. There's a business path. I see a path there and I think the community only benefits. >> Absolutely, and if the community benefits, and our goal is to actually make our community and our developers successful. That's actually our only goal. For them to be successful in their careers and their business, and that will, in turn, make Cisco successful, but really, it's really about making the community successful. >> I mean if you think about the 5G end-to-end. I mean, end-to-end architectures are winning. We do a whole segment on end-to-end, but to make it end-to-end work that's not just one company, you'd need to have a strong developer community, and I think this is kind of where I see the event's importance is true network transformation and programmability. The ethos of DevOps needs to go to the next level so cars can program themselves. I mean, everything. 5G's coming too, so a lot of new stuff happening. >> Absolutely. I don't think any major industry transformation happened with one company alone. It really takes a community, right? Be it a community of product makers, a community of solutions providers, surface providers, and consumers themselves. This is really about the community. >> Susie, congratulations on all your success, and we're looking forward to seeing DevNet Create's inaugural opening in May. Appreciate it, and great to talk to you about some of the mega trends and your perspective on that. >> And thank you for helping to drive this vision and agenda. I think that we'll be able to do this together. >> Susie, with CTO at Cisco Systems, DevNet creator and pioneer with her team of rebels, now a full on group. Really talking about the app meets infrastructure total transformation enabling all the AI in terms of vehicles, smart cities, smart home. Thanks for joining us. This is a Cube conversation. I'm John Furrier and thanks for watching. (upbeat music)

>> Announcer: Boston, Massachusetts It's theCUBE. Covering OpenStack Summit 2017. Brought to you by the OpenStack Foundation, RedHat, and additional ecosystem support. (upbeat techno music fades out) >> Hi, I'm Stu Miniman, joined by John Troyer, and this is theCUBE, SiliconANGLE Media's live broadcast of OpenStack 2017 here in beautiful Boston, Massachusetts. Actually, the clouds have been breaking up, a little bit of sunshine here, and it's our third day of broadcasts. We have really a lot of our editorial segment today. Going to be talking to more community members, talking to one of the Superuser winners, a number of startups, and happy to start the day, Lisa-Marie Namphy who is the US OpenStack ambassador. CUBE alum, been on a number of times. Lisa, tell us what's new in your world. >> Thank you Stu, and thanks John and what a pleasure to be here with you folks, and hello, Boston and world, good morning. What's new, well the OpenStack ambassador program is expanding all the time, we just had a great session that Sonia did to kick off the day today to really talk about, you know, how to get involved in OpenStack, even if you're not necessarily a technical person. It's really important to acknowledge how everybody in our community can contribute, and that's one of the things the ambassador program does really well. So we just had a session on that. One of the things that I've done with our user group that is new and super exciting is I've morphed it into a little bit of the OpenStack in Containers user group. So I've been focusing a lot on containers, done 12 or 13 meetups on Kubernetes and or Docker since last summer, and I just had the pleasure of speaking in the CNCF communities track, communities day track yesterday, and that was so much fun, out there in the grand ballroom, so that's kind of some new and fun things we're doing. >> It's great, this is our fifth year doing theCUBE at this show, always a robust community, really. When we started coming, it was the people building it, Now we have a lot of the users, there's different sub-segments, can you speak a little bit to the kind of maturity of the community, and, you know how do people get involved in the ambassador program, how many are there geographically, number wise, diversity, those kind of things. >> Oh gosh, yeah so it's geo, or it's a worldwide program and it's been going a lot, and you're right, you know years ago, here it was the Design Summit, and we sat around and talked about, you know the next six months of the project, and then it morphed into more users, adoption, customers, operators are a really big one too. And now those things are all so big, we have operators, Midcycles, and all and the Design Summit has been, you know sequestered off into, separated out so that we can really focus here on the customers, the community, users, and those type of contributors as well. So things have changed a lot in the seven years since we've been doing OpenStack. The ambassador program is fantastic. The foundation has done a really good job in the last couple of years of acknowledging the contributions of the user community, and so not necessarily the code contributors only, but the people who are also spending as much time contributing in really significant ways to our community, and growing our commnity. Open source doesn't work without a community. So we know that, and we're doing a much better job of acknowledging who those people are and rewarding them. >> John: How many ambassadors worldwide? >> There's about twenty of us. I'm the only one in the US right now, but we're about to change that. I believe my friend Sheila is going to join and cover the East Coast, and I'll be able to do everything west of the Mississippi, but most countries only have one, and... >> And the role of an ambassador, do you do a lot of meetups? Do you go speak? You're there as a, for people to contact as well, right? >> Yeah, we generally recruit or ask people to be ambassadors if they are already doing those things, if they're already running a local user group, if they already have a brand in OpenStack, and they speak, and they kind of already know how to reach out to people, and how to inspire people, or people see them on stage, and that's why the foundation approached me to do it. I had been running the San Francisco Bay area meetup for three years, and speaking, I don't know this is probably my eighth, ninth, maybe tenth OpenStack Summit that I've been speaking at, and OpenStack days and all of that. And so, you kind of see who's already doing it. The cool thing about community is nobody is asked to do it, like you do it because you have a passion for it, because you love it, because it's the right thing to do, because it's helpful to push the technology forward because you have a passion for the technology, because you love people, all these reasons is why people get into it. So you find all over the world people who are doing this. They're already doing it and they're not being paid to do it they're doing it, those are the people you grab, because you know, there is a burnout level to it but those are the people who have enough passion about it and commitment, and believe in community that they're going to be successful at it. >> Can you talk a little bit about the Bay Area OpenStack user group? It's one of the largest OpenStack user groups, and one of the themes we've seen this week is a lot of talk about containers, a lot of talk about, well, Kubernetes, but containers in general, kind of demystifying the sometimes confusing story about where's OpenStack good for, where's the container layer good for, it turns out it's good for a couple different places, you can containerize OpenStack, you can also... A lot of talk about the app layer on top, but you actually, what you just said, you've actually expanded the conversation, you don't just sit there and say "this month we're talking about Neutron," you talk about a lot of different topics, and you bring people to the table. >> Yeah, San Francisco area, you are correct, it is the world's largest OpenStack user group, we have over 6,000 members. Not all of them are located in the Bay Area, I think people like to join the user group because we provide a lot of really good content, and we live stream our meetups, we have Google Hangouts, I record them all, they're all on our calendar, if you go to meetup.com/openstack, you get to us because we were the first one. So we do get a lot of people from around the world, and I write newsletters with lots of interesting information but it is a local community and we do encourage people to participate, so the meetups are super important and the only way to make sure that you keep your community strong and keep people coming back is to have phenomenal content in your meetups. So I work really hard to make sure that the content is interesting, that it's relevant, and the most exciting, most relevant conversation since last summer has been containers. The year before that it was networking, and it still kind of is and always will be. So we do a lot of meetups on networking, too, but containers has been what people want to talk about. They're trying to figure this out. OpenStack has reached a maturity level where people, you know, they're not necessarily learning or if they are they can take an OpenStack 101 course and those exist all over the place. So we've gone to the next level, and whether it was Cloud Foundry or now Containers we do like to talk about what else you can do with this fabulous technology, and how you should do it. So we've had meetups where we've presented OpenStack on communities, communities on OpenStack, where I personally came in and did a whole meetup on Kubernetes as the underlay, and Rob Starmer came in and did a whole workshop and hands-on about how to run OpenStack on containers. Yesterday our panel, you heard Dan Berg talk about just simplifying it, run everything in a container, but keep it as simple as possible, so what pieces do you need? So these are the conversations that we like to have in our user group, and people keep coming back because it's an exciting conversation. >> Yeah, expanding on that, you talked about just people are always coming, new people to the community that don't know it, people that are changing jobs all the time, new technologies, I mean, we all know community building is a constant, you know, reinvention in something, you keep needing to work How do the ambassadors, how do stay energized on it, how do you keep the momentum and the energy of the community going? >> Yeah, well the cool thing about an open source community is no matter where you're working, you're still part of the community. So I've worked with so many other people here, I don't even know where they are sometimes. I mean we don't tend to talk about what company we're actually working for, or who's paying your paycheck, and especially in the early days of the project that was definitely true, and so some of my good friends have been at four different companies in the time that we've been doing this OpenStack thing, but we're all still working on OpenStack, and I suspect Kubernetes will be very similar, or Docker. You know, how many people are working on Docker? But there's only 200 people that work for Docker, right? So these technologies kind of take on these lives of their own, and people do switch jobs a lot, but people come to meetups because it's a constant thing, and it's also a good place to keep networking and keep looking for work, so we got a lot of that. The beginning of every meetup, I ask for a show of hands of who's hiring. If I ask for who's looking, not everybody raises their hand but if you ask who's hiring, there's a lot of people hiring all the time, and so then the people can look around and say "okay I'm going to go talk to those people," so yeah, the networking is an important part. >> On that point, are you seeing any trends as to what are the roles that they're hiring for, or you know, companies or industries that definitely have changing skillsets, you know John spent a lot of time helping all those virtualization people moving to that next thing, what are you seeing? >> Engineering is the big one, and people are still looking for OpenStack engineers. I mean people ping me all the time, saying "do you know any OpenStack engineers?" So that's usually the number one thing, developers to help build out these things, and then also the companies that, you know, that aren't OpenStack companies, you know companies like GE that are trying to hire what, 20,000 developers in the next couple years, and Mercedes and Tesla, and you see all these companies that are trying to build out their software developer programs. So another role that is interesting that people are hiring for is these developer, DevRel, Developer IVC community roles to try to figure out, you know how are we going to build our developer community within our company? If these are really large companies, or you know, companies like IBM which have interest in things like the Apache Spark community, or you know, you find these pockets in these large companies as well. Or there's a lot of startups, you know unlike, probably not like Docker as much, but Kubernetes is going to have this ecosystem of partners that build around it, and these companies are popping up out of the woodwork and they're growing like crazy, and there's like 30 of them in the Bay Area, right? So they're really trying to expand as well. >> I wanted to ask about the general mood of the summit. My first summit... You know, it happens every six months. I've been impressed by how grounded people are, I see a lot of first time attendees, people starting new OpenStack installations in 2017 right now, here to learn... I'm just kind of curious, over the last couple summits is there anything different you see about here in Boston, anything you're looking forward to going to in the next one, in terms of kind of mood and how people are, are people feeling good, are people, you know, are people still puzzling out this container issue, or are people still talking about public versus private, or what are kind of the mood and conversations you hear from other community members? >> I think people are talking about public versus private again, not still right? I mean is it, that was kind of an interesting one, and I think Johnathan brought it up on main stage on the first day about that kind of readoption of private cloud, and that you know, we knew that was a sweet spot for OpenStack particularly in the US. You know, lots of public clouds running on other parts of the world, but that's a fun conversation, and it's containers of course, but not just containers. I think it was maybe Lauren Sell who put the slide up of all of those other technologies that are, you know affiliate now, and... >> Another ecosystem of open source projects >> Lisa: Yeah, yeah >> that can all interoperate with openstack. >> With Cloud Foundry, and Ansible was up there, and Ceph, and you had a slide full of technologies, OpenDaylight, that are all playing a role here and that the conversation has been about, and I just encouraged in the ambassador session and in the meetup sessions to do that with your meetup. Our meetup has been really successful and the people have loved it because we started bringing in this other technology. People want to talk about IoT, they want to talk about AI, they want to talk about machine learning, so there's those, they want to talk about, you know what are the best use cases for OpenStack so we showcased to GoDaddy what they built with Docker on top of OpenStack. So there's a lot of fun conversations to be had right now, and I think there's a buzz around here, you know that, what, day one when Johnathan put the slide up saying, you know, people have predicted the end of OpenStack and that was like four years ago or whatever, that was an awesome slide, right? I'm sure talked to him about it. >> Yeah, I absolutely traded notes, and caught opinion about it, too. Lisa, you live in The Valley, I'm curious about perception in The Valley, you know, OpenStacks now been around seven years, it's kind of, you know, it's matured, it's moved on, some called it boring because we fixed some of the main issues, you know We mentioned all the OpenStack days with you know Cloud Foundry, Kubernetes, all these software pieces on top, what do you hear in The Valley when people talk about OpenStack, any misperceptions you'd want to clarify? >> Yeah, yeah it's not boring. It's funny when you say to a California girl "you live in The Valley," I'd be like, "let's just say The Silicon Valley." Not the, not the other Valley. >> Stu: Not the Valley girl >> Don't make me start talking like that, right? >> Stu: Oh my god! (laughs) >> Right, so, no. It's never boring, it's never... It hasn't been boring from day one, and there's been times where I felt like okay we've been talking about infrastructure for years now, let's talk about some other things, but I love the way at this conference they're talking about, they're calling it the "open infrastructure conference." You know, this is what OpenStack has become, and that just opens the conversation. You know, I love that shift. There's always something exciting to talk about, and I don't mean the little inside baseball things, like should we have done Big Ten, should Stackalytics go away, I mean, you know people like to talk about that stuff, but I don't find that customers or the people at the meetups are talking about that stuff. People at the meetups are talking about you know, how should we run this with Kubernetes? How do these technologies fit together? You know, lots of different things, you know where does Docker play into it? Networking is still a conversation and a problem to still be solved, and how are we going to do this? We had OpenContrail do a meetup with us a couple of weeks ago. There's still a lot of interest in figuring out the networking piece of it, and how to do that better. So we're never going to run out of things to talk about. >> Alright, so how do more people get involved, how do they find their meetups, where do they find resources? >> Most of, openstack.org has a list of all the communities, but most of the communities use meetup.com, almost globally, so if you go to meetup.com, and you put in your geo, you'll find one. You can contact your local ambassador. If you want to get involved, I say just go to a meetup. I mean you can't start leading communities until you participate in communities. There is no way to phone this in. You have to, it's hands-on, roll up your sleeves, let's get to work and participate, and have some fun. So go to a local meetup, and meet your meetup organizers, volunteer, help, and it's so rewarding. Some of my best friends that I have, I've met through OpenStack or open source projects. It creates many opportunities for jobs. So just start going to meetups and get involved, and if you want to be an ambassador, there's a list on the website of how to figure that out. Tom Fifield runs the whole program with Sonia's help out of Australia, but regionally we're always looking for help. There's no shortage of roles that people can play if people really want to. >> Definitely a vibrant community here, doing well, Lisa-Marie Namphy, always a pleasure to catch up with you, and we have a full day of programming coming, so stay tuned and thank you for watching the cube. >> Lisa: Thanks Stu, thanks John. (upbeat techno music)

>> Host: Live, from Santa Clara, California, it's TheCUBE covering Open Networking Summit 2017. Brought to you by the Linux Foundation. (upbeat music) >> Hey, welcome back everybody, Jeff Frick here with theCUBE. We are coming to the end of day two at Open Networking Summit. We just got here today, it's a great show. Everyone who's talking everything about software-defined networking is here. And along with Scott Raynovich we're joined by Dave Ward, one of the luminaries doing panels, doing keynotes. >> Here we are in TheCUBE. >> And here we are. Dave is the CTO of Engineering and Chief Architect at Cisco Systems. So Dave, great to see you as always. >> Great to see you guys. >> So what's the buzz of the show, you've been here for a couple of days, any surprises? >> No real big surprises to be honest, always there's some great announcements and great launches going on. But really what I'm finding surprising is that this is the sixth year of this conference, can you believe that? So year six from where we started, and I may be the first person to say this, have you ever had anybody in theCUBE today talking about openflow? >> Jeff: No. >> Remember those days? >> Now, nothing against open flow that's not my point, but think about how far we've gone and so. >> Scott: Actually, yeah, Martin was talking about it. >> Course he did. Course he did. He's not going to let it go. (laughter) But love you Martin. But really my point is, look how far we've come in six years. Six years ago we had a protocol, small community, one group working on this stuff, really working in standards, there was no open-source associated with that at that time, now look where we are. Basically the place to do work is now in open-source and come together as a community. So, the buzz for me really is holy shit, this thing is real! There's a lot of people investing a lot of money and time and really trying to work together to improve and build the ecosystem around networking, around network functions, what services are being delivered and building a business off networking again, so networking is back. It's cool again. >> Jeff: Right. Great. And then there's this whole new thing coming down the pike in the form of 5G, and IoT that's just opening up a new opportunity kind of redefine, what are these standards, and how is this going to help push things along? >> Well, it's kind of interesting and so I'm just ripping for a second. When you take a look at where we've come over the last several years and it was SDN controllers and configuring the network. Then it was virtualizing the network. There was a lot of talk yesterday and today about analytics and creating a reactive network. All of that has been built in the those six years and come together in different open-source communities to build those pieces. We've got SDN controllers, projects like OpenDaylight, projects like FD.io, projects like PNDA, P-N-D-A-.io. That's the SDN virtualized network and data analytics piece, but when you get to 5G and IoT, one thing I'll be talking about tomorrow in my keynote, is that there're big blocks missing in the industry. So, let's dial it back to historically, remember when the HVAC contractor logged on to the network and that malware on that laptop stole 70 million credit cards, remember that? >> Yes. >> Still haven't solved that problem yet. And so the reason why I'm bringing this up is what's missing, identity. So we had this notion that networks controlled by IT operators that are going to go in and config and provision that network. Well, we're now to the point where we need to link people and things to be able to drive what that intent is on the network, and whether its buzz words, which is real functionality by the way, of micro-segmentation. HVAC contractor goes into a micro-segment, can't get to the point of sale, can't steal the credit cards. Basic bread and butter stuff we want from the network. This is what SDN is supposed to deliver, virtualized services like firewalls and other sporadic security, we'll just hold that for a second. But that linking of who the person is, what device they're on, where they are on campus, where they are in the world, etc., etc., time of day, whatever the case may be, are now the variables that need to go into the top of this system, into a policy engine that then drives that reactive network. We've made a couple of great strides in six years, but to get to 5G, and in particular to get to IoT, we have to have another couple of major blocks come into the industry to make that work well. Hopefully it's open-source where that's going to go, and it's not just a standards body and not just open-source, cuz we still need things to be manufactured and interoperable and the rest of it. So hopefully these things come together as we've seen the maturing of those two big groups. >> I was going to say, it kind of begs the question, what is the interplay between standards bodies versa or together with open-source projects? Cuz before you didn't really have open-sources standards really set. Set the regs. Now you've got these open-source projects, which have a main channel, they might start forking, there's all kinds of places that they can go, and how do the two kind of work together? >> Well there's been a ton of effort, and coming out of the SDN open-source movement around model-driven networking, and although it sounds kind of geeky, the main way of representing those models is through representation called YANG. The interesting thing about YANG is that's been not only adopted in SDN, as the main object and way of representing the models being converted to network and equipment computes, computers etc. But the IETF has taken that up and really driven a service approach through the IETF which is I want to deliver a VPN service, I want to deliver load engineering on the network versus what we did with SNMP, or what the industry did, which was I'm going to fully distribute this out to all the protocols and all the functions and everybody's going to write a NIB etc., etc. and we know how that turned out. So the craze for model-driven networking, the standards bodies picking this up, IETF, MEF, which is metro ethernet forum, broadband forum, BBF. All these organizations have now taken on that mantra that came out of open-source SDN of model-driven networking and are working towards creating those models so that way we will have a standardized way to program the network. But what's next is the telemetry coming out. Those objects need to be standardized so that way whether it's a Cisco device or somebody else's device, it's actually sending out the same data that can be collected and can be interpreted properly. Does it mean that it's a NIB? Does it mean that it's only going to go over one particular transport? I don't think anybody in the industry really cares whether it's JSON, Google RPC, Protobuffs, Netconf, or any of these pieces, they're all perfectly fine, they have different semantics associated with them, but nonetheless those common objects and common data models have been what has been the key to keeping the industry working together, the common architectural philosophy, and then the standards bodies have thankfully picked that up over the last couple of years. >> Yeah we were talking here earlier, I mean you just threw out a bunch of alphabet soup there and I understand 80% of it, but it does raise the issue we were talking about earlier about these standards development organizations and the IETF, the TM Forum, the MEF. Now we have open-source, so we have the Linux Foundation. We have a lot of these different organizations and I think while you would know better than I as a CTO, people are becoming challenged by tracking and following all this stuff, do you think we need some sort of consolidation of these standards or at least some more unification, we just saw ECOMP and Open-O merge so there seems to be some consolidation. What will we see going forward? What's going to help you as the CTO? >> There's no doubt if there's consolidation, that would be easier to track and easier place to develop, but in reality, Scott, it's 50 shades of YANG. (laughter) >> And the reason why I say that is each and every standards body has done their own specific function, again whether it's Metro Ethernet or its broadband access or its mobility, each one of those standards bodies is redefining themselves to be SDN capable. There's no doubt. If there's a one stop shop, it would be the most optimal way to get something done the fastest, but that's not the way the world works. So actually I think we are going to see a continuous increase of more folks working on this, more foundations being build, etc., etc. Although, what we have witnessed over the last couple days in the last year, is that the communities, the open-source communities in particular, are coming together and trying to integrate the pieces together versus just islands of cool technology that there's a few geeks interested in, no. Thankfully the operators and some enterprises have come in and said I need this stuff to work and I need this stuff to work together and that discipline is actually fundamentally new and different than the way either standards bodies worked or open-source worked in the past. So I'd love to say that there'd be even more consolidation. There's frankly a bit of fatigue over, not saying it's wack-a-mole but you have to chase, you have to really figure out and track where all this stuff is going on in the industry to really keep abreast and understand how wide and how deep it goes. >> It's interesting this trend lately where people are just donating ... The project is just being absorbed into Linux Foundation. So now there's at least kind of a consistency across all these various projects, in terms of the way things are managed, the shows, the communication, and them helping standardize a process to help those projects be more successful in their distribution and adoption in the company. >> Linux Foundation has done the industry a huge service. They understand governance. They've gone through a zillion different experiences of how to build communities. What works well when there's competing factions that need to come together and work, on board marketing team, on board legal team, able to build foundations as necessary, or what's been experimented with over the last couple of years is, if you remember when we started to number these, you need to have a 503C, you need to have a foundation, there was frankly a high cost associated with these. Now, open-source is being contributed there's no foundation, and there's no cost. And so there's a whole continuum of things that the industry, the networking industry I should say, is learning about how to build communities and although this sounds cliche, you may launch a product, but you don't launch a community, you actually have to build it. And it's not all one company that's doing the donating or doing the working and that will produce, that'll create the longevity of that particular project. And that is what the Linux Foundation knows how to do well or at least catalyzed people to come together to do that well. >> Now you mentioned one of the big questions that always comes up with open-source is well how do we make money, right? Cause it's all free. It's like, you know ... >> Are we on Jerry Maguire? What's going on? (laughter) >> Jeff: Free like a puppy. (laughing) >> Still my favorite. >> Free like a puppy, yeah, you guys still got to change the newspaper. So you were on a panel today there was a big discussion about the commercialization and how does, I mean obviously Cisco has to stare at this big puppy in the room if you will, you know. What's going to happen to our licensing model with all this open-source, what came out of that discussion, what came out of the panel about how do you make money in this open-source world? >> So a couple of things, one thing that was discussed was not only how to make money, is which comes first, cost reduction, total cost of ownership, or new service revenue. And really the outcome there, and AT&T, Comcast, and Lightspeed Ventures was also in the panel with me. Needless to say it's a combination of both. If you're coming in with a project and the project is please spend this money so you can save this money, we know how to do that math. We can add up the rows and columns and can understand whether or not money will be saved over time. But the new service revenue really certainly in an enterprise space, is really what's being discussed. In particular, can I get these new services, I need these new security functions, I want to manage all my branches from the cloud or whatever the case might be. So new service revenue is depending on which use case, which technology, which layer. Both of those two balance out and they both are required in the algorithm. Now, can people make money off of it? And the answer is, needless to say, Lightspeed Ventures colleague said, "Hey man, if there's a community "and there's a technology, "you can list off a zillion cases of where that community "is turned into a true company that can provide value-add "and additional IP and move forward." Now, let's move this from just startups to big companies like Cisco or AT&T and Comcast and not only do we all use open-source in our projects, all those companies are contributing to open-source. And in Cisco's case, we're contributing to open-source for a couple of key reasons, one is there are gaps in the industry, which were limiting the industry. So let me give an example. We open-sourced a virtual switch router, which you might think, okay it's Cisco they're going to do something in networking, but the reason why we open-sourced it, and it's a piece that we actually use in our products, was there was not a virtual switch or router that had the scale, performance, or features that enabled the industry to utilize all the capabilities of the hardware underneath, whether it's computer or networking or security. And so the industry literally would have stalled with a limited feature set versus being able to utilize decades of networking knowledge and experience in things that are key and necessary, encapsulations, features, filters, quality of service etc., etc. There's a zillion of these pieces. And so there's a couple different ways, how can somebody make money off of this really is the fundamental question. We contribute into open-source communities and use that open-source to build products as well. And we can do this across video, we can do this in networking, and we do this in NFV, we do this in orchestration in these pieces and we also catalyze an ecosystem around these projects and then potentially around our portfolio as well. And so we continuously expand our ecosystem into startups that are using this technology, advancing the technology, enabling the industry to move faster, and trying to fundamentally create those business outcomes that our customers want. >> I just love that you just innately understand the value of an active community and that really comes through, so but unfortunately the janitors have rolled in, the vacuums are going, the garbage cans are rolling, so before they unplug all of our gear, I want to give you the last word Dave. What are some of your top priorities for 2017? >> So top priorities for 2017 really comes down to working towards filling the gaps I mentioned, identity and policy, but additionally number one, make sure that the automation orchestration policy around networking in a containerized stack is created. So we live through a long era of hypervisors and what it was like to work with open stack and what it was like in open-source and have to invent all this technology. We learned a ton. But it doesn't exist in a containerized world. So for 2017, fill the big gaps in the industry and work towards orchestrating and automating networking, compute, storage, and security in a containerized world. >> Pretty simple. I think that's the answer. I was going to say 42 is usually the answer, but I think that was it Dave. (laughter) >> I love 42. (laughing) >> Thanks Dave, so he's Dave Ward, Scott Raynovich, I'm Jeff Frick, you're watching TheCUBE from Open Networking Summit 2017. We'll see you tomorrow. Thanks for watching. (upbeat electronic music) >> You're also an entrepreneur, right? You know the business, you've been in the business.

>> Announcer: Live from Santa Clara, California, it's The Cube. Covering open networking summit 2017. Brought to you by the Linux foundation. >> Welcome back. We are live in Santa Clara at the open networking summit 2017. Been coming here for a couple years, it's a lot of open source going on in storage, for a long time, a lot of open source going on in compute for a long time, and you know, networking was kind of the last one, but we had Martin Casado on on earlier today. He says it's 10 years since he started Nicira. And now, it's a billion dollar revenue run raid inside vmware, so I think the software defined networking is pretty real. We're excited for this next segment, Scott Raynovich, been cohosting all day, good to see you again, Scott. But we're kind of shifting, we're going to add to open networking, we're going to add to open, not compute, but OpenStack, I get them all mixed up, we were just-- >> It's all infrastructure, it's all in the family. >> All right, so our next guest here, representing the OpenStack foundation, is Ildiko Vancsa, get that right? She is the ecosystem technical lead for OpenStack, welcome. And Lisa-Marie Namphy, she's now officially the OpenStack ambassador, which if you follow her on Twitter, you would have known that a long time ago. >> For the U.S. There's several others globally, but for the U.S., yeah. >> So first off, welcome. >> Thank you. >> And what is the OpenStack team doing here at open networking summit? >> So OpenStack itself is a multipurpose generated cloud platform, so we are not just looking into enterprise, IT use cases, but also trying to address the telecom and NFV space. And this is the conference where we are finding many of our ecosystem member companies represented, and we are also learning what's new in the networking space, what are the challenges of tomorrow and how we can start to address them today. >> Right, 'cause the telco is a very active space for OpenStack as well, correct, there's been a good market segment for you. >> Yes, it is an emerging area. I would say we have more and more telecommunications company around and they are also more and more involved in open source. Because I think it's kind of clear that they are also using open source for a while now, but using open source and participating in open source, those are two different things. So this kind of mindset change and transition towards participating In these communities and going out to the public field and do software development there and collaborate with each other and the enterprise IT segment as well, this is what is happening today and it is really great to see it. >> Host: Great, great. >> And you've seen more and more telco's participating in the OpenStack summits, there was an NFV day, I think, even going all the way back to the Atlanta summit. And certainly, in Barcelona, Ildiko was actually doing one of the main stage key notes, which was very focused on telco. And some of the main sponsors of this upcoming summit are telco's. So there's definitely a nice energy between telco and OpenStack. >> Now, why do you think the telco is just the one that's kind of getting ahead of the curve in terms of the adoption? >> Scalable low class clouds. (all laugh) >> Right, and we had John Donovan from AT&T said today that they're either rapidly approaching or going to hit, very soon, more than 50% of software defined networking within the AT&T network. So if there's any questions as to whether it's real or still in POC's, I think that pretty much says it's in production and running. >> I'm doing a lot more of that, so I also run the OpenStack user group for the San Francisco bay area and have been for the last three years, and if we're not talking about Kupernetes, or Docker and OpenStack, we're talking about networking. And tonight, actually, we're going to, the open contrail team is talking about some of the stuff they're doing with open contrail and containers and sort of just to piggyback off of this conference. And next week, as well, we're talking about the network functionality in Kupernetes at OpenStack, if you want to run in down to the OpenStack cloud. So it's a huge focus and the user group can't get enough of it. >> and your guys' show is coming up very, very soon. >> The OpenStack summit? >> Yes. >> Oh, absolutely, May 8th through 11th in Boston, Massachusetts. >> Host: Like right around the corner. >> Yeah. >> The incredible moving show, right? It keeps going and going and going. >> Yeah, yeah, there's going to be 6,000 plus people there. There was just some recent press releases about some of the keynotes that are happening there. There's a huge focus on, you know, I keep calling this the year of the user, the year of OpenStack adoption. And we're really, throughout the meetups, we're really doing a lot to try to showcase those use cases. So Google will be one that's onstage talking about some really cool stuff they're doing with OpenStack, some machine learning, just really intelligent stuff they're working on, and that's going to be a great keynote that we're looking forward to. Harvard will be up on there, you know, not just big name foundation members, but a lot of use cases that you'll see presented. >> So why do you think this is the year, what's kind of the breakthrough that it is the year of the user, would you say? >> Well, I think that just the reliability of OpenStack. I think enterprises are getting more comfortable. There are very large clouds running on OpenStack, more in Asia and in Europe and Ildiko can probably talk about it, particularly some of the telco related ones. But you know, the adoption is there and you see more stability around there, more integration with other, I don't know what to call it, emerging technologies like containers, like AI, like IOT. So there's a big push there, but I think enterprises have just, they have adopted it. And there's more expertise out there. We've focused a lot on the administrators. There's the COA, the certified administrator of, you know, OpenStack administrator exam you can take. So the operators have come a long way and they're really helping the customers out there get OpenStack clouds up and running. So I just think, you know, it's seven years now, into it, right, so we got to turn the corner. >> So there have been some growing pains with OpenStack, so what can you tell us about the metrics today versus, say, three or four years ago in terms of total installations, maybe breakdown of telecom versus enterprise, what kind of metrics do you have you there? >> I'll let you take that one. >> We are running, continuously running a user survey and we are seeing growing numbers in the telecom area. I'm not prepared with the numbers from the top of my head, but we are definitely seeing more and more adoption in the telecom space like how you mentioned AT&T, they are one of the largest telecom operators onboard in the community, and they are also very active, showing a pretty great example of how to adopt the software and how to participate in the community to make the software more and more NFV ready and ready for the telecom use cases. We also have, as Lisa-Marie just mentioned, the China area and Asia are coming up as well, like we have China Mobile and China Telecom onboard as well. Or Huawei, so we have telecom operators and telecom vendors as well, around the community. And we are also collaborating with other communities, so like who you see around OPNFV, OpenDaylight, and so forth. We are collaborating with them to see how we can integrate OpenStack into a larger environment as part of the full NFV stack. If you look into the ETSI NFV architectural framework, OpenStack is on the infrastructure layer. The NFV infrastructure and virtual infrastructure manager components are covered with OpenStack services mostly. So you also need to look into, then, how you can run on top of the hardware that the telecom industry is expecting in a data center and how to onboard the virtual network functions on top of that, how to put D management and orchestration components on top of OpenStack, and how the integration works out. So we are collaborating with these communities and what is really exciting about the Upcoming summit is that we are transforming the event a little bit. So this time, it will not be purely OpenStack focused, but it will be more like an open infrastructure, even. We are running open source days, so we will have representation from the communities I mentioned and we will also have Kubernetes onboard, for example, to show how we are collaborating with the representatives of the container technologies. We will also have Cloud Foundry and a few more communities around, so it will be a pretty interesting event and we are just trying to show the big picture that how OpenStack and all these other components of this large ecosystem are operating together. And that is going to be a super cool part of the summit, so the summit is May 8th through 11th and on May 9th, the CNCF, the Linux foundation, actually, behind this, the CNCF day, they're calling it Kupernetes day. And the whole day will be dedicated, there will be a whole track dedicated to Kupernetes, basically. And so they did another call for papers and it's like a little mini conference inside the conference. So that's kind of what I was saying about the adoption of other technologies. I'm sure the OpenStack foundation is putting those numbers together that you asked about and probably Jonathan or Bryce will stand onstage on the first day and talk about them. But what I think is more interesting and what I would encourage people to go, there's a Superuser magazine. Superuser does a great job telling the stories of what's happening out there, and some of these use cases, and who's adopting this technology and what they're doing with it. And those stories are more interesting than just, you know, the numbers. Because you can do anything with numbers and statistics, but these actual user stories are really cool so I encourage readers to go out to Superuser magazine and check that out. >> It's like, Lego uses it. >> There you go. >> I had to check real fast. >> Lot of information on there. They do a good job of that. >> Lego alligators. >> So you talked about this day with the Linux foundation, is there increasing amounts of cooperation between OpenStack and Linux foundation? Given all the projects that seem to be blossoming. >> Yeah, I don't even know that it needed to increase, there's always been nice energy between the two. There is, you know, Eileen Evans, who we know very well, was on the board of both, the first woman on both boards. She was my colleague for many years at Hewlett-Packard. She's still on the Linux foundation board and there's been a lot of synergy between those foundations. They've always worked closely together, especially things like the Cloud Foundry foundation that came out of the Linux foundation has always worked very closely with OpenStack, the OpenStack foundation, and the board members, and it's all one big happy family. We're all open source, yeah. >> And you talked about the enterprises being, you know, they've been using open source for a long time, Linux has been around forever. They're really more adopting kind of an open source ethos in terms of their own contributions back and participating back in. So you see just increased adoption, really, of using the open source vehicle as a way to do better innovation, better product development, and to get involved, get back to their engineers to get involved in something beyond just their day job. >> It is definitely a tendency that is happening, so it's not just AT&T, like, I can mention, for example, NTT DoCoMo, who now has engineers working on OpenStack code. They are a large operator in Japan. And it is really not something, I think, that a few years back, they would've imagined that they will just participate in an open source community. I've been involved with OPNFV for, I think, two years now, or two and a half. I'm an OPNFV ambassador as well, I'm trying to focus on the cross-community collaboration. And OPNFV is an environment where you can find many telecom operators and vendors. And it was a really interesting journey to see them, how they get to know open source more and more and how they learned how this is working and how working in public is like and what the benefits are. And I remember when a few people from, for example, DoCoMo came to OPNFV and they were, like, a little bit more shy, just exploring what's happening. And then like a half year later when they started to do OpenStack contributions, they had code batches merged into OpenStack, they added new functionalities, they kind of became advocates of open source. And they were like telling everywhere that open source is the way to go and this is what everyone should be doing and why it is so great to collaborate with other operators out in the public so you can address the common pain points together, rather than everyone is working on it behind closed doors and trying to invent the same wheel at the same time, separately. >> Right. >> So that was a really, really Interesting journey. And I think more and more companies are following this example. And not just coming and giving feedback, but also more and more participating and doing coding documentation work in the community. >> And I think if I can understand, what I think, also, the question you might have been asking, there wasn't a ton of python developers in the beginning and everybody's like how do we get these OpenStack developers in the company, you know, it was this huge shortage. And Linux was the little hanging fruit, it's like well, why do we just hire some Linux developers and then teach them python, and that's how a lot of OpenStack knowledge came into companies. So that was the trend. And I think enough companies, enough enterprises do see the value of something like OpenStack or Linux or Kupernetes or whatever the project has, Docker, to actually dedicate enough full time employees to be doing just that for as long as it makes sense and then maybe it's another technology. But we saw that for years, right, with OpenStack, huge companies. And there still are. Not always the same companies, depending on what a company needs and where they are, they absolutely find value in contributing back to this community. >> Okay, and you said you got a meetup tonight? >> I do, yeah. >> Give a plug for the meetup. >> Juniper, it's open contrail talking about open contrailing and containers. And it's at Juniper here in Sunnyville, so if you go to meetup.com/openstack, that's our user group. We're the first ones, we got that one. So meetup.com/openstack is the Silicon Valley, San Francisco bay area user group. And then next week, we're talking about networking and Kupernetes. >> All right, it's always good to be above the fold, that's for sure. All right, Ildiko, Lisa-Marie, great to see you again and thanks for stopping by, and we'll see you in Boston, if not before. >> Absolutely, we'll both be quite busy, we have four, both four presentations each, it's going to be a nutty week. So I'm looking forward to seeing you guys in Boston, always a pleasure, thanks for inviting us. >> Absolutely, all right, thanks for stopping by. With Scott Raynovich, I'm Jeff Frick, you're watching The Cube from open networking summit 2017. We'll be back after this short break, thanks for watching.