Pulp 2:
-
Dep solving
-
Finished the part which interacts with libsolv (the multi-repo copy
feature is the last one left to close the dep solving features/bugs for
pulp2)
-
No smash tests for the new stuff yet
-
*AI*: dalley will work with QE to assist if they need help (issues
are mostly already written)
-
Multi-repo copy
-
Almost done, but there’s no tests for it and they are probably not
written either
Pulp 3:
-
Kickstart update (david/fabricio)
-
Started working on modeling changes
-
Question 1: How do we identify kickstart repos?
-
Pulp 2: We check for a treeinfo file at sync time
-
Alternative: Create a specific remote (e.g.
DistributionTreeRemote) that syncs down kickstarts
-
+1 to have one remote (and have a kickstart content as a part of
RPM plugin) for now
-
Question 2: relationship between kickstarts and sets of RPMs
-
Create a join between DistributionTrees and repos (or rather repo
versions)?
-
Probably repos, since they need to be able to be managed
independently as well.
-
Question 3: DistributionTree mutability?
-
No, immutable (upstream). Maybe within Pulp they should be mutable
but only the related RPM repositories.
-
Spoke with QE and they are interested if we know of gaps in test coverage
-
*AI*: ttereshc to reach kersom and probably do an audit
-
Containers work update
-
it’s coming together, expected to be done in a week or two.
Open PRs:
-
https://github.com/pulp/pulp_rpm/pulls
Triage:
-
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
-
Triage etherpad https://etherpad.net/p/rpm_triage_grooming
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
