<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_12_2224242</id>
	<title>Lightning Strikes Amazon's Cloud (Really)</title>
	<author>ScuttleMonkey</author>
	<datestamp>1244820300000</datestamp>
	<htmltext>The Register has details on a recent EC2 outage that is being <a href="http://www.theregister.co.uk/2009/06/12/lightning\_strikes\_amazon\_cloud/">blamed on a lightning strike</a> that zapped a power distribution unit of the data center.  The interruption only lasted around 6 hours, but the irony should last much longer.  <i>"While Amazon was correcting the problem, it told customers they had the option of launching new server instances to replace those that went down. But customers were also able to wait for their original instances to come back up after power was restored to the hardware in question."</i></htmltext>
<tokenext>The Register has details on a recent EC2 outage that is being blamed on a lightning strike that zapped a power distribution unit of the data center .
The interruption only lasted around 6 hours , but the irony should last much longer .
" While Amazon was correcting the problem , it told customers they had the option of launching new server instances to replace those that went down .
But customers were also able to wait for their original instances to come back up after power was restored to the hardware in question .
"</tokentext>
<sentencetext>The Register has details on a recent EC2 outage that is being blamed on a lightning strike that zapped a power distribution unit of the data center.
The interruption only lasted around 6 hours, but the irony should last much longer.
"While Amazon was correcting the problem, it told customers they had the option of launching new server instances to replace those that went down.
But customers were also able to wait for their original instances to come back up after power was restored to the hardware in question.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157</id>
	<title>Lightning once striked our office building.</title>
	<author>Anonymous</author>
	<datestamp>1244824920000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>Our computer room was down for three days as a result.   Amazon's six hour downtime looks like a big improvement.<br>.<p>

I have to wonder if those who are critical of Amazon here have ever experienced a direct lightning strike?  I doubt it.</p></htmltext>
<tokenext>Our computer room was down for three days as a result .
Amazon 's six hour downtime looks like a big improvement. . I have to wonder if those who are critical of Amazon here have ever experienced a direct lightning strike ?
I doubt it .</tokentext>
<sentencetext>Our computer room was down for three days as a result.
Amazon's six hour downtime looks like a big improvement..

I have to wonder if those who are critical of Amazon here have ever experienced a direct lightning strike?
I doubt it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319131</id>
	<title>Re:Lightning once striked our office building.</title>
	<author>Jim Hall</author>
	<datestamp>1244900460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>[Lightning once striked{sic} our office building.] Our computer room was down for three days as a result. Amazon's six hour downtime looks like a big improvement.</p></div><p>Never had a lightning strike, but last year the building transformer that feeds our data center Fucking Exploded (I was on the other side of the building, and I tell you the earth <em>moved</em>.) No injuries, since it's shielded from the building by a retaining wall. Backup power (UPS, generator) went totally dark about 30 minutes later, which should <em>never happen</em>, but it was an odd day.</p><p>We were down for about 12 hours. And we're a University, not a Fortune-100. Massive electrical repair can happen quickly if you have the right people involved, with the right agreements.</p></div>
	</htmltext>
<tokenext>[ Lightning once striked { sic } our office building .
] Our computer room was down for three days as a result .
Amazon 's six hour downtime looks like a big improvement.Never had a lightning strike , but last year the building transformer that feeds our data center Fucking Exploded ( I was on the other side of the building , and I tell you the earth moved .
) No injuries , since it 's shielded from the building by a retaining wall .
Backup power ( UPS , generator ) went totally dark about 30 minutes later , which should never happen , but it was an odd day.We were down for about 12 hours .
And we 're a University , not a Fortune-100 .
Massive electrical repair can happen quickly if you have the right people involved , with the right agreements .</tokentext>
<sentencetext>[Lightning once striked{sic} our office building.
] Our computer room was down for three days as a result.
Amazon's six hour downtime looks like a big improvement.Never had a lightning strike, but last year the building transformer that feeds our data center Fucking Exploded (I was on the other side of the building, and I tell you the earth moved.
) No injuries, since it's shielded from the building by a retaining wall.
Backup power (UPS, generator) went totally dark about 30 minutes later, which should never happen, but it was an odd day.We were down for about 12 hours.
And we're a University, not a Fortune-100.
Massive electrical repair can happen quickly if you have the right people involved, with the right agreements.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317287</id>
	<title>Re:What irony?</title>
	<author>Anonymous</author>
	<datestamp>1244826780000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>That a computing technology that was supposed to be largely immune to damage of individual "nodes" in the cloud could be taken down by lightning hitting a single point?</p></htmltext>
<tokenext>That a computing technology that was supposed to be largely immune to damage of individual " nodes " in the cloud could be taken down by lightning hitting a single point ?</tokentext>
<sentencetext>That a computing technology that was supposed to be largely immune to damage of individual "nodes" in the cloud could be taken down by lightning hitting a single point?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317303</id>
	<title>Re:What irony?</title>
	<author>Anonymous</author>
	<datestamp>1244826960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>No, that's not irony, that's just stupid.<br>Irony is beaming thoughts into someone else's head while wearing a tinfoil hat yourself.</p></htmltext>
<tokenext>No , that 's not irony , that 's just stupid.Irony is beaming thoughts into someone else 's head while wearing a tinfoil hat yourself .</tokentext>
<sentencetext>No, that's not irony, that's just stupid.Irony is beaming thoughts into someone else's head while wearing a tinfoil hat yourself.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318053</id>
	<title>Re:Lightning once striked our office building.</title>
	<author>Anonymous</author>
	<datestamp>1244924940000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><blockquote><div><p> <i>I have to wonder if those who are critical of Amazon here have ever experienced a direct lightning strike? I doubt it.</i></p></div> </blockquote><p> Just so people know, this can be a real bitch.</p><p>I took a direct lightning strike at one site I work with that entered the corner of the building, traveled down the inside wall leaving a scorch mark on two levels and into the basement where all the servers and switches were located. The lightening then traveled through the electrical service main lines to an encased transformer located in the parking lot next door causing it to explode with enough force that is shattered the windows of the bank building next door and a door panel was found on a rood about a block away. It appears that one half of the electrical system was grounded properly through a specific ground rod and the other half was tied into the plumbing that ran inches away from the lightning rod grounds. When they purchased the building, they didn't redo all the electrical on the side of the building that wasn't remodeled and that way of grounding was normal.</p><p>We lost 3 of the 5 servers instantly and couldn't keep the other two stable. Both switches were down, 20 of the 44 workstations along with the tape backup machine, copiers, and networked printers were completely dead when we got there. The entire building had a lightning/surge protector with battery backup and natural gas generator on the mains so they weren't too concerned over in house specific protections. Only the systems with UPS on them directly survived with the exceptions of the servers which I'm not sure if they died from the lightning strike or from getting soaked by the fire sprinklers that was set off by the strike. (surprisingly, there was no fire).</p><p>It took us two days at almost 20 hours a day among 5 people with a lot of borrowing from other sites, about 20 trips to five or six computer stores in the surrounding counties, and a generator to come back on line and be operational again. We even had a make shift phone system in place while waiting on a new Avaya to come in. We did this all before the electric company got the transformer replaced and service back on. Until we replaced the other machines that were thought not to be effected, we experienced all sorts of weird behavior on the network and I'm still not confident with the cabling even though it <a href="http://www.idealindustries.com/prodDetail.do?prodId=LanTEK2&amp;div=2&amp;l1=certifiers&amp;l2=lantek2" title="idealindustries.com">passed the testing.</a> [idealindustries.com] Of course I didn't run the certification so it might just be me not trusting others.</p><p>If you get a direct strike, you might as well count on replacing everything in a production environment. When I say direct strike, I mean evidence it actually hit the building and not something down the road and traveled to the building. It will be easier and cheaper in the long run. Now, I have as part of the catastrophe plan, a means to replace every computer and component on the network at one time just to be safe. If it wasn't for two other sites having the same tape drives, we would have had to wait a week for a replacement to come in and start the data recovery process. Thank god for off-site tape storage.</p></div>
	</htmltext>
