Hi Morgan, Thanks a lot! I will look into the solution discussed in the WIKI and feed back to you if there are further questions.
Best, Gabriel From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com] Sent: Friday, February 24, 2017 12:38 AM To: Yuyang (Gabriel); rexlee8...@gmail.com; Gaoliang (kubi); Jose Lausuch; chenjiankun; kumar rishabh; feng.xiao...@zte.com.cn; Cooper, Trevor; Mark.Beierl Cc: test...@lists.opnfv.org Subject: Re: [OPNFV] Danube testing group priorities status Hi Gabriel sorry for the late answer see comments in the mail /Morgan Le 17/02/2017 à 03:53, Yuyang (Gabriel) a écrit : Hi Morgan, Currently, two stress testcases are under review for integrating into community CI pipeline. * Gerrit: https://gerrit.opnfv.org/gerrit/#/c/28671/ * one testcase is the performance life-cyle for ping test while increasing the user number in parallel * the other is the baseline test for dataplane traffic while increate the data size for a VM pair One issue is that, we use kibana to show the results. However, in the currently Bottlenecks CI process, the docker for kibana is set up in community CI POD. That is, no public access to the kibana. Could you gives us some suggestions or help on how to make the testing results and graphs publicly accessible? regarding Kibana we decided to outsource the work to Bitergia (already in charge of code and infra reporting) but they will be able to start working in H2 so it will be short for Danube my reco would be to push your results in the database in the details sections of the testcase (so maybe create the testcase if it is not already the case) you can copy/paster the preformated dataset you used for Kibana in local so when ready, Bitergia could consume it directly through the test API and display it in https://opnfv.biterg.io as the dataset is already kibana compatible, it could be one of the first implementation for bitergia we initiated a wiki page to discuss with bitergia and give some examples, see https://wiki.opnfv.org/display/testing/Result+alignment+for+ELK+post-processing it is a bit strange to have an intermediate Kibana => test results => kibana but then everything is centralized (projects, cases, results) and we plan to use also the DB to build a test case catalog...so a central point is needed so that would be my option 1 option 2 would be the use of a Kibana on testresults.opnfv.org as we use to have but we got license issues for addons (also a reason we prefered to ousource this part of the work) Thanks, Gabriel ________________________________ 发件人: morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> [morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>] 发送时间: 2017年2月13日 17:15 收件人: rexlee8...@gmail.com<mailto:rexlee8...@gmail.com>; Gaoliang (kubi); Jose Lausuch; chenjiankun; kumar rishabh; feng.xiao...@zte.com.cn<mailto:feng.xiao...@zte.com.cn> 抄送: Cooper, Trevor; Yuyang (Gabriel); feng.xiao...@zte.com.cn<mailto:feng.xiao...@zte.com.cn>; test...@lists.opnfv.org<mailto:test...@lists.opnfv.org> 主题: [OPNFV] Danube testing group priorities status Hi, I recently sent a mail to Heather to give my view of the testing group priorities for Danube. As mentioned in the mail, it was only my view and it was not consolidated => I added a slot for the next weekly meeting. I will not be able to attend (I will be off from the 15th to the 22) Heather asked for a global statement on this. My suggestion would be something like: "The testing working group aimed to create more consistency accross the different test projects and extend the testing scope for Danube. The consistency deals with the creation of commons such as an umbrella documentation, a web landing page giving the scenario status at glance and a test case catalogue. The testing working group also defined stress tests to be run on the Danube solution in addition of the functional and qualification tests already provided." Feel free to comment/modify/suggest somehting else as a statement to Heather on the behalf of the testing group Regargind the status 1) Test consolidation - release testing landing page has been created but still work to do for a full integration (back-end/API + add scenario reporting from test project at the end of CI) => my estimation 50% chance to be ready for Danube on the 22 of March but not blocking for the release and could be achieved once we have something more stable + 1 or 2 weeks @Serena: do you think we could create the scenario (I think so) and push results ater CI run now? When it is OK on Functest (beta test) we could ask the other test project to use the API tu update the status - catalogue: the DB/test API is ready => work in progress on the front end => my estimation 70% for a basic catalogue (display cases/projects), 30% for the mechanism to customize test list @jack, Rex: what is you view on this estimation If nothing has been already started for the web front end, Kumar, an intern working on VNF catalogue submitted some code for this catalogue on releng => https://git.opnfv.org/releng/tree/utils/test/vnfcatalogue Could we reuse this catalogue for a test case catalogue? 2) Introduction of stress test some tests (2 of the 3 test cases we considered) have been performed (Yardstick/Bottleneck integration) results shown during weekly meeting this week documentation and CI integration work => my estimation 80% 3) Documentation - umbrella page for the working group done - cross review agreed by all the test projects => my estimation 100% Feel free to review my figures... /Morgan _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -- Morgan Richomme Orange/ IMT/ OLN/ CNC/ NCA/ SINA Network architect for innovative services Future of the Network community member Open source Orange community manager tel. +33 (0) 296 072 106 mob. +33 (0) 637 753 326 morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
