<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_07_06_2244205</id>
	<title>Data Center Power Failures Mount</title>
	<author>timothy</author>
	<datestamp>1246881480000</datestamp>
	<htmltext><a href="http://www.gamehostingguide.com/" rel="nofollow">1sockchuck</a> writes <i>"It was a bad week to be a piece of electrical equipment inside a major data center. There have been <a href="http://www.datacenterknowledge.com/archives/2009/07/06/the-day-after-a-brutal-week-for-uptime/">five major incidents</a> in the past week in which generator or UPS failures have caused data center power outages that left customers offline. Generators were apparently the culprit in a <a href="http://www.techcrunch.com/2009/06/29/yes-rackspace-is-down-and-so-are-many-of-your-favorite-sites/">Rackspace outage</a> in Dallas and a <a href="http://www.techflash.com/microsoft/Seattle\_data\_center\_fire\_knocks\_out\_Bing\_Travel\_other\_Web\_sites\_49876777.html">fire at Fisher Plaza</a> in Seattle (which <a href="http://tech.slashdot.org/story/09/07/03/1637228/Seattle-Data-Center-Outage-Disrupts-E-Commerce">disrupted e-commerce</a> Friday), while UPS units were cited in brief <a href="http://www.datacenterknowledge.com/archives/2009/07/02/equinix-hit-by-outages-in-sydney-paris/">outages at Equinix</a> data centers in Sydney and Paris on Thursday and a <a href="http://www.datacenterknowledge.com/archives/2009/07/06/fire-causes-outage-at-toronto-carrier-hotel/">fire at 151 Front Street</a> in Toronto early Sunday. Google App Engine also had a <a href="http://www.theregister.co.uk/2009/07/06/dziuba\_google\_app\_engine/">lengthy outage Thursday</a>, but it was attributed to a data store failure."</i></htmltext>
<tokenext>1sockchuck writes " It was a bad week to be a piece of electrical equipment inside a major data center .
There have been five major incidents in the past week in which generator or UPS failures have caused data center power outages that left customers offline .
Generators were apparently the culprit in a Rackspace outage in Dallas and a fire at Fisher Plaza in Seattle ( which disrupted e-commerce Friday ) , while UPS units were cited in brief outages at Equinix data centers in Sydney and Paris on Thursday and a fire at 151 Front Street in Toronto early Sunday .
Google App Engine also had a lengthy outage Thursday , but it was attributed to a data store failure .
"</tokentext>
<sentencetext>1sockchuck writes "It was a bad week to be a piece of electrical equipment inside a major data center.
There have been five major incidents in the past week in which generator or UPS failures have caused data center power outages that left customers offline.
Generators were apparently the culprit in a Rackspace outage in Dallas and a fire at Fisher Plaza in Seattle (which disrupted e-commerce Friday), while UPS units were cited in brief outages at Equinix data centers in Sydney and Paris on Thursday and a fire at 151 Front Street in Toronto early Sunday.
Google App Engine also had a lengthy outage Thursday, but it was attributed to a data store failure.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601867</id>
	<title>check this out!!!</title>
	<author>Anonymous</author>
	<datestamp>1246885740000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Eric felt his scrotum contract in its latest desperate attempt to keep his testicles warm. This hospital, wherever it was, was damned drafty.</p><p>It didn't help that the nurses on his floor, who had been treating Eric like a complete bitch, liked to keep the air conditioning cranked up. Or was it just his room? He noticed they pulled their cardigans and sweaters around them only when they came to see him.</p><p>"Nurse! Nurse!" Eric shouted. "Excuse me, nurse?!"</p><p>Eric heard a chair creak, followed by footsteps coming down the hall. They were quick around here, one of the only good things Eric had yet noticed. Perhaps it was because of his celebrity status.</p><p>"Yes?" the nurse said, crossing her goose-pimpled arms.</p><p>"Nurse, it's damn cold in here," Eric said. "And I think my pain medication is wearing off. Can I have some more pills?"</p><p>Her beady eyes, set atop wrinkled, puffy cheeks, lasered him in his bed. This was the sixth time Eric had shouted for her since her shift began. She didn't know him well but she was definitely starting to hate him.</p><p>"Oh! And my urinal needs emptied!" Eric added.</p><p>The nurse pursed her lips and folded her arms without breaking eye contact, "get fucked" in body language.</p><p>Eric smiled a crooked, leering grin at her and winked in a bid to charm her into emptying his piss. The nurse wondered if he was about to have another seizure.</p><p>She picked up Eric's chart, flipped through it, and replaced it.</p><p>"Mr. Raymond," the nurse said, "you're not due for more pain medication for two more hours."</p><p>Eric's mustache, orange and drooping, twitched.</p><p>"Do you need your bandages looked at?"</p><p>Eric shifted in his bed, stiff and uncomfortable. He slowly, awkwardly, stretched his hospital gown down over his knees.</p><p>"Nooo, no, no I don't," Eric said. "My bandages are just fine."</p><p>"Fine then," the nurse said. "I'll get your urinal. Do you need anything else?"</p><p>Eric watched as the nurse lifted his urinal carefully off of his lunch tray. It was completely full1,000 cubic centimeters, one full quart of piss and mounding at the top.</p><p>The nurse stifled a gag as she slowly made her way into the restroom.</p><p>"This damn IV has me swimming!" Eric called after her with a quick laugh.</p><p>He heard her pouring his urine into the toilet and felt the urge to go again. It had been dark brown, viscous, and smelled to high heaven like sick wet meat. He really hoped whatever they had him on was working.</p><p>She returned from the restroom and replaced Eric's urinal.</p><p>"I'll be back when it's time for your medication," she said. "Dinner is in an hour."</p><p>With that she left until, she knew too well, the next time Eric grew bored or irritated.</p><p>Feeling as anxious as ever, Eric reached for <a href="http://www.catb.org/~esr/hardware.html" title="catb.org" rel="nofollow">billywig</a> [catb.org], his <a href="http://support.apple.com/kb/SP126" title="apple.com" rel="nofollow">blueberry iBook</a> [apple.com], which had finally charged. He hit the start button and watched <a href="http://us.fixstars.com/products/ydl/" title="fixstars.com" rel="nofollow">Yellow Dog Linux</a> [fixstars.com] slowly crawl off of the hard drive into RAM.</p><p>Thank god this hospital had wifi. Thank god he had an Airport card in his iBook.</p><p> <a href="http://www.google.com/search?q=brown+piss" title="google.com" rel="nofollow">http://www.google.com/search?q=brown+piss</a> [google.com] </p><p>"Nope."</p><p> <a href="http://www.google.com/search?q=my+piss+is+brown" title="google.com" rel="nofollow">http://www.google.com/search?q=my+piss+is+brown</a> [google.com] </p><p>"Hmm Nope."</p><p> <a href="http://www.google.com/search?q=my+piss+is+brown+std" title="google.com" rel="nofollow">http://www.google.com/search?q=my+piss+is+brown+std</a> [google.com] </p><p>"Nope."</p><p> <a href="http://www.google.com/search?q=my+piss+is+brown+and+smells+like+rotting+meat+std" title="google.com" rel="nofollow">http://www.google.com/search?q=my+piss+is+brown+and+smells+like+rotting+meat+std</a> [google.com] </p><p>Eric was having no luck. The more he optimized his Google searches, he noted with alarm, the less relevant his search hits became.</p><blockquote><div><p>foul smelling like decay meat and at times like grated yam. this odor<nobr> <wbr></nobr>... and fifth day i see dirth brown dischargeAbnormal discharge from the nipple<nobr> <wbr></nobr>.... the air asking what that rotten meat smell was...and the consequent search<nobr> <wbr></nobr>... So, my UA (urine analysis) came back abnormal </p></div> </blockquote><p>"Jesus Christ!" Eric muttered to himself as he squinted at his iBook's twelve inch screen. "I don't think I have anything coming out of my nipples!"</p><p>Making sure his iBook was steady, he gingerly squeezed his left pectoral.</p><p>"Nope."</p><p>Eric command-tabbed back to vi, where he was typing "RFI on brown piss that smells like rotting meat" to post to <a href="http://esr.ibiblio.org/" title="ibiblio.org" rel="nofollow">his blog</a> [ibiblio.org], when there was a knock at the door.</p><p>"Mr. Raymond?"</p><p>It was the nurse.</p><p>"There's someone here to see you."</p><p>Finally, company! A hacker mind like Eric's was not used to boredom. He needed plenty of <a href="http://www.trollaxor.com/2009/06/eric-emad-iranian-hackers-cyber-buddies.html" title="trollaxor.com" rel="nofollow">Iranian hackers</a> [trollaxor.com] to chat with, a cave full of LARP buddies, or, optimally, a <a href="http://www.trollaxor.com/2001/12/linux-party.html" title="trollaxor.com" rel="nofollow">Linux party</a> [trollaxor.com]. <i>Not</i> the sanitation of lonely, well-lit hospital.</p><p>A second later the door opened again and in walked not Eric's LARP troop or Linux party, but something far less arousing: a New Jersey state police officer.</p><p>"Eric Raymond?" the officer asked. He was 6'2" and built like the Mack trucks he probably ticketed on a daily basis.</p><p>"Yes, sir, that's me, officer," Eric stammered. He hated being dominated.</p><p>"You're under arrest for lewd conduct, public indecency, and conspiracy to solicit," the officer said. The tone in his voice told Eric not to interrupt. "You have the right to remain silent. Anything you say"</p><p>Eric's mind wandered. He had to call his wife. She was his attorney and had dealt with this sort of thing before. He had to keep this quiet.</p><p>Eric decided then and there to be as cooperative as possible.</p><p>"Do you understand these rights, Mr. Raymond?"</p><p>"Yeah, sure," Eric said. "But I'd like to share info about the other party involved in this incident."</p><p>"Go ahead?" the officer said, not expecting Eric's offer.</p><p>"The other party," Eric said, "is a man named Emad, an Iranian hacker, quite possible in this country illegally. His email address is <a href="mailto:emad.opensores@gmail.com" title="mailto" rel="nofollow">emad.opensores@gmail.com</a> [mailto] and his AIM handle is <a href="aim:goimscreennameiran2hax0rc0ck" title="aim" rel="nofollow">iran2hax0rc0ck</a> [aim]."</p><p>"Any idea who the other parties involved were?" the trooper asked, taking his notepad out.</p><p>"Other parties? There were no other parties. Just Emad and I."</p><p>"Mr Raymond," the trooper said, "you were the victim of sexual assault last night."</p><p>Eric's left eye twitched. It was usually him, with his Glock and J&#x00E4;germeister, in charge of the proceedings. Not the other way around. He felt so powerless.</p><p>"You'll be arraigned upon your release from the hospital. Do you understand that?"</p><p>"Sure," Eric said, "but why do you think there were other parties? It was just Emad and I the entire time."</p><p>"Mr. Raymond," the trooper said while replacing his notebook, "our crime lab extracted the DNA of two other people from your wounds."</p><p>Eric sweated, cold and salty, and his world spun. Who else had been there?</p><p>"Also," the trooper said, producing a plastic bag, "do you know what this is?"</p><p>He handed the object to Eric, who turned it back and forth. It reflected the room's lights weakly through the baggie.</p><p>"It's Ubuntu," Eric said softly.</p><p>"Ubuntu? What's that?" the trooper said.</p><p>"It's a Linux distribution," Eric said unhelpfully. "Where did you get it?"</p><p>He noticed the version number on the CD face as he passed it back to the trooper. 9.10<i>Karmic Koala</i>.</p><p>The trooper looked away before he spoke.</p><p>"The doctors removed it from deep inside your ass."</p></div>
	</htmltext>
