Se está descargando tu SlideShare. ×

Chef Compliance & Workflow w/Delivery

•

21 de abr de 2016

• •

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Anuncio

Chef Compliance and Workflow with Delivery

Adopt a proven workflow to go more quickly
from idea to shipped software
High velocity with safety
Reliable and repeatable...

Chef Provides a Proven Approach to DevOps
...
...
...
Targets/Workloads
Collaborative Dev
Chef Insights
Production
Chef Se...

Code Revision
Control
System
Automation
Server
Nodes
Policy
State
Infrastructure as Code

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Submi
t
Chang
e

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sub...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sub...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sec...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sec...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sec...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sec...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sec...

Unified Pipeline Shape
The stages are fixed, and each stage has a fixed set of phases
APPROVE DELIVER
Lint
Syntax
Unit
Sec...

Shared Workflow
Delivery’s pipeline is shared across projects and teams

Chef Provides a Proven Approach to DevOps
...
...
...
Targets/Workloads
Collaborative Dev
Chef Insights
Production
Chef Se...

Delivery Phases
Verify and Build
Build
Acceptance, Union, Rehearsal, Delivered
Provision Deploy
Smoke Functional

Delivery Phases – Example Java Application
• JUnit
Verify and Build
Build
• Lint4J • javac
• Fortify • FindBugs • Maven
• ...

Chef Compliance & Workflow w/Delivery

Siguientes SlideShares

Próximo SlideShare

Devops journey chefpopup-2016.04.26-v2

Devops journey chefpopup-2016.04.26-v2

Cargando en…3

×

Eche un vistazo a continuación

Role of Pipelines in Continuous Delivery

Compliance Automation with Inspec Part 2

Nike popup compliance workshop

Azure handsonlab

Infrastructure and Compliance Delight with Chef Automate

London Community Summit 2016 - Fresh New Chef Stuff

Compliance as Code

DevOpsDays Singapore - Continuous Auditing with Compliance as Code

Chef Compliance & Workflow w/Delivery

21 de abr de 2016

• •

Descargar para leer sin conexión

Presentation for Optum-Chef DevOps Transformation event held in Minneapolis on April 21st.

Presentation for Optum-Chef DevOps Transformation event held in Minneapolis on April 21st.

Licencia: CC Attribution-ShareAlike License

Más Contenido Relacionado

Role of Pipelines in Continuous Delivery

Compliance Automation with Inspec Part 2

Nike popup compliance workshop

Azure handsonlab

Infrastructure and Compliance Delight with Chef Automate

London Community Summit 2016 - Fresh New Chef Stuff

Compliance as Code

DevOpsDays Singapore - Continuous Auditing with Compliance as Code

Cooking Up Windows with Chef Automate

London Community Summit - Chef at SkyBet

Chef compliance - Intermediate Training

Sarah Hynes Cheney

Effective Testing with Ansible and InSpec

Intermediate/Compliance training Guide

Bay Area Chef Meetup February

Automating Compliance with InSpec - AWS North Sydney

Automating AWS Compliance with InSpec

Using Habitat to Unify Dev to CI to Production - Configmgmt Camp Feb/2018 Gent

Salim Afiune Maya

Delivery pipelines at Symphony Talent - Present and Future

Compliance Automation with Inspec Part 3

Role of Pipelines in Continuous Delivery

27 diapositivas

Compliance Automation with Inspec Part 2

52 diapositivas

Nike popup compliance workshop

136 diapositivas

Azure handsonlab

56 diapositivas

Infrastructure and Compliance Delight with Chef Automate

11 diapositivas

London Community Summit 2016 - Fresh New Chef Stuff

39 diapositivas

Etsy chef-workflow

Daniel Schauenberg

“Debugging is on the table” Dr. House pergunta a um Sysadmin

Leonardo Martins

Training Opscode Chef

Leonardo Martins

Chef - Administration for programmers

Deploying infrastructure with Opscode Chef

Eduardo Scarpellini

State of Puppet 2013 - Puppet Camp DC

CPU Performance Enhancements

Introduction to chef

Damith Kothalawala

