>> Narrator: From around the globe, it's theCUBE presenting enterprise digital resilience on hybrid and multicloud brought to you by Io-Tahoe. >> Okay, now we're going to go into the demo and we want to get a better understanding of how you can leverage OpenShift and Io-Tahoe to facilitate faster application deployment. Let me pass the mic to Sabita, take it away. >> Thanks, Dave. Happy to be here again. >> Guys as Dave mentioned my name's Sabita Davis. I'm the Enterprise Account Executive here at Io-Tahoe. So today we just wanted to give you guys a general overview of how we're using OpenShift. >> Yeah, hey, I'm Noah, Io-Tahoe's Data Operations Engineer working with OpenShift and I've been learning the ins and outs of OpenShift for like the past few months. And I'm here to share what I've learned. >> Okay so before we begin I'm sure everybody wants to know Noah. What are the benefits of using OpenShift? >> Well, there's five that I can think of, faster time to operations, simplicity, automation, control and digital resilience. >> Okay, so that's really interesting because those are the exact same benefits that we at Io-Tahoe deliver to our customers. But let's start with faster time to operation, by running Io-Tahoe on OpenShift is it faster than let's say using Kubernetes and other platforms? >> Well, our objective at Io-Tahoe is to be accessible across multiple cloud platforms, right? And so by hosting our application in containers we're able to achieve this. So to answer your question it's faster to create end user application images using container tools like Kubernetes with OpenShift as compared to like Kubernetes with Docker, Kryo >> or Containerd. >> Okay, so we got a bit technical there. Can you explain that in a bit more detail? >> Yeah, there's a bit of vocabulary involved. So basically containers are used in developing things like databases, web servers or applications such as Io-Tahoe. What's great about containers is that they split the workload. So developers can select the libraries without breaking anything. And CIS admins can update the host without interrupting the programmers. Now OpenShift works hand-in-hand with Kubernetes to provide a way to build those containers for applications. >> Okay, got it. So basically containers make life easier for developers and system admins. So how does OpenShift differ from other platforms? >> Well, this kind of leads into the second benefit I want to talk about which is simplicity. Basically there's a lot of steps involved with when using Kubernetes with Docker but OpenShift simplifies this with their source to image process that takes the source code and turns it into a container image but that's not all. OpenShift has a lot of automation and features that simplify working with containers an important one being its web console. So here I've set up a light version of OpenShift called CodeReady Containers. And I was able to set up for application right from the web console. And I was able to set up this entire thing in Windows, Mac and Linux. So it's environment agnostic in that sense. >> Okay, so I think I see in the top left that this is a developer's view. What would a systems admin view look like? >> That's a good question. So here's the administrator view and this kind of ties into the benefit of control. This view gives insights into each one of the applications and containers that are running and you can make changes without affecting deployment. And you can also within this view set up each layer of security and there's multiple that you can prop up but I haven't fully messed around with it because since with my luck, I'd probably lock myself out. >> Okay, so that seems pretty secure. Is there a single point security such as you user login or are there multiple layers of security? >> Yeah, there are multiple layers of security. There's your user login, security groups and general role based access controls but there's also a ton of layers of security surrounding like the containers themselves. But for the sake of time, I won't get too far into it. >> Okay, so you mentioned simplicity and time to operation as being two of the benefits. You also briefly mentioned automation and as you know automation is the backbone of our platform here at Io-Tahoe. So that certainly grabbed my attention. Can you go a bit more in depth in terms of automation? >> OpenShift provides extensive automation that speeds up that time to operation, right? So the latest versions of OpenShift come with a built-in cryo container engine which basically means that you get to skip that container engine installation step. And you don't have to like log into each individual container hosts and configure networking, configure registry servers, storage, et cetera. So I'd say it automates the more boring kind of tedious processes. >> Okay, so I see the Io-Tahoe template there. What does it allow me to do? >> In terms of automation in application development. So we've created an OpenShift template which contains our application. This allows developers to instantly like set up a product within that template or within that, yeah. >> Okay, so Noah, last question. Speaking of vocabulary, you mentioned earlier digital resilience is a term we're hearing especially in the banking and finance world. It seems from what you described industries like banking and finance would be more resilient using OpenShift, correct? >> Yeah, in terms of digital resilience, OpenShift will give you better control over the consumption of resources each container is using. In addition, the benefit of containers is that like I mentioned earlier sysadmins can troubleshoot the servers without bringing down the application. And if the application does go down it's easy to bring it back up using the templates and like the other automation features that OpenShift provides. >> Okay, so thanks so much Noah. So any final thoughts you want to share? >> Yeah, I just want to give a quick recap of like the five benefits that you gain by using OpenShift. The five are time to operation, automation, control, security and simplicity. You can deploy applications faster, you can simplify the workload, you can automate a lot of the otherwise tedious processes, and maintain full control over your workflow and you can assert digital resilience within your environment. >> So guys, thanks for that appreciate the demo. I wonder you guys have been talking about the combination of Io-Tahoe and Red Hat. Can you tie that in Sabita to digital resilience specifically? >> Yeah, sure Dave. So when we speak to the benefits of security controls in terms of digital resilience at Io-Tahoe we automated detection and apply controls at the data level. So this would provide for more enhanced security. >> Okay, but so if you were to try to do all these things manually I mean, what does that do? How much time can I compress? What's the time to value? >> So with our latest versions of Io-Tahoe we're taking advantage of faster deployment time associated with containerization and Kubernetes. So this kind of speeds up the time it takes for customers start using our softwares. They'd be able to quickly spin up Io-Tahoe in their own on-premise environment or otherwise in their own cloud environment like including AWS, Azure, Oracle GCP and IBM cloud. Our quick start templates allow flexibility to deploy into multicloud environments all just using like a few clicks. >> Okay, so now I'll just quickly add, so what we've done Io-Tahoe here is we've really moved our customers away from the whole idea of needing a team of engineers to apply controls to data as compared to other manually driven workflows. So with templates, automation, pre-built policies and data controls one person can be fully operational within a few hours and achieve results straight out of the box on any cloud. >> Yeah, we've been talking about this theme of abstracting the complexity that's really what we're seeing is a major trend in this coming decade. Okay, great. Thanks Sabita, Noah. How can people get more information or if they have any follow up questions, where should they go? >> Yeah, sure Dave I mean if you guys are interested in learning more reach out to us @infoatiotahoe.com to speak with one of our sales engineers. I mean, we'd love to hear from you. So book a meeting as soon as you can. >> All right, thanks guys. Keep it right there for more cube content with Io-Tahoe. (gentle music)

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

