Updates DNS records for Clearwater using AWS Route53 service
This charm supports deployment of the AWS Route53 DNS agent for installing Project Clearwater in AWS EC2. See http://www.projectclearwater.org for more information on Project Clearwater.
The Clearwater Route53 service should be deployed as part of a Clearwater system. A Clearwater system can be deployed in a Juju environment by creating a config.yaml file then running the following commands.
juju deploy --config config.yaml clearwater-route53
juju deploy --config config.yaml clearwater-ellis
juju deploy --config config.yaml clearwater-bono
juju deploy --config config.yaml clearwater-sprout
juju deploy --config config.yaml clearwater-homestead
juju deploy --config config.yaml clearwater-homer
juju add-relation clearwater-ellis clearwater-route53:register-ellis
juju add-relation clearwater-bono clearwater-route53:register-bono
juju add-relation clearwater-sprout clearwater-route53:register-sprout
juju add-relation clearwater-homestead clearwater-route53:register-homestead
juju add-relation clearwater-homer clearwater-route53:register-homer
juju expose clearwater-bono
juju expose clearwater-ellis
The config.yaml configuration file takes the following format.
access_key: <ec2 access key>
secret_key: <ec2 secret access key>
clearwater-route53 does not current support scaling out.
The only currently supported DNS service for Clearwater is clearwater-route53 (when deploying in Amazon EC2), so will currently only work on EC2. Additional DNS services will be added for other environments in future.
Note that this charm does not current pass charm proof because its hooks use EC2 APIs directly to obtain the public IP address rather than unit-get public-address. This is to work around what looks like a Juju bug - unit-get public-address on EC2 returns the public hostname of the unit rather than the public IP address. Unfortunately EC2 public hostname are actually split horizon hostnames, so if you attempt to resolve the hostname from within EC2 it actually resolved to a private IP address - it will only resolve to a public address if resolved from outside EC2.
Clearwater has a number of configuration fields which are non-defaultable. These are as follows.
See http:www.projectclearwater.org and https://github.com/Metaswitch/clearwater-docs/wiki for information about clearwater.
Clearwater source code and issue list can be found at https://github.com/Metaswitch/.
The Clearwater mailing list is at lists.projectclearwater.org.