Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Bringing the Chef Habitat Depot On-Premise in the Enterprise

Bringing a Chef Habitat Depot on-premise in the enterprise and managing it can pose some unique challenges. Throughout this presentation, we cover the challenges you may come across, how to overcome them and bring in real-life examples of how companies have implemented it in the Enterprise. This will include taking a look at the use of a proxy-Habitat Depot, scaling out individual parts of the Chef Habitat Depot for high-availability and using Continuous Integration to enforce role-based access control.

For more information on how Indellient helps Chef customers, check out https://www.indellient.com/pipeline/chef-services

Indellient is a front runner in DevOps services. Learn more at https://www.indellient.com/pipeline

  • Be the first to comment

  • Be the first to like this

Bringing the Chef Habitat Depot On-Premise in the Enterprise

  1. 1. BRINGING THE CHEF HABITAT DEPOT ON-PREMISE IN THE ENTERPRISE
  2. 2. Why Do We Need To Talk About This? Enterprise is complex Need to consider siloes and independent work streams Think about separation of duties
  3. 3. Good News! Chef Habitat Can Help
  4. 4. What I’ll Be Covering Chef Habitat Origins and Channel Patterns Single Depot vs. Multi-Depot Architecture CI/CD and Governance High Availability
  5. 5. Hi, I’m Skyler I’m a Senior DevOps Specialist at Indellient Involved in a number of Chef (Infra, InSpec and Habitat) implementations including one of the largest Chef Habitat ones to date. @skylerto @skylerto skylerl@indellient.com
  6. 6. Chef Habitat Origins And Channel Patterns
  7. 7. A Quick Refresher… Origins are like a workspace Channels are your environments
  8. 8. How do I know which Chef Habitat origins and channels are best for my organization?
  9. 9. AskYourself… How do my application / product teams work? How do we release code? How do we want to work and release code?
  10. 10. Options for Chef Habitat Origins and Channels Org Based Origin and Channels Product Based Origin and Channels
  11. 11. Org Based Origin and Channels Developer 1 Unstable Stable Developer 2 Unstable Stable Developer 3 Unstable Stable My Org Unstable -> Dev QA Staging Stable -> Prod
  12. 12. Org Based Origin and Channels Developer 1 Unstable Stable Developer 2 Unstable Stable Developer 3 Unstable Stable My Org Unstable -> Dev QA Staging Stable -> Prod Great for Standardizing processes Small/Medium enterprise
  13. 13. Product Based Origin and Channels Developer 1 Unstable Stable Developer 2 Unstable Stable Product 1 Unstable -> Dev QA Stable -> Prod Product 2 Unstable - > Dev QA Staging Stable -> Prod My Org Unstable -> Dev QA Staging Stable -> Prod
  14. 14. Product Based Origin and Channels Developer 1 Unstable Stable Developer 2 Unstable Stable Product 1 Unstable -> Dev QA Stable -> Prod Product 2 Unstable - > Dev QA Staging Stable -> Prod My Org Unstable -> Dev QA Staging Stable -> Prod Great for Decentralized teams Diverse channel definitions Large enterprises
  15. 15. The Pros and Cons Company Origins • Promotes standardized release pipelines through the organization • Works well for SME • Can cause bottlenecks since centrally managed Product Origins • Allows teams to work independently without losing site of company standards • Works well for larger, product driven organizations • Adds management overhead to product teams
  16. 16. Single vs. Multi-Depot
  17. 17. Single-Depot Overview
  18. 18. Multi-Depot Overview
  19. 19. Synchronization Service Chef Habitat Depot Synch: https://github.com/Indellient/bldr_package_sync
  20. 20. CI Pipeline Integration and Governance
  21. 21. Multi-Depot With CI Jenkins Habitat Plugin: https://github.com/jenkinsci/habitat-plugin
  22. 22. Multi-Depot With CI And RBAC
  23. 23. Pipeline Governance
  24. 24. High Availability
  25. 25. Service Architecture
  26. 26. Service Infrastructure
  27. 27. HA Multi-Depot With CI And RBAC
  28. 28. Chef Habitat is Flexible
  29. 29. Let’s Sum This Up • Select the correct origin and channel strategy • Ensure that CI pipeline integration and governance is addressed • HA S3 storage is essential for production readiness
  30. 30. Let’s Sum This Up • A multi-depot strategy depends on organizational needs (separation of responsibilities, etc.) • Chef Habitat is ready for the enterprise
  31. 31. Questions? Psst…here are the resources I referenced earlier: Chef Habitat Depot Synch: https://github.com/indellient/bldr_package_sync Jenkins Habitat Plugin: https://github.com/jenkinsci/habitat-plugin info@indellient.com indellient.com/pipeline/chef-services

×