<tokenext>Eric felt his scrotum contract in its latest desperate attempt to keep his testicles warm .
This hospital , wherever it was , was damned drafty.It did n't help that the nurses on his floor , who had been treating Eric like a complete bitch , liked to keep the air conditioning cranked up .
Or was it just his room ?
He noticed they pulled their cardigans and sweaters around them only when they came to see him. " Nurse !
Nurse ! " Eric shouted .
" Excuse me , nurse ? !
" Eric heard a chair creak , followed by footsteps coming down the hall .
They were quick around here , one of the only good things Eric had yet noticed .
Perhaps it was because of his celebrity status. " Yes ?
" the nurse said , crossing her goose-pimpled arms .
" Nurse , it 's damn cold in here , " Eric said .
" And I think my pain medication is wearing off .
Can I have some more pills ?
" Her beady eyes , set atop wrinkled , puffy cheeks , lasered him in his bed .
This was the sixth time Eric had shouted for her since her shift began .
She did n't know him well but she was definitely starting to hate him. " Oh !
And my urinal needs emptied !
" Eric added.The nurse pursed her lips and folded her arms without breaking eye contact , " get fucked " in body language.Eric smiled a crooked , leering grin at her and winked in a bid to charm her into emptying his piss .
The nurse wondered if he was about to have another seizure.She picked up Eric 's chart , flipped through it , and replaced it. " Mr .
Raymond , " the nurse said , " you 're not due for more pain medication for two more hours .
" Eric 's mustache , orange and drooping , twitched .
" Do you need your bandages looked at ?
" Eric shifted in his bed , stiff and uncomfortable .
He slowly , awkwardly , stretched his hospital gown down over his knees .
" Nooo , no , no I do n't , " Eric said .
" My bandages are just fine .
" " Fine then , " the nurse said .
" I 'll get your urinal .
Do you need anything else ?
" Eric watched as the nurse lifted his urinal carefully off of his lunch tray .
It was completely full1,000 cubic centimeters , one full quart of piss and mounding at the top.The nurse stifled a gag as she slowly made her way into the restroom .
" This damn IV has me swimming !
" Eric called after her with a quick laugh.He heard her pouring his urine into the toilet and felt the urge to go again .
It had been dark brown , viscous , and smelled to high heaven like sick wet meat .
He really hoped whatever they had him on was working.She returned from the restroom and replaced Eric 's urinal .
" I 'll be back when it 's time for your medication , " she said .
" Dinner is in an hour .
" With that she left until , she knew too well , the next time Eric grew bored or irritated.Feeling as anxious as ever , Eric reached for billywig [ catb.org ] , his blueberry iBook [ apple.com ] , which had finally charged .
He hit the start button and watched Yellow Dog Linux [ fixstars.com ] slowly crawl off of the hard drive into RAM.Thank god this hospital had wifi .
Thank god he had an Airport card in his iBook .
http : //www.google.com/search ? q = brown + piss [ google.com ] " Nope .
" http : //www.google.com/search ? q = my + piss + is + brown [ google.com ] " Hmm Nope .
" http : //www.google.com/search ? q = my + piss + is + brown + std [ google.com ] " Nope .
" http : //www.google.com/search ? q = my + piss + is + brown + and + smells + like + rotting + meat + std [ google.com ] Eric was having no luck .
The more he optimized his Google searches , he noted with alarm , the less relevant his search hits became.foul smelling like decay meat and at times like grated yam .
this odor ... and fifth day i see dirth brown dischargeAbnormal discharge from the nipple .... the air asking what that rotten meat smell was...and the consequent search ... So , my UA ( urine analysis ) came back abnormal " Jesus Christ !
" Eric muttered to himself as he squinted at his iBook 's twelve inch screen .
" I do n't think I have anything coming out of my nipples !
" Making sure his iBook was steady , he gingerly squeezed his left pectoral. " Nope .
" Eric command-tabbed back to vi , where he was typing " RFI on brown piss that smells like rotting meat " to post to his blog [ ibiblio.org ] , when there was a knock at the door. " Mr .
Raymond ? " It was the nurse .
" There 's someone here to see you .
" Finally , company !
A hacker mind like Eric 's was not used to boredom .
He needed plenty of Iranian hackers [ trollaxor.com ] to chat with , a cave full of LARP buddies , or , optimally , a Linux party [ trollaxor.com ] .
Not the sanitation of lonely , well-lit hospital.A second later the door opened again and in walked not Eric 's LARP troop or Linux party , but something far less arousing : a New Jersey state police officer .
" Eric Raymond ?
" the officer asked .
He was 6'2 " and built like the Mack trucks he probably ticketed on a daily basis .
" Yes , sir , that 's me , officer , " Eric stammered .
He hated being dominated .
" You 're under arrest for lewd conduct , public indecency , and conspiracy to solicit , " the officer said .
The tone in his voice told Eric not to interrupt .
" You have the right to remain silent .
Anything you say " Eric 's mind wandered .
He had to call his wife .
She was his attorney and had dealt with this sort of thing before .
He had to keep this quiet.Eric decided then and there to be as cooperative as possible .
" Do you understand these rights , Mr .
Raymond ? " " Yeah , sure , " Eric said .
" But I 'd like to share info about the other party involved in this incident .
" " Go ahead ?
" the officer said , not expecting Eric 's offer .
" The other party , " Eric said , " is a man named Emad , an Iranian hacker , quite possible in this country illegally .
His email address is emad.opensores @ gmail.com [ mailto ] and his AIM handle is iran2hax0rc0ck [ aim ] .
" " Any idea who the other parties involved were ?
" the trooper asked , taking his notepad out .
" Other parties ?
There were no other parties .
Just Emad and I .
" " Mr Raymond , " the trooper said , " you were the victim of sexual assault last night .
" Eric 's left eye twitched .
It was usually him , with his Glock and J   germeister , in charge of the proceedings .
Not the other way around .
He felt so powerless .
" You 'll be arraigned upon your release from the hospital .
Do you understand that ?
" " Sure , " Eric said , " but why do you think there were other parties ?
It was just Emad and I the entire time. " " Mr .
Raymond , " the trooper said while replacing his notebook , " our crime lab extracted the DNA of two other people from your wounds .
" Eric sweated , cold and salty , and his world spun .
Who else had been there ?
" Also , " the trooper said , producing a plastic bag , " do you know what this is ?
" He handed the object to Eric , who turned it back and forth .
It reflected the room 's lights weakly through the baggie .
" It 's Ubuntu , " Eric said softly. " Ubuntu ?
What 's that ?
" the trooper said .
" It 's a Linux distribution , " Eric said unhelpfully .
" Where did you get it ?
" He noticed the version number on the CD face as he passed it back to the trooper .
9.10Karmic Koala.The trooper looked away before he spoke .
" The doctors removed it from deep inside your ass .
"</tokentext>
<sentencetext>Eric felt his scrotum contract in its latest desperate attempt to keep his testicles warm.
This hospital, wherever it was, was damned drafty.It didn't help that the nurses on his floor, who had been treating Eric like a complete bitch, liked to keep the air conditioning cranked up.
Or was it just his room?
He noticed they pulled their cardigans and sweaters around them only when they came to see him."Nurse!
Nurse!" Eric shouted.
"Excuse me, nurse?!
"Eric heard a chair creak, followed by footsteps coming down the hall.
They were quick around here, one of the only good things Eric had yet noticed.
Perhaps it was because of his celebrity status."Yes?
" the nurse said, crossing her goose-pimpled arms.
"Nurse, it's damn cold in here," Eric said.
"And I think my pain medication is wearing off.
Can I have some more pills?
"Her beady eyes, set atop wrinkled, puffy cheeks, lasered him in his bed.
This was the sixth time Eric had shouted for her since her shift began.
She didn't know him well but she was definitely starting to hate him."Oh!
And my urinal needs emptied!
" Eric added.The nurse pursed her lips and folded her arms without breaking eye contact, "get fucked" in body language.Eric smiled a crooked, leering grin at her and winked in a bid to charm her into emptying his piss.
The nurse wondered if he was about to have another seizure.She picked up Eric's chart, flipped through it, and replaced it."Mr.
Raymond," the nurse said, "you're not due for more pain medication for two more hours.
"Eric's mustache, orange and drooping, twitched.
"Do you need your bandages looked at?
"Eric shifted in his bed, stiff and uncomfortable.
He slowly, awkwardly, stretched his hospital gown down over his knees.
"Nooo, no, no I don't," Eric said.
"My bandages are just fine.
""Fine then," the nurse said.
"I'll get your urinal.
Do you need anything else?
"Eric watched as the nurse lifted his urinal carefully off of his lunch tray.
It was completely full1,000 cubic centimeters, one full quart of piss and mounding at the top.The nurse stifled a gag as she slowly made her way into the restroom.
"This damn IV has me swimming!
" Eric called after her with a quick laugh.He heard her pouring his urine into the toilet and felt the urge to go again.
It had been dark brown, viscous, and smelled to high heaven like sick wet meat.
He really hoped whatever they had him on was working.She returned from the restroom and replaced Eric's urinal.
"I'll be back when it's time for your medication," she said.
"Dinner is in an hour.
"With that she left until, she knew too well, the next time Eric grew bored or irritated.Feeling as anxious as ever, Eric reached for billywig [catb.org], his blueberry iBook [apple.com], which had finally charged.
He hit the start button and watched Yellow Dog Linux [fixstars.com] slowly crawl off of the hard drive into RAM.Thank god this hospital had wifi.
Thank god he had an Airport card in his iBook.
http://www.google.com/search?q=brown+piss [google.com] "Nope.
" http://www.google.com/search?q=my+piss+is+brown [google.com] "Hmm Nope.
" http://www.google.com/search?q=my+piss+is+brown+std [google.com] "Nope.
" http://www.google.com/search?q=my+piss+is+brown+and+smells+like+rotting+meat+std [google.com] Eric was having no luck.
The more he optimized his Google searches, he noted with alarm, the less relevant his search hits became.foul smelling like decay meat and at times like grated yam.
this odor ... and fifth day i see dirth brown dischargeAbnormal discharge from the nipple .... the air asking what that rotten meat smell was...and the consequent search ... So, my UA (urine analysis) came back abnormal  "Jesus Christ!
" Eric muttered to himself as he squinted at his iBook's twelve inch screen.
"I don't think I have anything coming out of my nipples!
"Making sure his iBook was steady, he gingerly squeezed his left pectoral."Nope.
"Eric command-tabbed back to vi, where he was typing "RFI on brown piss that smells like rotting meat" to post to his blog [ibiblio.org], when there was a knock at the door."Mr.
Raymond?"It was the nurse.
"There's someone here to see you.
"Finally, company!
A hacker mind like Eric's was not used to boredom.
He needed plenty of Iranian hackers [trollaxor.com] to chat with, a cave full of LARP buddies, or, optimally, a Linux party [trollaxor.com].
Not the sanitation of lonely, well-lit hospital.A second later the door opened again and in walked not Eric's LARP troop or Linux party, but something far less arousing: a New Jersey state police officer.
"Eric Raymond?
" the officer asked.
He was 6'2" and built like the Mack trucks he probably ticketed on a daily basis.
"Yes, sir, that's me, officer," Eric stammered.
He hated being dominated.
"You're under arrest for lewd conduct, public indecency, and conspiracy to solicit," the officer said.
The tone in his voice told Eric not to interrupt.
"You have the right to remain silent.
Anything you say"Eric's mind wandered.
He had to call his wife.
She was his attorney and had dealt with this sort of thing before.
He had to keep this quiet.Eric decided then and there to be as cooperative as possible.
"Do you understand these rights, Mr.
Raymond?""Yeah, sure," Eric said.
"But I'd like to share info about the other party involved in this incident.
""Go ahead?
" the officer said, not expecting Eric's offer.
"The other party," Eric said, "is a man named Emad, an Iranian hacker, quite possible in this country illegally.
His email address is emad.opensores@gmail.com [mailto] and his AIM handle is iran2hax0rc0ck [aim].
""Any idea who the other parties involved were?
" the trooper asked, taking his notepad out.
"Other parties?
There were no other parties.
Just Emad and I.
""Mr Raymond," the trooper said, "you were the victim of sexual assault last night.
"Eric's left eye twitched.
It was usually him, with his Glock and Jägermeister, in charge of the proceedings.
Not the other way around.
He felt so powerless.
"You'll be arraigned upon your release from the hospital.
Do you understand that?
""Sure," Eric said, "but why do you think there were other parties?
It was just Emad and I the entire time.""Mr.
Raymond," the trooper said while replacing his notebook, "our crime lab extracted the DNA of two other people from your wounds.
"Eric sweated, cold and salty, and his world spun.
Who else had been there?
"Also," the trooper said, producing a plastic bag, "do you know what this is?
"He handed the object to Eric, who turned it back and forth.
It reflected the room's lights weakly through the baggie.
"It's Ubuntu," Eric said softly."Ubuntu?
What's that?
" the trooper said.
"It's a Linux distribution," Eric said unhelpfully.
"Where did you get it?
"He noticed the version number on the CD face as he passed it back to the trooper.
9.10Karmic Koala.The trooper looked away before he spoke.
"The doctors removed it from deep inside your ass.
"
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602585</id>
	<title>Re:Be Redundant!</title>
	<author>mcrbids</author>
	<datestamp>1246890540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's required that you have two name servers when you register a domain name.</p><p>Physical separation is not required. It's just good practice. (I do, in separate cities on different ISP networks) Having separate nameservers in different geo regions is implicit because you have to register at least two for each domain name. I've seen some people game this by having a single nameserver with two IP addresses, which strikes me as the height of stupidity, but it's not happening on my watch.</p></htmltext>
<tokenext>It 's required that you have two name servers when you register a domain name.Physical separation is not required .
It 's just good practice .
( I do , in separate cities on different ISP networks ) Having separate nameservers in different geo regions is implicit because you have to register at least two for each domain name .
I 've seen some people game this by having a single nameserver with two IP addresses , which strikes me as the height of stupidity , but it 's not happening on my watch .</tokentext>
<sentencetext>It's required that you have two name servers when you register a domain name.Physical separation is not required.
It's just good practice.
(I do, in separate cities on different ISP networks) Having separate nameservers in different geo regions is implicit because you have to register at least two for each domain name.
I've seen some people game this by having a single nameserver with two IP addresses, which strikes me as the height of stupidity, but it's not happening on my watch.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603911</id>
	<title>Re:If only you had listened...</title>
	<author>Schemat1c</author>
	<datestamp>1246900740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I'm guessing that the majority of these were caused by leaks or spilled drinks. If only you guys had listened to me and gotten Zorbeez(tm)[SOAKS UP 10x ITS OWN WEIGHT!] [wikipedia.org].</p> </div><p>Even that wouldn't work. What you have here is your textbook Pepsi Syndrome and only a President in yellow booties can fix it.</p></div>
	</htmltext>
