Atmosphere Conference 2015: Bottoms-up and back DevOps
43
Transcript of Atmosphere Conference 2015: Bottoms-up and back DevOps
What are you ?
Bookshelf
*shamelessly stolen from @dromologue
It is not down on any map; tru“ plac“sn“v“r ar“.
Same story different perspective
THE PEOPLE
FRIENDS ABROAD
2013 A TON OF WORK
I NEED FOCUS
WE KNEW THERE WAS DEVOPSWHAT WE LACKED WAS TIME
STARTING POINT
HERE WE GO
DEVOPS ???
KANBAN ? MIGHT BE DANGEROUS
LET'S SCRUM
THE SPLIT50% - ATTACK THE ROOT CAUSE
30% - DEVOPS TOOLSET
20% - AD HOC
PRODUCT OWNERS
OFF WE GO
AND THE 30% WENT TO...
AND DEMOS...
SUCCESS DELIVERED
hindsight wisdom #1
OPPORTUNITYHUNTING
OPPORTUNITY CAUGHTTight deadlineMassive processingErrors more than likely
TESTINGEnvironments, environmentsRefresh takes timeMistakes, mistakes
WIDER
THE DECEPTIONFlashbackDid the trick
so we faked it :)
Refresh - MVP1Install - MVP2Process - MVP3
DevOps taking off
hindsight wisdom #2
To the prod we go
Back in the real world
Scaling Agile
The big thing
KILL THE SILO CULTURE
ALL IS CODE"servers": { "myplslcoedev1wls01": { "ipaddress": "10.14.201.56", "WLNODEROLE": "WLNode", "WLNODENAME": "cl1_srv_a", "config_name": "dev_gsb1", "enable_restarts": true }
"apps": {"factorlink": { "flk.env.local.config.jndi.url": "t3://vault:CLPORTS_XXXXX", "flk.config.docuware.username": "vault:factorlink:flk.config.docuware.flk.config.docuware.username" "flk.config.docuware.password": "vault:factorlink:flk.config.docuware.flk.config.docuware.password" "flk.config.docuware.ip": "192.168.XXX.YY", "flk.config.docuware.port": "90ZZ", "flk.config.docuware.poolSize": "5", "flk.config.docprocessor.url": "t3://vault:CLPORTS_XYZX", "flk.config.docprocessor.jndi": "ejb/DocProcessor" },
DEVELOPER+ MODEL
THE BIG THING TOOKOFF
HORIZONTALSCALLING
EASY ...
REALLY BIG THING
EoS/Compliance driven2000+ users (100 VMs)Complete desktop environment
ALL TOGETHERProduced in sprintsReps from other teams collocatedLess than 5h to deploy
SUCESS FACTORSThe teamdeveloper+ modelMVP