<tokenext>I have to wonder if those who are critical of Amazon here have ever experienced a direct lightning strike ?
I doubt it .
Just so people know , this can be a real bitch.I took a direct lightning strike at one site I work with that entered the corner of the building , traveled down the inside wall leaving a scorch mark on two levels and into the basement where all the servers and switches were located .
The lightening then traveled through the electrical service main lines to an encased transformer located in the parking lot next door causing it to explode with enough force that is shattered the windows of the bank building next door and a door panel was found on a rood about a block away .
It appears that one half of the electrical system was grounded properly through a specific ground rod and the other half was tied into the plumbing that ran inches away from the lightning rod grounds .
When they purchased the building , they did n't redo all the electrical on the side of the building that was n't remodeled and that way of grounding was normal.We lost 3 of the 5 servers instantly and could n't keep the other two stable .
Both switches were down , 20 of the 44 workstations along with the tape backup machine , copiers , and networked printers were completely dead when we got there .
The entire building had a lightning/surge protector with battery backup and natural gas generator on the mains so they were n't too concerned over in house specific protections .
Only the systems with UPS on them directly survived with the exceptions of the servers which I 'm not sure if they died from the lightning strike or from getting soaked by the fire sprinklers that was set off by the strike .
( surprisingly , there was no fire ) .It took us two days at almost 20 hours a day among 5 people with a lot of borrowing from other sites , about 20 trips to five or six computer stores in the surrounding counties , and a generator to come back on line and be operational again .
We even had a make shift phone system in place while waiting on a new Avaya to come in .
We did this all before the electric company got the transformer replaced and service back on .
Until we replaced the other machines that were thought not to be effected , we experienced all sorts of weird behavior on the network and I 'm still not confident with the cabling even though it passed the testing .
[ idealindustries.com ] Of course I did n't run the certification so it might just be me not trusting others.If you get a direct strike , you might as well count on replacing everything in a production environment .
When I say direct strike , I mean evidence it actually hit the building and not something down the road and traveled to the building .
It will be easier and cheaper in the long run .
Now , I have as part of the catastrophe plan , a means to replace every computer and component on the network at one time just to be safe .
If it was n't for two other sites having the same tape drives , we would have had to wait a week for a replacement to come in and start the data recovery process .
Thank god for off-site tape storage .</tokentext>
<sentencetext> I have to wonder if those who are critical of Amazon here have ever experienced a direct lightning strike?
I doubt it.
Just so people know, this can be a real bitch.I took a direct lightning strike at one site I work with that entered the corner of the building, traveled down the inside wall leaving a scorch mark on two levels and into the basement where all the servers and switches were located.
The lightening then traveled through the electrical service main lines to an encased transformer located in the parking lot next door causing it to explode with enough force that is shattered the windows of the bank building next door and a door panel was found on a rood about a block away.
It appears that one half of the electrical system was grounded properly through a specific ground rod and the other half was tied into the plumbing that ran inches away from the lightning rod grounds.
When they purchased the building, they didn't redo all the electrical on the side of the building that wasn't remodeled and that way of grounding was normal.We lost 3 of the 5 servers instantly and couldn't keep the other two stable.
Both switches were down, 20 of the 44 workstations along with the tape backup machine, copiers, and networked printers were completely dead when we got there.
The entire building had a lightning/surge protector with battery backup and natural gas generator on the mains so they weren't too concerned over in house specific protections.
Only the systems with UPS on them directly survived with the exceptions of the servers which I'm not sure if they died from the lightning strike or from getting soaked by the fire sprinklers that was set off by the strike.
(surprisingly, there was no fire).It took us two days at almost 20 hours a day among 5 people with a lot of borrowing from other sites, about 20 trips to five or six computer stores in the surrounding counties, and a generator to come back on line and be operational again.
We even had a make shift phone system in place while waiting on a new Avaya to come in.
We did this all before the electric company got the transformer replaced and service back on.
Until we replaced the other machines that were thought not to be effected, we experienced all sorts of weird behavior on the network and I'm still not confident with the cabling even though it passed the testing.
[idealindustries.com] Of course I didn't run the certification so it might just be me not trusting others.If you get a direct strike, you might as well count on replacing everything in a production environment.
When I say direct strike, I mean evidence it actually hit the building and not something down the road and traveled to the building.
It will be easier and cheaper in the long run.
Now, I have as part of the catastrophe plan, a means to replace every computer and component on the network at one time just to be safe.
If it wasn't for two other sites having the same tape drives, we would have had to wait a week for a replacement to come in and start the data recovery process.
Thank god for off-site tape storage.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317161</id>
	<title>God here...</title>
	<author>Deus.1.01</author>
	<datestamp>1244824920000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Is the message clear?</p><p>-RMS</p></htmltext>
<tokenext>Is the message clear ? -RMS</tokentext>
<sentencetext>Is the message clear?-RMS</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317749</id>
	<title>Re:What irony?</title>
	<author>The Grim Reefer2</author>
	<datestamp>1244833560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Popular irony is like getting a fly in your white wine.</p></div><p>Actually that would be, "It's a black fly in your Chardonnay...<br>It's a death row pardon two minutes too late<br>And isn't it ironic... don't you think"</p></div>
	</htmltext>
<tokenext>Popular irony is like getting a fly in your white wine.Actually that would be , " It 's a black fly in your Chardonnay...It 's a death row pardon two minutes too lateAnd is n't it ironic... do n't you think "</tokentext>
<sentencetext>Popular irony is like getting a fly in your white wine.Actually that would be, "It's a black fly in your Chardonnay...It's a death row pardon two minutes too lateAnd isn't it ironic... don't you think"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317839</id>
	<title>We all know where lightings come from...</title>
	<author>Anonymous</author>
	<datestamp>1244835000000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><p>...the clouds!</p></htmltext>
