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

Registered by Scott Kitterman on 2008-06-06

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

Blueprint information

Status:
Complete
Approver:
Rick Clark
Priority:
Undefined
Drafter:
Scott Kitterman
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Started
Milestone target:
milestone icon later
Started by
Scott Kitterman on 2008-06-09
Completed by
Scott Kitterman on 2010-09-23

Related branches

Sprints

Whiteboard

This will take more than one release cycle to implement. Initial target is 9.04.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.