The problem is that 10.04 is literally hardcoded.  Before the above patch,
there's no way to change that without knowing IDs.
On Aug 15, 2012 5:57 PM, "Andrew Bayer" <[email protected]> wrote:

> ...and you don't actually have to specify the OS stuff at all. Just
> whirr.hardware-min-ram=1024 or whatever, and it'll automatically pick an
> Ubuntu 10.04 image for you.
>
> A.
>
> On Wed, Aug 15, 2012 at 5:54 PM, Andrew Bayer <[email protected]
> >wrote:
>
> > You'll actually have to do some manual tweaks due to HP Cloud public IPs
> > not having reverse-resolvable IP addresses - you'll need to manually go
> > onto each of your hosts and change any references to hostnames they put
> in
> > there to the IP instead.
> >
> > A.
> >
> >
> > On Wed, Aug 15, 2012 at 5:53 PM, Adrian Cole <[email protected]> wrote:
> >
> >> Hi, Paul.
> >>
> >> Here's easiest way
> >>
> >> Apply latest patch here https://issues.apache.org/jira/browse/WHIRR-593
> >>
> >> Set
> >>
> >>
> whirr.template=osFamily=UBUNTU,osVersionMatches=12.04,os64Bit=true,minRam=1024
> >>
> >> Should be good.  If works, ping the issue and I can help commit it
> >> tonight.
> >>
> >> -A
> >> On Aug 15, 2012 5:45 PM, "Paul Baclace" <[email protected]> wrote:
> >>
> >> > I need to get Whirr 0.8.0 running on HPCloud *today* so I can help
> >> people
> >> > generate
> >> > clusters for the ACM local chapter (sfbayacm.org) hackathon on Aug.
> 18
> >> > sponsored in part by HPCloud.
> >> >
> >> > Because of WHIRR-593, I built Whirr from trunk.
> >> >
> >> > My plan is to use Ubuntu 12.04 LTS Precise, 64-bit.
> >> >
> >> > whirr.provider=hpcloud-compute
> >> >
> >> > How does one find the possible values for:
> >> >
> >> > whirr.image-id  // I assume numbers seen in HP web console work here
> >> > whirr.hardware-id  // use number from openstack or names like
> >> > standard.medium ?
> >> > whirr.location-id  // what is proper form here?
> >> >
> >> > and any other property settings I need to know about for HPCloud?
> >> >
> >> > Thanks,
> >> >
> >> > Paul
> >> >
> >> >
> >>
> >
> >
>

Reply via email to