<tokenext>...the clouds !</tokentext>
<sentencetext>...the clouds!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317079</id>
	<title>flanhrr</title>
	<author>Anonymous</author>
	<datestamp>1244824020000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>i c u</p></htmltext>
<tokenext>i c u</tokentext>
<sentencetext>i c u</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317815</id>
	<title>Re:What irony?</title>
	<author>zippthorne</author>
	<datestamp>1244834400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Regular irony is what happens to your drinking water when the junk yard dumps its old car bodies in the reservoir.</p><p>Or when a robot reads the definition of "irony" from the OED during a one-off production of the greatest opera ever.</p><p>Magnetite suspended in oil is pretty irony, too.</p><p>Your tin foil hat example is just plain, old, ordinary unfortunate coincidence.  a.k.a alanian irony.  Calling it "tin foil" when it's actually aluminum, however...</p><p>BTW, the the white wine thing actually is irony (well, fairly loosely).  See, in the song, it seems like she's saying that the fly ruined the wine.  But the wine is chardonnay, so it's actually the other way around.</p></htmltext>
<tokenext>Regular irony is what happens to your drinking water when the junk yard dumps its old car bodies in the reservoir.Or when a robot reads the definition of " irony " from the OED during a one-off production of the greatest opera ever.Magnetite suspended in oil is pretty irony , too.Your tin foil hat example is just plain , old , ordinary unfortunate coincidence .
a.k.a alanian irony .
Calling it " tin foil " when it 's actually aluminum , however...BTW , the the white wine thing actually is irony ( well , fairly loosely ) .
See , in the song , it seems like she 's saying that the fly ruined the wine .
But the wine is chardonnay , so it 's actually the other way around .</tokentext>
<sentencetext>Regular irony is what happens to your drinking water when the junk yard dumps its old car bodies in the reservoir.Or when a robot reads the definition of "irony" from the OED during a one-off production of the greatest opera ever.Magnetite suspended in oil is pretty irony, too.Your tin foil hat example is just plain, old, ordinary unfortunate coincidence.
a.k.a alanian irony.
Calling it "tin foil" when it's actually aluminum, however...BTW, the the white wine thing actually is irony (well, fairly loosely).
See, in the song, it seems like she's saying that the fly ruined the wine.
But the wine is chardonnay, so it's actually the other way around.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165</id>
	<title>What irony?</title>
	<author>MrMista\_B</author>
	<datestamp>1244825040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>What irony?</p><p>Maybe I'm just tired, but I'm not sure what irony is being referred to by the poster.</p></htmltext>
<tokenext>What irony ? Maybe I 'm just tired , but I 'm not sure what irony is being referred to by the poster .</tokentext>
<sentencetext>What irony?Maybe I'm just tired, but I'm not sure what irony is being referred to by the poster.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317151</id>
	<title>Well, now that that's over with....</title>
	<author>Anonymous</author>
	<datestamp>1244824860000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>There's nothing to worry about, because as we all know, Lightning never strikes twice.</p><p>Yay for savings on the surge protectors!</p></htmltext>
<tokenext>There 's nothing to worry about , because as we all know , Lightning never strikes twice.Yay for savings on the surge protectors !</tokentext>
<sentencetext>There's nothing to worry about, because as we all know, Lightning never strikes twice.Yay for savings on the surge protectors!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317955</id>
	<title>Re:Do any of you know how they survived?</title>
	<author>sirsnork</author>
	<datestamp>1244923680000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>RAID Controllers have batteries so they can remember whats in the cache (for about 48hours), not so they can write that data out to disks befoer they power off. When power is returned and thr disks come back up the cache is flushed before any other action, thereby keeping the array in one piece</htmltext>
<tokenext>RAID Controllers have batteries so they can remember whats in the cache ( for about 48hours ) , not so they can write that data out to disks befoer they power off .
When power is returned and thr disks come back up the cache is flushed before any other action , thereby keeping the array in one piece</tokentext>
<sentencetext>RAID Controllers have batteries so they can remember whats in the cache (for about 48hours), not so they can write that data out to disks befoer they power off.
When power is returned and thr disks come back up the cache is flushed before any other action, thereby keeping the array in one piece</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317415</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317091</id>
	<title>Struck the cloud, eh?</title>
	<author>BorgCopyeditor</author>
	<datestamp>1244824260000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Did it leave a silver lining?</p></htmltext>
<tokenext>Did it leave a silver lining ?</tokentext>
<sentencetext>Did it leave a silver lining?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28322063</id>
	<title>Re:Irony?</title>
	<author>Anonymous</author>
	<datestamp>1244884080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Lightning actually comes from the ground.</p></htmltext>
<tokenext>Lightning actually comes from the ground .</tokentext>
<sentencetext>Lightning actually comes from the ground.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320857</id>
	<title>Telecom</title>
	<author>Anonymous</author>
	<datestamp>1244916960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Telecom Class A data centers have a few characteristics to prevent - YES PREVENT - this type of issue.</p><p>a) lightning rods at every corner of the building and the highest points that are PROPERLY GROUNDED. Sometimes you need to drip water to get a good ground.<br>b) Power supplied from two or more *different* power substations<br>c) Local UPSes - different for each power feed.  We're talking $150K each.<br>d) On site generation (diesel or gas turbine usually)<br>e) Heavy construction to survive tornadoes and hurricanes<br>f) Strong physical security procedures (the computer, inside the cage, inside the room,  inside the room, in the center of the building).<br>g) data center floors may be located on huge springs to reduce earthquake impacts.<br>h) Not located an area prone to flooding, not even 100 year floods.<br>i) EMC DMX systems have built in batteries and capacitors with enough juice that if power is pulled, all data in cache will still be written to disk. <a href="http://www.emc.com/collateral/hardware/specification-sheet/c1166-dmx4-ss.pdf" title="emc.com" rel="nofollow">http://www.emc.com/collateral/hardware/specification-sheet/c1166-dmx4-ss.pdf</a> [emc.com]</p><p>And they usually get something else that the rest of us can't - extremely high prioritization for refueling. A trauma hospital may be higher priority, but other normal hospitals are lower priority that a telecom data center.</p><p>Did you ever wonder why your phone bill was so high? REDUNDANCY is a way of life.  Chances are your telecom has automatic fail over to a redundant system 500+ miles away too.  Keeping those systems and their data synchronized isn't cheap either. Fortunately, the huge data pipes are considered internal costs.</p></htmltext>
