Treating Deployments as Code with Puppet and the Atlassian Toolsuite Puppet Camp, Geneva

Size: px

Start display at page:

Download "Treating Deployments as Code with Puppet and the Atlassian Toolsuite Puppet Camp, Geneva"

Erica Carroll
6 years ago
Views:

1 Treating Deployments as Code with Puppet and the Atlassian Toolsuite Christoph Leithner

2 Who is celix? Puppet Labs Partner Atlassian Expert IT Service Management (ITSM) Continuous Deployment und DevOps Agile Development

3 Deployments as code Puppet Manifests Nearly all Puppet Manifests belong in Modules Module = Directory with a defined structre Module = Manifests + Files + Templates + Plugins Module should contain Tests and Examples

4 Puppet Forge Repository of Modules contributed by users Find, install, upgrade and uninstall Modules puppet module subcommand (since ) Manage module dependencies Modules contain related code and should be as self contained as possible

5 Working with Puppet Modules Using Puppet Forge Modules Developing your own Modules Managing Dependencies Tracking Changes

6 Puppet Environments During development and testing multiple versions of the modules exist Environments enable the use of these different sets of Modules Different modulepath for each environment Common names for environments: production, testing, development or trunk

7 Puppet Environments Modulepath has to be defined: Own [config block] in puppet.conf for each environment Definition referencing the $environment variable Dynamic Environments

8 Version Control Strategies Version the environment or modules folder Check out only tags to the production environment Develop modules in trunk environment or Create branches for development and testing environments see Pro Puppet Book Chapter 3

9 Version Control Strategies Version each module in a separate repo and use a superproject to point to the modules. (Git submodules and Mercurial superproject) see by P. Debois New: Use the puppet module subcommand to manage the Modules in a directory under version control

10 Multiple Module Directory Example own_dev forge forge_dev modules modules modules Version modules directory for own Modules (own_dev) Use Superproject with submodules for Puppet Forge Modules (forge) Version individual Modules for own Puppet Forge Development (forge_dev)

11 Developing a Module Code the feature Check the syntax Check code against style guidelines Run Tests: cucumber-puppet, rspec-puppet see by P. Debois Deploy to environment on Puppet Master Apply catalog to dedicated machines

12 Geppetto Puppet IDE Based on Eclipse Supports Puppet Project Types Version Control Integration (Git, SVN) Eclipse Task Management (Mylyn) Adds Puppet Support to your existing Eclipse Installation More info:

13 Atlassian Bamboo Manage your Puppet Environments with Bamboo Build plan for every environment Provides A Task for everything (Git, puppet subcommands, mcollective, rspec-puppet, puppetlint, rake, git-rake, Dashboard Rake API,...) Automate Development and Release process No longer use the shell on your Puppet Master

Feature Environments (Branches) Effortlessly add new plans for

14 Atlassian Bamboo Stay in You IDE Atlassian IDE Connector for Eclipse Start builds from your IDE Automatic Plan Branching Feature Environments (Branches) Effortlessly add new plans for branches to your build system Automatic or at the push of a button

15 Atlassian Bamboo Automatic Branch Merging Two Strategies: The "Gatekeeper : Merges changes from your branch into the main link and builds the result The "Build Updater : Merges the main line into the branch and build the combined code. Optional commit after a successful build

One-Click Release Process Initiate your release

16 Atlassian Bamboo Manual Stages Automate what you can, one step at a time Pause the plan at manual stages One-Click Release Process Initiate your release process to the production environment from JIRA with one click

17 Manage Your Application Life Cycle with the Atlassian Toolsuite

18 Atlassian JIRA Define Your Own Processes Different Process for each Issue Type Visualize Your Workflow Visual Workflow Editor Users can view current status of the workflow

agile practices implementing your Modules Integrate

19 Atlassian JIRA Agile Project Planning Atlassian GreenHopper AddOn Scrum + Kanban = ScrumBan Use agile practices implementing your Modules Integrate with CI Atlassian Bamboo Build Notifications Release Management

20 Atlassian GreenHopper Measure Cycle Time Time an Issue spends in progress Analyze Trends Cumulative Flow Diagram See where work is building up

21 Atlassian JIRA Link Issues to Source Code Atlassian Fisheye Use Issue IDs in Commit Messages Encourage Code Review Atlassian Crucible Ensure a second set of eyes looks over every line of code

22 Atlassian Fisheye Real Time Dev Activity Identify source that caused builds to fail Development Forensics How did a change get introduced into the codebase Diagnose and solve problems

23 Atlassian Crucible Issues to Reviews Browse Code Reviews associated with an Issue or Project One Click Review creation from JIRA Reviews to Issues View Issues related to Code reviews Create JIRA Issue from Cucible review comments

24 Atlassian Crucible Code Discussions Reviewing code is learning code Share best Practices No Meetings Required Workflow based Review Review Changesets Review Snippets

26 Summary Your Puppet Modules are code, just like the webapp you are deploying: Use the Puppet IDE Geppetto Use the Atlassian Bamboo Buildplans to manage your Puppet Environments Manage your agile Module development with JIRA and GreenHopper Use Code reviews with Fisheye and Crucible

27 Thank you!

JIRA Studio Use Cases and Tutorial basis

JIRA Studio Use Cases and Tutorial basis Analysis of usefulness of JIRA Studio Eclipse tool-chain Tolga Tuncbilek, Elisa Kallio, Shiyuan Wang, Viktor Porvaznik Table of Contents 1 Introduction... 3 2 Data