Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

HP talks cloud delivery options, the importance of OpenStack, how it competes on price

John Dix, Brandon Butler | Nov. 26, 2014
An in-depth conversation with Bill Hilf, Senior Vice President of Product and Service Management for HP Cloud, about where Helion fits in, cloud consumption models and coming change.

Above that we have the Helion Development Platform, which is a PaaS layer, but think of it as using Cloud Foundry as the host, or the run time, for applications. So it supports all these different languages and you can publish your Java app or node.js app or Python app or Ruby app into that full application lifecycle environment.

Then alongside of that we have a set of application services. So, for example, if someone wants to use database-as-a-service, we have an easy-to-use DB service so a developer can quickly add a database to their app. Behind the scenes we do a binding between that database-as-a-service at the PaaS layer, all the way down into OpenStack's database-as-a-service offering called Trove. That way we can then offer that database-as-a-service at the development platform layer in a way that's automatically highly available, and automatically has disaster recovery built in because we're leveraging the Trove system underneath and providing that resilience to the database behind the scenes.

We'll do a lot more things like that where we basically illuminate the capabilities inside OpenStack at a higher level for developers to take advantage of. For example, there's this concept called affinity scheduling inside OpenStack where you can say, assign my VM to a high memory machine or assign these VMs to that data center because that is the only one that's HIPAA compliant. As that grows in OpenStack, we want to light up that type of capability higher in the platform so it becomes really easy for the developer.

Also, what we use behind the scenes in our Helion development platform is Docker. Every app you build on our Helion development platform instantiates as a Docker container so you can take those Docker containers and assign them wherever you want. We think this Docker + OpenStack combination is going to very powerful.

So, back to your question, they are two different architectural layers. One is targeted at developers, and one is targeted at IT ops. They can be used independently but we're doing a lot of work to make them better together.

When it comes to use cases for cloud, VMware is positioning its vCloud Air as a natural landing spot for ESX workloads, and Microsoft Azure is a natural spot for Hyper-V and System Center, so where do you see HP being the natural answer?

Because of my Microsoft background I can ask a company what versions of Windows Server and System Center they're using and I'll know right away if they're a Microsoft loyalist or not, and for those customers, the Azure story is compelling. And AWS is definitely the default if you're a startup and looking for the fastest onramp to getting some compute and storage resources that can scale wide. Where we win are with enterprises that have stepped all the way through the virtualization steps in the past three to four years, companies that have more than 50% of their environment virtualized. Now they're getting a lot of pressure on being able to go faster.


Previous Page  1  2  3  4  5  6  7  8  Next Page 

Sign up for CIO Asia eNewsletters.