September 9th Agenda - [mikedep333] I want to say that the rest of the subteam was right about something from ~3 months ago. It was best not to create a branch supporting CI for pulp_installer. The effort would not have paid off. - We cannot run CentOS 8 molecule containers on our Fedora 32 systems right now. service/systemd module fails: - https://bugzilla.redhat.com/show_bug.cgi?id=1853407 - https://bugzilla.redhat.com/show_bug.cgi?id=1853736#c8 - switching to systemd module does not help - Can we ask RHEL8 for a fix? - agreed: Just run molecule on a VM - CI is red on source-upgrade: https://pulp.plan.io/issues/7479 - try pipdeptree - try https://github.com/pulp/pulp-oci-images/commit/755fa0f816bfac40fbf97f2dc2ca8fa5d6a6c873#diff-ef37552d3bc0dec828902c8331d481c7R10 - What is needed from the installer to support smooth roll out of https://github.com/pulp/pulpcore/pull/799 ? - Created installer subtask. - how docker changes can affect us? (Free plan – anonymous users: 100 pulls per 6 hours ) - https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/ - agreed: This will probably break many projects, so they might revert. Travis/GHA may also have a cache. So let’s address this later. We can consider Quay if it is more reliable then. - How Mike responded to the user email about RPMs install - Team thinks it was good to spend time investigating, for the user’s sake, for the sake of other users, and to look into the underlying issues (we want to find out about them early in CI, not when users report.)
-- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 <https://www.redhat.com/>
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev