TYPO3 Infrastructure
1 like1,881 views
The document provides an overview of the TYPO3 infrastructure presented by Christian Trabold at the TYPO3 Conference Asia 2012, highlighting its history, lessons learned, and future plans. Key topics include the evolution of TYPO3's service structures, the importance of automation and monitoring, and best practices for quality control. The presentation also outlines upcoming steps such as enhancing monitoring and documentation efforts.
TYPO3 Infrastructure
- 1. TYPO3 Infrastructure TYPO3 Conference Asia 2012 Christian Trabold Saturday, August 18, 12
- 4. Christian Trabold Senior Developer dkd Internet Service GmbH TYPO3 since 2004 Focus on quality assurance Author of TYPO3 Cookbook, O'Reilly Member of TYPO3 Server Team About me Saturday, August 18, 12
- 5. Twitter: @ctrabold eMail: typo3@christian-trabold.de Slides: slideshare.net/ctrabold Contact Saturday, August 18, 12
- 6. - History of TYPO3's infrastructure - Lessons learned - Future steps - How to get in touch - Question and answers Agenda Saturday, August 18, 12
- 7. In The Beginning Of Saturday, August 18, 12
- 8. Simple Structures Saturday, August 18, 12
- 9. mailing typo3.org list(s) TYPO3 Code CVS later SVN Simple Structures Saturday, August 18, 12
- 10. Several years later… Saturday, August 18, 12
- 11. typo3.org More services Saturday, August 18, 12
- 12. lists buzz notes typo3.org api forge wiki SVN More services Saturday, August 18, 12
- 13. lists buzz notes typo3.org api forge wiki SVN Two version control systems Saturday, August 18, 12
- 14. lists buzz notes typo3.org api forge wiki Git SVN Two version control systems Saturday, August 18, 12
- 15. lists buzz notes typo3.org api wiki Git SVN Two version control systems Saturday, August 18, 12
- 16. lists buzz notes typo3.org api wiki Git SVN Service down??! Saturday, August 18, 12
- 17. lists buzz notes typo3.org api wiki #wtf Git SVN Service down??! Saturday, August 18, 12
- 18. wiki Git SVN monitor rev iew ing We need Quality Control Saturday, August 18, 12
- 19. ci m etr ics … MORE Quality Control! Saturday, August 18, 12
- 20. chef grant va Configuration Management Saturday, August 18, 12
- 21. logs ? Future plans Saturday, August 18, 12
- 22. Server Team Build solid ground Saturday, August 18, 12
- 23. Saturday, August 18, 12
- 24. Powered by OpenSource Saturday, August 18, 12
- 25. Debian Linux OpenVZ MediaWiki Jenkins Sonar Redmine Chef Vagrant Powered by OpenSource Saturday, August 18, 12
- 26. OpenSource powered by OpenSource Saturday, August 18, 12
- 27. OpenSource powered by OpenSource Saturday, August 18, 12
- 28. Lessons learned Saturday, August 18, 12
- 29. - Automation is very important - Use configuration management tools like Chef to automate and document processes - Be able to operate even when the Team member "in charge" leaves the team Best practices Saturday, August 18, 12
- 30. - Metrics and Monitoring are super important to react quickly - You should know when something goes down before the users - Publish status report when something goes wrong. The community will appreciate it. Best practices Saturday, August 18, 12
- 31. The future Saturday, August 18, 12
- 32. - Write more Chef cookbooks - We aim for documentation that is executable and always up to date - Publish our cookbooks github.com/organizations/ typo3-cookbooks/ Next steps Saturday, August 18, 12
- 33. - Improve our Monitoring with a centralized Log-Server - Automate and monitor more everything! - Get lazy and work remotely from the beach Next steps Saturday, August 18, 12
- 34. © Christian Trabold Saturday, August 18, 12
- 35. Get in touch admin@typo3.org Saturday, August 18, 12
- 36. Follow for Updates @TYPO3server Saturday, August 18, 12
- 37. Join the Team http://typo3.org/ teams/server-team Saturday, August 18, 12
- 39. Have fun with TYPO3! Get it on http://get.typo3.org/ Saturday, August 18, 12
- 40. អរគុណ&'ច)ន Thank you! Saturday, August 18, 12
Editor's Notes
- #2: Provide solid Infrastructure for a growing community\nWe are a service provider for community and teams.\n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: Explain history of TYPO3's infrastructure (that's how I recall it, probably incomplete).\n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: … everything goes well until something strange happens …\n
- #21: … everything goes well until something strange happens …\n
- #22: \n
- #23: Monitoring: Zabbix + custom checks\n\nReview: And a Tool to review code - death to dev list "patch" workflow\n\nNow you just patch and commit and wait for a review +1/-1\n
- #24: "Support" the review process\n\n- Get metrics for all TYPO3 extensions\n- Testing TYPO3 v4 Core against CGL\n- Testing TYPO3 v4 Core UnitTests via Travis-CI\n
- #25: Example cookbooks: otrs, zabbix\n\nAlso featured in the FoodFight Podcast\n\nVagrant for testing the cookbooks and Testmate\n
- #26: More tools planned:\nlogs.typo3.org -> Graylog2\n
- #27: Bottom line: The Server Team builds the Soil for the TYPO3 ecosystem\n\nONE address to address issues and to communicate: admin@typo3.org\nThis forwards to OTRS which allows filtering and further processing\n
- #28: old but gold.\n\nNot the latest pic but you get an idea. We're humans :)\n
- #29: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #30: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #31: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #32: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #33: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #34: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #35: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #36: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #37: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #38: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #39: Open Source projects in use\nBigBlueButton\nBackupPC\nDebian Linux\nGerrit\nJenkins\nMediaWiki\nOpenVZ Virtualization System\nOpscode Chef\nOTRS\nTravis-CI\n\n
- #40: This applies IMO for every OpenSource project\n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: We are happy to answer your questions\nand learn from your feedback!\n
- #48: This way we inform you about server outages, changes and new cool features\n
- #49: Everybody \n
- #50: \n
- #51: \n
- #52: \n