Pipelines for SysAdmins #pipelineconf 2015
- 3. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 Matt Wallace ● Started as a “developer” ● Moved to SysAdmin ● Took a break from IT ● Started back in support ● Back to SysAdmin ● Consultancy ● Back to SysAdmin ● “Developer” again ● “DevOps” ! @proffalken @proffalken www.devopsguys.com
- 4. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 Why “for SysAdmins”? ● Event-driven workflow ● “Reactive, not Proactive” ● Not always understood ● Often not involved until Deploy @proffalken www.devopsguys.com
- 5. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 The story so far... ● Bash scripts ● Configuration Management ● Virtualisation ● More configuration management ● More virtualisation ● More configuration management @proffalken www.devopsguys.com
- 6. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Where do we start?
- 7. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com What is a pipeline? “The process by which code or configuration progresses from the developer's workstation into the production environment.”
- 8. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com When are we “done”? ● My Manager told me to work on something else... ● Code has been commited to the repo... ● Code has been commited to the repo with tests... ● Code has been commited to the repo with tests that work... ● Those tests have passed... ● QA have told me that those tests have passed... ● I've closed the ticket... ● The code is in production...
- 9. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com When are we “done”? “Is it being monitored?”
- 10. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Tools available today
- 11. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Keep it simple! http://jess4921.deviantart.com/art/Behold-A-Rainbow-Unicorn-Ninja-89652879
- 12. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Monitoring Driven Development
- 13. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Why use monitoring scripts? ● Icinga/Nagios: – 0 is OK – 1 is Warning – 2 is Critical ● Jenkins: – 0 is OK – Anything else is a failure
- 14. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Lessons learned ● Get everyone involved at the start ● Including Management ● And Security ● And QA ● And the developers ● EVERYONE
- 15. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Lessons learned ● Start small and iterate ● Kanban-style “To do, Doing, Done” works well ● Don't over-complicate ● Automate, Automate, Automate ● Use opensource ● Find others who have already solved your problems ● Abuse Twitter contacts heavily ● Attend conferences (and the pub sessions afterwards!)
- 16. Pipelines for SystemsAdministrators ©DevOpsGuys 2015 @proffalken www.devopsguys.com Questions?
Editor's Notes
- #4: Dev (ASP Classic, Windows 98) Linux (1999) Epre Healthcare, Nursing Back to First line support Consultancy Namesco HPCS SysAdmin, then Dev DevOpsGuys (Hiring)
- #5: Scrum/Agile don't really work too well with event driven workflows (where do you put the ticket you're working on when a P1 comes in?) No matter how hard you try, at some point it's going to be 3AM and a pager getting you out of bed Very different world to that of development. “Works on my machine” is never acceptable, can take hours to work out why something is not working Silos have made most SysAds suspicious of “DevOps” - especially when some people think it means developers doing operations.
- #6: Email servers - “copy the config from an existing server” Puppet Cucumber-libvirt “given that I want a webserver...” Chef Openstack Ansible
- #7: Complex field Tooling Many complicated SaaS/Of the Shelf solutions available It's hard, but it doesn't need to be complex
- #8: Developer != python/java/c#/whatever, sometimes developer == sysadmin (Puppet/Chef/Ansible/etc) All we are talking about is a process that gets code into production in a safe manner. The tools are relatively immaterial, it is the process that matters, the tools simply facilitate that.
- #9: I've seen all of these...
- #10: “If it's not being monitored, then it's not in production. If it's not in production, it's not DONE”
- #11: Quite a lot, we'll cover Vagrant, Virtualbox, Openstack, Jenkins, Ansible and Git
- #12: This is based on a pipeline I originally created in around 200, however back then I had to write my own wrappers around libvirt. Now, I just use someone elses!
- #13: Mentioned once or twice today, I thought I was being original... ;)
- #14: They test your “code” and infrastructure at the same time Deploy your “tests” and run them against prod – the best possible way to make sure that the code in prod matches what you expected!
- #15: You really do need everyone on the project to buy in to this. One company where only the immediate line managers bought the idea of starting off simple, the project ended up using unsuitable technologies and was replaced after two years. Phoenix project - “Don't let security get involved, they'll just stop us from doing stuff” QA – can't test unles they understand what the original requirement was Developers – you need to talk to them otherwise you won't know what is being deployed If all else fails, try to encourage them to go to the pub with you and offer to pick up the tab (you can always try and expense it later ;) )
- #16: Don't try and solve everything all at once Don't think that once you get past a certain point it will all be fine and there will be no interruptions. You are wrong. Everything in it's simplest form but no simpler Automation is your friend. Use it. It will give you more time in the pub on a Friday night OpenSource software has solved a lot of these problems already. OpenStack infra git repos are a good source of information.