public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is distfile partial mirror with failover possible?
Date: Wed, 6 Sep 2023 09:52:11 +0800	[thread overview]
Message-ID: <11e91796-7806-0b6f-35d9-1ec1a6dee509@iinet.net.au> (raw)
In-Reply-To: <ZPdB_crY71Z_SIAa@waltdnes.org>


On 5/9/23 22:58, Walter Dnes wrote:
> On Tue, Sep 05, 2023 at 08:04:19AM +0100, Neil Bothwick wrote
>> On Mon, 4 Sep 2023 22:54:38 -0400, Walter Dnes wrote:
>>
>>>    It looks like remote-mounting /var/cache/distfiles might be the
>>> quick-n-dirty solution like Alan suggested.  And I never have a need to
>>> have emerge run simultaneously on more than one machine.
>> It seems the simplest suitable solution for your needs.
>    And while we're at it, howsabout "emerge --sync" on one host, and then
> remote-mounting /var/db/repos/gentoo ?
>
Similarly - I was mounting a single location on moosefs (network 
filesystem) for ~15 hosts.  One host updates using --sync.  One 
buildhost for each architecture building packages.  Distfiles are 
handled the same way. Then "emerge -k" on the remainder checking for 
packages that needed an actual build.  If none, parallel merge (via 
ansible) or else single builds.  Resulting packages are also stored 
remotely per arch (various amd64, arm32, arm64 etc.)

Working well for a few years, but I am in the process of converting to 
nfs with a similar structure as I have decommissioned the moosefs system 
and many machines that are no longer needed.  A single machine will 
handle built packages, distfiles and repos which are mounted on the 
other systems via nfs. I will look into apt-cacher-ng as I was a fan of 
http-replicator until it was deprecated.

BillK



  parent reply	other threads:[~2023-09-06  2:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 10:12 [gentoo-user] Is distfile partial mirror with failover possible? Walter Dnes
2023-09-04 13:04 ` Michael
2023-09-04 17:21   ` Neil Bothwick
2023-09-04 17:49     ` Alan McKinnon
2023-09-04 18:26       ` Neil Bothwick
2023-09-04 19:37         ` Alan McKinnon
2023-09-04 20:02           ` Mark Knecht
2023-09-04 21:20             ` Arve Barsnes
2023-09-05 16:34           ` Laurence Perkins
2023-09-05  2:54     ` Walter Dnes
2023-09-05  7:04       ` Neil Bothwick
2023-09-05 14:58         ` Walter Dnes
2023-09-05 15:07           ` Michael
2023-09-05 15:26             ` Neil Bothwick
2023-09-05 15:33             ` Walter Dnes
2023-09-05 18:28               ` Michael
2023-09-06  1:52           ` William Kenworthy [this message]
2023-09-05  9:06   ` hitachi303
2023-09-05 15:05     ` Michael

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=11e91796-7806-0b6f-35d9-1ec1a6dee509@iinet.net.au \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@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