On 4/6/06, Robert Latham <[EMAIL PROTECTED]> wrote:
I appologize for combining the two. There was a little confusion on this end that ended up melting those into the same patch. I will try to keep those separate in future cases.
The --ioports and --metaports options will take a list of ports an apply it to all of the hosts given (every port in --ioports will be mapped to every host in --ioservers). The --iospecs and --metaspecs that I provided allow specific ports to be given for each host. They also allow a user specified storage space for each host/port combination. It just allows us to be more specific about where servers will run and where their storage is located. The changes do not really fit with --ioports and --metaports since it does a broader mapping of ports to servers and does not facilitate using specific storage spaces.
As an example, suppose that you are using a SAN and you want one particular server to have a dedicated LUN for metadata. In that case you might want to specify something like this:
--iospecs host1:3335:/mnt/data-lun,host2:3335:/mnt/data-lun
--metaspces host1:3334:/mnt/meta-lun
Hi Bart. Thanks for the patches. A few comments
On Mon, Apr 03, 2006 at 10:53:28AM -0600, Bart Taylor wrote:
> RHEL4-compiler-warnings.patch:
>
> This is a few quick data type fixes so the source will also compile on
> 64 bit RHEL4 without warnings. These changes are on test programs.
The test/ programs do need more attention, it's true. We usually
solve them by using the llu() macro, which will cast everything in
such a way that both 32 and 64 bit compiles end up clean.
> pvfs2-ping.patch:
>
> Some white space fixes were applied using
> pvfs2-mangle-in-place-80col.sh.
We've not been too careful with our formatting, have we? However,
such whitespace changes make it hard to see the more substantial
changes. In the future, separate whitespace changes from all other
parts of your patch.
I appologize for combining the two. There was a little confusion on this end that ended up melting those into the same patch. I will try to keep those separate in future cases.
> It is also updated to continue after encountering some errors such
> as one of the services being unreachable or an unreachable entry
> being found in the tab file. This was mainly done by setting flag
> if a problem occurs instead of returning -1.
Defintely useful. Might not apply it directly, but something like
this is a good idea.
> pvfs2-genconfig.patch:
>
> Two options were added and the functionality to run multiple servers
> per node.
>
> The two options --iospecs --metaspecs take arguments of the form
> node:port:dir,node:port:dir,?. These are the node name, the port
> for the server to run on, and the storage directory for the server
> running on that port. This allows any number of IO or meta servers,
> each on a unique port and storage location, to run on a node. It
> creates the filesystem conf and server conf files appropriately and
> moves the log file location entry to the server conf file(s) so that
> each service will have its own log. The logfile name always has the
> port appended now even in the case with one server or run
> interactively. Allowing multiple servers per node is not supported
> in the interactive mode. It must be done using the new options.
> The ?h option reflects the changes.
Sam not that long ago added --ioports and --metaports options so that
servers would listen on differetn ports on the same machine and append
port number to the storage spaces and log files.
Your approach is definitely more flexible, but it seems like we've got
an approach that already does what you're trying to do. Are there
situations i'm missing where --ioports and --metaports won't do the
job?
The --ioports and --metaports options will take a list of ports an apply it to all of the hosts given (every port in --ioports will be mapped to every host in --ioservers). The --iospecs and --metaspecs that I provided allow specific ports to be given for each host. They also allow a user specified storage space for each host/port combination. It just allows us to be more specific about where servers will run and where their storage is located. The changes do not really fit with --ioports and --metaports since it does a broader mapping of ports to servers and does not facilitate using specific storage spaces.
As an example, suppose that you are using a SAN and you want one particular server to have a dedicated LUN for metadata. In that case you might want to specify something like this:
--iospecs host1:3335:/mnt/data-lun,host2:3335:/mnt/data-lun
--metaspces host1:3334:/mnt/meta-lun
Thanks for sending the patches
==rob
--
Rob Latham
Mathematics and Computer Science Division A215 0178 EA2D B059 8CDF
Argonne National Labs, IL USA B29D F333 664A 4280 315B
_______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
