From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Orchestration working group (before: Guix orchestration notes) Date: Thu, 1 Mar 2018 17:18:55 +0100 Message-ID: <20180301161855.GA6170@thebird.nl> References: <871shigbgz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39571) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1erQyw-0007E9-Sg for guix-devel@gnu.org; Thu, 01 Mar 2018 11:22:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1erQyr-0000ZZ-Pi for guix-devel@gnu.org; Thu, 01 Mar 2018 11:22:58 -0500 Received: from mail.thebird.nl ([95.154.246.10]:50466) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1erQyr-0000Z1-IR for guix-devel@gnu.org; Thu, 01 Mar 2018 11:22:53 -0500 Content-Disposition: inline In-Reply-To: <871shigbgz.fsf@gmail.com> 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: Chris Marusich Cc: guix-devel@gnu.org Hi Chris, 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. 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. 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. Pj.