We are currently in a 4 week Modularity Sprint #10, the usual 2 week sprint got extended due to FLOCK and pre-FLOCK developer meetings.
As you can see in the 'In Progress' and 'Complete' columns on our Taiga board, lots of tiny and larger pieces are coming together.
The following text describes how various parts of the Modularity infrastructure work together. Ralph Bean shows these connections in his Modularity infrastructure diagram.
Module build tasks can be submitted to orchestrator (rida) either by posting a short yaml text into the REST API or with 'fedpkg module-build'. The orchestrator will then download and parse the module description file, check the dependencies and schedule koji builds for missing components. The build process can be monitored with the Build Pipeline Overview (BPO) component and the final result will be fed into the Product definition center (PDC) which is a webapp and API designed for storing and querying product metadata.
All of the above is already done and in a usable state after this sprint, although not all patches have been added to the upstream repositories yet. Same features are still missing, but we'll continue adding them in the upcoming weeks.
Langdon demoed how all this works from a user perspective during his talk  at FLOCK in Krakow. Unfortunately a recording of his talk isn’t available on YouTube yet. Nils and Adam therefore put together a similar demo, you’ll find it in the Fedora Modularity channel on Youtube
Recent Posts from This Journal
Modularity New-Module-Process Adding and building a module for Fedora This describes the process of adding a new module to the Fedora Modularity…
[ Link to Part 1 One of our main communication channels is IRC. We've recently decided to standardize the name of our efforts as ' Modularity'…
The Fedora Modularity Project is an effort to fix several problems that all distributions face. One of them is the disconnect between Fedora's…