>> Narrator: Live, from Las Vegas, it's theCUBE. Covering IBM Think, 2018. Brought to you by IBM >> Hello everyone, welcome back to theCUBE, we are here on the floor at IBM Think 2018 in theCUBE studios, live coverage from IBM Think. I'm John Furrier, the host of theCUBE, and we're here with Stefanie Chiras, who is the Vice President of Offering Management IBM Cognitive Systems, that's Power Systems, a variety of other great stuff, real technology performance happening with Power, it's been a good strategic bet for IBM. Stefanie, great to see you again, thanks for coming back on theCUBE. >> Absolutely, I love to be on, John, thank you for inviting me. >> When we we had a brief (mumbles) Bob Picciano, who's heading up Power and that group, one of the things we learned is there's a lot of stuff going on that's really going to be impacting the performance of things. Just take a minute to explain what you guys are offering in this area. Where does it fit into the IBM portfolio? What's the customer use cases? Where does that offering fit in? >> Yeah, absolutely. So I think here at Think it's been a great chance for us to see how we have really transformed. You know, we have been known in the market for AIX and IBMI. We continue to drive value in that space. We just GA'd on, yesterday, our new systems, based Power9 Processor chip for AIX and IBMI in Linux. So that remains a strong strategic push. Enterprise Linux. We transformed in 2014 to embrace Linux wholeheartedly, so we really are going after now the Linux base. SAP HANA has been an incredible workload where over a thousand customers run in SAP HANA. And boy we are going after this cognitive and AI space with our performance and our acceleration capabilities, particularly around GPUs, so things like unique differentiation in our NVLink is driving our capabilities with some great announcements here that we've had in the last couple of days. >> Jamie Thomas was on earlier, and she and I were talking about some of the things around really the software stack and the hardware kind of coming together. Can you just break that out? Because I know Power, we've been covering it, Doug Balog's been on many times. A lot of great growth right out of the gate. Ecosystem formed right around it. What else has happened? And separate out where the hardware innovation is and technology and what's software and how the ecosystem and people are adopting it. Can you just take us through that? >> Yeah, absolutely. And actually I think it's an interesting question because the ecosystem actually has happened on both sides of the fence, with both the hardware side and the software side, so OpenPOWER has grown dramatically on the hardware side. We just released our Power9 processor chip, so here is our new baby. This is the Power9. >> Hold it up. >> So this is our Power9 here, 8 billion transistors, 14 miles of wiring and 17 layers of metal, I mean it's a technology wonder. >> The props are getting so small we can't even show on the camera. (laughing) >> This is the Moore's Law piece that Jenny was talking about in her keynote. >> That's exactly it. But what we have really done strategically is changed what gets delivered from the CPU to more what gets delivered at a system level, and so our IO capabilities. First chip to market, delivering the first systems to market with PCIe Gen 4. So able to connect to other things much faster. We have NVLink 2.0, which provides nearly 10x the bandwidth to transport data between this chip and a GPU. So Jensen was onstage yesterday from NVIDIA. He held up his chip proudly as well. The capabilities that are coming out from being able to transport data between the power CPU and the GPU is unbelievable. >> Talk about the relationship with NVIDIA for a second, 'cause that's also, NVIDIA stocks up a lot of (mumbles) the bitcoin mining graphics card, but this is, again, one use case, NVIDIA's been doing very well, they're doing really well in IOT, self-driving cars, where data performance is critical. How do you guys play in that? What's the relationship with NVIDIA? >> Yeah, so it has been a great partnership with NVIDIA. When we launched in 2013, right at the end of 2013 we launched OpenPOWER, NVIDIA was one of the five founding members with us, Google, Mellanox, and Tyan. So they clearly wanted to change the game at the systems value level. We launched into that with we went and jointly bid with NVIDIA and Mellanox, we jointly bid for the Department of Energy when we co-named it Coral. But that came to culmination at the end of last year when we delivered the Summit and Sierra supercomputers to Oak Ridge and Lawrence Livermore. We did that with innovation from both us and NVIDIA, and that's what's driving things like this capability. And now we bring in software that exploits it. So that NVLink connection between the CPU and the GPU, we deliver software called PowerAI, we've optimized the frameworks to take advantage of that data transport between that CPU and GPU so it makes it consumable. With all of these things it's not just about the technology, it's about is it easy to consume at the software level? So great announcement yesterday with the capabilities to do logistic regression. Unbelievable, taking the ability to do advertising analytics, taking it from 70 minutes to 1 and 1/2. >> I mean we're going to geek out here. But let's go under the hood for a second. This is a really kind of a high end systems product, at the kind of performance levels. Where does that connect to the go to market? Who's the buyer of it? Is it OEMs? Is it integrators? Is it new hardware devices? How do I get involved and who's the target customer? And what kind of developers are you reaching? Can you just take us through that who's buying this product? >> So this is no longer relegated to the elite set. What we did, and I think this is amazing, when we delivered the Summit and Sierra, right? Huge cluster of these nodes. We took that same node, we pulled it into our product line as the AC922, and we delivered a 4 GPU air-cooled version to market. On December 22nd we GA'd, of last year. And we sold to over 40 independent clients by the end of 2017, so that's a short runway. And most of it, honestly, is all driven around AI. The AI adoption, and it's a cross enterprise. Our goal is really to make sure that the enterprises who are looking at AI now with their developer are ready to take it into production. We offer support for the frameworks on the system so they know that when they do development on this infrastructure, they can take it to production later. So it's very much driven toward taking AI to the enterprise, and it's all over. It's insurance, it's financial services sector. It's those kinds of enterprise that are using AI. >> So IO sensitive, right? So IOT not a target or maybe? >> So you know when we talk out to edge it's a little bit different, right? So the IOT today for us is driving a lot of data, that's coming in, and then you know at different levels-- >> There's not a lot of (mumbles) power needed at the edge. >> There is not, there is not. And it kind of scales in. We are seeing, I would say, kind of progression of that compute moving out closer. Whether or not it's on, it doesn't all come home necessarily anymore. >> Compute is being pushed to where the data is. >> Stefanie: Absolutely right. >> That's head room for you guys. Not a priority now because there's not an intense (mumbles) compute can solve that. >> Stefanie: That's right. >> All right, so where does the Cloud fit into it? You guys powering IBMs Cloud? >> So IBM Cloud has been a great announcement this year as well. So you've seen the focus here around AI and Cloud. So we announced that HANA will come on Power into the Cloud, specializing in large memory sets, so 24 terabyte memory sets. For clients that's huge to be able to exploit that-- >> Is IBM Cloud using Power or not? >> That will be in IBM Cloud. So go to IBM Cloud, be able to deploy an SAP certified HANA on Power deployment for large memory installs, which is great. We also announced PowerAI access, on Power9 technology in IBM Cloud. So we definitely are partnering both with IMB Cloud as well as with the analytics pieces. Data Science Experience available on Power. And I think it's very important, what you said earlier, John, about you want to bring the capabilities to where the data is. So things like a lot of clients are doing AI on prem where we can offer a solution. You can augment that with capabilities like Watson, right? Off prem. You can also do dev ops now with AI in the IBM Cloud. So it really becomes both a deployment model, but the client needs to be able to choose how they want to do it. >> And the data can come from multiple sources. There's always going to be latencies. So what about blockchain? I want to get to blockchain. Are you guys doing anything in the blockchain ecosystem? Obviously one complaint we've been hearing, obviously, is some of these cryptocurrency chains like Ethereum, has performance issues, they got projects coming out. A lot of open source in there. Is Power even puttin' their toe in the water with blockchain? >> We have put our toe in the water. Blockchain runs on Power. From an IBM portfolio perspective-- >> IBM blockchain runs on Power or blockchain, or other blockchains? >> Like Hyperledger. Like Hyperledger will run. So open source, blockchain will run on Power, but if you look at the IBM portfolio, the security capabilities in Z14 that that brings and pulling that into IBM Cloud, our focus is really to be able to deliver that level of security. So we lead with system Z in that space, and Z has been incredible with blockchain. >> Z is pretty expensive to purchase, though. >> But now you can purchase it in the Cloud through IBM Cloud, which is great. >> Awesome, this is the benefit of the Cloud. Sounds like soft layer is moving towards more of a Z mainframe, Power, backend? >> I think the IBM Cloud is broadening the capabilities that it has, because the workloads demand different things. Blockchain demands security. Now you can get that in the Cloud through Z. AI demands incredible compute strength with GPU acceleration, Power is great for that. And now a client doesn't have to choose. They can use the Cloud and get the best infrastructure for the workload they want, and IBM Cloud runs it. >> You guys have been busy. >> We've been busy. (laughing) >> Bob Picciano's been bunkered in. You guys have been crankin' out... love to do a deeper dive on this, Stefanie, and so we'd love to follow up with you guys, and we told Bob we would dig into that, too. Question I have for you now is, how do you talk about this group that you're building together? You know, the names are all internal IBM names, Power... Is it like a group? Do you guys call yourself like the modern infrastructure group? Is it like, what is it called, if you had to explain it to outside IBM, AIs easy, I know what AI team does. You're kind of doing AI. You're enabling AI. Are you a modern infrastructure? What is the pillar are you under? >> Yeah, so we sit under IBM systems, and we are definitely systems proud, right? Everything runs on infrastructure somewhere. And then within that three spaces you certainly have Z storage, and we empower, since we've set our sites on AI and cognitive workloads, internally we're called IBM Cognitive Systems. And I think that's really two things, both a focus on the workloads and differentiation we want to bring to clients, but also the fact that it's not just about the hardware, we're now doing software with things like PowerAI software, optimized for our hardware. There's magic that happens when the software and the hardware are co-optimized. >> Well if you look, I mean systems proud, I love that conversation because you look at the systems revolution that I grew up in, the computer science generation of the 80s, that was the open movement, BSD, pre-Linux, and then now everything about the Cloud and what's going on with AI and what I call the innovation sandwich with data in the middle and blockchain and AI as bread. >> Stefanie: Yep. >> You have all the perfect elements of automation, you know, Cloud. That's all going to be powered by a system. >> Absolutely. >> Especially operating systems skills are super imprtant. >> Super important. Super important. >> This is the foundational elements. >> Absolutely, and I think your point on open, that has really come in and changed how quickly this innovation is happening, but completely agree, right? And we'll see more fit for purpose types of things, as you mentioned. More fit for purpose. Where the infrastructure and the OS are driving huge value at a workload level, and that's what the client needs. >> You know, what dev ops proved with the Cloud movement was you can have programmable infrastructure. And what we're seeing with blockchain and decentralized web and AI, is that the real value, intellectual property, is going to be the business logic. That is going to be dealing with now a whole 'nother layer of programmability. It used to be the other way around. The technology determined >> That's right. >> the core decision, so the risk was technology purchase. Now that this risk is business model decision, how do you code your business? >> And it's very challenging for any business because the efficiency happens when those decisions get made jointly together. That's when real business efficiency. If you make one decision on one side of the line or the other side of the line only, you're losing efficiency that can be driven. >> And open is big because you have consensus algorithms, you got regulatory issues, the more data you're exposed to, and more horsepower that you have, this is the future, perfect storm. >> Perfect storm. >> Stefanie, thanks for coming on theCUBE, >> It's exciting. >> Great to see you. >> Oh my pleasure John, great to see you. >> You're awesome. Systems proud here in theCUBE, we're sharing all the systems data here at IBM Think. I'm John Furrier, more live coverage after this short break. All right.

