50
DevOps Anti-Patterns Fernando Ike (fike)

DevOps Anti-Patterns

Embed Size (px)

Citation preview

Page 1: DevOps Anti-Patterns

DevOps Anti-Patterns

Fernando Ike (fike)

Page 3: DevOps Anti-Patterns
Page 4: DevOps Anti-Patterns

“DevOps” Training

Agile Infrastructure

● Github● AWS● Introduction to Configuration Management ● Management Docker

Page 5: DevOps Anti-Patterns

“DevOps” Training

Continuous Delivery

● Introduction to Continuous Delivery ● Introduction to Continuous Integration● How to create a Continuous Delivery environment ● Jenkins Basics

Page 6: DevOps Anti-Patterns

“DevOps” Course

DevOps

● Linux● Git● Jenkins

Page 7: DevOps Anti-Patterns

Ability in playing Street Fighter 2 (you really want that).

Page 8: DevOps Anti-Patterns

“Throwing shurikens and Chunnin's certification test also are highlights.”

Job Descriptions

Page 9: DevOps Anti-Patterns

Job Descriptions

“Oops ... I missed something… and if you like a relaxed environment, enjoy working in shorts, flipflops, cap…”

Page 10: DevOps Anti-Patterns

Job Descriptions

“...If you want to propose new products, study groups, hackathons, dojos, etc.”

Page 11: DevOps Anti-Patterns

Job Descriptions

Analyst, Devops Developer and Analyst of Mainframe systems - Cobol

Page 12: DevOps Anti-Patterns
Page 13: DevOps Anti-Patterns
Page 14: DevOps Anti-Patterns

● “Fridays often have pizza! After deploy, we are in the War Room.”

● “I’m DevOps, I implemented Jenkins and Puppet.”

● “We are requested as “DevOps” when Devel team call us to participate in the Scrum meetings.”

● “I’m DevOps architect… I paid a course.”

● “We do dozens a deploys per day, developers have root passwords in our servers”

● “Our applications are immutable, they are frozen for weeks until new deploy”

We use “DevOps”

Page 15: DevOps Anti-Patterns
Page 16: DevOps Anti-Patterns

Sysadmin

● “I chose sysadmin professional because I don’t know to code”

● “I don’t care to talk to people, I prefer machines”

● “DevOps are bu$#@%. Nobody knows how to compile linux kernel”

● “Developers don’t understand how to work the Operation”

● “My servers…”

Page 17: DevOps Anti-Patterns
Page 18: DevOps Anti-Patterns
Page 19: DevOps Anti-Patterns

Buzzwords

● They aren't necessary good or bad, depends who and how they are used

● Buzzwords are often a good way to implement new methods and/or technical

stuff.

● They are being used to change mindsets of companies and professionals…● … Sometimes they are are just a way to sell new products/services.

Page 20: DevOps Anti-Patterns
Page 21: DevOps Anti-Patterns

What DevOps Is Not...

Page 22: DevOps Anti-Patterns
Page 23: DevOps Anti-Patterns

Heroes/Ninjas/Warriors

DevOps Is Not Only...

Page 24: DevOps Anti-Patterns
Page 25: DevOps Anti-Patterns

A Job

DevOps Is Not Only...

Page 26: DevOps Anti-Patterns
Page 27: DevOps Anti-Patterns

Training/Course

DevOps Is Not Only...

Page 28: DevOps Anti-Patterns
Page 29: DevOps Anti-Patterns

Tools

DevOps Is Not Only...

Page 30: DevOps Anti-Patterns
Page 31: DevOps Anti-Patterns

DevOps Is Not Only...

Continuous Delivery

Continuous Deployment

Continuous Integration

Page 32: DevOps Anti-Patterns
Page 33: DevOps Anti-Patterns

Automation

DevOps Is Not Only...

Page 34: DevOps Anti-Patterns
Page 35: DevOps Anti-Patterns
Page 36: DevOps Anti-Patterns

Recruitment “DevOps”

● Passion and willingness to learn

● Problem solving mentality

● Self-motivation

● Great social skills

● Tools and experience are important, but are not the only, and certainly not the most important factor.

Page 37: DevOps Anti-Patterns
Page 38: DevOps Anti-Patterns

Sysadmins skills

● Passion and willingness to learn

● Problem solving mentality

● Self-motivation

● Great social skills

Page 39: DevOps Anti-Patterns
Page 40: DevOps Anti-Patterns

Dev/Ops

● Infrastructure as code means CODING

● Some tools are really good and perhaps you don’t need CODE

● Don’t been married to softwares or languages, next softwares/languages will be “better” than the current ones

● Don’t be a hero, work with your team and think of how to improve everything

● Patients, Resilience and good Communication skills are really important to practice DevOps mindsets.

Page 41: DevOps Anti-Patterns
Page 42: DevOps Anti-Patterns

Courses/Training

● Trainings are limited and brief (short duration)

● They never approach all tools, methods but they a good start point

● Perhaps a better way are to develop non technical skills

Page 43: DevOps Anti-Patterns
Page 44: DevOps Anti-Patterns

Devs/Ops/Managers

● Agile methodologies shouldn’t be “Follow strictly the process”, be flexible.

● Onboarding practice among teams

● Tools are relevant but people are more important to implement DevOps (Agile) process

Page 45: DevOps Anti-Patterns
Page 46: DevOps Anti-Patterns

● Don’t use root user as service owner

● Don’t allow frequently access directly in production databases

● Update as last as possible software versions (mainly securities updates)

Devs/Ops/Managers

Page 48: DevOps Anti-Patterns

Fishbowl time

Page 49: DevOps Anti-Patterns

links

● http://naruto.wikia.com/wiki/Ch%C5%ABnin_Exam_on_Fire!_Naruto_vs._Konohamaru!● https://en.wikipedia.org/wiki/Shuriken● http://jurasicgamespc.blogspot.com/2013/04/super-street-fighter-2-portable.htm● https://flic.kr/p/9efgm7● https://dzone.com/articles/designing-tests-talk-iasa● https://www.flickr.com/photos/84568447@N00/5549927129/● http://www.gamesradar.com/14-freaky-sci-fi-and-fantasy-prisons/● https://www.flickr.com/photos/kaykim/3883340152● https://xebialabs.com/periodic-table-of-devops-tools● https://en.wikipedia.org/wiki/Blacksmith● https://flic.kr/p/c4QJzC● https://flic.kr/p/dRbGxB● https://en.wikipedia.org/wiki/Lord_Kitchener_Wants_You● http://dilbert.com/strip/2008-09-03