From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by sourceware.org (Postfix) with ESMTPS id 845F23858296 for ; Thu, 16 Jun 2022 17:40:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 845F23858296 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 smtp3.osuosl.org (Postfix) with ESMTP id 82FF260AAB; Thu, 16 Jun 2022 17:40:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N01-dUeFsYcU; Thu, 16 Jun 2022 17:40:42 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp3.osuosl.org (Postfix) with ESMTP id 6CA3961232; Thu, 16 Jun 2022 17:40:42 +0000 (UTC) Received: by ash.osuosl.org (Postfix, from userid 81) id 52CA71C1148; Thu, 16 Jun 2022 17:40:42 +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: Thu, 16 Jun 2022 10:40:42 -0700 X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, 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: Thu, 16 Jun 2022 17:40:46 -0000 On Tue Jun 07 15:25:09 2022, mark@klomp.org wrote: > Hi Lance (and hi builder hackers, this is the OSUOSL request), > > > The sourceware overseers, who do the technical management of all of > > > sourceware can be reached at overseers@sourceware.org. The builder > > > maintainers can be reached at buildbot@sourceware.org. Both are public > > > mailinglists: > > > https://sourceware.org/mailman/listinfo/overseers > > > https://sourceware.org/mailman/listinfo/buildbot > > > > Should either of these email addresses be included on this request? > > Yes. I didn't know if it was appropriate to include a public list on osuosl > tickets. But I added the builder project email address buildbot@sourceware.org > to this email. We've done it with other projects so it shouldn't be a problem as long as you're OK with it. > > > The type(s) of server(s) or service(s) you are requesting hosting for, if > > > applicable: > > > > > > We are looking for a larger x86_64 server with 16 to 32 cores, 32G memory > > > and 200GB diskspace on which we would like to run a container based > > > buildbot-worker (our current container hosts use Fedora Core with docker, > > > but any OS which supports docker and user namespaces would do). > > > > I believe we had some hardware around for this and we shouldn't have a > > problem with installing Fedora on it if that's what you want. > > 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. > > We typically name systems as -.osuosl.org. So > > I'd assume we'd go with sourceware-.osuosl.org. Do you have a > > hostname in mind? > > sourceware-builder.osuosl.org but note that we don't need a public reachable > host. All that is needed is a port to access it through ssh, which doesn't > need to be port 22. I'll likely go with sourceware-builder1.osuosl.org so we can easily increment it if we add more hosts. > > We'll also need an ssh key. > > Mine is: > ssh-rsa > AAAAB3NzaC1yc2EAAAADAQABAAABAQCgVJJnY8zh8uHn8d/E7p4j+9ueTvTHMRYOS0kkGhHBC7JmxCw6/EvbnbTsI0CQeyIJHlmPIqDVgRVjijcTWacd3vIdazzH9sqs65nl49yMnA23tIya4VWlbHC3J4x/LL84A4GaJO/FVF2vv6hVg3IGbopp5KX+pr6s56TiWddSDqMgjb7rSzjWuNyRK75ToctL7Y/Zn6st3ZioO7LXq3ghkWf8JR7ZaUFIY6P1qS5heiCHP0PxQJSrtpYzH3rKJoHpIkjxnsB/sD0C05cAdlzXBTUVTNLY+DPlQ7FeRkG+VK91briG4tvQ8ohhEiC9HuJu1AKMNWBZ9qeUwsXaJvNz > openpgp:0xC8437776 > > Which is derived from my pgp key: > https://gnu.wildebeest.org/blog/mjw/2019/02/17/new-pgp-key/ > > If that provides me admin access I would use it to create a builder user with > uid 1001 in the docker group with an authorized key to access the docker > socket to create the buildbot-worker containers. Using a separate account and > ssh authorization makes sure it can only be used for the container builder. OK sounds good. -- Lance Albertson Director Oregon State University | Open Source Lab