Closed (fixed)
Project:
Hostmaster (Aegir)
Version:
6.x-0.4-alpha3
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Oct 2009 at 22:02 UTC
Updated:
3 Jan 2014 at 00:29 UTC
Jump to comment: Most recent
Comments
Comment #1
anarcat commentedCurrent status: DNS provisionning works. We have a mostly complete, but very "advanced" frontend interface to edit zonefiles. It's way too complicated for the average user but should satisfy power users (but even then, it would require usability improvements). It also lacks proper permission and access controls. The backend is now able to create rather crude zonefiles and hook them up in bind, if bind is properly configured. The install/delete site tasks do not hook into DNS anymore.
Comment #2
anarcat commentedStatus update: the code was lost during the CVS->git migration, and I have made an effort to resurrect the branch. I haven't tested any of the new code, and it needs a proper kick in the butt to integrate with teh new server refactoring, but at least it's there (dev_dns branches on provision and hostmaster).
For the curious, note that I had to use
git format-patchandgit amto reapply the patches. It looked something like this:A similar process was applied to provision.
It wasn't possible to simply rebase the branch or import the whole branch because the master branch was merged in it a few times. That is bad practice: we should always *rebase* dev branches master, not merge master in it. The only time when we should use merge with dev branches is when they are ready to hit the master branch.
Comment #3
anarcat commentedcurrent frontend status:
1. the zone editor still works, but zone verification is broken for an unknown reason
2. the server stuff has been ported to the new server API in the frontend
current backend status: unknown.
Comment #4
anarcat commentedSo I'm going to close this meta-ticket now. I consider the first phase of DNS development to be complete: we have basic tools to manage zonefiles in the backend and creating/deleting sites creates and deletes records in zonefiles (#366814: manage DNS records properly when creating/restoring/verifying/disabling/deleting sites). Zonefile configs are also synced to slave servers (#366420: DNS slave server support) and the NS records are created in zonefiles according to the slave server configuration. The frontend can configure slaves on the master server.
I'll open more tickets for the next steps.