Upgrade to Pro — share decks privately, control downloads, hide ads and more …

DevOps Journey for Fox | Matt Chung

90d05761d7a5206db9ac0186c20d0e73?s=47 Matt Chung
February 11, 2015

DevOps Journey for Fox | Matt Chung

FOX Network Engineering and Operations Technical operations transition to Dev/Ops model.

90d05761d7a5206db9ac0186c20d0e73?s=128

Matt Chung

February 11, 2015
Tweet

More Decks by Matt Chung

Other Decks in Technology

Transcript

  1. DevOps Journey for Fox

  2. Agenda 4 Intro 4 Where we were last year 4

    Where do we even begin ? 4 Questions ?
  3. NEO TechOps Responsibilities 4 Infrastructure Hosting | Rackspace 4 Code

    deployment 4 CDN Management | Akamai 4 Culture of sharing
  4. Code deployment and issues 4 Works in QA and STG,

    but not Prod ? 4 Environment variance 4 Different processes for each website? 4 How do we knowledge share?
  5. Removing environment variance 1. Rebuild and automate build of all

    environments 2. Institutionalize configuration management (Ansible) | Infrastructure as codeEnvironment Specific variableng 4s 3. Weekly rotation of
  6. Building automation Keeping Deployment pipeline simple 1. Git + Bitbucket

    - Revision Control 2. Jenkins - build artifact 3. Rackspace Cloud Files - Artifact Repository 4. Ansible - deploy artifact 5. Jenkins UI - Deploy application
  7. Environment settings 1. Git + Bitbucket - Revision Control 2.

    Jenkins - build artifact (built only once) 3. Rackspace Cloud Files- Artifact Repository 4. Ansible - deploy artifact
  8. None
  9. Code review process 1. Create branch 2. Push to remote

    branch 3. Create pull request 4. Team member reviews, accepts, and merges request
  10. Where does docker come into play? 1. How do we

    manage different libraries, programming language versions? 2. Explosion of jenkins build out 3. Docker is a temporary environment for building artifacts 4. Collapsing QA | STAGING environments
  11. Questions ?