Stas Oskin wrote: > My largest concert over GlusterFs is really the luck of central > administration tool. Modifying the configuration files on every > server/client with every topology change becomes a hurdle on 10 servers > already, and probably impossbile beyond 100. You can always use rsync or scp to "replicate" your config changes across lots of servers, especially if there are minimal changes. You can use a cron script to do this and detect when a gluster restart is needed. Localized edits can be automated with a sed script or similar on either end. Another idea might be to put a client gluster spec on an NFS export, but that leads to an single-point-of-failure issue if the NFS "goes away". -- -- ============================ Tom Lahti BIT Statement LLC http://www.bitstatement.net/ -- ============================
