History: Tiki Suite 2013 deployment plan
Preview of version: 17
- «
- »
What
A plan to deploy Tiki Suite "as is" for a company of 20-30 employees. Document everything along the way, and gather experience on interoperability and additional components. This company will dogfood internally, with the goal of offering as a service to their customers.
When
- September-October 2013
Budget
Absolute minimum
Install and configure the base packages as-is, without 3rd party packages. We configure all three systems with built-in features and configure them to all work nicely together.
These three packages have so many features, it's just insane 😊
- https://doc.tiki.org/Features
- http://www.bigbluebutton.org/
- http://www.clearfoundation.com/Software/overview.html
They also manage internally the complexity of interoperability of a huge number of components, libraries, etc
- https://dev.tiki.org/External+Libraries
- http://www.bigbluebutton.org/components/
- http://www.clearfoundation.com/Foundation/integrated-code.html
We need 2 root servers (virtual servers are fine) on which we will install
- ClearOS + Tiki (1 gig RAM, 10 Gig disk)
- BigBlueButton
- https://code.google.com/p/bigbluebutton/wiki/081InstallationUbuntu
- Alternatively, for the test, we can get a hosted account at http://hostbbb.com/ and just need one server.
Low-hanging fruit
Here, we implement desired things that are not part of the base packages, but have already been implemented by others, following and improving the documentation. We must also think ahead for the new possibilities offered by HTML5 (like WebRTC, etc.). We get in touch with the various projects and by the end of this phase, we'll have clearer idea of the road ahead.
Webmail
"The default groupware and mail solution is now based on Zarafa technology."
http://www.clearfoundation.com/docs/release_info/clearos_community_6.3.0/final_release_information
http://www.clearcenter.com/support/documentation/clearos_professional_6/6.3.0_release_notes
If this is not suitable for us because the community edition has limitations, we can look into Kolab and RoundCube
- http://kolab.org/news/2013/07/16/kolab-3.1-alpha-released-irony
- http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,40/func,view/id,46421/limit,10/limitstart,20/
Phone system
- http://www.clearfoundation.com/docs/howtos/freeswitch_with_sipxecs
- BigBlueButton: We can add a 1-8xx phone number so people can call in from Skype and regular phones
Presence
To be discussed
Better inetgration between Tiki and ClearOS
Under the hood, a new engine for supporting web applications is also in development.
Dreaming
Once we have experimented enough with the various components, we can start improving interoperabiliy, adding missing features, and thinking of large scale deployment and maintenance
- Tight integration of users, groups, search, etc. between all systems
- Configuration Management and Systems Orchestration so we can deploy this automatically
- Make Tiki Webmail awesome (and associated features like Contacts and Calendar)
History
| Information | Version | |||||
|---|---|---|---|---|---|---|
| Marc Laporte | 41 | |||||
| Marc Laporte | 40 | |||||
| Marc Laporte | 39 | |||||
| Marc Laporte | 38 | |||||
| Marc Laporte sipX and ClearOS have conflicts | 37 | |||||
| Marc Laporte | 36 | |||||
| Marc Laporte 3 servers | 35 | |||||
| Marc Laporte | 34 | |||||
| Marc Laporte | 33 | |||||
| Marc Laporte | 32 | |||||
| Marc Laporte Zarafa looks really good | 31 | |||||
| Marc Laporte | 30 | |||||
| Marc Laporte | 29 | |||||
| Marc Laporte | 28 | |||||
| Marc Laporte | 27 | |||||
| Marc Laporte | 26 | |||||
| Marc Laporte | 25 | |||||
| Marc Laporte | 24 | |||||
| Marc Laporte typo | 23 | |||||
| Marc Laporte | 22 | |||||
| Marc Laporte | 21 | |||||
| Marc Laporte | 20 | |||||
| Marc Laporte | 19 | |||||
| Marc Laporte | 18 | |||||
| Marc Laporte | 17 | |||||