Project

With names like cloudstack-rabbitmq-dnsconsumer or acs-amq-dnsupdate it aims for the badest project name on github.

What is it useful for?

It's a simple but efficient glue between Apache CloudStack RabbitMQ and Nameservers with nsupdate/RFC 2136-capabilities.

It's able of adding, modifying and removing A, AAAA and PTR ressource-records on behalf of creating, editing or destroying VirtualMachines in CloudStack.

Schematics

---------------------
| apache cloudstack | <- VM creation, modification, removal
---------------------
         ||
     (rabbitMQ)
         \/
---------------------
| rabbitMQ exchange |
---------------------
         ||
     (rabbitMQ)
         \/
---------------------
| acs-amq-dnsupdate | <- (DNS TSIG and Zones JSON configuration)
---------------------\
         ||           \----------------------
     (RFC2136)        | SQLite stateful set |
         \/           -----------------------
---------------------
| authoritative \   |
|        nameserver |
---------------------

For this particular configuration example, we assume that the primary network is a Cloudstack Shared Network. The network is configured as a dualstack VLAN with IPv4 RFC 1918- and IPv6 public-addresses. It's DNS name shoud be identical to a (sub)domain delegated to an authoritative nameserver which needs to be accept Zone Updates via TSIG authentication. For this example, we publish IPv6 AAAA and IPv6 PTR to the public and private views of a split-horizon DNS (public./.internal), but to expose private IPv4 addresses (and their PTR counterpart) only to the private view.

See: /etc/acs-amq-dnsupdate.json

As an easy example, we install a RabbitMQ-Server locally. Apache CloudStack needs to be configured to use AMP/RabbitMQ. We're using the very same property values in our example:

See: /etc/default/acs-amq-dnsupdate

For your convenience, here's a systemd-unitfile and a small setup "script" which matches the bespoken example:

See: /etc/systemd/system/acs-amq-dnsupdate.service

See: use it as hint and handle with care :)

sudo -i
apt install python3-pika rabbitmq-server
pip3 install cs # https://github.com/exoscale/cs
cd /usr/local/src
git clone https://github.com/pussy-hosting/cloudstack-rabbitmq-dnsconsumer.git
install --mode=0755 --owner=root --group=root bin/acs-amq-dnsupdate.py /usr/local/bin/acs-amq-dnsupdate.py
install --mode=0640 --owner=root --group=root conf/acs-amq-dnsupdate /etc/default/acs-amq-dnsupdate
install --mode=640 --owner=root --group=root conf/acs-amq-dnddsupdate.json /etc/acs-amq-dnsupdate.json
install --mode=644 --owner=root --group=root systemd/acs-amq-dnsupdate.service /etc/systemd/system/acs-amq-dnsupdate.service
systemctl daemon-reload
# doing the cloudstack configuration ( http://docs.cloudstack.apache.org/en/latest/adminguide/events.html )
systemctl restart cloudstack-management
systemctl enable --now acs-amq-dnsupdate.service
journalctl -f acs-aqm-dnsupdate.service

There's also a doc directory with additional informations.

How is it done?

acs-amq-dnsupdate registers to an RabbitMQ Exchange for cloudstack-events. If getting notified due to VM.CREATE, VM.MODIFY or VM.DESTROY messages, it subsequently verifies and completes the VM information via CloudStack API calls, and finally builds nsupdate queries based on a configuration matrix. A sqlite-db was added to get stateful sets.

See: INSTALL.md