DEVOPS INNOVATION HOW OPEN SOURCE IS DRIVING

HOW OPEN SOURCE IS DRIVINGDEVOPS INNOVATIONGordon Haff @ghaffWilliam Henry @ipbabbleCloud & DevOps Product Strategy, Red Hat17 August 2015

What is DevOps?Source: DevOps Days DC 2015 word cloud from Open Spaces.

DevOps applies open sourceprinciples and practices with.

TOOLS drawingfrom innovativedevelopmentcommunitiesDEVOPS:THE WHAT & THE WHY

A typical DevOps workflow

Tools for operations*/infrastuctureContainerized infrastructureOrchestrationPolicy-based governanceConfiguration managementAutomationPackagingUpdates* But they bleed into developer land!

Infrastructures evolve for cloud-nativeMonolithic app containerScale up by adding hardware resourcesLimited scale out through clusteringAPPDistributed, networked, containerized servicesScale out by orchestrating servicesFaster iteration and releaseMore robustAPPRHELSINGLE-HOST APPSMULTI-HOST APPS

Infrastructure layer:A Cloud Platform for Microservice Cloud AppsProvision apps fromservice catalogOPS MANAGEMENT ANDSERVICE CATALOG(e.g. RED HAT CLOUDFORMS)Red HatCloudFormsMonitoringDockerImageRed HatCloudFormsOrchestrationDockerImageRHEL ATOMICHOST GUESTProvide dynamic, programmableinfrastructureRed HatSatelliteContentDockerImageRed HatJBossAMQDockerImageApp DBDockerImageRHEL ATOMICHOST GUESTRED HAT ENTERPRISE LINUX OPENSTACK PLATFORMCOMPUTE STORAGE NETWORK(e.g. OPENSTACK, CEPH, OPEN DAYLIGHT)Red HatJBossBRMSDockerImagePaaS(e.g. OPENSHIFT)SERVICE SCHEDULER/ORCHESTRATOR(e.g. KUBERNETES)Orchestrate and place appsRun composed microservicesin containersCONTENT, ENTITLEMENT,AND LIFECYCLE(e.g. RED HAT SATELLITE)

Tools for developer* workflowsCollaborationCI/CDIssue trackingSource code controlCode reviewPlatform-as-a-Service* But they bleed into ops land!

CI/CD Pipeline ToolsetCI/CD Workflow UI

Automation ofPROCESSfrom developmentDEVOPS:through ongoingTHEWHAT&THEWHYoperations

Automation as a CI/CD ProcessCDCILocal poDeploy

Collaboration Kanban - Trello Docs - etherpad, google docs Pastebin - fpaste Ticketing - Jira, RedmineLocalTest - Eclipse, Emacs, easeRepoDeploy

Asset Management Code/Config - git, subversion Docs - git, Google docsCI Policy/rules - ManageIQ, KatelloCDLocal poDeploy

Continuous Integration Jenkins Travis CI BuildBotCDCILocal poDeploy

Code/Image Build Compilers Code Build - Ant, Maven,CIBuildbot, Cruisecontrol, etc.CDLocal poDeploy

Testing SonarQube Cucumber JUnitCI ArquillianLocal RepoDeploy

Review/Approve Gerrit, Github Ticket UpdateCI Jira, Redmine CDLocal poDeploy

Packaging RPM Images Docker, OCICDCI Applications/Services Kubernetes, AtomicappLocal poDeploy

CILocal ldTest3rdPartyReview/ApprBuildRepoAnisible,Puppet, iverReleaseRepoDeploy

Local TestPushCommitmyRepo Tomcat Wildfly MongoDB MySQL Vert.x Node.js Docker ActiveMQ ProjectFeedHenry Build RepoOpenstack prBuildRepoDeliverReleaseRepoDeploy

Automation Across EnvironmentsContinuous Integration /Continuous DeploymentEventssrc repoDev./BuildQAAssetsImage & Package &Metadata RepositoryProductionin OHC

Portable ApplicationAtomicApp

Automation Across EnvironmentsContinuous Integration /Continuous DeploymentEventssrc repoDev./BuildQAAssetsImage & Package &Metadata RepositoryProductionin OHC

PaaS provides an integration point

CULTUREof collaborationDEVOPS:valuing opennessand transparency THE WHAT & THE WHY

Our culture is too difficult!Really?Consider post war 4/

Impose a culture of:EmpathyTrustLearningCooperationResponsibility?

Issues with just “changing culture” Lack of agreed-to model of what “right” culture looks like Different organizations require different behaviors Culture change is difficult to measure and quantify Culture is very hard to impose Culture is an output, not an input

Culture f (l, o, i, t, )where:l leadershipo organizationi incentivest trust many other thingsOpen source offers guidance

Leadership and vision but no oneorganizational structureMultiple models work butcharacteristics need to fitthe project, participants,and vision

Solve specific problemsOpen source projects often begunbecause of an individual’s interest or issueDevOps projects (often) benefit by tacklinglow surface area problem cases(But, like open source, DevOps canbecome the default)

TransparencyWho made changes?When and why did theymake them?What’s the state of theproject?What’s the state of thesystem?It’s the expectation for bothopen source and DevOps

Rich communication flows matterOpen source projects havebeen forced to deal withdistributed (cross-timezone)teamsTools vary by teamsVideo getting betterF2F time still a big plus

Don’t fear failureOpen source innovation highlydriven by experimentationOne of the points of DevOps isto enable better experimentationIf it doesn’t work, move on(But fast failures)

Incentives matterOpen source projects (tend to)reward based on merit andcontributionIncentives in DevOps organization(advancement, money, recognition)need to reward trust and cooperationIndividual has control over their ownsuccess

Open source is driving DevOpsBut it’s more than the code!

CreditsTools: Dorli Photography, cc/flickr obots: davidgariepy, cc/flickr 427/Kids programming: Esti Alvarez cc licenseDev: Nelson Pavlosky/flickr under CC ps: Leonardo Rizzi/flickr under CC nbows and Unicorns: inbows-3-151273843Join hands: /Thanks to J.P.Morgenthal for some of his thoughts about culture change. See also orgtrumpcultureinentdevopsGovernance models: ransparent code: iStockPhotoLinux Collaboration Summit: Linux FoundationWipeout: 192No: Wikimedia

Thank you!Questions?

DEVOPS INNOVATION Gordon Haff @ghaff William Henry @ipbabble Cloud & DevOps Product Strategy, Red Hat 17 August 2015. What is DevOps? Source: DevOps Days DC 2015 word cloud from Open Spaces. DevOps applies open source principles and practices with. DEVOPS: THE WHAT & THE WHY TOOLS drawing . Linux Collaboration Summit: Linux Foundation .