2019/06/26: DevOps Enterprise Summit Day 2a

by Gene Kim on

#DOES19

2019/06/26: DevOps Enterprise Summit Day 2a

Up: Tom Clark, Head of Common Platform, ITV: @tomoncle

  • @tomonocle: "Core ITV Business Processes: Airtime Sales; Content Sales; Talent Payments; we couldn't find spare parts for these platforms; our COBOL programmers supporting these were literally dying out, causing existential risk
  • @DOES_EUR: .⁦@tomonocle⁩ going over the recent history of technology transformation at ⁦@ITV⁩ - also giving us some 😂 this morning #DOES19 https://t.co/308p9vdQ9m
  • @agilist_: "We had to virtualise it because we couldn't find spare parts on eBay anymore" @tomonocle #DOES19
  • @RealGeneKim: RT @agilist_: "From the high quality content like Downton Abbey to ... the other end of the spectrum" @tomonocle, now presumably ex-ITV. #D
  • @tomonocle: "common platform: security, logging
  • @DevOpsSmith: The modernisation story from @ITV - not the journey but what happens when you get to the right hand side by @tomonocle #devops #does19 https://t.co/zYAzuJF4aZ
  • @RealGeneKim: OMG! Hahaha! That’s so awesome!!! #does19
  • @tomonocle: "
  • @DOES_EUR: We want high IQ and high EQ people on the team @tomonocle #does19 @ITV
  • @tomonocle: "
  • @seizethedave: Common Platform takes away the cross-cutting infrastructure concerns from the teams at ITV #DOES19
  • @DOESEUR: RT @agilist: Platform Engineers: where smart and kind intersect. @tomonocle #DOES19
  • @tomonocle showing Better, Faster, Safer, quoting @jonsmart: another example of scenius!
  • @DOES_EUR: Remote sites meant lonely engineers ⁦@tomonocle#DOES19 https://t.co/zjgPNL6hEf
  • @tomonocle: "People struggled with YAML files". (Ha! The human condition.)
  • @tomonocle: So true: "we found that 15m CI/CD times were too long; remember, we used to think 8 week deploy times was ok!"
  • @samknutson: The slides from #DOES19 will be available for download on both Dropbox and GitHub. Dropbox: https://t.co/RqjHkEwTFq GitHub: https://t.co/YYZpqEAnlc #DevOps https://t.co/kgLkVqAb8C
  • @seizethedave: "Field" platform engineers are embedded within feature teams with 3 different responsibilities: operations, force multiplication (making the team more efficient), and influencing quality in the team #DOES19
  • @seizethedave: However, 95% of time, platform engineers didn't get to work with other platform engineers, which made them sad #DOES19
  • @agilist_: "Do something when you can afford to, not when you can't afford not to." @tomonocle #DOES19
  • @tomonocle: "As part of a roadshow, we did retrospective net promoter score,
  • @agilist_: (Hot people - clothes) * deama / voting = Love Island #DOES19
  • @edwardpearson: Great start to #DOES19 day 2 with @tomonocle from #ITV. Philosophy of their common platform team: “Do one thing and do brilliantly”. By creating a team to focus on the plumbing product teams can focus on delivering value. https://t.co/wYjAYFiFHQ

  • @tomonocle: "

  • @DevOpsSmith: The cost of agility is the constant investment in, and integration of, new technology [and working practices] #itv #does19 #agile

  • @DOES_EUR: We were running a well-maintained classic car, but everyone else was running Tesla’s @tomonocle #does19

  • @tomonocle: "

  • @DOES_EUR: 😂😂 secret formula of Love Island per ⁦@tomonocle⁩. Can’t wait to see how he ties this one back into his #DevOps journey ⁦@ITV#DOES19 #loveisland https://t.co/VkPIj7RU4K

  • @tomonocle: showing astonishing stats showing the 10m before start of Love Island episode; most tune in exactly at start of program.

  • @RealGeneKim: #DOES19 @tomonocle: showing astonishing stats showing the 10m before start of Love Island episode; most tune in exactly at start of program. https://t.co/iqVSQ1eUGW

  • @daveherpen: Hands down one of the best platform/product team stories I've seen. Honest, hilarious, comprehensive. Managed to talk about Love Island, without losing credibility. @tomonocle #does19 https://t.co/58ySxDMpDD

  • @DOES_EUR: You need a vision- @tomonocle at @ITV | #DOES19 https://t.co/xVIeba8LLV

  • @tomonocle: "We found that most developers didn't care about the container; they didn't care about how the sausage is made; they didn't care about YAML, Helm charts, etc.." (SO TRUE!!!)

  • @tomonocle: Devs put Mission Patches on laptops! And customized cake!

  • @DOES_EUR: Cycle time is 10x faster @ITV! @tomonocle | #DOES19 https://t.co/WciWnYjVRl

  • @DevOpsSmith: @itv cut deployment cycle time from 15 minutes to 90 seconds with their development platform enhancements. #FirstWorldProblems #devops #DOES19

  • @tomonocle: They survived Love Island launch!!! Woot!

  • @seizethedave: CP team deployed a fix during the Love Island premiere, the biggest ITV event of the summer #DOES19

  • @RealGeneKim: RT @DevOpsSmith: @itv cut deployment cycle time from 15 minutes to 90 seconds with their development platform enhancements. #FirstWorldProblems #devops #DOES19

  • @RealGeneKim: RT @DevOpsSmith: @itv cut deployment cycle time from 15 minutes to 90 seconds with their development platform enhancements. #FirstWorldProblems #devops #DOES19

  • @matthewpskelton: Excellent points from @tomonocle of ITV - "reduce cognitive load on engineers" by use of a Simple Mode for their v2 Platform. 🧠🧠🧠 #DOES19

