|
|
Line 1: |
Line 1: |
| PDC already stores data about products, releases and related information, but for modules we need to record additional things.
| | {{admon/important|This page is deprecated| All Fedora Modularity Documentation has moved to the new [https://docs.pagure.org/modularity/ Fedora Modularity Documentation website] with source hosted along side the code in the [https://pagure.io/modularity Fedora Modularity website git repository]}} |
| | |
| This page is about these changes, and how they should fit together with the existing structures. | |
| | |
| = Models =
| |
| | |
| The main new models are <code>UnreleasedVariant</code> which is where we store modules (but other stuff may use this, too, in the future, so it's a generic term) and <code>Tree</code> which carries each tree created for one such module. This is so we can store e.g. RPM packages for a module which isn't yet tied to a release, because we may not know that at the time we build the module. There are peripheral models, e.g. for storing inter-module dependencies, but they aren't fleshed out yet, so not described here.
| |
| | |
| = Diagram =
| |
| | |
| This abridged ER diagram outlines the changes we plan to do in terms of what's stored in the database. Everything upwards from and including <code>ReleaseVariant</code> are existing tables, everything below is new for Modularity. New relations are from the <code>UnreleasedVariant</code> to <code>ReleaseVariant</code> and from <code>Tree</code> to <code>ComposeTree</code>.
| |
|
| |
| [[File:Modularity-Architecture-PDC-Compose-Release-Trees-ER.png]]
| |
| | |
| = See Also =
| |
| | |
| * [[Modularity/Architecture/Infra]]
| |
| | |
| [[Category:Modularity]]
| |