<tokenext>Telecom Class A data centers have a few characteristics to prevent - YES PREVENT - this type of issue.a ) lightning rods at every corner of the building and the highest points that are PROPERLY GROUNDED .
Sometimes you need to drip water to get a good ground.b ) Power supplied from two or more * different * power substationsc ) Local UPSes - different for each power feed .
We 're talking $ 150K each.d ) On site generation ( diesel or gas turbine usually ) e ) Heavy construction to survive tornadoes and hurricanesf ) Strong physical security procedures ( the computer , inside the cage , inside the room , inside the room , in the center of the building ) .g ) data center floors may be located on huge springs to reduce earthquake impacts.h ) Not located an area prone to flooding , not even 100 year floods.i ) EMC DMX systems have built in batteries and capacitors with enough juice that if power is pulled , all data in cache will still be written to disk .
http : //www.emc.com/collateral/hardware/specification-sheet/c1166-dmx4-ss.pdf [ emc.com ] And they usually get something else that the rest of us ca n't - extremely high prioritization for refueling .
A trauma hospital may be higher priority , but other normal hospitals are lower priority that a telecom data center.Did you ever wonder why your phone bill was so high ?
REDUNDANCY is a way of life .
Chances are your telecom has automatic fail over to a redundant system 500 + miles away too .
Keeping those systems and their data synchronized is n't cheap either .
Fortunately , the huge data pipes are considered internal costs .</tokentext>
<sentencetext>Telecom Class A data centers have a few characteristics to prevent - YES PREVENT - this type of issue.a) lightning rods at every corner of the building and the highest points that are PROPERLY GROUNDED.
Sometimes you need to drip water to get a good ground.b) Power supplied from two or more *different* power substationsc) Local UPSes - different for each power feed.
We're talking $150K each.d) On site generation (diesel or gas turbine usually)e) Heavy construction to survive tornadoes and hurricanesf) Strong physical security procedures (the computer, inside the cage, inside the room,  inside the room, in the center of the building).g) data center floors may be located on huge springs to reduce earthquake impacts.h) Not located an area prone to flooding, not even 100 year floods.i) EMC DMX systems have built in batteries and capacitors with enough juice that if power is pulled, all data in cache will still be written to disk.
http://www.emc.com/collateral/hardware/specification-sheet/c1166-dmx4-ss.pdf [emc.com]And they usually get something else that the rest of us can't - extremely high prioritization for refueling.
A trauma hospital may be higher priority, but other normal hospitals are lower priority that a telecom data center.Did you ever wonder why your phone bill was so high?
REDUNDANCY is a way of life.
Chances are your telecom has automatic fail over to a redundant system 500+ miles away too.
Keeping those systems and their data synchronized isn't cheap either.
Fortunately, the huge data pipes are considered internal costs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317763</id>
	<title>Re:Irony?</title>
	<author>jo42</author>
	<datestamp>1244833620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Amazon's definition of a "cloud" is a whole bunch of XEN-based VPSes running in less than a handful of data centers here and there.</p><p>Resilience is an exercise left to the customer.</p></htmltext>
<tokenext>Amazon 's definition of a " cloud " is a whole bunch of XEN-based VPSes running in less than a handful of data centers here and there.Resilience is an exercise left to the customer .</tokentext>
<sentencetext>Amazon's definition of a "cloud" is a whole bunch of XEN-based VPSes running in less than a handful of data centers here and there.Resilience is an exercise left to the customer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317481</id>
	<title>It evidently did</title>
	<author>grahamsz</author>
	<datestamp>1244829300000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>1</modscore>
	<htmltext><p>If i'm not mistaken then the whole point of a cloud is that you spread your processing around different hardware (in different geographies) and so that no part failing constitutes a total failure. Only one of Amazon's two zones went down so a well designed cloud app shouldn't have failed.</p></htmltext>
<tokenext>If i 'm not mistaken then the whole point of a cloud is that you spread your processing around different hardware ( in different geographies ) and so that no part failing constitutes a total failure .
Only one of Amazon 's two zones went down so a well designed cloud app should n't have failed .</tokentext>
<sentencetext>If i'm not mistaken then the whole point of a cloud is that you spread your processing around different hardware (in different geographies) and so that no part failing constitutes a total failure.
Only one of Amazon's two zones went down so a well designed cloud app shouldn't have failed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193</id>
	<title>Re:What irony?</title>
	<author>Anonymous</author>
	<datestamp>1244825340000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>I think the poster means popular irony, not irony as it actually means.

Popular irony is like getting a fly in your white wine.

Regular irony is not wearing your tin foil hat on the one day someone actually does beam thoughts into your brain.</htmltext>
<tokenext>I think the poster means popular irony , not irony as it actually means .
Popular irony is like getting a fly in your white wine .
Regular irony is not wearing your tin foil hat on the one day someone actually does beam thoughts into your brain .</tokentext>
<sentencetext>I think the poster means popular irony, not irony as it actually means.
Popular irony is like getting a fly in your white wine.
Regular irony is not wearing your tin foil hat on the one day someone actually does beam thoughts into your brain.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319659</id>
	<title>Re:Irony?</title>
	<author>MadnessASAP</author>
	<datestamp>1244906280000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Well as it just so happens most lightning is ground to cloud or cloud to cloud with very little cloud to ground.</p><p>  My nerdiness goes up to 11 by the way.</p></htmltext>
<tokenext>Well as it just so happens most lightning is ground to cloud or cloud to cloud with very little cloud to ground .
My nerdiness goes up to 11 by the way .</tokentext>
<sentencetext>Well as it just so happens most lightning is ground to cloud or cloud to cloud with very little cloud to ground.
My nerdiness goes up to 11 by the way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319713</id>
	<title>Re:It evidently did</title>
	<author>friedo</author>
	<datestamp>1244907060000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p> <i>Only one of Amazon's two zones went down</i> </p><p>
There are two <i>regions</i> (US and EU) each with several <i>availability zones</i> (US currently has four.) The AZ's are designed to be isolated from one another. This outage affected one AZ in the US region.
</p><p>
If you are doing load balancing across instances in multiple AZ's (or even using Amazon's own Elastic Load Balancing and Auto-Scaling features) you would have been fine, since this is exactly the kind of problem they're designed to handle.
</p></htmltext>
<tokenext>Only one of Amazon 's two zones went down There are two regions ( US and EU ) each with several availability zones ( US currently has four .
) The AZ 's are designed to be isolated from one another .
This outage affected one AZ in the US region .
If you are doing load balancing across instances in multiple AZ 's ( or even using Amazon 's own Elastic Load Balancing and Auto-Scaling features ) you would have been fine , since this is exactly the kind of problem they 're designed to handle .</tokentext>
<sentencetext> Only one of Amazon's two zones went down 
There are two regions (US and EU) each with several availability zones (US currently has four.
) The AZ's are designed to be isolated from one another.
This outage affected one AZ in the US region.
If you are doing load balancing across instances in multiple AZ's (or even using Amazon's own Elastic Load Balancing and Auto-Scaling features) you would have been fine, since this is exactly the kind of problem they're designed to handle.
</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317481</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173</id>
	<title>Inconcievable!</title>
	<author>Anonymous</author>
	<datestamp>1244825220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>While everyone is talking up the cloud and how resilient it is... this is just yet another example to never put all your eggs in one basket. If your service is so damn important that it can't go down - have it hosted in two places.</p><p>Notice, Amazon.com didn't go down...<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>While everyone is talking up the cloud and how resilient it is... this is just yet another example to never put all your eggs in one basket .
