From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Managing updates on many identical Gentoo systems
Date: Fri, 19 Jan 2018 09:45:18 -0500 [thread overview]
Message-ID: <CAAr7Pr9Y2m39TbarD9cjhUk3GX4180rRmun4s8-2LT+Yp+X+uQ@mail.gmail.com> (raw)
In-Reply-To: <ff36ac2b-f477-a13c-44fd-9b8ee6f35b2c@iinet.net.au>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Thu, Jan 18, 2018 at 5:13 PM, Bill Kenworthy <billk@iinet.net.au> wrote:
> On 18/01/18 23:36, Duncan wrote:
> > Anthony G. Basile posted on Thu, 18 Jan 2018 06:46:53 -0500 as excerpted:
> >
> >> I'm trying to design an update system for many identical Gentoo systems.
> >> Using a binhost is obvious, but there are still problems with this
> >> approach.
> >>
>
> I'd suggest go for a semi diskless OS - boot them from one central image
> with an individual overlay filesystem with local customisations. NFS
> mount the common directories.
>
> you just have a one central host to build for and don't need to worry
> about portage everywhere.
>
> Worked ok with a small number of mythtv frontends.
>
It doesn't work if you have a WAN; NFS needs low latencies between the NFS
server and the client or you will have a bad time.
>
> BillK
>
>
[-- Attachment #2: Type: text/html, Size: 1435 bytes --]
next prev parent reply other threads:[~2018-01-19 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 11:46 [gentoo-dev] Managing updates on many identical Gentoo systems Anthony G. Basile
2018-01-18 12:00 ` Joakim Tjernlund
2018-01-18 12:34 ` Lars Wendler
2018-01-18 19:22 ` NP-Hardass
2018-01-18 12:42 ` Martin Gysel
2018-01-18 15:36 ` [gentoo-dev] " Duncan
2018-01-18 22:13 ` Bill Kenworthy
2018-01-19 14:45 ` Alec Warner [this message]
2018-01-19 15:03 ` Anthony G. Basile
2018-01-19 18:13 ` Zac Medico
2018-01-20 15:34 ` Anthony G. Basile
2018-01-20 21:48 ` Zac Medico
2018-01-18 16:13 ` [gentoo-dev] " Alec Warner
2018-01-18 23:01 ` Zac Medico
2018-01-18 22:30 ` Alexander Tsoy
2018-01-18 22:53 ` Alexander Tsoy
2018-01-18 23:00 ` R0b0t1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAr7Pr9Y2m39TbarD9cjhUk3GX4180rRmun4s8-2LT+Yp+X+uQ@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox