SOGo. Open Source Groupware at the University of Konstanz

Transcription

1 SOGo Open Source Groupware at the University of Konstanz -- Pascal Gienger Mail: University of Konstanz, IT Services Department ("Rechenzentrum") Building V, Room V404, Phone , Fax G+:

2 The groupware dilemma

3 The groupware dilemma Commercial systems are "all in a box":

4 The groupware dilemma Commercial systems are "all in a box": All parts ( , Calendaring, Appointments, Backend Storage) are combined - integrating them in a heterogenous environment means a total replacement.

5 The groupware dilemma Commercial systems are "all in a box": All parts ( , Calendaring, Appointments, Backend Storage) are combined - integrating them in a heterogenous environment means a total replacement. License costs often per user

6 The groupware dilemma Difficulty to avoid any vendor "lock-in"

7 The groupware dilemma Difficulty to avoid any vendor "lock-in" Users'/Customers' demand: Web applications

8 The groupware dilemma Difficulty to avoid any vendor "lock-in" Users'/Customers' demand: Web applications A "Linux/Unix"-based IT department has difficulties integrating a non-unix solution

9 Situation Univ. Konstanz

10 Situation Univ. Konstanz Mail: 40,000,000 stored mails in 40,000,000 files + working Tivoli TSM backup on ZPOOL

11 Situation Univ. Konstanz Mail: 40,000,000 stored mails in 40,000,000 files + working Tivoli TSM backup on ZPOOL 13,000 user accounts - 156,000 mail folders

12 Situation Univ. Konstanz Mail: 40,000,000 stored mails in 40,000,000 files + working Tivoli TSM backup on ZPOOL 13,000 user accounts - 156,000 mail folders Two proprietary groupware systems: - Zimbra - Microsoft Exchange

13 Situation Univ. Konstanz 40,000 new mails per 24h

14 Situation Univ. Konstanz 40,000 new mails per 24h 5,000-6,000 open connections on our Cyrus IMAP

15 Situation Univ. Konstanz 40,000 new mails per 24h 5,000-6,000 open connections on our Cyrus IMAP 10 TB mail storage, approx 4 TB used (compressed, 6 TB uncompressed)

16 Our decision: SOGo

17 Our decision: SOGo Cyrus IMAP infrastructure is supported

18 Our decision: SOGo Cyrus IMAP infrastructure is supported OpenLDAP is supported

19 Our decision: SOGo Cyrus IMAP infrastructure is supported OpenLDAP is supported PostgreSQL is supported: Performance can be analyzed easily (ANALYZE EXPLAIN...)

20 Our decision: SOGo Cyrus IMAP infrastructure is supported OpenLDAP is supported PostgreSQL is supported: Performance can be analyzed easily (ANALYZE EXPLAIN...) No migration overhead

21 SOGo basic architecture

22 SOGo basic architecture

23 IMAP SMTP LDAP pgsql Ironports Cyrus IMAP SOGo c OpenLDAP FC SAN Storage PostgreSQL HA Service

24 IMAP SMTP LDAP pgsql Ironports SOGo Webfrontend Cyrus IMAP SOGo c OpenLDAP FC SAN Storage PostgreSQL HA Service

25 SOGo Web interface

26 SOGo Web interface

27 SOGo Web interface

28 SOGo Web interface

29 SOGo Web interface

30 Example: Thunderbird

31 Example: Thunderbird

32 Example: Thunderbird

33 Example: Thunderbird

34 Example: Thunderbird

35 Example: Android 2.3

36 Example: Android 2.3

37 Example: Android 2.3

38 Example: Android 2.3

39 Example: Android 2.3

40 Example: Android 2.3

41 Example: Android 2.3

42 Example: Apple ical

43 Example: Apple ical

44 Example: Apple ical

45 Example: Apple ical

46 Example: Apple ical

47 IMAP SOGo + Outlook LDAP pgsql Cyrus IMAP SOGo c OpenLDAP PostgreSQL HA Service

48 SOGo + Outlook OpenLDAP University AD Cyrus IMAP SOGo 2.0 AD Slave: Samba 4 as Domain Member Outlook MAPI OpenChange

49 SOGo 2.0

50 SOGo 2.0 SOGo 2.0 comes with an OpenChange plugin.

51 SOGo 2.0 SOGo 2.0 comes with an OpenChange plugin. OpenChange enables MAPI, i.e. Exchange- Compatibility for Microsoft Outlook

52 SOGo 2.0 SOGo 2.0 comes with an OpenChange plugin. OpenChange enables MAPI, i.e. Exchange- Compatibility for Microsoft Outlook Samba 4 as Domain Member of an active AD Domain will be a supported configuration.

53 SOGo 2.0 SOGo 2.0 comes with an OpenChange plugin. OpenChange enables MAPI, i.e. Exchange- Compatibility for Microsoft Outlook Samba 4 as Domain Member of an active AD Domain will be a supported configuration. Authentication to Cyrus IMAP is "trusted".