Roadmap

• Milestone: Fastdeploy 0.4

  2 years late (05/21/07)

  Prospective feature completion:

  * Installer mechanism - multi-stage, "Web 1.0"; configures and installs into MySQL; checks filesystem permissions; creates directory structure for internal FD site, TFTPBOOT, and mirrors directories; checks existence of PEAR libraries (pre-flight check for Smarty and PEAR itself--some distributions don't have it installed by default?); multi-language support; generates configuration file.

  * Self-serve module: DSL based installer that connects via Firefox to simplified "Wizard" type installer based on MAC address. User cannot pick IP address info. If MAC does not exist, the self-serve module rejects the user. Self-serve users will have their own user authentication table with the potential to use another auth mechanism (another database, LDAP, etc.).

  * Solaris 10 x86 support. Preliminary testing reveals this is feasible. NFS server must exist as "install_media" option passed to the Sol kernel doesn't support http/ftp/etc options. Linux apparently doesn't support NFSv4 properly so NFSv3 server support must be forced in the running kernel. xBSD and of course Solaris servers serving Fastdeploy may be a different story.

  * General cleanup of Windows support. This is mostly done. Partitioning was NOT working on the 0.3 beta. I think this is now fixed. Need a full installation guide available on how to get Windows support working as well as requisite tarballs and RPMs/DEBs to support Windows from a Linux/UNIX perspective.

  * Yum and APT repositories. Mostly done. SPEC and .deb build files complete. Should be easy to build new RPMS and DEBs. Yum repositories not easy to create from Debian servers.

  * Build system and process standardizations (for backend). Mostly helter skelter right now.

  * Need simple tarballs and RPMs/DEBs for TFTPBOOT structure and initrd images used for Windows and rescue disk support.

  * VMWare virtual appliance. Part of the way there. Once the installer mechanism is done I'd like to have a simplified installer that can run automatically once the appliance runs. This appliance will use NFS mounted mirror directories rather than mounted ISOs like other appliances.

  * Support partitioning for as many OSes as possible.