H2006 P5 691822 OpenSourceSoftware

Open Source Software& Communication Infrastructure: 

Open Source Software & Communication Infrastructure Jean Talbot

Plan: 

Plan Main question: Should a company consider open source software to build its infrastructure? Introduction to OSS (David Wheeler) Presentations Case: Mail infrastructure of HEC Montréal OSS Market Look at the numbers (David Wheeler) Choice of OSS &economic consideration

Introduction to OSS: 

Introduction to OSS See David Wheeler

Case: HEC’s email infrastructure: 

Case: HEC’s email infrastructure

HEC Montreal’s e-mail infrastructure: 

HEC Montreal’s e-mail infrastructure Large and complex system Old system 4 IBM AIX Servers Netscape Messaging Server 4.15 (Netscape/Iplanet/Sun) POP3, IMAP, SMTP, Webmail Slow, not scalable, inundate with Spam, UBE Almost “unusable”

Size: 

Size 35,000 accounts Growth of 2,000-3,000 users a year 125,000 emails per day of which 40 to 60% is UBE In one week over 600,000 UBE Number of connections 300,000 POP3 60,000 IMAP

Constraints: 

Constraints Could not afford a per user license Management should be automated as much as possible (account creation/destruction) Scalable Had to be proven

Solution: 

Solution 11 IBM eServer x305 and x355 Red Hat LINUX (XFS kernel) with Linux HA Heartbeat 2 Cyrus IMAP Servers: (IMAP, LMTP, POP3, SASL) 4 SMTP Servers which run Postfix, AMaVis, SpamAssassin, Vipul’s Razor and NAI’s Virus Scan 2 Webmail servers running Apache, PHP4, IMAP proxy, SquirrelMail 2 OpenLDAP Servers The two x355 are connected to an IBM FAST 700 SAN using Fiber Channel

Solution: 

Solution UBE filtering real-time blackhole lists (RBLs); header and MIME header checks using up-to-date maps from SecuritySage, Inc.; content filtering initiated from AMaViS using SpamAssassin, Vipul’s Razor for UBEs analysis and VirusScan for viruses.

acronyms: 

acronyms IMAP: Internet Message Access Protocol POP3: Post Office Protocol SMTP: Simple Mail Transfer Protocol LMTP: local Mail Transfer Protocol SASL: Simple Authentication and Security Layer PHP: Hypertext PreProcessor Postfix: Mail Transfer Agent RBL: Real-Time Blackhole List

Rest of the Communication Infrastructure: 

Rest of the Communication Infrastructure Oracle Calendar Windows Sharepoint Services Mail clients: Outlook and Outlook Express CMS

Open Source Market: 

Open Source Market OS: Linux/GNU, BSD Desktop: Open Office from Sun; FireFox from Mozilla DBMS:MySQL; PostgreSQL ERP; Compiere E-mail: SendMAil, Postfix, Cyrus IMAP, Hula Sever (ex Novell NetMail) Collaboration: Kolab2, Open GroupWare Web Server: Apache Programming Language: PHP Middleware: Jboss, Zope, JOnAS, Resin Learning Management System: Sakai

OSS Market: 

OSS Market Look at the numbers (see David Wheeler)

Free Software Foundation (http://www.fsf.org/) : 

Free Software Foundation (http://www.fsf.org/) The freedom to run the program, for any purpose (freedom 0). The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this. The freedom to redistribute copies so you can help your neighbor (freedom 2). The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.

Open Source Initiative(http://www.opensource.org/): 

Open Source Initiative (http://www.opensource.org/) See Open Source Definition

Creative Commons: 

Creative Commons http://creativecommons.org/

OSS Evaluation: 

OSS Evaluation D. Wheeler, “How to Evaluate Open Source Software / Free Software (OSS/FS) Programs’” (http://www.dwheeler.com/oss_fs_eval.html) D. Wheeler, “Generally recognized as Mature OSS/FS Programs,” http://www.dwheeler.com/gram.html Gap Gemini, “Open Source Maturity Model,” available on www.seriouslyopen.org Patricia Seybold Group, “Open Source Considerations: Evaluation criteria for Open Source Solutions,” Kenwood, C.A. “A Business case Study of Open Source Software,” Mitre Corporation, July 2001

David Wheeler’s Methodology: 

David Wheeler’s Methodology Identify candidates Read existing reviews Briefly compare the leading programs’ attributes to your needs Functionality, cost, market share, support, maintenance/longevity, reliability, performance, scalability, usability, security, flexibility/customizability, interoperability, legal/license issues, other issues Perform an in-depth analysis of top candidates In-depth analysis for adding functionality, In-depth analysis of software security

Business Model: 

Business Model Loss Leader/Market Positioner Widget frosting: Make money on hardware Give Away the Recipe, Open a Restaurant: Make money on service, branding, distribution Accessorizing (books, compatible hardware, complete systems with OSS) Free the software sell the content