Hu, Kolla does not manage the global requirements process as it is global to OpenStack. The Kolla core reviewers essentially rubber stamp changes from the global requirements bot assuming they pass our gating. If they don’t pass our gating, we work with the committer to sort out a working solution.
Taking a look at the specific issues you raised: Pbr: https://github.com/openstack/requirements/blame/stable/ocata/global-requirements.txt#L158 Here is the change: https://github.com/openstack/requirements/commit/74a8e159e3eda7c702a39e38ab96327ba85ced3c (from the infrastructure team) Docker-py: https://github.com/openstack/requirements/blame/stable/ocata/global-requirements.txt#L338 Here is the change: https://github.com/openstack/requirements/commit/330139835347a26f435ab1262f16cf9e559f32a6 (from the magnum team) oslo-utils: https://github.com/openstack/requirements/blame/62383acc175b77fe7f723979cefaaca65a8d12fe/global-requirements.txt#L136 https://github.com/openstack/requirements/commit/510c4092f48a3a9ac7518decc5d3724df8088eb7 (I am not sure which team this is – the oslo team perhaps?) I would recommend taking the changes up with the requirements team or the direct authors. Regards -steve From: "hu.zhiji...@zte.com.cn" <hu.zhiji...@zte.com.cn> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <email@example.com> Date: Wednesday, April 19, 2017 at 8:45 PM To: "firstname.lastname@example.org" <email@example.com> Subject: [openstack-dev] [kolla] [daisycloud-core]Do we really need to upgrade pbr, docker-py and oslo.utils Hello, As global requirements changed in Ocata, Kolla upgrads pbr＞=1.8  , docker-py＞=1.8.1 . Besides, Kolla also starts depending on oslo.utils＞=3.18.0 to use uuidutils.generate_uuid() instead of uuid.uuid4() to generate UUID. IMHO, Upgrading of  and  are actually not what Kolla really need to, and uuidutils.generate_uuid() is also supported by oslo.utils-3.16. I mean If we keep Kolla's requirement in Ocata as what it was in Newton, upper layer user of Kolla like daisycloud-core project can still keep other things unchanged to upgrade Kolla from stable/newton to stable/ocata. Otherwise, we have to upgrade from centos-release-openstack-newton to centos-release-openstack-ocata(we do not use pip since it conflicts with yum on files installed by same packages). But this kind of upgrade may be too invasive that may impacts other applications. I know that there were some discusstions about global requirements update these days. So if not really need to do these upgrades by Kolla itself, can we just keep the requirement unchanged as long as possible? My 2c.  https://github.com/openstack/kolla/commit/2f50beb452918e37dec6edd25c53e407c6e47f53  https://github.com/openstack/kolla/commit/85abee13ba284bb087af587b673f4e44187142da  https://github.com/openstack/kolla/commit/cee89ee8bef92914036189d02745c08894a9955b B. R., Zhijiang
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev