From mboxrd@z Thu Jan 1 00:00:00 1970 From: Devan Subject: Re: Orchestration working group (before: Guix orchestration notes) Date: Sun, 4 Mar 2018 03:18:39 +0100 Message-ID: <20180304021839.j7ittjuexbzdjtuj@kowloon> References: <871shigbgz.fsf@gmail.com> <20180301161855.GA6170@thebird.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="hbdq6ozzha7r2jve" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58687) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1esJEg-0003PL-UJ for guix-devel@gnu.org; Sat, 03 Mar 2018 21:18:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1esJEf-0007AJ-Si for guix-devel@gnu.org; Sat, 03 Mar 2018 21:18:50 -0500 Received: from q.meshwith.me ([2001:41d0:1:e20d::1]:45198) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1esJEf-00076u-L3 for guix-devel@gnu.org; Sat, 03 Mar 2018 21:18:49 -0500 Content-Disposition: inline In-Reply-To: <20180301161855.GA6170@thebird.nl> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Pjotr Prins Cc: guix-devel@gnu.org --hbdq6ozzha7r2jve Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, Pjotr Prins transcribed 0.6K bytes: > Hi Chris, >=20 > That was a lengthy writeup, thanks :). I think the first step is to > think in terms of (container/VM) provisioning. Then build that up towards > orchestration and workflows. I agree. I think a good start would be figuring out ways to essentially replace what you can do with Dockerfiles. Which to me=20 mainly means having the ability to arbitrarily copy files into, and=20 further manipulate the tarballs made from using `guix pack`. This would already allow us to build useful container images without=20 having to pull in random blob layers, which is the current state of affairs with docker. These could then be orchestrated with the many existing tools, and it would be a big step forward in reproducability=20 and security for that ecosystem. > There is some overlap with the HPC > working group, but I think we ought to have one on > orchestration/provisining/work flows. I am quite keen to have > something in place in the coming year. I.e., roll out firing up of > software combinations in isolated environments. Let's keep discussing > and build up a web page for that. >=20 > My first provisioning step is to start up a Guix container on a server > somewhere through a REST API and fire up a script that can run in the > container. That all sounds like good ideas to me. > Pj. Devan --hbdq6ozzha7r2jve Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEDMARp8PcbrR1Z5vJrAq6MYZqfnYFAlqbV3sACgkQrAq6MYZq fnYA7A/8CTFTYd2m4J1jGh/sJVfrgyGuzore280rrFE1RRsmG7klnAzVPSK1znCR guqdBx/Wc7Z1ubUrH/7v72Fbk5L5GMB4pf3KLqK832+kA0NDzvgYCx1BQO/HBNTi zdxzanhAjR44lzuFNc6SJFaTV6o6n7d0L/NjN9STTLkeheLicMDJY7cTnoeYaqNd sc+BVREjHYBDHKXUXz/xm5lq7A2XVLVH8QCjNxVpaZ81KIG4mSrRoCvsJBzHisF0 LeZMgYHHikA0cg7jfad8r4SLgZfByNQHwAXP16Ene5L4VVXbRmq1iI5NfLd5sU6C wDEgxu0CbuTWLVv/j2kr4MVCTFSmlOQhfrZPxNxnQHlpYKu7d1tfjB5wa7BbOoWT TC2OztvP1F+95Sb8p9j6Wf50FKGXG3PCg02R2nO0MLgv0Jn7I3z+zn8o+z++X4K6 cnbeki4rT/ur3r11in92deplP8GSq6bsybzFLpEI2WPsH4IwGE5g+0FLGicAGGYh sJr1UKpl/BjXXgVsPNZb4hwZB07CpJKnXh+MEnJlHJrygSadfrTZtmoHUmG0kEUA SJGfYHy7uaXZaSur2eQnoh4xsp31Nrq2dcXWY1wi1BZV2TcbP8CW4nTQlS23toVI s441tHoQ4OjhfbHHxZ7c/trMuFO6YBBXSD+2nZNEHEB5tixJ9zA= =6aJR -----END PGP SIGNATURE----- --hbdq6ozzha7r2jve--