(bright orchestral music) >> Hello everyone, and welcome to theCUBE Conversations here in Palo Alto Studios. For theCUBE, I'm John Furrier, the co-founder of SiliconANGLE Media inc. My next guest is Bruce Arthur, who's the Vice President of engineering at Banter.ai. Good friend, we've known each other for years, VP of engineering, developer, formerly at Apple. >> Yes. >> Worked on all the big products; the iPad-- had the the tin foil on your windows back in the day during Steve Jobs' awesome run there. Welcome to theCUBE. >> Thank you, it's good to be here. >> Yeah, great, you've got a ton of experience and I want to get your perspective as a developer, VP of engineering, entrepreneur, you're doing a startup around AI. Let's have a little banter. >> Sure. >> Banter.ai is a little bit a chat bot, but the rage is DevOps. Software really models change, infrastructure as code, cloud computing. Really a renaissance of software development going on right now. >> It is, it's changing a lot. >> What's your view on this? >> Well, so, years and years ago you would work really hard on your software. You would package it up in a box and you'd send it over the wall and you hope it works. And that seems very quaint now because now you write your software, you deploy it the first day, and you change it six times that day, and you're A/B-testing it, you're driving it forward, it's so much more interactive. It does require a different skillset. It also doesn't, how do I say this carefully? It used to be very easy to be craft, to have high craft and make a very polished product, but you didn't know if it was going to work. Today you know if it's going to work, but you often don't get to making sure it's high quality, high craft, high value. >> John: So, the iteration >> Exactly, the iteration runs so fast, which is highly valuable, but you sort of just a little bit of you miss the is this really something I am proud of and I can really work with it because you know, now the product definition can change so quickly, which is awesome but it is a big change. >> And that artisan crafting thing is interesting, but now some are saying that the UX side is interesting because, if you get the back end working, and you're iterating, you can still bring that artisan flavor back. We heard that cloud computing vendors like Amazon, and I was just in China for Alibaba, they're trying to bring this whole design artisan culture back. Your thoughts on the whole artisan craft in software, because now you have two stages, you have deploy, iterate, and then ultimately polish. >> Right, so, I think it's interesting, it used to be, engineering is so expensive and time-consuming. You have to design it upfront and you make one version of it and you're done. That has changed now that engineering has gotten easier. You have better tools, we have better things, you can make six versions and that used to be, so back in the day at Apple, you would make six versions, five of which Steve would hate and throw out, and eventually they would get better and better and better and then you would have something you're proud of. Now those are just exposed. Now everybody sees those, it's a very different process. So you, I think, the idea that you. Engineering used to be this scarce resource. It's becoming easier now to have many versions and have more engineers working on stuff, so now it is much more can I have three design teams, can they compete, can they make all good ideas, and then who's going to be the editor? Who evaluates them and decides I like this from this one, I like that, and now let's put this together to make the right product. >> So, at Apple, you mentioned Steve would reject, well, that's well-documented. >> Sure. >> It's publicly out there that he would like, really look at the design-side. Was it Waterfall-based, was it Agile, Scrum, did you guys, was it like, do you lay it all out in front of him and he points at it? What were some of the work flows like with Steve Jobs? >> So, when he was really excited about something he would want to meet with them every week. He'd want to see progress every week. He'd give lots of feedback every week, there'd be new ideas. It was very Steve-focused. I think the more constructive side of it was the design teams were always thinking about What can we build, how do we put it in front of him, and I remember there was a great quote from a designer that said. It's not that Steve designs great things, it's that you show him three things, and if you throw him three bad things, he'll pick the least bad. If you show him three great things, he'll pick the most great, But it's not, it was more about the, you've got to iterate in the process, you've got to try ideas, you take ideas from different people and some of them, like, they sound like a great idea. When we talk, it sounds really good. You build it, and you're like, that's just not, that's just not right. So, you want, how do I say this? You don't want to lock yourself in up front. You want to imagine them, you want to build them, you want to try 'em. >> And that's, I mean, I've gotten to know the family over the years, too, through some of the Palo Alto interactions, and that's the kind of misperception of Steve Jobs, was that he was the guy. He enabled people, he had that ethos that-- >> He was the editor, it's an old school journalism metaphor, which is, he had ideas, he wanted, but he also, he ran the team. He wanted to have people bring their ideas and come in. And then he decided, this is good, this is not. That's better, you can do better, let's try this. Or, sometimes, this whole thing stinks. It's just not going anywhere. So, like, it was much more of that. Now it's applied to software, and he was a marketing genius, about sort of knowing what people were going to go for, but there was a little bit of a myth for it, that there's one man designing everything. That is a very saleable marketing story. >> The mythical man. (laughs) >> Well, it's powerful, but no, there's a lot of people, and getting the best work of all those people. >> I mean, he's said on some of the great videos I've watched on YouTube over the years, Hire the best people, only work with the best, and they'll bring good stuff to the table. Now, I want to bring that kind of metaphor, one step further for this great learning lesson, again it's all well-documented on YouTube. Plenty of Steve videos there, but now when you go to DevOps, you mention the whole quality thing and you got to ship fast, iterate, you know there's a lot of moving fast break stuff as Zuckerberg would say, of Facebook, although he's edited his tune to say move fast and be reliable. (laughing) Welcome to the enterprise, welcome to software and operations. This is now a scale game at the enterprise side 'cause, you know, you start seeing open source software grow so much now, where a lot of the intellectual property might be only 10% of software. >> Right. >> You might be using other pieces. You're packaging it so that when you get it to the market, how do bring that culture? How do you get that innovation of, Okay, I'm iterating fast, how do I maintain the quality. What are some of your thoughts on that? Because you've got machine learning out there, you've got these cool things happening. >> Yup. So, you want, how do I say this? You just, you really need to leave time to schedule it. It needs to be in your list. There's a lot of figuring out what are we going to build and you have to try things, iterate things, see if they resonate with consumers. See if they resonate with people who want to pay. See if they resonate with investors. You have to figure than out fast, but then you have to know that, okay, this is a good prototype. Now I have to make it work better because the first version wouldn't scale well, now it has to scale, now it has to work right for people, now you have to have a review of: here's the bugs, here's the things that are not working. Why does this chatbot stop responding sometimes? What is causing that? Now, the great story is, with good DevOps, you actually have a system that's very good at finding and tracking those problems. In the old world, so the old world with the shrink-wrap software, you'd throw it over the fence. If it misbehaves, you will never know. Today you know. You've got alerts, you've got pagers going off, you've got logs, >> It's instrumented big-time. >> Yeah, exactly, you can find that stuff. So, since you can actually make, you can make very high-quality software because you have so much more data about what's going on with it, it's nice. And actually, chatbot software has this fascinating little side effect, with, because it's all chats and it's all text, there are no irreproducible bugs. You can go back and look at exactly what happened. I have a recording, I know exactly what happened, I know exactly what came in, I know what came out, and then I know that this failure happened. So, it's very reproducible, sort of, it's nice you can, it doesn't always work this way, but it's very easy to track down problems. >> It's event-based, it's really easy to manage. >> Exactly, and it's just text. You can just read it. It's not like I have to debug hacks, it's just these things were said and this thing died. >> No core dumps. (laughs) >> No, there's nothing that requires sophisticated analysis, well the code is one thing, but like, the sequence of events is very human-readable, very understandable. >> Alright, so let's talk about the younger generation. So, we've been around the block, you and I. We've talked, certainly many times around town, about the shifts, and we love these new waves. A lot of great waves coming in, we've seen many waves. What's going on, in your mind, with the younger generation? Because this is a, some exciting things happening. Decentralized internet. >> Bruce: Yup. >> There's blockchain, getting all the attention. Outside of the hype, Alpha VCs, Alpha engineers, Alpha entrepreneurs are really honing in on blockchain because they see the potential. >> Sure. >> Early people are seeing it. Then you've got cloud, obviously unlimited compute potentially, the new, you know, kind of agile market. All these young guys, they never shipped, actually never loaded Linux on a server. (laughing) So, like, what are you seeing for the younger guys? And what do you see as someone who's experienced, looking down at the next, you know, 20 year run we see. >> So, I think what I see that's most exciting is that we now have people solving very non-technical problems with technology. I think it used to be, you could build a computer, you could write code, but then, like, your space was limited to the computer in front of you. Like, I can do input and outputs. I can put things on the screen, I can make a video game, but it's in this box. Now everyone's thinking of much bigger, Solving bigger problems. >> John: Yeah, healthcare, we're seeing verticals. >> Yeah, healthcare's a massive one. You can, operation things, shipping products. I mean, who would've thought Amazon was going to be delivering things, basically. I mean, they're using technology to solve the physical delivery of objects. That is, the space of what people are tackling is massive. It' no longer just about silicon and programming, it's sort of, any problem out there, there's someone trying to apply technology, which is awesome and I think that's because these people these youngsters, they're digital natives. >> Yeah. >> They've come to expect that, of course video conferencing works, of course all these other items work. That I just need to figure out how to solve problems with them, and I'm hopeful we're going to see more human-sized problems solved. I think, you know, we have, technology has maybe exacerbated a few things and dislocated, cost a lot of people jobs. Disconnected some people from other sort of stabilizing forces, >> Fake news. (laughs) >> Fake news, you know, we need-- >> John: It's consequences, side effects. >> I hope we get people solving those problems because fake news should now be hard to solve. They'll figure it out, I think, but, like, the idea is, we need to, technology does have a bit of a responsibility to solve, fix some of the crap that it broke. Actually, there's things that need, old structures, journalism is an old profession. >> Yeah. >> And it used to actually have all these wonderful benefits, but when the classified business went down the tubes, it took all that stuff down. >> Yeah. >> And there needs to be a venue for that. There needs to be new outlets for people to sort of do research, look things up, and hold people to account. >> Yeah, and hopefully some of our tools we'll be >> I hope so. >> pulling out at Silicon Angle you'll be seeing some new stuff. Let's talk about, like just in general, some of the fashionable coolness around engineering. Machine learning, AI obviously tops the list. Something that's not as sexy, or as innovative things. >> Sure. >> Because you have machines and industrial manufacturing plant equipment to people's devices. Obviously you worked at Apple, so you understand that piece, with the watch and everything. >> Yup, >> So you've got, that's an internet, we're things, people are things too. So, machines and people are at the edge of the network. So, you've got this new kind of concept. What gets you excited? Talk about how you feel about those trends. >> So, there's a ton going on there. I think what's amazing is the idea that all these sensors and switches and all the remote pieces can start to have smarts on them. I think the downside of that is some of the early IoT stuff, you know, has a whole open SSL stack in it. And, you know, that can be out of date, and when you have security problems with that now your light switch has access to your tax returns and that's not really what you want. So, I think there's definitely, there's a world coming, I think, at a technical level, we need to make operating systems and tools and networking protocols that aren't general purpose because general purpose tools are hackable. >> John: Yeah. >> I need to have a sensor and a switch that know how to talk to each other, and that's it. They can't rewrite code, they can't rewrite their firmware, they can't, like, I want to be able to know that, you have a nice office here, if somebody came in and tried to hack your switches, would you ever know? And the answer's like, you'd have no idea, but when you have things that are on your network and that serve you, if they're a general, if they're a little general purpose computing device, they're a mess. Like, you know, a switch is simple. A microphone, a microphone is simple. There's an output from it, it needs, I think we, >> So differentiated software for device. >> Well, let's get back to old school. You studied operating systems back in the day. >> Yeah. >> A process can do whatever the hell it wants. It can read from memory, it can write to disk, it can talk to all these buses. It's a very, it can do, it's very general purpose. I don't want that in my switch. I want my switch to be sort of, much more of these old little micro-controller. >> Bounded. >> Yeah, it's in a little box. I mean, so the phone and the Mac have something called Sandbox, which sort of says, you get a smaller view of the world. You get a little piece of the disk, you can't see everything else, and those are parts of it, but I think you need even more. You need, sort of, this really, I don't want a general purpose thing, I want a very specific thing that says I'm allowed to do this and I'm allowed to talk to that server; I don't have access to the internet. I've got access to that server. >> You mentioned operating systems. I mean, obviously I grew up in the computer science genre of the '80s and you did as well. That was a revolution around Unix. >> Yes. >> And then Berkeley, BSD, and all that stuff that happened around the systems world, operating systems, was really the pioneers in computing at that time. It's interesting with cloud, it's almost a throwback now to systems thinking. >> Bruce: It's true, yeah. >> You know, people looking at, and you're discussing it. >> Bruce: Yeah, Yeah. >> It's a systems problem. >> Yeah, it is. >> It's just not in a box. >> Right, and I think we witnessed the, let's get everyone a general purpose computer and see what they can do. And that was amazing, but now you're like I don't want everything to be a general I want very specific, I want very little thing, dedicated things that do this really well. I don't want my thermostat actually tracking when I'm in the house. You know, I want it to know, eh, maybe there's someone in the house, but I don't want it to know it's me. I don't want it reporting to Google what's going on. I want it to track my temperature and manage that. >> Our Wikibon team calls the term Unigrid, I call it hypergrid because essentially it's grid computer; there's no differentiation between on-premise and cloud. >> Right. >> It's one pool of resource of compute and things processes. >> It is, although I think, and that's interesting, you want that, but again you want it, how do I say this? I get a little nervous when all of my data goes to some cloud that I can't control. Like, I would love if, I'll put it this way. If I have a camera in my house, and imagine I put security cameras up, I want that to sort of see what's going on, I don't want it to publish the video to anywhere that's out of my control. If it publishes a summary that says, oh, like, someone came to your door, I'm like, okay, that's a good, reasonable thing to know and I would want to get that. So, Palo Alto recently added, there's traffic cameras that are looking at traffic, and they record video, but everyone's very nervous about that fact. They don't want to be recorded on video. So, the camera, this is actually really good, the camera only reports number of cars, number of bikes, number of pedestrians, just raw numbers. So you're pushing the processing down to the end and you only get these very anonymous statistics out of it and that's the right model. I've got a device, it can do a lot of sophisticated processing, but it gives nice summary data that is very public, I don't think anyone's really >> There's a privacy issue there that they've factored into the design? >> Yes, exactly. It's privacy and it's also the appropriateness of the data, you don't want, yeah, people don't want a camera watching them when they go by, but they're happy and they're like, oh, yeah, that street has a big increase in traffic, And there's a lot of, there were accidents here and there's people running red lights. That's valuable knowledge, not the fact that it's you in your Tesla and you almost hit me. No. (laughs) >> Yeah, or he's speeding, slow down. >> Exactly, yeah, or actually if you recorded speeders the fact that there's a lot of speeding is very interesting. Who's doing it, okay, people get upset if that's recorded. >> Yeah, I'm glad that Palo Alto is solving their traffic problem, Palo Alto problems, as we say. In general, security's been a huge issue. We were talking before we came on, about just the security nightmare. >> Bruce: Yes. >> A lot of companies are out there scratching their heads. There's so much of digital transformation happening, that's the buzzword in the industry. What does that mean from your standpoint? Because engineers are now moving to the front lines. Developers, engineering, because now there's a visibility to not just the software, it's an end goal. They call it outcome. Do you talk to customers a lot around, through your entrepreneurial venture, around trying to back requirements into product and yet deliver value? Do you get any insight from the field of kind of problems, you know, businesses are generally tryna solve with tech? >> So, that's interesting, I think when we try to start tech companies, we usually have ideas and then we go test that premise on customers. Perhaps I'm not as adaptable as I should be. We're not actually going to customers and asking them what they want. We're asking them if this is the kind of thing that would solve their problems. And usually they're happy to talk to us. The tough one, then, is then are they going to become paying customers, there's talking and there's paying, and they're different lines. >> I mean, certainly is validation. >> Exactly, that's when you really know that they care. It is, it's a tough question. I think there's always, there's a category of entrepreneur that's always very knowledgable about a small number of customers and they solve their problems, and those people are successful and they're often, They often are more services-based, but they're solving problems because they know people. They know a lot of people, they know what their paying point are. >> Alright, so here's the real question I want to know is, have you been back to Apple in the new building? >> Have I been to, I have not been in the spaceship. (laughing) I have not been in the spaceship yet. I actually understand that in order to have the event there, they actually had to stop work on the rest of the building because the construction process makes everything so dirty; and they did not want everyone to see dirty windows, so they actually halted the construction, they scrubbed down the trees, they had the event, and now it's, but now it's back. >> Now it's back to, >> So, I'll get there at some point. >> Bruce Arthur it the Vice President of Banter.ai, entrepreneur, formerly of Apple, good friend, Final question for you, just what are you excited about these days and as you look out at the tooling and the computer science and the societal impact that is seen with cloud and all these technologies, and open source, what do you, what are you excited about? >> I'm most excited, I think we actually have now enough computing resources and enough tools at hand that we can actually go back and tackle some harder computer science problems. I think there's things that used to be so big that you're like, well, that's just not, That's too much data, we could never solve that. That's too much, that would take, you know, that would take a hundred computers a hundred years to figure out. Those are problems now that are becoming very tractable, and I think it's been the rise of, yeah, it starts with Google, but some other companies that sort of really made these very large problems are now tractable, and they're now solvable. >> And open source, your opinion on open source these days? >> Open source is great. >> Who doesn't love more code? (laughs) >> Well, I should back this up, Open source is the fastest way to share and to make progress. There are times where you need what's called proprietary, but in other words valuable, when you need valuable engineers to work on something and, you know, not knowing the providence or where something comes from is a little sticky, I think there's going to be space for both. I think open source is big, but there's going to be-- >> If you have a core competency, you really want to code it. >> Exactly, you want to write that up and you-- >> You can still participate in the communities. >> Right, and I think open source is also, it's awesome when it's following. If there's something else in front, it follows very fast, it does a very good job. It's very thorough, sometimes it doesn't know where to go and it sort of meanders, and that's when other people have advantages. >> Collective intelligence. >> Exactly. >> Bruce, thanks for coming on. I really appreciate it, good to see you. This is a Cube Conversation here in the Palo Alto studio, I'm John Furrier, thanks for watching. (light electronic music)

