[Nix-dev] Nix-Store sharing (with NFS + AUFS)?

[Wout Mertens]

I looked into what would be needed to have multiple writers on the same
store here: https://github.com/NixOS/nix/issues/378#issuecomment-62724778

The same would apply for aufs-type multi writer setups.

The tl;dr is that Nix would need to treat sqlite as only a cache, with all
needed info written in the store, and that Eelco didn't like the idea :-)

I still would love to have this, the store is at the mercy of a single file
right now…

On Sat, Jan 16, 2016, 1:49 PM Arseniy Seroka <ars.seroka at gmail.com> wrote:

> You can't share over nfs because of sqlite. I've tried that myself and got
> no luck.
>
> --
> Sincerely,
> Arseniy Seroka
>
>
>
> On 16 January 2016 15:47:26 Matthias Beyer <mail at beyermatthias.de> wrote:
>
> > On 15-01-2016 17:19:37, Rok Garbas wrote:
> >> Quoting Matthias Beyer (2016-01-15 16:38:30)
> >> > Hi,
> >> >
> >> > I'm currently thinking about the following problem:
> >> >
> >> > I want to share the /nix/store from one Master machine to several
> Slaves, but
> >> > in a slightly different way than is currently possible with ssh /
> http:
> >> >
> >> > I want _one_ store which contains software, which then can be used by
> all the
> >> > slaves (like you'd do with NFS).
> >> >
> >> > The Slave machine should still be able to install software with the
> package
> >> > manager (nix) but only locally, not globally.
> >> >
> >> > So the Slave installs software to /nix/store locally, while /nix/store
> >> contains
> >> > store entries which are hosted on the master.
> >> >
> >> > My first idea would be NFS + AUFS, but maybe there are nix-buildin
> >> > possibilities?
> >> >
> >> >
> >> > Use-Case: Provide a standard-set of software but allow each VM to
> install own
> >> > software if needed, while keeping the amount of used storage as small
> as
> >> > possible.
> >> >
> >> > With the solution I'm searching for, 100 VMs which only use the
> standard
> >> > set on software would cause 1 % Storage-use (the packages are only
> phyiscally
> >> > available on one machine: the master) of the amount of storage which
> would be
> >> > needed with each VM installing the stuff.
> >> >
> >>
> >> you could also just use ``services.nix-serve`` module
> >>
> https://github.com/NixOS/nixpkgs/blob/release-15.09/nixos/modules/services/networking/nix-serve.nix
> >>
> >> and change all slaves to point their binary cache to Master's url.
> >>
> >
> > But wouldn't that cause the slaves to download the binaries from the
> > master instead of using them directly from the masters harddisc?
> >
> > --
> > Mit freundlichen Grüßen,
> > Kind regards,
> > Matthias Beyer
> >
> > Proudly sent with mutt.
> > Happily signed with gnupg.
> >
> >
> >
> > ----------
> > _______________________________________________
> > nix-dev mailing list
> > nix-dev at lists.science.uu.nl
> > http://lists.science.uu.nl/mailman/listinfo/nix-dev
> >
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-- 

Wout.
(typed on mobile, excuse terseness)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160116/148b5aa4/attachment.html