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.1.tar.gz (2.9 kB view details)

Uploaded Source

File details

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

File metadata

File hashes

Hashes for exhibitor2dns-0.1.1.tar.gz
Algorithm Hash digest
SHA256 aa42713fd0e1fc93c382dfbfd724f17e7f6180cf4fe12570c9cb66340f69dddc
MD5 cc30625c3e7dfb92a493acd4c516679c
BLAKE2b-256 229aafc7f893201c2d46c1bcab25a5442ce75e0efb7c717e783f2d53974a9a9a

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