 Live from Copenhagen, Denmark, it's theCUBE, covering KubeCon and CloudNativeCon Europe 2018, brought to you by the CloudNative Computing Foundation and its ecosystem partners. Hello everyone, welcome back to theCUBE's exclusive coverage of KubeCon 2018, the CloudNative Compute Foundation, CNCF. I'm John Furrier with theCUBE. My co-host Lauren Cooney is here with me this week. Our next two guests are from HPE developer program, Paul Holland, director of open source program office and Said Said, who's the head of HPE developer experience. Kube alumni, welcome back, good to see you. Thanks for having us. Thanks for coming on. Thank you. So, first of all, new logo, love that, I want to get into it. HPE developer program, we've had many conversations in the past, the relationship with Docker, the work you guys are doing inside the enterprises with cloud, multi-cloud and hybrid cloud. Why are you guys here? What's the story? What's the update from HPE? So, in December we launched this new program called the HPE developer community program and that's really focused on reaching out to the developers that are out there, whether these are DevOps developers, CloudNative application developers, IT DevOps developers who are looking to do integration with HPE infrastructure as well as our software-defined platforms. It's basically evangelizing all of the good work that HPE is doing in the open source program and other areas. Do you want to add something? Yeah, I think part of it is people recognize the recognition that HPE is a software company. Is after all of the separations, the divestiture with HPE, then micro-focus and we're left with really a lot of still developer power. And so it's the idea that as we work with developers internal and externally, we need to formalize that developer program both inside of open source and the general developer through our APIs and some of that coordination to really make the developer work. I mean, we're talking software-defined everything now. You guys have been part of that and I give you guys some props. We've interviewed over the past four or five years, you guys were talking micro-services early on. That's right. Again, the enterprise has software-defined systems. You guys are a big part of that. So I got to ask you, the perfect storm is here. I mean, Kubernetes, which is on the scene is now, at least in my opinion, the de facto standard for interoperability around multi-cloud. This is the perfect storm for a company as big as HPE with all the customers. So what is, I mean, you guys must be like sitting there going, perfect timing. What does it mean for you guys, Kubernetes? This is going to give you certainly a tailwind for deployments and customer value creation. What's it mean internally for HPE? Well, I think Kubernetes is at the heart, as you mentioned, of the open source ecosystem. It's about all of those Lego blocks now finally coming together with micro-services and being able to put them together for an enterprise-class workload. And given our history and our expertise there, I think you're right, that it's a great opportunity to make sure that it works for the enterprise developer, for general developers, and how everything comes together within a corporate world of development. You guys doubling down, I mean. Absolutely. What's the story internally? Is it got the charter from the top? That's right. Yeah, so we're definitely doubling down. I mean, as you mentioned, we started early on with microservices, with our partnership with Docker. We have a great relationship with Lisa Sphere. And we're full on with Kubernetes. We have a product that we're actually demoing here on the show called HPE One Sphere. We launched the product in December of last year. And one of the things it actually does, it enables Kubernetes cluster management on-prem and off-prem, for example, in AWS. So deployment, management, all of those things. So we are full on. We also have open source projects in the Kubernetes landscape. It's called Project Dory. That enables persistent storage. And it's actually contributed by our Nimble business unit. So yeah, we're very focused on enabling our developers. Things that enables them is things like, how can I automatically deploy applications and so on using Kubernetes cluster, Kubernetes environment. So working with Paul and others, that's exactly what we're focused on. What are some of the use cases that you guys are seeing, as you mentioned, some of those deployments. Is it really kind of existing integration within HPE? So it's like One Sphere and One Sphere is obviously going to be a nice pane of glass to look at the platform of what the cloud offers. Is it Edge? Is it IoT? I mean, what are some of the use cases? I think it's all of the above. I think what we're seeing is legacy enterprises having all these legacy applications that they need to migrate to this new world. At the same time, they're struggling with how do then I make hybrid? How do I then go to the Edge? And so across the board, and I think that's the power going back to the original question around HPE is we've seen all of that in the enterprise. And can we put those proprietary componentry, the products, like One Sphere, on top of open source components. The reason we're here at Kubernetes as an example is to really highlight to developers that if you really want to bring things together, we can help you do that. Whether it be legacy applications, new application, green field applications, all within this, again, Lego block type environment within Kubernetes and these other open source. You guys were also, again, on the composable infrastructure kind of story. It's kind of here, right? That's right, yeah. So again, we started down this journey three, four years ago with Docker and several others. We built this unified ecosystem, a composable ecosystem, and in the ecosystem, I think there are now like 40 some partners, but that's growing. So if you look at it from a layered cake point of view, the infrastructure is here, that problem has been solved for a long time. You have infrastructure management, so with one view, with our composable APIs, working with components like Docker and Mesosphere and Redfish and other open source products and services. On top of that, with One Sphere as the multi-cloud, hybrid cloud management platform, again, using the power of our APIs and then integrating Northbound with these hybrid cloud, multi-cloud management environments as well as Southbound with infrastructure management. Now you have the overall story. So we're really exploiting the power of APIs and enabling our developers internally, as well as developers outside of HPE to kind of really come together and then start to think about this new idea. Is there a solution for that? Absolutely, there's an app for it. And then the way you build that app is build that API integration. So you talked about an app store that you guys are working on. It has about 40 different partners in it. What about users of the solutions that are in there? Are you seeing an uptick in that? And what are you seeing in terms of them? What are they using? Yeah, so I'll give you a quick example. So we launched a developer community program in December. We launched the portal in December and in the past two and a half months, we have seen a significant uptick in actually just people coming in and hanging out on the portal. I think we are up to about 30,000 unique views of our page and most people are spending three to four minutes, which is a lot in today's terms. Someone who's going there, reading our content. And then on top of that, actually, you know, a consumer ship off our projects. So Gromit, for example, is one of our open source projects that HPE funds. It's a UX front end. I think it has more than 10,000 people that are following it and using it. Companies like Netflix, for example, use Gromit as a UX. Most of our SDC software defined applications are now using Gromit. So one sphere, one view, that's our de facto standard, but it's open source. Anyone can use it. And are you finding, you know, HPE has traditionally been kind of a company that does a lot of things internally. Are you guys opening up for the first time, really? I would almost say, with allowing your developers to build things that will be put into open source or you talk a little bit about that. Yeah, I think the power of HPE is we've had a rich collaboration history for a long, long time. And I think you alluded to it before, from an enterprise perspective, how can we make that easy, not only for our own internal developers? And maybe this is where the question comes from from an internal perspective. But even 10, 15 years ago with Martin Fink at the home of the open source group and then ultimately as the CTO and things have shifted through the separations. But taking, how do you leverage that power of openness, collaboration that's in our DNA and really empowering them to share? And so how do we take concepts like inner sourcing which is the open sourcing of activities inside a company? And really, you start to develop those habits and capabilities. Whether or not it's external is just a flip of the switch but developers know how to contribute. They're also learning best of breed skills and developing their own career over time. That is great to hear. And then enabling that for other enterprises as well which is where a lot of our customers come to us and say, hey, you're at enterprise with lots and lots of developers. How do I get that same power with mine? And you kind of walk them through the journey. It's interesting. I'd love to get your thoughts on this. I think you guys are doing, first of all, I love the new logo. I think it's really important that everyone knows that you guys have a very active and open source community. And it'd been on this. It's not like a new thing, a revelation within HP. But Intel is the same challenge. They're trying to move away from that Intel inside. You guys are known to a lot of people as a hardware company and then you got HP.com is now the printer and the peripheral side. But it's a cloud game. So yeah, you're still selling servers but I mean, people are still buying servers. The cloud providers need servers. So they need it. But the software is the key. The software defined infrastructure is that glue layer. Service meshes are hot. You're seeing Istio's got massive traction. Everything's pointing to this new level of services at scale. I want to get your thoughts on the HP story there. Can you take a minute to explain what you guys are doing with that vision? Because cloud native isn't just about the cloud. There's a lot of on-prem activity that's moving to a cloud operating model. So it's not a full public cloud. What's your story? I think from a, if you look at the overall strategy, it's around, we make hybrid IT simple, recognizing that it's all those different flavors. We have to enable the software capabilities because the world is software enabled. So you have all of those componentries working together seamlessly and automated. And then we have the services groups to make it happen. So with the point next and the acquisitions of cloud technology partners in the new areas, we have a wide variety of portfolio services that are now enabled and experts to actually go help customers do it. And so we have the capability legacy. We also have the capability of the new generation of IT and everywhere in between. And then you talked about the edge. And so with our acquisition of Aruba, which seems like a long time ago, it's just a few years. They've been an integral part of taking that from the data center all the way to the edge and in between. So I think we've got those multiple layers of hybrid IT. We have the software enabled activities, which definitely includes open source because you can't be software enabled without software and open source. And then from a service perspective, the wealth of depth of bench in terms of the- And one sphere is the key product that, for you guys that connects all this, is that kind of where the moment that's- It's one of them. One of them, okay. And then if you look at some of the acquisitions we've made, CTP for example, Cloud Cruiser for example, these are all helping us build our portfolio of rich services, then enable customers to go from a pure on-prem, pure hardware-focused company to now a new age cloud native, or hybrid cloud sort of company where we have the experience. Now we have the experience with all of these different acquisitions like CTP to enable them to have a full hybrid cloud, micro plus macro services, kind of migration capabilities. What are you guys offering developers? Not that you're going to ask you for the pitch because everyone, the developers are now getting a lot of pitches, if you will, and people say I got to own the developer. They don't want to be owned, they want to be collaborative, but they're closer to the front lines than ever these developers. And they're really looking at business problems. It's not just, here's the specs, go code it. They're on the front lines at the right at the point of engagement for the business logic and the business models a lot of these applications. So what do you guys bring to the table for the developer? Is it marketplace? Is it distribution? Is it opportunity? What is the value proposition that you guys are talking to developers about specifically? I think it's all three. So we really start with internal, right? So we are aligning our internal developers to really consume our own champagne, you know what? So you drink your own champagne, so what does that mean? Well, can you use OneSphere to develop OneSphere? Absolutely. So our mentality is our OneSphere developers, and in fact, a couple of our Distinguished Technologies are here, so more customer focus. So do your development on your own products, on your own products, does that make sense? So that's number one, right? So if they go through the pains of developing on our own products, they will know exactly which areas to focus on. And so that's one thing that we are really, you know, enabling our developers to do is really think outside in versus inside out, right? You know, go on other days, we'll build it, and they will come. No, they won't. You have to really give them what they are going to consume. So from a strategy perspective, we're really exposing our developers to the outside world. Hey, go out there, talk to them, learn what they're looking for, right? So that's number one. Number two, with the developer community program and the developer portal and the open source program, now that we're collaborating across HPE at the top end and the bottom end, we're not really able to think about how we use the power of our APIs from layer one, your infrastructure all the way up to layer seven, or layer five and above and say, all right, how do we enable these guys to build value at that really solves their problem, whether it's DevOps problems, you know, CICD, whether it's deploying applications, managing, monitoring applications, it's all through the Power API. If you can automate it, orchestrate it and manage it, then we have really solved your problem. So this is why we're not only going after and enabling the developers by giving them what they need, we're also partnering with key partners in our ecosystem that actually brings the best of breed, and that's what the customers are used to using today. And you guys got to move up the stack, certainly the application level is a key point. What about the channel opportunity? Because I've been talking about this on theCUBE lately as developers are the new sales channel, because in the old days, VARs and ISVs and channel partners would bring solutions and you guys have a great channel that brings solutions to customers. Now these customers are having programming and developing done from the partners. So you guys have to create that. Are you guys looking at that as a significant opportunity with this program? Well I think in today's world, you have to think about things in a different way. And I think with the advent of DevOps and the developers are no longer in their cubes not touching production, they're releasing the production daily or regular or multiple times per day. And so we're looking at and we have looked at that with how does the developer work and get that all the way to production? At the same time, what's the skill sets to work within the open? Now you talk about the channel, the open source community is a great channel not only for ideas and conversations, but also to meet people, because not only are we releasing- Your buyers are there. Yeah, exactly. We're releasing the customers, but customers is part of our community. Vendors are part of our community, partners are part of our community, and together we're building a community of developers that are doing work that ultimately goes to production regular multiple times every week. You guys get this right, the gains will be huge. Well I'll give you an example. One of the largest wealth companies in the world. We're partnering with them, they're a huge customer of ours. Instead of selling to their frontline, we went and started talking to their developers and their developer leaderships and to the point where we actually are working on joint hackathons. So our developers, their developers in the same conference room solving joint problems together. So co-development. Co-development, exactly. We call it a hackathon, but yeah, co-development, absolutely. That's where we're focused. Because today, developers and the line of businesses have more and more and more influence on key technology decisions. That's where the money is. Being genuine and authentic in these communities certainly a great, successful formula. You guys see that. We'll be following your progress. Thanks for coming on theCUBE and sharing the update and congratulations on the new program and the new logo. Love to get a shirt. We'll get a shirt. I will be, yeah. Great, congratulations. Thanks for coming on. Thanks for coming on. We are here at KubeCon 2018 in Europe. This is theCUBE. I'm John Furrier. Thanks for watching. We'll be back with more live coverage after this short break.