From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" <dthompson2@worcester.edu> Subject: Re: Guix orchestration notes Date: Tue, 27 Mar 2018 14:27:25 -0400 Message-ID: <CAJ=RwfbMK13+HkcqgTUHUq-aZhVT8n8nfwxVCxrv=6_wst=y3g@mail.gmail.com> References: <871shigbgz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org> Received: from eggs.gnu.org ([2001:4830:134:3::10]:51779) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <dthompson2@worcester.edu>) id 1f0tJf-0000gC-JW for guix-devel@gnu.org; Tue, 27 Mar 2018 14:27:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <dthompson2@worcester.edu>) id 1f0tJe-00030c-Md for guix-devel@gnu.org; Tue, 27 Mar 2018 14:27:27 -0400 Received: from mail-vk0-x229.google.com ([2607:f8b0:400c:c05::229]:36309) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from <dthompson2@worcester.edu>) id 1f0tJe-00030T-Gn for guix-devel@gnu.org; Tue, 27 Mar 2018 14:27:26 -0400 Received: by mail-vk0-x229.google.com with SMTP id q198so7095181vke.3 for <guix-devel@gnu.org>; Tue, 27 Mar 2018 11:27:26 -0700 (PDT) In-Reply-To: <871shigbgz.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." <guix-devel.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>, <mailto:guix-devel-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/archive/html/guix-devel/> List-Post: <mailto:guix-devel@gnu.org> List-Help: <mailto:guix-devel-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>, <mailto:guix-devel-request@gnu.org?subject=subscribe> Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org> To: Chris Marusich <cmmarusich@gmail.com> Cc: guix-devel <guix-devel@gnu.org> Hi Chris, On Sat, Feb 17, 2018 at 11:37 PM, Chris Marusich <cmmarusich@gmail.com> wrote: > Hi, > > At FOSDEM, some of us discussed "orchestration", which means something > like "how to deploy services to more than 1 machine in a coordinated > fashion". Many people contributed to the discussion. I took notes. > I've thought about this more, reviewed the "wip-deploy" branch, and > written up my thoughts in the attached file. > > It's a rough sketch of ideas, biased with my own opinions and > experience, but I think it's good enough to share. I invite you to > improve upon it: share your own thoughts, hack some code together, and > just iterate on this a bit, so we can make some progress. > > Hopefully, we can agree on a basic design and get a working proof of > concept. Then we can make a blog post about it! These are good notes, thanks for sharing them! One additional use-case I would consider for an orchestration tool would be so-called "immutable deployment", where virtual machines are replaced entirely rather than updated in-place. This is commonly used for deploying web applications into auto scaling groups (where the actual number of hosts at any given time is dynamic) using a "blue-green" deployment technique (in a nutshell it's a double buffer that allows updating the application without downtime and allows easy rollback in the event the deploy breaks critical functionality). This is the kind of thing that I do at my day job, and we are but one of many companies that do things this way. - Dave