Comment 4 for bug 1183831
Revision history for this message
| Marius B. Kotsbak (mariusko) wrote Re: ec2 constraints missing | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The reason we are using this is to have spread instances between Amazon HA zones (until Juju learns to do this itself). It works, although it makes juju status and juju-gui output harder to view.
The workaround is like this:
juju deploy --config config.yaml --constraints ec2-zone=a haproxy haproxy-a
juju deploy --config config.yaml --constraints ec2-zone=b haproxy haproxy-b
juju deploy --config config.yaml --repository charms --constraints ec2-zone=a local:apache2 apache-a
juju deploy --config config.yaml --repository charms --constraints ec2-zone=b local:apache2 apache-b
juju add-relation apache-a:balancer haproxy-a:website
juju add-relation apache-a:balancer haproxy-b:website
juju add-relation apache-b:balancer haproxy-a:website
juju add-relation apache-b:balancer haproxy-b:website
Please add support for ec2 zones again until there is another way to do this.