As part of the initiative to move Fedora IoT to Image Builder via Koji instead of ImageFactory, we have received some requests from the Image Builder team. Ideally, if we could do this on koji staging to test everything and then move to koji prod that would be ideal.
We're not even sure if these are possible so any help/guidance would be much appreciated.
Outlined below:
There are two things that we will need in Fedora's Koji: We will need a service account. Image Builder will use this account to act as a content generator and create builds containing the built image. An account called something like osbuild-automation would be ideal. We would also like to be able to run a scratch osbuildImage task in Fedora's koji. osbuildImage task unfortunately doesn't support any kind of a scratch task so we need to think of another way to allow selected people to run a scratch task that's clearly not an official build. This is very useful for testing if the Image Builder integration works. I'm not 100% sure how Koji works but allowing us to run an osbuildImage task and tag it to some kind of "scratch" tag should be fine, right?
There are two things that we will need in Fedora's Koji:
We will need a service account. Image Builder will use this account to act as a content generator and create builds containing the built image. An account called something like osbuild-automation would be ideal.
osbuild-automation
We would also like to be able to run a scratch osbuildImage task in Fedora's koji. osbuildImage task unfortunately doesn't support any kind of a scratch task so we need to think of another way to allow selected people to run a scratch task that's clearly not an official build. This is very useful for testing if the Image Builder integration works. I'm not 100% sure how Koji works but allowing us to run an osbuildImage task and tag it to some kind of "scratch" tag should be fine, right?
If both asks are possible, then the sooner the better would be ideal.
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
So, first thing: Yeah, you can make your own service account(s) (one in stg and prod). See: https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/#_bot_accounts basically it just needs a wiki page and list of whos responsible for it, etc. Then it's a normal account otherwise.
I am not sure what to tell you about the scratch builds. Perhaps we could consult with @mikem / @tkopecek and see if they have any ideas?
Yes, osbuild doesn't have scratch builds. 1) I would file a ticket to add that support to https://github.com/osbuild/koji-osbuild 2) Meanwhile, as proposed. I would create some -scratch tag which can be aggressively garbage-collected and allowed tagging from anyone.
I think that answers things... please re-open if there's more questions or you hit problems with anything.
Once the service account is setup, we can make some sort of osbuildimage-scratch tag that test tasks go into and garbage collect it from time to time?
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Yes, that's great thanks for the responses.
Log in to comment on this ticket.