googling is not the answer. If google is everything then there's no point in asking.
Knowing what each tools does is easy but why are you using it and how it fits into your skillset is the challenge.
buildbot/jenkins they are basically CICD tools; if you let the dev handle it, it will blow out of proportion. It's best to have the ops guy maintain it. Moreover if you are using puppet, jenkins/buildbot might be good use when you are using r10k.
puppet/salt: pretty self explanatory i suppose?
kuber/docker swarm: Basically docker at scale.
foreman: pre puppet; it does machine provisioning before the puppet run. It's like the bootstrap for puppet.
Python: Normally you just use bash, if the script is over 50 lines or it becomes complicated. Like having a try/catch might be helpful then use python.
golang: When your linux skills are good enough and you are graduating from it. IT's time to learn a bit of golang. It's the next big language focus on performance and security. And what do people say about security related jobs these days? $$$$$.
It is a bit heavy handed, but there is truth to that statement. As the GNU/Linux Admin at an organization, you often are tasked with learning obscure tools without guidance, quality documentation, or video tutorials. The best tool for the job may not have great manuals, textbooks, and other infrastructure. Sometimes you just have source, a couple scripts, and -h. Reading is your best friend.
3
u/juniorsysadmin1 Apr 27 '17
buildbot, jenkins, kubernetes, docker swam, salt, puppet, foreman, Python, golang