| 2012-09-27 19:01:27 |
Clint Byrum |
description |
The OpenStack provider is fairly isolated from the rest of the code base in Juju, and enables access to additional cloud providers (Namely, HP). |
== SRU Information ==
Note that this is not a bug fix bug a backported API enablement fix. Without this change, HPCloud and others cannot be used with juju in precise.
[Test Case]
1. Obtain credentials for an OpenStack cloud (HPCloud or a private instance of OpenStack)
2. Setup your credentials in ~/.juju/environments.yaml - Here is a redacted sample for hpcloud:
hpcloud:
juju-origin: proposed
access-key: XXXXXXXXXXXXXXXXXXXX
secret-key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
project-id: "youremail@yourdomain.foo-tenant1"
admin-secret: ffffffffffffffffffffffffffffffff
control-bucket: juju-eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
default-image-id: 8419
default-instance-type: standard.small
default-series: precise
region: az-1.region-a.geo-1
nova-uri: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/
auth-url: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/
auth-mode: userpass
username: youremail@yourdomain.foo
password: ZZZZZZZZ
project-name: youremail@yourdomain.com-tenant1
type: openstack
3. deploy mysql
juju bootstrap -e hpcloud
juju deploy mysql -e hpcloud
4. Verify it works
juju ssh -e hpcloud mysql/0 'sudo mysql -uroot -p`cat /var/lib/juju/mysql.passwd`'
[Regression Potential]
This is entirely new code, so the risk of regression is very low. One issue may be that entries of type: openstack added to environments.yaml will cause errors on earlier versions of juju, but these can be easily commented out.
==
The OpenStack provider is fairly isolated from the rest of the code base in Juju, and enables access to additional cloud providers (Namely, HP). |
|
