Hi Saul I'm working at home remotely at home for the Government's restriction, my colleagues are also working remotely or still on vacation. You may see that my colleagues Yakun has just sent the preliminary result to you, and he will do some more test and update later. Wesley -----邮件原件----- 发件人: Saul Wold <sgw@linux.intel.com> 发送时间: 2020年2月4日 8:54 收件人: wesley.yang@jitstack.com; daniels.cai@jitstack.com; Yang, Bin <bin.yang@intel.com> 抄送: Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io 主题: Re: PBR Status Check Hi Wesley, Following up on this, I am not sure what your working status is because of the Virus and various Gov't restrictions. If you are working, can you give us an update on the Performance impact question I listed below. Thanks Sau! On 1/22/20 10:14 AM, Saul Wold wrote:
Hi All & Welcome Wesley,
We have a new community member from JitStack starting to look at the PBR work, here is some background for him.
The PBR work was proposed via the StarlingX Feature Specification process, see the Flock Versioning specification [0], this is based on the OpenStack Python Build Reasonableness [1] and Semantic Versioning (SemVer) [2] definition.
One of the issues that we are trying to resolve is the impact of the proposed change from Bin Yang to the time it takes to build a single package with PBR before and after the change. Ideally this would be done multiple times and provide the average along with the deviation. This in an important part of the project in order for us to move forward.
Look forward to working with you.
Sau!
[0] https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_flo ck_versioning.html
[1] https://docs.openstack.org/pbr/latest/ [2] https://docs.openstack.org/pbr/latest/user/semver.html