<div dir="ltr"><div>Hi,</div><div><br></div><div>Note that all pins related to python2 support removal have been removed from RDO Trunk master (Ussuri) today [1].</div><div><br></div><div>What that means for RDO users?</div><div><br></div><div>- Some packages are now failing to build in <a href="https://trunk.rdoproject.org/centos7-master/report.html">https://trunk.rdoproject.org/centos7-master/report.html</a>, this centos7-master RDO Trunk repo will not be consistent again and it's recommended that anyone using RDO Trunk for master/Ussuri in CentOS 7 to move to CentOS 8 equivalent.</div><div>- Now RDO Trunk repo for CentOS 8 in master <a href="https://trunk.rdoproject.org/centos8-master/report.html">https://trunk.rdoproject.org/centos8-master/report.html</a> is consistent and following master branch or using versions defined in upper-constraints [2].</div><div>- Content in promoted repositories previously both for CentOS 7 and 8 should be unaffected by this change.<br></div><div>- There are still two projects still pinned (mistral and neutron) for other unrelated issues, we'll keep working to get them unpinned as soon as possible.</div><div>- This change has no impact in stable releases.<br></div><div><br></div><div>Please, let us know if you have any question or issue related to this.</div><div><br></div><div>Best regards,</div><div><br></div><div>Alfredo<br></div><div><div><br></div><div>[1] <a href="https://review.rdoproject.org/r/#/q/topic:unpin-py2+(status:open+OR+status:merged)">https://review.rdoproject.org/r/#/q/topic:unpin-py2+(status:open+OR+status:merged)</a></div><div>[2] <a href="https://github.com/openstack/requirements/blob/master/upper-constraints.txt">https://github.com/openstack/requirements/blob/master/upper-constraints.txt</a></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 20, 2020 at 3:03 PM Alfredo Moralejo Alonso <<a href="mailto:amoralej@redhat.com">amoralej@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div id="gmail-m_1973726473100481690gmail-magicdomid9"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid10"><span>Hi,</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid11"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid124"><span>I'd like to open </span><span>a </span><span>discussion about the status of RDO Ussuri repositories on CentOS7.</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid13"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid701"><span>As you know RDO and upstream teams (kolla, puppet-openstack, TripleO, TripleO CI, etc...) have been working to switch to CentOS8 during last</span><span> few</span><span> weeks.</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid15"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid730"><span>In order to make the transition easier from CentOS</span><span> </span><span>7 to CentOS</span><span> </span><span>8, RDO is still maintaining Trunk repos consistent for both CentOS</span><span> </span><span>7/</span><span>P</span><span>ython</span><span> </span><span>2 and CentOS</span><span> </span><span>8/</span><span>P</span><span>ython</span><span> </span><span>3. As </span><span>OpenStack </span><span>p</span><span>rojects</span><span> have been dropping support for </span><span>P</span><span>ython</span><span> </span><span>2, we've </span><span>started </span><span>pinning them to </span><span>the </span><span>last commit working with </span><span>P</span><span>ython</span><span> </span><span>2</span><span>[1], we were expecting that transition will finish soon but it's still goin</span><span>g</span><span> on.</span><span> Over</span><span> </span><span>time</span><span>,</span><span> the number of pinned packages ha</span><span>s</span><span> been growing including services and </span><span>O</span><span>slo libraries where we can't follow upper-constraints anymore</span><span>[2]</span><span>. Recently, </span><span>K</span><span>olla has removed support for CentOS</span><span> </span><span>7 so i doubt it makes sense to keep pinning packages to keep RDO Trunk consistent artificially and continue running promotion pipelines on a repo with so many </span><span>outdated</span><span> packages. Also, pinning these projects makes that changes needed for CentOS 8 will not be in RDO and would need to be backported manually to each package. My proposal is:</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid17"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid739"><span>- Unpin all packages in Ussuri to follow master trunk</span><span>,</span><span> or versions in u</span><span>pper</span><span>-c</span><span>onstraints</span><span> (for clients and libraries).</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid885"><span>- RDO Ussuri on CentOS</span><span> </span><span>7 repo consistent link will not move anymore (so no more promotions based on it).</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid907"><span>- We</span><span> wi</span><span>ll keep running centos7-master</span><span> DLRN builder</span><span>, so </span><span>that </span><span>packages still buil</span><span>ing</span><span> with </span><span>P</span><span>ython</span><span> </span><span>2 will be available in current repo [3] to be used by team</span><span>s</span><span> </span><span>needing them</span><span> until migration to CentOS 8 is finished everywhere.</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid897"><span>- Projects which already ha</span><span>ve</span><span> </span><span>C</span><span>ent</span><span>OS </span><span>8 jobs gating in master branch can remove </span><span>C</span><span>ent</span><span>OS </span><span>7 ones.</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid377"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid599"><span>We understand this can add some pressure on moving to CentOS8 to the teams working on it, but I'd say it's already a priority and it's justified at this stage.</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid22"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid811"><span>What do you think about this plan?, is there any reason to keep CentOS</span><span> </span><span>7</span><span> artificially </span><span>consistent and promoting at this point of the transition to CentOS</span><span> </span><span>8?</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid224"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid25"><span>Best regards,</span></div><div id="gmail-m_1973726473100481690gmail-magicdomid26"><br></div><div id="gmail-m_1973726473100481690gmail-magicdomid27"><span>Alfredo</span></div><div><span><br></span></div><div><div id="gmail-m_1973726473100481690gmail-magicdomid355"><span>[1] </span><span><a href="https://review.rdoproject.org/r/#/q/topic:pin-py2" target="_blank">https://review.rdoproject.org/r/#/q/topic:pin-py2</a></span></div><div id="gmail-m_1973726473100481690gmail-magicdomid374"><span>[2] </span><span><a href="https://review.rdoproject.org/r/#/c/24796/" target="_blank">https://review.rdoproject.org/r/#/c/24796/</a></span></div><div id="gmail-m_1973726473100481690gmail-magicdomid373"><span>[3] </span><span><a href="http://trunk.rdoproject.org/centos7-master/current" target="_blank">http://trunk.rdoproject.org/centos7-master/current</a></span></div><span></span></div></div>
</blockquote></div>