On Thu, Jan 06, 2011 at 12:37:12PM -0600, Aaron McCaleb wrote: > > This dove-tails into an idea that has been kicking around my cranium > for a while. Instead of trying to put together a large laundry list > of things that must be configured on Redhat Linux, SuSE Linux, > Windows, and $platform...I think it would be better to abstract this > out to "System Administration Design Patterns". For instance, "Single > Sign-On" could be one such pattern...or possibly a compound pattern. > Each required component for implementing SSO would be represented as a > unique "object class" within the pattern, and the basic, commonly > required configuration information would comprise the properties and > interface of each "object class". > > We could start with the system administration design patterns, > determine which of those are an integral part of any system > adminstration role, and then determine curriculum recommendations > (perhaps require that labs implement of these patterns within at least > two platforms...bonus points for heterogeneous platform > implementations) to ensure sufficient competency for any graduate to > be successful in an entry-level position. > > By focusing on design patterns, and not specific platforms, > technologies, file system implementations, network standards or vendor > product offerings, we also provide a better foundation of knowledge > that can improve any system administrators understanding of what they > are doing. This is sometimes lost when a "computer guy" only learns > how to configure one product, but doesn't understand which of those > configured services are common to _any_ product that implements some > or all of the same functionality. This _also_ would provide a > resource for those who have to combine heterogeneous platforms into a > single, _cleanly_ integrated system. "I know that both platforms, at > a minimum, have to have a way of implementing this set of service > components to provide the same functionality. So these > services/platforms should integrate or overlap in such-and-such > manner, minimizing the amount of 'middle-ware' needed to get it > $desired_services to work throughout the whole environment."
In the interests of brevity: 1) I wholly agree with this approach. 2) A more commonly used term/paradigm is Best Practices, which I think LOPSA is and should be in the business of collecting, editing, and publishing. Thanks! Jesse -- Jesse Trucks, GCUX [email protected] Director, LOPSA 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/
