Skip to main content

Dynamically sync Route53 DNS entries for Zookeeper servers in an Exhibitor cluster

Project description

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.

Usage:

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

exhibitor2dns-0.1.2.tar.gz (2.9 kB view details)

Uploaded Source

File details

Details for the file exhibitor2dns-0.1.2.tar.gz.

File metadata

File hashes

Hashes for exhibitor2dns-0.1.2.tar.gz
Algorithm Hash digest
SHA256 76d8a8f56c8c3b53a4ac8b1ae5880e08dd964b315febfebd48fd1e11d7e58600
MD5 d6f52fd4b27c2d4dbe02886db25c9922
BLAKE2b-256 7267d7ab3fa7bc78930894bfd408acfeeab4fa2e7e509f70d42373ca37c2b73f

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page