From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by sourceware.org (Postfix) with ESMTPS id 75F813857BA9 for ; Mon, 20 Jun 2022 19:36:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 75F813857BA9 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=osuosl.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=osuosl.org Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 0A732408DD; Mon, 20 Jun 2022 19:36:24 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 0A732408DD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1655753784; bh=OTj9IGq1G74gbYZZSNwM59FBsInktVEZsQjnNtnFgVo=; h=Subject:From:Reply-To:In-Reply-To:References:To:Cc:Date:From; b=uiXA1kvXPGhCcn0J0ROqNG6cVRPFGqi7JkmyJpishmassxmsXXg8527Lxf/4LZlPu WLIYMJEiAyAxer9QLy+9uTjVvLCvSDulPEKwNBfYcWMGLGux5JmtwZfbk/wB49wPL3 KK+Q+4EeqALbVHM7TPGU1GUNGZvIQIednMW1/2xnpN7k/BuobmFnz4+/z3/1ZjYlqC izRpOMlDLOxc492HMdRS1f45T1H0h7n0Xh4+uGQQZHZdJVTg956MX5Z+2QohZhEBr/ W13AqUR6YS+gD2g+8B+7clfmWXv8kNjxax2F4Oq5CAt3LY3sw7bBPxNjWI/7i85zET Zqy9GVTdT9BxQ== X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSfRhoDP8uQj; Mon, 20 Jun 2022 19:36:23 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp4.osuosl.org (Postfix) with ESMTP id DA1804086F; Mon, 20 Jun 2022 19:36:22 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org DA1804086F Received: by ash.osuosl.org (Postfix, from userid 81) id BF0631BF9B9; Mon, 20 Jun 2022 19:36:22 +0000 (UTC) Subject: [support.osuosl.org #32563] Request CI hosting for builder.sourceware.org From: "Lance Albertson via RT" Reply-To: hosting-request@osuosl.org In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: support.osuosl.org RT-Ticket: support.osuosl.org #32563 Managed-by: RT 4.0.4 (http://www.bestpractical.com/rt/) RT-Originator: ramereth@osuosl.org To: mark@klomp.org Cc: buildbot@sourceware.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Mon, 20 Jun 2022 12:36:22 -0700 X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2022 19:36:27 -0000 On Thu Jun 16 15:49:29 2022, mark@klomp.org wrote: > > > Fedora would be fine. But for the other container builders we are actually > > > using Fedora CoreOS, which is an auto updating variant (which is great for > > > our zero maintenance infrastructure). We could install that ourselves. Or > > > go with plain Fedora if we make sure it also autoupdates. > > > > I haven't had a chance to get in the data center to allocate a system. I'm > > hoping to get to that next week. Sorry for the delay! I'll try and get > > Fedora CoreOS installed. > > If you could use something like the attached butane/ignition file that would > be great. You might need to change the disk device name if it isn't /dev/vda > but everything else (except the hostname) is generic and allows the buildbot > to connect to it through ssh directly (might be on a different port behind > NAT). > > This is all the state/config needed. Everything else (docker images, git > repos, buildbot workers, builds, etc) can/will be regenerated when needed. So > we don't need any backups, because the whole setup can be regenerated by this > butane.yaml file. > > Assuming you are using openstack, see also > https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-openstack/ > > You don't need to use my ssh key for the core user. With this setup I don't > really need access. You can assign a different authorized key if you want to > have access yourself. > > But we can also go with plain Fedora and then I'll setup docker and the > builder user up myself. I believe we were going to allocate a new phyiscal system for this instead of allocating VM(s) for it on our OpenStack. Is that still correct? I was planning on using the bare metal installation guide [1] once I got hardware allocated. It doesn't look like it'll be that much work to install for us but I'll let you know if we run into any issues. I hope to get this online by the end of the week. [1] https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/ -- Lance Albertson Director Oregon State University | Open Source Lab