ContinuousDelivery

Challenges in a Private Datacenter

Alex Zbarcea - CD Chief Engineer @SWIFT - Apache Committer(alexz@apache.org, in/azbarcea, @azbarcea)

ABOUT THIS PRESENTATION

ContinuousDelivery

“organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations - M. Conway

test

dev

devops

CC

git

nexus

build (CI) Dev Test QA Prod

nexuspulp

katello

env

env

env

env

env

env

env

env

predictibilityautomation

promotion

artifacts

CD blueprint

..

.

.

.

....

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

Business is a System

inputs outputs

feedback

Business is a System

Empower businessto make decisionsit’s about API

DEVELOPMENT QUALITY PRODUCTION

DEVELOPMENT QUALITY PRODUCTION

DEVELOPMENT QUALITY PRODUCTION

LEGACYLEGACY

DEVELOPMENT QUALITY PRODUCTION

.docker

.git

.docker

.git

.jar

.war

.npm

.pip

.rpm

.tar.gz

.wiki

.html

.md

.docker

.docker

.git

containerize everything

rhel

tomcat

java

app

Another Distro

One package manager- automated patches

Reuse

Isolated app.

One hierarchy

security

Conf. Mngt.

Demo

development... software development and release processes

Challenges Development

- feature branches- Continuous Integration- Continuous Release- Everybody needs to

understand the Pipeline

distribution... the process of making a product or service available for use or consumption by a consumer or business user

Summary Challenges

- inventory of INs and OUTs- limited set of artefact types- artefact warehouse management- containerize everything

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

beaurocracy… the administrative system governing any large institution

Generated

Versioned

Deliverable

Shared

Searchable

{ }…

Starts and ends with Documentation and Reports

Beaurocracy Challenges

- Release- Promotion- Quality assurance (reports)- Project management- Deployment plan

eliminate non-value processes

operations… the administrative system governing any large institution

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

Thank you Continuous Delivery meetup

apifocal