20d2643f74
On the old bridge node we had some unmanaged venv's with a very old, now unmaintained RAX DNS API interaction tool. Adding the RDNS entries is fairly straight forward, and this small tool is mostly a copy of some of the bits for our dns api backup tool. It really just comes down to getting a token and making a post request with the name/ip addresses. When the cloud the node is launched as is identified as RAX, this will automatically add the PTR records for the ip4 & 6 addresses. It also has an entrypoint to be called manually. This is added and hacked in, along with a config file for the appropriate account (I have added these details on bridge). I've left the update of openstack.org DNS entries as a manual procedure. Although they could be set automatically with small updates to the tool (just a different POST) -- details like CNAMES, etc. and the relatively few servers we start in the RAX mangaed DNS domains means I think it's easier to just do manually via the web ui. The output comment is updated. Change-Id: I8a42afdd00be2595ca73819610757ce5d4435d0a
14 lines
303 B
Django/Jinja
14 lines
303 B
Django/Jinja
gitea_kube_key: Z2l0ZWFfazhzX2tleQ==
|
|
|
|
ansible_cron_disable_job: true
|
|
cloud_launcher_disable_job: true
|
|
extra_users: []
|
|
|
|
rackspace_dns_username: user
|
|
rackspace_dns_project_id: 1234
|
|
rackspace_dns_api_key: apikey
|
|
|
|
rackspace_rdns_username: user
|
|
rackspace_rdns_project_id: 1234
|
|
rackspace_rdns_api_key: apikey
|