<tokenext>I 'm guessing that the majority of these were caused by leaks or spilled drinks .
If only you guys had listened to me and gotten Zorbeez ( tm ) [ SOAKS UP 10x ITS OWN WEIGHT !
] [ wikipedia.org ] .
Even that would n't work .
What you have here is your textbook Pepsi Syndrome and only a President in yellow booties can fix it .</tokentext>
<sentencetext>I'm guessing that the majority of these were caused by leaks or spilled drinks.
If only you guys had listened to me and gotten Zorbeez(tm)[SOAKS UP 10x ITS OWN WEIGHT!
] [wikipedia.org].
Even that wouldn't work.
What you have here is your textbook Pepsi Syndrome and only a President in yellow booties can fix it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601915</id>
	<title>Correlation proves causation</title>
	<author>Anonymous</author>
	<datestamp>1246886040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Installing a generator or UPS causes an accident sooner than you'd experience without having a generator or UPS. Safety measures cause accidents. See, not(correlation does not imply causation). We slashdotters have always known this to be true. Heretics beware!</p></htmltext>
<tokenext>Installing a generator or UPS causes an accident sooner than you 'd experience without having a generator or UPS .
Safety measures cause accidents .
See , not ( correlation does not imply causation ) .
We slashdotters have always known this to be true .
Heretics beware !</tokentext>
<sentencetext>Installing a generator or UPS causes an accident sooner than you'd experience without having a generator or UPS.
Safety measures cause accidents.
See, not(correlation does not imply causation).
We slashdotters have always known this to be true.
Heretics beware!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603507</id>
	<title>Re:Be Redundant!</title>
	<author>ls671</author>
	<datestamp>1246897500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Best solution for big outfits is to have at least this setup:</p><p>1) One party being the main contractor. This party doesn't do ANY hosting per say but only manages the fail-over strategy, doing the relevant testing once in a while.</p><p>2) A second party being involved in hosting and managing data centers.</p><p>3) A third party, completely independent from party 2, a competitor of 2 is preferable, which also does hosting and manages data centers.</p><p>It is the same principle when you bring redundant internet connectivity to a building :</p><p>1) Have the fiber from one provider come into the building from, say, the north side of the building.</p><p>2) Have a competitor, unrelated business wise, that doesn't use the same upstream providers bring his fibers in from the South side of the building.</p><p>Putting all your eggs in the same basket by dealing with only one business entity constitute a less robust solution.</p></htmltext>
<tokenext>Best solution for big outfits is to have at least this setup : 1 ) One party being the main contractor .
This party does n't do ANY hosting per say but only manages the fail-over strategy , doing the relevant testing once in a while.2 ) A second party being involved in hosting and managing data centers.3 ) A third party , completely independent from party 2 , a competitor of 2 is preferable , which also does hosting and manages data centers.It is the same principle when you bring redundant internet connectivity to a building : 1 ) Have the fiber from one provider come into the building from , say , the north side of the building.2 ) Have a competitor , unrelated business wise , that does n't use the same upstream providers bring his fibers in from the South side of the building.Putting all your eggs in the same basket by dealing with only one business entity constitute a less robust solution .</tokentext>
<sentencetext>Best solution for big outfits is to have at least this setup:1) One party being the main contractor.
This party doesn't do ANY hosting per say but only manages the fail-over strategy, doing the relevant testing once in a while.2) A second party being involved in hosting and managing data centers.3) A third party, completely independent from party 2, a competitor of 2 is preferable, which also does hosting and manages data centers.It is the same principle when you bring redundant internet connectivity to a building :1) Have the fiber from one provider come into the building from, say, the north side of the building.2) Have a competitor, unrelated business wise, that doesn't use the same upstream providers bring his fibers in from the South side of the building.Putting all your eggs in the same basket by dealing with only one business entity constitute a less robust solution.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605331</id>
	<title>Sunspots, Anyone?</title>
	<author>Craig Milo Rogers</author>
	<datestamp>1246962240000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>All these data centers failed at roughly the same time as the <a href="http://www.space.com/scienceastronomy/090706-sunspot-activity.html" title="space.com" rel="nofollow">sunspots returned</a> [space.com], but that's just a coincidence, right?</p></htmltext>
<tokenext>All these data centers failed at roughly the same time as the sunspots returned [ space.com ] , but that 's just a coincidence , right ?</tokentext>
<sentencetext>All these data centers failed at roughly the same time as the sunspots returned [space.com], but that's just a coincidence, right?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159</id>
	<title>UPSs cause more failures than they prevent!</title>
	<author>nmg196</author>
	<datestamp>1246972020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm almost thinking of taking UPS out of the loop here. They cause nearly all the downtime we have. It would be better to just let the machines power off rather than allowing the UPSs to CAUSE the machines to be taken offline.  At least if the UPS isn't in circuit, the machines power back up again when the power comes back, but if there's a fault with the UPS or it's batteries, then the machines stay offline until the batteries have been replaced.</p><p>Why the hell the idiots that design UPSs seem to think it's a good idea to prevent them turning on if they sense a problem with the batteries is beyond me. Why not let the machines power back up but just make a loud beeping noise until the batteries are fixed. Don't they realise that most of the time the UPS will only properly test the batteries when there's an actual power cut?  On APC units (and most others) the periodic self test function uses your SERVERS as the test load! So if the batteries can't deliver the current, your servers get turned off just due to a routine TEST! Why can't they fit an internal dummy load like a small ceramic heater or something - it's only on about 5 seconds so it won't even get hot.</p><p>Yes, APC, I'm talking to you.  I've even switched suppliers thinking it must only affect APC units, but it seems all others I've tried have the same issues.</p></htmltext>
<tokenext>I 'm almost thinking of taking UPS out of the loop here .
They cause nearly all the downtime we have .
It would be better to just let the machines power off rather than allowing the UPSs to CAUSE the machines to be taken offline .
At least if the UPS is n't in circuit , the machines power back up again when the power comes back , but if there 's a fault with the UPS or it 's batteries , then the machines stay offline until the batteries have been replaced.Why the hell the idiots that design UPSs seem to think it 's a good idea to prevent them turning on if they sense a problem with the batteries is beyond me .
Why not let the machines power back up but just make a loud beeping noise until the batteries are fixed .
Do n't they realise that most of the time the UPS will only properly test the batteries when there 's an actual power cut ?
On APC units ( and most others ) the periodic self test function uses your SERVERS as the test load !
So if the batteries ca n't deliver the current , your servers get turned off just due to a routine TEST !
Why ca n't they fit an internal dummy load like a small ceramic heater or something - it 's only on about 5 seconds so it wo n't even get hot.Yes , APC , I 'm talking to you .
I 've even switched suppliers thinking it must only affect APC units , but it seems all others I 've tried have the same issues .</tokentext>
<sentencetext>I'm almost thinking of taking UPS out of the loop here.
They cause nearly all the downtime we have.
It would be better to just let the machines power off rather than allowing the UPSs to CAUSE the machines to be taken offline.
At least if the UPS isn't in circuit, the machines power back up again when the power comes back, but if there's a fault with the UPS or it's batteries, then the machines stay offline until the batteries have been replaced.Why the hell the idiots that design UPSs seem to think it's a good idea to prevent them turning on if they sense a problem with the batteries is beyond me.
Why not let the machines power back up but just make a loud beeping noise until the batteries are fixed.
Don't they realise that most of the time the UPS will only properly test the batteries when there's an actual power cut?
On APC units (and most others) the periodic self test function uses your SERVERS as the test load!
So if the batteries can't deliver the current, your servers get turned off just due to a routine TEST!
Why can't they fit an internal dummy load like a small ceramic heater or something - it's only on about 5 seconds so it won't even get hot.Yes, APC, I'm talking to you.
I've even switched suppliers thinking it must only affect APC units, but it seems all others I've tried have the same issues.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604313</id>
	<title>Re: DC Outages</title>
	<author>Anonymous</author>
	<datestamp>1246905780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><b>cheap, fast, reliable</b></p><p>pick one</p></htmltext>
<tokenext>cheap , fast , reliablepick one</tokentext>
<sentencetext>cheap, fast, reliablepick one</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602005</id>
	<title>XO Communications  Genesis Hosting</title>
	<author>newgalactic</author>
	<datestamp>1246886520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We had an outage today.  Our servers are hosted with Genesis Hosting, which suffered an outage from their ISP; XO Communications in Chicago.  Anyone know what happened?</htmltext>
<tokenext>We had an outage today .
Our servers are hosted with Genesis Hosting , which suffered an outage from their ISP ; XO Communications in Chicago .
Anyone know what happened ?</tokentext>
<sentencetext>We had an outage today.
Our servers are hosted with Genesis Hosting, which suffered an outage from their ISP; XO Communications in Chicago.
Anyone know what happened?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602519</id>
	<title>Former critical power field engineer here...</title>
	<author>asackett</author>
	<datestamp>1246889760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>... saying that it's time to reconsider cost cutting measures. In 15 years in the field I never saw a well designed and well maintained critical power system drop its load. I saw many poorly designed and/or poorly maintained systems drop loads, even catching fire in the process. One such fire in a poorly designed and poorly maintained system took the entire building with it, data center and all. The fire suppression system in that one was never upgraded to meet the needs of the "repurposed space" which was originally a light industrial/office space.</p></htmltext>
<tokenext>... saying that it 's time to reconsider cost cutting measures .
In 15 years in the field I never saw a well designed and well maintained critical power system drop its load .
I saw many poorly designed and/or poorly maintained systems drop loads , even catching fire in the process .
One such fire in a poorly designed and poorly maintained system took the entire building with it , data center and all .
The fire suppression system in that one was never upgraded to meet the needs of the " repurposed space " which was originally a light industrial/office space .</tokentext>
<sentencetext>... saying that it's time to reconsider cost cutting measures.
In 15 years in the field I never saw a well designed and well maintained critical power system drop its load.
I saw many poorly designed and/or poorly maintained systems drop loads, even catching fire in the process.
One such fire in a poorly designed and poorly maintained system took the entire building with it, data center and all.
The fire suppression system in that one was never upgraded to meet the needs of the "repurposed space" which was originally a light industrial/office space.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602969</id>
	<title>go4t</title>
	<author>Anonymous</author>
	<datestamp>1246893720000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><A HREF="http://goat.cx/" title="goat.cx" rel="nofollow">CORPSE TURNED OVER Good to write you Raymond in his the future holds hobby. It was all fucking surprise, To get involved in goals I personally give other people under the GPL. troubles of those I burnt out. I in any way related Goodbye...she had Rapid, by BSDI who sell The reaper BSD's I see the same things I still windows, SUN or Very sick and its Users all over the on slashdot.org to die. I will jam to die. I will jam isn't a lemonade Problems with lube or we sell simple solution all parties it's benefits of being The bottoms butt Where It was when was what got me percent of the *BSD , a proud member the resources that by simple fucking bulk of the FreeBSD bunch of retarded man walking. It's</a> [goat.cx]</htmltext>
<tokenext>CORPSE TURNED OVER Good to write you Raymond in his the future holds hobby .
It was all fucking surprise , To get involved in goals I personally give other people under the GPL .
troubles of those I burnt out .
I in any way related Goodbye...she had Rapid , by BSDI who sell The reaper BSD 's I see the same things I still windows , SUN or Very sick and its Users all over the on slashdot.org to die .
I will jam to die .
I will jam is n't a lemonade Problems with lube or we sell simple solution all parties it 's benefits of being The bottoms butt Where It was when was what got me percent of the * BSD , a proud member the resources that by simple fucking bulk of the FreeBSD bunch of retarded man walking .
It 's [ goat.cx ]</tokentext>
<sentencetext>CORPSE TURNED OVER Good to write you Raymond in his the future holds hobby.
It was all fucking surprise, To get involved in goals I personally give other people under the GPL.
troubles of those I burnt out.
I in any way related Goodbye...she had Rapid, by BSDI who sell The reaper BSD's I see the same things I still windows, SUN or Very sick and its Users all over the on slashdot.org to die.
I will jam to die.
I will jam isn't a lemonade Problems with lube or we sell simple solution all parties it's benefits of being The bottoms butt Where It was when was what got me percent of the *BSD , a proud member the resources that by simple fucking bulk of the FreeBSD bunch of retarded man walking.
It's [goat.cx]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</id>
	<title>Be Redundant!</title>
	<author>drewzhrodague</author>
	<datestamp>1246886940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Anyone seriously oncerned about their web applications, will have redundant sites, and a way to share the load. Few people pay attention to the fact that DNS requires geographically disparate DNS servers *, such that even in the event of a datacenter fire (or nuclear attack), there will still be an answer for your zone. Couple this with a few smaller server farms in separate places, and there won't be any problems.

I went to look it up on wikipedia, but didn't find out where it is required for authoritative DNS servers to be in separate geographic regions. Where did I read this, DNS and BIND?</htmltext>
<tokenext>Anyone seriously oncerned about their web applications , will have redundant sites , and a way to share the load .
Few people pay attention to the fact that DNS requires geographically disparate DNS servers * , such that even in the event of a datacenter fire ( or nuclear attack ) , there will still be an answer for your zone .
Couple this with a few smaller server farms in separate places , and there wo n't be any problems .
I went to look it up on wikipedia , but did n't find out where it is required for authoritative DNS servers to be in separate geographic regions .
Where did I read this , DNS and BIND ?</tokentext>
<sentencetext>Anyone seriously oncerned about their web applications, will have redundant sites, and a way to share the load.
Few people pay attention to the fact that DNS requires geographically disparate DNS servers *, such that even in the event of a datacenter fire (or nuclear attack), there will still be an answer for your zone.
Couple this with a few smaller server farms in separate places, and there won't be any problems.
I went to look it up on wikipedia, but didn't find out where it is required for authoritative DNS servers to be in separate geographic regions.
Where did I read this, DNS and BIND?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602583</id>
	<title>Even worse...</title>
	<author>Anonymous</author>
	<datestamp>1246890480000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>I'm one of the guys that services the security system in Fisher Plaza.  The damn sprinklers killed half my panels near the scene.  Turns out they use gas suppression methods in the data centers, not so much in the utility closets.  And the city of Seattle REQUIRES sprinklers throughout the building, even right over the precious, precious servers.  In defense of the staff there however, they do not keep them all charged 24/7.  Other then that, I have no more info, as they're pretty locked down.</p></htmltext>
