Ansible & GitLab CI / CD Workshop 101 ( @Agile Tour Taipei 2017)
5 likes1,043 views
该文档介绍了一个Ansible和GitLab CI/CD的工作坊，强调自动化的各个阶段，从代码提交到部署的流程。文中探讨了中间环境的构建、测试和生产环境的差异，以及如何管理和优化自动化脚本和测试过程。文档还提出了一系列思考题，鼓励参与者深入理解和反思CI/CD实施中的最佳实践。
Ansible & GitLab CI / CD Workshop 101 ( @Agile Tour Taipei 2017)
- 1. Cheng Wei Chen @ Agile Tour Taipei 2017Photo by Daniel McCullough on Unsplash Ansible & GitLab CI / CD Workshop 101
- 2. Cheng Wei Chen 陳 正瑋 DevOps Engineer @ 得寬科技 http://chengweichen.com
- 5. 現場不進行詳細的操作步驟
- 7. 在開始之前...
- 8. 你讀完了嗎？
- 9. 你讀完了嗎？
- 10. 沒讀完也很正常啦
- 12. code build test release deploy operateplan Continuous Integration Continuous Delivery 目標 Continuous Deployment CIcommit dev stagingtest testprod deploy environment dev staging prod local
- 13. commit code build test release deploy operateplan Continuous Integration Continuous Delivery 今天的案例 Continuous Deployment CI staging testprod deploy environment staging prod
- 14. commit build stg-deploy test unit test prod-deploy 今天的案例 prod-remove
- 15. 該選用哪些工具？
- 20. 該從何處開始著手？
- 21. code build test release deploy operateplan Automation 從痛點、小處著手 Automation
- 22. Deploy 從痛點、小處著手 stagingdev test test production staging test production Project-1 Project-2 production Project-3 x10 x5 x3
- 24. .gitlab-ci.yml
- 30. build Stage: Build build-test build-release Artifacts (test) Artifacts (release) Artifacts Repository (release) Artifacts Repository (release)
- 32. ‧什麼是 Artifacts？ ‧為何需要 Artifacts？ ‧以及 Artifacts Repository？ 延伸思考
- 33. 延伸思考 ‧為何要在 Build 時，同步進行 兩個 Jobs，一次就將測試與 Production 兩種環境的 Artifacts 給建立？ ‧有沒有更好的做法？
- 34. 延伸思考 ‧在建立給 Production 使用的 Artifacts 時，還有哪些不必要 的檔案可以刪除，並不需要一 起放進 Artifacts Repository？
- 35. ‧將 Ansible Playbook 與程式碼一起 送進同一個 Project Repository？ ‧自動化腳本應該如何存放？存放於 何處？ ‧該如何讓 CI Runner 可以順利取得 自動化腳本呢？ 延伸思考
- 36. build unit test Stage: unit-test build-test build-release phpunit
- 40. build unit test Stage: stg-deploy build-test build-release phpunit stg-deploy
- 48. ‧續上，你規劃的自動 Deploy 流程可以反覆的 Re-eploy 嗎？ ‧當自動 Deploy 失敗時該如何 處理？ 延伸思考
- 49. ‧Token、Key、inventory 或其 他 CI Job 需要的機敏資料應該 怎麼管理？並傳遞給 Runner？ 延伸思考
- 51. build unit test Stage: stg-test build-test build-release phpunit stg-deploy stg-test stg server stg server
- 57. build unit test Stage: prod-deploy build-test build-release phpunit stg-deploy stg-test stg server stg server prod-deploy
- 60. ‧Deploy 至 Staging 與 Production 的差異有哪些？ 延伸思考
- 62. ‧再一次，Zero downtime deploy？ ‧同樣 Files、Storages？ ‧DB Migration？ 延伸思考
- 65. ‧如何管理不同 Branch 不同 Pipeline？ ‧哪些 Job 可以共用？ 延伸思考
- 66. build unit test Stage: prod-deploy build-test build-release phpunit stg-deploy stg-test stg server stg server prod-deploy prod-remove
- 68. Summary
- 69. code build test release deploy operateplan Continuous Integration Continuous Delivery 目標 Continuous Deployment CIcommit dev stagingtest testprod deploy environment dev staging prod local
- 70. : https://unsplash.com/photos/Fixg8KipOg8 Trigger ScriptsInterface ServiceFlow 注意每個環節
- 74. code build test release deploy operateplan Automation 從痛點、小處著手 Automation
- 75. • • • • • 思考並評估
- 76. 好書非讀不可
- 79. • Operator-triggered manual action • Operator-written, system-specific automation • Externally maintained generic automation • Internally maintained, system-specific automation • Autonomous systems that need no human intervention 自動化的演進 https://landing.google.com/sre/book.html
- 80. 反覆評估、持續改善 Photo by Sweet Ice Cream Photography on Unsplash 迭代
- 81. 工商服務
- 83. 尋求志工、贊助 : https://pixabay.com/en/building-joy-planning-plans-1080592/ , https://pixabay.com/en/baby-hand-dad-200760/
- 87. Photo by Clark Tibbs on Unsplash Thank You