On Tue, Jun 29, 2021 at 10:08 PM Cleber Rosa <cr...@redhat.com> wrote: > > On Fri, Jun 11, 2021 at 7:04 AM Alex Bennée <alex.ben...@linaro.org> wrote: > > > > > > Cleber Rosa Junior <cr...@redhat.com> writes: > > > > > On Tue, Jun 8, 2021 at 2:30 AM Philippe Mathieu-Daudé <f4...@amsat.org> > > > wrote: > > > > > > Hi Alex, Stefan, > > > > > > On 6/8/21 5:14 AM, Cleber Rosa wrote: > > > > The QEMU project has two machines (aarch64 and s390x) that can be used > > > > for jobs that do build and run tests. > > > > > <snip> > > > > > > Who has access to what and should do what (setup)? How is this list of > > > hw managed btw? Should there be some public visibility (i.e. Wiki)? > > > > > > These are good questions, and I believe Alex can answer them about those > > > two machines. Even though I hooked them up to GitLab, > > > AFAICT he is the ultimate admin (maybe Peter too?). > > > > > > About hardware management, it has been suggested to use either the Wiki > > > or a MAINTAINERS entry. This is still unresolved and feedback > > > would be appreciated. For me to propose a MAINTAINERS entry, say, on > > > a v7, I'd need the information on who is managing them. > > > > I can only talk about aarch64.ci.qemu.org which is a donated Equinix > > machine that comes from the WorksOnArm initiative. I applied for it on > > behalf of the QEMU project and we can have it for as long as it's > > useful. > > > > I don't know if we need anything more that documenting the nominal > > contacts in: > > > > https://wiki.qemu.org/AdminContacts > > > > That's enough indeed, thanks. I'll follow up with a proposal about > the expected duties of admins, which should be nothing but common > sense. > > Is there anyone that can speak for the s390x machine? >
I can be the backup here, if needed. Willian