<tokenext>I 'm one of the guys that services the security system in Fisher Plaza .
The damn sprinklers killed half my panels near the scene .
Turns out they use gas suppression methods in the data centers , not so much in the utility closets .
And the city of Seattle REQUIRES sprinklers throughout the building , even right over the precious , precious servers .
In defense of the staff there however , they do not keep them all charged 24/7 .
Other then that , I have no more info , as they 're pretty locked down .</tokentext>
<sentencetext>I'm one of the guys that services the security system in Fisher Plaza.
The damn sprinklers killed half my panels near the scene.
Turns out they use gas suppression methods in the data centers, not so much in the utility closets.
And the city of Seattle REQUIRES sprinklers throughout the building, even right over the precious, precious servers.
In defense of the staff there however, they do not keep them all charged 24/7.
Other then that, I have no more info, as they're pretty locked down.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602505</id>
	<title>Re:Be Redundant!</title>
	<author>JWSmythe</author>
	<datestamp>1246889700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>
&nbsp; &nbsp; Be nice, people don't read the books nor RFC's any more.</p><p>
&nbsp; &nbsp; At the biggest operation I ran, I had redundant servers in multiple cities, and DNS servers in each city.  If we lost a city, it was never a big deal, other than the others needing to handle the load.  With say 3 cities, a one-city outage only accounted for a 16.6\% increase in the other two.  Each city was set up to handle &gt;100\% of the typical peak day traffic, so it was never a big deal.  I don't think we ever suffered a two-city simultaneous failure, even though we simulated them by shutting down a city for a few minutes.  Testing days were always my favorite.  I loved to prove what we could or couldn't do.  I peaked out one provider in a city once.  We had the capacity as far as the lines went, but they couldn't handle the bandwidth.  It was entertaining when they argued, so I dumped the other two cities to the one in question, and they were begging me to stop.  "Oh, so there is a fault.  Care to fix it?"</p><p>
&nbsp; &nbsp; I could quantify anything (and everything) at that place.  I could tell you a month or so in advance what the peak bandwidth would be on a given day, and how many of which class of servers we needed to have operating to handle it.  I classed servers by CPU and memory, which in turn gave how many users and how much bandwidth each could do.  I only wanted our machines to every peak out at 80\%, but sometimes it was fun to run them up through 100\%.  I set the limits a little low, so we could run at say 105\% without a failure.</p><p>
&nbsp; &nbsp; Such information let us know if we had a server problem, before we knew we did.  I'd notice a server was running 10\% low, and that really means that it is going to fail.  We'd watch for a little while, and it would.<nobr> <wbr></nobr>:)  We'd power it down, and leave it in the datacenter until we had another scheduled site visit.</p></htmltext>
<tokenext>    Be nice , people do n't read the books nor RFC 's any more .
    At the biggest operation I ran , I had redundant servers in multiple cities , and DNS servers in each city .
If we lost a city , it was never a big deal , other than the others needing to handle the load .
With say 3 cities , a one-city outage only accounted for a 16.6 \ % increase in the other two .
Each city was set up to handle &gt; 100 \ % of the typical peak day traffic , so it was never a big deal .
I do n't think we ever suffered a two-city simultaneous failure , even though we simulated them by shutting down a city for a few minutes .
Testing days were always my favorite .
I loved to prove what we could or could n't do .
I peaked out one provider in a city once .
We had the capacity as far as the lines went , but they could n't handle the bandwidth .
It was entertaining when they argued , so I dumped the other two cities to the one in question , and they were begging me to stop .
" Oh , so there is a fault .
Care to fix it ?
"     I could quantify anything ( and everything ) at that place .
I could tell you a month or so in advance what the peak bandwidth would be on a given day , and how many of which class of servers we needed to have operating to handle it .
I classed servers by CPU and memory , which in turn gave how many users and how much bandwidth each could do .
I only wanted our machines to every peak out at 80 \ % , but sometimes it was fun to run them up through 100 \ % .
I set the limits a little low , so we could run at say 105 \ % without a failure .
    Such information let us know if we had a server problem , before we knew we did .
I 'd notice a server was running 10 \ % low , and that really means that it is going to fail .
We 'd watch for a little while , and it would .
: ) We 'd power it down , and leave it in the datacenter until we had another scheduled site visit .</tokentext>
<sentencetext>
    Be nice, people don't read the books nor RFC's any more.
    At the biggest operation I ran, I had redundant servers in multiple cities, and DNS servers in each city.
If we lost a city, it was never a big deal, other than the others needing to handle the load.
With say 3 cities, a one-city outage only accounted for a 16.6\% increase in the other two.
Each city was set up to handle &gt;100\% of the typical peak day traffic, so it was never a big deal.
I don't think we ever suffered a two-city simultaneous failure, even though we simulated them by shutting down a city for a few minutes.
Testing days were always my favorite.
I loved to prove what we could or couldn't do.
I peaked out one provider in a city once.
We had the capacity as far as the lines went, but they couldn't handle the bandwidth.
It was entertaining when they argued, so I dumped the other two cities to the one in question, and they were begging me to stop.
"Oh, so there is a fault.
Care to fix it?
"
    I could quantify anything (and everything) at that place.
I could tell you a month or so in advance what the peak bandwidth would be on a given day, and how many of which class of servers we needed to have operating to handle it.
I classed servers by CPU and memory, which in turn gave how many users and how much bandwidth each could do.
I only wanted our machines to every peak out at 80\%, but sometimes it was fun to run them up through 100\%.
I set the limits a little low, so we could run at say 105\% without a failure.
    Such information let us know if we had a server problem, before we knew we did.
I'd notice a server was running 10\% low, and that really means that it is going to fail.
We'd watch for a little while, and it would.
:)  We'd power it down, and leave it in the datacenter until we had another scheduled site visit.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605271</id>
	<title>Re:Be Redundant!</title>
	<author>Anonymous</author>
	<datestamp>1246961520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><i>I set the limits a little low, so we could run at say 105\% without a failure.</i></p><p>Wow, so you could turn it up all the way to 11! Rockin', dude!</p></htmltext>
