public inbox for
 help / color / mirror / Atom feed
From: " via RT" <>
Subject: Re: [ #32565] AARCH64 OpenStack Request Form
Date: Tue, 7 Jun 2022 16:22:54 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Let's approve this request.


From: via RT <>
Sent: Wednesday, June 8, 2022 1:04:09 AM
Subject: [ #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
       Queue: AARCH64-Hosting
     Subject: AARCH64 OpenStack Request Form
       Owner: Nobody
      Status: new
 Ticket <URL: >


I tried submitting through the form at but got an error: Bad Request The
browser (or proxy) sent a request that this server could not

Name: Mark Wielaard

Project Name: sourceware - GNU Toolchain Infrastructure builder
Project URL:

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. 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

  parent reply	other threads:[~2022-06-07 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-06-07 23:03 ` Mark Wielaard
     [not found]   ` <>
     [not found]     ` <>
2022-06-07 23:22       `  via RT [this message]
     [not found]       ` <>
2022-06-07 23:39         ` [ #32565] AARCH64 OpenStack Request: sourceware - GNU Toolchain Infrastructure builder Lance Albertson via RT
     [not found]         ` <>
2022-07-11 22:47           ` Frank Nguyen via RT
2022-07-11 23:32             ` Mark Wielaard
2022-07-11 23:33               `  via RT
     [not found]               ` <>
2022-07-13 21:32                 ` Lance Albertson via RT
2022-07-14  9:30                   ` Mark Wielaard
2022-07-14  9:30                     `  via RT
     [not found]           ` <>
2022-07-14 20:54             ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).