How can I go from System Administration to DevOps?
First, I was a very seasoned sysadmin with over 12 years experience across 5 large companies where I had always taken the “I’m here to make myself redundant” approach, that is I saw the role of systems administration as a role that shouldn’t exist if a system was done right.
So everywhere I worked I looked at every process and improved on it, I looked at any repetitive task and automated it… Obsessively. I could give hundreds of examples the extent I would go to just to either never have to do something again or to turn a 10 step process in to 1 or zero steps.
Many of the places I worked had 10+ I.t people in operations and support and after a few years of me being there they had to make most of them redundant.. Call me an asshole if you want, I just hate inefficiency. Continue reading this thread at Quora
What should DevOps know about system administration?
In my current role, we aren’t so cut into silos. Our tech support / system administrators will often restart services, and reboot servers if they are acting up, but a lot of time if the issue runs outside of that, I’ll get that 4am call to verify that it isn’t an infrastructure issue.
My incentive for not getting those calls is keeping resilience and self-healing in mind when pushing new CM changes to the instances. At times we find issues with a service running on the box, or an issue with the CI process within production. In these cases, we produce a new gold image with the changes and cycle it back into the auto scaling group, and kill the old instances. Often times after a big fix from an outage, that issue never arises again. There have been some growing pains. Continue reading this thread at Quora
I am a Linux System Administrator, what are the basic things to learn for DevOps?
So, before listing the tools, I’ll list my understanding of “DevOps”: DevOps is the title/role which combines traditional OPs/SysAdmin work with that of Software Engineering. The goal is programmatic. It takes the SysAdmin idea of, “If you’re going to run it more than once, you should write a script to do that” and turns the automation into an infrastructure/tool framework.
For folks who have been in SA work for a while and have slowly been adapting to greater and greater demands, for instance, going from 20–30 servers to 2000–3000 servers for a team of 2–4 people. You probably already went through the process of automating more and more of your work. Continue reading this thread at Quora
Sysadmin: how the role is changing between Cloud and DevOps
Operations’s approach maybe very different depending on whether the tasks are delegated to a developer rather than a Sysadmin. These different attitudes can also be found in the tools used for configuration management as they depend too much from the trader mindset.
Developers will be more friendly with Puppet or Chef, while the pure systems engineer will appreciate the schematic nature and the immediacy of Salt or Ansible. Continue reading this article at ServerManaged
DevOps and the future of system administrators
In every case, the future scenario involves big changes. At the same time, one thing is clear: if you’re a systems administrator and you want to continue doing something that looks vaguely like what you do today, you need to be into DevOps. Future IT solutions are going to be dynamic situations driven by responses rather than pre-determined conditions. And that requires a systems master, not a systems administrator. Enjoy the ride. Continue reading this article at CupFighter
From System Administrator to System Engineer
Automation of IT-operations can lead to fantastic productivity gains, increased quality of service and reduced operational costs. But what about the people, and their jobs?
System Administrators will not become obsolete, but the nature of their work often changes in highly automated environments. The ones who adapt typically enter into more proactive roles. The ones who willingly or unwillingly are left behind, end up fighting fires and home made scripts, until they will eventually be replaced. This evolution should not be viewed as a threat, but as an opportunity. Continue reading this article at CFEngine
How to stay relevant in the DevOps era: A SysAdmin’s survival guide
The merging of development and operations to speed product delivery, or DevOps, is all about agility, automation and information sharing. In DevOps, servers are often treated like cattle”that can be easily replaced, rather than individual pets”to be nurtured.
System administrators that built their careers configuring and troubleshooting individual servers still have a role to play in this new world. But they must learn to apply their skills to entire IT infrastructures described and managed by code. They must learn to manage cloud services and use automated deployment tools and code repositories—and to share their expertise with others. Continue reading this article at TechBeacon
Should you become a system administrator?
As a sysadmin you have the responsibility to keep all your servers up to date; both software and hardware. This means you’ll be first to test all the cool new gadgets and be in charge of deciding whether this could indeed help the company. There will never be a boring moment! Come to think of it, we also have a shiny toy that you should try out (for free of course)!
Unemployment will be a thing of the past.
There is an ever increasing demand of people who are able to handle servers and come up with stable, reliable ways of managing a network of servers. Regardless of whether the job title sysadmin merges into another title such as DevOps engineer – as long as there are servers out there that need maintenance and monitoring, your expertise will be in demand. Continue reading this article at Server Density