On 04/13/2012 02:26 PM, Ian Latter wrote:
Hello,
Until yesterday all of my experiments with Gluster have
been with a vi'd vol file and the Glusterfsd process.
Michael and I have now done testing with glusterd under
Gluster version 3.2.6 and this has raised some issues.
The one I'd like to query in this thread is stateless
environments.
If I have a PXE distribution that boots, tftp's a config
file, mounts storage devices and then initialises gluster
then;
Previously - I wrote out the appropriate vol file and
started the necessary daemons.
Now - I start the necessary daemon and issue a set
of commands to build the appropriate configuration.
.. however, this results in a new gluster UUID each
time the node restarts.
So;
1) Is there a gluster command to configure gluster
with a specific UUID?
-or-
2) Is there a means to provide gluster with UUID
data outside of the gluster commands
You could populate glusterd.info in the working directory (/etc/glusterd
or /var/lib/glusterd) with the desired UUID and start glusterd. glusterd
uses this UUID as part of its initialization process. If the file (or
UUID) is not available, then it re-generates a new UUID.
--Vijay
