vortex_panda

I'm aware of the "lift and shift" mentality that some people have. I know several people who work at another company that decided to just uplift their on-prem VM-based software stack into AWS. It went very poorly.

"A sysadmin doesn’t want to automate his job and let the cloud provider manage what they can manage"

There may be some people like that, but I never said that I didn't want to automate my job. I'd rather automate as much as possible. I realize that in order to scale infrastructure, you can't be sitting around manually pressing buttons and running apt-get command to install software.

Thanks. I have thought about something like that, but I wouldn’t know what to write or blog.

I was wondering about that. Every time I looked at AWS pricing, it seemed insanely expensive for the people that just forklifted their on-prem services into the cloud without re-architecting it to fit that type of environment.

"google for a while and then call the vendor"

This is unfortunately how most of our organization works. For certain types of things, we're actually required to do this due to regulations, bureaucracy, and what not.

I'm not sure why it's as difficult as it is for me. I'm sure there are people for whom it's not as much of a herculean task.

"Okay, first off, being a sysadmin or an ops person is important!"

This is the first time that I have heard or read anyone say this in years. Thanks

I do enjoy automating infrastructure. I guess I feel somewhat obligated to dive into the development side due to the industry trends and the constant "Anyone can code", "Coding bootcamps", and such.

Thanks

I think that some of my issues possibly stem from a combination of my previous job being a hostile work environment as well as repeatedly being told by other coworkers (and even a former manager) that: "The work that I was doing wasn't valuable."

I still haven't come to terms with it I think.

I have been wanting to try out things like AWS and containers and such, but I haven't had the chance yet. I think part of it is that I haven't had the chance in a work setting to check those things out. We have thousands of physical machines and on-prem VMs. Sometimes I feel like we're kind of "old-world".

Thanks, this is good to know.

Thanks for the response.

As far as debugging other people's work, I do that a fair bit within our configuration management system. I also write "fresh" config management states (we use SaltStack), fairly often as well. But SaltStack is mostly human-readable YAML/Jinja, so it doesn't seem to cause the same issues as trying to write and parse Python.