Once horizon properly manipulates domains, we need to migrate everything out of ldap and into pdns, then turn off the old ldap-based pdns server.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Andrew | T42525 Cant add a security group to an existing instance | |||
Resolved | Andrew | T87279 Make OpenStack Horizon useful for production labs | |||
Resolved | Andrew | T124181 Support instance manipulation, proxies, dns with Horizon | |||
Resolved | • AlexMonk-WMF | T104521 Support reverse dns for public labs IPs | |||
Resolved | Andrew | T124184 Switch to using Horizon/Designate for labs public dns | |||
Resolved | Andrew | T129272 Migrate DNS entries from ldap to designate |
Event Timeline
I have a script on californium that can do this: ~andrew/ldaptodesignate.py
Probably no need to put the script in puppet since it's a one-off.
Does this also handle SPF/TXT records? tools.wmflabs.org has one set, and there may be some others (although iirc non-A records were a manual process)
All done now except for:
probable domain conflict: beta in wmflabs.org for 208.80.155.135 in wmflabsdotorg
probable domain conflict: tools in wmflabs.org for 208.80.155.131 in wmflabsdotorg
...designate doesn't like me attaching an A record that matches a domain
I hacked those entries into the designate record table, but they still don't resolve :(
It turns out to be possible to create these, I just had to specify the fqdn:
openstack recordset create eae60a3b-a0df-47b2-9492-5fab480514fe tools.wmflabs.org. --type A --records "208.80.155.131"