<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">imo, we should follow global requirements restrict and upgrade the package when</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">openstack/requirements upgrade it.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">several reason.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">1. Even if you do not co-install kolla with other project, it also affect the distro packaging.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">   For example RDO package kolla now and we should provide a good requirements.txt for them.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">   And we do not prevent user to co-install kolla with other project too.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">2. requirements upgrade may related to vulnerable bug.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">3. It is hard to maintain the requirements for kolla with project/requirements.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 20, 2017 at 11:45 AM,  <span dir="ltr"><<a href="mailto:hu.zhijiang@zte.com.cn" target="_blank">hu.zhijiang@zte.com.cn</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_8356727488691210471zcontentRow"> <p>Hello,</p><p><br></p><p>As global requirements changed in Ocata, Kolla upgrads pbr＞=1.8 [1] , </p><p>docker-py＞=1.8.1[2] . Besides, Kolla also starts depending on </p><p>oslo.utils＞=3.18.0 to use uuidutils.generate_uuid() instead of uuid.uuid4() to</p><p>generate UUID.</p><p><br></p><p>IMHO, Upgrading of [1] and [2] are actually not what Kolla really need to,</p><p>and uuidutils.generate_uuid() is also supported by oslo.utils-3.16. I mean</p><p>If we keep Kolla's requirement in Ocata as what it was in Newton, upper layer</p><p>user of Kolla like daisycloud-core project can still keep other things unchanged </p><p>to upgrade Kolla from stable/newton to stable/ocata. Otherwise, we have to </p><p>upgrade from centos-release-openstack-<wbr>newton to </p><p>centos-release-openstack-<wbr>ocata(we do not use pip since it conflicts with yum </p><p>on files installed by same packages). But this kind of upgrade may be too </p><p>invasive that may impacts other applications. </p><p><br></p><p>I know that there were some discusstions about global requirements update</p><p>these days. So if not really need to do these upgrades by Kolla itself, can</p><p>we just keep the requirement unchanged as long as possible?</p><p><br></p><p>My 2c.</p><p><br></p><p>[1] <a href="https://github.com/openstack/kolla/commit/2f50beb452918e37dec6edd25c53e407c6e47f53" target="_blank">https://github.com/openstack/<wbr>kolla/commit/<wbr>2f50beb452918e37dec6edd25c53e4<wbr>07c6e47f53</a></p><p>[2] <a href="https://github.com/openstack/kolla/commit/85abee13ba284bb087af587b673f4e44187142da" target="_blank">https://github.com/openstack/<wbr>kolla/commit/<wbr>85abee13ba284bb087af587b673f4e<wbr>44187142da</a></p><p>[3] <a href="https://github.com/openstack/kolla/commit/cee89ee8bef92914036189d02745c08894a9955b" target="_blank">https://github.com/openstack/<wbr>kolla/commit/<wbr>cee89ee8bef92914036189d02745c0<wbr>8894a9955b</a> </p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><div class="m_8356727488691210471zMailSign"><div><div><p>B. R.,</p><p>Zhijiang</p></div></div></div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Regards,</font></span></div><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Jeffrey Zhang</font></span></div><div><span style="font-family:monospace,monospace;font-size:12.8px">Blog: </span><a href="http://xcodest.me/" style="font-family:monospace,monospace;font-size:12.8px" target="_blank">http://xcodest.me</a><font face="monospace, monospace"><br></font></div></div></div></div></div></div></div></div></div>
</div>