<tokenext>I set the limits a little low , so we could run at say 105 \ % without a failure.Wow , so you could turn it up all the way to 11 !
Rockin ' , dude !</tokentext>
<sentencetext>I set the limits a little low, so we could run at say 105\% without a failure.Wow, so you could turn it up all the way to 11!
Rockin', dude!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602505</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28609105</id>
	<title>Re:UPSs cause more failures than they prevent!</title>
	<author>Critical Facilities</author>
	<datestamp>1246985280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I'm almost thinking of taking UPS out of the loop here.</p></div><p>That would be suicide.  If you think that all of the pieces of gear in a data center could go down and then come back up with no problem,  I may have a bridge that you can buy for a very reasonable price.</p><p><div class="quote"><p>Why the hell the idiots that design UPSs seem to think it's a good idea to prevent them turning on if they sense a problem with the batteries is beyond me. Why not let the machines power back up but just make a loud beeping noise until the batteries are fixed. Don't they realise that most of the time the UPS will only properly test the batteries when there's an actual power cut?</p></div><p>Oh where to start.  First of all,  enterprise level UPS Systems (not the little "shoe box" APC unit under your desk) do not shut down on battery issues.  At worst,  during a catastrophic failure,  they will trip to bypass.  If properly arranged in a 2N or 2N+1 configuration,  your Critical Load will migrate to an alternate,  redundant UPS System just as a precaution.  If there are battery issues,  the data center operators will know it long before the UPS modules register any alarms (or they're not doing their job).  Battery PMs are just as important as generator,  transfer switch,  static switch,  and other PMs.  <br> <br>You are also mistaken that the only time batteries can be tested is during an outage.  If the Preventive Maintenance regimen is thorough,  there should be full battery discharge testing in addition to quarterly and semi annual battery PMs looking for specific gravity and internal resistance along with cell voltages,  and various other components.  In other words,  there should be no surprises.  True,  you can't rule everything out,  but you can reduce chance and surprises by a HUGE margin if you're vigilant and thorough.</p></div>
	</htmltext>
<tokenext>I 'm almost thinking of taking UPS out of the loop here.That would be suicide .
If you think that all of the pieces of gear in a data center could go down and then come back up with no problem , I may have a bridge that you can buy for a very reasonable price.Why the hell the idiots that design UPSs seem to think it 's a good idea to prevent them turning on if they sense a problem with the batteries is beyond me .
Why not let the machines power back up but just make a loud beeping noise until the batteries are fixed .
Do n't they realise that most of the time the UPS will only properly test the batteries when there 's an actual power cut ? Oh where to start .
First of all , enterprise level UPS Systems ( not the little " shoe box " APC unit under your desk ) do not shut down on battery issues .
At worst , during a catastrophic failure , they will trip to bypass .
If properly arranged in a 2N or 2N + 1 configuration , your Critical Load will migrate to an alternate , redundant UPS System just as a precaution .
If there are battery issues , the data center operators will know it long before the UPS modules register any alarms ( or they 're not doing their job ) .
Battery PMs are just as important as generator , transfer switch , static switch , and other PMs .
You are also mistaken that the only time batteries can be tested is during an outage .
If the Preventive Maintenance regimen is thorough , there should be full battery discharge testing in addition to quarterly and semi annual battery PMs looking for specific gravity and internal resistance along with cell voltages , and various other components .
In other words , there should be no surprises .
True , you ca n't rule everything out , but you can reduce chance and surprises by a HUGE margin if you 're vigilant and thorough .</tokentext>
<sentencetext>I'm almost thinking of taking UPS out of the loop here.That would be suicide.
If you think that all of the pieces of gear in a data center could go down and then come back up with no problem,  I may have a bridge that you can buy for a very reasonable price.Why the hell the idiots that design UPSs seem to think it's a good idea to prevent them turning on if they sense a problem with the batteries is beyond me.
Why not let the machines power back up but just make a loud beeping noise until the batteries are fixed.
Don't they realise that most of the time the UPS will only properly test the batteries when there's an actual power cut?Oh where to start.
First of all,  enterprise level UPS Systems (not the little "shoe box" APC unit under your desk) do not shut down on battery issues.
At worst,  during a catastrophic failure,  they will trip to bypass.
If properly arranged in a 2N or 2N+1 configuration,  your Critical Load will migrate to an alternate,  redundant UPS System just as a precaution.
If there are battery issues,  the data center operators will know it long before the UPS modules register any alarms (or they're not doing their job).
Battery PMs are just as important as generator,  transfer switch,  static switch,  and other PMs.
You are also mistaken that the only time batteries can be tested is during an outage.
If the Preventive Maintenance regimen is thorough,  there should be full battery discharge testing in addition to quarterly and semi annual battery PMs looking for specific gravity and internal resistance along with cell voltages,  and various other components.
In other words,  there should be no surprises.
True,  you can't rule everything out,  but you can reduce chance and surprises by a HUGE margin if you're vigilant and thorough.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602049</id>
	<title>Outages</title>
	<author>Solokron</author>
	<datestamp>1246886820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Outages happen more than that. We have been in several data centers, ThePlanet and The Fortress both have had major outages in the last two years which has affected business.</htmltext>
<tokenext>Outages happen more than that .
We have been in several data centers , ThePlanet and The Fortress both have had major outages in the last two years which has affected business .</tokentext>
<sentencetext>Outages happen more than that.
We have been in several data centers, ThePlanet and The Fortress both have had major outages in the last two years which has affected business.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603057</id>
	<title>Been through too many of these.</title>
	<author>Velox\_SwiftFox</author>
	<datestamp>1246894320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>"Major" data center or not, the one your company employing you at the time is using is the important one.<br>In my experiences, data center backups fail about a third the time power is interupted somewhere.</p><p>Servers in an Oakland California center were the victim of the loss of one of three power phases, while the monitoring that would have switched over to the diesel generators was looking at the power level of other phases.  UPS systems ran out of power.  An extra level of redundancy in the form of rack mount UPSes allowed servers to shut down properly despite the data center's loss of routing.</p><p>Data center #2 was the victim of a simple power outage and immediate failure of the main data center UPS system.  According to a security guard I talked to, "it exploded".  The diesel backup never had a chance to start.</p><p>Then the doubly-sourced Power Distribution Unit supplying a rack at a third ISP failed in a way that turned off both sources supplying the servers.</p><p>Hint:  Add an extra level of UPS redundancy and safe shutdown software daemons, at least.  Multiple data centers if you need more nines.</p></htmltext>
<tokenext>" Major " data center or not , the one your company employing you at the time is using is the important one.In my experiences , data center backups fail about a third the time power is interupted somewhere.Servers in an Oakland California center were the victim of the loss of one of three power phases , while the monitoring that would have switched over to the diesel generators was looking at the power level of other phases .
UPS systems ran out of power .
An extra level of redundancy in the form of rack mount UPSes allowed servers to shut down properly despite the data center 's loss of routing.Data center # 2 was the victim of a simple power outage and immediate failure of the main data center UPS system .
According to a security guard I talked to , " it exploded " .
The diesel backup never had a chance to start.Then the doubly-sourced Power Distribution Unit supplying a rack at a third ISP failed in a way that turned off both sources supplying the servers.Hint : Add an extra level of UPS redundancy and safe shutdown software daemons , at least .
Multiple data centers if you need more nines .</tokentext>
<sentencetext>"Major" data center or not, the one your company employing you at the time is using is the important one.In my experiences, data center backups fail about a third the time power is interupted somewhere.Servers in an Oakland California center were the victim of the loss of one of three power phases, while the monitoring that would have switched over to the diesel generators was looking at the power level of other phases.
UPS systems ran out of power.
An extra level of redundancy in the form of rack mount UPSes allowed servers to shut down properly despite the data center's loss of routing.Data center #2 was the victim of a simple power outage and immediate failure of the main data center UPS system.
According to a security guard I talked to, "it exploded".
The diesel backup never had a chance to start.Then the doubly-sourced Power Distribution Unit supplying a rack at a third ISP failed in a way that turned off both sources supplying the servers.Hint:  Add an extra level of UPS redundancy and safe shutdown software daemons, at least.
Multiple data centers if you need more nines.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604989</id>
	<title>Re:If only you had listened...</title>
	<author>Anonymous</author>
	<datestamp>1246957440000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext>It was a bad week to be Billy Mays, too.  He died.</htmltext>
<tokenext>It was a bad week to be Billy Mays , too .
He died .</tokentext>
<sentencetext>It was a bad week to be Billy Mays, too.
He died.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604751</id>
	<title>Ugh.  I just finished re-watching, "Die Hard 4".</title>
	<author>Fantastic Lad</author>
	<datestamp>1246997940000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p>It was a terrible movie, not the kind I like to watch anyway, but for some reason I felt compelled to view the damned thing twice in two days.</p><p>The Big Bad Threat in the film was all about something called a Fire Sale, ("It All Has To Go"), where the population's fear level is spiked up into a panic by a group of bad guys deliberately crashing the national infrastructure by way of hacking all the most important computer systems.  --All to create a giant distraction so that the stock market could be plundered by thievesssssss!  The story is weirdly in keeping with the theme of this Slashdot article.</p><p>Consider:  Everything is a metaphor in this big old world of ours where matter and energy are based on nothing more than space and the vague notion that there is something which exists.  With no matter to speak of, the whole of reality is little more than a hologram, and that being the case, the power of thought and awareness holds about the same amount of substance, if not more.  --The subconscious is connected quite well to the whole affair, and events of some magnitude like today's server outages will tend to send ripples through reality so that poor shmucks like me find themselves watching in fascination stupid movies they hate without knowing why.</p><p>All I know for sure is that Bruce Willis was a lot more fun to watch when he was playing opposite Cybill Shepherd.</p><p>-FL</p></htmltext>
<tokenext>It was a terrible movie , not the kind I like to watch anyway , but for some reason I felt compelled to view the damned thing twice in two days.The Big Bad Threat in the film was all about something called a Fire Sale , ( " It All Has To Go " ) , where the population 's fear level is spiked up into a panic by a group of bad guys deliberately crashing the national infrastructure by way of hacking all the most important computer systems .
--All to create a giant distraction so that the stock market could be plundered by thievesssssss !
The story is weirdly in keeping with the theme of this Slashdot article.Consider : Everything is a metaphor in this big old world of ours where matter and energy are based on nothing more than space and the vague notion that there is something which exists .
With no matter to speak of , the whole of reality is little more than a hologram , and that being the case , the power of thought and awareness holds about the same amount of substance , if not more .
--The subconscious is connected quite well to the whole affair , and events of some magnitude like today 's server outages will tend to send ripples through reality so that poor shmucks like me find themselves watching in fascination stupid movies they hate without knowing why.All I know for sure is that Bruce Willis was a lot more fun to watch when he was playing opposite Cybill Shepherd.-FL</tokentext>
<sentencetext>It was a terrible movie, not the kind I like to watch anyway, but for some reason I felt compelled to view the damned thing twice in two days.The Big Bad Threat in the film was all about something called a Fire Sale, ("It All Has To Go"), where the population's fear level is spiked up into a panic by a group of bad guys deliberately crashing the national infrastructure by way of hacking all the most important computer systems.
--All to create a giant distraction so that the stock market could be plundered by thievesssssss!
The story is weirdly in keeping with the theme of this Slashdot article.Consider:  Everything is a metaphor in this big old world of ours where matter and energy are based on nothing more than space and the vague notion that there is something which exists.
With no matter to speak of, the whole of reality is little more than a hologram, and that being the case, the power of thought and awareness holds about the same amount of substance, if not more.
--The subconscious is connected quite well to the whole affair, and events of some magnitude like today's server outages will tend to send ripples through reality so that poor shmucks like me find themselves watching in fascination stupid movies they hate without knowing why.All I know for sure is that Bruce Willis was a lot more fun to watch when he was playing opposite Cybill Shepherd.-FL</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28609133</id>
	<title>Re:"bad week to be a piece of electrical equipment</title>
	<author>stim</author>
	<datestamp>1246985340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If by "broken several stories" you mean "posted links to stories that were broken elsewhere" than you may have a very good point.</htmltext>
<tokenext>If by " broken several stories " you mean " posted links to stories that were broken elsewhere " than you may have a very good point .</tokentext>
<sentencetext>If by "broken several stories" you mean "posted links to stories that were broken elsewhere" than you may have a very good point.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601899</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441</id>
	<title>Downside to consolidation</title>
	<author>Anonymous</author>
	<datestamp>1246889160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Surprise surprise...there's a downside to consolidation. Hey morons, the internet was invented as a means to ensure redundant communications paths given nuclear warfare. The old central switch (physical switching) was seen as too cumbersome and vulnerable. Now that we have wonderfully redundant communications, and have done away with most of the downsides of physically distributed systems, morons are building logically centralized systems.</p><p>NEWSFLASH - Redundant communications and physical virtualization do very little for you if you build a logical mainframe.</p><p>Truly distributed systems must be physically AND logically DISTRIBUTED with redundant comms paths in order to gain the full benefits of decentralization. (e.g. Distributed isn't distributed if all your authentication is done at one site or all your traffic must pass through<nobr> <wbr></nobr>.)</p></htmltext>
<tokenext>Surprise surprise...there 's a downside to consolidation .
Hey morons , the internet was invented as a means to ensure redundant communications paths given nuclear warfare .
The old central switch ( physical switching ) was seen as too cumbersome and vulnerable .
Now that we have wonderfully redundant communications , and have done away with most of the downsides of physically distributed systems , morons are building logically centralized systems.NEWSFLASH - Redundant communications and physical virtualization do very little for you if you build a logical mainframe.Truly distributed systems must be physically AND logically DISTRIBUTED with redundant comms paths in order to gain the full benefits of decentralization .
( e.g. Distributed is n't distributed if all your authentication is done at one site or all your traffic must pass through .
)</tokentext>
<sentencetext>Surprise surprise...there's a downside to consolidation.
Hey morons, the internet was invented as a means to ensure redundant communications paths given nuclear warfare.
The old central switch (physical switching) was seen as too cumbersome and vulnerable.
Now that we have wonderfully redundant communications, and have done away with most of the downsides of physically distributed systems, morons are building logically centralized systems.NEWSFLASH - Redundant communications and physical virtualization do very little for you if you build a logical mainframe.Truly distributed systems must be physically AND logically DISTRIBUTED with redundant comms paths in order to gain the full benefits of decentralization.
(e.g. Distributed isn't distributed if all your authentication is done at one site or all your traffic must pass through .
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602241</id>
	<title>Are they over drawing the power out the units? poo</title>
	<author>Joe The Dragon</author>
	<datestamp>1246887900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Are they over drawing the power out the units? poor battery that blow up? Not having the right wire gauge? Not cooling the power buses and switches?</p></htmltext>
<tokenext>Are they over drawing the power out the units ?
poor battery that blow up ?
Not having the right wire gauge ?
Not cooling the power buses and switches ?</tokentext>
<sentencetext>Are they over drawing the power out the units?
poor battery that blow up?
Not having the right wire gauge?
Not cooling the power buses and switches?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602801</id>
	<title>Re:Be Redundant!</title>
	<author>Anonymous</author>
	<datestamp>1246892400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>While geographic diversity is certainly an excellent goal, it's not always that simple. My ISP's network core was located in the Peer 1 suite at 151 Front (whose UPS caused the fire). Power was cut to Peer 1's suite, but not the rest of the building (151 Front has independent power/cooling/etc. per-suite to the extent where each tenant is responsible for getting their own solution).</p><p>Redundant power sources could have mitigated the issue had there not been a fire; running two independent circuits to critical equipment that passes through different UPS, different PDUs, different generators, and different utilities.</p><p>Even for those on a budget, geographic diversity isn't necessarily difficult, even within the same company. Many companies have multiple locations; my VPS provider, Linode, has colo space in virtually all corners of the continent, about as far apart as you can get without going overseas. Getting a second VPS at a geographically distinct location could be a cheap way to provide failover if getting something from a different provider isn't financially feasible.</p></htmltext>
<tokenext>While geographic diversity is certainly an excellent goal , it 's not always that simple .
My ISP 's network core was located in the Peer 1 suite at 151 Front ( whose UPS caused the fire ) .
Power was cut to Peer 1 's suite , but not the rest of the building ( 151 Front has independent power/cooling/etc .
per-suite to the extent where each tenant is responsible for getting their own solution ) .Redundant power sources could have mitigated the issue had there not been a fire ; running two independent circuits to critical equipment that passes through different UPS , different PDUs , different generators , and different utilities.Even for those on a budget , geographic diversity is n't necessarily difficult , even within the same company .
Many companies have multiple locations ; my VPS provider , Linode , has colo space in virtually all corners of the continent , about as far apart as you can get without going overseas .
Getting a second VPS at a geographically distinct location could be a cheap way to provide failover if getting something from a different provider is n't financially feasible .</tokentext>
<sentencetext>While geographic diversity is certainly an excellent goal, it's not always that simple.
My ISP's network core was located in the Peer 1 suite at 151 Front (whose UPS caused the fire).
Power was cut to Peer 1's suite, but not the rest of the building (151 Front has independent power/cooling/etc.
per-suite to the extent where each tenant is responsible for getting their own solution).Redundant power sources could have mitigated the issue had there not been a fire; running two independent circuits to critical equipment that passes through different UPS, different PDUs, different generators, and different utilities.Even for those on a budget, geographic diversity isn't necessarily difficult, even within the same company.
Many companies have multiple locations; my VPS provider, Linode, has colo space in virtually all corners of the continent, about as far apart as you can get without going overseas.
Getting a second VPS at a geographically distinct location could be a cheap way to provide failover if getting something from a different provider isn't financially feasible.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28610219</id>
	<title>Re:Rackspace in Dallas</title>
	<author>Josh Wieder</author>
	<datestamp>1246989660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Have you considered Atlantic.Net as your collocation provider? We have a Data Center in Central Florida and our pricing is competitive. Give me an email at joshw  atlantic.net for a quote.

Josh Wieder
Atlantic.Net</div>
	</htmltext>
<tokenext>Have you considered Atlantic.Net as your collocation provider ?
We have a Data Center in Central Florida and our pricing is competitive .
Give me an email at joshw atlantic.net for a quote .
Josh Wieder Atlantic.Net</tokentext>
<sentencetext>Have you considered Atlantic.Net as your collocation provider?
We have a Data Center in Central Florida and our pricing is competitive.
Give me an email at joshw  atlantic.net for a quote.
Josh Wieder
Atlantic.Net
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603323</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603323</id>
	<title>Rackspace in Dallas</title>
	<author>Thundersnatch</author>
	<datestamp>1246896060000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>We're a Rackspace customer in their DFW datacenter. This is the <em>third</em> power-related outage they've had in the last two years at that supposedly world-class facility.</p><p>The first wasn't really their fault: truck driver with health condition runs into their transformers. Generators kick in, but chillers don't re-start quickly enough. Temps skyrocket in minutes, emergency shutdowns. Maybe the transformes should have had some $50 concrete pylons surrounding them?</p><p>The second outage was the result of a botched generator upgrade.</p><p>This latest outage was the result of a botched UPS maintenance.</p><p>None of the outages was long enough to trigger our failover policy to our DR site, but our customers definitely noticed.</p><p>While their messaging has been very open and honest about the problems, and the SLA credits have been immediate, we pay them nearly $20K per month. Nedless to say, we are shopping, and looking into a "multiple cheap colos" architecture instead of "Tier-1 managed hosting". Nothing beats geographic redundancy.</p></htmltext>
<tokenext>We 're a Rackspace customer in their DFW datacenter .
This is the third power-related outage they 've had in the last two years at that supposedly world-class facility.The first was n't really their fault : truck driver with health condition runs into their transformers .
Generators kick in , but chillers do n't re-start quickly enough .
Temps skyrocket in minutes , emergency shutdowns .
Maybe the transformes should have had some $ 50 concrete pylons surrounding them ? The second outage was the result of a botched generator upgrade.This latest outage was the result of a botched UPS maintenance.None of the outages was long enough to trigger our failover policy to our DR site , but our customers definitely noticed.While their messaging has been very open and honest about the problems , and the SLA credits have been immediate , we pay them nearly $ 20K per month .
Nedless to say , we are shopping , and looking into a " multiple cheap colos " architecture instead of " Tier-1 managed hosting " .
Nothing beats geographic redundancy .</tokentext>
<sentencetext>We're a Rackspace customer in their DFW datacenter.
This is the third power-related outage they've had in the last two years at that supposedly world-class facility.The first wasn't really their fault: truck driver with health condition runs into their transformers.
Generators kick in, but chillers don't re-start quickly enough.
Temps skyrocket in minutes, emergency shutdowns.
Maybe the transformes should have had some $50 concrete pylons surrounding them?The second outage was the result of a botched generator upgrade.This latest outage was the result of a botched UPS maintenance.None of the outages was long enough to trigger our failover policy to our DR site, but our customers definitely noticed.While their messaging has been very open and honest about the problems, and the SLA credits have been immediate, we pay them nearly $20K per month.
Nedless to say, we are shopping, and looking into a "multiple cheap colos" architecture instead of "Tier-1 managed hosting".
Nothing beats geographic redundancy.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602595</id>
	<title>Re:"bad week to be a piece of electrical equipment</title>
	<author>Anonymous</author>
	<datestamp>1246890600000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>Because out of all of the data centers in the world, there were problems at <em>five</em>?  Riiiiight.  Good reporting, Slashdot.</p><p>Can I sign up for broken water main notices here, too, or do I need to go to another website?</p></div><p>100+ million people daily are "serviced" by these 5 data centers.</p><p>Company's such as authorize.net where COMPLETELY unavailable for payments to hundred of thousands of webmasters sites (ya know the people who make money)</p><p>If you don't think this is serious news then you are still living at home.</p><p>Ya that's what I thought.</p></div>
	</htmltext>
<tokenext>Because out of all of the data centers in the world , there were problems at five ?
Riiiiight. Good reporting , Slashdot.Can I sign up for broken water main notices here , too , or do I need to go to another website ? 100 + million people daily are " serviced " by these 5 data centers.Company 's such as authorize.net where COMPLETELY unavailable for payments to hundred of thousands of webmasters sites ( ya know the people who make money ) If you do n't think this is serious news then you are still living at home.Ya that 's what I thought .</tokentext>
<sentencetext>Because out of all of the data centers in the world, there were problems at five?
Riiiiight.  Good reporting, Slashdot.Can I sign up for broken water main notices here, too, or do I need to go to another website?100+ million people daily are "serviced" by these 5 data centers.Company's such as authorize.net where COMPLETELY unavailable for payments to hundred of thousands of webmasters sites (ya know the people who make money)If you don't think this is serious news then you are still living at home.Ya that's what I thought.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601765</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603111</id>
	<title>Power Fail Often</title>
	<author>blantonl</author>
	<datestamp>1246894680000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Frankly, if data centers are going to proclaim their redundancy, they should test by power failing the entire data center once every two weeks at a minimum.  A data center that goes down twice in a month would get ahead of any issue pretty fast.  Lessons learned from the staff and the management are very valuable.</p><p>The marketing messaging:</p><p>"We power fail our data center every two weeks to ensure our backups work..."</p><p>Sound scary?  Just think about the data center that has never been through this process.  at that point, the wet paper bag you tried to market your way out of dried rather quickly and you are now faced with the prospect of slapping around inside of a zip-lock.</p></htmltext>
<tokenext>Frankly , if data centers are going to proclaim their redundancy , they should test by power failing the entire data center once every two weeks at a minimum .
A data center that goes down twice in a month would get ahead of any issue pretty fast .
Lessons learned from the staff and the management are very valuable.The marketing messaging : " We power fail our data center every two weeks to ensure our backups work... " Sound scary ?
Just think about the data center that has never been through this process .
at that point , the wet paper bag you tried to market your way out of dried rather quickly and you are now faced with the prospect of slapping around inside of a zip-lock .</tokentext>
<sentencetext>Frankly, if data centers are going to proclaim their redundancy, they should test by power failing the entire data center once every two weeks at a minimum.
A data center that goes down twice in a month would get ahead of any issue pretty fast.
Lessons learned from the staff and the management are very valuable.The marketing messaging:"We power fail our data center every two weeks to ensure our backups work..."Sound scary?
Just think about the data center that has never been through this process.
at that point, the wet paper bag you tried to market your way out of dried rather quickly and you are now faced with the prospect of slapping around inside of a zip-lock.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602201</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602549</id>
	<title>Qld Health datacentre disaster</title>
	<author>Anonymous</author>
	<datestamp>1246890060000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>See story of Qld Health datacentre disaster on ZDnet recently:<br>http://www.zdnet.com.au/news/hardware/soa/Horror-story-Qld-Health-datacentre-disaster/0,130061702,339297206,00.htm</p></htmltext>
<tokenext>See story of Qld Health datacentre disaster on ZDnet recently : http : //www.zdnet.com.au/news/hardware/soa/Horror-story-Qld-Health-datacentre-disaster/0,130061702,339297206,00.htm</tokentext>
<sentencetext>See story of Qld Health datacentre disaster on ZDnet recently:http://www.zdnet.com.au/news/hardware/soa/Horror-story-Qld-Health-datacentre-disaster/0,130061702,339297206,00.htm</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605351</id>
	<title>Re:Downside to consolidation</title>
	<author>BBCWatcher</author>
	<datestamp>1246962480000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>No, I think you have it exactly backwards, or at least you're missing an important nuance. It's really, really expensive to duplicate everything across two (or more) data centers. And it's full scope increase in IT costs: most or all cost categories increase. We're talking <i>more</i> than double the costs, in round numbers. Beyond the cost, it's very hard technically to recover hundreds or thousands of servers simultaneously or even near-simultaneously, because you are typically trying to recover not hundreds or thousands of atomistic, independent servers but all the moment-in-time state and functional dependencies among servers. Very, very difficult, which also means hugely expensive and prone to error. Unfortunately, service interruptions are also extremely expensive. What to do?
</p><p>You could just buy a pair of mainframes, one at site one and the other (configured with reserve capacity, which is lower cost) at site two. (More only if you need the capacity. Then they just operate like a single machine.) That all works really, really well. As in, credit card holders would have no clue that site #1 just burned to the ground -- the credit cards still keep working. That particular form of consolidation makes disaster recovery a relative breeze. DR is just thoroughly baked into the DNA of such equipment, and the very computing model itself supports rapid recovery. (Down to zero interruption effectively and zero data loss, if that's what you need. Or, in DR lingo, RPO and RTO of zero.)
</p><p>The critical nuance here is if you only consolidate sites, which a lot of businesses have done, you're <i>reducing</i> business resiliency, ceteris paribus. Yes indeed, if you merely forklift your hundreds or thousands of servers into a smaller number of data centers and do basically nothing to consolidate applications, databases, operating system images, etc., onto better DR-protected assets, then disaster recovery will be much tougher and much more expensive. Site-wide disasters will be more disastrous. The game-changer (otherwise known as re-learning time-tested lessons<nobr> <wbr></nobr>:-)) is if you untangle the mess and do <i>real</i> consolidation onto a much smaller number of robust, well-protected servers with some decent DR investments and realistic rehearsals. That'd be mainframes and mainframe IT discipline, basically, or at least something that resembles mainframes (if such a thing exists).</p></htmltext>
<tokenext>No , I think you have it exactly backwards , or at least you 're missing an important nuance .
It 's really , really expensive to duplicate everything across two ( or more ) data centers .
And it 's full scope increase in IT costs : most or all cost categories increase .
We 're talking more than double the costs , in round numbers .
Beyond the cost , it 's very hard technically to recover hundreds or thousands of servers simultaneously or even near-simultaneously , because you are typically trying to recover not hundreds or thousands of atomistic , independent servers but all the moment-in-time state and functional dependencies among servers .
Very , very difficult , which also means hugely expensive and prone to error .
Unfortunately , service interruptions are also extremely expensive .
What to do ?
You could just buy a pair of mainframes , one at site one and the other ( configured with reserve capacity , which is lower cost ) at site two .
( More only if you need the capacity .
Then they just operate like a single machine .
) That all works really , really well .
As in , credit card holders would have no clue that site # 1 just burned to the ground -- the credit cards still keep working .
That particular form of consolidation makes disaster recovery a relative breeze .
DR is just thoroughly baked into the DNA of such equipment , and the very computing model itself supports rapid recovery .
( Down to zero interruption effectively and zero data loss , if that 's what you need .
Or , in DR lingo , RPO and RTO of zero .
) The critical nuance here is if you only consolidate sites , which a lot of businesses have done , you 're reducing business resiliency , ceteris paribus .
Yes indeed , if you merely forklift your hundreds or thousands of servers into a smaller number of data centers and do basically nothing to consolidate applications , databases , operating system images , etc. , onto better DR-protected assets , then disaster recovery will be much tougher and much more expensive .
Site-wide disasters will be more disastrous .
The game-changer ( otherwise known as re-learning time-tested lessons : - ) ) is if you untangle the mess and do real consolidation onto a much smaller number of robust , well-protected servers with some decent DR investments and realistic rehearsals .
That 'd be mainframes and mainframe IT discipline , basically , or at least something that resembles mainframes ( if such a thing exists ) .</tokentext>
<sentencetext>No, I think you have it exactly backwards, or at least you're missing an important nuance.
It's really, really expensive to duplicate everything across two (or more) data centers.
And it's full scope increase in IT costs: most or all cost categories increase.
We're talking more than double the costs, in round numbers.
Beyond the cost, it's very hard technically to recover hundreds or thousands of servers simultaneously or even near-simultaneously, because you are typically trying to recover not hundreds or thousands of atomistic, independent servers but all the moment-in-time state and functional dependencies among servers.
Very, very difficult, which also means hugely expensive and prone to error.
Unfortunately, service interruptions are also extremely expensive.
What to do?
You could just buy a pair of mainframes, one at site one and the other (configured with reserve capacity, which is lower cost) at site two.
(More only if you need the capacity.
Then they just operate like a single machine.
) That all works really, really well.
As in, credit card holders would have no clue that site #1 just burned to the ground -- the credit cards still keep working.
That particular form of consolidation makes disaster recovery a relative breeze.
DR is just thoroughly baked into the DNA of such equipment, and the very computing model itself supports rapid recovery.
(Down to zero interruption effectively and zero data loss, if that's what you need.
Or, in DR lingo, RPO and RTO of zero.
)
The critical nuance here is if you only consolidate sites, which a lot of businesses have done, you're reducing business resiliency, ceteris paribus.
Yes indeed, if you merely forklift your hundreds or thousands of servers into a smaller number of data centers and do basically nothing to consolidate applications, databases, operating system images, etc., onto better DR-protected assets, then disaster recovery will be much tougher and much more expensive.
Site-wide disasters will be more disastrous.
The game-changer (otherwise known as re-learning time-tested lessons :-)) is if you untangle the mess and do real consolidation onto a much smaller number of robust, well-protected servers with some decent DR investments and realistic rehearsals.
That'd be mainframes and mainframe IT discipline, basically, or at least something that resembles mainframes (if such a thing exists).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28610709</id>
	<title>Re:Even worse...</title>
	<author>evil-merodach</author>
	<datestamp>1246991640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We had the largest data center in Seattle and believe me we did NOT have sprinklers in our data center. Saying that the city required them sounds like a cop-out to me.

