I also like what OpsSchool is trying to do, but not sure it's defining best practices as a whole; seems like it's more for training people who think they may want to be a sysadmin in the nuts and bolts, to get them to at least a "junior" (SAGE I) level.
From http://www.opsschool.org/en/latest/introduction.html#goals-and-focus - "Goals and Focus To have a complete syllabus for training smart persons with high potential who already have a basic understanding of Linux or other UNIX variant, to become strong junior systems administrators." For sure there is an overlap (I should hope they'd teach stuff in light of best practices) but not sure they'd be the ones to define it. I really think LOPSA would do well to lead in this area... Also, hopefully the principals would be abstracted, and not purely focused on one operating system or another (as a dual network/systems admin, I can see that there are a lot of overlaps in principals, but the environment/OS's and management thereof are wildly different... ) The more I think about it, I believe a great foundation would be "The Practice of System and Network Administration, Second Edition" by Limoncelli/Hogan/Chalup ( http://www.amazon.com/Practice-System-Network-Administration-Edition/dp/ 0321492668 ) - It may be in need of updating in light of "DevOps" principals, but this book seems to me to cover the basic best practices very well. Very great (as others have previously mentioned) to be discussing this topic... -Will From: [email protected] [mailto:[email protected]] On Behalf Of Carlo Flores Sent: Wednesday, July 03, 2013 7:57 PM To: john boris Cc: [email protected] Subject: Re: [lopsa-discuss] Mark Burgess quote from April 2013 ;login: Ops School deserves linkage in this discussion on documentation and shared knowledge. https://ops-school.readthedocs.org/en/latest/ On Wed, Jul 3, 2013 at 4:36 PM, john boris <[email protected]> wrote: One trait that a. System administrator should have is strong troubleshooting skills. They also have to to be a logical person so they don't chase down rabbit holes. You really can't list a definite programming language as that is a moving target as is become more sophisticated. On Wednesday, July 3, 2013, Robert Hajime Lanning wrote: On 07/03/13 15:37, Joseph Kern wrote: I guess we could start by asking something like this: "What is a System Administrator not responsible for?" and working backwards. "It depends..." -- Mr. Flibble King of the Potato People _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/ -- John J. Boris, Sr. Online Services www.onlinesvc.com _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
