Home

Proposed Features

Feature	Owner	Decision	Current Status	Notes
IPv6 support	fsweetser			Address storage no good 128 bit int in Mysql - may require switching to Postgresql backend.
Switch to Postgresql backend	fsweetser		First pass implemented at WPI - read working, write ops untested.	Better transaction support, native inet/cidr column types provide easier IPv6 support.
Convert to Catalyst application				Think Ruby on Rails, for Perl. http://www.catalystframework.org/ http://www.amazon.com/Definitive-Guide-Catalyst-Maintainable-Applications/dp/1430223650
DNSSec			User somlo at CMU has DNSSec aware dns-config.pl working.	If the DNSSec-specific bits (key management, zone signing) are delegated to a (master) DNS server (see link above), this could be as simple as implementing DS record attributes on delegated zones, with behavior almost identical to how NS records are currently handled
Simple RPZ support				New zone type to automatically associate RPZ policy with policy zone.
UI overhaul				Could use some updated aesthetics (CSS, icons), and possibly a sprinkling of javascript.
Add ostype and serial number data to machine records	fsweetser		Implemented at WPI.	New columns vs attribute? Mandatory vs optional?
Database schema versioning				Need to have explicit schema version tracking in database. Continue rolling custom vs pre-canned solution (couldn't find many in perl...)? Require rollback support?
Overhaul DNS/DHCP/etc deployment scripts				On-demand runs vs fixed schedule? Better orchestration: mcollective, puppet
Make links idempotent				Browser refresh action should always be safe (never try to add host twice, etc)
Split horizon DNS				BIND Views, separate DNS servers.
Support for multiple NICs per machine, multiple IPs per NIC, and multiple VLANS per NIC.
Alternate DNS server support				djbdns support - others?
IP Range support	fsweetser		Implemented at WPI.	Adds IP ranges as a new first class object. Each IP range consists of a subnet reference, and a high and low IP address contained with the subnet. Users create registrations with a range, rather than a subnet. This allows IP addresses to be organized within a subnet, such as for keeping a particular class of machines behind a firewall block or within QoS classification.