Hi Jack I submitted a patch for the reorganization of the reporting https://gerrit.opnfv.org/gerrit/#/c/24433/
see comments in line Le 16/11/2016 à 12:52, chenjiankun a écrit : > > Hi Morgan, > > > > Thank you for your clarification. This help a lot for me. > > > > To finish the test case selection work, I think maybe we should > firstly create a table for the scenario owners to modify the test case > configuration in the DB, and then offer an API for scenario owners to > modify this table. > yes it is planned I proposed a scenario collection in the Mongo DB that will collect the results + scenario owner + custom scenario It would mean also an evolution of the current testapi to includes methods to access/update these info I created a JIRA Epic with associated tasks https://jira.opnfv.org/browse/RELENG-159 > I am very willing to be in charge of creating those pages. I will > send you the design of those pages after I finish it and wait for your > opinion. > I assigned the JIRA to you:) > > > > As for the use of JIRA, I very agree with your idea. > > > > Since currently our static page are generated by Jinja2, and I think > it is better to separate html code from back-end code(such as python). > you will see in the patch, I created an html subdirectory I also created a display sub directory where I put the html + static pages created with JIRA > > So for me, I prefer Jinja2. By the way, I don’t know much about php. > jinja2 is fine > > > > I will keep focus on your patch. > > > > Regards, > > Jack Chan > > > > *发件人:*[email protected] <mailto:[email protected]> > [mailto:[email protected]] > *发送时间:*2016年11月14日21:41 > *收件人:*chenjiankun > *抄送:*[email protected] > <mailto:[email protected]>; Gaoliang (kubi); Kamsali, > Raghavendrachari > *主题:*Re: [OPNFV] testing meeting APAC slot > > > > Hi Jack > > see comments in the mail > > /Morgan > > Le 14/11/2016 à05:46, chenjiankun a écrit : > > Hi Morgan, > > > > I am Jack from yardstick. How is it going? > > fine and you? > > > > I have attended the last APAC Testing meeting. I really appreciate > your work in Testing view and Case Selection. > > > > In the meeting you replied to me that the Testing user’s case > configuration will be stored in the public mongoDB. > > maybe not the use, the scenario owner > the user should be able to get the config and do whatever he/she wants > with the config > we do not need to keept it stored unlike the custom configuration of > the scenario owner that is sued for the CI > > > So I think maybe we need a register/login mechanism to manage this > user’s configuration. What’s your point? > > yes I add in mind > a login/password for the scenario owner > for the other user a login with anonymous/anonymous or opnfv/opnfv > could be enough. > The only difference is that user will not have the right to push their > config into the DB > only the scenario owner will have this right > > Or can we store it in local DB? > > for users = local DB > for scenario owners = Mongo DB + localDB > note that the scenario owner list can be stored locally on our side > (so far not sure there are stored anyway except in the wiki...) > I imagined we coudl add that into the furture scenario tables in mongo > but according to infra patches the info, a DB is planned to store such > info, wait and see > in a first step a local DB would be enough > > > > I have been in charge of yardstick reporting and yardstick API and > have experience with web. > > cool I am too slow dealing with jinja2, js and web stuff.. > > > I really enjoy working in web. So I am wondering if there is anything > I can do in Testing view and Case Selection. > > I initiated some refactoring in releng (reporting) in order to have > more mutualization between functest and yardstick (and later qtip & > other test projects) > the goal is to implement the aggregated view I shared during the meeting > > I hope I would be able to push a patch before the end of the week. > The changes lead to structure changes > - dockerization > - reorganization of the subdirectories > - creation of util library for reporting that can be used by all the > projects > - mutualization images, css, js, ... > - sh script to run the cron > > probably too many things for one patch... > first step: produce yardstick and functest reporting page as it is > today + dockerization > > then I hope you coudl help me with > - css > - login page > - landing page > - test selection page > > as it is a task addressing many projects, I suggect to use the JIRA of > the projects we are used to work for and just use the tag reporting if > we want some JIRA aggregation > let's wait for the patch (I will put you and Rex in review) > then allocate tasks to work on the improvements > > note that some time ago, Ragha developped some web pages to > visualize/add the cases => > https://git.opnfv.org/cgit/releng/tree/utils/test/declaration > I have no strong view on the best framework assuming that currently > functest and yardstick static pages are generated through Jinja2 > what is your view? > > > > I am looking forward to your reply. > > > > Regards, > > Jack Chan > > > > *发件人:*[email protected] <mailto:[email protected]> > [mailto:[email protected]] > *发送时间:*2016年11月8日17:15 > *收件人:*Gaoliang (kubi); Lijun (Matthew); [email protected] > <mailto:[email protected]>; Yujun Zhang; Cooper, Trevor; Jose > Lausuch; [email protected] <mailto:[email protected]>; chenjiankun > *抄送:*[email protected] > <mailto:[email protected]> > *主题:*[OPNFV] testing meeting APAC slot > > > > Hi > > the next weekly meeting APAC slot is not clear. We indicate 2 dates in > the wiki: https://wiki.opnfv.org/display/meetings/TestPerf > > According to the calendar it is on the 9th but the agenda is declared > for the 10th... > > I assume it is the 9 8UTC => I modified the wiki > > if so for the moment we do not have chair/minutes and the agenda is > limited to the discussion on priority for Danube (I assume I will > introduce the topic during the TSC meeting today see attached > "Building a TSC vision for Danube" deck ) > > I also created some slides to illustrate what we have discussed in > Barcelona on the some aggregation actions to provide a consistent > Testing reporting view as well as web pages to allow scenario > owner/user to select their list of cases among all the test cases... > > I can present it but I have a constraints at 8h25 so I may not be able > to attend all the meeting > > Suggested agenda (do not hesitate to amend it on the wiki...) > > * Testing community Danube release landing page + scenario selection > proposals(15') > * Test community common goals > (20') https://etherpad.opnfv.org/p/TestCommunityGoals > * QTIP presentation (15') > * AoB (5') > > /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 > [email protected] <mailto:[email protected]> > _________________________________________________________________________________________________________________________ > > 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 [email protected] _________________________________________________________________________________________________________________________ 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 [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
