Juju and HP Cloud Beta
nick.barcet at canonical.com
Thu Mar 29 21:17:18 UTC 2012
On 03/27/2012 05:35 PM, Clint Byrum wrote:
> Excerpts from James Page's message of Tue Mar 27 00:58:51 -0700 2012:
>> Hash: SHA256
>> Hi Marco
>> On 26/03/12 17:09, Marco Ceppi wrote:
>>> I've been trying to connect to the HP Cloud Beta with Juju and
>>> keep getting a 401 error from Twisted. Has anyone been able to do
>>> this yet? Here's my environment stanza stripped of sensitive
>>> information and the verbose error from Twisted
>>> hp-beta: type: ec2 default-instance-type: standard.xsmall
>>> access-key: --- secret-key: --- ec2-uri:
>>> default-image-id: ami-000004da control-bucket: juju-hp-test
>>> admin-secret: --- default-series: oneiric juju-origin: ppa
>>> The error is in the following pastebin link:
>> I don't think that the HP Cloud Beta supports the s3 API - so I would
>> suspect that the s3-uri is not working which is why you get this issue.
>> I guess you might still be able to use Amazon S3 with the HP Cloud
>> compute resources - I think juju's usage is pretty light.
> This won't work without changes to juju. It uses txaws's AWSServiceRegion
> to represent "AWS" as a whole, which sets the ec2 and s3 endpoints to
> connect to. Even though the uri's can be set individually, the auth
> keys cannot. A simple change would be to allow different auth credentials
> to be specified for s3.
> We've seen a number of problems with non Amazon providers of the EC2 api
> that do not really support S3. I wonder if a simple solution would be to
> include an optional WEBDAV service on node 0 to host charms and the seed
> data, sort of borrowing from the method used by orchestra and the local
> Another option is to decouple machine providers from object storage
What about using ceph RADOS + S3 Gateway as an option. Dreamhost's about
to release its public service based on that...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 900 bytes
Desc: OpenPGP digital signature
More information about the Juju