[Gluster-devel] Stateless Gluster 3.x series

[Ian Latter]

----- Original Message -----
>From: "Ian Latter" <ian.latter at midnightcode.org>
>To: "Vijay Bellur" <vijay at gluster.com>
>Subject:  Re: [Gluster-devel] Stateless Gluster 3.x series
>Date: Fri, 13 Apr 2012 23:04:59 +1000
>
> 
> 
> 
> 
> ----- Original Message -----
> >From: "Vijay Bellur" <vijay at gluster.com>
> >To: "Ian Latter" <ian.latter at midnightcode.org>
> >Subject:  Re: [Gluster-devel] Stateless Gluster 3.x series
> >Date: Fri, 13 Apr 2012 18:27:38 +0530
> >
> > 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
> > 
> 
> 
> Thanks Vijay,
> 
>   I thought we'd try this, but I will re-test in case we
> missed it.
> 
> Cheers,
> 

Thanks Vijay,

  Clearly my mistake, as this works.  

  I think I have confused this with my volume testing (we
were unable to find a minimal set of files to populate per 
volume in order to get it to start from static config info 
only), and I recall a uuid in there also.

  I have run out of time to do more integration testing; I
will come back with further queries when I get another 
chance.


Cheers,



--
Ian Latter
Late night coder ..
http://midnightcode.org/