A talk about Dev Ops

~ by @anna ~

Pizza courtesy of @Imosphere

about me

I did a CS Masters here
I was a member of HackSoc
Now a .NET software engineer
Work at Imosphere /i-mo-sphere/
Interests include Linux, open source, devOps, automaton and getting involved in the tech community

about this talk

Where did it come from
What is DevOps??
Continuous stuff
Examples of different tools
How to DevOps in your own time

Where did DevOps come from?

Deep breath

Let’s go back in time

🦕

Waterfall

Long development cycle
Tightly controlled change management
Slow to release new features to customers
Long feedback loop

One computer per family
No smart phones
Systems develop

Agile

Short development iterations
Quicker to develop new features
Shorter feedback loop

Everyone has as smart phone Multiple devices Online ²⁴⁄₇

Lots of new features
Fragile infrastructure
Needed to change

Stopped new development for 2 months
Re wrote internal tools
Re trained their release cycle
Just before going public

Ok, so DevOps is just Devs doing their own Ops?

Deep breath
Lets meet the team

This is Dev

👩‍💻

Works on the product
Wants new features
Goes home at 5pm

This is Ops

👩‍💻

Manages the product in the wild
Maintain stability at all times
Change resistant
Going to get called out at 2am if the site goes down

It’s all in the culture

Dev, meet Ops. Ops, meet Dev

🙋‍♀️ 🙋‍♀️

A CULTURE
Working as one
Shared goals - a good feature rich stable product
As is appropriate

Google wrote the book on site reliability
Lets take a look at how google does it

Service Level Agreement

Services don’t need 100% uptime
Realistic uptime goals
New features vs stability
Cost of resources

Product owners, developers and SREs agree a realistic goal
If it’s new, doesn’t need to be that reliable
Data can be old as long as data is returned?
Data must be up to date but can be late

Error Budget

📈

100% uptime
SREs and developers agree together
Releases?

Monitor all the things

🎛️

What’s relevant to monitor?
Don’t monitor what isn’t important
Push alerts

Spend it!

💸

Use it on deployments
New features
Over budget, halt new releases

50x the expected traffic
Upgraded the container engine (kubernetes is based on) mid flight to allow more than a thousand extra nodes per container cluster - in flight
Upgraded the Google cloud HTTPS load balancer to be more efficient at handling that level of traffic

Bringing the Dev into Ops

deep breath
Bring the Engineering into site reliability

Shell scripts

🐚


$ ssh production@critical-server
$ ./deploy-billion-servers.sh

Automation starts with replacing manual steps with scripts
You can still reproduce the steps by hand
Need an audit trail
Not scalable

Engineering solutions

ServerId	CPU	TimeUp	ApplicationId	Memory
1	85%	18.02.19t06.45.40	3456	196
2	76%	14.02.19t08.20.00	763456	134

Need to scale
Borg - based on Kubernetes
Clusters of tens of thousands of machines
Automate fixing problems
Route traffic to other data centres

Let’s get continuous

Let’s have a look at how to devOps in practise

Continuous Integration

Small bite size chunks that work well together
Merging work into the main branch often, multiple times a day
Hour long branches

Small manageable changes

Continuous Delivery

Always have something to release:
It’s tested
Automated build

Continuous Deployment

Deploying the code to customers:
- Easily
- Often
- Automated
Aim is no downtime or affect to users

Easily
Often
Automated

With Confidence

How To DevOps

Spin it Up!

(And back it up)

AWS Cloud Formation
Google Cloud
Azure
On prem

Provisioning

Fancy word for installing stuff

Configuration Management
Bash
Chef
Ansible
Puppet

Multiple servers and data centres

clusters

AWS - elastic container service
Kubernetes
Docker Swarm
Borg

So you wanna devOps??

Stuff to do

💻 Linux

💻 Networking

💻 Manage a server

📘 SRE book

📘 DevOps Handbook

📘 Phoenix Project

📘 https://cloud.google.com/blog/products/gcp/bringing-pokemon-go-to-life-on-google-cloud

Thanks for listening!

Ask me questions

(or not - that’s cool too)

I’ll be hanging around for pizza, come say hi

A talk about Dev Ops ~ by @anna ~ Pizza courtesy of @Imosphere