If your service is so damn important that it ca n't go down - have it hosted in two places.Notice , Amazon.com did n't go down... : )</tokentext>
<sentencetext>While everyone is talking up the cloud and how resilient it is... this is just yet another example to never put all your eggs in one basket.
If your service is so damn important that it can't go down - have it hosted in two places.Notice, Amazon.com didn't go down... :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320603</id>
	<title>Re:Who covers the cost?</title>
	<author>Anonymous</author>
	<datestamp>1244914860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>What if they insured with AIG?</p><p>Who covers the cost then?<nobr> <wbr></nobr>:)</p></div><p>Tax payers.</p></div>
	</htmltext>
<tokenext>What if they insured with AIG ? Who covers the cost then ?
: ) Tax payers .</tokentext>
<sentencetext>What if they insured with AIG?Who covers the cost then?
:)Tax payers.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317645</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317103</id>
	<title>Amazon</title>
	<author>Anonymous</author>
	<datestamp>1244824380000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>== Makes my pensu ERECTION!!!!</p></htmltext>
<tokenext>= = Makes my pensu ERECTION ! ! !
!</tokentext>
<sentencetext>== Makes my pensu ERECTION!!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317117</id>
	<title>Who covers the cost?</title>
	<author>Anonymous</author>
	<datestamp>1244824560000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Naive question: Are data centers usually insured for the cost of hardware replacement and/or loss of revenue in a situation like this?</p></htmltext>
<tokenext>Naive question : Are data centers usually insured for the cost of hardware replacement and/or loss of revenue in a situation like this ?</tokentext>
<sentencetext>Naive question: Are data centers usually insured for the cost of hardware replacement and/or loss of revenue in a situation like this?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191</id>
	<title>Do any of you know how they survived?</title>
	<author>mr\_stinky\_britches</author>
	<datestamp>1244825340000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Do any of you know how an instance could survive a power outage?  Surely every operation is written out to disk before it's performed..so how did they design it?</htmltext>
<tokenext>Do any of you know how an instance could survive a power outage ?
Surely every operation is written out to disk before it 's performed..so how did they design it ?</tokentext>
<sentencetext>Do any of you know how an instance could survive a power outage?
Surely every operation is written out to disk before it's performed..so how did they design it?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889</id>
	<title>Re:Irony?</title>
	<author>log0n</author>
	<datestamp>1244896920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>The irony is that a cloud was struck by lightning.  Lightning usually comes from clouds.</p><p>Sometimes we all need to tone back the nerd a bit<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>The irony is that a cloud was struck by lightning .
Lightning usually comes from clouds.Sometimes we all need to tone back the nerd a bit : )</tokentext>
<sentencetext>The irony is that a cloud was struck by lightning.
Lightning usually comes from clouds.Sometimes we all need to tone back the nerd a bit :)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28324687</id>
	<title>Re:Inconcievable!</title>
	<author>Servo</author>
	<datestamp>1244914980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You can make the "cloud" resilient, redundant, and highly available.  They obviously did not.   If the cloud is extended to two places then you don't need servers (virtual or otherwise) in two places.</p></htmltext>
<tokenext>You can make the " cloud " resilient , redundant , and highly available .
They obviously did not .
If the cloud is extended to two places then you do n't need servers ( virtual or otherwise ) in two places .</tokentext>
<sentencetext>You can make the "cloud" resilient, redundant, and highly available.
They obviously did not.
If the cloud is extended to two places then you don't need servers (virtual or otherwise) in two places.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318003</id>
	<title>Re:What irony?</title>
	<author>Sulphur</author>
	<datestamp>1244924340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hey hey you you get off a my cloud</htmltext>
<tokenext>Hey hey you you get off a my cloud</tokentext>
<sentencetext>Hey hey you you get off a my cloud</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317307</id>
	<title>Re:Inconcievable!</title>
	<author>nine-times</author>
	<datestamp>1244827020000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Well it does seem like it was pretty resilient:</p><p><div class="quote"><p>While Amazon was correcting the problem, it told customers they had the option of launching new server instances to replace those that went down.</p></div><p>So basically a set of servers went down, and it took down the particular instances running on those servers.  Customers were still able to take the same exact image and start new instances-- it sounds like immediately.  Now sure, it'd be nice if they worked out some kind of automatic clustering and failover to take care of this sort of thing for you, but when my server goes down with my dedicated host, I don't have the option to start up a new host immediately with the same exact configuration.</p></div>
	</htmltext>
<tokenext>Well it does seem like it was pretty resilient : While Amazon was correcting the problem , it told customers they had the option of launching new server instances to replace those that went down.So basically a set of servers went down , and it took down the particular instances running on those servers .
Customers were still able to take the same exact image and start new instances-- it sounds like immediately .
Now sure , it 'd be nice if they worked out some kind of automatic clustering and failover to take care of this sort of thing for you , but when my server goes down with my dedicated host , I do n't have the option to start up a new host immediately with the same exact configuration .</tokentext>
<sentencetext>Well it does seem like it was pretty resilient:While Amazon was correcting the problem, it told customers they had the option of launching new server instances to replace those that went down.So basically a set of servers went down, and it took down the particular instances running on those servers.
Customers were still able to take the same exact image and start new instances-- it sounds like immediately.
Now sure, it'd be nice if they worked out some kind of automatic clustering and failover to take care of this sort of thing for you, but when my server goes down with my dedicated host, I don't have the option to start up a new host immediately with the same exact configuration.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317139</id>
	<title>Bars</title>
	<author>Anonymous</author>
	<datestamp>1244824800000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Nice story. The story has lots of twist and turns which makes it interesting.<br>=============<br>Karen Walter<br><a href="http://www.restaurantjobboard.com/category/bartender" title="restaurantjobboard.com" rel="nofollow">Bartending Jobs</a> [restaurantjobboard.com]</p></htmltext>
<tokenext>Nice story .
The story has lots of twist and turns which makes it interesting. = = = = = = = = = = = = = Karen WalterBartending Jobs [ restaurantjobboard.com ]</tokentext>
<sentencetext>Nice story.
The story has lots of twist and turns which makes it interesting.=============Karen WalterBartending Jobs [restaurantjobboard.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089</id>
	<title>Irony?</title>
	<author>Anonymous</author>
	<datestamp>1244824260000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Isn't cloud computing supposed to tackle such instances?</htmltext>
<tokenext>Is n't cloud computing supposed to tackle such instances ?</tokentext>
<sentencetext>Isn't cloud computing supposed to tackle such instances?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28321971</id>
	<title>Re:Well, now that that's over with....</title>
	<author>P1h3r1e3d13</author>
	<datestamp>1244926380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The guy who played Jesus in The Passion of the Christ got hit twice during filming.<br>
<br>
Also, lightning rods on tall buildings can get hit hundreds of times annually.</htmltext>
<tokenext>The guy who played Jesus in The Passion of the Christ got hit twice during filming .
Also , lightning rods on tall buildings can get hit hundreds of times annually .</tokentext>
<sentencetext>The guy who played Jesus in The Passion of the Christ got hit twice during filming.
Also, lightning rods on tall buildings can get hit hundreds of times annually.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317151</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317601</id>
	<title>Re:Lightning once striked our office building.</title>
	<author>Anonymous</author>
	<datestamp>1244831460000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Three days is lucky.  My very first job (many, many moons ago) was at a company which had a few 5, 10 and 15 meter SATCOM dishes outside.  One fall night, a set of severe T-storms rolled through around 2 am, and lightning struck the SAT farm.  Nearly knocked me out of my NOC chair where I was fighting to stay awake, and I swore something big had exploded outside.</p><p>Turns out, one of the SAT dishes had not been properly grounded, and the current surged through the SATNET into our internal networks.  Several mid-range systems, network gear, LAN pc's, modems, etc were fried. Console terminals were also, and if I'd been typing instead of fighting sleep, I would have been crispy.</p><p>The next several days were spent replacing the instantly fried gear. But initially unaffected systems started having serious glitches show up over the next few weeks.  My guess is that Amazon may have this same problem.</p></htmltext>
<tokenext>Three days is lucky .
My very first job ( many , many moons ago ) was at a company which had a few 5 , 10 and 15 meter SATCOM dishes outside .
One fall night , a set of severe T-storms rolled through around 2 am , and lightning struck the SAT farm .
Nearly knocked me out of my NOC chair where I was fighting to stay awake , and I swore something big had exploded outside.Turns out , one of the SAT dishes had not been properly grounded , and the current surged through the SATNET into our internal networks .
Several mid-range systems , network gear , LAN pc 's , modems , etc were fried .
Console terminals were also , and if I 'd been typing instead of fighting sleep , I would have been crispy.The next several days were spent replacing the instantly fried gear .
But initially unaffected systems started having serious glitches show up over the next few weeks .
My guess is that Amazon may have this same problem .</tokentext>
<sentencetext>Three days is lucky.
My very first job (many, many moons ago) was at a company which had a few 5, 10 and 15 meter SATCOM dishes outside.
One fall night, a set of severe T-storms rolled through around 2 am, and lightning struck the SAT farm.
Nearly knocked me out of my NOC chair where I was fighting to stay awake, and I swore something big had exploded outside.Turns out, one of the SAT dishes had not been properly grounded, and the current surged through the SATNET into our internal networks.
Several mid-range systems, network gear, LAN pc's, modems, etc were fried.
Console terminals were also, and if I'd been typing instead of fighting sleep, I would have been crispy.The next several days were spent replacing the instantly fried gear.
But initially unaffected systems started having serious glitches show up over the next few weeks.
My guess is that Amazon may have this same problem.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318021</id>
	<title>Re:Do any of you know how they survived?</title>
	<author>rivaldufus</author>
	<datestamp>1244924460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>the problem was that the lightning rods were all grounded to the pdus....</htmltext>
<tokenext>the problem was that the lightning rods were all grounded to the pdus... .</tokentext>
<sentencetext>the problem was that the lightning rods were all grounded to the pdus....</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317415</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317475</id>
	<title>Apropos, sure.  Irony, nah</title>
	<author>dmomo</author>
	<datestamp>1244829300000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext><p>Unless by Irony, you mean "like rain on your wedding day"</p></htmltext>
<tokenext>Unless by Irony , you mean " like rain on your wedding day "</tokentext>
<sentencetext>Unless by Irony, you mean "like rain on your wedding day"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320401</id>
	<title>speaking of lightning and electronics.</title>
	<author>stine2469</author>
	<datestamp>1244913240000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><tt>Back in the late 80's, I worked as network admin at a university.&nbsp; &nbsp;Most of the buildings on campus where relatively old, but I only had recurring problems in one of them.&nbsp; &nbsp;The building that held the English and History departments had an Equinox LM-48 in a cabinet in the back of a typing lab.&nbsp; &nbsp;One Monday morning we got a call that no-one in the building could get online.&nbsp; &nbsp;I checked the DS-15 port in the data center, and sure enough, no link, so I walked over to the lab and met the assistant dean who had the keys to let me in.&nbsp; When he unlocked the door, we both knew something was wrong because we could both smell the fried electronics... When I disconnected the LM-48 and picked it up,&nbsp; we could both hear what turned out to be pieces of serial chips rattling around inside the case.&nbsp; &nbsp; I replaced the unit with a spare and took the dead one back to my office.&nbsp; When I opened it up, I could see a couple (don't remember how many) of the chips had been blown up.&nbsp; &nbsp;Looking back, I probably had enough information to determine which PCs weren't grounded by which chips blew up, but that didn't occur to me then.&nbsp; &nbsp;About a month or so later, the same thing happened, but it happened on a week-night and when I heard the thunder, I knew I had just lost the replacement unit.&nbsp; &nbsp;Unfortunatlely, this was at 1am or so and I did not have keys to the English department.... So at 7am the next morning, when the assistant dean showed up, I was sitting outside his office with another replacement.&nbsp; &nbsp;He said something like "...the storm last night..." and I just nodded.<br><br>I don't remember the final resolution of the problem, but I do remember that from the 2nd strike until the problem was solved, every time I heard thunder I would run to the English building and with my newly assigned key, run upstairs and disconnect the rj-21 fanout cables.&nbsp; &nbsp;I would then leave a note on the English dept office informing them that they'd need to plug them in the in a.m.&nbsp; &nbsp; One evening, I didn't make it.&nbsp; I heard thunder and bolted for the English dept... I had my key in the buildings' outside door when lightning struck the building...and I knew I was too late.&nbsp; When I got upstairs, I could smell burnt electronics....<br><br>Probably at the same time as this was going on for me, my dad, who was a large-scale CSE had similar problems.&nbsp; &nbsp;I don't know how much 16-port line-cards for the system that he was supporting cost, but one day he had to replace eight or nine of them.&nbsp; &nbsp;The next day, UPS delivered two cases of copper-fiber-copper serial surge suppressors and he scheduled to install them.&nbsp; I don't think that site had problems after that.</tt></htmltext>