(upbeat music) >> Narrator: Live from the Seattle, Washington, it's the Cube on the ground, covering KubeCon 2016. Brought to you by the Linux Foundation and Red Hat. Here's your host, John furrier. >> Hello, everyone. Welcome to the Cube special on the ground coverage of KubeCon or CloudNativeCon, this is an event. Seattle booming with attendance, great growth from last year, and we are here in Seattle covering it all. And my next guest is Dan Kohn, who's the executive director of the CNCF, which stands for the Cloud Native Computing Foundation. It's a mouthful, but it's super important part of the Linux foundation. Welcome. >> Thanks so much, really glad to be here. >> Yeah, so big fan of what's happening here. One, the event's awesome. Great uptake from last attendance from last year. >> Yeah, unfortunately, maybe a little too much. We're a little crowded in the foyer and a little bumping on the way into getting in the restroom and everything, but it's one of the challenges of fast growing technology space is trying to figure out a year ahead of time, what size space to get? >> And how many people to squeeze in without getting the fire marshal on your back. >> Exactly. >> Certainly this is going to be a great one because the hallway conversation has been spectacular, and normally the excitement's pretty strong at tech events like this because they're developers, so there's a lot of collaboration going on. But you have a kind of an air of really forward-thinking entrepreneurial kind of thinking going on here. And I haven't seen that in a while and I think that's one of the main things that we're seeing that came out of the containers, Kubernetes. I would say the unveiling and the clarity of at least a path. >> Yes, absolutely. >> And the importance of that. So that's been super important to (indistinct) community. Now making that a part of a foundation, an open source, has challenges. So that's what you're doing. So give us the plan, what's the strategy? >> Sure, so I'm actually relatively new to the space. I just became an executive director five months ago, and this is somewhat of a coming out party. This is the first big event that we've run as the first CloudNativeCon. And it's really just been extraordinary. I'm thrilled to see the range where we're getting some of the biggest companies in the world of the Cisco's, and Wallway's, and IBM's, Red Hat's and such. And then tons of startups, and a lot of real diversity in the end-users as well. Of startups looking at Kubernetes, massive companies, just saw a great presentation from Ticketmaster, about them having 50 year old technology that they're moving forward and putting into containers. >> So in the growth of the market, one of the challenges is to kind of, you know, not so much be a chess player, but be a gardener if you will, kind of like let the flowers bloom, if you will. And that's a challenge cause opensource is very opinionated, but there's also a lot of passion involved. So how do you look at, what's your philosophy on establishing kind of a rules of engagement? How do you foster the innovation? Certainly the market drivers are for more growth, but people have inhibitors on the enterprise that we hear about, support and these things of that nature. So how do you enable that? What's your strategy and what's your view? >> Sure, so CNCF is a very new organization. And my goal on it is to look at a lot of the giants that have come before us of like the Internet Engineering Task Force and the Apache Software Foundation and OpenStack. And my goal is to try and learn from them and ideally to try and make entirely new and different mistakes as opposed to the ones that they may have made in the past. So one of the things that's a little unusual in our setup is that we very much separate all of the technology decisions from the business decisions. We have a governing board of a bunch of the biggest technology companies in the world, the ones I mentioned, plus Google and Samsung just joined, which we're very excited about, a number of others. But they can't actually adopt projects in. So we have a separate group called the technical oversight committee, which is some of the top architects in the cloud space. So we have folks like Ben Hindman of Mesosphere, and Solomon Hykes of Docker, Brian Gantt of Google, and six others, and that's the group that looks at new projects and evaluates them and talks to them and decides whether to adopt them into CNCF or not. And we feel that that separation is really critical so that the technology decisions are not being biased by the business one. >> Yeah, it's always hard to foster growth in the innovation around business models, conflicting with the technology enablement, that's really key. Great to see that decoupling. So on the business model side, thoughts on things that you've learned and observed, learnings that you've had in your past career and applying that now, I mean, the Bait, the rage is on, Open Core to Apache, GPL, you saw some things going on there. So there's like all kinds of different approaches. Are there any thoughts of the winds blowing any which way or the other? >> Sure, I was previously the chief operating officer at the Linux Foundation between '06 and '10, and I definitely think you can, CNCF as part of the Linux Foundation, we took that model of saying, "the technology decisions "need to be separate from business ones." One thing that's interesting to me is that when I was last in this space 10 years ago, people were perfectly fine. Linux Journals, GPL, people were fine with free licenses like MIT and BSD. Since then, and for this group, there is an enormous focus on the Apache license. And the reason why, is the fear of submarine patents. And so the whole goal of CNCF is for us to be an intellectual property no fly zone. That you can have all of these companies that compete very hard in the marketplace, but they can come together and collaborate and share their ideas and their technology without the belief that a couple years later, someone's going to be able to trick someone else in with a lawsuit, and win that. And the Apache license is really the industry consensus right now for best practices. >> It's interesting cause that no fly zone gives the freedom for the creation and the invention side of it. The patent thing is always worrisome, but in general, there's also the business model down the road kind of approach. Which is, "let's go innovate." Apache has done great on packaging. Have someone get some traction. It fosters the community aspect as well as a startup. Maybe not thinking about packaging. >> No, we have an advantage that we're not, unlike OpenStack as an example, we're not trying to come up with the projects ourself. What we're actually doing is scouring the Cloud Native landscape, talking to different groups and saying, "Oh, what do we think is "the best in class project out there?" And in some cases it's more than one, but today we just announced the fourth project that's added to the CNCF. So we have Kubernetes, we have Prometheus, which is a monitoring application. OpenTracing is a tracing, and then today we just added Fluentd, which is a logging solution. And this is the idea that if you have dozens or hundreds of different applications and projects that are each producing a log stream, and then you have a perhaps dozens of other applications that are consuming it, you don't want to have an M times N problem of creating adapters for all of them. Instead, you can plug them all into Fluentd, it has over 300 adapters for different solutions out there. And that provides one comprehensive approach. But what's interesting is that we don't need to win over the community and say, "Oh, here's this project you may not have heard of." There's actually over 2000 users of that today. But by having them here at CNCF, showing how it plugs into other technologies of ours, we think we can hope-- >> You're cross-pollinating? >> Dan: Exactly. >> You're letting it bubble up and you're not being a-- >> Dan: That's exactly the metaphor. >> (laughs) A dictator. Okay, and back to the project side, this is awesome. So you have some gravity around these projects. Is there any cadence or expectation, or is it free for all in terms of the velocity of adoption of projects that the technical committee will oversight? >> We would love to be at the pace of one a month. And I don't know that we'll quite get that fast. One big change that we're hoping to make in the next month or two. When our first two projects were Kubernetes and Prometheus, those are two of the fastest growing best respected projects on GitHub right now. We didn't want to have such a high milestone for every other project we considered. So we're adopting what we think we're going to call an inception stage of earlier projects that we're going to sort of try out, but they have to essentially prove themselves within 12 months. And hopefully that'll allow us to keep a pretty good velocity where we think there's a fantastic number of projects, we think as a community, we can-- >> Yeah, let people fight it out, surface stuff and let people kick the tires, right? That's the incubation period basically. What about the forking and all the battle cage matches that go on, how do you want to handle that or you just let nature take its course? Is that philosophy there? >> Thankfully, when we look at the space and this is really coming out of the Linux Space as well, anyone can fork, and of course it has a slightly different connotation now with GitHub, where when you make a change, you fork it, but there's also just a massive centripetal force pushing people together. And when you have a really high velocity of changes, the idea of forking and you would lose out on that, becomes a lot less appealing. And so, so far thankfully, all of our members and everyone in the community has really been on board on having a single head on working together to have that consultation. >> We just had Richard Kaufman on from, I think Robert Kaufman, I mean, from Samsung, he was talking about that the number two contributor is other. >> Dan: Yes. >> Which is a nice balance to the whole critical mass. >> It's an incredible accomplishment cause for Google to pull in enough people that they're no longer the majority contributor, is something that we're thrilled with. >> Yeah, it's great to see you have Richard Kaufman. Google is the number one contributor, are you worried about that? Maybe, they've been certainly good actors in the community. I mean, they had MapReduce and let Cloudera run with it, look at what happened with that? So, we kind of all know this backstory of Kubernetes, they're kind of letting it bloom on its own. That's consistent with their current posturing? >> Well, I don't think they want to have another Cloudera. >> Which is why they embraced Kubernetes. >> But I definitely don't think it's fair to say that they're doing it on their own. They're still the largest contributor of any one company and they have a massive amount of resources, and I think they see it as a really key technology, it's something they mentioned-- >> What I was referring to is that Cloudera kind of took MapReduce under their wing and made a commercial venture out. >> Dan: Oh yeah, absolutely. >> I think Google didn't want that. >> No, and they, I mean, the way I think about it is, they had this technology a few years ago. This is definitely oversimplified. They could have kept it as a proprietary in the house thing, like Amazon Elastic Container Service. They could have made it an internal open source project, like Go, or they could have just created a Kubernetes foundation that allowed other people in, but they still controlled it. But instead they were really interested in working with the Linux Foundation and creating this Cloud Native Computing Foundation that was always designed to be much more than just Kubernetes. And that really was about trying to push the project out of the nest. But I will say that my understanding is they're still see that as an absolutely core for their business. >> Yeah, I got to give Google props out there for that because they did do the right thing there. they put it out in the open, they did a line, and they could have land grabbed that, in a different way, I mean, certainly not the way that one was above. Final question on this event, KubeCon or KubernetesCon, KubeCon, it's KubeCon, however people call it. Not to confuse with the Cube, this Cube product which is seven years and might be trademark infringement but yeah, we'll get that later. >> Dan: With a K. (both laughing) >> It's still causing a lot of confusion. But that aside, CloudNativeCon also is in conjunction, this is part of the expansion you were mentioning. Talk about the vision for the events, you got one in Berlin coming up, and certainly you could have had probably at least a few more thousand people here for sure. >> Oh well, certainly a few more hundred. And we do feel a little bad that we didn't quite aim high enough. So our vision going forward is that we have CloudNativeCon that represents all of our projects, and that KubeCon represents the biggest part of CloudNativeCon. So it's multiple tracks. It's what a ton of folks go for but we think that it also gives us a chance to expose those people to our other projects, and by the time we get to Berlin, we're certainly hoping that we have another two or three or more projects-- >> And the date on Berlin? >> It's March 29th and 30th. And then we also announced that we're going to be in Austin, in early December. And I'll say that for both of those events, we're tripling the capacity from what we had last year. So we're hoping not to be so crowded. >> I was talking to Andy Jassy last night, we had a one-on-one with him and he's talking about the first Reinvent, he didn't think he can get 4,000 people there as packed. I think you might be, having to look at more capacity potentially. I mean, at this pace. >> It's the hard question is we'd actually like to be signing contracts for 2018, and it's just really hard to predict what the right size is to get for that, because I feel terrible about the fact that we did turn people away, especially end-users that we'd like to be introducing to this space. >> Yeah, well, I can attest people watching this, definitely a fire marshal issue, because it's really packed. That's why we're in a separate room here. There was sunlight in the background earlier. Normally, we're on the show floor with the Cube, but yeah, every space is taken, hallways are jamming. >> The other thing I'll mention though, is that we are also interested in going out and reaching customers and vendors where they are. So we're going to have a booth at AWS Reinvent, and we're looking at other conferences that we can be at to help spread the Cloud Native word. >> We're certainly going to be able to have a hundred events this year, so let us know where you're at, we'll certainly bring you guys on. Let me give you the final word. Tell the folks why Kubernetes is so important. Why is this movement, why are people so excited here? For the folks that couldn't make it, what's the vibe, why is it important, and what's the impact to customers in the industry? >> So the belief is that if you're deploying a new modern software application that, putting into containers, using an orchestration platform like Kubernetes, dividing your app up into microservices is a really such a benefit in terms of optimizing your resources, and tying into a whole rapid development process, continuous integration, continuous deployment, that not doing it almost makes it impossible to compete. And so we think there's just a ton of momentum around containerization and orchestration. >> And the speed of the innovation is one of those things if you're not on it, you fall further behind and it takes more energy to catch up if you try to do it by yourself. That's the benefit of the collective communities and it highlights open source. >> Right. >> Big time in terms of successes. Dan, thanks so much for coming on, sharing the perspective, congratulations and sorry for the folks who couldn't make it, hopefully this video will help. This is the Cube here in Seattle for special coverage of CloudNativeCon and KubeCon, here in Seattle. Thanks for watching, I'm John furrier. >> Dan: Thanks. (upbeat music)