According to our docs https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/DNS DNS zones should belong to the cloudinfra project. I tried a couple mechanism for the initial setup of the zones but I'm not convinced:
- Create zone in the admin project using the cmdline, then manually update the database to set the owner project for the domain
This was how wmcloud.org was set until today. @Krenair discovered the zone lacked the SOA records, thus an invalid zone that I finally deleted to recreate.
Not sure what happened here, but a workflow requiring manual updates to the database is far from elegant.
- Create zone in the admin project, using the cmdline. Then try using the openstack zone transfer native mechanism for updating the zone ownership.
I couldn't figure out how this work. The 2 commands below resulted in the zone still being owned by the admin project.
openstack zone transfer request create --target-project-id cloudinfra 6ddcb082-69d6-43f4-9993-5c6bdc27dfc9 openstack zone transfer accept request --transfer-id cb12641f-7cdc-4b0f-85c6-5ecaae43bd3b --key XXXXXX --sudo-project-id cloudinfra
This task is about reviewing this workflow and documenting it in wikitech, probably here: