Brandon Lamb wrote:
Basically when glusterfs parses the spec file there would have to be a
way for it to know that a volume specification was for *itself* and if
not (ie it was defining a volume for another server) it would ignore
the volume.
Right. That's why I asked about an "option hosts".
On Thu, May 1, 2008 at 2:22 PM, John Marshall <[EMAIL PROTECTED]> wrote:
> Brandon Lamb wrote:
> >
> > On Thu, May 1, 2008 at 1:49 PM, John Marshall <[EMAIL PROTECTED]>
> wrote:
> >
> >
> >
> > > My question comes from wanting to export multiple, differently named,
> > > directories from different
>
> 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 a
Brandon Lamb wrote:
On Thu, May 1, 2008 at 1:49 PM, John Marshall <[EMAIL PROTECTED]> wrote:
My question comes from wanting to export multiple, differently named,
directories from different hosts (assume 1 dir/host). Must I create a
separate server volume spec for each host, or can I simply p
On Thu, May 1, 2008 at 1:49 PM, John Marshall <[EMAIL PROTECTED]> wrote:
>
> Brandon Lamb wrote:
> > Replies are inline, hopefully im right here ;-)
> >
> >
> >
> >
> >
> > > Note: it is assumed that host-a:/data/a, host-b:/data/b,
> > > host-ns:/data/ns exist.
> > >
> > > Q. Does gluster have
Brandon Lamb wrote:
Replies are inline, hopefully im right here ;-)
Note: it is assumed that host-a:/data/a, host-b:/data/b,
host-ns:/data/ns exist.
Q. Does gluster have a problem with server spec volumes which do
not exist on a given host?
I believe you are asking "what happen
Replies are inline, hopefully im right here ;-)
> Note: it is assumed that host-a:/data/a, host-b:/data/b,
> host-ns:/data/ns exist.
>
> Q. Does gluster have a problem with server spec volumes which do
> not exist on a given host?
I believe you are asking "what happens when you export a non
>
>
> volume unify
>type cluster/unify
>option scheduler rr
>option namespace remote-ns
>subvolumes remote-a remote-b* remote-ns*
> end-volume
>
'remote-ns' is not a subvolume. its just a namespace option for unify.
>
> -
> Note: it is assumed that host-a:/data
Hi,
Given the following server volume specification:
-
volume a
type storage/posix
option directory /data/a
end-volume
volume b
type storage/posix
option directory /data/b
end-volume
volume ns
type storage/posix
option directory /data/ns
end-
