Check out my "Training program to make a Novice System Administrator": http://verticalsysadmin.com/blog/training-program-to-make-a-...
Ask HN: DevOps learning resources
61–68 of 68 posts
Re: Ask HN: DevOps learning resources
#62The first thing to realize is that DevOps is an ambiguous term (at least partly by design, it seems). My belief—shaped by many at the forefront of the DevOps movement—is that it is a cultural focus rather than a technical one. In many ways, it's an extension of agile philosophies, with a focus on fast feedback, transparency, heightened interactions between teams, etc. There is also a heavy focus on automation (CICD),…
For those who've gone, is the DevOpsDays $175 price tag worth it?
They're offered all over the world, so the quality probably varies quite a bit (especially since it's a fairly decentralized organization). However, for the price tag, I'd say it's a steal—the networking value alone is worth more than that.
DevOpsDays has been around since the very beginning of the movement—in fact, the term was popularized at DevOpsDays Belgium in 2009.
Re: Ask HN: DevOps learning resources
#63devops is more of a principle than a job. that's my opinion though.
i've been reading through this book and it does a decent job of covering the principles for CICD, builds, tests releases: https://www.amazon.com/Continuous-Delivery-Deployment-Automa...
you'll run across various "thought leaders" in devops and its important to remember that a) each employer treats devops and cicd differently and you'll want to learn their practices as you bring about your own ideas to the culture and b) form your own opinions, just b/c thought leaders and books are out there its important to learn what you like to do and improve how you like to do it.
Re: Ask HN: DevOps learning resources
#64Well, the best way to learn is to actually do something. Create a small service in your favourite framework. Something really small, an echo service will probably suffice. Then stop "developing" and switch on "Ops mode". Automate: - builds (build & packaging scripts) - deployments - try all 3 major approaches: - push deployment: running a command on a central server that orchestrates everything (Ansible, Salt, chef-s…
I forgot to mention 3 very important things "to add": - security (you should already know a great deal from your work as a developer, the general things such as no open ports, no plain text passwords, etc.) - related to security: secret management (Chef, Puppet - I think, Vault) - backups, backups, backups: for the database and basically anything which is not reproducible from source (which in general should only be…
Interesting only one comment made a clear call to backups. Strongly second the notion of backups as a high priority to learn and implement. Could make it more "devops-y" by also automating the verification of them with restores/testing.
Re: Ask HN: DevOps learning resources
#65Shameless plug - I've got a 15 hour course on building a full infrastructure on AWS:
https://awsdevops.io/p/practical-and-professional-devops-wit...
We go from zero to fully scalable/loadbalanced etc. infrastructure on AWS. :D
Re: Ask HN: DevOps learning resources
#66I recommend the following books to learn more about the work involved on the Ops side: https://www.amazon.com/Modern-Linux-Administration-Cutting-E... https://www.amazon.com/Practice-Cloud-System-Administration-... https://landing.google.com/sre/book.html https://www.amazon.com/How-Linux-Works-Superuser-Should/dp/1... https://www.amazon.com/Effective-Monitoring-Alerting-Web-Ope... https://www.amazon.com/Ansible-DevOp…
for that linux administration book, how do you know whether its good or not? it's not out yet.
Re: Ask HN: DevOps learning resources
#67Well, the best way to learn is to actually do something. Create a small service in your favourite framework. Something really small, an echo service will probably suffice. Then stop "developing" and switch on "Ops mode". Automate: - builds (build & packaging scripts) - deployments - try all 3 major approaches: - push deployment: running a command on a central server that orchestrates everything (Ansible, Salt, chef-s…
With respect, Puppet is push-based, not pull-based.
Chef is pull-based by default, but you can also use it in a push-oriented manner.
Having worked with both Chef and Puppet, it is my opinion that Chef is the more scalable of the two, and the one that makes more logical sense to me. YMMV.
Re: Ask HN: DevOps learning resources
#68Devops: One word of caution. The future really will be having a docker file and finding a place to run code (docker swarm, ecs, etc). When you commit code it will be ran through a ci system (unit tested, staged) then updated. The salts, puppets, chefs, Vaults, running your own Kubernetes (wtf), VMs, Nagios, sendmails, vpcs and all this other drama will be latin in a few years. The future will be running the code on y…
This could be true, from a developer's perspective. But the OP was in the spirit of expanding one's knowledge and understanding. But even if a single-interface, fully-managed container orchestration service is available to all, the value of understanding how the underlying systems actually function will not cease to exist. Anyone building moderately complex systems will still want to know about OS, networks, storage…
[deleted]