public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 4 Aug 2022 17:29:12 -0700	[thread overview]
Message-ID: <rt-4.0.4-180474-1659659352-852.32563-6-0@osuosl.org> (raw)
In-Reply-To: <rt-4.0.4-135343-1655762795-1742.32563-6-0@osuosl.org>

> > 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.
> 
> The same file can be used for bare metal. You only have to change the disk
> device entry from /dev/vda to /dev/sda. And you have to provide the ignition
> file through an URL that the system can reach.
> 
> BTW. The osuosl-butane.yaml file is a butane yaml file, while the install
> wants an ignition json file. You transform the yaml file into a json file
> using the butane binary, see
> https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/

I _finally_ got this system online. You should be able to ssh to it as
sourceware-builder1.osuosl.org.

A few changes I made to the ignition file:

- Change the console to go to ttyS1 so IPMI works properly
- Add OSL unmanaged ssh key to core user
- Setup IPv6 as a static IP address

Can you please confirm you have access and let me know how it looks?

Thanks-

-- 
Lance Albertson
Director
Oregon State University | Open Source Lab 

  parent reply	other threads:[~2022-08-05  0:29 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
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 [this message]
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-180474-1659659352-852.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).