Develop a mechanism for scalably defining specifc sets of packages and package configurations for different server needs

To deliver a ready to use "Out of the box" experience for various server use cases, both package sets to be installed and special configurations must be provided at install. It needs an approach that is scalable, produces an easy to use install experience, and is policy compliant.

The initial test case for providing a server flavor is an inbound mail gateway flavor. It will use postfix as MTA, amavisd-new to provide content filtering (with clamav and spamassassin), and relay to an internal MDA. It will not have any local delivery. It will not support SASL. A feature goal is getting a valid recipient list via LDAP (possibly not until Intrepid +1).

This server flavor process will produce a unique CD image per flavor and possibly per install.

Needed pieces:

DI with preseed adjustments to call FAI late in the install process
FAI class definition for this flavor
A scenario editor to allow specification of per installation options in the FAI class