Introduction to Continuous Integration with Jenkins

OpenStack Deployment with Chef Workshop

Infrastructure Automation with Chef

Git Presentation

Prem Aseem Jain

Basic Git Intro

Puppet for dummies - ZendCon 2011 Edition

Joshua Thijssen

Chef Fundamentals Training Series Module 1: Overview of Chef

Chef Software, Inc.

Overview of Chef - Fundamentals Webinar Series Part 1

Introduction to Chef: Automate Your Infrastructure by Modeling It In Code

Chef for DevOps - an Introduction

Etsy chef-workflow

Daniel Schauenberg

15 diapositivas

“Debugging is on the table” Dr. House pergunta a um Sysadmin

Leonardo Martins

39 diapositivas

Training Opscode Chef

Leonardo Martins

32 diapositivas

Chef - Administration for programmers

27 diapositivas

Deploying infrastructure with Opscode Chef

68 diapositivas

Eduardo Scarpellini

20 diapositivas

Strong practices for rails applications continuous delivery

IP Expo Nordic: Successful Practices for Continuous Delivery

A Bit of Everything Chef

AWS Summit Auckland - Application Delivery Patterns for Developers

Amazon Web Services

Sistemas operacionais 12

Building Evolvable Infrastructure

Webinar: “Continuous Delivery: il tuo primo passo verso il DevOps”

Emerasoft, solutions to collaborate

Real World Git Workflows - EclipseCon Europe 2013

Nicola Paolucci

Setting up Continuous Delivery Culture for a Large Scale Mobile App

Continuous delivery xebia

Continuous Delivery in the Enterprise

IBM UrbanCode Products

Continuous Integration & Delivery

DevOps with Microsoft Stack

Continous integration and delivery for single page applications

Successful Practices for Continuous Delivery CodeCPH

MesosCon_Asia_2016_DevOps_at_GSShop

Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion

Product Marketing Services

Dennis Benkert - The Dog Ate My Deployment - Symfony Usergroup Berlin March ...

Continuous Delivery with a PaaS Application

CI CD Pipeline Using Jenkins | Continuous Integration and Deployment | DevOps...

Strong practices for rails applications continuous delivery

51 diapositivas

IP Expo Nordic: Successful Practices for Continuous Delivery

50 diapositivas

A Bit of Everything Chef

74 diapositivas

AWS Summit Auckland - Application Delivery Patterns for Developers

Amazon Web Services

42 diapositivas

Sistemas operacionais 12

68 diapositivas

Building Evolvable Infrastructure

55 diapositivas

Habitat Managed Chef

Automation, Audits, and Apps Tour

Automation, Audits, and Apps Tour

Compliance Automation Workshop

London Community Summit 2016 - Adopting Chef Compliance

Learning from Configuration Management

London Community Summit - From Contribution to Authorship

London Community Summit 2016 - Chef Automate

London Community Summit 2016 - Community Update

London Community Summit 2016 - Habitat

Compliance Automation with Inspec Part 1

Nike pop up habitat

The caseforawesome

Netflix's Could Migration

Alaska Airlines DevOps Journey

And The Slow Suffer What They Must

Visualizing your journey with chef

The New IT Game

How to Accelerate Agile, Lean and DevOps Adoption Across Your Organization

Our DevOps Journey - An Exercise in Cultural Change

Habitat Managed Chef

34 diapositivas

Automation, Audits, and Apps Tour

142 diapositivas

Automation, Audits, and Apps Tour

151 diapositivas

Compliance Automation Workshop

106 diapositivas

London Community Summit 2016 - Adopting Chef Compliance

22 diapositivas

Learning from Configuration Management

23 diapositivas

FundamentalsofComputerStudies.pdf

NguynThanhTriu2

Javascript Methods and events

Introduction to CloudHub 2.0

NeerajKumar1965

Reaktive Programmierung mit den Reactive Extensions (Rx)

NETUserGroupBern

NETUserGroupBern

Paralel Algorithms.pptx

EXCEL 2016 FOR MAC QUICK START GUIDE.PDF

NMR-diagnosis.pptx

