Cool Linux Tricks With Atlas 127
dpilgrim writes: "Looks like some powerful players want to see Linux going toe to toe with Unix 'big iron.' Would you like to be able to run two Linuxes simultaneously on the same box? Or seemless swap processor and memory in and out of your machine? The Atlas project aims to bring you all that and more. There's a press release from TurboLinux reported here, and a more in-depth article running on SourceForge's
Linux on Large Systems Foundry."
Do you need special MOBO to hot swap memory/cpu (Score:1)
Re:Do you need special MOBO to hot swap memory/cpu (Score:1)
Heh heh.
Dumb ass.
Re:Do you need special MOBO to hot swap memory/cpu (Score:4, Informative)
Re:Do you need special MOBO to hot swap memory/cpu (Score:1)
Seriously, though, yes you need special hardware on the motherboard side (HP has hot-swap PCI system(s), and IBM has hot-swap everything but not for ia32 or ia64 class hardware). AFAIK, the CPU/RAM/PCI card itself does not need to be special, just the motherboard.
As for hot-swap RAM, it is _very_ hard to do this without special hardware support. You would need something like RAID for RAM + special hardware that would let you remove/install DIMMs live.
Re:Do you need special MOBO to hot swap memory/cpu (Score:1)
Re:Do you need special MOBO to hot swap memory/cpu (Score:1)
I realize its not difficult to add that functionality to an OS, but you introduce at least one and probably many third parties (the OS developers) that you then need to rely on to add this functionality according to some spec that might take years for everyone to agree on..And of course, it won't work with older versions of the OS(es)...
In any case, hot-swappable-everything is neat, but usually not worth the increased price of the hardware involved unless you have very specific needs.. For most reliable-server type applications it makes more sense to just have more standard hardware in a load-balanced configuration that allows you to bring one box down for a time, make changes, etc, without the clients losing access. Of course, for fully interactive sessions built on older protocols like telnet, this doesn't work so well and hot-swapping is more desirable.
Re:Do you need special MOBO to hot swap memory/cpu (Score:1)
Starcat (Score:5, Insightful)
I'm not trolling, I mean it. What does Linux offer me that Solaris doesn't?
And please avoid the philosophical ramifications -- I have nothing against commercial software, except that 99% of it sucks.
--NBVB
Re:Starcat (Score:3, Insightful)
Mony is Money (Score:2)
-- kai
Re:Starcat (Score:2)
I'm not entirely sure that's always true. I can't find the URL right now, but I vividly remember some time ago reading that SGI had gotten the Linux kernel compiled for MIPS running, supposedly really well, on a 32-processor Origin 2000 system. I've tried google, groups.google.com, and archive.org with no luck. Maybe somebody can post a link so I don't look like a complete moron....
Re:Starcat (Score:2)
Surely if you buy a Sun, you get Solaris too?
Re:Starcat (Score:1)
In my experience, Linux is much more capable when it somes to minimalist or embedded tasks. With a machine that could swap NICs and memory on the fly, you could have a high-reliability router/smart switch without paying Cisco an arm and a leg.
Re:Starcat (Score:4, Insightful)
"What does Solaris offer me that Linux doesn't"
Re:Starcat (Score:1, Informative)
Re:Starcat (Score:2)
Given that Solaris comes bundled with Sun hardware, the original question makes more sense. Dumping Solaris and installing Linux requires a conscious decision, time and effort, so you'd better be looking for a good reason to prefer Linux over Solaris before you do it.
Re:Starcat (Score:2)
the sourcecode to the OS.
This is the ONE thing that is vitally important in an Open Source OS. It blows away everyone else because I have the sourcecode.
If you dont need to ever modify your system outside what they want you to have? then no you dont need it at all.
Re:Starcat (Score:5, Insightful)
Re:Starcat (Score:3, Interesting)
IBM is now marketing Linux as a big-iron OS and is actively selling S/390 mainframes with Linux. I believe that Linux now has a good chance of becoming the standard OS for big-iron systems - IBM and SGI first, then Compaq and HP, and finally Sun. Sun have switched Unixes before. I worked at Sun during the transition from SunOS 4 (BSD) to Solaris (SVR4). If they can do it once, they can do it again. Solaris is also gradually becoming more Linux-like, with a Linux compatability layer and Gnome. This could ease an eventual transition from Solaris to Linux. I'm not saying that this will happen, just that it's becoming increasingly likely.
HH
Re:Starcat (Score:5, Insightful)
The primary thing that Linux offers is the ability to run on non-Sun hardware. That's actually bigger than you might think. Consider the following ways that it might be nice:
Basically, the fact that big iron manufacturers already have their own OSes is not a strong argument about adding big-iron features to Linux. That's especially true if I'm a manufacturer and I want to break into that very lucrative market. It may very well be cheaper for me to help to develop the needed features in Linux and put that on my new hardware than to develop my own OS. By making those things available in a comodity OS you have the potential to convert big iron into a comodity market, just as comodity OSes for desktop systems helped turn them into comodity goods.
Solaris and Hardware (Score:3, Informative)
Now look at the architectures that Linux runs on:
PowerPC
Alpha
x86
IA64
Clawhammer
Power4
etc.
This means that you have much more choice about what you run the Linux machine on.
Also, I think the parent's point about ease of transition being the point of using Linux was missed by you. I would not run my business off Solaris on x86 anymore than I would use Mac OS9 on my web server... Although it is different on the SPARC, Linux and BSD are still the choice *Nix on x86 hardware. If you are running servers on x86, then you may want to move to Linux servers on big iron because the transition would be easier.
Re:Starcat (Score:1)
free as well as for real hardware?
Re:Starcat (Score:2)
But being available for x86 isn't the whole game. That might give you the ability to move easily from x86 to Sparc, provided that you had been running Solaris x86 to start out with. But hardly anyone is going to be starting with Solaris on x86 with the intention of making it easy to move to Sun's big iron when the need comes, especially because reviews of Solaris for x86 seem to be generally negative compared to Linux and *BSD.
And even if you had started on Solaris for x86, that still doesn't solve the issue of migrating from one big iron vendor to another. What happens if it turns out that you really want to be running on one of IBM's POWER-based systems, or a S390? Then you'll have a vendor to vendor migration problem. The advantage of Linux is that it's comparatively vendor agnostic. Once the kernel works on a given processor, it's likely to keep working there, and its range currently seems to be better than any of the proprietary Unixes. The big reason to use those proprietary Unixes is that they support "big iron" features; if and when Linux does the same there will be no reason not to use it instead.
Interesting. (Score:4, Interesting)
But I think your question was, given the Sparc platform.. why not use solaris?
At this point, you are right. Solaris is where it's at.. I mean, if you are buying Sun.. you obviously want more than just a fast machine... you want the support, etc.
But... as to why I prefer using linux to solaris, in general...
Linux is the new reference platform. new tools are developed on linux first, then ported to other unixes (the mahjority, anyway).
The number of tools quickly & easily available for linux vastly outnumbers the same for Solaris. Yes, you can get, compile, and run pretty much everything on solaris.. it's easy to port form linux to solaris.. but it's still easier to use linux.
Linux is open.. I just, well, I DO like that. Sure, I'm not gonna go out and modify a kernel.. but it means I'm not necessarily stuck with what Sun tells me I'm stuck with.
Would I buy a server farm of solaris boxes and run linux on it now? no.
Would I if Linux sparc supportw as as good as it's intel support? probably (once SPM is fixed)
Re:Starcat (Score:1)
It can't happen *that* often..
Re:Starcat (Score:2)
Companies that buy those things have dedicated sales weasels.......
Which, truthfully, is a cool thing. The dedicated-to-your-account part is important, 'cuz then the sales guy has *2* interests:
1) Getting his MONEY.
2) Making sure you spend MO' MONEY.
Unlike generic sales weasels, the dedicated sales weasel has only ONE account. So if he makes you unhappy, he stops getting money. Therefore, they tend to treat you really well, in hopes you spends lots more money.
So they do things like throw in ServerStarts for free and extra disk and things like that...
All the more reason to stick with Solaris.
Webservers? (Score:2, Interesting)
Increase the reliability of the internet? (Score:1)
It's called 'Revolving DNS' (Score:1)
At my university, our information servers get hammered on the day grades are released. EVERYBODY is checking out how they did throughout the term. What we do is set up a 'revolving dns', which basicly cycles through a small group of servers to prevent users from not being able to get through.
So what's this have to do with upgrading? We can upgrade machines without bringing down the whole webserver. Just unplug one, open it, swap in components, and add it back to the rack. Rinse and repeat, without losing web time.
-Senine
Re:It's called 'Revolving DNS' (Score:1)
The proper solution is a load balancer, which has a single IP at the internet end and distributes requests to multiple webservers (and knowing which ones are up and which are down).
Of course if your load balancer goes down..
Thought Turbo was on the Rocks ... (Score:1, Offtopic)
Mandrake and RedHat also sent us CD's, They were nice but also installed Gnome and KDE along with other huge apps that an average user wouldn't know what they were let alone ever use them.
Personally I would like to see Turbo up and going again, but I haven't heard anything positive coming out of it besides it's huge market-share in asia.
Drat. (Score:2, Interesting)
I want hot-swap PCI now. The memory swapping would be good in the case of a failed DIMM or two. The processor swapping...well, I'll just admit that wouldn't work too well in a uniprocessor computer.
Since I really doubt memory connectors are grounded properly to handle hot-swapping, that leaves PCI as the only one that's remotely feasible with today's computers. I know Solaris SPARC has it, what about x86?
Hot-swap PCI could be a really nifty feature on x86 machines. Especially for net guys like me who move NICs around all the time...
Re:Drat. (Score:2)
No PCI hot-swap? Huh??? (Score:1)
Re:Drat. (Score:2)
99% of all enterprise computing needs fall outside this. in even gigantic companies less than 3% of all their servers will lose the company huge sums of money for being down for a short amount of time.
Now research? that's a different story. Running a computation that takes 3 months to complete on a 500 processor 99Gigahertz each processor machine (or whatever the insane amounts of processing computers are up to now.) the shutdown to replace a nic card or ram module would have substantial effects.. and I doubt highly that more than 5 people that are here at slashdo ever do such advanced mathematics.
you dont need it, dont waste the time and money on it.
Re:Drat. (Score:1)
reliability they would more likely go for cheaper
faster hardware. They are the once who write code
for their computations, so they include
checkpoints, so that they can recover from any
crashes. They also prefer using many machines
instead of single machine if that will increase
their price/performance, as it also improves
reliability, if a processor goes down, the
computation slows down but does not stop.
You can see that research people are moving very
fast to Beowulf architectures. Only people who
cannot move are the ones who need some very fast
networking architectures.
Linux ``bad ram'' patch (Score:1)
Let's have a count down (Score:3, Funny)
Beowulf cluster
Re:Let's have a count down (Score:1, Funny)
Beowulf cluster
What the hell use is a timer when you already uttered those same words!?
Hmmmm..... (Score:3, Funny)
On KDE I just push the big button with the 2 on it...
An Atlas is Needed! (Score:2, Offtopic)
I can't wait to run Atlas on Linux!
That's what it's talking about, right?
(Shrug.)
--SC
Re:An Atlas is Needed! (Score:1)
Re:Does it.........work? (Safely) (Score:2, Insightful)
Notice all the computers that have hot-swap hard drive arrays. The exact same logic applies.
Oh, and about electrocution - unless you droll a lot or stuck yoru hand into th epower supply, you aren't getting electrocuted. The most voltage you'll ever see exposed to the computer as a whole is 12V. The high voltages are all relegated to the power supply.
Re:Does it.........work? (Safely) (Score:1)
Re:Does it.........work? (Safely) (Score:2)
I would assume that the CPU's and MB would be designed around this, much the way PCMCIA is.
I think it would work safely, but would require custom hardware and software.
focus of 2.5 series (Score:4, Insightful)
IBM kinda does this stuff already (Score:1, Interesting)
So far as IBM is concerned, they don't seem to be "competing against" Linux, they are running it on their servers right now. If you want some big iron running Linux, look at their zSeries machines. [ibm.com] They run hundreds of simultaneous Linux images through their Virtual Image Facility. [ibm.com] Of course, this has been discussed before here [slashdot.org] and probably some other places...
Other computer companies might have the same offerings, but IBM is the only one I am familiar with. Of course, we are also talking some serious cash for these IBM machines, whereas the Atlas project seems to be geared at more mid-range stuff that a smaller company could afford. So, I know it's a little like comparing apples to oranges, but I thought it might be of interest...
Increased system reliability in Linux 2.5 (Score:4, Funny)
Just like the similar complete rewrites in Linux 2.0, 2.2, and 2.4, Linux once again finally be a winning combination on the very high end!
Re:Increased system reliability in Linux 2.5 (Score:1)
What's wrong with the one we have?
What features would a new VM have that would make it better for these high-end systems?
Why do these high-end systems with skads and kaboodles of RAM need VM?
Just curious.
BSD? (Score:1)
Don't get me wrong, I run Linux on my home servers, but I would run it on kit that had the operational requirements that go with those hefty price tags.
Re:BSD? (Score:1)
And for what is talked about here ther is a linux fs for, its called XFS.
Stability is something else, its sayed that (Open|Free|Net)BSD or Solaris are more stable than linux, i cant say anything about that.
An intresting thing is SGI, theyre quite intrested in Linux for their HUGE boxen, maybe they will realease a special certified kernel wich is stable on this machinene type.
Maybe its really easier to build a kernel for a machine you built yourself and wich exists only in a few varieties like SGI or SUN can do (Solaris for x86 doesnt support a lot of hardware, so the BeOS policy - we support only good hardware)
Someone had to say it... (Score:1)
grammar nazi bait (Score:1)
What we need (Score:5, Insightful)
Most companies that currently employ Linux tend to use it for things like DNS, Web servers, and file sharing. Fitting Linux with enterprise features is critical in moving beyond these types of services and truly entering the enterprise world of hot plugging, scalability, and *proven* reliability.
While I realize that its reliability is more than proven to most of us here, it's important that it be proven to executives as well. Not only must it be reliable, but proven companies must have track records of standing behind the product 100%.
One concern I've heard voiced is that no company providing support for Linux will take ultimate responsiblity for a product that isn't theirs.
Get a few more years and services behind Linux, and we should see it explode.
Re:What we need (Score:3, Insightful)
NO company will take ultimate responsibility for products that are theirs.
Microsoft, SCO,SUN SiliconGraphics. everyone has in the license that they are not responsible for anything for any reason.
this concern needs to be met with a direct response that no company will, even for their own product.
Re:What we need (Score:1)
It's important to remember that much of Linux's competition comes not from the dreaded MS, but from commercial UNIX vendors, like Sun and IBM.
Unfortunatly, this is true the other way around: Linux isn't replacing Windows anywhere, but other Unices like Solaris or AIX. If it only were as good an OS...
Re:What we need (Score:3, Informative)
No, its not proven, at all!
Because you ran your Linux boxen at home and work without powering down for a year doesn't prove anything. You haven't gotten your machines even close to the level of load that enterprise server machines handle each day. Also, most of us run uniprocessor or 2-CPU machines. Not too much stuff is being done on the 32-CPU enterprise machines with Gigs and Gigs of RAM, hundreds of disks, network connections, and PCI buses.
Linux has not been proven in these environments at all. And even if you say that it runs on those machines, when you install an OS on a $1 million machine, you better damn be sure its proven to be reliable.
Now, big Uni*es -- Sun, IBM, HP, etc. have entire teams of people running stress tests on these machines, and (as a former developer of HP-UX) I know that developers must run through at least 12 hours of stress testing a system (thats a system running through automated test suites that excercise every subsystem, and get system load averages to about 200 consistently) when making kernel changes. These things are TESTED
Noone does that with linux, because noone wants to do it -- its not fun work at all. But the companys do do it, and must do it, since they must guarantee 99.99% uptime for the "executives" to buy the system.
So don't blame them for not jumping on Linux.
IBM supports Linux (Score:1)
Re:What we need (Score:1)
maybe first.. (Score:1)
Other idea (Score:4, Interesting)
Actually, I'd like to be able to run one Linux on N boxes, or M Linuxes on N boxes where M!=N. Just immagine a cluster of 50 machines where the failure of one machine has no effect on the operation of the cluster as a whole. There are some good projects in this area, but I don't think they can quite offer this kind of transparency.
Amazing! (Score:1)
Great geek party trick.
Re:Amazing! (Score:1)
As long as the board maintains the RAM contents, and can vector a newly inserted CPU to an area of memory capable of setting up the CPU where it was previously, this shouldn't be too impossible.
After all, its not that far removed from 'hibernation' mode that most laptops offer (under windows), with the difference that you're not powering up the whole machine back to a previous state, just the CPU.
Is it a useful feature on a single CPU machine? Maybe, Maybe not. It would reduce downtime for a server running on a 1 CPU box, but most serious servers where that matters aren't running 1 CPU.
The only complication would be that most legitimate reasons to allow hot-swapping a CPU on a single-CPU board are based around failure conditions, where you probably can't assume that the contents of RAM are 'sane'.
partitioning (Score:2, Interesting)
Partitioning, especially the dynamic variety, lets you take maximum advantage of a large multiprocessor machine. Can you say, 'OS upgrade without downtime'? From testing to gradual rollout, to full deployment, and if needed roll back, all without having to bring the machine down. Really cool!
I realize that atlas only envisages static partitioning for now. But can dynamic partitioning be far behind?
Oh the joy... (Score:1)
Virtual machines (Score:2)
VMWARE [vmware.com] has been doing this for years, on Intel architeture. Plus, you can run multiple operating systems, not only Linux. It creates a virtual machine, so it runs in protected mode, has a completely independent BIOS, uses the memory you assign... Works like a breeze.
I frequently run Win 2000 AND Debian Linux AND Win 98 (this one for some testing purposes), at the very same time. So you can have the best of all worlds.
Re:Virtual machines (Score:2, Informative)
And true virtualisation, mainframe-style, needs not just CPU support, but support from lots more of the hardware in the computer system.
So, VMWare is part virtualiser, part emulator.
The open source VMWare clone, plex86, similarly, has a lot in common with the bochs x86 emulator.
It's all very clever, but the PeeCee architecture is simply vile, and definitely an example of the "Eat shit, 10 billion flies can't be wrong" effect - even way, way back, there were better designed hardware architectures than the PC available for similar prices - the dominance of the PC arose partly because it was easy to semi-legally produce IBMPC-compatible clones, and partly through non-technological forces (i.e. lying salesmen and marketers combined with completely computer-clueless businessmen who believed them).
Looks more like Intel toe to toe with 'big iron' (Score:5, Informative)
This isn't a linux issue. It's a hardware issue.
The significant thing about 'big iron' is that it's an enabling hardware technology.
Once you have it you can write firmware and software that creates the illusion that the hardware never fails
Until you have it, you can't.
The hardware described looks about right - if they handled machine checks properly. (And the fact that they even used the term implies they either did or are trying.) Basic idea: The machine catches ANY error, with enough state saved that you can:
CORRECT the error
IDENTIFY any failed components,
MOVE tasks to non-failed components or reconfigure the failing components to limp along,
NOTIFY the OS of any problem, so it can do things like start moving things off a dying component, and
pick up the computation where it left off WITHOUT the error.
When you can do this you can write a modified Linux, Windows, BeOS, or what-have-you that can do the things a mainframe can. (But you'll need to have a REALLY reliable OS for your starting point - you're now talking uptimes measured in decades. The software better not take the system down in the absense of hardware trouble, and there IS NO hardware troube. B-) )
Hot-swappable parts are more a side-effect than something key. You have to be able to hot-swap to replace a broken part with the system live. Once you have the ability to hot-swap in a replacement for a failed part and add it back into a running domain, it's trivial to generalize that to "fix" parts that were "bad" because they had never been installed.
Partitioning is also implied: You need a minimum of two domains ("virtual machine" subsets of the total device) - working (where the live system is) and diagnostic (where the maintainence guys check out the parts). Once you have that mechanism, making a LARGE number of working domains (with varying amounts of resource, including full or time-shared CPUs) is straightforward.
Multiple Linuxes on IBM zSeries (Score:1)
Great! Another feature to brag about (Score:1)
"Now I just have to pop in this new memory stick, and I'm done, Oh @$%#!@! I must have shorted something out when I accidentally dragged this contact against something on the motherboard.
Irony? (Score:2)
My office is now 100% Window-less as of about 6 months ago, but we're instead 100% Mac OS X (currently 10.1).
You don't find it just a little hypocritical to demean MS Windows in one breath and praise your Mac because it runs MS office?
Re:Irony? (No Irony here... move along) (Score:2)
Some people dislike Microsoft, true, but others (like myself) just hate Windows, and think it's been on a track to just get worse. I also think Word peaked with Office 97... but if I could buy a copy of Word 97 for Linux, I'd get it. Since that's unlikely, I'm hoping that KWord will replace it as my favorite Word Processor/ Light DTP tool.
Some people dislike MS Windows, but don't have a problem with Microsoft. As a full groupware tool, Outlook + Exchange was a nice internal solution... not perfect, but arguably the best out there (and no, I won't argue it). As a platform for applications (which is what an OS really is), Windows sucks, blows and gargles (and again, no, I won't argue it).
--
Evan