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

Continuous Delivery - Challenges in a Private D...

Continuous Delivery - Challenges in a Private Datacenter

The following presentation was held at Continuous Delivery Meetup (https://www.meetup.com/DC-continuous-delivery/events/233212164/) on 18 Aug 2016.

Alexandru Zbarcea

August 18, 2016
Tweet

More Decks by Alexandru Zbarcea

Other Decks in Programming

Transcript

  1. Continuous Delivery Challenges in a Private Datacenter Alex Zbarcea -

    CD Chief Engineer @SWIFT - Apache Committer ([email protected], in/azbarcea, @azbarcea)
  2. “ organizations which design systems ... are constrained to produce

    designs which are copies of the communication structures of these organizations - M. Conway
  3. test dev devops CC git nexus build (CI) Dev Test

    QA Prod nexus pulp katello env env env env env env env env predictibility automation promotion artifacts CD blueprint . . . . . . . . .
  4. Successful Practices for Continuous Delivery - by Nathen Harvey -

    Manual process - Legacy systems and tools - Organizational silos - Infrequent large release - Regulatory burdens - ‘‘ - Automate - Infrastructure as Code - Increase collaboration - CD of infrastructure and apps. - Compliance at velocity
  5. DEVELOPMENT QUALITY PRODUCTION .docker .git .docker .git .jar .war .npm

    .pip .rpm .tar.gz .wiki .html .md .docker .docker .git containerize everything
  6. rhel tomcat java app Another Distro One package manager -

    automated patches Reuse Isolated app. One hierarchy security Conf. Mngt.
  7. Challenges Development - feature branches - Continuous Integration - Continuous

    Release - Everybody needs to understand the Pipeline
  8. distribution ... the process of making a product or service

    available for use or consumption by a consumer or business user
  9. Summary Challenges - inventory of INs and OUTs - limited

    set of artefact types - artefact warehouse management - containerize everything
  10. Challenges on Versioning and Packaging and Docker Images - Use

    OS (distro) package manager - Enforce semver - know your upstream versions: docker-v1.11.2-1ubuntu2.1 <app>-v<upstream-version><groupId><buildId> - Jail your apps - Use data containers - Use compositions (docker/rancher) - Define your release trust model - individuals - each commit a release
  11. Beaurocracy Challenges - Release - Promotion - Quality assurance (reports)

    - Project management - Deployment plan eliminate non-value processes
  12. Operations Challenges - FAIL is good. Trust the upgrade button

    - complexity gets bigger - generates: lack of trust - difficult to investigate - .git/social becomes a core system - focus is on scaling - deployments as a non-event