os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Documentation of Netperf Cluster procedures is now on the wiki, as is

Browse source 
cluster reservation.  Drop in appropriate links and trim duplicated text.
This commit is contained in:
Robert Watson 2006-12-11 16:29:00 +00:00
parent cf968ca12f
commit c06c913708
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=29221
1 changed files with 11 additions and 55 deletions
Download patch file Download diff file Expand all files Collapse all files

66
en/projects/netperf/cluster.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../.."> <!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/projects/netperf/cluster.sgml,v 1.16 2006/12/11 12:54:07 rwatson Exp $"> <!ENTITY date "$FreeBSD: www/en/projects/netperf/cluster.sgml,v 1.17 2006/12/11 13:10:53 rwatson Exp $">
<!ENTITY title "FreeBSD Network Performance Project (netperf)"> <!ENTITY title "FreeBSD Network Performance Project (netperf)">
<!ENTITY email 'mux'> <!ENTITY email 'mux'>
<!ENTITY % navinclude.developers "INCLUDE"> <!ENTITY % navinclude.developers "INCLUDE">
@ -168,60 +168,9 @@
systems in the cluster, as well as to avoid treading on each others systems in the cluster, as well as to avoid treading on each others
toes.</p> toes.</p>
<ul> <p>Pointers and documentation on Netperf Cluster procedures can be found
<li><p><b>Reserving a system</b> is now done using a <a on the <a href="http://wikitest.freebsd.org/NetperfClusterPointers">
href="http://wikitest.FreeBSD.org/NetperfClusterReservations"> page Netperf Cluster Pointers</a> page on the FreeBSD wiki.
on the FreeBSD.org wiki</a>. Please make sure to mark machines as
available when done with them, and log your use in the "past users"
list for any significant project, as this information can be used
to help support additional hardware acquisition and requests for
donations.</p></li>
<li><p><b>Power cycling a system</b> is currently performed by
connecting to apc[234], the remote power systems, using either a
serial port on zoo or telnet from zoo. Please be careful to only
power cycle machines you have a reservation for, and disconnect
from power controller serial/telnet sessions after using them as
multiple simultaneous connections by different users are not
supported by the hardware.</p></li>
<li><p><b>Booting a specific configuration</b> is currently performed
by interrupting the boot of a system using the serial console, or
modifying the /zoo/hostname/boot/loader.conf file to point at a new
kernel. Please do not replace the kernel in the NFS boot tree for a
host; instead, install kernels in your /zoo/username tree, and
explicitly configure hosts to use that kernel. Please restore the
defaults for a system, including removing any non-standard entries
from loader.conf, when you are done with a test or
experiment.</p></li>
<li><p><b>Reconfiguring on-disk installs</b> should be done only in
coordination with the cluster admins. If you change configuration
settings for hosts during an experiment, please restore them. If
you install packages on the file systems of tests, please remove
them when done. A useful technique is to store required packages for
experiments in NFS, and to add the packages for the duration of a
development session. While data can be left on systems between test
runs, developers who are using data sets for common applications,
such as MySQL, may wish to store that data in a personal directory
as other testing on the host could interfere with it. Developers
are advised to check the configuration of systems before using them
to make sure all is as expected.</p></li>
<li><p><b>Reconfiguring system BIOSes</b> should be avoided if at all
possible. Please restore any settings as soon as a test or
experiment is complete. <b>Please do not turn off BIOS serial console
redirection, or modify any settings associated with console
redirection!</b></p></li>
<li><p><b>Check software configurations before testing</b> --
specifically, use uname to confirm that the right kernel is running,
that it's not configured for WITNESS or INVARIANTS if that's not
needed, and that /etc/malloc.conf is set to "aj" if no debugging is
desired. Use 'ps' and 'pkg_info' to make sure only the software you
expect is running, and that the version of the software you expect is
installed.</p></li>
</ul>
<a name="notes"></a> <a name="notes"></a>
<h2>Current Configuration Notes and News</h2> <h2>Current Configuration Notes and News</h2>
@ -230,6 +179,13 @@
to users of the netperf cluster:</p> to users of the netperf cluster:</p>
<ul> <ul>
<li><p><b>20061211</b> - The <a
href="http://wikitest.freebsd.org/NetperfClusterReservations">Netperf
Cluster Reservations page</a> is now online on the wiki. Also, a
<a href="http://wikitest.freebsd.org/NetperfClusterPointers">Netperf
Cluster Pointers</a> wiki page has been set up documenting procedures
for the Netperf cluster.</p></li>
<li><p><b>20061205</b> - <b>zoo.FreeBSD.org</b> has been updated to <li><p><b>20061205</b> - <b>zoo.FreeBSD.org</b> has been updated to
the most recent version of 6-STABLE.</p></li> the most recent version of 6-STABLE.</p></li>