Fedora and PDC, road forward

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Good Morning Everyone,

So yesterday we held a meeting on #fedora-apps about the future of PDC in Fedora.
We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora
Here is the gist of it:

What do we currently store in PDC:
* modules data - the list of what modules have been built, what rpms are in them,
    and which ones are active or not.
* Stream branches, branch ownership, retirement dates (EOL/SLE)
* release/life-circle tracking
   * product and product versions (fedpkg gets active Fedora and EPEL releases 
    from product versions endpont) 
* critpath boolean on packages (bodhi uses this)
* metadata from composes (RPMS/images)
* "dependency" data about which rpms depend on which other rpms and which 
    containers include other rpms.  This is not used by anything and can be 
    de-prioritized, dropped.  (It was originally going to be used in Freshmaker.)
  Endpoints:
  * release-component-relationships
  * release-components
* List of all packages: fedora-packages uses this list to know what to index. 
    It sets up the "for loop" from which fedora-packages pulls data from all our
    other systems.
   Endpoints:
       * global-components


After some discussion the decision we reached was:
* The "dependency" data in its current form can be dropped. It's something we'll
    need in the future but the data structure will most likely need to be 
    adjusted so let's just drop the existing data and worry about this later.
* The critpath boolean can just be imported into bodhi itself, especially 
    considering that bodhi is the only tool using this flag.
* The modules data is entirely going to move into MBS

Everything else (ie: composes metadata, release/life-circle tracking,
package/branches information) will need to find a new home.
This new home will be a new django app using the Django Rest Framework (DRF) in
which we will import the PDC apps as needed (potentially adjusting them where
desired).

- kellin has agreed to be the project leader for this work but needs a team to
  do the actual work.
- pingou has agreed to look for said team


If you have any worries, questions or suggestions or if you want to join the
effort, please let us know :)


Finally some links:
Minutes: https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.2018-06-11-14.01.html      
Minutes (text): https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.2018-06-11-14.01.txt
Log: https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.2018-06-11-14.01.log.html      


Have a nice day,
Pierre 

Attachment: signature.asc
Description: PGP signature

_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx/message/N5UHPQE4NZO6O4VZK7WPFWPWVSSN3367/

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux