Comments on: Design Patterns in System Administration http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/ Made with only the finest 1's and 0's Thu, 04 Dec 2008 18:07:34 +0000 http://wordpress.org/?v=2.6.5 By: Steve Loughran http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/#comment-3140 Steve Loughran Fri, 29 Aug 2008 07:55:57 +0000 http://www.protocolostomy.com/?p=348#comment-3140 I'm building a 'patterns of deployment' wiki, where deployment==the act of getting a working system up and running. The focus is mostly on CM-tool deployment (and java apps). And, patterns-style, it likes to look at the disadvantages of various approaches too: http://wiki.smartfrog.org/wiki/display/sf/Patterns+of+Deployment I’m building a ‘patterns of deployment’ wiki, where deployment==the act of getting a working system up and running. The focus is mostly on CM-tool deployment (and java apps). And, patterns-style, it likes to look at the disadvantages of various approaches too: http://wiki.smartfrog.org/wiki/display/sf/Patterns+of+Deployment

]]> By: Julian Simpson http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/#comment-2938 Julian Simpson Wed, 20 Aug 2008 09:55:26 +0000 http://www.protocolostomy.com/?p=348#comment-2938 Have you read this book? http://www.intel.com/intelpress/sum_book2.htm I found it really interesting: an attempt to address the lack of patterns in infrastructure design. It really only scratches the surface by describing things like n-tier designs. But it's a start. Great blog post, BTW! Have you read this book? http://www.intel.com/intelpress/sum_book2.htm

I found it really interesting: an attempt to address the lack of patterns in infrastructure design. It really only scratches the surface by describing things like n-tier designs. But it’s a start.

Great blog post, BTW!

]]> By: m0j0 http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/#comment-2667 m0j0 Mon, 04 Aug 2008 16:59:08 +0000 http://www.protocolostomy.com/?p=348#comment-2667 TPOSANA is a great timeless tome for system administrators. I read the first version all the way through, but I haven't yet made it through volume two. As for your point about the paradox between open software and closed network designs, I've often wondered the same thing. Certainly lots of people are under a blanket of secrecy put on them by their employer. In other cases, it's a matter of specialization: in a LOT of places, no single person really knows all there is to know. As for not wanting to expose badness, I tend to find two trends: 1. People readily talk about badness in the hopes that someone can give them a clue about how to make it better, or 2. The people I'm talking to (clients, usually) don't even know the badness exists, otherwise it might not! TPOSANA is a great timeless tome for system administrators. I read the first version all the way through, but I haven’t yet made it through volume two. As for your point about the paradox between open software and closed network designs, I’ve often wondered the same thing. Certainly lots of people are under a blanket of secrecy put on them by their employer. In other cases, it’s a matter of specialization: in a LOT of places, no single person really knows all there is to know.

As for not wanting to expose badness, I tend to find two trends:

1. People readily talk about badness in the hopes that someone can give them a clue about how to make it better, or

2. The people I’m talking to (clients, usually) don’t even know the badness exists, otherwise it might not!

]]> By: Andrew http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/#comment-2666 Andrew Mon, 04 Aug 2008 16:51:08 +0000 http://www.protocolostomy.com/?p=348#comment-2666 Practice of System and Network Administration is probably the best book out there for this. While it doesn't give exact how-to instructions, it is a great general resource for Systems Administrators. I would have loved this book if I had discovered it in the early days of my career. http://www.amazon.com/Practice-System-Network-Administration-2nd/dp/0321492668/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217868163&sr=8-1 Something I have been wondering about is why we like to Open Source our software, but then treat our networks as proprietary information. Security? Shame? Laziness? - A. Practice of System and Network Administration is probably the best book out there for this. While it doesn’t give exact how-to instructions, it is a great general resource for Systems Administrators. I would have loved this book if I had discovered it in the early days of my career.

http://www.amazon.com/Practice-System-Network-Administration-2nd/dp/0321492668/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217868163&sr=8-1

Something I have been wondering about is why we like to Open Source our software, but then treat our networks as proprietary information. Security? Shame? Laziness?

- A.

]]>