<div dir="ltr"><h2 class="gmail-part" id="gmail-September-30-Agenda">September 30 Agenda</h2><ul class="gmail-part"><li class="gmail-"> Test ansible 2.10 and drop 2.8 - <a href="https://github.com/pulp/pulp_installer/pull/448" target="_blank" rel="noopener">https://github.com/pulp/pulp_installer/pull/448</a> <ul><li class="gmail-">[mikedep333] to review the PR</li></ul> </li><li class="gmail-"> CI failing - <a href="https://github.com/pulp/pulp_installer/runs/1185310416#step:7:2174" target="_blank" rel="noopener">https://github.com/pulp/pulp_installer/runs/1185310416#step:7:2174</a> - already addressed <a href="https://github.com/pulp/pulpcore/commit/45827312f87c5d5fb88e01f206d27e5d813a85fd" target="_blank" rel="noopener">https://github.com/pulp/pulpcore/commit/45827312f87c5d5fb88e01f206d27e5d813a85fd</a> </li><li class="gmail-"> The majority of the issues at NEW are from the installer team, and most of them have been carried from multiple sprints ago - <a href="https://pulp.plan.io/agile/board?query_id=151" target="_blank" rel="noopener">https://pulp.plan.io/agile/board?query_id=151</a> <ul><li class="gmail-">[dkliban] schedule a meeting for next week to go through the backlog of issues - <a href="https://pulp.plan.io/projects/pulp/issues?query_id=162" target="_blank" rel="noopener">https://pulp.plan.io/projects/pulp/issues?query_id=162</a> (this query is only for the installer, container and operator not included)</li></ul> </li><li class="gmail-"> molecule has dropped python2 support since March, and we are using an ancient version in our CI that lacks support for collections on many levels. <ul><li class="gmail-">Can we drop python2 support in the installer? (The software we are installing doesn’t have it.)</li><li class="gmail-"><a href="https://github.com/ansible-community/molecule/issues/2629" target="_blank" rel="noopener">https://github.com/ansible-community/molecule/issues/2629</a></li><li class="gmail-"><a href="https://github.com/ansible-community/molecule/pull/" target="_blank" rel="noopener">https://github.com/ansible-community/molecule/pull/</a></li><li class="gmail-">Mike: This is about the control node (management node), not the managed node.</li><li class="gmail-">Mike: Many control nodes will have Ansible installed via Python2. <ul><li class="gmail-"> If an EL7 control (management) node user just does “sudo yum install ansible”, <a href="https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora" target="_blank" rel="noopener">as the Ansible 2.10 install docs say to do</a>, they’ll have python2 ansible. </li><li class="gmail-"> Many orgs have large, 3rd-party, Python 2 stacks. e.g., installed under /opt or an NFS share. I’ve seen this in the ML, experienced this IRL. </li><li class="gmail-"> If a Mac user runs <code>pip</code>, <a href="https://apple.stackexchange.com/a/376081" target="_blank" rel="noopener">they get python2, pip3 is a stub.</a> If a Mac user follows <a href="https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-macos" target="_blank" rel="noopener">the Ansible 1st party install instructions</a>, they use Python2. </li><li class="gmail-"> If an Ubuntu user follows their Ubuntu install instructions (install from PPA), they get python2 also. (Tested on 18.04) </li><li class="gmail-"> If a Mac / EL7 / Ubuntu 18.04 user follows <a href="https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-with-pip" target="_blank" rel="noopener">the Ansible pip install instructions</a>, they use Python2. <ul><li class="gmail-">All good arguments to bring to the molecule team <ul><li class="gmail-"><a href="https://github.com/ansible-community/molecule/issues/2764" target="_blank" rel="noopener">https://github.com/ansible-community/molecule/issues/2764</a></li></ul> </li></ul> </li></ul> </li><li class="gmail-">Mike: Can we just not test Python2 anymore with Molecule? <ul><li class="gmail-">What we don’t test, we don’t support. +1</li><li class="gmail-">Can we drop to use molecule and test with vagrant only? <ul><li class="gmail-">We can use py3 with molecule and install one vagrant box with py2 this is blocked by <a href="https://github.com/pulp/pulp_installer/pull/440" target="_blank" rel="noopener">https://github.com/pulp/pulp_installer/pull/440</a></li></ul> </li><li class="gmail-">Can molecule on py3 use ansible on py2?</li><li class="gmail-">Travis resources will be overwhelmed with running the vagrant box tests (approximately 9 out of 17) with every pulp_installer PR.</li><li class="gmail-">New org only for installers repos?</li></ul> </li></ul> </li></ul> -- <div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Mike DePauloHe / Him / HisService Reliability Engineer, Pulp<a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat</a><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-bottom:4px"></div>IM: mikedep333GPG: 51745404<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>