#249 RFE: MBS should import a note about built modules back into koji via the content-generator API.
Closed 6 years ago Opened 7 years ago by ralph.

From talking with @dgregor, there is a requirement that we make some sort of metadata note in Koji about the existence of everything we ship.

If we're going to ship modules as a new meta object wrapping rpms, then we should have some representation of it in koji.

We can use the content-generator API in koji to do this.


This is for RCM's sanity, but is not necessarily high priority. We don't have an immediate use case for it yet, but it makes sense for data consistency.

  • This requires defining the metadata spec that goes into the content-generator in koji.
  • A naming and numbering scheme for how the module would be translated into an NVR (mbs has its own notion of this, but it would need to be mapped to koji; the MBS has <name>-<stream>-<version>).
  • Define a lifecycle/workflow for the module objects that we're creating. Is there anything done to them, or are they just there? Do they get put into tags? Do they get tagged into a release tag when modules get shipped? Do they get tagged into an updates tag when the module gets updated?

Metadata Update from @sochotni:
- Issue assigned to sochotni

6 years ago

Metadata Update from @sochotni:
- Issue assigned to sochotni

6 years ago

Metadata Update from @sochotni:
- Issue assigned to sochotni

6 years ago

PR #522 is initial work on this. I've also sent out RFC email to koji-devel (I'd share a link but I think the infra is still recovering from PHX outage so the email is not visible in https://lists.fedorahosted.org/archives/list/koji-devel@lists.fedorahosted.org/)

Closing this since the PRs have been merged. Only thing remaining is enabling this - but that needs koji config changes.

Metadata Update from @sochotni:
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata