DevopsDays 2015 Conference Notes
Overview
- Where: Toronto - CBC Building , Glen Gould studio. Very nice venue.
- Who: Colin and David Attended.
- What: http://www.devopsdays.org/events/2015-toronto/
- Why:
vendors of note:
- victorops
- make operations a big chat channel. Monitoring , ticketing , client ocmms all go into a big chat log. This does lots of things, for exmple you get transparency with client, you get a single place to see what's going on. You get chatops ( the new buzzword for doing ops work via a chat interface ). it also make it easier to write timelines of activity for incidents. I felt like that have a lot of operational intelligence built-in, but the structured Incident maangement and problem management aspect are not addressed or considered.
- shomi - a scalar client
- Shaw / Rogers Joint venture to do TV over internet. Not a vendor, jsut a participant who wanted to talk about what they did.
and the resst:
- Azure
- Chef
- ansible
- Puppetlabs
Hacking the CxO Code
J. Paul Reed, @SoberBuildEng
aka "how to talk to CXOs about devops."
This was a good talk well executed, good subject matter, applicable, correct audience ( talking to techies about talking to management / non techies )
You have to understand the world before you can change it. - annonymous
Q: What is devops? A: tools and culture
Story arc:
- cost
- value chain
- "safe to fail" rollouts
- "potential energy"
What are the Costs
- consultant / lic / training / operatoinalize
how do I get the rest of the team to support this.
"site loads fast" - non funtional req.
- leaders don't want to hear about fixing today, they want to know what this will give them.
- stay in scope / don't change everything.
- you are not necisary for the success.
there are two buckets: capex / opex. ( dev:capex, ops:opex )
you could make the argument to accounting that cloud servers are cap ex ( even though they are typically opex )
"get to know your budgets personality"
kanban game
leadership doesn't understand that effect of their dictums.
devops meeting : dev + devops + ops => painful meeting.
risks: reputation , budget -> water cooler = less pagentry
skunkworks: work useful, but had to be hid. ( low risk , low cost ) legitimize projects?
until devs understand it's context, then devsops for devops doesn't matter.
d'uh - this is like IT for the sake of IT.
devops team is an anti pattern
---
Agent of Change - Here's Your Helmet H. "Waldo" Grunenwald, @gwaldo
the people who made bad dcisions
they did the best that they could at the time. bullshit : they knew what the ywere doing was wrong, the hardest part is finding the person who owns the change. "trying to make htings better" - but how? don't right stupid, make more awesome - doesn't owrk for me.
---
Chef, test-kitchen, Docker, CI, Oh My! Arthur Maltson, @amaltson
___
ignite??
one branch: master many small branches, merge often bug in full ports Travis CI for automated CI no custom follw up, no frintion. ?roll back? "external demos on latest" - what does that mean? what does this mean: in the wild? in production? donald knuth term: mumbo jumbo.
day 2 ignite: --- @fawzymanaa
http://ronjeffries.com/xprog/articles/the-noestimates-movement/
___________
layer documentation must be in canad dev enviroments low latency for contract stuff securoty / encryption integration testing. delphix
can give a veiw of enviroment.
Victoria Bradley
documentat management for laywers reference: http://www.lsuc.on.ca/For-Lawyers/Manage-Your-Practice/File-Management/Document-Management/File-Management-Practice-Management-Guideline/ http://www.advocatesllp.com/our-technology.htm http://www.tloma.com/events
