Gabriel and Kubi made an update recently on 2 stress tests that should be defined/available/documented for Danube
https://wiki.opnfv.org/display/meetings/TestPerf?preview=/2926539/9568872/Stress%20Testing%20Update.pptx https://wiki.opnfv.org/display/meetings/TestPerf?preview=/2926539/9569090/stress.mp4 I think we could imagine to run such tests during the plugfest for E we should elaborate a stress / robustness tests (with long duration tests) on the test working group /Morgan Le 02/03/2017 à 00:16, Cooper, Trevor a écrit : > > I support Al’s suggestion. As a goal for the Danube Plugfest I think > we should define at least one performance oriented test that we run > using different deployments / configurations … with an objective to > define a range of good vs bad performance in order to get started with > performance as a dimension of CVP. Plugfest is a good opportunity for > accelerating this IMO … we can discuss it in the Test Working Group > and try to make an initial proposal. > > > > /Trevor > > > > > > > > *From:*opnfv-tech-discuss-boun...@lists.opnfv.org > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of > *Raymond Paik > *Sent:* Wednesday, March 01, 2017 1:36 PM > *To:* MORTON, ALFRED C (AL) <acmor...@att.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest > planning call > > > > Al, > > > > I'm not sure if performance testing has been specifically excluded in > OPNFV Plugfests. A number of projects like Storperf participated in > past two Plugfests. Of course we can't get into things like Storperf > results were better on X vs. Y discussions, but there's no reason why > performance testing can't be done during the Plugfest. > > > > Thanks, > > > > Ray > > > > On Wed, Mar 1, 2017 at 5:24 AM, MORTON, ALFRED C (AL) > <acmor...@att.com <mailto:acmor...@att.com>> wrote: > > Hi Ray and Plugtesters, > > > > Apologies for missing Monday’s meeting > > (Jury Duty is a Civic responsibility, > > but makes attending some meetings impossible). > > > > Regarding test cases, I wonder if the Scope of > > testing has been decided, and whether a > > **performance-oriented** test case might be entertained > > this time? This topic has been out of scope in the > > previous Plugfests and ETSI CTI’s Plugtest™, AFAIK. > > > > It may still be too soon, but it’s worth asking now. > > > > regards, > > Al > > > > *From:*opnfv-tech-discuss-boun...@lists.opnfv.org > <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org > <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>] *On Behalf Of > *Raymond Paik > *Sent:* Wednesday, March 01, 2017 1:21 AM > *To:* opnfv-tech-discuss@lists.opnfv.org > <mailto:opnfv-tech-discuss@lists.opnfv.org> > *Subject:* [opnfv-tech-discuss] Quick follow-up from the Plugfest > planning call > > > > All, > > > > A few things after our call on Monday.... > > > > First, I realized that I had sent out a recurring weekly meeting > for Plugfest planning when this is supposed to be a bi-weekly > meeting. I will go ahead and cancel the current series and start > a new one that starts on March 13th. (so the upcoming meetings > are March 13/27 plus April 10th). Apologies for the thrash, but > you can also find the upcoming meeting info. > at > https://wiki.opnfv.org/display/EVNT/Plugfest+-+Danube+Release#Plugfest-DanubeRelease-PlugfestPlanningMeetings > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_EVNT_Plugfest-2B-2D-2BDanube-2BRelease-23Plugfest-2DDanubeRelease-2DPlugfestPlanningMeetings&d=DQMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=xOGhTlU5-EMqlnyLFtqPizrXQ-akx_8ep_lJEF5cyOM&s=hGHI9eHyvlhG1A_irMzzC6Tat-VZQAcFQ6t8KMYaa4k&e=> > > > > Second, I started a test cases page > at https://wiki.opnfv.org/display/EVNT/Danube+Plugfest+Test+Cases > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_EVNT_Danube-2BPlugfest-2BTest-2BCases&d=DQMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=xOGhTlU5-EMqlnyLFtqPizrXQ-akx_8ep_lJEF5cyOM&s=PQLI3Pwk95McmnXgKYUFxdh80nOSy3T6ARcoQx4zKBw&e=>. > > I followed the template from the last Plugfest, but as you can see > it's just a skeleton. I encourage everyone (esp. those who were > on the call yesterday) to contribute ideas/suggestions for what we > should focus on for the upcoming Plugfest. > > > > Finally, a reminder that the Plugfest is open to both members & > non-members of OPNFV. You can register > at https://www.regonline.com/OPNFVPlugfestApril2017 > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.regonline.com_OPNFVPlugfestApril2017&d=DQMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=xOGhTlU5-EMqlnyLFtqPizrXQ-akx_8ep_lJEF5cyOM&s=ecQNyyn30-voJn-s3qMzlmTxUcdUF4RcE3TfQ2oMAZ8&e=> > > > > > Thanks, > > > > Ray > > > > > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss -- 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 _________________________________________________________________________________________________________________________ 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