>> Announcer: Live from Las Vegas, it's theCUBE, covering Interconnect 2017. Brought to you by IBM. >> Hey, welcome back everyone. We're live here in Las Vegas at the Mandalay Bay for IBM InterConnect 2017 exclusive Cube coverage. I'm John Furrier, my co-host Dave Vellante, our next guest Dr. Angel Diaz who is the vice president of developer technology. Also you know him from the open source world. Great to see you again. >> Nice to see you. Thanks for spending time with us. >> Thank you. >> Boy, Blockchain, open source, booming, cloud-native, booming, hybrid cloud, brute force but rolling strong. Enterprise strong, if you will, as your CEO Ginni Rometty started talking about yesterday. Give us the update on what's going on with the technology and developers because this is something that you guys, you personally, have been spending a lot of time with. Developer traction, what's the update? >> Well you know if you look at history there's been this democratization of technology. Right, everything from object oriented programming to the internet where we realize if we created open communities you can build more skill, more value, create more innovation. And each one of these layers you create abstractions. You reduce the concept count of what developers need to know to get work done and it's all about getting work done faster. So, you know, we've been systematically around cloud, data, and AI, working really hard to make sure that you have open source communities to support those. Whether it's in things like compute, storage, and network, platform as a service like say Cloud Foundry, what we're doing around the open container initiatives and the Cloud Native Computing Foundation to all the things you see in the data space and everywhere else. So it's real exciting and it's real important for developers. >> So two hot trends that we're tracking obviously, one's pretty obvious. That's machine learning in cloud. Really hand and glove together. You see machine learning really powering the AI, hitting IOT all the way up to apps and wearables and what not, autonomous vehicles. Goes on and on. The other one is Kubernetes, and Kubernetes, the rise of Kubernetes has really brought the containers to a whole nother level around multi-cloud. People might not know it, but you are involved in the CNCF formation, which is Kubernetes movement, which was KubeCon, then it became part of the Linux Foundation. So, IBM has had their hand in these two trends pretty heavily. >> Angel: Oh yeah, absolutely. >> Give the perspective, because the Kubernetes one, in particular, we'll come back to the machine learning, but Kubernetes is powering a whole nother abstraction layer around helping containers go to the next level with microservices, where the develop equation has changed. It's not just the person writing code anymore, a person writing code throws off an application that has it's own life in relationship to other services in the community, which also has analytics tied to it. So, you're seeing a changing dynamic on this potential with Kubernetes. How important is Kubernetes, and what is the real impact? >> No, it is important. And what there actually is, there's a couple of, I think, application or architecture trends that are fundamentally changing how we build applications. So one of them I'll call, let's call it Code First. This is where you don't even think about the Kubernetes layer. All you do is you want to write your code and you want to deploy your code, and you want it to run. That's kind of the platform. Something like Cloud Foundry addresses the Code First approach. Then there's the whole event-drive architecture world. Serverless, right? Where it has a particular use case, event-driven, standing, stuff up and down, dealing with many types of inputs, running rules. Then you have, let's say the more transactional type applications. Microservices, right? These three thing, when combined allows you to kind of break the shackles of the monolith of old application architectures, and build things the way that best suit your application model, and then come together in much more coherent way. Specifically in Kubernetes, and that whole container stuff. You think think about it, initially, when, containers have been around a long time, as we all know, and Docker did a great job in making container accessible and easy, right? And we worked really closely with them to create some multisource activities around the base container definitions, the open container initiative in the Linux Foundation. But of course, that wasn't enough. We need to then start to build the management and the orchestration around that. So we teamed up with others and started to kind of build this Kubernetes-based community. You know, Docker just recently brought ContainerD into the CNCF, as well, as another layer. They are within the equation. But by building this, it's almost just Russian doll of capability, right, you know, you're able to go from one paradigm, whether it's a serverless paradigm running containers, or having your microservices become use in serverless or having Code First kick off something, you can have these things work well together. And I think that's the most exciting part of what we're doing at Kubernetes, what we're doing in serverless, and what we're doing, say, in this Code First world. >> So, development's always been kind of an art form. How is that art form evolving and changing as these trends that you're describing-- >> Oh, that's a great, I love that. 'Cause I always think of ourselves as computer science artists. You and I haven't spoken about that. That's awesome. Yeah, because, you know, it is an art form, right? Your screen is your canvas, right, and colors are the services that you can bring in to build, and the API calls, right? And what's great is that your canvas never ends, because you have, say, a cloud infrastructure, which is infinitely scalable or something, right? So, yeah. But the definition of the developer is changing because we're kind of in this next phase of lowering concept count. Remember I told you this lowering of concept count. You know, I love those O'Reilly books. The little cute animals. You know, as a developer today, you don't have to buy as many of those books, because a lot of it is done in the API calls that you've used. You don't write sorting algorithms anymore. Guess what, you don't need to do speech to text algorithms. You don't need to do some analysis algorithms. So the developer is becoming a cognitive developer and a data science developer, in addition to a application developer. And that is the future. And it's really important that folks skill up. Because the demand has increased dramatically in those areas, and the need has increased as well. So it's very exciting. >> So the thing about that, that point about cognitive developer, is that in the API calls, and the reason why we don't buy all those books is, the codes out there are already in open source and machine learning is a great example, if you look at what machine learning is doing. 'Cause now you have machine learning. It used to be an art and a science. You had to be a great computer scientist and understand algorithms, and almost have that artistic view. But now, as more and more machine learning comes out, you can still write custom machine learning, but still build on libraries that are already out there. >> Exactly. So what does that do? That reduces the time it takes to get something done. And it increases the quality of what you're building, right? Because, you know, this subroutine or this library has been used by thousands and thousands of other people, it's probably going to work pretty well for your use case, right? But I can stress the importance of this moment you brought up. The cognitive data application developer coming together. You know, when the Web happened, the development market blew up in orders of magnitude. Because everybody's is sort of learning HTML, CSS, Javascript, you know, J2E, whatever. All the things they needed to build, you know, Web Uize and transactional applications. Two phase commit apps in the back, right? Here we are again, and it's starting to explode with the microservices, et cetera, all the stuff you mentioned, but when you add cognitive and data to the equation, it's just going to be a bigger explosion than the Web days. >> So we were talking with some of the guys from IBM's GBS, the Global Business Services, and the GTS, Global Technology Services, and interesting things coming out. So if you take what you're saying forward, and you open innovation model, you got business model stacks and technology stacks. So process, stacks, you know, business process, and then technology, and they now have to go hand-in-hand. So if you take what you're saying about, you know, open source, open all of this innovation, and add say, Blockchain to it, you now have another developer type. So the cognitive piece is also contributing to what looks like to be a home run with Blockchain going open source, with the ledger. So now you have the process and the stacks coming together. So now, it's almost the Holy Grail. It used to be this, "Hey, those business processor guys, they did stuff, and then the guys coded it out, built stacks. Now they're interdependent a bit. >> Yeah. Well I mean, what's interesting to me about Blockchain, I always think of, at this point about business processes, you know, business processes have always been hard to change, right? You know, once you have partners in your ecosystem, it's hard to change. Things like APIs and all the technology allows it to be much quicker now. But with Blockchain, you don't need a human involved in the decision of who's in your partner network as long as they're trusted, right? I remember when Jerry Cuomo and Chris Ferris, in my team, he's the chairman of the Blockchain, of the hyperledger group, we're talking initially when we kind of brought it to the Linux Foundation. We were talking a lot about transactions, because you know, that was one of the initial use cases. But we always kind of new that there's a lot of other use cases for this, right, in addition to that. I mean, you know, the government of China is using Blockchain to deal with carbon emissions. And they have, essentially, an economy where folks can trade, essentially, carbon units to make sure that as an industry segment, they don't go over, as an example. So you can have people coming in and out of your business process in a much more fluid way. What fascinates me about Blockchain, and it's a great point, is it takes the whole ecosystem to another level because now that they've made Blockchain successful, ecosystem component's huge. That's a community model, that's just like open source. So now you've got the confluence of open source software, now with people in writing just software, and now microservices that interact with other microservices. Not agile within a company, agile within other developers. >> Angel: Right. >> So you have a data piece that ties that together, but you also have the process and potential business model disruption, a Blockchain. So those two things are interesting to me. But it's a community role. In your expert opinion on the community piece, how do you think the community will evolve to this new dynamic? Do you think it's going to take the same straight line growth of open source, do you think there's going to be a different twist to it? You mentioned this new persona is already developing with cognitive. How do you see that happening? >> Yes, I do. There's two, let's say three points. The first on circling the community, what we've been trying to do, architecturally, is build an open innovation platform. So all these elements that make up cloud, data, AI, are open so that people can innovate, skills can grow, anything, grow faster. So the communities are actually working together. So you see lots of intralocks and subcommittees and subgroups within teams, right? Just say this kind of nesting of technology. So I think that's one megatrend that will continue-- >> Integrated communities, basically. >> Integrated communities. They do their own thing. >> Yeah. >> But to your point earlier, they don't reinvent the wheel. If I'm in Cloud Foundry and I need a container model, why am I going to create my own? I'll just use the open compute initiative container model, you know what I'm saying? >> Dave: And the integration point is that collaboration-- >> Is that collaboration, right. And so we've started to see this a lot, and I think that's the next megatrend. The second is, we just look at developers. In all this conversation, we've been talking about the what? All the technology. But the most important thing, even more so than all of this stuff, is the how. How do I actually use the technology? What is the development methodology of how I add scale, build these applications? People call that DevOp, you know, that whole area. We at IBM announced about a year and a half ago, at Gene Kim's summit, he does DevOps, the garage method, and we open sourced it, which is a methodology of how you apply Agile and all the stuff we've learned in open source, to actually using this technology in a productive way at scale. Often times people talk about working in theses little squads and so forth, but once you hire, say you've got 10 people in San Francisco, and you're going to hire one in San Ramon, that person might as well be on Mars. Because if you're not on the team there, you're not in the decision process. Well, that's not reality. Open source is not that way, the world doesn't behave that way. So this is the methodology that we talked about. The how is really important. And then the third thing, is, if you can help developers, interlock communities, teach them about the how to do this effectively, then they want samples to fork and go. Technology journeys, physical code. So what you're start to see a lot of us in open source, and even IBM, is provide starters that show people how to use the technology, add the methodology, and then help them on their journey to get value. >> So at the base level, there's a whole new set of skills that are emerging. You mentioned the O'Reilly books before, it was sort of a sequential learning process, and it seems very nonlinear now, so what do you recommend for people, how do they go about capturing knowledge, where do they start? >> I think there's probably two or three places. The first one is directly in the open source communities. You go to any open source community and there's a plethora of information, but more so, if you hang out in the right places, you know, IRC channels or wherever, people are more than willing to help you. So you can get education for free if you participate and contribute and become a good member of a community. And, in fact, from a career perspective today, that's what developers want. They want that feeling of being part of something. They want the merit badge that you get for being a core committer, the pride that comes with that. And frankly, the marketability of yourself as a developer, so that's probably the first place. The second is, look, at IBM, we spend a huge amount of time trying to help developers be productive, especially in open source, as we started this conversation. So we have a place, developer.ibm.com. You go there and you can get links to all the relevant open source communities in this open innovation platform that I've talked about. You can see the methodologies that I spoke about that is open. And then you could also get these starter code journeys that I spoke about, to help you get started. So that's one place-- >> That's coming out in April, right? >> That's right. >> The journeys. >> Yeah, but you can go now and start looking at that, at developer.ibm.com, and not all of it is IBM content. This is not IBM propaganda here, right? It is-- >> John: Real world examples. >> Real world examples, it's real open source communities that either we've helped, we've shepherded along. And it is a great place, at least, to get your head around the space and then you can subset it, right? >> Yeah. So tell us about, at the last couple of minutes we have, what IBM's doing right now from a technology, and for developers, what are you guys doing to help developers today, give the message from what IBM's doing. What are you guys doing? What's your North Star? What's the vision and some of the things you're doing in the marketplace people can get involved in? You mentioned the garage as one. I'm sure there's others. >> Yeah, I mean look, we are m6anically focused on helping developers get value, get stuff done. That's what they want to do, that's what our clients want to do, and that's what turns us on. You build your art, you talk, you're going back to art, you build your drawing, you want to look at it. You want it to be beautiful. You want others to admire it, right? So if we could help you do that, you'll be better for it, and we will be better for it. >> As long as they don't eat their ear, then they're going to be fine. >> It's subjective, but give value of what they do. So how do they give value? They give value by open technologies and how we've built, essentially, cloud, data, AI, right? So art, arts technology adds value. We get value out of the methodology. We help them do this, it's around DevOps, tooling around it, and then these starters, these on-ramps, right, to getting started. >> I got to ask you my final question, a more personal one, and Dave and I talk about this all the time off camera, being an older guy, computer science guy, you're seeing stuff now that was once a major barrier, whether it's getting access to massive compute, machine learning, libraries, the composability of the building blocks that are out there, to create art, if you will, it's phenomenal. To me, it's just like the most amazing time to be be a computer scientist, or in tech, in general, building stuff. So I'm going to ask you, what are you jazzed up about? Looking back, in today's world, the young guns that are coming onto the scene not knowing that we walked barefoot in the snow to school, back in the old days. This is like, it's a pretty awesome environment right now. Give us personal color on your take on that, the change and the opportunity. >> Yeah, so first of all, when you mentioned older guys, you were referring to yourselves, right? Because this is my first year at IBM. I just graduated, there's nothing old here, guys. >> John: You could still go to, come on (laughs). >> What does that mean? Look you know, there's two things I'm going to say. Two sides of the equation. First of all, the fundamentals of computer science never go away. I still teach, undergrad seminars and so forth, and you have to know the fundamentals of computer science. That does not go away because you can write bad code. No matter what you're doing or how many abstractions you have, there are fundamental principles you need to understand. And that guides you in building better art, okay? Now putting that aside, there is less that you need to know all the time, to get your job done. And what excites me the most, so back when we worked on the Web in the early 90s, and the markup languages, right, and I see some in the audience there, Arno, hey, Arno, who helped author some of the original Web standards with me, and he was with the W3C. The use cases for math, for the Web, was to disseminate physics, that's why Tim did it, right? The use case for XML. I was co-chair of the mathematical markup language. That was a use case for XML. We had no idea that we would be using these same protocols, to power all the apps on your phone. I could not imagine that, okay? If I would have, trust me, I would have done something. We didn't know. So what excites me the most is not being able to imagine what people will be able to create. Because we are so much more advanced than we were there, in terms of levels of abstraction. That's what's, that's the exciting part. >> All right. Dr. Angel Diaz, great to have you on theCUBE. Great inspiration. Great time to be a developer. Great time to be building stuff. IOT, we didn't even get to IOT, I mean, the prospects of what's happening in industrialization, I mean, just pretty amazing. Augmented intelligence, artificial intelligence, machine learning, really the perfect storm for innovation. Obviously, all in the open. >> Angel: Yes. Awesome stuff. Thanks for coming on the theCUBE. Really appreciate it. >> Thank you guys, appreciate it. >> IBM, making it happen with developers. Always have been. Big open source proponents. And now they got the tools, they got the garages for building. I'm John Furrier, stay with us, there's some great interviews. Be right back with more after this short break. (tech music)