>> Announcer: Live from Copenhagen, Denmark, it's theCUBE! Covering KubeCon + CloudNativeCon Europe 2018. Brought to you by the Cloud Native Computing Foundation, and it's ecosystem partners. >> Hello there and welcome back to theCUBE's exclusive coverage of KubeCon 2018, the Cloud Native Compute Foundation. CNCF, I'm John Furrier with theCUBE. My cohost 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 Syed, who is the Head of HP Developer Experience. CUBE alumni. Welcome back. Good to see you. >> Thanks for having us. >> Thanks for comin' on. >> Thank you. >> First of all, new logo. I love that, I want to get into it. HPE Developer program. We've had many conversations in the past about 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? >> In December we launched this new program called the HP Community Developer Program. And that's really focused on reaching out to the developers that are out there. Whether these are DevOps developers, Cloud Native application developers, ITOps 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 HP's doing in the open source program and other areas. Do you want to add something, Paul? >> Yeah, I think part of it is the recognition that HPE is a software company. After all of the separations, the divestiture with HPI and that micro-focus. We're left with really still a lot of developer power. It's the idea that as we work with developers internally and externally, we need to formalize that developer program. Both inside of open source and the general developer. Go through our API's 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. To give you guys some props, we've interviewed in the past four or five years, you guys were doing, talking micro services early on. >> Syed: 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 defacto standard for interoperability around multi-cloud. This is the perfect storm for a company as big as HP with all the customers. So what is... I mean you guys must be sitting there going, perfect timing! What does it mean for you guys, Kubernetes? This is going to give you certainly a tail wind 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 'em together for an enterprise class workload. And given our history and expertise there I think you're right. It's a great opportunity to make sure that it works for the enterprise developer, for general developers. And how everything comes together within it, within a corporate world of development. >> Are you guys doubling down? >> Syed: Absolutely. >> What's the story internally? Is it got the charter from the top? >> That's right, yeah, we're definitely doubling down. As you mentioned, we started early on with micro services, with our partnership at Docker. We have a great relationship with Mesosphere. And we're full on with Kubernetes. You know we have a product that we're actually demoing here on the show floor, called HPE OneSphere. 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. Deployment, management, all of those things. We are full on. We also have open source projects in the Kubernetes landscape. It's called Project Dory. That enables persistent storage. It's actually contributed by our Nimble big business unit. We're very focused on enabling our developers. Things that enable them is things like, how can I automatically deploy applications? And so on. Using Kubernetes cluster or Kubernetes environment. Working with Paul and others that's exactly what we're focused on. >> What are some of the user cases that you guys are seeing? As you mentioned some of those deployments. Is it really existing integration within HP Solutions? Like OneSphere? And OneSphere's obviously going to be a nice paint a glass and look at the platform of what the cloud offers. Is it Edge? Is it IoT? I mean what are some of the user cases? >> I think it's all of the above. I think what we're seeing is legacy enterprises having all of these legacy applications that they need to migrate 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, I think that's the power of going back to your original question about HPE. Is we've seen all of that in the enterprise. And can we put those proprietary componentry into the products? Like a OneSphere 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, greenfield applications. All within this again Lego block type environment, within Kubernetes and these other open source platforms. >> I mean you guys also again on the composable infrastructure kind of story. It's kind of here, right? >> That's right. 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's now like 40 some partners. But that's growing. 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. With one view, with our composable API's. Working with components like Docker, and Mesosphere, and Redfish, and other open source products and services, on top of that with OneSphere as the multi-cloud/hybrid cloud management platform, again using the power of our API's. And then integrating north bound with these hybrid multi-cloud management environments, as well as south bound with infrastructure management. Now you have the overall story. We're really exploiting the power of API's. And enabling our developers internally, as well as developers outside of HPE, To come together and 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. >> 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 that and what are they using? >> Yeah so I'll give you a quick example. We launched the 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 and actually just people comin' in and hanging out on the portal. I think we are up to about 30,000 unique, unique views of our page. Most people are spending three to four minutes, which is a lot in today's terms. Someone who is going there, reading our content. And then on top of that actually consumer-ship of our projects. Grommet for example is one of our open source projects that HP 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 Grommet as a UX. Most of our SDCG is off our defined applications are now using Grommet. So OneSphere, One View. That's our de facto standard. But it's open source, anyone can use it. >> Are you finding, HP is traditionally been kind of a company that does a lot of things internally. Are you guys opening up for the first time? With allowing your developers to build things that will be put into open source? Can you talk a little bit about that? >> The power of HP 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 this question comes from from an internal perspective. Even ten, 15 years ago with Martin Fink, at the helm of the open source group. And then ultimately as the CTO. And things have shifted through the separations. How do you leverage that power of openness, collaboration, that's in their DNA? And really empowering them to share. How do we take concepts like inner sourcing, which is the open sourcing of activities inside a company, And really start 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. >> Cooney: That is great to hear. >> And enabling that for other enterprises as well. Which is really where a lot of our customers come to us and say, hey you're an 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 everyone knows you guys have a very active and open source community. And have been on this. This is not a new thing, revelation within HP. But Intel has the same challenge. They're tryna move away from that Intel Inside. You guys are known to a lot of people as a hardware company. You got HP.com is now the printer and the peripheral side. But it's a cloud game. You're still selling servers but people are still buying servers. The cloud providers need servers. They need it. But the software is the key, the software defined infrastructure is now that glue layer. Service meshes are hot. You're seeing SDO's got massive traction. Everything's pointing to this new level of services at scale. >> That's right. >> 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? >> If you look at the overall strategy. 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. You have all those componentries working together seamlessly and automated. And then we have the services groups to make it happen. With the Pointnext, and the acquisitions of cloud technology partners in the new areas. We have a wide variety of a portfolio of 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 talk about the Edge. And so with our acquisition Aruba, which it seems like a long time ago. It's just a few years. They've been an integral part of taking that from a data center all the way to the edge and in between. 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, depth of bench, in terms of... >> And OneSphere's the key product that, for you guys, that connects all this. Is that kind of where the momentum is? >> Holland: It's one of them. >> One of them, okay. >> And then if you look at some of the acquisitions we have made. CTP, for example, or Cloud Cruiser, for example. These are all helping us build our portfolio of rich services that enable customers to go from a pure on-prem, pure hardware focus 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 of micro plus macro services kind of migration capabilities. >> What are you guys offering developers? Not that I'm going to ask you for the pitch. Cause everyone, the developers are getting a lot of pitches, if you will. 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. Right at the point of engagement for the business logic, and the business models of a lot of these applications. What do you guys bring to the table for the developers? 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. We really start with internal, right? We are aligning our internal developers to really consume our own champagne. Drink your own champagne. So what does that mean? Can you use OneSphere to develop OneSphere? Absolutely. Our mentality is, our OneSphere developers, in fact a couple of our distinguished technologists are here. So more customer focused. Do your development on your own products, on your own products. Does that make sense? >> Yeah. >> So that's number one, right? 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 we are really enabling our developers to do. Is really think outside in, versus inside out. Gone are the days of, we will 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 API's, from layer 1 infrastructure all the way up to layer 7. Or Layer 5 and above. And say, "Alright how do we enable these guys to build value add that really solves their problem?" Whether it's DevOps problems. CI/CD? Whether it deploying applications, managing, monitoring applications. It's all through the power of API. If you can automate it, orchestrate it and manage it. Then we have really solved your problems. 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 had it more up to stack. Certainly the application level is a key point. What about the channel opportunity? Cause I'm seeing, and I've been talking about this on theCUBE lately, is developers are the new sales channel, because in the old days VAR's, and ISV's and channel partners would bring solutions. And you guys had a great channel, have a great channel that brings solutions to customers. Now these customers are having programming and developing done from the partners. You guys have to create that. Are you guys looking at that as a significant opportunity, with this program? >> In today's world you have to think about things in a different way. With the advent of DevOps. With the developers no longer in their cubes, not touching production, they're releasing the production daily. Or multiple times per day. And so we're lookin', or have looked with that with, how do the developer work. And get that all the way to production. At the same time, what's the skill sets to work with in the open? Are you talking about the channel? The open source community is a great channel. Not only for ideas and conversations, but also to meet people. Not only are we there. >> Furrier: 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 multiple times per year. >> When you guys get this right, I think the gains will be huge. >> Well I'll give you an example. One of the largest web 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. To the point where we are working on doing hackathons. So our developers, their developers, in the same conference room, solving joint problems together. >> Cooney: So co-development. >> Co-developing, exactly. We call it a hackathon. But yeah, co-developing, 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 is 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. I'd love to get a shirt when you get a chance. >> Absolutely, yeah. >> Congratulations, great to see you. Thanks for comin' 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.