Our disaster recovery plan was pretty solid with off-site recovery several thousands of miles away within minutes.

Unfortunately, we did not have a disaster recovery plan for being seized by the federal government and sold to a competitor.</htmltext>
<tokenext>We had the largest data center in Seattle and believe me we did NOT have sprinklers in our data center .
Saying that the city required them sounds like a cop-out to me .
Our disaster recovery plan was pretty solid with off-site recovery several thousands of miles away within minutes .
Unfortunately , we did not have a disaster recovery plan for being seized by the federal government and sold to a competitor .</tokentext>
<sentencetext>We had the largest data center in Seattle and believe me we did NOT have sprinklers in our data center.
Saying that the city required them sounds like a cop-out to me.
Our disaster recovery plan was pretty solid with off-site recovery several thousands of miles away within minutes.
Unfortunately, we did not have a disaster recovery plan for being seized by the federal government and sold to a competitor.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602583</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604491</id>
	<title>Re:Be Redundant!</title>
	<author>rdnetto</author>
	<datestamp>1246908420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>But then how will you know who is attacking you, and where to go? Not to mention how to best shield yourself from radiation...</htmltext>
<tokenext>But then how will you know who is attacking you , and where to go ?
Not to mention how to best shield yourself from radiation.. .</tokentext>
<sentencetext>But then how will you know who is attacking you, and where to go?
Not to mention how to best shield yourself from radiation...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602357</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28608767</id>
	<title>Re:Power Fail Often</title>
	<author>Critical Facilities</author>
	<datestamp>1246983900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Frankly, if data centers are going to proclaim their redundancy, they should test by power failing the entire data center once every two weeks at a minimum.</p></div><p>I disagree.  If you perform a full load test of your facility every 2 weeks (or heaven forbid more frequently) you will be buying LOTS and LOTS of UPS batteries.  Not to mention putting additoinal wear and tear on your generators,  transfer switches,  UPS Modules,  Control Cabinets,  etc.<br> <br>You are correct,  data centers should do "pull the plug" tests,  but not as frequently as you suggest,  otherwise they'll effectively be reducing their availability by introducing more risk to the equation.</p></div>
	</htmltext>
