[opnfv-tech-discuss] [linuxfoundation.org #45985] 答复: Re: [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] 答复: RE: RE: Hi, ollivier and functest team, one test issue from community CI.

I'v got it. thanks. 尚小冬 shangxiaodong 原始邮件 发件人： ; 收件人： ; 抄送人：冯晓伟00125593; ; 日 期 ：2017年12月11日 18:07 主 题 ：Re: [opnfv-tech-discuss][OPNFV Helpdesk #45985]

[opnfv-tech-discuss] 答复: Re: [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] 答复: RE: RE: Hi, ollivier and functest team, one test issue from community CI.

I'v got it. thanks. 尚小冬 shangxiaodong 原始邮件 发件人： ; 收件人： ; 抄送人：冯晓伟00125593; ; 日 期 ：2017年12月11日 18:07 主 题 ：Re: [opnfv-tech-discuss][OPNFV Helpdesk #45985]

[opnfv-tech-discuss] [releng] Plugfest Topics Followup

Hi all, I wanted to summarize a few of the releng topics I was involved in at the OPNFV Plugfest last week. Thank you all who attended the sessions I lead! There was a lot of great feedback from the projects as well as the OpenStack community. * Automating Release[1] This topic was

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Hi Fatih, this was just a suggestion - mostly to keep Releng in line with what other projects do in OPNFV - the test-projects are probably the closest comparison here. I also don't think that there would not be much of a change: You'd have a Releng working group with several projects (those

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 Jose > On 08 Dec 2017, at 01:01, Fatih Degirmenci > wrote: > > Hi Releng Committers, > > During OPNFV Plugfest, we had conversations around having committer list per > Releng repository/Gerrit Project. > > The reason behind this is that, Releng

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Hi Frank, Thanks for the feedback. Splitting Releng is perhaps an option but I personally do not think it will add too much value. I believe support functions such as what Releng aims to provide is best handled as a whole rather than multiple individual projects. This is important in order to

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] 答复: RE: RE: Hi, ollivier and functest team, one test issue from community CI.

It seems a run-time dependency as your shell script calls it. My understanding is that test-requirements.txt should mainly include unit tests requirements. It is synchronized with OpenStack Pike's global requirements then you should add the lower bound as well.

[opnfv-tech-discuss] [linuxfoundation.org #45985] RE: [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] 答复: RE: RE: Hi, ollivier and functest team, one test issue from community CI.

It seems a run-time dependency as your shell script calls it. My understanding is that test-requirements.txt should mainly include unit tests requirements. It is synchronized with OpenStack Pike's global requirements then you should add the lower bound as well.

[opnfv-tech-discuss] [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] 答复: RE: RE: Hi, ollivier and functest team, one test issue from community CI.

Ok， we will add the dependency in parser project. Actually it's only a test requirement without specified version, parser doesn't need python-openstackclient. 尚小冬 shangxiaodong 原始邮件 发件人： ; 收件人：尚小冬10032185; 抄送人：

[opnfv-tech-discuss] [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] RE: RE: Hi, ollivier and functest team, one test issue from community CI.

Listing upper-constraints doesn’t mean that it will be installed. It only enforces the right version. Functest doesn’t leverage on it then why should we force the installation in our container? It must be installed as any parser dependency when installing your package. I can modify your

Re: [opnfv-tech-discuss] Hi, ollivier and  functest team, one test issue from community CI.

Listing upper-constraints doesn’t mean that it will be installed. It only enforces the right version. Functest doesn’t leverage on it then why should we force the installation in our container? It must be installed as any parser dependency when installing your package. I can modify your

[opnfv-tech-discuss] 答复: RE: Hi, ollivier and  functest team, one test issue from community CI.

python-openstackclient is already included in the file of upper-constraints.txt( https://git.opnestack.org/cgit/openstack/requirements/plain/upper-constrains.txt) which is used in functest/core dockefile. and i notice that all the other clients(nova,neutron,cinder.etc) are installed except

[opnfv-tech-discuss] [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] 答复: RE: Hi, ollivier and functest team, one test issue from community CI.

python-openstackclient is already included in the file of upper-constraints.txt( https://git.opnestack.org/cgit/openstack/requirements/plain/upper-constrains.txt) which is used in functest/core dockefile. and i notice that all the other clients(nova,neutron,cinder.etc) are installed except

Re: [opnfv-tech-discuss] Hi, ollivier and  functest team, one test issue from community CI.

Hello, It should have been added as dependency (requirements.txt) in your python package. I don’t want to list it in the Dockerfile to bypass your issue. Cédric De : opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] De la part de

[opnfv-tech-discuss] [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] RE: Hi, ollivier and functest team, one test issue from community CI.

Hello, It should have been added as dependency (requirements.txt) in your python package. I don’t want to list it in the Dockerfile to bypass your issue. Cédric De : opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] De la part de

[opnfv-tech-discuss] [OPNFV Helpdesk #45985] [linuxfoundation.org #45985] Hi, ollivier and functest team, one test issue from community CI.

I consider the following ci functest test result about parser project in master branch. ==={ Parser functest begin }== |= 1/4. Preparing VM image for parser... =| Download image cirros-0.3.5-x86_64-disk.img... ./functest_run.sh:

[opnfv-tech-discuss] Hi, ollivier and  functest team, one test issue from community CI.

I consider the following ci functest test result about parser project in master branch. ==={ Parser functest begin }== |= 1/4. Preparing VM image for parser... =| Download image cirros-0.3.5-x86_64-disk.img... ./functest_run.sh: