#6430 please grant koji admin permissions to a service "rida" for koji-stage
Closed: Fixed None Opened 7 years ago by lkocman.

Hello,

as a modularity group member (and former RH rel-eng), I'd like to get access to create koji-stage tags and targets as well as build individual rpms.

https://fedoraproject.org/wiki/Modularity_Working_Group

Business need:

Module build orchestrator "Říďa" (the director in Czech) is going to construct targets on demand including buildroot construction (build-tag inheritance based on module buildrequires).

fedpkg module-build core # supposed to contact orchestrator (layer above koji) build underlying rpms and track the progress of module build. Send message once it's done.

also please make sure that user "rida" exists and can build individual rpms.

Just to ensure:

We do need to be able to build from srpm (purely as temporary workaround for generating dist-tag macros on fly). Our tags are going to start by "module-*". The only user who will build modules is "rida". I suppose that admin permission for user/service rida should be enough.

Thanks

Lubos


there is a user in fas called rida, I think for development purposes we should just use someone's cert. Ideally we have more information about what is actually going to be done, and some say in the design of something that longer term we will have to run.

@ausil, can we have admin granted to 'lkocman', 'psabata', and 'ralph' in staging only? That way we can each use our own certs for development and we don't have to share one between us?

{{{
[dennis@ra ~]$ stg-koji grant-permission admin ralph
GenericError: user ralph already has permission: admin
[dennis@ra ~]$ stg-koji grant-permission admin lkocman
[dennis@ra ~]$ stg-koji grant-permission admin psabata
}}}

done, Note I really want to be more involved in the development here.

I also added these users to the template we use when syncing production koji db to staging.

Metadata Update from @lkocman:
- Issue set to the milestone: Fedora 25 Alpha

7 years ago

Login to comment on this ticket.

Metadata