Here's a deployer bundle to deploy. rm -rf ./trusty wherever you are about to juju-deployer from to ensure you don't use cached charm checkouts
cat block-storage-trusty.yaml
common: services: storage: branch: lp:~chad.smith/charms/precise/storage/storage-volume-label-availability-zone options: provider: block-storage-broker volume_size: 9 block-storage-broker-ec2: branch: lp:~chad.smith/charms/precise/block-storage-broker/bsb-trusty-support options: provider: ec2 key: <YOUR_EC2_ACCESS_KEY> endpoint: <YOUR_EC2_URL> secret: <YOUR_EC2_SECRET_KEY> postgresql: branch: lp:~chad.smith/charms/precise/postgresql/postgresql-using-storage-subordinate constraints: mem=2048 options: extra-packages: python-apt postgresql-contrib postgresql-9.3-debversion max_connections: 500
doit: inherits: common series: trusty relations: - [postgresql, storage] - [storage, block-storage-broker-ec2]
juju-deployer -c block-storage-trusty.yaml doit
« Back to merge proposal
Here's a deployer bundle to deploy.
rm -rf ./trusty wherever you are about to juju-deployer from to ensure you don't use cached charm checkouts
cat block-storage- trusty. yaml
common:
options:
provider: block-storage- broker
volume_ size: 9
block- storage- broker- ec2:
options:
provider: ec2
key: <YOUR_EC2_ ACCESS_ KEY>
endpoint: <YOUR_EC2_URL>
secret: <YOUR_EC2_ SECRET_ KEY>
constraint s: mem=2048
options:
extra- packages: python-apt postgresql-contrib postgresql- 9.3-debversion
max_connectio ns: 500
services:
storage:
branch: lp:~chad.smith/charms/precise/storage/storage-volume-label-availability-zone
branch: lp:~chad.smith/charms/precise/block-storage-broker/bsb-trusty-support
postgresql:
branch: lp:~chad.smith/charms/precise/postgresql/postgresql-using-storage-subordinate
doit: broker- ec2]
inherits: common
series: trusty
relations:
- [postgresql, storage]
- [storage, block-storage-
juju-deployer -c block-storage- trusty. yaml doit