[opnfv-tech-discuss] 答复: [release][gambia] Intent to Participate in theOPNFV Gambia Release

HI, David. Parser will participate in the OPNFV Gambia Release. and 1. We intend to follow the traditional track. 尚小冬 shangxiaodong 原始邮件 发件人：DavidMcBride 收件人：TECH-DISCUSS OPNFV

[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] 答复: 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] 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] 答复: Re: [opnfv-project-leads] [release][fraser] MS2 - Test casedocumentation in the test case database - Nov 17

Hi David: There is not any new test case from parser project in release F, and following is the old: http://testresults.opnfv.org/test/api/v1/projects/parser/cases Thanks. 尚小冬 shangxiaodong 原始邮件 发件人： ; 收件人：

[opnfv-tech-discuss] 答复: [OPNFV Helpdesk #46018] [linuxfoundation.org #46018] Re: 答复: Re: 答复: Re: 答复: Re: About parser integration with functest usingthe lates container

The test result on jenkins is PASS which means parser integration with new functest framework is successful. Congratulations! and thanks for your coorporation! 尚小冬 shangxiaodong IT开发工程师 IT Development Engineer 虚拟化四部/无线研究院/无线产品经营部 NIV Dept. IV/Wireless Product R＆D

[opnfv-tech-discuss] 答复: Re: 答复: Re: 答复: Re: About parser integration with functest usingthe lates container

Hi, The docker image building has been failing in https://hub.docker.com/r/opnfv/functest-parser/builds/ since 7 days. but it is successful when build manually in my local env. Please have a look and fix it as soon as possible,thanks. Successfully installed certifi-2017.4.17

[opnfv-tech-discuss] 答复: Re: 答复: Re: 答复: Re: About parser integration with functest usingthe lates container

HI, It seems that the patch works. the test result of parser container is OK now in my local env. 尚小冬 shangxiaodong IT开发工程师 IT Development Engineer 虚拟化四部/无线研究院/无线产品经营部 NIV Dept. IV/Wireless Product R＆D Institute/Wireless Product Operation Division

[opnfv-tech-discuss] 答复: Re: 答复: Re: About parser integration with functest usingthe lates container

Hi,ollivier. After updating your patch about Rally error, i built the functest-parsr image and tested it locally, it still doesn't pass step of creating rally deployment, the log is shown as following: 2017-09-19 07:02:50,682 - functest.ci.prepare_env - INFO -

[opnfv-tech-discuss] 答复: [OPNFV Helpdesk #45794] [linuxfoundation.org #45794] Re: 答复: Re: About parser integration with functest usingthe lates container

Would you remind me if you fix the issue? i'll check the integration with parser. thanks. Another issue, how to create the parser container image(maybe other feature project container building are similar) is need to be considered. If patches are merged in parser, the parser image need to be

[opnfv-tech-discuss] 答复: Re: About parser integration with functest usingthe lates container

Yes, the image size increase about 100MB. Maybe it's a solution to install tempest directly when building parser container. But i wonder why it's neccessary to call tempest in parser container? 尚小冬 shangxiaodong IT开发工程师 IT Development Engineer 虚拟化四部/无线研究院/无线产品经营部 NIV Dept.

[opnfv-tech-discuss] 答复: Re: 答复: Re: 答复: Re: About parser in OPNFV release E

Hi，David. Thanks for remiding. Currently parser mainly is focusing on bugs fixes(most of bugs feeded back from onap) , the others are optimizations about verigraph(subproject under parser). 尚小冬 shangxiaodong IT开发工程师 IT Development Engineer 虚拟化四部/无线研究院/无线产品经营部 NIV Dept. IV/Wireless

[opnfv-tech-discuss] 答复: Re: 答复: Re:  About parser in OPNFV release E

Thanks Serina. According our planning, we must finish the items with priority 1(the highest priority), and then the items with priority 2 or 3. Because in release E, parser team has a top priority task: release a parser version for the ONAP community, in which Modeling project and VF-C

[opnfv-tech-discuss] 答复: Re:  About parser in OPNFV release E

HI, riccardo and serena. There was external email authorization issue since i switched to a new R department from June this year，may be some emails have been missed for you. Currently parser in MS7, is there any update from your side about verigraph module? If you have any question