<tokenext>Frankly , if data centers are going to proclaim their redundancy , they should test by power failing the entire data center once every two weeks at a minimum.I disagree .
If you perform a full load test of your facility every 2 weeks ( or heaven forbid more frequently ) you will be buying LOTS and LOTS of UPS batteries .
Not to mention putting additoinal wear and tear on your generators , transfer switches , UPS Modules , Control Cabinets , etc .
You are correct , data centers should do " pull the plug " tests , but not as frequently as you suggest , otherwise they 'll effectively be reducing their availability by introducing more risk to the equation .</tokentext>
<sentencetext>Frankly, if data centers are going to proclaim their redundancy, they should test by power failing the entire data center once every two weeks at a minimum.I disagree.
If you perform a full load test of your facility every 2 weeks (or heaven forbid more frequently) you will be buying LOTS and LOTS of UPS batteries.
Not to mention putting additoinal wear and tear on your generators,  transfer switches,  UPS Modules,  Control Cabinets,  etc.
You are correct,  data centers should do "pull the plug" tests,  but not as frequently as you suggest,  otherwise they'll effectively be reducing their availability by introducing more risk to the equation.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603111</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602201</id>
	<title>No preventative maintenance?</title>
	<author>Anonymous</author>
	<datestamp>1246887720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>My wild guess is they are deferring preventative maintenance on these data centers so we are seeing these major outages now. Fire suppression, UPS, transfer switches, generators, distribution panels, transformers, network gear, server, storage devices and other gear will fail if you don't maintain them properly. As loads increase, the equipment will fail earlier and my guess the people have pushed the limit of this equipment beyond they the lifespan of load rating.</p></htmltext>
<tokenext>My wild guess is they are deferring preventative maintenance on these data centers so we are seeing these major outages now .
Fire suppression , UPS , transfer switches , generators , distribution panels , transformers , network gear , server , storage devices and other gear will fail if you do n't maintain them properly .
As loads increase , the equipment will fail earlier and my guess the people have pushed the limit of this equipment beyond they the lifespan of load rating .</tokentext>
<sentencetext>My wild guess is they are deferring preventative maintenance on these data centers so we are seeing these major outages now.
Fire suppression, UPS, transfer switches, generators, distribution panels, transformers, network gear, server, storage devices and other gear will fail if you don't maintain them properly.
As loads increase, the equipment will fail earlier and my guess the people have pushed the limit of this equipment beyond they the lifespan of load rating.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737</id>
	<title>If only you had listened...</title>
	<author>Anonymous</author>
	<datestamp>1246885080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>I'm guessing that the majority of these were caused by leaks or spilled drinks. If only you guys had listened to me and gotten <a href="http://en.wikipedia.org/wiki/Zorbeez" title="wikipedia.org" rel="nofollow">Zorbeez(tm)[SOAKS UP 10x ITS OWN WEIGHT!]</a> [wikipedia.org].

<br>
<br> -B. Mays</htmltext>
<tokenext>I 'm guessing that the majority of these were caused by leaks or spilled drinks .
If only you guys had listened to me and gotten Zorbeez ( tm ) [ SOAKS UP 10x ITS OWN WEIGHT !
] [ wikipedia.org ] .
-B. Mays</tokentext>
<sentencetext>I'm guessing that the majority of these were caused by leaks or spilled drinks.
If only you guys had listened to me and gotten Zorbeez(tm)[SOAKS UP 10x ITS OWN WEIGHT!
] [wikipedia.org].
-B. Mays</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601765</id>
	<title>"bad week to be a piece of electrical equipment"</title>
	<author>raddan</author>
	<datestamp>1246885260000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext>Because out of all of the data centers in the world, there were problems at <em>five</em>?  Riiiiight.  Good reporting, Slashdot.
<br> <br>
Can I sign up for broken water main notices here, too, or do I need to go to another website?</htmltext>
<tokenext>Because out of all of the data centers in the world , there were problems at five ?
Riiiiight. Good reporting , Slashdot .
Can I sign up for broken water main notices here , too , or do I need to go to another website ?</tokentext>
<sentencetext>Because out of all of the data centers in the world, there were problems at five?
Riiiiight.  Good reporting, Slashdot.
Can I sign up for broken water main notices here, too, or do I need to go to another website?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603297</id>
	<title>Re:If only you had listened...</title>
	<author>Puppet Master</author>
	<datestamp>1246895880000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext>Billy, welcome back!!!</htmltext>
<tokenext>Billy , welcome back ! !
!</tokentext>
<sentencetext>Billy, welcome back!!
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603845</id>
	<title>Re:If only you had listened...</title>
	<author>Stenchwarrior</author>
	<datestamp>1246900140000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext>First it was Ed, Farrah, Michael and then Billy. Now wide-spread power outages?? Not sure about you guys, but I smell Apocalypse brewing. Time to get right with Mr. Noodle and his Parmesan profits.</htmltext>
<tokenext>First it was Ed , Farrah , Michael and then Billy .
Now wide-spread power outages ? ?
Not sure about you guys , but I smell Apocalypse brewing .
Time to get right with Mr. Noodle and his Parmesan profits .</tokentext>
<sentencetext>First it was Ed, Farrah, Michael and then Billy.
Now wide-spread power outages??
Not sure about you guys, but I smell Apocalypse brewing.
Time to get right with Mr. Noodle and his Parmesan profits.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604201</id>
	<title>Re:Downside to consolidation</title>
	<author>DNS-and-BIND</author>
	<datestamp>1246904400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>1) The internet wasn't redundant, ARPANET was redundant.  The internet hasn't been able to withstand a nuclear attack since it was put online.<p>Putting all your eggs in one basket is nothing new under the sun.  You ever see Ma Bell's idea of a "redundant" circuit?  Two wires in the same condiut.  But at least Ma Bell was doing it out of thriftiness and laziness, not ignorance and superstition.</p></htmltext>
<tokenext>1 ) The internet was n't redundant , ARPANET was redundant .
The internet has n't been able to withstand a nuclear attack since it was put online.Putting all your eggs in one basket is nothing new under the sun .
You ever see Ma Bell 's idea of a " redundant " circuit ?
Two wires in the same condiut .
But at least Ma Bell was doing it out of thriftiness and laziness , not ignorance and superstition .</tokentext>
<sentencetext>1) The internet wasn't redundant, ARPANET was redundant.
The internet hasn't been able to withstand a nuclear attack since it was put online.Putting all your eggs in one basket is nothing new under the sun.
You ever see Ma Bell's idea of a "redundant" circuit?
Two wires in the same condiut.
But at least Ma Bell was doing it out of thriftiness and laziness, not ignorance and superstition.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602357</id>
	<title>Re:Be Redundant!</title>
	<author>Anonymous</author>
	<datestamp>1246888620000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>In the event of a nuclear attack, you probably have more pressing issues to deal with than your server uptime.</p></htmltext>
<tokenext>In the event of a nuclear attack , you probably have more pressing issues to deal with than your server uptime .</tokentext>
<sentencetext>In the event of a nuclear attack, you probably have more pressing issues to deal with than your server uptime.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603779</id>
	<title>Re:"bad week to be a piece of electrical equipment</title>
	<author>Alpha830RulZ</author>
	<datestamp>1246899480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The Fisher Plaza story is big.  I happened to be walking by right after it happened, noticed the generators running and went, 'Hm-m-m".  We've toured their facility in the past, and wanted to use them, but they didn't have capacity at the time.  They seemed first rate.  If a first tier provider can have this happen...</p></htmltext>
<tokenext>The Fisher Plaza story is big .
I happened to be walking by right after it happened , noticed the generators running and went , 'Hm-m-m " .
We 've toured their facility in the past , and wanted to use them , but they did n't have capacity at the time .
They seemed first rate .
If a first tier provider can have this happen.. .</tokentext>
<sentencetext>The Fisher Plaza story is big.
I happened to be walking by right after it happened, noticed the generators running and went, 'Hm-m-m".
We've toured their facility in the past, and wanted to use them, but they didn't have capacity at the time.
They seemed first rate.
If a first tier provider can have this happen...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602595</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602833</id>
	<title>So the real question is...</title>
	<author>Anonymous</author>
	<datestamp>1246892700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>...what is the normal (historical) rate of data center power failures, and how does the recent spate compare? Five in a week sounds severe, but what's the normal worldwide average? I can imagine that with thousands of data centers around the globe, there's likely a serious failure occurring <i>somewhere</i> in the world once every couple of days.</htmltext>
<tokenext>...what is the normal ( historical ) rate of data center power failures , and how does the recent spate compare ?
Five in a week sounds severe , but what 's the normal worldwide average ?
I can imagine that with thousands of data centers around the globe , there 's likely a serious failure occurring somewhere in the world once every couple of days .</tokentext>
<sentencetext>...what is the normal (historical) rate of data center power failures, and how does the recent spate compare?
Five in a week sounds severe, but what's the normal worldwide average?
I can imagine that with thousands of data centers around the globe, there's likely a serious failure occurring somewhere in the world once every couple of days.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602847</id>
	<title>Re:Damn you Michael Bay!</title>
	<author>jd2112</author>
	<datestamp>1246892820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Well, one review (CNN, I think) described Transformers as "Robot Porn".</htmltext>
<tokenext>Well , one review ( CNN , I think ) described Transformers as " Robot Porn " .</tokentext>
<sentencetext>Well, one review (CNN, I think) described Transformers as "Robot Porn".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601899</id>
	<title>Re:"bad week to be a piece of electrical equipment</title>
	<author>Anonymous</author>
	<datestamp>1246885980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Quiet troll.  Slashdot has broken several stories over the years and most of them started as these little coincidences.  Go back to reading CNN if you want your news filtered.</p></htmltext>
<tokenext>Quiet troll .
Slashdot has broken several stories over the years and most of them started as these little coincidences .
Go back to reading CNN if you want your news filtered .</tokentext>
<sentencetext>Quiet troll.
Slashdot has broken several stories over the years and most of them started as these little coincidences.
Go back to reading CNN if you want your news filtered.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601765</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28616815</id>
	<title>Re:UPSs cause more failures than they prevent!</title>
	<author>jabelli</author>
	<datestamp>1246978320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's because you keep buying the cheap "Back-UPS" home computer crap to run servers on. I'm using a 15-year-old Smart-UPS 600. I've replaced the batteries once. When the original set wore out, it didn't refuse to power up, it complained about the batteries with das blinkenlights and the warning beeper until they were replaced.</p></htmltext>
<tokenext>That 's because you keep buying the cheap " Back-UPS " home computer crap to run servers on .
I 'm using a 15-year-old Smart-UPS 600 .
I 've replaced the batteries once .
When the original set wore out , it did n't refuse to power up , it complained about the batteries with das blinkenlights and the warning beeper until they were replaced .</tokentext>
<sentencetext>That's because you keep buying the cheap "Back-UPS" home computer crap to run servers on.
I'm using a 15-year-old Smart-UPS 600.
I've replaced the batteries once.
When the original set wore out, it didn't refuse to power up, it complained about the batteries with das blinkenlights and the warning beeper until they were replaced.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602161</id>
	<title>Re:Damn you Michael Bay!</title>
	<author>tnk1</author>
	<datestamp>1246887480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I guess Megan Fox's character is upgrading.</p></htmltext>
<tokenext>I guess Megan Fox 's character is upgrading .</tokentext>
<sentencetext>I guess Megan Fox's character is upgrading.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28611387</id>
	<title>Re:Rackspace in Dallas</title>
	<author>RichINetU</author>
	<datestamp>1246994100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>We're a Rackspace customer in their DFW datacenter. This is the <em>third</em> power-related outage they've had in the last two years at that supposedly world-class facility.</p><p>The first wasn't really their fault: truck driver with health condition runs into their transformers. Generators kick in, but chillers don't re-start quickly enough. Temps skyrocket in minutes, emergency shutdowns. Maybe the transformes should have had some $50 concrete pylons surrounding them?</p><p>The second outage was the result of a botched generator upgrade.</p><p>This latest outage was the result of a botched UPS maintenance.</p><p>None of the outages was long enough to trigger our failover policy to our DR site, but our customers definitely noticed.</p><p>While their messaging has been very open and honest about the problems, and the SLA credits have been immediate, we pay them nearly $20K per month. Nedless to say, we are shopping, and looking into a "multiple cheap colos" architecture instead of "Tier-1 managed hosting". Nothing beats geographic redundancy.</p></div><p>Thundersnatch - I'm sorry to hear you've had the same types of troubles over the past few years at Rackspace.  I can't blame you for feeling burned by it, you're paying a good amount to have many 9's of uptime because whatever you're running online is clearly critical to your business.

It sounds like this is definitely something we can help you out with.  The company I work for (INetU) focuses on working with businesses who run critical operations online.  Do you have some time for a call?  My contact info is:

Rich Giunta
Sr. Solutions Consultant
INetU Inc.
988-664-6388 x109
rgiunta@inetu.net

Best Regards,

Rich</p></div>
	</htmltext>
