> > Are separate spec files a _must_? Now and in the future? I'd prefer to > manage a single file (even if there are non-fatal errors) than many. Of > course, the examples allow for a brick and brick-ns in the specification, > which makes them simple. > > Might there be any interest in supporting an option which allows for a > single server volume spec file to be used but to not cause errors? E.g., > if you want to do that, you can use the server spec file you sent in the first mail , on all the servers. It will create those directories, but the volume is not used at all (if not linked by the client protocol). Its possible with current code base itself. Regards, -- Amar Tumballi Gluster/GlusterFS Hacker [bulde on #gluster/irc.gnu.org] http://www.zresearch.com - Commoditizing Super Storage!
