HP and the enterprise cloud
HP sees an opportunity to couple HP's pure-play IaaS cloud with private HP clouds that will "integrate very naturally" with each other. In that hybrid approach, HP relies on OpenStack, the open source cloud operating system, to provide the underpinning for HP's public and private cloud offerings. Q: What sort of developers do you feel will be inclined to adopt HP's cloud offerings? HP: We're going after the enterprise developer, where there are a bunch of expectations about which production workloads are going to end up on the public cloud. We happen to think there will be tens of thousands use cases that are ultimately going to be driven by the need for a secure, SLA-driven, enterprise-class quality of service. Our focus is the enterprise developer, but also IT ops. For production workloads enterprises may consider running, they want the scale, they want the advantage of cost efficiencies. They want the security. But most importantly, they want a vendor who understands what they're about, who they've done business with, who understands the need for innovative services yet can balance out SLA, security, and customer service -- and who provides choices in terms of being an open architecture, partnering with other stacks and not locking in customers. If you look at infrastructure clouds, AWS (Amazon Web Services) is obviously at one end of the spectrum, but you also have a bunch of telcos that have tried this, and their notion of cloud is -- well, stand up a bunch of VMs and let's see what happens. I think that's such a 2009 phenomena; we've passed that. What developers and enterprises are looking for, they're saying: Give me a set of services. I want to be able to run workloads in a secure cloud environment. And I want the best tools, the most modern languages and frameworks to build those. We're trying to address the needs of developers and IT ops with a particular emphasis on the kind of enterprise, production-grade workloads are going to be running. Q: Obviously, dev and test has been one of the big uses of the public cloud from the very beginning. But you're talking about dev, test, and deploy for the enterprise, which is something different. From what we've seen, for the enterprise, it's been dev and test in the public cloud, but not deploy in the public cloud. You bring it back in-house and deploy it on your own servers. How are you going to succeed in deploying enterprise apps in your public cloud where others have failed? HP: Let's talk about deploying specifically; then I'll talk about PaaS (platform as a service) as well. In terms of the deploy model, everyone has a sandbox on AWS or is trying, but they very quickly realize that in order to get to production they've got to pull these environments back in. One of two things happens. CIOs will say, well, I'm 70 percent, 80 percent virtualized, so why can't I just do that here? And running a dev/test application in a cloud setting versus running it in-house on a highly virtualized setting, there are different things you have to manage. It becomes a very different experience and technically different for the apps guys or the IT ops guys to manage that. The other thing that happens is people get spoiled by the ease of dev/test, whether on AWS, whether on HP Cloud or any environment, because you get out of the old provisioning and the many weeks of provisioning and all that. But now you can also impact the application and the interaction with the applications. So people get used to the ease of deployment. That's why I think ultimately private clouds and public clouds become sort of one and the same. There's an on-ramp and a secure orchestration model to it. But that's what CIOs want. People say: Oh, virtualization and cloud are really one thing. They're very different, actually. With virtualization, you're managing clusters of VMs and there's a certain management and security model for that. You're essentially building on your hypervisor,...
Please join StudyMode to read the full document