Infrastructure/arc
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

decouple bodhi from pdc

Browse source 
Signed-off-by: Mark O Brien <markobri@redhat.com>
This commit is contained in:
Mark O Brien 2021-11-24 15:51:24 +00:00
parent 62e4abaa15
commit ccb94b5401
2 changed files with 38 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

37
docs/bodhi/decouple_bodhi_from_pdc.rst
View file

@ -3,3 +3,40 @@
Decouple Bodhi from pdc
========================================
Resources
----------
* Dtabase Models: https://bodhi.fedoraproject.org/docs/developer/models.html
Discussion
----------
Bodhi currently relies on PDC for criticl path package information, this
information could potentiallt=y be stored in Bodhi itself to remove the need to
call out to PDC at all. PDC currently works but is not maintained, n the case of
a CVE or some other reason we need to update PDC there could be knock on effects
with Bodhi.
What would be needed
--------------------
To add this functionality to Bodhi we would need to investigate if the packaging
entity present has the ability to cope with this change. New tooling would need
to be added to Bodhi to cope with the changes in the application.
The biggest piece of work would be to remodel the database to include a new
relation which would have the information to check if each package is critical
path for each release. Every package would need a record to specify if it was
critical path or not.
Conclusion
----------
After some initial investigation and discussion it was deemed that this should
not go into bodhi.
Dist-git is the source of truth for al packages so all package information
should be held in that application

2
docs/bodhi/index.rst
View file

@ -14,7 +14,7 @@ Resources
---------
* Bodhi repo: https://github.com/fedora-infra/bodhi
Bodhi wiki: https://fedoraproject.org/wiki/Bodhi
* Bodhi wiki: https://fedoraproject.org/wiki/Bodhi
Investigation
-------------