New Data Center Standard
mstansberry writes to tell us that the Telecommunications Industry Association (the people who brought you the CAT standards for unshielded twisted pair cabling) recently published a 148 page document meant to standardize the design considerations for every single aspect of a data center. The standard covers everything from site selection to rack mounting methods.
Speaking of CAT standards, has anyone else had a good look at the differences between CAT3, CAT5, etc?
CAT5 just seems to be twisted a little tighter, but CAT6 actually modifies the twist gradually, in a cycle that repeats every few feet, with each pair 90 degrees "out of phase" from the next. Plus theres (sometimes) a plastic "spine" in there to maintain spacing and/or bend radius. It's not obvious to me how varying the twists-per-foot along the cable should help - anyone know?
How boring ... who wants to work somewhere identical to the last place. And identical to your friends' places of work.
... and I'm not bloody paying $250 just to make more work for myself.
How about letting a bit of originality in once in a while?
Oh yeah
---
jon_edwards@spanners4us.com
Be interesting to see if it's useful.
When you specify something like a cable, it's straightfoward to get it right, because the job the cable does and the way it's used is very well understood and doesn't vary between users.
With something complex like a data center, there's so much variance in how they're operated, exactly what they do, where they are, etc...having a standard may well *not* fit everyone's needs, either because their needs were not perceived or understood at the time or because their needs simply cannot be met by the standard.
--
Toby
I'm curious to see what this document contains: whether it's an ITIL-like view of the world (e.g. a data centre runs on change management, capacity management, problem management, ...), a hardware based view (e.g. a data centre needs a raised floor to duct cables, air conditioning, secure access, racks, ...) or something else.
Just not curious enough to pay the price to find out
I wonder if they considered defences to the /. effect when writing this.
Seriously. If all manuals were that expensive there would have been no 'RTFM'. It would have been 'STFM'.
Loose lips lose spit.
I welcome this standard with open arms. I look forward to the not-too-distant day when I will be able to buy 100m(sq) of Standard Data Centre on eBay for $25. No more un-backed-up un-RAIDed hard drives for my mp3s!
// It had been Fat's delusion for years that he could help people. --Philip K. Dick, Valis
[this post intentionally left blank]
I never said I was smart, I just said I was smarter than you
A data center shall consist of hardware, appropriate HVAC, and gigabytes of pornography.
This is great news for people who host servers in colocation facilities.
If you've ever tried to find a place to host your server in the past, you've probably found that not only does the price wildly fluctuate between hosts for no apparent reason, but also it's very difficult to determine exactly what you're getting, even if you take the time and effort to actually visit the site.
I think that the disorganized fashion of colo services allows people to charge ridiculous prices
and get away with things that they wouldn't be able to do in a more stable competitive environment (like charging ridiculous amounts for bandwidth overage and support).
With some sort of standard in place, vendors will be forced to compete on more even ground, prices will be more reasonable, and users won't be afraid to leave their current colo provider because the next one could potentially be even worse.. Not that it will be perfect, of course - just somewhat better.
Does anybody have a link to the document yet, since $1.6 per page of bs is a bit too much.
Slashdot moral concept #7: If item is perceived to suck, stealing - oops sorry, forgot Slashdot moral concept #6 - infringing it is allowed.
Example: "If $band would put out better songs, maybe I'd buy their album. Until then, I will continue to use BitTorrent to get their material."
Greetings and Salutations.
Interestingly enough, a quick google search for "data center design" comes up with more hits than one can shake a stick at, ranging from free to fairly inexpensive (under $100.00). I have to admit that I wonder if THIS magnum opus has anything in it that these OTHER resources do not cover.
It never ceases to amaze me at the number of books out there that are supposed to be useful learning tools that are nothing more than a slightly changed rehash of the man pages for a given program.
Regards
Dave Mundt
YAB - http://blog.beemandave.com/
To "detune" the coils. If the twists were equidistant (especially in the straighter parts) it would resemble a tuned antenna.
-AT
Working in a DevOps shop is like playing in a band made up entirely of keytarists.
My two favs:
/sbin/fsck-y on the console - "It says command not found", says the "engineer".
#1. Driving all the way to the data center at 4 am to find the keyboard plugged into the mouse port - "The keyboard's not responding", says the "engineer".
#2. Driving all the way at to the data center at 3am to see
Installed X and AIM after that and made the "engineers" read the commands off that provided they could get that working.
I agree completely. The "industry standards" for many things are used alot, even if they dont partularly apply to your site. I would love to see people dress the cables in the back of a cabnet with uniform bending radius' and with a proper service loop. I would love to see that in every data center I work in. I wouldn't have to replace cables when a channel bank gets moved. I would love to see this fiber I have to deal with be secured properly and not cinched down hard enough to break your 1st. 6th, 18th, 32nd, and 72nd strand. That would save me a lot of work. I am not going to pay to see what they say... but I bet its just a culmination of proper install techniques and "industry standard" dressings to make the tech's and the installers times easier. Remeber "if it aint pretty, it dont work", err... that's what they told me in BICC anyways.
Stop signs are only Suggestions
From TFA, this is a "checklist" for CIO's. Last thing I need is my PHB having a list to check off and thinking they are requirements instead of suggestions. You never give a PHB this much info. They dont know what you are doing a good part of the time anyways... and a little info is more dangerous than none.
It can be a good idea if the techs get a hold of it though and stop giving my 2 inches of slack on these fiber runs and give be a proper service loop with good cable dressing instead of the rats nests I've had to fix recently.
Stop signs are only Suggestions
Well that sure is an interesting comment. Just how many marks do you think that you can round up who would each pay $250 a pop for a 148 page report because it "is bound to have some good ideas in it"? At that price it wouldn't take too many people to convince me to crank out 150 pages of opnion, particular when the subject is as broad as "every single aspect of a data center". Maybe even sell it at the bargan price of $229.99 and undercut this report (but be close enough in price that some might think mine and the one discussed here are the same). And it wouldn't be like I was stealing their money, would it? It's bound to have some good ideas in it.
I'm an American. I love this country and the freedoms that we used to have.
Being unable to lash out and indeed darned if I woudl ever pay $250 for a datacentre for dummies kidna guide given that every case has to be treated on its own merets.
;0.
I wonder if they cover aspects like power phase balancing given alot of places have 3-phase and we all know how box's move about so the aspect of auditing the balancing across the 3 phases comes in. Why well power costs given you pay for the highest usage over the 3 and then there is the UPS aspects and resiliance aspects.
Oh and DR sites, if you have enough eggs for one basket then you need backup plans.
As you who work in the feild can imagine there are sooo many aspects that need to be looked at and whilst a guidline/crib sheet is always welcome no two datacenters are the same or some manufactuirer would be making a killing selling them in a box
The smallest deatil on one site becomes the largest priority on another. Hell i've even set up a site were we had critical servers spread across the area just to give that extra resiliance incase a train derailed and came thru, albeit remote possibility but still was a potential, and all before 9/11 which in itself shows the level of which murphy's law can stoop.
So whilst this type of thing is nice I do erk when people hold it up as a definitive guide as the only people fooled by that are those that dont know and highup managers and we all know a little knowledge is a dangerous thing.
Still its nice to have stuff like this as long as they are viewed in the context of guidlines and not guides in themselves.
I mean if all doctors were to follow a needle injection guidline of insert needle in left arm 13cm down from main index finger and on the horizontal plane of the wrist joint, not everybody would get the injection into a vien as we are all not exactly the same albiet similiar and indeed some people have no index finger nor left arm.
I personaly wish they would invest more time in a cable standard were the outer colouring deformed in relation to the number of times the cable is bent, now that would in itself be a much more useful input into datacenters in that they could pre-emptivly identify cable that is going past its shelf life or been over abused/used and liable to induce errors.
The document TIA-842 has been issued on April 1, 2005!
I'd not take in too serious consideration this doc!
Maybe Computers will never be as intelligent as Humans.
For sure they won't ever become so stupid. [VR-1988]
Sample scenario:
Hi, your datacenter isn't TIA-compliant. We won't sell you xyz hardware. We won't sell you xyz fire-suppression system.
Hi, I notice your datacenter doesn't have a fire-suppression system. I have to close it, by law, until it's installed.
Hi, I can't install a fire-suppression system until you bring the datacenter up to TIA-standards.
Needless to say, TIA doesn't have to make their spec law for it to be able to screw your datacenter over.
My other car is first.
Don't worry, it's available in PDF. I predict it's available over eDonkey or BitTorrent within the week.
Another one bites the dust
But not all datacenters are equal for a reason. I've seen maybe 20-30 datacenters in the past few years for various clients and they all have different features, different offerings, and different goals.
I'll list a few of the big differences I've seen in my experiences:
Some want to be in the downtown core, close to many businesses, but charging a premium for the space. Others claim that being in the outskirts of the city provide security in the event of any problems (mainly hyped due to 'terrorist attacks').
Some feel the need for N+2 generators, others more. Some feel that a fallback to city power if their PDUs ever fail is good, and others feel there should be a whole other protected power distribution system (at an extremely high cost for something rarely used).
Some like cooling each rack from the top, others blow it up every other isle and suck air down on the opposite. Some cool the whole room, claiming lots and lots of cooling units around the outside does the trick.
Some like the datacenter two stories underground. Others claim that they're a first target for flooding and other problems stereotypically associated with a basement. Others say that the datacenter on the 10th floor of a tower is inaccessable and subject to other security feats of the building.
Some like dedicated buildings, others like quietly slotting themselves in office towers.
A few I went to were monitored from 3000+km's away, and others had 24/7 onsite staff. Some had technical electronic keys, and others a simple mailbox key. Some had biometrics, others just a key.
One I went to even had outter walls capable of withstanding most missiles. Others had windows with only paper over them for security reasons.
Some let you roam freely by a security personelle and simply log equipment, others weigh you on the way out to make sure that you didn't take anything you didn't show up with without signing it out.
The point is each of these serves a very different purpose. If you are going to have lots of untrusted people working on equipment, it's important to make sure nobody takes anything. Each one has its advantage and disadvantage, and I don't think any one of them is 'right'- it's just trying to find a solution to problems that experience has provided.
Is there a right answer with anything? Who is to say that any answer is right or wrong? They're just different solutions to the problem. If power stays up, systems are secure, systems get cooled, and the network is available, who is to say the solution is wrong?
-M
when you see the word 'Linux', drink!
To me, that does not imply buying a cheap rack, getting a T1 and a router, and sticking 5 servers in whatever closet is available in your office space.
You just described our setup almost exactly.
Above sea level. Check.
Somewhere the US/Chinese government won't be monitor ing everything... still looking.
- Adam L. Beberg - The Cosm Project - http://www.mithral.com/