Hi, I tried submitting through the form at https://osuosl.org/services/aarch64/ but got an error: Bad Request The browser (or proxy) sent a request that this server could not understand. Name: Mark Wielaard Email: mark@klomp.org CC: buildbot@sourceware.org Project Name: sourceware - GNU Toolchain Infrastructure builder Project URL: https://builder.sourceware.org/ Estimated Size of User Community: ~500 committers across all projects, but only ~3 buildbot admins might need direct access Description of Project Mission: sourceware provides hosting for the GNU Toolchain, gcc, binutils, gdb, glibc, but also various other related projects like valgrind, elfutils, bzip2, libabigail, dwz, debugedit. builder.sourceware.org is our buildbot based CI for these projects. We have native/VM workers for ppc64le, s390x, ppc64, i386, arm64 and armhf for debian, fedora and centos and x86_64 container builders for fedora, debian and opensuse. Doing hundreds of builds a day. But our arm64 worker is a single odroid N2+ board which is really underpowered and is unable to build the larger projects. Expected Usage Model: buildbot based CI Anticipated duration of need: indefinitely Deployment timeframe: Within 7 business days Flavor: 8 CPU, 16G RAM, 160G Disk Number of nodes: 1 Distribution: Fedora OpenStack Access: Have the OSL create the node for me SSH Public Key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCgVJJnY8zh8uHn8d/E7p4j+9ueTvTHMRYOS0kkGhHBC7JmxCw6/EvbnbTsI0CQeyIJHlmPIqDVgRVjijcTWacd3vIdazzH9sqs65nl49yMnA23tIya4VWlbHC3J4x/LL84A4GaJO/FVF2vv6hVg3IGbopp5KX+pr6s56TiWddSDqMgjb7rSzjWuNyRK75ToctL7Y/Zn6st3ZioO7LXq3ghkWf8JR7ZaUFIY6P1qS5heiCHP0PxQJSrtpYzH3rKJoHpIkjxnsB/sD0C05cAdlzXBTUVTNLY+DPlQ7FeRkG+VK91briG4tvQ8ohhEiC9HuJu1AKMNWBZ9qeUwsXaJvNz openpgp:0xC8437776
Lance, Let's approve this request. P ________________________________ From: via RT <aarch64-hosting-request@osuosl.org> Sent: Wednesday, June 8, 2022 1:04:09 AM Subject: [support.osuosl.org #32565] AARCH64 OpenStack Request Form [EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.] Tue Jun 07 16:04:09 2022: Request 32565 was acted upon. Transaction: Ticket created by mark@klomp.org Queue: AARCH64-Hosting Subject: AARCH64 OpenStack Request Form Owner: Nobody Requestors: mark@klomp.org Status: new Ticket <URL: https://support.osuosl.org/Ticket/Display.html?id=32565 > Hi, I tried submitting through the form at https://osuosl.org/services/aarch64/ but got an error: Bad Request The browser (or proxy) sent a request that this server could not understand. Name: Mark Wielaard Email: mark@klomp.org CC: buildbot@sourceware.org Project Name: sourceware - GNU Toolchain Infrastructure builder Project URL: https://builder.sourceware.org/ Estimated Size of User Community: ~500 committers across all projects, but only ~3 buildbot admins might need direct access Description of Project Mission: sourceware provides hosting for the GNU Toolchain, gcc, binutils, gdb, glibc, but also various other related projects like valgrind, elfutils, bzip2, libabigail, dwz, debugedit. builder.sourceware.org is our buildbot based CI for these projects. We have native/VM workers for ppc64le, s390x, ppc64, i386, arm64 and armhf for debian, fedora and centos and x86_64 container builders for fedora, debian and opensuse. Doing hundreds of builds a day. But our arm64 worker is a single odroid N2+ board which is really underpowered and is unable to build the larger projects. Expected Usage Model: buildbot based CI Anticipated duration of need: indefinitely Deployment timeframe: Within 7 business days Flavor: 8 CPU, 16G RAM, 160G Disk Number of nodes: 1 Distribution: Fedora OpenStack Access: Have the OSL create the node for me SSH Public Key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCgVJJnY8zh8uHn8d/E7p4j+9ueTvTHMRYOS0kkGhHBC7JmxCw6/EvbnbTsI0CQeyIJHlmPIqDVgRVjijcTWacd3vIdazzH9sqs65nl49yMnA23tIya4VWlbHC3J4x/LL84A4GaJO/FVF2vv6hVg3IGbopp5KX+pr6s56TiWddSDqMgjb7rSzjWuNyRK75ToctL7Y/Zn6st3ZioO7LXq3ghkWf8JR7ZaUFIY6P1qS5heiCHP0PxQJSrtpYzH3rKJoHpIkjxnsB/sD0C05cAdlzXBTUVTNLY+DPlQ7FeRkG+VK91briG4tvQ8ohhEiC9HuJu1AKMNWBZ9qeUwsXaJvNz openpgp:0xC8437776
On Tue Jun 07 16:22:53 2022, ppouliot@amperecomputing.com wrote:
> Lance,
>
> Let's approve this request.
We'll get this going soon!
--
Lance Albertson
Director
Oregon State University | Open Source Lab
Hi, Your machine is ready on 140.211.167.69. Frank.
Hi Frank,
On Mon, Jul 11, 2022 at 03:47:15PM -0700, Frank Nguyen via RT wrote:
> Your machine is ready on 140.211.167.69.
Thanks. I found the fedora account and could login and have sudo
access.
I see the machine has Fedora 32 installed. Can we just upgrade to
Fedora 36 using normal sudo dnf system-upgrade ... or is there a
different procedure to do that?
Thanks,
Mark
Hi Frank,
On Mon, Jul 11, 2022 at 03:47:15PM -0700, Frank Nguyen via RT wrote:
> Your machine is ready on 140.211.167.69.
Thanks. I found the fedora account and could login and have sudo
access.
I see the machine has Fedora 32 installed. Can we just upgrade to
Fedora 36 using normal sudo dnf system-upgrade ... or is there a
different procedure to do that?
Thanks,
Mark
> On Mon, Jul 11, 2022 at 03:47:15PM -0700, Frank Nguyen via RT wrote:
> > Your machine is ready on 140.211.167.69.
>
> Thanks. I found the fedora account and could login and have sudo access.
>
> I see the machine has Fedora 32 installed. Can we just upgrade to Fedora 36
> using normal sudo dnf system-upgrade ... or is there a different procedure to
> do that?
I just uploaded a Fedora 36 image. If you would like, we could rebuild your VM
using that image. I know you had already started the upgrade from what you said
on IRC. Please let me know how you'd like to proceed.
--
Lance Albertson
Director
Oregon State University | Open Source Lab
Hi Lance, On Wed, Jul 13, 2022 at 02:32:03PM -0700, Lance Albertson via RT wrote: > I just uploaded a Fedora 36 image. If you would like, we could rebuild your VM > using that image. I know you had already started the upgrade from what you said > on IRC. Please let me know how you'd like to proceed. The dnf system-upgrade to f34 and then to f36 worked out fine. And the system is already integrated into builder.sourceware.org crunching out builds: https://builder.sourceware.org/buildbot/#/workers/25 So we are totally happy with the current setup. Thanks, Mark
Hi Lance, On Wed, Jul 13, 2022 at 02:32:03PM -0700, Lance Albertson via RT wrote: > I just uploaded a Fedora 36 image. If you would like, we could rebuild your VM > using that image. I know you had already started the upgrade from what you said > on IRC. Please let me know how you'd like to proceed. The dnf system-upgrade to f34 and then to f36 worked out fine. And the system is already integrated into builder.sourceware.org crunching out builds: https://builder.sourceware.org/buildbot/#/workers/25 So we are totally happy with the current setup. Thanks, Mark
> > I just uploaded a Fedora 36 image. If you would like, we could rebuild your
> > VM using that image. I know you had already started the upgrade from what
> > you said on IRC. Please let me know how you'd like to proceed.
>
> The dnf system-upgrade to f34 and then to f36 worked out fine. And the system
> is already integrated into builder.sourceware.org crunching out builds:
> https://builder.sourceware.org/buildbot/#/workers/25
>
> So we are totally happy with the current setup.
Awesome! Glad it's working out for you. Going ahead and closing this ticket.
--
Lance Albertson
Director
Oregon State University | Open Source Lab