...but the overall goal is the same; the business doesn't want to worry about the infrastructure behind their app. They simply want it to work.
Which is why internal "clouds" have always amused me to no end...
It's understandable that you'd think that way if you don't understand how wildly organizational structures vary from organization to organization, and you're used to organizations where there is "The IT department" and customers of that IT department. In that case, yes, why on earth would The IT department build a "cloud", when the only customers of it would be themselves?
I'll give you an example of where this is arguably a good idea: NASA. Across ten or so centers, there are hundreds of generally self-sufficient small projects. The norm for many projects is to run their own small data centers (ranging from a single server running under someone's desk and up), because shared services typically don't provide the flexibility they need. Often this is software dev, wacky data distribution (like GDS), that sort of thing.
In that environment, an Infrastructure cloud (IaaS, whatever buzzword strikes your fancy) starts to make sense. Which is exactly what NASA is doing, though I'll reserve judgment as to how good of an idea it was until it's been in place for a couple of years.:) But in theory and on paper, it's not unreasonable to have an "internal" cloud.
I have no doubt that it would be similarly a "good idea" in other organizations, like a large university.
*I* can't follow a conversation? I responded directly to the point that the parent poster made about the aviation industry, and I even *disclaimed* my own ability to truly characterize the risk.
Can't YOU follow a conversation? I see it went like this:
My paraphrase of what RichiH said: I don't get why they didn't stop and check other drilling to make sure they aren't experiencing the same issues. And why don't they have requirements in place that would have mitigated the risk?
My paraphrase of what AC replied: Stop and check other drilling? What, do we stop and figure out what went wrong with an airplane when airplanes crash?
My paraphrase of what I said: Yes, as a matter of fact, we do. Not that I necessarily disagree with you, sir AC, but that's not supporting your argument.
You came in and started talking about misrepresentation of the findings of a panel, which I agree is the actual issue that TFA is about, but decidedly *NOT* what we were discussing in this *thread*.
Oh shit, a plane crashed, better ground all planes indefinitely until we figure out the cause.
You mean, like the grounding of the Airbus A380 until the root cause of the engine failure that caused an emergency landing last week is understood?
Or the grounding of the Boeing 787 until the root cause of the fire that caused an emergency landing earlier this week is understood?
Don't keep up much on the news, do ya? Personally, I don't really think a drilling moratorium was necessary (but I'm no expert), however, using the aviation industry as an example of light reactions to major failures isn't much going to help your point.
However, for any distance under (say) 600 miles or so, I'd agree: drive. It actually is quicker, and is substantially cheaper without the hassle. An hour to the airport, 1-3 hours waiting, an hour or so in transit, and another hour to get your bags, rental, etc. and then another 30 minutes to 2 hours to your actual destination. Anywhere on the seaboards, I'd say "just drive".
Anywhere along the Northeast Corridor, I'd say "Just Amtrak." (Just about to board an Acela Express, as a matter of fact...)
Now we also need them roaming the streets? "Hey Joe, hottie on your six, make a turn and flip the switch boy, let's see what she's got!".
I was actually watching the millimeter wave scanners in operation over the weekend while bored in the airport. Granted, it's anecdotal, but I was surprised that there were three young, large breasted females that were re-routed through the scanner in the course of maybe 15 minutes. (I, uh, notice this sort of thing.)
I'm pretty sure compared to the percentage of them "in the wild", they were significantly overrepresented in that scanner. Either that, or I'm hanging out in the wrong places "in the wild".
Again, if you read about this subject you'll see examples of people who HAD NO INTERNET ACCESS because they were volunteering to rebuild Haiti.
Interestingly, AT&T has a Haiti Relief international roaming package that gives you $0.50/MB data, $0.25/min calls to the US, and $0.10 outgoing text messages for $19.99. It about floored me. Compared with my trip there back in 2007, it's dirt cheap. In fact, compared to roaming rates in *Canada*, it's cheap.
This is less so at NASA, IME. I've been a contractor at NASA for just about 10 years. It's not abnormal for NASA contractor folk to move around between projects, but leaving the agency doesn't happen so much as I'd expect. When contracting companies change, generally all of the same people stay on board, but just get hired by the new contractor. Save, of course, for management.
The majority of the people who leave seem to do so out of disillusionment with NASA or better career opportunities. I'm finding myself more and more in the former category.
I just want the comments section to actually WORK in idle. Like, actually expand a comment when I click it instead of reloading the page with only that comment.
I was just in Haiti over the weekend. On my prior trip in 2007, Digicel was everywhere. This time, it was Viola, and relatively little Digicel. My phone connected to Viola. In fact, Digicel wasn't even listed in the list of carriers on my iPhone when I checked. I was actually wondering if they still existed.
What's striking about Haiti (and, from what I'm told from missionary friends, parts of Africa) is how many people have cell phones. People who don't even have electricity in their homes run around with cell phones. When you wander around the mission I was working at, everywhere you go there is a cell phone plugged in and charging. Viola even has charging stations at retailers in Port-au-Prince.
I'm saying it's bad to enjoy it as a sport. Capice?
If you're saying that it's wrong to kill deer for no other reason than to kill them, we're in agreement. If you kill a deer, you should eat the deer. It's why I don't fish, I find it enjoyable but I don't like eating fish.
The courts disagree. DC handgun ban is unconstitutional...
While I agree with the Court's decision in this particular case, I caution you against using "the courts agree" as a defense. The US Supreme Court has been making brain-dead obvious anti-constitutional decisions for most of its existence. Just because the Supreme Court rules something as constitutional does not make it so.
If your notion of leisure is blowing out the lungs of a deer with a high-powered rifle or bow-and-arrow, it qualifies you as a moron.
And what's your opinion of fishing? Are fishermen morons also? Are you somehow a übergenius because you get your slaughtered meat from the store?
I'm not into hunting myself, but I know quite a few deer hunters. They do it because they like deer meat, its cheap, AND they enjoy it.
If you say you're doing it to "keep deer from overpopulating" you are a moron and a bullshitter.
Have you ever lived anywhere rural? Have you ever hit a deer with your car? Had deer ruin your garden? Ever known someone who's had a run-in with Lyme disease? Deer *are* wildly over-populated.
Anyway, I understand your point is merely to state that you don't know any hunters that you consider to be non-morons. My point is that your standard for judging them is probably skewed, based on what you're saying.
And how would you know for sure that it would actually boot correctly the next time you actually *need* to?
There is nothing worse than having an actual unexpected reboot (UPS hiccup, whatever), and finding that the system that has been up for 3 years isn't booting, and not having ANY idea which patch put in place in the intervening time actually broke it.
Not that, ahem, I speak from experience, or anything...
Occasional rebooting is good, if for no other reason than making it happen in a controlled situation so you aren't surprised in an uncontrolled situation. If you really need the 100% uptime, then by all means, design a proper high availability system.
Slashdot Mirror
...but the overall goal is the same; the business doesn't want to worry about the infrastructure behind their app. They simply want it to work.
Which is why internal "clouds" have always amused me to no end...
It's understandable that you'd think that way if you don't understand how wildly organizational structures vary from organization to organization, and you're used to organizations where there is "The IT department" and customers of that IT department. In that case, yes, why on earth would The IT department build a "cloud", when the only customers of it would be themselves?
I'll give you an example of where this is arguably a good idea: NASA. Across ten or so centers, there are hundreds of generally self-sufficient small projects. The norm for many projects is to run their own small data centers (ranging from a single server running under someone's desk and up), because shared services typically don't provide the flexibility they need. Often this is software dev, wacky data distribution (like GDS), that sort of thing.
In that environment, an Infrastructure cloud (IaaS, whatever buzzword strikes your fancy) starts to make sense. Which is exactly what NASA is doing, though I'll reserve judgment as to how good of an idea it was until it's been in place for a couple of years. :) But in theory and on paper, it's not unreasonable to have an "internal" cloud.
I have no doubt that it would be similarly a "good idea" in other organizations, like a large university.
*I* can't follow a conversation? I responded directly to the point that the parent poster made about the aviation industry, and I even *disclaimed* my own ability to truly characterize the risk.
Can't YOU follow a conversation? I see it went like this:
My paraphrase of what RichiH said: I don't get why they didn't stop and check other drilling to make sure they aren't experiencing the same issues. And why don't they have requirements in place that would have mitigated the risk?
My paraphrase of what AC replied: Stop and check other drilling? What, do we stop and figure out what went wrong with an airplane when airplanes crash?
My paraphrase of what I said: Yes, as a matter of fact, we do. Not that I necessarily disagree with you, sir AC, but that's not supporting your argument.
You came in and started talking about misrepresentation of the findings of a panel, which I agree is the actual issue that TFA is about, but decidedly *NOT* what we were discussing in this *thread*.
Now go away.
Oh shit, a plane crashed, better ground all planes indefinitely until we figure out the cause.
You mean, like the grounding of the Airbus A380 until the root cause of the engine failure that caused an emergency landing last week is understood?
Or the grounding of the Boeing 787 until the root cause of the fire that caused an emergency landing earlier this week is understood?
Don't keep up much on the news, do ya? Personally, I don't really think a drilling moratorium was necessary (but I'm no expert), however, using the aviation industry as an example of light reactions to major failures isn't much going to help your point.
Proper availability is generally achieved through redundancy, not silly stunts like this.
However, for any distance under (say) 600 miles or so, I'd agree: drive. It actually is quicker, and is substantially cheaper without the hassle. An hour to the airport, 1-3 hours waiting, an hour or so in transit, and another hour to get your bags, rental, etc. and then another 30 minutes to 2 hours to your actual destination. Anywhere on the seaboards, I'd say "just drive".
Anywhere along the Northeast Corridor, I'd say "Just Amtrak." (Just about to board an Acela Express, as a matter of fact...)
Use his brain.
I'm sorry, but I don't want to live in a country where the judge can decide that they don't like a given law and ignore it.
This is what you're looking for: https://secure.eff.org/site/Ecommerce/3366529?VIEW_PRODUCT=true&product_id=1441&store_id=2441
Now we also need them roaming the streets? "Hey Joe, hottie on your six, make a turn and flip the switch boy, let's see what she's got!".
I was actually watching the millimeter wave scanners in operation over the weekend while bored in the airport. Granted, it's anecdotal, but I was surprised that there were three young, large breasted females that were re-routed through the scanner in the course of maybe 15 minutes. (I, uh, notice this sort of thing.)
I'm pretty sure compared to the percentage of them "in the wild", they were significantly overrepresented in that scanner. Either that, or I'm hanging out in the wrong places "in the wild".
He meant himself: Sculley admits it was a mistake to hire Sculley to run the company.
Again, if you read about this subject you'll see examples of people who HAD NO INTERNET ACCESS because they were volunteering to rebuild Haiti.
Interestingly, AT&T has a Haiti Relief international roaming package that gives you $0.50/MB data, $0.25/min calls to the US, and $0.10 outgoing text messages for $19.99. It about floored me. Compared with my trip there back in 2007, it's dirt cheap. In fact, compared to roaming rates in *Canada*, it's cheap.
The insane way: Tap into the actual mains distribution cables under the roads or on utility poles.
This is how it's done in Haiti. The crazy thing: Something like half of the electrical customers are connected illegally this way.
Last time I checked, OSX guests on Virtualbox only worked on OSX hosts.
Like Wave, right?
This is less so at NASA, IME. I've been a contractor at NASA for just about 10 years. It's not abnormal for NASA contractor folk to move around between projects, but leaving the agency doesn't happen so much as I'd expect. When contracting companies change, generally all of the same people stay on board, but just get hired by the new contractor. Save, of course, for management.
The majority of the people who leave seem to do so out of disillusionment with NASA or better career opportunities. I'm finding myself more and more in the former category.
NUMMI was GM.
Funny, it's working again. I hadn't tried it in a while. Thanks!
Take “idle.” out of the URL and reload the page. It’s a pain in the ass but it works.
That used to work for me, but now it always redirects to idle.
This may be a little crazy, but it's almost as if the /. "editors" don't actually *read* the site. !!!
I just want the comments section to actually WORK in idle. Like, actually expand a comment when I click it instead of reloading the page with only that comment.
So would dumping him in the ocean somewhere in the first 5 minutes
You're forgetting that's where he came from... Meesa think yousa don't remember.
Funny. :)
But just in case you're serious: http://www.voilacomcel.com/static/home.html
I was just in Haiti over the weekend. On my prior trip in 2007, Digicel was everywhere. This time, it was Viola, and relatively little Digicel. My phone connected to Viola. In fact, Digicel wasn't even listed in the list of carriers on my iPhone when I checked. I was actually wondering if they still existed.
What's striking about Haiti (and, from what I'm told from missionary friends, parts of Africa) is how many people have cell phones. People who don't even have electricity in their homes run around with cell phones. When you wander around the mission I was working at, everywhere you go there is a cell phone plugged in and charging. Viola even has charging stations at retailers in Port-au-Prince.
I'm saying it's bad to enjoy it as a sport. Capice?
If you're saying that it's wrong to kill deer for no other reason than to kill them, we're in agreement. If you kill a deer, you should eat the deer. It's why I don't fish, I find it enjoyable but I don't like eating fish.
The courts disagree. DC handgun ban is unconstitutional...
While I agree with the Court's decision in this particular case, I caution you against using "the courts agree" as a defense. The US Supreme Court has been making brain-dead obvious anti-constitutional decisions for most of its existence. Just because the Supreme Court rules something as constitutional does not make it so.
If your notion of leisure is blowing out the lungs of a deer with a high-powered rifle or bow-and-arrow, it qualifies you as a moron.
And what's your opinion of fishing? Are fishermen morons also? Are you somehow a übergenius because you get your slaughtered meat from the store?
I'm not into hunting myself, but I know quite a few deer hunters. They do it because they like deer meat, its cheap, AND they enjoy it.
If you say you're doing it to "keep deer from overpopulating" you are a moron and a bullshitter.
Have you ever lived anywhere rural? Have you ever hit a deer with your car? Had deer ruin your garden? Ever known someone who's had a run-in with Lyme disease? Deer *are* wildly over-populated.
Anyway, I understand your point is merely to state that you don't know any hunters that you consider to be non-morons. My point is that your standard for judging them is probably skewed, based on what you're saying.
And how would you know for sure that it would actually boot correctly the next time you actually *need* to?
There is nothing worse than having an actual unexpected reboot (UPS hiccup, whatever), and finding that the system that has been up for 3 years isn't booting, and not having ANY idea which patch put in place in the intervening time actually broke it.
Not that, ahem, I speak from experience, or anything...
Occasional rebooting is good, if for no other reason than making it happen in a controlled situation so you aren't surprised in an uncontrolled situation. If you really need the 100% uptime, then by all means, design a proper high availability system.