Dev (ASP Classic, Windows 98)
Linux (1999)
Epre
Healthcare, Nursing
Back to First line support
Consultancy
Namesco
HPCS SysAdmin, then Dev
DevOpsGuys (Hiring)
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.
Email servers - “copy the config from an existing server”
Puppet
Cucumber-libvirt “given that I want a webserver...”
Chef
Openstack
Ansible
Complex field
Tooling
Many complicated SaaS/Of the Shelf solutions available
It's hard, but it doesn't need to be complex
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.
I've seen all of these...
“If it's not being monitored, then it's not in production. If it's not in production, it's not DONE”
Quite a lot, we'll cover Vagrant, Virtualbox, Openstack, Jenkins, Ansible and Git
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!
Mentioned once or twice today, I thought I was being original... ;)
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!
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 ;) )
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.
