Dynamically sync Route53 DNS entries for Zookeeper servers in an Exhibitor cluster
Exhibitor2dns will keep a round-robin A record in sync with the state of a Zookeeper ensemble managed by the excellent Exhibitor supervisor from Netflix. This is particularly useful if your Zookeeper nodes are in an autoscaling group, or any other setup where you don’t have fixed IP addresses for your Zookeeper servers.
exhibitor2dns --zone=yourzone.example.com \ --exhibitor_url=http://your-exhibitor-endpoint.example.com/ \ --rr=zookeeper
exhibitor2dns uses Boto to interact with Route53, so you have various options for providing aws credentials. You can set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY envivonment variables, or if exhibitor2dns is running on an ec2 instance it will try to use the instance’s IAM role if there is one available. See the Boto documentation for more details.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size exhibitor2dns-0.1.2.tar.gz (2.9 kB)||File type Source||Python version None||Upload date||Hashes View hashes|