Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Going DevOps with BMC
Search
Niek Bartholomeus
June 03, 2015
Technology
0
190
Going DevOps with BMC
Using DevOps to improve the release process of big enterprises
Niek Bartholomeus
June 03, 2015
Tweet
Share
More Decks by Niek Bartholomeus
See All by Niek Bartholomeus
openthebox.be - smart publications
niekbartho
0
160
openthebox.be
niekbartho
1
2.5k
From idea to production with NLP, Scala and Spark
niekbartho
3
470
Orchestration in meatspace
niekbartho
4
2k
Self-organization vs. global optimization - a comparison between traditional and modern organizations
niekbartho
2
450
DevOps for Dinosaurs
niekbartho
12
3k
Other Decks in Technology
See All in Technology
ClaudeCodeにキレない技術
gtnao
1
860
Bill One 開発エンジニア 紹介資料
sansan33
PRO
4
13k
サイバーエージェントグループのSRE10年の歩みとAI時代の生存戦略
shotatsuge
4
1k
PHPからはじめるコンピュータアーキテクチャ / From Scripts to Silicon: A Journey Through the Layers of Computing
tomzoh
2
120
三視点LLMによる複数観点レビュー
mhlyc
0
230
「Chatwork」のEKS環境を支えるhelmfileを使用したマニフェスト管理術
hanayo04
1
400
60以上のプロダクトを持つ組織における開発者体験向上への取り組み - チームAPIとBackstageで構築する組織の可視化基盤 - / sre next 2025 Efforts to Improve Developer Experience in an Organization with Over 60 Products
vtryo
3
1.9k
IPA&AWSダブル全冠が明かす、人生を変えた勉強法のすべて
iwamot
PRO
2
230
SRE不在の開発チームが障害対応と 向き合った100日間 / 100 days dealing with issues without SREs
shin1988
2
2k
助けて! XからWaylandに移行しないと新しいGNOMEが使えなくなっちゃう 2025-07-12
nobutomurata
2
200
[SRE NEXT 2025] すみずみまで暖かく照らすあなたの太陽でありたい
carnappopper
2
470
ポストコロナ時代の SaaS におけるコスト削減の意義
izzii
1
470
Featured
See All Featured
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
Embracing the Ebb and Flow
colly
86
4.8k
Why You Should Never Use an ORM
jnunemaker
PRO
58
9.5k
Designing for humans not robots
tammielis
253
25k
Optimizing for Happiness
mojombo
379
70k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
8
700
Large-scale JavaScript Application Architecture
addyosmani
512
110k
KATA
mclloyd
30
14k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
181
54k
[RailsConf 2023] Rails as a piece of cake
palkan
55
5.7k
StorybookのUI Testing Handbookを読んだ
zakiyama
30
5.9k
Transcript
1"
2"
3"
4"
5"
6"
This"is"what"a"typical"enterprise"applica6on"looks"like:"lots"of"technologies"with" interdependencies."Also"dependencies"on"the"infra"layers"and"on"technical"services." And"a"lot"of"documenta6on"to"describe"all"of"it." Development"and"produc6on"support"of"such"applica6ons"is"quite"complex"" 7"
we"have"many"teams"to"develop,"maintain"and"support"all"of"these"technologies."" In"order"to"successfully"deliver"your"applica6on"to"the"end"users"it"has"to"pass"all"of" these"hands." " In"tradi6onal"enterprises"these"teams"are"typically"split"up"by"technology,"by" specialty."Each"team"typically"has"its"own"liJle"process"to"accomplish"the"work"and" may"have"its"own""pocket""of"tooling"and"automa6on."But"the"teams"have"very"liJle" knowledge"of"what"the"other"teams"are"doing"and"the"handMoffs"of"the"work"between" the"teams"is"very"ar6sanal,"using"word"templates,"or"6cke6ng"systems"with"long" queues"and"wai6ng"6me"and"lots"of"confusions"and"misunderstandings."
" We"can"summarize"in"saying"that"the"work"is"op6mized"locally:"each"team"will"use"the" process"and"the"tooling"that"is"op6mized"for"THEIR"needs." " In"a"stable,"mature"domain"with"high"repe66on"of"work"and"rela6vely"liJle"handMoffs" between"the"teams"this"may"lead"to"a"reduc6on"of"the"cost"of"delivering"the"service" or"product." " In"soSware"development"on"the"other"hand,"its"hard"to"predict"things"upfront." Instead"the"specialists"need"to"work"closely"together"to"make"sure"the"different" technologies"work"nicely"together"in"the"final"product." 8"
9"
From"isolated"islands"of"understanding,"the""us"against"them""feeling" 10"
To"shared"goals,"empathy,"doing"an"effort"to"understand"each"other's"problems," finding"the"best"solu6on"overall" " Culture"is"very"specific"to"the"individual"organiza6on"so"the"solu6on"is"also"very" specific"to"the"company:"you're"on"your"own"here." " 11"
We"have"to"op6mize"globally,"focusing"on"the"speed"of"delivering"new"features"into" produc6on."This"will"increase"the"feedback"loop"between"idea"and"user"and"will"bring" beJer"features"in"the"long"run." " We"should"make"sure"that"everyone"understands"this"high"level"process"well"and"that" the"team's"internal"processes"don't"conflict"with"this"high"level"process" 12"
Each"team"prefers"its"own"tool."The"team"will"manage"the"informa6on"that"they"own" with"this"tool."But"in"order"to"do"a"good"job,"they"also"need"informa6on"that"is" managed"by"other"teams,"to"get"a"beJer"visibility"of"the"surrounding"context."E.g."the" release"managers"may"be"interested"in"the"features"that"the"developers"are"working" on,"the"developers"want"to"know"the"coming"releases,"or"which"version"of"their"app"is" deployed"in"which"environment,"etc." " Therefore"it"is"important"to"integrate"the"different"tools,"so"that"each"team"can"see"a" complete"view"of"their"reality,"reliably"and"realM6me." 13"
14"
Let"us"have"a"look"at"one"of"the"main"use"cases"where"dev"and"ops"teams"are" involved:"the"release"of"applica6on"into"produc6on."" " Other"use"cases:"environment"provisioning,"changing"the"infrastructure"(eg"add"a" new"messaging"queue),"produc6on"troubleshoo6ng" 15"
16"
17"
18"
19"
BRPM"is"well"suited"here"to"help"with"the"global"op6miza6on"because"it"sits"right"in" the"middle"of"the"(release)"universe." " BRPM"helps"out"in:" M"Process:"release"plans,"deployment"requests,"visibility"on"environment" configura6ons"(which"version"of"which"component"in"which"environment),"..." M"Tooling"integra6on:"JIRA,"jenkins,"soSware"repo,"test"automa6on,"Bladelogic,"..." " It's"also"a"tool"itself"for"the"release"management"team"(and"environment" management"team)."BRPM"captures"the"info"that"is"managed"in"each"separate"tool"
and"integrates"them"with"its"own"info"to"facilitate"the"work"of"the"users." " 20"
Of"course"the"demo"only"shows"a"small"improvement,"from"a"locally"op6mized" manual"release"process"to"a"well"aligned"endMtoMend"process."This"is"not"the"end"of" the"story,"but"rather"the"first"step"in"a"con6nuous"journey"of"improvement"towards" an"agile,"CD,"autonomous,"..."context." " At"one"point"the"organiza6on"structure"will"have"to"be"adapted"to"further"increase" the"speed"of"delivery"(~"<"1"week)."This"is"a"highly"risky"undertaking"and"having"the" exis6ng"processes"under"control"will"help"reduce"the"risk"considerably." " For"new"apps/teams"we"can"just"start"at"the"agile,"autonomous"side,"but"for"exis6ng"
apps"we"should"take"it"one"step"at"a"6me." 21"
22"
BRPM"is"a"collabora6on"tool,"focused"on"improving"the"communica6on"between" humans"as"well"as"with"tooling"and"automa6on" Humans"can"execute"steps" OnMthe–fly"modifica6on"of"running"requests" This"allows"BRPM"to"capture"processes"that"are"s6ll"very"manual"and"error"prone"and" gradually"move"to"more"maturity"in"terms"of"process"and"tooling"integra6on" " These"features"allow"BRPM"to"support"the"scenarios"from"the"leS"side"of"the" industrializa6on"arrow"(manual"work"etc)" "
" 23"
In"addi6on"to"the"automa6on"scripts"BRPM"has"a"complete"REST"API"and"a"messaging" system"that"supports"all"possible"events."This"allows"it"to"be"easily"integrated"in"both" direc6ons"with"other"tools" " Moreover,"by"using"the"REST"API"from"within"the"automa6on"scripts"or"the"messaging" system"BRPM"can"also"be"easily"extended"itself"with"new"func6onali6es"(eg"crea6ng"a" new"plan,"request,"applica6on,"environment,"..."from"an"automa6on"step)" " These"features"allow"BRPM"to"support"the"scenarios"from"the"right"side"of"the" industrializa6on"arrow"(agile"etc)"
24"
This"feature"enables"infraMasMcode"workflows"where"the"requests"etc"can"be"saved" into"a"VCS,"can"be"shared"and"collaborated"on,"etc." 25"
RBAC"is"a"very"important"feature"in"the"big"enterprises"with"its"fine"grained" separa6on"of"du6es" 26"
27"
28"
29"
30"
31"
32"
33"
34"