7 ms·
This is, I think, one of the classic splits between developers and sysadmins. Sysadmins are always logging in to unconfigured systems, new systems, foreign syst
by dsr_ 14y ago
This is, I think, one of the classic splits between developers and sysadmins. Sysadmins are always logging in to unconfigured systems, new systems, foreign systems, and of course broken systems. Being fluent in sh, bash, vi (appreciating, but not depending on vim-isms) and knowing your way around every config file in /etc... those are basic tools for sysadmins.
Developers should have the most productive environments possible. If that means eleventy megabytes of dotfiles and the like stored in a git repo, so be it. Once you move in, nothing should get in the way of turning thoughts into code.
What this means for DevOps... is that you had better have a development system which is in no way experimental. Try not to do dawn surgery on a patient you're going to need to run a marathon in the afternoon.
- alttab 14y agoDisagree sir. It all depends on how much you depend on your toolset to get anything done. I don't use textmate because its not installed on servers. I used to use ksh instead of shimming in bash when on AIX systems because it was the default. My toolchain: Bash, VIM, and... well, that's freaking it. No NERDTree, no craziness, nothing. The only thing I need to configure my fully functional environment and be at full productivity: set tabstop=2 set ruler set expandtab syntax on filetype on * formatting
- jaylevitt 14y agoNo, what this means for DevOps is that you'd better create a foolproof method to insert your dotfiles into the distribution - and that it's more important than ever to argue for individual user accounts, not role accounts, on production machines. For security and logging, of course. Love, DevOps
- moe 14y agomore important than ever to argue for individual user accounts, not role accounts, on production machines. For security and logging, of course. That's a terrible idea on so many levels, I hope you're being sarcastic.
- jaylevitt 14y agoYou're saying it's better for sysadmins to all log in as "prod" or "root"? How do you figure?
- moe 14y agoFirstly on properly automated hosts you very rarely have to login. And when you do then 'prod' and 'root' work just fine. Scattering user-accounts across machines is a maintenance headache (trust graph, sudo passwords or passwordless sudo, filesystem permissions) and encourages bad practices ("i'll just run this small script, quickly"). If you're serious about auditing then wtmp and notoriously incomplete shell-history files are not your tools either.
- ams6110 14y agoLogging in a root is an exceedingly BAD idea, regardless of how properly configured the host is.
- donavanm 14y agoLet me know how your compliance audits go. I'm sure the pci dudes won't mind that "root" logged in from 20 different hosts.
- moe 14y agoWhy would a human login at all? In serious deployments people don't login to production hosts outside of extra-ordinary incidents. This entire discussion is based on a broken premise.
- jaylevitt 14y agoIn single-server deployments, you're logging in because you're the only employee. In ten-server deployments, you're logging in because every machine is trying to take on a new role or aspect and you're still learning how to automate that. In thousand-server deployments you're logging in because the latest batch of Seagate drives has a statistically significant failure rate and you need to try some experimental firmware they wrote for you. When do you get "serious"? I don't always log into my production boxes... but when I do, I log in as 'jay'.