I can understand the interest in the existence of Eucalyptus itself (it's a more or less interface compatible implementation of a bunch of Amazon's heavily used 'cloud' services that you can run stuff on in house or at a non-Amazon 3rd party). Amazon's pricing is crazy aggressive; but sometimes you need to do things in house, want to do things in house, or want to go mixed-strategy(in-house/Amazon for overflow, spread across more than one 3rd party provider, etc, etc.) and in general it's not a good feeling to have a stack of important stuff dependent on a single vendor.
What I find much harder to understand is what HP gains from this, or what I, the hypothetical customer, as supposed to be willing to pay HP to put its name on here.
Is this just more HP flailing, or is there an angle I'm missing? Are there lots of potential customers who won't touch Amazon (perhaps because they have to keep stuff internal); but won't touch Eucalyptus without some giant company selling them a support agreement? If so, since Amazon is off the table, why would they care about Amazon API compatibility? Who is the target here, and why aren't they either DIYing it, paying Amazon's incredibly aggressive prices for the real thing, or using an architecturally different cloud/VM arrangement?