@manupaisable and I expand on this in our talk at 14.10 today in Arcadia. 👍 https://t.co/x25wfoa282

Up: Nithya Ruff: Head of the Open Source Program Office, Comcast: just elected as Chair of the Board of Directors for the Linux Foundation!! Woot! @nithyaruff

  • @nithyaruff: the Comcast enterprise
  • @nithyaruff: 170K employees
  • @nithyaruff: the Linux Foundation mission is to create a sustainable ecosystem for open source projects
  • @nithyaruff: "Open source started as a fringe movement, which created a lot of fear for CFOs and lawyers" (and rightly so; enterprises didn't know how to deal with GPL and copyleft)
  • @nithyaruff: "Open source changed with 2nd generation: Linus Torvald's Linux; OSI and OSDL" (the goals was to make open source usable by companies; term became "open source" instead of "free")
  • @nithyaruff: "...this set the stage for Linux Foundation and Apache Foundation; came to dominate almost all infrastructure categories: web servers, etc..."
  • @TheOpsMgr: If you are a #telco and you're not embracing #OpenSource and modern software development practices the list of open source networking and orchestration projects from @linuxfoundation should make you very nervous. #Does19 https://t.co/QAWzOz1RIG
  • @nithyaruff: "In 2006, Comcast was highly reliant on commercial vendors and their roadmaps we decided to control our destiny and we can't wait for vendors to deliver what we need; we embraced open source and started contributing to it based on our own needs
  • @seizethedave: The third wave is the explosion of companies built on Open Source, like AWS and other cloud vendors #DOES19
  • @seizethedave: Early corporate adopters (IBM, Sun, Red Hat) start to get behind Linux #DOES19
  • @seizethedave: The second wave started with the creation of the Linux kernel, the birth of the OSI and creation of the OSDL (free 👉 open source) #DOES19
  • @seizethedave: The first wave of open source (GNU, FSF, GPL) was strongly ideological, and scared off many enterprises #DOES19
  • @seizethedave: The first wave of open source (GNU, FSF, GPL) was strongly ideological, and scared off many enterprises #DOES19
  • @seizethedave: The second wave started with the creation of the Linux kernel, the birth of the OSI and creation of the OSDL (free 👉 open source) #DOES19
  • @seizethedave: Early corporate adopters (IBM, Sun, Red Hat) start to get behind Linux #DOES19
  • @seizethedave: The third wave is the explosion of companies built on Open Source, like AWS and other cloud vendors #DOES19
  • @nithyaruff: Showing the OSS journey at Comcast
  • @nithyaruff:
  • @RealGeneKim: #DOES19 @nithyaruff: https://t.co/9cMneNHThU
  • @DevOpsSmith: Inspiring to be able to listen to @nithyaruff who is such an amazing role model for the technology industry. Thank you #does19 for finding such awesome speakers. #inspired #opensource #devops #womenintech https://t.co/QL03Ea9Y6P
  • @natasha_woods3: What a coincidence that Comcast's open source journey started in 2006, which is the same year I was a Communications intern at the company. #DOES19 keynote
  • @nithyaruff: "these are the orgs that have open source offices"
  • @RealGeneKim: #DOES19 @nithyaruff: "these are the orgs that have open source offices" https://t.co/eRBVVH6Uzc
  • @nithyaruff: "Benefit #1: focus on core competencies; things that customers actually care about

  • @RealGeneKim: #DOES19 @nithyaruff: Showing the OSS journey at Comcast https://t.co/9jWLMGw79N

  • @nithyaruff: "Benefit of OSS #2: open source enables talent acquisition; faster onboarding; faster ecosystems"

  • @seizethedave: What's the value of having a focused Open Source office in your organisation? #DOES19 https://t.co/08b2GXUdCp

  • @nithyaruff: "More Benefits of OSS: know what your critical open source dependencies are; help us synchronize OSS roadmaps with internal product roadmaps; encourages devs up submit their changes upstream in OSS projects; influence those projects; ensure those OSS projects don't die! (we contribute code and $$$)

  • @nithyaruff: "Benefit of OSS #3: as a huge enterprise, we have so many silos and engr teams using so many diff tech; OSS enables more collaboration and standardization; for internal DNS as service, teams able to PR their chgs

  • @nithyaruff: "Challenge #1: engaging middle management: execs like it conceptually; developers love it; but middle managers who have to deliver on budgets and projects don't want their devs to work on OSS, go to conferences, etc... urgent deadlines

  • @nithyaruff: "...but we help them understand that OSS lets them retire their tech debt; we're still working on it!"

  • @nithyaruff: "Challenge #2: Legal teams: their job is to identify and mitigate risk: 'why are we enabling our competition?'; we help them understand biz benefits of OSS; we created OSS Advisory Council to create mutli-perspective arg to make biz-lead discussion

  • @nithyaruff: "Challenge #3: diversity of people and contributions in OSS"

  • @nithyaruff: Help I'm looking for...

  • @DOES_EUR: If you see ⁦@nithyaruff⁩ in the halls, she’s love to hear your thoughts on these challenges ⬇️⬇️ #DOES19 https://t.co/3zFljjmNht

Up: Andy Burgin: Platform Engineer at Sky Betting and Gaming: @andyburgin

  • @ITRevBooks: RT @JanJoostBouwman: Starting to be an impressive collection! @ITRevBooks book case @DOES_EUR #DOES19 https://t.co/PqNdMOM9HG
  • @DOES_EUR: What DevOps looked like at ⁦@SkyBet⁩ in 2011 per ⁦@andyburgin#does19 https://t.co/yuXS3Dl1ZB

  • @RealGeneKim: #DOES19 # Up: Andy Burgin: Platform Engineer at Sky Betting and Gaming: @andyburgin

  • @seizethedave: Talk #3 of the day is about the DevOps Transformation at @SkyBet with @andyburgin #DOES19

  • @andyburgin

  • @agilist_: "We are what we repeatedly do. Excellence, then, is not an act, but a habit." - Aristotle #DOES19

  • @RealGeneKim: #DOES19 @andyburgin https://t.co/Wbvj2FWXeF

  • @matthewpskelton: "The important thing is that we have autonomous teams doing agile software delivery" @andyburgin of Sky Betting & Gaming #does19 https://t.co/BD7qBfs2O6

  • @DevOpsSmith: @andyburgin walking us through the changes in #devops topology over the last 8 years of the #skybet journey. #does19 https://t.co/B4NerLwCd5

  • @RealGeneKim: RT @DevOpsSmith: @andyburgin walking us through the changes in #devops topology over the last 8 years of the #skybet journey. #does19 https://t.co/x7X5r1CcnD

  • The MVP approach being used to develop platforms being presented by @tomonocle and @andyburgin. Cc @mik_kersten

  • @DOES_EUR: The journey of @skybet. By 2016, they had autonomous teams doing #agile software and delivery @andyburgin | #DOES19 https://t.co/Mhkfx0li2P

  • @andyburgin: "at Minimum Viable Operability stage, we bring in Service Lifecycle Management and Security"

  • @matthewpskelton: Prerequisites for high performance at SkyBet include: "You Build It, You Run/Own/Support/Fix It" 📟📈🛠️

@andyburgin at #does19 https://t.co/imhyjhi9Mt
- @DOESEUR: The four stages of product pattern @andyburgin | #DOES19 https://t.co/pmVQ24AEYV
- @andyburgin: "Tech debt as a service is bad..." hahaha
- @andyburgin: "MVP to MMP: Minimum Marketable Product; that's we market our platform; sell it to the rest of the teams"
- @andyburgin: "MVP -> MMP -> PaaS: this is when some of the devs might move into the customer teams to become their SMEs to help them get onboarded, help solve problems, etc..."
- @andyburgin: "Our pilot for container platform: the Notifications team: peaks at 1000 msgs/second: 500K connected clients!"
- @seize
thedave: When the product is in production, the team shrinks and may be absorbed into a wider service team #DOES19
- @seize
thedave: Cross-functional teams are regular agile teams used to take the product through MVP, MMP and into production #DOES19
- @seize
thedave: Pilot teams consist of specialists responsible for building the POC #DOES19
- @matthewpskelton: Nice to see a clear Platform definition from SkyBet - treating product teams as customers. @andyburgin #does19 https://t.co/CEGcZN39br
- @seize
thedave: Volatility of a product's requirements a d technology might delay movement from a cross-functional team into a product-as-a-service team [ed: why overload PaaS?! #facepalm] #DOES19
- @tomonocle: Loving @andyburgin's SkyBet story at #DOES19 - the pilot/mvp/mmp/PAAS model makes a lot of sense when products can be (mostly) "done" https://t.co/ssvL1OyuXc
- @DOES
EUR: The outcomes of @skyber journey, including reduction of hosting costs by 60% @andyburgin | #DOES19 https://t.co/6Qs9pmx6Rq

  • @seizethedave: At MMP, more customers are added, and focus is broadened to non-functional requirements, readying it for production #DOES19
  • @seizethedave: At MVP stage, add security, service and MOST IMPORTANTLY, a customer! #DOES19
  • @seizethedave: Sky Bet have two types of patterns: products and teams. #DOES19
  • @andyburgin: each engineer has 10% R&D "free time", who built Monkeybot to fix this problem: that urgent requests via Slack but are never recorded, thus disrupting prioritization
  • @RealGeneKim: #DOES19 @andyburgin: each engineer has 10% R&D "free time", who built Monkeybot to fix this problem: that urgent requests via Slack but are never recorded, thus disrupting prioritization https://t.co/3g7w2k0QK9
  • @andyburgin: "monkeybot results: it helps us record the unplanned work, and what it was for"

  • from @notorious_mvk: "Everyone is wearing Project Unicorn socks!"

  • @seizethedave: . @SkyBet use a single ticketing system for all requests, but tickets also create problems in terms of unplanned work. Unresolved unplanned work caused problems with interruptions through Slack #DOES19

  • @seizethedave: The solution to this is to route support requests to an on-call engineer through ChatOps (called "MonkeyBot" 🐵) in Slack. This creates fast feedback, an audit trail, and helps identify sources of unplanned work #DOES19

  • @DOESEUR: DevOps confessions kicking off now! Tom Smart reads an anonymous letter with ⁦@chawklady⁩ and ⁦⁦@mikkersten⁩ giving a lovely portrayal 😂 #DOES19 https://t.co/FlJNqQKFJF

  • "You cannot trust engineers; you can only control them" (hahaha)

  • @RealGeneKim: #DOES19 @andyburgin: "Our pilot for container platform: the Notifications team: peaks at 1000 msgs/second: 500K connected clients!" https://t.co/jJdZtdrm2x

TODO

  • when uploading photo: have red/yellow/green indicator or something to indicate uploading, uploaded