Slashdot Mirror
Ken Brill, the Man Who Defined the Data Center, Dies
dcblogs writes "The founder of the UpTime Institute, Kenneth G. Brill, 69, died Tuesday, the institute's parent company announced. Brill, an electrical engineer by training, is credited with playing an enormous role in shaping the modern data center industry. 'He singled-handedly crafted an industry out of nothing,' said Mike Manos, the chief technology officer at AOL, who had known Brill since the late 1990s. Until Brill's efforts, enterprises had been defining and measuring data centers in their own way, said Manos. 'There was no commonality.' Today, 'you can't go anywhere in the world without people talking about tier 1, tier 2, tier 3 data centers — it's that fundamental,' he said. In 2011, following Amazon's prolong outage, Brill warned that the perceived reliability of large cloud providers was going to lead to problems. 'There will always be an advocate for how it can be done cheaper, [but] if you haven't had a failure for five years — who is the advocate for reliability?' said Brill. 'My prediction is that in the years ahead, we will see more failures than we have been seeing, because people have forgotten what we had to do to get to where we are.'"
'My prediction is that in the years ahead, we will see more failures than we have been seeing, because people have forgotten what we had to do to get to where we are.'
And considering the cloud isn't exactly known for reliability right now, yet another reason not to trust your data out there.
"First they came for the slanderers and i said nothing."
Have gnu, will travel.
I thought Google defined the data-center.
http://infolab.stanford.edu/pub/voy/museum/pictures/display/0-4-Google.htm
Everything I write is lies, read between the lines.
on what each tier means.
This is a case where there are too many different standards, all using the same terms.
In any case, administrative processes are going to affect uptime numbers far more than simple infrastructure redundancy
remember that Google (who has some of the best uptime around) doesn't bother with dual power for it's servers, so it could not be more than a lowly tier 2 datacenter per some standards.
on what each tier means.
This is a case where there are too many different standards, all using the same terms.
In any case, administrative processes are going to affect uptime numbers far more than simple infrastructure redundancy
remember that Google (who has some of the best uptime around) doesn't bother with dual power for it's servers, so it could not be more than a lowly tier 2 datacenter per some standards.
The actual standards define availability redundancy and concurrency of systems, not of individual devices. When your systems are composed of multiple independent devices, it affects what is looked at accordingly.
a handful of selfish greedy people are no match for millions of selfish, greedy people -u4ya
With 0 comments preserved for eternity
rewriting history since 2109
It's a good way to go.
Who did what now?
From another article
Ken Brill, founder of the Uptime Institute and a forward thinker in data center design and operations, died this week at the age of 68, the Institute said on Thursday. The cause was cancer, a spokesman said.
Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
No, it is a data-defined software center.
There are many aspects of our society and world for which this is true, not just data centers.
By the taping of my glasses, something geeky this way passes
UpTime Institute got the tiers more standardized though; even some of the telecom companies have gone from Bellcore tiers to uptime tiers (1 most critical to 4 most critical). Ken and UpTime did a lot for the industry. They also did a lot to the industry. They tried to complicate the simplification in order to monetize it. Plenty of others are guilty of the same thing, but I do wish Uptime would go away as the standard-bearer.
Their solution is the right software and no legacy applcations, a lot of existing applications are not 'cloud scale' or whatever you want to call it.
So it won't automatically send the same request to an other machine and have it work.
That is what is needed if you want to play 'in the cloud' properly. Only then will you get reliability and costsavings.
All the other legacy applications people put 'in the cloud' will have less reliability in 'the cloud'.
New things are always on the horizon
'My prediction is that in the years ahead, we will see more failures than we have been seeing, because people have forgotten what we had to do to get to where we are.'
As long as data center engineers are at risk of being woken up in the middle of the night, they won't forget how to make sure things stay running.