This is an old revision of the document!
A blueprint for an open source, identity managed, unix based office-automation and business infrastructure.
The Hannibal is an architecture and documentation project. It consists of a carefully selected set of open source programs, which, put together and configured in the right way, can harmoniously form a very useful package of service for you or your organisation.
The system-stack provides file/print/e-mail/web/etc. functionality with single sign-on. It does this for all types of workstations (microsoft-windows-95/nt4/nt5/xp), Unix/Linux and Apple macintosh. It serves files with the cifs/smb protocol using Samba (NT-primary domain controller emulation) or NFS. It serves mail with SMTP/LMTP using Postfix. It filters mail on the server-side using Sieve, it scans mail for virusses and spam using Amavis, Spamassassin and Clamav, it serves mailboxes to users with IMAP using Cyrus-IMAPd or with a webmailer using Squirrelmail or Roundcube. It serves HTTP using Apache (including http-authentication and web-dav folders). Mort important, all authentication of this is done against an LDAP database (the Redhat/Fedora directory server). The used operatingsystem is a standard Debian GNU/Linux system. In a oneliner; all you need for your office automation and business infrastructure.
The best of it is that this is all done with open standards and open source software. No worries about vendor lock-in scenario’s from suppliers or whatsoever.
Buy yourself an implementation and subsequent maintenance support from one of the certified Hannibal-system-stack partners, or build it with your own IT-staff. The choice is yours, experienced staff is more than useful, but the technology is full-disclosure. Thanks to all open source developers!
Below is the outline of the Hannibal infrastructure. Each item represents a separate module. Normally each module corresponds with one physical server. As an alternative virtualization like Xen, KVM or User-mode-linux can be used. For instance, our laboratory is only one big physical machine that runs Xen. Some of our own considerations and documentation regarding Xen are available at the Xen section of this wiki.