I'm so grateful DevOps is now a thing. I remember getting a phone call from a client at 2am on a Friday because their site was down and having to ssh in from a Nokia with the world's tiniest keyboard to reboot the server.

Of course that particular server only exposed port 22 on it's local network, so I had to first ssh into another server which did have its ssh port open to external connections.

Trying to remember two sets of credentials and type them in on a tiny keyboard, while so drunk you were seeing double, standing outside in the rain as it was the only place you got signal. Yeah…I'm so grateful DevOps is now a thing

Drunk bastion-hosting?

#drunkmin

Been there bro. One of our clients would only allow us access from our building so we had to ssh into one of our server, ssh from there to their hop box then finally to the target server.

It was made worse by the fact they actually paid another company to administer the servers but didn't trust them with root access so that company used our support to effectively do their job for them.

I'm sorry, but "DevOps" doesn't fix this problem, unless of course you have created some kind of automation script to reboot the machine, but even still DevOps as a methodology neither fixes your access problem to reboot the server, nor does it address the fact that some faulty code in the application caused it in the first place. however, if you consider agile part of DevOps (but is not in of itself) it may help you fail faster and fix the problem sooner... or better yet, create a user story to be included in the next sprint that say you want to be able to call an API to reboot that server from a cell phone... then maybe the. you can say that DevOps, as a "thing" helped you with this problem.

@daarkfall Oh the irony

@techgesture lol wut?

@tisaconundrum sorry, that was my rant on his rant... I found it comical.