This should wait till @arrfab will be back from PTO, he has more insight into it.

@lrossett : can you elaborate ?
sig-automotive builds happen on https://cbs.centos.org so you're talking about something else ?
If you mean the duffy ec2 node, they are already using 2 * 40Gb ebs volumes (one unconfigured, so that tenants can do what they need on top)
As we're limited with resources in that pool, and if you need something bigger, I'd like to discuss that on the dedicated ci-users list , instead of a ticket (easier to track and also participate for other CI tenants)

@phsmoura : can you verify also as I don't think that we ever had automotive SIG listed in the CI tenants so worth verifying/updating ?

Would it be possile to request nodes with more storage?

Some Automotive SIG builds can use a lot of storage while the build is being processed which ends up with an error because of insufficient disk size.

Which builds are you referring to? RPM or images?
The image builds aren't happening on the CentOS Infra and it's the ToolChain
team which has the hand on the pipeline, including the cloud instances used.

They are not being using by CBS or auto's toolchain CI system, I am using it to build aarch64 images but the available storage is not enough to build some images, such the soafee one which deploys autoware open ad kit.

My original question was about asking if there is a standard process of adding sercers with different capabilities to a pool/tenant but I can start that conversation in the ci user list as well.

@pingou : as automotive SIG chair, do you confirm you (automotive SIG) need a namespace on the CentOS CI cluster ? as we're migrating to AWS, automotive wasn't in our list of SIGs that opted in but we can easily add it and it would be using the sig-automotive group from FAS/ACO to grant access to that namespace.

Because there wasn't any feedback I'm closing this issue
Feel free to reopen it anytime if you have any update