<tokenext>Back in the late 80 's , I worked as network admin at a university.     Most of the buildings on campus where relatively old , but I only had recurring problems in one of them.     The building that held the English and History departments had an Equinox LM-48 in a cabinet in the back of a typing lab.     One Monday morning we got a call that no-one in the building could get online.     I checked the DS-15 port in the data center , and sure enough , no link , so I walked over to the lab and met the assistant dean who had the keys to let me in.   When he unlocked the door , we both knew something was wrong because we could both smell the fried electronics... When I disconnected the LM-48 and picked it up ,   we could both hear what turned out to be pieces of serial chips rattling around inside the case.     I replaced the unit with a spare and took the dead one back to my office.   When I opened it up , I could see a couple ( do n't remember how many ) of the chips had been blown up.     Looking back , I probably had enough information to determine which PCs were n't grounded by which chips blew up , but that did n't occur to me then.     About a month or so later , the same thing happened , but it happened on a week-night and when I heard the thunder , I knew I had just lost the replacement unit.     Unfortunatlely , this was at 1am or so and I did not have keys to the English department.... So at 7am the next morning , when the assistant dean showed up , I was sitting outside his office with another replacement.     He said something like " ...the storm last night... " and I just nodded.I do n't remember the final resolution of the problem , but I do remember that from the 2nd strike until the problem was solved , every time I heard thunder I would run to the English building and with my newly assigned key , run upstairs and disconnect the rj-21 fanout cables.     I would then leave a note on the English dept office informing them that they 'd need to plug them in the in a.m.     One evening , I did n't make it.   I heard thunder and bolted for the English dept... I had my key in the buildings ' outside door when lightning struck the building...and I knew I was too late.   When I got upstairs , I could smell burnt electronics....Probably at the same time as this was going on for me , my dad , who was a large-scale CSE had similar problems.     I do n't know how much 16-port line-cards for the system that he was supporting cost , but one day he had to replace eight or nine of them.     The next day , UPS delivered two cases of copper-fiber-copper serial surge suppressors and he scheduled to install them.   I do n't think that site had problems after that .</tokentext>
<sentencetext>Back in the late 80's, I worked as network admin at a university.   Most of the buildings on campus where relatively old, but I only had recurring problems in one of them.   The building that held the English and History departments had an Equinox LM-48 in a cabinet in the back of a typing lab.   One Monday morning we got a call that no-one in the building could get online.   I checked the DS-15 port in the data center, and sure enough, no link, so I walked over to the lab and met the assistant dean who had the keys to let me in.  When he unlocked the door, we both knew something was wrong because we could both smell the fried electronics... When I disconnected the LM-48 and picked it up,  we could both hear what turned out to be pieces of serial chips rattling around inside the case.    I replaced the unit with a spare and took the dead one back to my office.  When I opened it up, I could see a couple (don't remember how many) of the chips had been blown up.   Looking back, I probably had enough information to determine which PCs weren't grounded by which chips blew up, but that didn't occur to me then.   About a month or so later, the same thing happened, but it happened on a week-night and when I heard the thunder, I knew I had just lost the replacement unit.   Unfortunatlely, this was at 1am or so and I did not have keys to the English department.... So at 7am the next morning, when the assistant dean showed up, I was sitting outside his office with another replacement.   He said something like "...the storm last night..." and I just nodded.I don't remember the final resolution of the problem, but I do remember that from the 2nd strike until the problem was solved, every time I heard thunder I would run to the English building and with my newly assigned key, run upstairs and disconnect the rj-21 fanout cables.   I would then leave a note on the English dept office informing them that they'd need to plug them in the in a.m.    One evening, I didn't make it.  I heard thunder and bolted for the English dept... I had my key in the buildings' outside door when lightning struck the building...and I knew I was too late.  When I got upstairs, I could smell burnt electronics....Probably at the same time as this was going on for me, my dad, who was a large-scale CSE had similar problems.   I don't know how much 16-port line-cards for the system that he was supporting cost, but one day he had to replace eight or nine of them.   The next day, UPS delivered two cases of copper-fiber-copper serial surge suppressors and he scheduled to install them.  I don't think that site had problems after that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317273</id>
	<title>Re:What irony?</title>
	<author>ZorbaTHut</author>
	<datestamp>1244826540000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>In Soviet Russia, clouds get hit by lightning?</p><p>Yeah, it's sorta weak, but that's what they were going for.</p></htmltext>
<tokenext>In Soviet Russia , clouds get hit by lightning ? Yeah , it 's sorta weak , but that 's what they were going for .</tokentext>
<sentencetext>In Soviet Russia, clouds get hit by lightning?Yeah, it's sorta weak, but that's what they were going for.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318215</id>
	<title>Having taken weather and climate 101...</title>
	<author>turing\_m</author>
	<datestamp>1244884200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>This is clearly a case of cloud-to-cloud lightning.</p></htmltext>
<tokenext>This is clearly a case of cloud-to-cloud lightning .</tokentext>
<sentencetext>This is clearly a case of cloud-to-cloud lightning.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317539</id>
	<title>Re:Do any of you know how they survived?</title>
	<author>Anonymous</author>
	<datestamp>1244830260000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p><div class="quote"><p>Do any of you know how an instance could survive a power outage?  Surely every operation is written out to disk before it's performed..so how did they design it?</p></div><p>Unless they were using ext4.</p></div>
	</htmltext>
<tokenext>Do any of you know how an instance could survive a power outage ?
Surely every operation is written out to disk before it 's performed..so how did they design it ? Unless they were using ext4 .</tokentext>
<sentencetext>Do any of you know how an instance could survive a power outage?
Surely every operation is written out to disk before it's performed..so how did they design it?Unless they were using ext4.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317417</id>
	<title>Re:What irony?</title>
	<author>quanticle</author>
	<datestamp>1244828640000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Perhaps they were referring to the irony of Amazon's EC2 being affected by one of the very natural disasters it advertises protection against.</p><p>Its rather like an "unsinkable" vessel going down on her maiden voyage.</p></htmltext>
<tokenext>Perhaps they were referring to the irony of Amazon 's EC2 being affected by one of the very natural disasters it advertises protection against.Its rather like an " unsinkable " vessel going down on her maiden voyage .</tokentext>
<sentencetext>Perhaps they were referring to the irony of Amazon's EC2 being affected by one of the very natural disasters it advertises protection against.Its rather like an "unsinkable" vessel going down on her maiden voyage.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317333</id>
	<title>Lightning once striked my friends house.</title>
	<author>z4ckpete</author>
	<datestamp>1244827260000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext>It blew a hole in the kitchen so big you could climb through it.</htmltext>
<tokenext>It blew a hole in the kitchen so big you could climb through it .</tokentext>
<sentencetext>It blew a hole in the kitchen so big you could climb through it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28478169</id>
	<title>Re:Irony?</title>
	<author>Hurricane78</author>
	<datestamp>1245957660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>There's a "in soviet amazon" joke in there somewhere. I know it!</p></htmltext>
<tokenext>There 's a " in soviet amazon " joke in there somewhere .
I know it !</tokentext>
<sentencetext>There's a "in soviet amazon" joke in there somewhere.
I know it!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317271</id>
	<title>Re:Do any of you know how they survived?</title>
	<author>Darkness404</author>
	<datestamp>1244826540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Any decent server is at the very least hooked up to a UPS, I would imagine that any mission-critical desktops would be too.</htmltext>
<tokenext>Any decent server is at the very least hooked up to a UPS , I would imagine that any mission-critical desktops would be too .</tokentext>
<sentencetext>Any decent server is at the very least hooked up to a UPS, I would imagine that any mission-critical desktops would be too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28323501</id>
	<title>Re:Who covers the cost?</title>
	<author>afidel</author>
	<datestamp>1244898300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Probably too much money to buy insurance, if you're that large having multiple physically dispersed systems IS your insurance. For the customers the insurance is included in the cost of the service, Amazon adds a little bit to the bill and puts it in a fund in case they have to issue SLA related refunds (or more likely they just make less that month due to issuing credits).</htmltext>
<tokenext>Probably too much money to buy insurance , if you 're that large having multiple physically dispersed systems IS your insurance .
For the customers the insurance is included in the cost of the service , Amazon adds a little bit to the bill and puts it in a fund in case they have to issue SLA related refunds ( or more likely they just make less that month due to issuing credits ) .</tokentext>
<sentencetext>Probably too much money to buy insurance, if you're that large having multiple physically dispersed systems IS your insurance.
For the customers the insurance is included in the cost of the service, Amazon adds a little bit to the bill and puts it in a fund in case they have to issue SLA related refunds (or more likely they just make less that month due to issuing credits).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317117</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317645</id>
	<title>Re:Who covers the cost?</title>
	<author>Anonymous</author>
	<datestamp>1244832000000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>What if they insured with AIG?<br><br>Who covers the cost then?<nobr> <wbr></nobr>:)</htmltext>
<tokenext>What if they insured with AIG ? Who covers the cost then ?
: )</tokentext>
<sentencetext>What if they insured with AIG?Who covers the cost then?
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317117</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317415</id>
	<title>Re:Do any of you know how they survived?</title>
	<author>KahabutDieDrake</author>
	<datestamp>1244828580000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>You've never actually worked with enterprise class gear have you?  It's standard for most of the servers and all of the data storage to have capacitance/battery backups for just such an emergency.  <br> <br>Typically, the raid controller will have enough on board capacity to clear it's write cache before losing power entirely.  While the drive array will be connected to a decent UPS that can hold for at least a few minutes.  Meanwhile, the server itself will also likely be connected to the same UPS, or a different one.<br> <br> The real question at hand is, were the UPS between the power distribution node and the server, or were they on the other side of the distribution node, and therefore worthless in a case like this?  I've seen both configurations, but the latter is rarer.  Not because of this particular case, but because of efficiency concerns.<br> <br> If there was a failure of design, it was most likely in the building wiring itself.  The building was clearly not properly grounded against lightning strikes, as if it was, the surge would never have hit the internal wiring.  It might have kicked the building off the grid for a time, but it should never have reached a power distribution node.  Although it's likely the outcome would be similar if not identical.</htmltext>
<tokenext>You 've never actually worked with enterprise class gear have you ?
It 's standard for most of the servers and all of the data storage to have capacitance/battery backups for just such an emergency .
Typically , the raid controller will have enough on board capacity to clear it 's write cache before losing power entirely .
While the drive array will be connected to a decent UPS that can hold for at least a few minutes .
Meanwhile , the server itself will also likely be connected to the same UPS , or a different one .
The real question at hand is , were the UPS between the power distribution node and the server , or were they on the other side of the distribution node , and therefore worthless in a case like this ?
I 've seen both configurations , but the latter is rarer .
Not because of this particular case , but because of efficiency concerns .
If there was a failure of design , it was most likely in the building wiring itself .
The building was clearly not properly grounded against lightning strikes , as if it was , the surge would never have hit the internal wiring .
It might have kicked the building off the grid for a time , but it should never have reached a power distribution node .
Although it 's likely the outcome would be similar if not identical .</tokentext>
<sentencetext>You've never actually worked with enterprise class gear have you?
It's standard for most of the servers and all of the data storage to have capacitance/battery backups for just such an emergency.
Typically, the raid controller will have enough on board capacity to clear it's write cache before losing power entirely.
While the drive array will be connected to a decent UPS that can hold for at least a few minutes.
Meanwhile, the server itself will also likely be connected to the same UPS, or a different one.
The real question at hand is, were the UPS between the power distribution node and the server, or were they on the other side of the distribution node, and therefore worthless in a case like this?
I've seen both configurations, but the latter is rarer.
Not because of this particular case, but because of efficiency concerns.
If there was a failure of design, it was most likely in the building wiring itself.
The building was clearly not properly grounded against lightning strikes, as if it was, the surge would never have hit the internal wiring.
It might have kicked the building off the grid for a time, but it should never have reached a power distribution node.
Although it's likely the outcome would be similar if not identical.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317261</id>
	<title>Re:Do any of you know how they survived?</title>
	<author>ShadowRangerRIT</author>
	<datestamp>1244826240000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>UPS, or backup generator, or some other equivalent system that gives just enough power for a clean shut down.  I've seen blades with built-in UPS (possibly not even a battery, just a capacitor) that exists solely to sync to disk in the event of a power loss.</htmltext>
<tokenext>UPS , or backup generator , or some other equivalent system that gives just enough power for a clean shut down .
I 've seen blades with built-in UPS ( possibly not even a battery , just a capacitor ) that exists solely to sync to disk in the event of a power loss .</tokentext>
<sentencetext>UPS, or backup generator, or some other equivalent system that gives just enough power for a clean shut down.
I've seen blades with built-in UPS (possibly not even a battery, just a capacitor) that exists solely to sync to disk in the event of a power loss.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317289</id>
	<title>Probability</title>
	<author>PleaseFearMe</author>
	<datestamp>1244826840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If a service is so resilient that it takes a highly unlikely lightning strike for it to go down, then the service is good.</htmltext>
<tokenext>If a service is so resilient that it takes a highly unlikely lightning strike for it to go down , then the service is good .</tokentext>
<sentencetext>If a service is so resilient that it takes a highly unlikely lightning strike for it to go down, then the service is good.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317475
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317333
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317307
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317417
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319713
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317481
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317271
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317955
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317415
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320603
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317645
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317117
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317539
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28324687
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317601
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317815
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28322063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317287
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317261
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317303
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317749
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318053
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28323501
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317117
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317289
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320857
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319659
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318003
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28321971
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317151
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318021
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317415
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317763
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28478169
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_12_2224242_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317273
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317117
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28323501
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317645
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320603
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317161
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317151
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28321971
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317191
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317415
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317955
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318021
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317261
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317271
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317539
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28320857
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317157
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317601
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319131
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318053
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317333
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317165
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317193
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317749
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317815
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318003
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317303
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317417
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317273
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317287
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317475
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317173
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28324687
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317289
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317307
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_12_2224242.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317089
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317763
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28318889
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319659
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28322063
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28478169
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28317481
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_12_2224242.28319713
</commentlist>
</conversation>