Tendersniper profile dated October 2022.pdf

ECM for Dummy 2021.pptx

ChusakHanucharoenkul

Streamline Your Validation Process with GoVal - Features and Benefits

SUNDAR RAMAN SEKAR

SravanKosaraju1

MDM-SGG_Business_User_Guide_v2_2_0_2.pptx

AdityaDas899782

AnshuKUMARI534030

Promovidz V2 Platinum

SAP MM Purchasing .pptx

.NETworking Workshop Design Thinking

NETUserGroupBern

DerbyDev_ModMonolith_290323.pptx

AaronWhite801549

Applicant Tracking software.pdf

What the hell is PowerShell?

NETUserGroupBern

FundamentalsofComputerStudies.pdf

NguynThanhTriu2

60 diapositivas

Javascript Methods and events

12 diapositivas

Introduction to CloudHub 2.0

NeerajKumar1965

19 diapositivas

Reaktive Programmierung mit den Reactive Extensions (Rx)

NETUserGroupBern

46 diapositivas

NETUserGroupBern

75 diapositivas

Paralel Algorithms.pptx

12 diapositivas

Chef Compliance & Workflow w/Delivery

1. Chef Compliance and Workflow with Delivery
2. Adopt a proven workflow to go more quickly from idea to shipped software High velocity with safety Reliable and repeatable workflow Visibility of who did what, and when
3. Chef Provides a Proven Approach to DevOps ... ... ... Targets/Workloads Collaborative Dev Chef Insights Production Chef Server Chef Server Chef Supermarket Assessment Chef Compliance Search Audit Discover Deploy Chef Delivery Local Dev Model Build Test Chef DK Chef Client & Cookbooks
4. Code Revision Control System Automation Server Nodes Policy State Infrastructure as Code
5. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Submi t Chang e
6. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Submi t Chang e
7. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Submi t Chang e Does this code change look good?
8. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Security Quality Publish Lint Syntax Unit Submi t Chang e Does this code change look good?
9. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Security Quality Publish Lint Syntax Unit Provision Deploy Smoke Functional Submi t Chang e Does this code change look good?
10. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Security Quality Publish Lint Syntax Unit Provision Deploy Smoke Functional Submi t Chang e Does this code change look good? Do we want to ship this?
11. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Security Quality Publish Lint Syntax Unit Provision Deploy Smoke Functional Provision Deploy Smoke Functiona l Submi t Chang e Does this code change look good? Do we want to ship this?
12. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Security Quality Publish Lint Syntax Unit Provision Deploy Smoke Functional Provision Deploy Smoke Functiona l Provision Deploy Smoke Functional Submi t Chang e Does this code change look good? Do we want to ship this?
13. Unified Pipeline Shape The stages are fixed, and each stage has a fixed set of phases APPROVE DELIVER Lint Syntax Unit Security Quality Publish Lint Syntax Unit Provision Deploy Smoke Functional Provision Deploy Smoke Functiona l Provision Deploy Smoke Functional Provision Deploy Smoke Functional Submi t Chang e Does this code change look good? Do we want to ship this?
14. Shared Workflow Delivery’s pipeline is shared across projects and teams
15. Chef Provides a Proven Approach to DevOps ... ... ... Targets/Workloads Collaborative Dev Chef Insights Production Chef Server Chef Server Chef Supermarket Assessment Chef Compliance Search Audit Discover Deploy Chef Delivery Local Dev Model Build Test Chef DK Chef Client & Cookbooks
16. Delivery Phases Verify and Build Build Acceptance, Union, Rehearsal, Delivered Provision Deploy Smoke Functional
17. Delivery Phases – Example Java Application • JUnit Verify and Build Build • Lint4J • javac • Fortify • FindBugs • Maven • Artifactory Acceptance, Union, Rehearsal, Delivered • EC2 • Chef Provisioning Provision Deploy • Load jar in Tomcat • Curl $URL; check for 200 OK Smoke Functional • Selenium • Cucumber • Chef InSpec

Notas del editor

Chef Delivery accelerates adoption of Continuous Delivery and reinforces DevOps best practices

