Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Reclaiming the lost art of Linux server administration

pietrorea.com

Post reply on HN
Print view View original

481–485 of 485 posts

Re: Reclaiming the lost art of Linux server administration

#481

Post by CRConrad »

akira2501 wrote: post #7
SkipperCat wrote: post #2

Time is money, and the more time I spend on infrastructure, the less time I spend on product. And thus is born the incredible demand of infrastructure as a service. Thankfully one person's cloud is another person's on prem infrastructure so sysadmin skills will always be in demand. From my perspective in enterprise computing, I now see people taking 2 paths. One where they become super deep sysadmins and work on infr…

That's when it clicked for me.. comparing my hourly salary rate vs. the cost of running these services "in the cloud." Entirely eliminating "system administration" from my duties was absolutely a net win for me and our team.

So why are there so many job adverts looking for people with "cloud experience"? If there were no system administration for the user to do, that wouldn't be necessary; they could be looking just for people with experience of running the actual software their job is all about, on top of the "no administration needed" infrastructure.

Re: Reclaiming the lost art of Linux server administration

#482

Post by CRConrad »

readingnews wrote: post #75
bblb wrote: post #41

Earlier quoted context omitted.

I work in IT Operations of a big IT house. 100% local gov customers. We fully manage around 5000 pet servers. ~30 sysadmins and some of us do architecture designing also. There's also a separate networking team of about 10 network specialists. Senior sysadmins are really hard to come by today, not to mention someone who wants to do architecture also. My hunch is that the 5000 onprem pet servers are not going away any…

>>Senior sysadmins are really hard to come by today, not to mention someone who wants to do architecture also. I am not so sure... I am a well seasoned sysadmin, been doing server, network, architecture. I consider myself a solid linux/network expert and have managed datacenters. When I look for a new/more exciting job, or for a pay raise, all I see are "cloud, AWS, devops". I never see "old school" sysadmin jobs e.g…

> When I look for a new/more exciting job, or for a pay raise, all I see are "cloud, AWS, devops". I never see "old school" sysadmin jobs

Because the old school systems just chug alongg with a minimum of administration, while those newfangled cloud thingamajigs need tons of adminning...?

I mean, that's one interpretation of your (admittedly, anecdotal -- but that's what I see too. Lots of anecdotes sums up to:) data. A valid one, AFAICS.

Re: Reclaiming the lost art of Linux server administration

#483

Post by cerved »

willjp wrote: post #440
cerved wrote: post #378

Earlier quoted context omitted.

the friend doesn't need to be techy just have a house

Well, a house and some kind of NAS or at least a computer that is always on. But I take your point. This idea is brilliant though!!

I expect one buys the NAS themselves and pay electricity

Re: Reclaiming the lost art of Linux server administration

#484

Post by akireu »

nix23 wrote: post #456
southerntofu wrote: post #420

Earlier quoted context omitted.

I thought AWS was the mainframe in the parent comment?!

Please educate yourself what a mainframe is.

Of course AWS is the mainframe in this analogy! It's a huge throughput- and reliability-optimized overhyped crazy expensive server that you hire someone else to run for you. It's designed the same way, with dedicated storage, compute and backplane servers. Even the discourse is the same to the 80s: "why we have to rent a $$$ monster when a $ commodity server outperforms it". How is this not obvious is beyond me.

Re: Reclaiming the lost art of Linux server administration

#485

Post by lambdaba »

trabant00 wrote: post #477
lambdaba wrote: post #417

Earlier quoted context omitted.

Yes, basically if I could peek into your activity for a day it would be awesome (I'm not asking that, although I would like it :P :)). I'm just curious of what a day's work looks like.

Typical day is actually mostly working to go around corporate "security" limitations that restrict everybody to not being able to do much for fear they will do harm. The last few days: - we have a commercial ssh bastion that requires direct ssh login and then input ip address. So no dns available for sshing. I wrote a bash autocomplete script that resolves dns host entries and uses expect to automatically input the i…

Thank you! Yes, that was my suspicion as well.
Post reply on HN