<div dir="ltr"><div>Apologies for not sending all these sooner</div><div><br></div><div>## Dec 1 Agenda<br>* 3.15 RPMs support<br>    * [Figured out EL8 upgrade](<a href="https://github.com/pulp/pulp_installer/pull/793/commits/21bb6b64b406a28771881cbfb8d903b41c9e146c">https://github.com/pulp/pulp_installer/pull/793/commits/21bb6b64b406a28771881cbfb8d903b41c9e146c</a>) at last<br>    * Figured out EL7. Now idempotency is failing, but that is resolvable<br>    * Just realized I could easily create a 3.8 container with the old installer. Because no pip dependency issues to worry about.<br>    * [Issue with affinity](<a href="https://github.com/pulp/pulp-operator/issues/289#issuecomment-982702761">https://github.com/pulp/pulp-operator/issues/289#issuecomment-982702761</a>)<br>* Moving pulp_pkg_repo URLs from the molecule (CI) variables to the installer itself<br>    * [mikedep333] In a convo several months ago, I recall the Foreman build team saying this is OK to do now.<br>    * agreed: Put the URLs in pulp_installer, along with docs warnings about being unsupported, and have the Foreman build team review.<br>* Making redis optional in the installer<br>    * Agreed: If a user does not want redis, tell them to use a roles list [pulp_database, pulp_services, pulp_health_check, pulp_webserver]<br></div><div><br></div>## Nov 17 Agenda<br>* track sprint[s] on github issues? && how?<br>    * We can use labels<br>    * agreed: This subteam never followed sprints closely, so no need now.<br>    * agreed: We will implement if we feel the need for it.<br>* [mikedep333] Still trying to make time to work on pulpcore 3.15 RPM packages support<br>* [mikedep333] Still need to rename master branches to main<br>    * [mikedep333] Just renamed them. fao89 and I agreed we would just fix any breakages quickly, since it's easy to do.<br>    * pulp_installer master branch checks out pulpcore-selinux master. This needs to be updated ASAP to fix CI.<br>* Gave 2 talks and colected excellent feedback at pulpcon.<br>    * Still ongoing discussions about the feedback and engineering plans based on it. Such as:<br>        * pulp-pip-installer<br>        * Changing the docs or separating pulp_installer into "installing pulp" (`pulp_services`) vs "orchestrating the entire pulp node" (`pulp_all_services`)<br><br>## Nov 03 Agenda<br>* Fedora 35 - <a href="https://github.com/pulp/pulp_installer/pull/797">https://github.com/pulp/pulp_installer/pull/797</a><br>* Risky file permissions<br>    * ansible-lint warning<br>    * dkliban to file issue, ppicka to work it<br>        * <a href="https://github.com/pulp/pulp_installer/issues/800">https://github.com/pulp/pulp_installer/issues/800</a><br>* 3.15 release (Satoe request)<br>    * <a href="https://github.com/pulp/pulp_installer/pull/793">https://github.com/pulp/pulp_installer/pull/793</a><br>        * Mike to hopefully finish by end of day. Will follow up then.<br>    * <a href="https://github.com/pulp/pulp_installer/pull/796">https://github.com/pulp/pulp_installer/pull/796</a><br>* Plugins<br>    * <a href="https://github.com/pulp/pulp_installer/pull/382">https://github.com/pulp/pulp_installer/pull/382</a><br>* Working on pulpcore 3.15 RPM packages support<br>    * Debugging an issue, just FYI<br>    * I know it is blocking the 3.15.2-3 release<br><br>## Oct 20 Agenda<br>* Moving to github issues<br>    * check our backlog to close stale issues<br>    * <a href="https://blogs.harvard.edu/rprasad/2014/07/10/moving-from-redmine-to-github-issues/">https://blogs.harvard.edu/rprasad/2014/07/10/moving-from-redmine-to-github-issues/</a><br>    * Agreed: File new issues in GitHub.<br>    * Agreed: Move over existing issues when discussed/updated.<br>    * Agreed: Just rename the Redmine "category" "Installer" to "Installer - move to GitHub". Most users will not even use Redmine, or get the hint.<br>* <a href="https://pulp.plan.io/issues/9450">https://pulp.plan.io/issues/9450</a><br>    * Didn't we ask about the squid setup? In matrix/irc?<br>    * Squid proxy was run on same machine as pulp.<br>    * We do not understand why they would do that.<br>    * Agreed: Dkliban will talk to Yanis about it.<br>* How to run entire GHA workflow locally, not just molecule locally?<br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:capitalize"><span>Mike</span> <span>DePaulo</span><span style="text-transform:uppercase;color:rgb(170,170,170);margin:0px"></span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px 0px 4px;text-transform:capitalize">He / Him / His</p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px;text-transform:capitalize"><span>Service Reliability Engineer, Pulp</span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px 0px 4px;font-size:12px"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat<span></span></a></p><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-bottom:4px"></div><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px;font-size:12px"><span>IM: <span>mikedep333</span></span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px"><span>GPG: 51745404</span></p><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-top:12px"><table border="0"><tbody><tr><td width="100px"><a href="https://www.redhat.com/" target="_blank"><img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" width="90" height="auto"></a></td></tr></tbody></table></div></div></div></div>