Chef has identified a proven workflow for managing change, validated with enterprise and big web customers.

Every business is a software business. To stay competitive, teams need a reliable and safe way to deliver value to customers as quickly as the business demands.
Delivery provides an automation solution that spans the entire lifecycle of a change, from local dev on a workstation through deployment to production.
Chef’s workflow has been developed based on industry best practices around DevOps, and Delivery promotes adoption of this proven workflow.

How do you reduce risk when continuously deploying change?
Test for quality and compliance as part of the workflow
(add flow elements)
Stakeholders--dev, ops, and others– need a collaborative workflow
Applications, runtimes and infrastructure must be deployed together
- Write your recipes and test, storing them in source control
- When ready to deploy, you push your cookbooks to the Chef Server which knows current state ("what is currently deployed") vs. desired state ("what SHOULD be deployed")
- Chef-client (small agent on your nodes) checks in with Chef Server to receive its instructions, and the client becomes compliant with that policy
- Chef-client runs on a schedule of your choosing, avoids configuration drift

Heavy-lifting of dependency solving, etc. is done in the chef-client, making it incredibly easy to scale thousands and thousands of nodes against a single chef server.
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
We’ve taken a different approach compared to other solutions in that in Delivery the pipeline has a fixed shape.
Pipelines consist of six fixed stages, each of which is comprised of a fixed set of phases.
It's not that we're trying to be inflexible; change the conversation. The common pipeline is prescriptive because it's based on our collective experience.
The flexibility resides in the way you define what happens in each phase, described in the next two slides.
An example here is you can include compliance in your workflow via the Functional phase to confirm that your organization’s security rules are part of testing a change
Part of the reason this is the right approach is that arguing over the pipeline shape can become a huge delay to adopting CD.
Custom pipelines are more difficult to maintain and keep stable over time.

Delivery includes explicit review and approval gates
This allows you to manage change in a way that is compliant with your business or regulatory requirements
Delivery behaves no differently for "infrastructure" code or "application" code. One of our core principles is that code is code, and Union is where all the pieces meet.
- To weave compliance in here, you can talk about using the pipeline to quickly delivery patches needed in an emergency remediation scenario (vulnerability response)
An update for compliance is likely something that should be managed via a cookbook, such as OpenSSL patch to remediate a vulnerability

Each project has its own acceptance pipeline.

The system enforces a single change-at-a-time moving through each of
Union, Rehearsal, and Delivered.

This keeps things stable. If something breaks, you can identify the
change that introduced the breakage, and you know who to pull into
a conversation about how to fix things.

NOTE: the psychology of what are you making a change to? The WHOLE THING. It's a system. Not a project.

This is a good place to talk about why the shared pipeline model promotes safety:
Delivery promotes a “small batch” model, shipping one thing at a time to ensure discovery of integration problems before a change reaches production.
Union is the place where all the pieces meet within a dependency set to ensure the system as a whole is safe. If you are managing 4 projects through your Delivery pipeline and the first 3 have dependencies within each other, we can think of those as a conceptual dependency set within Union. If the fourth project that is not part of that dependency set has a change that needs to go through, it will not get “stuck” behind changes related to the first 3 projects. In this way it is possible for changes to move through the shared pipeline in parallel, where there are not overlaps in their respective dependencies.
Being able to move fast itself adds safety: remediation of defects, vulnerabilities etc. Systems that are easy to fix are safer.

Q. Why did we not choose "QA", "staging" and "production" as the names instead of "union", "rehearsal", and "delivered"? And can I customize the names?
A. The semantics of those words are overloaded and different in each business, so we wanted to start from a clean slate. The names cannot be changed.
(add flow elements)
Stakeholders--dev, ops, and others– need a collaborative workflow
Applications, runtimes and infrastructure must be deployed together
Delivery can work with your existing tool chain; anything that can be executed via Chef cookbook
Each of the boxes corresponds to a recipe in the build cookbook
You don’t need to “start from scratch” or throw away tools that are working for you today
Delivery’s phases are customizable to work with your existing tool chain
This illustrates an example tool set for a Java application