[Pvfs2-cvs] commit by slang in pvfs2/doc: pvfs2-faq.tex
pvfs2-guide.tex pvfs2-ha-heartbeat-v2.tex pvfs2-quickstart.tex
CVS commit program
cvs at parl.clemson.edu
Mon Nov 19 16:33:42 EST 2007
Update of /projects/cvsroot/pvfs2/doc
In directory parlweb1:/tmp/cvs-serv31101/doc
Modified Files:
Tag: pvfs-2-7-branch
pvfs2-faq.tex pvfs2-guide.tex pvfs2-ha-heartbeat-v2.tex
pvfs2-quickstart.tex
Log Message:
doc changes, changes to script that fixes the latex2html gen-ed docs.
Index: pvfs2-faq.tex
===================================================================
RCS file: /projects/cvsroot/pvfs2/doc/pvfs2-faq.tex,v
diff -p -u -r1.56 -r1.56.4.1
--- pvfs2-faq.tex 28 Jun 2007 03:56:54 -0000 1.56
+++ pvfs2-faq.tex 19 Nov 2007 21:33:42 -0000 1.56.4.1
@@ -17,7 +17,6 @@
\title{Frequently Asked Questions about PVFS}
-\author{ PVFS Development Team }
% \date{Last Updated: September 2004}
%
Index: pvfs2-guide.tex
===================================================================
RCS file: /projects/cvsroot/pvfs2/doc/pvfs2-guide.tex,v
diff -p -u -r1.5 -r1.5.12.1
--- pvfs2-guide.tex 23 Oct 2006 19:19:49 -0000 1.5
+++ pvfs2-guide.tex 19 Nov 2007 21:33:42 -0000 1.5.12.1
@@ -23,8 +23,6 @@
%
\title{Parallel Virtual File System, Version 2}
-\author{PVFS2 Development Team}
-\date{September, 2003}
\pagestyle{plain}
\begin{document}
Index: pvfs2-ha-heartbeat-v2.tex
===================================================================
RCS file: /projects/cvsroot/pvfs2/doc/pvfs2-ha-heartbeat-v2.tex,v
diff -p -u -r1.1 -r1.1.2.1
--- pvfs2-ha-heartbeat-v2.tex 7 Nov 2007 21:54:12 -0000 1.1
+++ pvfs2-ha-heartbeat-v2.tex 19 Nov 2007 21:33:42 -0000 1.1.2.1
@@ -17,7 +17,7 @@
\headheight 0.0in
\title{PVFS2 High-Availability Clustering using Heartbeat 2.0}
-\date{2007}
+\author{Phil Carns}
\pagestyle{plain}
\begin{document}
Index: pvfs2-quickstart.tex
===================================================================
RCS file: /projects/cvsroot/pvfs2/doc/pvfs2-quickstart.tex,v
diff -p -u -r1.41 -r1.41.4.1
--- pvfs2-quickstart.tex 1 Dec 2006 17:23:42 -0000 1.41
+++ pvfs2-quickstart.tex 19 Nov 2007 21:33:42 -0000 1.41.4.1
@@ -22,7 +22,6 @@
\title{A Quick Start Guide to PVFS2}
-\author{ PVFS2 Development Team }
%
% BEGINNING OF DOCUMENT
@@ -171,12 +170,10 @@ several questions to determine your desi
particular attention to the listing of the metadata servers and I/O
servers. In this example we will use ``testhost'' for both.
-The pvfs2-genconfig tool will generate two configuration files. One
-is a file system configuration file that will be identical for all
-servers (if we had more than one). The second is a server specific
-configuration file that will be different for each server. The server
-specific files have the hostname of the server that they belong to
-appended to the file name. This script should be excuted as root, so
+\em{NEW:} The pvfs2-genconfig tool will generate
+\em{a single} configuration file. Previous versions (before 2.7.0) of PVFS
+generated two files, but the format allows for easier deployment
+using a single file. This script should be excuted as root, so
that we can place the configuration files in their default /etc/
locations.
@@ -186,7 +183,7 @@ every field. We will use the hostname `
\begin{verbatim}
root at testhost:~# /usr/bin/pvfs2-genconfig \
- /etc/pvfs2-fs.conf /etc/pvfs2-server.conf
+ /etc/pvfs2-fs.conf
**********************************************************************
Welcome to the PVFS2 Configuration Generator:
@@ -249,16 +246,24 @@ a storage space in /pvfs2-storage-space
files.
\begin{verbatim}
-bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf \
- /etc/pvfs2-server.conf-testhost -f
+bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf -f
\end{verbatim}
Once the above step is done, you can start the server in normal mode
as follows:
\begin{verbatim}
-bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf \
- /etc/pvfs2-server.conf-testhost
+bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf
+\end{verbatim}
+
+The server uses the hostname of the machine to determine the endpoint
+for the config file that it should attach to. If the server is unable
+to match the hostname to one of the endpoints in the config file, the
+\em{-a} option can be given, using the alias string
+to specify the endpoint.
+
+\begin{verbatim}
+bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf -a myhost1
\end{verbatim}
All log messages will be directed to /tmp/pvfs2-server.log, unless you specified
@@ -267,8 +272,7 @@ pvfs2-server in the foreground and direc
you may run the server as follows:
\begin{verbatim}
-bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf \
- /etc/pvfs2-server.conf-testhost -d
+bash-2.05b# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf -d
\end{verbatim}
\subsubsection{Automatic server startup and shutdown}
@@ -529,24 +533,13 @@ Writing 8 server config file(s)... Done.
Configuration complete!
\end{verbatim}
-The generated config files will have conservative default values. The PVFS2
+The generated config file will have conservative default values. The PVFS2
Users Guide has more information about the settings and the consequences of
setting more aggressive, high performance values.
-We have now made all the config files for an 8-node storage cluster:
-\begin{verbatim}
-root at cluster1:~# ls /etc/pvfs2/foo/
-pvfs2-fs.conf pvfs2-server.conf-cluster5
-pvfs2-server.conf-cluster1 pvfs2-server.conf-cluster6
-pvfs2-server.conf-cluster2 pvfs2-server.conf-cluster7
-pvfs2-server.conf-cluster3 pvfs2-server.conf-cluster8
-pvfs2-server.conf-cluster4
-\end{verbatim}
-
-Now the config files must be copied out to all of the server nodes. If you
-use the provided (Redhat style) rc scripts, then you can simply copy all
-config files to every node; each server will pick the correct config files
-based on its own hostname at startup time. The following example assumes
+Now the config file must be copied out to all of the server nodes. If you
+use the provided (Redhat style) rc scripts, then you can simply copy
+the config file to every node. The following example assumes
that you will use scp to copy files to cluster nodes. Other possibilities
include rcp, bpcp, or simply storing the configuration files on an NFS volume.
Please note, however, that the rc script should be modified if you intend
@@ -557,7 +550,6 @@ each machine.
\begin{verbatim}
root at cluster1:~# for i in `seq 1 8`; do
-> scp /etc/pvfs2-server.conf-cluster\${i} cluster\${i}:/etc/
> scp /etc/pvfs2-fs.conf cluster\${i}:/etc/
> scp /usr/src/pvfs2/examples/pvfs2-server.rc \
cluster\${i}:/etc/rc.d/init.d/pvfs2-server
@@ -573,16 +565,14 @@ does not already exist. Run the followi
or IO node in the cluster:
\begin{verbatim}
-root at cluster1# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf \
- /etc/pvfs2-server.conf -f
+root at cluster1# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf -f
\end{verbatim}
Then once the storage space is created, start the server for real with a
command like this on every metadata or IO node in the cluster:
\begin{verbatim}
-root at cluster1# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf \
- /etc/pvfs2-server.conf
+root at cluster1# /usr/sbin/pvfs2-server /etc/pvfs2-fs.conf
\end{verbatim}
If you want to run the server in the foreground (e.g. for debugging), use the
More information about the Pvfs2-cvs
mailing list