tags 619065 - moreinfo thanks On 03/22/2011 10:47 AM, Hilko Bengen wrote: > Here is another example that I didn't even think of when I first wrote > the bug report. This is what I have been running successfully for a few > years, using vblade and home-grown wrappers: > > > A server exports identical but separate AoE targets to a number of > rather "dumb" clients, each on a separate VLAN. Separation using VLANs > puts each client into its own broadcast domain, so I am able to present > the same configuration to each client as far as AoE is concerned: From > every client's point of view, the "disk" it accesses is AoE target e0.0. > > > If I had used vblade-persist, only the first target could be > successfully brought up since the symlink creation would fail for every > target after that.
Gotcha! OK, this finally makes sense to me, thanks for your
persistence. Sorry if i seemed thick-headed about it initially; having
your concrete example of the problem in a real-world case is really useful.
> I suggest the following changes:
>
> - Don't let vblade-persist create the symlinks by default.
> - Add an option so the administrator can explicitly specify a symlink
> location. (This should be trivial by setting an environment variable.)
>
> If you want, I'll provide a patch.
> If you document the change in NEWS.Debian, there should be no surprises.
I'm going to go with a variant of your suggested approach -- the
symlinks will be created by default, but it will be trivial to disable
them for both existing and new vblade-persisted instances.
I've just started transitioning the package (upstream and debian
packaging) to git, so i'll make these changes as part of the transition.
Thanks for the discussion here, Hilko. I hope to have something pushed
out shortly.
--dkg
signature.asc
Description: OpenPGP digital signature
