[support.osuosl.org #32563] Request CI hosting for builder.sourceware.org

["Lance Albertson via RT" <hosting-request@osuosl.org>]

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 <short project name>-<hostname>.osuosl.org. So
> > I'd assume we'd go with sourceware-<hostname>.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