mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
10215a6375
commit
ff21d04224
|
|
@ -156,7 +156,15 @@ which will have the same effect but you will now also be able to see the
|
|||
packages yourself.
|
||||
|
||||
</para>
|
||||
|
||||
<para>On some Layer 3 switches you other configs might be required.
|
||||
An openMosix user
|
||||
found out that on his Switch Summit48Si (Extreme Networks) he had to run
|
||||
<programlisting>
|
||||
disable ipmcforwarding (to deactivate the routing of multicast paquets)
|
||||
disable igmp snooping
|
||||
</programlisting>
|
||||
before he was the different omdiscd's were able to see eachother, other switches might require similar configs.
|
||||
</para>
|
||||
|
||||
|
||||
<para>
|
||||
|
|
|
|||
|
|
@ -11,10 +11,11 @@
|
|||
<!entity Hints system "openMosix_Hints.sgml">
|
||||
<!entity Administration system "openMosix_Admin.sgml">
|
||||
<!entity ClumpOS system "ClumpOS.sgml">
|
||||
<!entity PlumpOS-HOWTO system "PlumpOS-HOWTO-sgml/PlumpOS.sgml">
|
||||
<!entity PlumpOS-FAQ system "PlumpOS-HOWTO-sgml/PlumpOS-FAQ.sgml">
|
||||
<!entity PlumpOS-HOWTO system "../PlumpOS-HOWTO-sgml/PlumpOS.sgml">
|
||||
<!entity PlumpOS-FAQ system "../PlumpOS-HOWTO-sgml/PlumpOS-FAQ.sgml">
|
||||
<!entity LastChapter system "openMosix_Last_Chapter.sgml">
|
||||
<!entity Distributions system "openMosix_And_Distributions.sgml">
|
||||
<!entity RPM system "openMosix-RPM-Build.sgml">
|
||||
<!entity Credits system "openMosix_Credits.sgml">
|
||||
<!entity GnuDOC system "fdl.sgml">
|
||||
<!entity openMosixview system "openMosixview.sgml">
|
||||
|
|
@ -27,7 +28,7 @@
|
|||
<!entity Testing system "openMosix_Testing.sgml">
|
||||
<!entity Statistics system "openMosix_Statistics.sgml">
|
||||
<!entity Internals system "openMosix_Internals.sgml">
|
||||
<!entity FAQ system "../openMosix-FAQ/openMosix-FAQ-Text.sgml">
|
||||
<!entity FAQ system "../openmosixfaq/openMosix-FAQ-Text.sgml">
|
||||
]>
|
||||
|
||||
<BOOK ID="openMosix-HOWTO">
|
||||
|
|
@ -43,7 +44,7 @@ The best way to become acquainted with a subject is to write a book about it.</q
|
|||
</abstract><AUTHORGROUP>
|
||||
<AUTHOR><FIRSTNAME>Kris</FIRSTNAME>
|
||||
<SURNAME>Buytaert</SURNAME>
|
||||
<AFFILIATION><ADDRESS><EMAIL>buytaert@stone-it.be</EMAIL>
|
||||
<AFFILIATION><ADDRESS><EMAIL>buytaert@x-tend.be</EMAIL>
|
||||
</ADDRESS></AFFILIATION></AUTHOR>
|
||||
<AUTHOR><FIRSTNAME>and</FIRSTNAME>
|
||||
<SURNAME>Others</SURNAME>
|
||||
|
|
@ -53,6 +54,27 @@ The best way to become acquainted with a subject is to write a book about it.</q
|
|||
|
||||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>v1.0.3</revnumber>
|
||||
<date>18 june 2004</date>
|
||||
<revremark>Minor Fixes</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>v1.0.2</revnumber>
|
||||
<date>29 july 2003</date>
|
||||
<revremark>RPM Build</revremark>
|
||||
</revision>
|
||||
<revision>
|
||||
<revnumber>v1.0.1</revnumber>
|
||||
<date>19 july 2003</date>
|
||||
<revremark>Major updates</revremark>
|
||||
</revision>
|
||||
|
||||
<revision>
|
||||
<revnumber>v1.0</revnumber>
|
||||
<date>09 july 2003</date>
|
||||
<revremark>Minor updates</revremark>
|
||||
</revision>
|
||||
|
||||
<revision>
|
||||
<revnumber>v1.0</revnumber>
|
||||
|
|
@ -199,7 +221,9 @@ The best way to become acquainted with a subject is to write a book about it.</q
|
|||
<part><title>FAQ</title>
|
||||
&FAQ
|
||||
&PlumpOS-FAQ
|
||||
|
||||
</part>
|
||||
&RPM
|
||||
&LastChapter
|
||||
|
||||
<!--&ListOfWorking -->
|
||||
|
|
|
|||
|
|
@ -13,7 +13,52 @@ be discussed in one of the next chapters.
|
|||
</PARA>
|
||||
|
||||
</SECT1>
|
||||
<SECT1><TITLE>Getting openMosix</TITLE>
|
||||
<SECT1><TITLE>Before getting openMosix</TITLE>
|
||||
|
||||
<PARA> First of all, you must understand that openMosix is made up of
|
||||
a kernel patch and some user-space tools. The kernel patch is needed
|
||||
to make the kernel capable of talking to other openMosix-enabled
|
||||
machines on the network. If you download openMosix as a binary package
|
||||
(such as an rpm file), you don't even need to take care about the
|
||||
kernel patch because the kernel has been patched and compiled with the
|
||||
most common default options and modules for you. </PARA>
|
||||
|
||||
<PARA> The user-space tools are needed in order to make an effective
|
||||
use of an openMosix-enabled kernel. They are needed to start/stop the
|
||||
migration daemon, the openMosix File System, to migrate jobs to
|
||||
certain nodes and other tasks which are usually
|
||||
accomplished with the help our good old friend: the command line
|
||||
interface. About binary packages: the same as in the kernel patch goes
|
||||
for the user-space tools: if you install an rpm you don't need to
|
||||
care about compiling them or configuring anything; just let them install
|
||||
and run. That's all. Really :) </PARA>
|
||||
|
||||
<PARA> Once you get to the download page (which we'll talk about in a
|
||||
second), you'll need to get two distinct parts: the kernel and the
|
||||
user-space tools. You can either download two binary packages or get
|
||||
the kernel patch plus the user-space tools' sources. The kernel patch
|
||||
is usually named after this scheme: openMosix-x.y.z-w where x.y.z is
|
||||
the version of the vanilla Linux Kernel against which the patch should
|
||||
be applied and w is the patch revision for that particular kernel
|
||||
release. For the precompiled kernel binaries, please refer to the
|
||||
README-openMosix-kernel.txt file you'll find in the download
|
||||
page. This file also contains updated info about manually compiling a
|
||||
kernel. </PARA>
|
||||
|
||||
<PARA> About the user-space tools: you'll find those in a package
|
||||
named openmosix-tools. We use the terms user-space tools,
|
||||
userspace-tools and openmosix-tools interchangeably.
|
||||
Updated info about precompiled binaries and
|
||||
manually compiling the tools are also provided in the
|
||||
README-openmosix-tools.txt file. Please note that since version 0.3 of
|
||||
the openmosix-tools, the openmosix.map file is deprecated and the use
|
||||
of the autodiscovery daemon is highly encouraged since it tends to
|
||||
make your life easier. </PARA>
|
||||
|
||||
</SECT1>
|
||||
|
||||
<SECT1><TITLE>Getting openMosix</TITLE>
|
||||
|
||||
<PARA>
|
||||
You can download the latest versions of openMosix from <ulink
|
||||
url="http://sourceforge.net/project/showfiles.php?group_id=46729">
|
||||
|
|
@ -459,7 +504,8 @@ grub.conf. So all you have to do is install 2 RPMs:
|
|||
rpm -Uvh openmosix-kernel-2.4.20-openmosix2.i686.rpm openmosix-tools-0.2.4-1.i386.rpm
|
||||
</programlisting>
|
||||
|
||||
and edit your /etc/openmosix.map.
|
||||
and edit your /etc/openmosix.map if you don't wish to use the
|
||||
autodiscovery daemon (omdiscd).
|
||||
|
||||
Since this seems to be a problem for lots of people, let's go with
|
||||
another example. Say you have 3 machines: 192.168.10.220,
|
||||
|
|
@ -532,6 +578,8 @@ Total configured: 3
|
|||
opt for the src rpm and run rpmbuild --rebuild on it.
|
||||
This will install the source for you and create an initial config file.
|
||||
From there you can go further applying patches to openMosix
|
||||
</para>
|
||||
<para>A tutorial on how to build your own openMosix RPM's can be found in the Appendixes.
|
||||
|
||||
|
||||
</para>
|
||||
|
|
|
|||
|
|
@ -143,9 +143,9 @@ group with different configurations)
|
|||
</PROGRAMLISTING>
|
||||
|
||||
Note that neither of the machines ask for a password.
|
||||
This is because we have set up rsa authentication between the different
|
||||
This is because we have set up RSA authentication between the different
|
||||
accounts. If you want to run commands with multiple parameters you will
|
||||
have either have to put the command between quotes.
|
||||
either have to put the command between quotes.
|
||||
|
||||
<PROGRAMLISTING>
|
||||
[root@inspon root]# dsh -r ssh -g mosix "uname -a"
|
||||
|
|
|
|||
|
|
@ -49,6 +49,10 @@ the HOWTO
|
|||
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2><title>Russian</title>
|
||||
<para>Dmitry Katusubo translated the openmosix website and together with Yuri Prushinsky he also translated the openMosix HOWTO
|
||||
<ulink url="http://www.openmosix.org.ru/docs/openMosix-HOWTO-multi/"><citetitle>http://www.openmosix.org.ru/docs/openMosix-HOWTO-multi/ </citetitle></ulink></para>
|
||||
</sect2>
|
||||
</SECT1>
|
||||
|
||||
<SECT1><TITLE>Links</TITLE>
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ these machines is capable of doing so.
|
|||
</para>
|
||||
|
||||
<para> I'm talking about preparing one or more 19" racks to host the
|
||||
machines, configure the appropriate network topology, either straight,
|
||||
machines, configuring the appropriate network topology, either straight,
|
||||
single connected or even a 1 to 1 cross connected network between all
|
||||
your nodes. You will also need to make sure that there is enough
|
||||
power to support such a range of machines, that your air-conditioning
|
||||
|
|
@ -62,7 +62,7 @@ down your cluster, you are in trouble.
|
|||
<TITLE>Software requirements</TITLE>
|
||||
|
||||
<PARA> The systems we plan to use will need a basic Linux installation
|
||||
of your choice: Red Hat, Suse, Debian, Gentoo or any another
|
||||
of your choice: Red Hat, SuSe, Debian, Gentoo or any another
|
||||
distribution: it doesn't really matter which one.
|
||||
|
||||
What does matter is that the kernel is at least on 2.4 level, and that
|
||||
|
|
@ -95,7 +95,7 @@ This of course makes your workstation a part of the pool.
|
|||
<para>
|
||||
In an environment that is called a <emphasis>Server-pool</emphasis>,
|
||||
servers are a part of the cluster while workstations aren't part of
|
||||
it, they don't even haven openMosix kernel. If you want to run
|
||||
it, they don't even have openMosix kernel. If you want to run
|
||||
applications on the cluster you will need to
|
||||
specifically log on to these servers. However your workstation will also
|
||||
stay
|
||||
|
|
@ -127,8 +127,8 @@ by using mosctl.
|
|||
openMosix cluster at night, you'll have to consider training your end
|
||||
users not to pull the power switch of those machines when they want to use
|
||||
them again. More recent machines support automatic shutdowns when hitting
|
||||
the power button, but with older machines you might loose some data now
|
||||
and then when this actually happens.</PARA> </SECT1>
|
||||
the power button, but with older machines you might loose some data
|
||||
when this actually happens.</PARA> </SECT1>
|
||||
|
||||
</CHAPTER>
|
||||
|
||||
|
|
|
|||
|
|
@ -148,20 +148,21 @@ Contributed by Evan Hisey
|
|||
<PARA>
|
||||
Channel bonding is actually horrible easy. This may explain the lack of
|
||||
documentation on this subject A bonded network appears as a normal
|
||||
network to the applications. All machines on a subnet must be either bonded the same way. Bonded and non-bonded machine really don't talk well
|
||||
network to the applications. All machines on a subnet must be bonded the same way. Bonded and non-bonded machine really don't talk well
|
||||
to each other.
|
||||
</PaRA>
|
||||
<PARA>
|
||||
|
||||
Channel bonding needs at least to physical sub-nets but can have
|
||||
Channel bonding needs at least two physical sub-nets but can have
|
||||
more(Currently I have a tri-bonded cluster). To enable bonding you need to
|
||||
either compile in to the kernel or as a module (bonding.o) the Channel Bonding kernel code, as of 2.4.x is it a standard option of the kernel.
|
||||
The NIC's are setup as normal with except that you only us 'ifconfig' to initialize the first card of the bond. 'ifenslave' is used to initialize
|
||||
the remaining cards in the bonded connection. 'ifenslave' can be locate in the linux/Documentation/network/ directory. It will need to be
|
||||
compiled as it is a .c file. The basic format for use is
|
||||
<programlisting><![CDATA[
|
||||
ifenslave <master> <slave1> <slave2>
|
||||
]]></programlisting> ...'. Channel bonded networks can connect to
|
||||
ifenslave <master> <slave1> <slave2> ...
|
||||
]]></programlisting>
|
||||
Channel bonded networks can connect to
|
||||
standard networks via a router or bridge that supports channel bonding( I just use an extra NIC and port-forwarding in the head node).
|
||||
</PARA>
|
||||
</SECT1>
|
||||
|
|
|
|||
|
|
@ -264,7 +264,7 @@ project. Because there is a significant user base out there (about
|
|||
1000 installations world-wide), Moshe Bar has decided to continue the
|
||||
development and support of the Mosix project under a new name:
|
||||
openMosix and under the full GPL2 license. Whatever code in openMosix
|
||||
comes from the old Mosix project is Copyright 2002 by Amnon Bark. All
|
||||
comes from the old Mosix project is Copyright 2002 by Amnon Barak. All
|
||||
the new code is Copyright 2002 by Moshe Bar.
|
||||
</PARA>
|
||||
|
||||
|
|
@ -472,12 +472,8 @@ and also provides higher computing power to openMosix users who are
|
|||
developing or porting their applications.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To get your userid and password to the cluster:
|
||||
<ulink
|
||||
url="http://www.mosixcluster.com/trial.php">
|
||||
<citetitle>http://www.mosixcluster.com/trial.php</citetitle>
|
||||
</ulink>
|
||||
<para>Please send an email to <email>om@majorlinux.com</email> for a trial account.
|
||||
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ rewrote all parts/functions/methods to a cleaner c++ interface
|
|||
</><member>
|
||||
replaced MosixMem+Load with the openMosixanalyzer
|
||||
</><member>
|
||||
.. many more changes
|
||||
... many more changes
|
||||
</></simplelist>
|
||||
|
||||
</sect1>
|
||||
|
|
@ -107,7 +107,7 @@ replaced MosixMem+Load with the openMosixanalyzer
|
|||
Requirements
|
||||
|
||||
<simplelist>
|
||||
<member>QT</>
|
||||
<member>QT library</>
|
||||
<member>
|
||||
root rights ! </>
|
||||
<member>rlogin and rsh (or ssh) to all cluster-nodes without password
|
||||
|
|
|
|||
Loading…
Reference in New Issue