From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id DD8A0138206 for ; Thu, 18 Jan 2018 12:34:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E1E78E08AE; Thu, 18 Jan 2018 12:34:47 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7F84DE0835 for ; Thu, 18 Jan 2018 12:34:47 +0000 (UTC) Received: from abudhabi.paradoxon.rec (p54A9D0A1.dip0.t-ipconnect.de [84.169.208.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: polynomial-c) by smtp.gentoo.org (Postfix) with ESMTPSA id CA3B5335C37; Thu, 18 Jan 2018 12:34:45 +0000 (UTC) Date: Thu, 18 Jan 2018 13:34:36 +0100 From: Lars Wendler To: "Anthony G. Basile" Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Managing updates on many identical Gentoo systems Message-ID: <20180118133436.532d5cef@abudhabi.paradoxon.rec> In-Reply-To: <2686de8e-334c-084b-4828-6109b10dd536@gentoo.org> References: <2686de8e-334c-084b-4828-6109b10dd536@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/h0Xb.0Z.w9jz9lvVHBmyodk"; protocol="application/pgp-signature" X-Archives-Salt: 2131038d-56f6-443a-a1a1-886f6b5b2217 X-Archives-Hash: 15f2a118f0cede4f58e7b504efc65d93 --Sig_/h0Xb.0Z.w9jz9lvVHBmyodk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Anthony, On Thu, 18 Jan 2018 06:46:53 -0500 Anthony G. Basile wrote: >Hi everyone, > >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. > >Unless there's some magic I don't know about (and this is why I'm >sending this email) each machine still needs to have the portage tree >installed locally (1.5 GB) or somehow mounted by a network filesystem >(which is not practical if the machines are not on a local network). >Furthermore, each machine would have to run emerge locally to do the >calculation of what packages need updating. > >This procedure is redundant because each machine is housing the same >data and doing the same dependence-tree calculation. It should be >possible to do this calculation on a centralized binhost and simply >communicate the update information to the remote machines. They would >then only have to download the .tbz2's and install them, keeping a tidy >/var/db/pkg. Thus they avoid having to house the portage tree and >burning cpu cycles that just calculate redundant information. > >I'm inspired here by OpenBSD's pkg_add which doesn't require all of >ports to be installed, and mender which is a > >Any ideas? > well, I never did anything like that but regarding the dependency calculation... how about something like emerge -1OKanv $(qlist -CISq) (--oneshot --nodeps --usepkgonly --ask --noreplace --verbose) which simply omits dependency calculations, only takes into account available binary packages and doesn't replace same versions? Of course this requires all installed packages really being available as binpkgs. Since all the installations are the same, as long as you provide a sane set of binpkgs, dependency calculation should not matter anyway. The only issue I can think of is that a system might become broken if the update gets interrupted before all packages have been updated. Kind regards --=20 Lars Wendler Gentoo package maintainer GPG: 21CC CF02 4586 0A07 ED93 9F68 498F E765 960E 9B39 --Sig_/h0Xb.0Z.w9jz9lvVHBmyodk Content-Type: application/pgp-signature Content-Description: Digitale Signatur von OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWCOBmo8i7LhvVmNAVx3S0DQ8YDkFAlpglF0ACgkQVx3S0DQ8 YDnD2w/+PrE8WjpmAhh01wNT9pa4EhvLzASRL5anWFuTUzU8SNOT73ncC+MBqZGS Qyf+f6liRxaR2NG3VVpkdaDJ1lUEQXueD2V/yatUGX1Xv3Gu7JgzdlFhvFEkuZE9 kHad8UZ5W9YGsplN9JKYhOO6Ui93FSNSwMQ0VjGX8/ew2A0wNTdsRWTemOpU7ZPN XYLNJp214z/sdww3qoVlyOUCnx4aDqbt8edDmdc6UZFOlobBhnMOjAnTDouBDaqF UnwZcsIZ7HvTOLwvdTEHCV50e2SNZqe91bT7QucQPibqryY+kf6NP5YVoYTKjZ/9 g5dun8sJfKbTF32TgZPSPCtTlyJ8J5V+doshOr1tzkiVWSKtQ56S02GMJvMo0rew LkhO5acswdYQlCS59qMPZbkAN8ge6xwX8KV7YFLPX0Y/EgVuP95IEZnL2bRvxWHf QhwUXYFBotF4+zfI1O0HYq8UZ75nXUNSa8aih+eZeeqiVqNanbxCqmOrvnAUq5to SyaLYewjyc0eysoc308V+M303JEL/pURoxBvbFBW2w/6C3c8R6nfTlJvHUdghq55 cL/0q+IiylkkCbC/jcBDE3FKD56So76bt5UfsX/JYoT/OhiYajmNlA0uCEW7fAQF jeLr8uJVThZE/oCMdpYbtnxVtwp1Tvyh8DwDTnMhfCeQ15bJdpE= =mamq -----END PGP SIGNATURE----- --Sig_/h0Xb.0Z.w9jz9lvVHBmyodk--