<tokenext>We 're a Rackspace customer in their DFW datacenter .
This is the third power-related outage they 've had in the last two years at that supposedly world-class facility.The first was n't really their fault : truck driver with health condition runs into their transformers .
Generators kick in , but chillers do n't re-start quickly enough .
Temps skyrocket in minutes , emergency shutdowns .
Maybe the transformes should have had some $ 50 concrete pylons surrounding them ? The second outage was the result of a botched generator upgrade.This latest outage was the result of a botched UPS maintenance.None of the outages was long enough to trigger our failover policy to our DR site , but our customers definitely noticed.While their messaging has been very open and honest about the problems , and the SLA credits have been immediate , we pay them nearly $ 20K per month .
Nedless to say , we are shopping , and looking into a " multiple cheap colos " architecture instead of " Tier-1 managed hosting " .
Nothing beats geographic redundancy.Thundersnatch - I 'm sorry to hear you 've had the same types of troubles over the past few years at Rackspace .
I ca n't blame you for feeling burned by it , you 're paying a good amount to have many 9 's of uptime because whatever you 're running online is clearly critical to your business .
It sounds like this is definitely something we can help you out with .
The company I work for ( INetU ) focuses on working with businesses who run critical operations online .
Do you have some time for a call ?
My contact info is : Rich Giunta Sr. Solutions Consultant INetU Inc . 988-664-6388 x109 rgiunta @ inetu.net Best Regards , Rich</tokentext>
<sentencetext>We're a Rackspace customer in their DFW datacenter.
This is the third power-related outage they've had in the last two years at that supposedly world-class facility.The first wasn't really their fault: truck driver with health condition runs into their transformers.
Generators kick in, but chillers don't re-start quickly enough.
Temps skyrocket in minutes, emergency shutdowns.
Maybe the transformes should have had some $50 concrete pylons surrounding them?The second outage was the result of a botched generator upgrade.This latest outage was the result of a botched UPS maintenance.None of the outages was long enough to trigger our failover policy to our DR site, but our customers definitely noticed.While their messaging has been very open and honest about the problems, and the SLA credits have been immediate, we pay them nearly $20K per month.
Nedless to say, we are shopping, and looking into a "multiple cheap colos" architecture instead of "Tier-1 managed hosting".
Nothing beats geographic redundancy.Thundersnatch - I'm sorry to hear you've had the same types of troubles over the past few years at Rackspace.
I can't blame you for feeling burned by it, you're paying a good amount to have many 9's of uptime because whatever you're running online is clearly critical to your business.
It sounds like this is definitely something we can help you out with.
The company I work for (INetU) focuses on working with businesses who run critical operations online.
Do you have some time for a call?
My contact info is:

Rich Giunta
Sr. Solutions Consultant
INetU Inc.
988-664-6388 x109
rgiunta@inetu.net

Best Regards,

Rich
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603323</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603645</id>
	<title>Re:Downside to consolidation</title>
	<author>ls671</author>
	<datestamp>1246898340000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>&gt;&gt; "morons are building logically centralized systems"</p><p>I have worked with such a moron doing architecture on a big government project<nobr> <wbr></nobr>;-)) unbelievable...</p><p>His argument was that "The government likes centralized systems"<nobr> <wbr></nobr>;-))</p></htmltext>
<tokenext>&gt; &gt; " morons are building logically centralized systems " I have worked with such a moron doing architecture on a big government project ; - ) ) unbelievable...His argument was that " The government likes centralized systems " ; - ) )</tokentext>
<sentencetext>&gt;&gt; "morons are building logically centralized systems"I have worked with such a moron doing architecture on a big government project ;-)) unbelievable...His argument was that "The government likes centralized systems" ;-))</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602817</id>
	<title>Good</title>
	<author>jd2112</author>
	<datestamp>1246892520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I work for a company that makes high-end datacenter power systems, this should be good for business once the trade rags the CxOs read report on the millions and millions of lost business.<br> <br>
Or at least it will keep the sales staff busy writing up quotes that will be rejected for being too expensive (although much less than the cost of a prolonged outage...)</htmltext>
<tokenext>I work for a company that makes high-end datacenter power systems , this should be good for business once the trade rags the CxOs read report on the millions and millions of lost business .
Or at least it will keep the sales staff busy writing up quotes that will be rejected for being too expensive ( although much less than the cost of a prolonged outage... )</tokentext>
<sentencetext>I work for a company that makes high-end datacenter power systems, this should be good for business once the trade rags the CxOs read report on the millions and millions of lost business.
Or at least it will keep the sales staff busy writing up quotes that will be rejected for being too expensive (although much less than the cost of a prolonged outage...)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28612051</id>
	<title>Re:Outages</title>
	<author>Anonymous</author>
	<datestamp>1246996620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><i>Outages happen more than that. We have been in several data centers, ThePlanet and The Fortress both have had major outages in the last two years which has affected business.</i> <br>
<br>
I've been a hosting customer since 2000 with a large national firm.<br>
<br>
We've had exactly one outage that resulted in downtime of more then 30-60 minutes.  They released extensive information about the incident, what they were doing to fix it, and what steps were being put in place to prevent future incidents.</htmltext>
<tokenext>Outages happen more than that .
We have been in several data centers , ThePlanet and The Fortress both have had major outages in the last two years which has affected business .
I 've been a hosting customer since 2000 with a large national firm .
We 've had exactly one outage that resulted in downtime of more then 30-60 minutes .
They released extensive information about the incident , what they were doing to fix it , and what steps were being put in place to prevent future incidents .</tokentext>
<sentencetext>Outages happen more than that.
We have been in several data centers, ThePlanet and The Fortress both have had major outages in the last two years which has affected business.
I've been a hosting customer since 2000 with a large national firm.
We've had exactly one outage that resulted in downtime of more then 30-60 minutes.
They released extensive information about the incident, what they were doing to fix it, and what steps were being put in place to prevent future incidents.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604219</id>
	<title>Re:Be Redundant!</title>
	<author>DNS-and-BIND</author>
	<datestamp>1246904640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It wasn't me!!</htmltext>
<tokenext>It was n't me !
!</tokentext>
<sentencetext>It wasn't me!
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603585</id>
	<title>it was my fault</title>
	<author>bgd73</author>
	<datestamp>1246897980000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext> my pc. it is 3400mhz and all the data center host sites of my interest. for the first time in 21020 hours of perfect runtime the ups saved it in a series of northeast thunderstorms coniciding with the outages around the globe. the permeating physics were too much for the world, reverberating to an unintentional master of perfect float, hardly busy, waiting to send a message.

 Believe it or not.</htmltext>
<tokenext>my pc .
it is 3400mhz and all the data center host sites of my interest .
for the first time in 21020 hours of perfect runtime the ups saved it in a series of northeast thunderstorms coniciding with the outages around the globe .
the permeating physics were too much for the world , reverberating to an unintentional master of perfect float , hardly busy , waiting to send a message .
Believe it or not .</tokentext>
<sentencetext> my pc.
it is 3400mhz and all the data center host sites of my interest.
for the first time in 21020 hours of perfect runtime the ups saved it in a series of northeast thunderstorms coniciding with the outages around the globe.
the permeating physics were too much for the world, reverberating to an unintentional master of perfect float, hardly busy, waiting to send a message.
Believe it or not.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603037</id>
	<title>The solution is Geographical diversity</title>
	<author>bdwarr6</author>
	<datestamp>1246894200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This is why you should look into company's with geographical diversity such as Ubiquity (http://www.ubiquityservers.com) or various other companies in the data center market.</htmltext>
<tokenext>This is why you should look into company 's with geographical diversity such as Ubiquity ( http : //www.ubiquityservers.com ) or various other companies in the data center market .</tokentext>
<sentencetext>This is why you should look into company's with geographical diversity such as Ubiquity (http://www.ubiquityservers.com) or various other companies in the data center market.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601917</id>
	<title>Long live the cloud...long live the cloud....</title>
	<author>Anonymous</author>
	<datestamp>1246886040000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Just keep having your stupid cloud fantasies, you pathetic dweebs waiting for the Singularity to lift you from your humdrum  jobs.  Maybe if you focused at least some of your life around what it means to be a individual sentient mind and be content with that--instead of slaving away at the abstractions of 1s and 0s--the need for 'the Cloud' would evaporate and we would even consider this a story.</p></htmltext>
<tokenext>Just keep having your stupid cloud fantasies , you pathetic dweebs waiting for the Singularity to lift you from your humdrum jobs .
Maybe if you focused at least some of your life around what it means to be a individual sentient mind and be content with that--instead of slaving away at the abstractions of 1s and 0s--the need for 'the Cloud ' would evaporate and we would even consider this a story .</tokentext>
<sentencetext>Just keep having your stupid cloud fantasies, you pathetic dweebs waiting for the Singularity to lift you from your humdrum  jobs.
Maybe if you focused at least some of your life around what it means to be a individual sentient mind and be content with that--instead of slaving away at the abstractions of 1s and 0s--the need for 'the Cloud' would evaporate and we would even consider this a story.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939</id>
	<title>Damn you Michael Bay!</title>
	<author>StaticEngine</author>
	<datestamp>1246886160000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>"A blown transformer appears to be the culprit"</p><p>I'd heard the new movie was crude, but I didn't realize how crude it actually was!</p></htmltext>
<tokenext>" A blown transformer appears to be the culprit " I 'd heard the new movie was crude , but I did n't realize how crude it actually was !</tokentext>
<sentencetext>"A blown transformer appears to be the culprit"I'd heard the new movie was crude, but I didn't realize how crude it actually was!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28616327</id>
	<title>Re:UPSs cause more failures than they prevent!</title>
	<author>asackett</author>
	<datestamp>1246974420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Ain't it amazin' that all those UPS engineers whose workdays are nothing but thinking about the design of systems all arrive at the same conclusion and refuse to start their machines if the battery is failed? It's just incredible that these guys with EE degrees come out of college smart enough to do right things and somehow get it so wrong. Oh wait... I'm being sarcastic, which isn't very nice. I'd never suggest that the idiot isn't them, might instead be you, because that would be bad for my karma.</p></htmltext>
<tokenext>Ai n't it amazin ' that all those UPS engineers whose workdays are nothing but thinking about the design of systems all arrive at the same conclusion and refuse to start their machines if the battery is failed ?
It 's just incredible that these guys with EE degrees come out of college smart enough to do right things and somehow get it so wrong .
Oh wait... I 'm being sarcastic , which is n't very nice .
I 'd never suggest that the idiot is n't them , might instead be you , because that would be bad for my karma .</tokentext>
<sentencetext>Ain't it amazin' that all those UPS engineers whose workdays are nothing but thinking about the design of systems all arrive at the same conclusion and refuse to start their machines if the battery is failed?
It's just incredible that these guys with EE degrees come out of college smart enough to do right things and somehow get it so wrong.
Oh wait... I'm being sarcastic, which isn't very nice.
I'd never suggest that the idiot isn't them, might instead be you, because that would be bad for my karma.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28612297</id>
	<title>Re:Be Redundant!</title>
	<author>sjames</author>
	<datestamp>1246997580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>On the other hand, if your servers are all down, is there a lot of point to people knowing their IP address?</p><p>One secondary DNS per location is just fine. If there is just one datacenter, then use 2 DNS servers there.</p><p>It is recommended, but not required. The server police won't take your hardware away if you don't do it.</p></htmltext>
<tokenext>On the other hand , if your servers are all down , is there a lot of point to people knowing their IP address ? One secondary DNS per location is just fine .
If there is just one datacenter , then use 2 DNS servers there.It is recommended , but not required .
The server police wo n't take your hardware away if you do n't do it .</tokentext>
<sentencetext>On the other hand, if your servers are all down, is there a lot of point to people knowing their IP address?One secondary DNS per location is just fine.
If there is just one datacenter, then use 2 DNS servers there.It is recommended, but not required.
The server police won't take your hardware away if you don't do it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606035</id>
	<title>Buy Chinese; save money up front, but...</title>
	<author>Anonymous</author>
	<datestamp>1246970820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>pay down the road. Transformers going out? Guess where it was built? Until ppl quit buying inferior made products, we will see more and more of these issues come up.</htmltext>
<tokenext>pay down the road .
Transformers going out ?
Guess where it was built ?
Until ppl quit buying inferior made products , we will see more and more of these issues come up .</tokentext>
<sentencetext>pay down the road.
Transformers going out?
Guess where it was built?
Until ppl quit buying inferior made products, we will see more and more of these issues come up.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604755</id>
	<title>Re:Damn you Michael Bay!</title>
	<author>shentino</author>
	<datestamp>1246998000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Didn't ThePlanet recently have an outage for the exact same reason?<br><br>Methinks that electrical standards are falling behind the demand created by computing resources.</htmltext>
<tokenext>Did n't ThePlanet recently have an outage for the exact same reason ? Methinks that electrical standards are falling behind the demand created by computing resources .</tokentext>
<sentencetext>Didn't ThePlanet recently have an outage for the exact same reason?Methinks that electrical standards are falling behind the demand created by computing resources.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604313
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602049
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604491
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602357
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28610219
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603323
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603507
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605351
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602161
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28612297
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28616815
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28609133
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601899
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601765
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603645
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604755
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603845
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603779
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602595
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601765
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603297
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604201
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28608767
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603111
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602201
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28612051
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602049
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604989
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28611387
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603323
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604219
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28616327
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603911
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28609105
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605271
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602505
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602585
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602801
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_06_2244205_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28610709
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602583
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602817
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28606159
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28616327
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28616815
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28609105
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603037
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602441
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605351
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603645
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604201
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601939
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602161
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604755
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602847
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602583
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28610709
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601737
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604989
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603911
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603297
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603845
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602049
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28612051
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604313
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601765
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602595
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603779
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601899
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28609133
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602005
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602833
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602201
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603111
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28608767
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602063
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602505
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28605271
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603507
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602585
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28612297
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602801
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28602357
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604491
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28604219
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28603323
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28610219
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28611387
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_06_2244205.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_06_2244205.28601915
</commentlist>
</conversation>
