From: "Lance Albertson via RT" <hosting-request@osuosl.org>
To: mark@klomp.org
Cc: buildbot@sourceware.org
Subject: [support.osuosl.org #32563] Request CI hosting for builder.sourceware.org
Date: Mon, 20 Jun 2022 12:36:22 -0700 [thread overview]
Message-ID: <rt-4.0.4-117150-1655753782-23.32563-6-0@osuosl.org> (raw)
In-Reply-To: <rt-4.0.4-176523-1655419769-1468.32563-6-0@osuosl.org>
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
next prev parent reply other threads:[~2022-06-20 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-32563@osuosl.org>
[not found] ` <Yp5+pqvhR8WYiaqq@wildebeest.org>
[not found] ` <rt-4.0.4-32453-1654617175-469.32563-6-0@osuosl.org>
2022-06-07 22:24 ` Mark Wielaard
[not found] ` <rt-4.0.4-80639-1654640709-839.32563-6-0@osuosl.org>
2022-06-16 17:40 ` Lance Albertson via RT
2022-06-16 22:49 ` Mark Wielaard
2022-06-16 22:49 ` via RT
[not found] ` <rt-4.0.4-176523-1655419769-1468.32563-6-0@osuosl.org>
2022-06-20 19:36 ` Lance Albertson via RT [this message]
2022-06-20 22:06 ` Mark Wielaard
2022-06-20 22:06 ` via RT
[not found] ` <rt-4.0.4-135343-1655762795-1742.32563-6-0@osuosl.org>
2022-08-05 0:29 ` Lance Albertson via RT
2022-08-05 1:30 ` Mark Wielaard
2022-08-05 1:31 ` via RT
[not found] ` <rt-4.0.4-195587-1659663068-623.32563-6-0@osuosl.org>
2022-08-05 15:52 ` Lance Albertson via RT
2022-08-05 21:17 ` Mark Wielaard
2022-08-05 21:17 ` via RT
[not found] ` <rt-4.0.4-171867-1659734276-616.32563-6-0@osuosl.org>
2022-08-05 21:52 ` Lance Albertson via RT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rt-4.0.4-117150-1655753782-23.32563-6-0@osuosl.org \
--to=hosting-request@osuosl.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).