Re: [SLE] SUSE = Ubuntu?

On Thursday 21 September 2006 15:54, Peter Van Lone wrote:
despite the power issues for a home user, I want to start playing in
this sand box, too ...

will you discuss a bit the hardware and software resources you have
marshalled in your HPC? What interconnect - just GB ethernet? What
linux distro and cluster packages?
I am not at the point where I can share the distribution source yet, but
you can bet when I've got things a little closer to a 0.9 package level I
will. (and it will be a gpl source package too, to be sure)
But the following are some things to play with that anyone can do without
any programming at all... ok, maybe some small setup, but minimal.
Picture three machines (all headless, no desktops--- not even virutal
ones) and one terminal, running kde--- my personal favorite desktop. I have
three things I really want to do today... 1) monitor my mail all day, 2)
recompile my experimental kernel as many times as an 8 hour day will allow,
and 3) work on my distributed network package--- mostly compilation, tweak,
and recompilation, repeating all day as necessary.... whew. Ok, ?
All I use the terminal for is KDE and X. That's it--- that's all.
The headless machines are assigned my three tasks...
1) kernel compiling
2) monitoring my mail all day
3) production development system all day
In this scenario all four machines appear to me as one machine with four
processors. All three major tasks appear to be running on my terminal...
however, actually each process is running on its own processor somewhere out
there on my network.
This works well in this scenario because most of the work is processor
intensive, and not network traffic intensive.
Each task is run on a remote machine, passing its X output back to the
terminal via compressed and secure stream over an SSH tunnel.
The machines are set-up with firewall rules locking everything down
except SSH with capability for X11 forwarding turned on. Consider the
following terminal command:

ssh -X -C -c blowfish -f myuser@remotehost "nohup xterm; sleep 2; exit"

What happens here? SSH starts a background process (-f) with X11
forwarding (-X) compressed (-C) using blowfish encryption (-c) to my first
remote system starting an x terminal (which will display through a virtual
X11 connection back at my terminal machine) with hup signaling turned off so
that when I logoff the initiating xterm the secure X11 channel will stay up.
When I'm done and logoff the remote system the "sleep 2; exit" will clean
things up nicely on the remote end. So how is this helpful?? This works
with any application.... even vncviewer, of kontact, or whatever development
environment you're using... emacs or whatever. The remote machines are used
to provide the power behind the compilations, mail management, development,
whatever, and the terminal I'm logged into is used for really nothing else
except a remote X server. This is the simplest and easiest form of
distributed processing that can be done with no programming... and its
powerful. Essentially the four machines are working together as one large
multiprocessor computer with one graphical user interface.
Note: I should point out that on slower networks like mine (normal
10/100) the -C compression flag is essential. However, on fast internal
networks it just slows things down... if you have a GB network all the more
power to you... things will really fly.
Note2: The -X flag is a client flag initiating X11 forwarding virtual
display info... you don't need to manually set the display... however, you do
need to turn on X11 forwarding on the ssh server at each remote node.





--
Kind regards,

M Harris <><

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: setting up a remote location (another netbios domain, maybe)...
    ... Jorge Silva wrote: ... > inside network neighborhood, ... IMHO 6 machines are few machines to justify a DC at remote location, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Suggestions for remote admin of linux machines
    ... ]pleased with the methods for remote administration that have come to ... So just do it, by command line and scripts, via the network. ... The only problem is that the machines may need on site if they crash ... ]Solution #3: KVM over IP. ...
    (comp.os.linux.networking)
  • Re: Suggestions for remote admin of linux machines
    ... ]pleased with the methods for remote administration that have come to ... So just do it, by command line and scripts, via the network. ... The only problem is that the machines may need on site if they crash ... ]Solution #3: KVM over IP. ...
    (comp.os.linux.misc)
  • Re: Remote Assistance User Acceptance exclusion
    ... way to Remote assistance. ... that doesn't really answer the question in a network infrastructure ... >> more practical for me to manage these machines remotely then to have to go ... >>> SBS Rocks! ...
    (microsoft.public.windows.server.sbs)
  • Re: vpn - can see all remote computers except 1
    ... Posting on MS newsgroup will benefit all readers and you may get more help. ... I can ping all machines on their network via IP address. ... I can find all machines from windows explorer> My Netwrok Places> Search ... I can ping this machine by IP, I can connect to it via remote desktop, I ...
    (microsoft.public.win2000.networking)
Loading