[Pvfs2-developers] Review: Unify PVFS2 configuration files

Murali Vilayannur murali.vilayannur at gmail.com
Sun Feb 25 00:36:21 EST 2007


Hi all,
Attached patch against HEAD removes the need for maintaining/having 2
separate config files and consolidate all server specific information
into a single fs.conf file.
Hopefully, this will be a step closer to a zeroconf style deployment for pvfs.

Basically, I have added a new context <ServerOptions> in which we can
specify any server specific options using the "Option" keyword/tag.

Example:
Suppose we want to say that Server S needs to use storage space /opt/pvfs2 then
the config file looks like
<ServerOptions>
Option S StorageSpace /opt/pvfs2
</ServerOptions>
i.e. Option is followed with the alias which is followed by a keyword
which can be any of the accepted keywords in the <Defaults> section
which is then followed by the value to override for this server.

I have also modified pvfs2-genconfig to emit the new look config file
so that people can take a look at the config file and see if it looks
ok :)
If people feel strongly, I guess we could change it to something more
aesthetically
pleasing. :)

NOTE: This still requires that the server be passed in a command line
parameter which is the alias for that particular server. I just can't
think of any way around that.
However, this patch should still be a win since we go from reading 1 +
n config files to just 1 file when we start the servers...

Comments welcome,
thanks,
Murali
-------------- next part --------------
A non-text attachment was scrubbed...
Name: unify-config-files.patch
Type: text/x-patch
Size: 65481 bytes
Desc: not available
Url : http://www.beowulf-underground.org/pipermail/pvfs2-developers/attachments/20070224/49049e55/unify-config-files-0001.bin


More information about the Pvfs2-developers mailing list