[opnfv-tech-discuss] [qtip] Agenda for Weekly Meeting

Please feel free to add topics you wish to discuss. QTIP project weekly meeting on 2016-11-02 online chatting: irc://#opnfv-qtip@freenode screen sharing: https://zoom.us/j/914417686 Action followup - #done @yujunz resend PyCharm keys to @serena - #done @yujunz to promote at least one more

Re: [opnfv-tech-discuss] [opnfv-project-leads] Security Vulnerability Classification in OPNFV JIRA

disclosure' > approach. > > More details on how to sign up are on the security group wiki page: > https://wiki.opnfv.org/display/security/Security+Vulnerability+Classification+in+OPNFV+JIRA > > Big thanks for Mark Beierl for setting this up, and the support from Yujun > Zhan

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Planning of D release documentation

The epic name is quite long. Since it is all under OPNFV namespace, we may omit the prefix and use some abbreviation. e.g. Danube docs -- Yujun On Tue, Nov 1, 2016 at 8:18 PM Sofia Wallin wrote: > Hi Maryam, > > Depending on which documents you plan contributing to, create one or more > new sto

Re: [opnfv-tech-discuss] Graduation reviews discussion

I think there would be a different expectation for "mature" projects. It is quite difficult to define "fully functional" and "stable" since the projects never stop evolution even after mature. >From a developer's view, a mature project can be judged from 1. regular release cycle 2. test co

Re: [opnfv-tech-discuss] OPNFV on Github

Looks great! Can we just disable "issue", "pull request" and "wiki"? And it would be good to provide project link in the description line. On Fri, Nov 4, 2016 at 4:07 AM Trevor Bramwell < tbramw...@linuxfoundation.org> wrote: Hi Luke, et al., The OPNFV Gerrit repos should now exist under http

[opnfv-tech-discuss] [qtip] Agenda for Weekly Meeting

Please note that it has been rescheduled to *UTC0800 every Monday* to avoid confliction with TestPerf APAC meeting. And we shall use only IRC. This change is affecting all the future meetings. See agenda as below and feel free to add new topics you wish to talk. https://etherpad.opnfv.org/p/qtip

Re: [opnfv-tech-discuss] [Doctor] Reset Server State and alarms in general

ay, October 04, 2016 3:48 PM > *To:* Juvonen, Tomi (Nokia - FI/Espoo) ; Yujun > Zhang ; opnfv-tech-discuss@lists.opnfv.org > > > *Subject:* RE: [opnfv-tech-discuss] [Doctor] Reset Server State and > alarms in general > > > > Tomi, > > > > > > So,

[opnfv-tech-discuss] [infra] etherpad down?

I got 502 Bad Gateway error while accessing https://etherpad.opnfv.org/ Is it down? -- Yujun ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [infra] etherpad down?

ent an email to opnfv-helpdesk so that a > ticket has been created > > Thanks, > > Ray > > On Sun, Nov 6, 2016 at 5:20 PM, Yujun Zhang > wrote: > > I got 502 Bad Gateway error while accessing https://etherpad.opnfv.org/ > Is it down? > > -- > Yujun >

Re: [opnfv-tech-discuss] [VES] Team Meeting Schedule

Which week day is the meeting? Not mentioned in the original message. On Wed, Nov 2, 2016 at 12:17 AM SULLIVAN, BRYAN L wrote: > FYI: OPNFV MANO WG Meeting Details > Meeting Times: Weekly 7 AM PDT (15:00 UTC) this week and 7 AM PST (14:00 > UTC) after daylight changes next week > ___

Re: [opnfv-tech-discuss] [OPNFV] testing meeting APAC slot

Hi, all Thank Morgan for bringing QTIP to the agenda. May I propose to postpone it to next week? I haven't get the presentation ready yet :-(. It is too hurry for tomorrow. About the APAC slot, it is even more confusing for Dec because Dec 1st is Thursday. How about modifying the rule as *2nd m

Re: [opnfv-tech-discuss] [OPNFV] testing meeting APAC slot

lot should be the 14th of December (not > the 1st of December...) > > Maybe an alignment on the day (always Thursday) would also a good idea... > > /Morgan > > > Le 08/11/2016 à 10:23, Yujun Zhang a écrit : > > Hi, all > > Thank Morgan for bringing QTIP to t

[opnfv-tech-discuss] [doctor] performance profile design spec

Hi, doctors, Would you spare sometime to review the spec for performance profile[1]? The motivation for this feature is described in JIRA: DOCTOR-72 [2] Please feel free to give comments. [1]: https://gerrit.opnfv.org/gerrit/#/c/23963/ [2]: https://jira.opnfv.org/browse/DOCTOR-72 __

[opnfv-tech-discuss] [opnfvdocs] documentation landing page

Folks, @Morgan mentioned a landing page for test results during yesterdays weekly meeting. I wonder if there is any similar plan for documentation. Currently the published documents are available on artifacts site. But it seems there is no landing page giving an table of all available contents an

[opnfv-tech-discuss] [qtip] Attention required for project folder structure

Dear qtip runners, We planned a folder reorganization[1] in this sprint. And it is quite important to complete it ASAP so other tasks won't get blocked. So I propose to merge a patch set[2] to setup the base folder structure. The existing features might get broken. But I believe it will be easie

Re: [opnfv-tech-discuss] OPNFV meeting pages - info on updates

Looks good. But I doubt there is usually another copy of meeting information under each project so the index is likely out of sync. Secondly, it is easy to search for one dedicated meeting in this page, but hard to find out an available time slot for new meetings. In this case, I would prefer the

[opnfv-tech-discuss] [qtip] Agenda of Weekly Meeting on 2016-11-14

https://etherpad.opnfv.org/p/qtip-meetings-2016-11-14 QTIP project weekly meeting on 2016-11-14 time: UTC0800 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - #open @zhihui to do some research on dovetail on how to consume test data from YardSti

[opnfv-tech-discuss] [qtip] sprint QTIP-D2 update and QTIP-D3 proposal

QTIP contributors, Would you please update the status of JIRA tickets in current sprint[1]? It is supposed to be completed last Friday. To get the sprint cycle synchronized with weekly meeting, I would propose we delay QTIP-D2 to end of today and QTIP-D3 will be started tomorrow. Please also joi

[opnfv-tech-discuss] [qtip] QTIP-D2 sprint report

Hi all qtip runners QTIP-D2 is completed with 6 out of 8 tasks done. Thanks to everyone's contribution we are one or two steps closer to our release target - finished directory reorganization - setup script for installation with pip See sprint report[1] for details and participate in the

[opnfv-tech-discuss] [qtip] sprint QTIP-D3 started

QTIP runners, Sprint QTIP-D3 is kicked off today. It will last for 15 working days. We shall focus on - architecture design - yardstick integration - compute QPI - internship program Please feel free to claim the tasks in current sprint[1]. Thank you. [1]: https://jira.opnfv.org/sec

Re: [opnfv-tech-discuss] [dovetail] candidate of report content

Is it a log message or final report for end user? If it is targeting end user, a user friendly name for test cases might be prefered, e.g. aggregating the result, short name. - [2/3] objective - [pass] bulk create delete network - [fail] bulk create delete port - [pass] bulk create delete s

Re: [opnfv-tech-discuss] [dovetail] candidate of report content

On Wed, Nov 16, 2016 at 10:27 AM Leo Wang wrote: > Hi Yujun, Chris > > I suggest that add a segment for each test case in their definition > scripts to explicitly tell this info > then the tool can generate the report in a general way > +1 for auto generation from test case description __

Re: [opnfv-tech-discuss] [dovetail] candidate of report content

On Wed, Nov 16, 2016 at 10:27 AM Leo Wang wrote: > Hi Yujun, Chris > > I suggest that add a segment for each test case in their definition > scripts to explicitly tell this info > then the tool can generate the report in a general way > +1 for auto generation from test case description _

Re: [opnfv-tech-discuss] 答复: [fuel][CI]Fuel deployment CI job is failed on ZTE PODs

It seems the target site is forcing a redirection to https. -L will work. An alternative solution is downloading from the target link, i.e. https://build.opnfv.org/artifacts.opnfv.org/fuel/latest.properties On Wed, Nov 16, 2016 at 3:00 PM wrote: > I think I find the reason. > ZTE PODs use URL

[opnfv-tech-discuss] [doctor] question on code refactoring task (DOCTOR-71)

Hi, doctors, Carlos has started code refactoring of the test script[1]. It looks good to separate common function and installer specific function into different modules and improve the readability of main script.[2][3] I just have some concerns about the future complexibility of this test script.

Re: [opnfv-tech-discuss] [doctor] question on code refactoring task (DOCTOR-71)

openzero-zte/doctor_test_refactor>* > > BR. > dwl > > > > > *Yujun Zhang >* > 发件人: opnfv-tech-discuss-boun...@lists.opnfv.org > > 2016-11-17 09:48 > > 收件人 > TECH-DISCUSS OPNFV > > 抄送 > 主题 > [opnfv-tech-discuss] [doctor] question on code

[opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-11-21

https://etherpad.opnfv.org/p/qtip-meetings-2016-11-21 QTIP project weekly meeting on 2016-11-21 time: UTC0800 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - @zhihui to do some research on dovetail on how to consume test data from YardStick thi

Re: [opnfv-tech-discuss] 答复: [doctor] question on code refactoring task (DOCTOR-71)

ease see below my reply. > > > > Carlos > ... > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [ > mailto:opnfv-tech-discuss-boun...@lists.opnfv.org > ] *On Behalf Of * > dong.wenj...@zte.com.cn > > > *Sent:* 17 November 2016 05:34 > *To:*

[opnfv-tech-discuss] [doctor] Danube plan overview

Hi doctors, I'm reviewing the requirement document for an internal presentation. There is a release plan for Arno and it looks good[1]. We have already sorted out the working items for Danube release, but it would be better if we can have an overview about the goals we want to achieve. @Ryota, w

Re: [opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-11-21

ommitters. Cheers to you. > > > > Wenjing > > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Yujun Zhang > *Sent:* Thursday, November 17, 2016 10:18 PM > *To:* TECH-DISCUSS OPNFV > *Sub

[opnfv-tech-discuss] [qtip] Agenda for weekly meeting

https://etherpad.opnfv.org/p/qtip-meetings-2016-11-28 QTIP project weekly meeting on 2016-11-28 time: UTC0800 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - @all send @yujunz google account for document sharing and review Topics - project up

Re: [opnfv-tech-discuss] ##freemail## [doctor] Danube plan overview

hive. > > > BR, > Ryota > > > -Original Message- > > From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] > > Sent: Wednesday, November 23, 2016 3:59 PM > > To: TECH-DISCUSS OPNFV > > Cc: Mibu Ryota(壬生 亮太) > > Subject: ##freemail## [doctor]

Re: [opnfv-tech-discuss] [qtip] Agenda for weekly meeting

Postponed to this Wednesday 16:00, Nov 30th. Sorry for late notification. -- Yujun On Fri, Nov 25, 2016 at 2:06 PM Yujun Zhang wrote: > https://etherpad.opnfv.org/p/qtip-meetings-2016-11-28 > > QTIP project weekly meeting on 2016-11-28 > time: UTC0800 > irc://#opnfv-qtip@f

[opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-11-30

Deferred from 11-28 QTIP project weekly meeting on 2016-11-30 time: UTC0800 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - @all send @yujunz google account for document sharing and review Topics - project update - contact page: https://

[opnfv-tech-discuss] [infra] "gate" job BEFORE merging

During the code refactoring in QTIP project, I found it easily to get things broken[1]. And it can only be detected during the daily integration AFTER merge. Is it possible that we have a gate job to detect such failure before a patchset get merged? I remember it may have been discussed before. C

Re: [opnfv-tech-discuss] [infra] "gate" job BEFORE merging

p has it so you need to decide what > other checks you want to have and adjust the job accordingly. > > https://build.opnfv.org/ci/view/qtip/job/qtip-verify-master/616/console > > /Fatih > > On 30 Nov 2016, at 04:36, Yujun Zhang wrote: > > During the code refactoring

Re: [opnfv-tech-discuss] [infra] "gate" job BEFORE merging

:15 PM Fatih Degirmenci < > fatih.degirme...@ericsson.com> wrote: > > Hi, > > The purpose of verify jobs is this. Qtip has it so you need to decide what > other checks you want to have and adjust the job accordingly. > > https://build.opnfv.org/ci/view/qtip/job/qtip-veri

Re: [opnfv-tech-discuss] [infra] "gate" job BEFORE merging

led one. > > I'm aware that this is probably not the answer you're looking for but this > is what we have with the current tooling. I hope openstack releases stable > zuul v3 soon so we try it out. > > [1] http://docs.openstack.org/infra/zuul/gating.html#dependent-pipeline

[opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-12-05

https://etherpad.opnfv.org/p/qtip-meetings-2016-12-05 QTIP project weekly meeting on 2016-12-05 time: UTC0800 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - #done yujunz fix permission issues of contact page - shared in https://goo.gl/aGJN5n

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

Nice job! One comment inline. On Sun, Dec 4, 2016 at 3:55 PM Ryota Mibu wrote: > Hi, > > > Doctor CI jobs are now available and I confirmed those returns green > lights with current codes on the master branch. > > Reviewers, please check the CI results before merging a patch set. So the verif

[opnfv-tech-discuss] [doctor] performance profiler

Doctors, Please find the slides[1] for the background of performance profiler[2] as requested in gerrit review[3] and last meeting[4]. Feel free to give comments. [1]: https://goo.gl/98Osig [2]: https://jira.opnfv.org/browse/DOCTOR-72 [3]: https://gerrit.opnfv.org/gerrit/#/c/25081/ [4]: http://m

[opnfv-tech-discuss] [qtip] Sprint Report QTIP-D3

Thanks to all contributors' effort, we accomplished many goals in this sprint 1. kicked off the first internship program in QTIP 2. completed the compute QPI design specification 3. resumed verification job is after framework refactoring Though there is some delay on YardStick integration spec an

[opnfv-tech-discuss] [qtip] Sprint QTIP-D4 started

QTIP runners, Ready for the fourth sprint in Danube? Let's go! In this sprint, we shall focus on 1. YardStick integration 2. CLI evolution (intern project) 3. Runner module refactoring Check the active sprint page[1] for details [1]: https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=135

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

> *From:* Carlos Goncalves [mailto:carlos.goncal...@neclab.eu] > *Sent:* Monday, December 05, 2016 11:52 AM > *To:* Yujun Zhang ; Mibu Ryota(壬生 亮太) < > r-m...@cq.jp.nec.com>; opnfv-tech-discuss@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss] [doctor] doctor CI now available &

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

On Thu, Dec 8, 2016 at 6:41 AM Ryota Mibu wrote: Yujun, Yes, but I can remove it if some can provide POD(s) for these CI jobs. Maybe I can put document how to build such pod. That would be great. Let me see if we can request some resource from ZTE lab for Doctor CI. _

[opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-12-12

Please note that the it has been rescheduled to UTC0730 from now on. https://etherpad.opnfv.org/p/qtip-meetings-2016-12-12 QTIP project weekly meeting on 2016-12-12 time: UTC0730 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - all review CLI inte

[opnfv-tech-discuss] [qtip][yardstick] co-meeting about integration in Danube

Dear testers, We shall hold a co-meeting between QTIP and Yardstick team to discuss about the integration of these two projects in Danube release. Please check the logistical information as below and join us if you are interested. See agenda in https://etherpad.opnfv.org/p/qtip-yardstick Topic:

[opnfv-tech-discuss] Fwd: [qtip][yardstick] co-meeting about integration in Danube

*Correction!* Time: Thursday, Dec 15, 2016 UTC0030 -- Forwarded message - From: Yujun Zhang Date: Tue, Dec 13, 2016 at 9:49 AM Subject: [qtip][yardstick] co-meeting about integration in Danube To: TECH-DISCUSS OPNFV , test-wg < test...@lists.opnfv.org> Cc: Gaoliang (D)

Re: [opnfv-tech-discuss] committer list maintainance

I think there is no mandatory rule for PTL to attend TSC meeting in order to complete the removal process. At least, I never did that before. On my side, I have tried to contact several inactive committers to ask for their willingness and most of them replies politely to explain why. And we have a

Re: [opnfv-tech-discuss] Taking Tech Discuss to the Forums

It seems this new forum requires new account. Would it possible to enable single sign on with existing account? On Wed, Dec 14, 2016 at 4:25 PM Ash wrote: > All, > > To help make discussions easier between time zones, searchable,linkable, > etc., we've put up a new Tech Discuss Forum

[opnfv-tech-discuss] [doctor] subtasks created for performance profiler

Hi, Ryota I have split the task into several working items in JIRA[1]. Some of them may not catch up with Danube release as I explained in last meeting [2]. Shall I modify the `Fix Version/s` field now or wait till release window to update them? [1]: https://jira.opnfv.org/browse/DOCTOR-72 [2]:

Re: [opnfv-tech-discuss] [qtip][yardstick] co-meeting about integration in Danube

book another joint meeting next week 2. yujunz 1. kubi001 yujunz continue discussion on etherpad People present (lines said) 1. yujunz (41) 2. kubi001 (7) 3. Mingjiang1 (5) 4. collabot (4) 5. zhihui (1) 6. JackChan (1) On Tue, Dec 13, 2016 at 9:54 AM Yujun Zhang

[opnfv-tech-discuss] [all] TestPerf EcoSystem diagram now editable

Hi testers, I have replaced the previous image of TestPerf EcoSystem with an editable diagram in the overview section of testperf wiki page[1]. Please review and amend if something is missing. https://wiki.opnfv.org/display/testing/TestPerf ___ opnfv-te

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

On Thu, Dec 15, 2016 at 9:20 PM Jose Lausuch wrote: > Hi Yujun, > > > > That looks good. It’s a great idea to have diagrams and pictures editable > so that we can change it when we see the need. > Sure. Manage the images like code. > Maybe we should apply the same for the other pictures/graphs.

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

structure and the key words of each area. Thanks. > > > > Regards, > > Kubi > > > > *发件人:* test-wg-boun...@lists.opnfv.org [mailto: > test-wg-boun...@lists.opnfv.org] *代表 *Yujun Zhang > *发送时间:* 2016年12月15日 21:05 > *收件人:* test-wg > *抄送:* TECH-DISCUSS OPNFV >

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

Replies inline On Thu, Dec 15, 2016 at 10:20 PM Gaoliang (kubi) wrote: > Hi Yunjun, > > > > Thanks for your work to make the TestPerf Ecosystem image editable. But I > ‘m a little confused with the rule of the TestPerf EcoSystem Diagram > modification. > > It seems that you have modified the Te

[opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-12-19

@Kubi, @Rex, you are welcomed to join this meeting since the first and main topic would be *yardstick integration*. Thanks a lot for the answers on etherpad page. @zhihui, please review the answers and let me know whether it is clear enough for us to create a proposal on how to implement it. QTIP

Re: [opnfv-tech-discuss] committer list maintainance

months => raise an alarm to TSC to clean also the project > > /Morgan > > > > Le 14/12/2016 à 08:31, joehuang a écrit : > > +1000 for this "I never think it is a shame to leave a project, since it > is normal that people move on to a new target and didn't ha

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

See my replies inline. On Fri, Dec 16, 2016 at 3:43 PM Gaoliang (kubi) wrote: > Hi Yujun, > > > > it may delivers misleading information to the whole community. > This is exactly my motivation of the modification. I hope we can find out the original agreement so we can know why it is deliveri

Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

On Fri, Dec 16, 2016 at 3:36 AM Raymond Paik wrote: > All, > > Next step is to see if there's a way to streamline the meetings calendar > on the upper right corner. If anyone has good ideas/suggestions, please > let me know. > We use the list view in TestPerf meeting calendar[1]. Not sure if th

Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

Hi Ray, I have similar question. Since I want to keep the meeting information in QTIP front page to give the visitor all essential information on the first glance. Can we link from the index page to a daughter page like https://wiki.opnfv.org/display/functest/Functest+Meeting or an anchor like

Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

oid > maintaining a Promise calendar and the “OPNFV Team Meetings” calendar. > > Best regards, > Gerald > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [ > mailto:opnfv-tech-discuss-boun...@lists.opnfv.org > ] *On Behalf Of *Yujun Zhang > *Sent:* Freitag, 16. Dezembe

Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

(AL) 于2016年12月18日 周日00:17写道： > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Yujun Zhang > *Sent:* Saturday, December 17, 2016 8:10 AM > *To:* Beierl, Mark; Kunzmann, Gerald > *Cc:* opnfv-tech-di

Re: [opnfv-tech-discuss] [qtip] Agenda for weekly meeting 2016-12-19

4# or +16465588656,834597864# Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) Meeting ID: 834 597 864 International numbers available: https://zoom.us/zoomconference?m=oi98SXg-voXc3EAzJLjm_k3Ja5cqdVFx On Fri, Dec 16, 2016 at 9:32 AM Yujun Zhang wrote: > @Kubi, @Rex,

Re: [opnfv-tech-discuss] [Opnfv-security] Security checks at Gate

Luke, I remember that Fatih once mentioned that there are no gates in OPNFV CI yet. So you are talking about some additional verification jobs enforced on each commit. Or it is something like the current daily/weekly job. Could you help to clarify it? On Mon, Dec 19, 2016 at 7:39 PM Luke Hinds

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

=blob;f=docs/com/img/OPNFV_testing_group.png;h=4b8c2c053e0143b1a9abc7e54fd9e7671ccfcee8;hb=HEAD > > Thanks, > > Kubi > > > > > > *发件人:* Yujun Zhang [mailto:zhangyujun+...@gmail.com] > > *发送时间:* 2016年12月16日 16:43 > > *收件人:* Gaoliang (kubi); test-wg > *抄送:* TECH-D

[opnfv-tech-discuss] [qtip] Weekly Meeting Agenda 2016-12-26

https://etherpad.opnfv.org/p/qtip-meetings-2016-12-26 QTIP project weekly meeting on 2016-12-26 time: UTC0730 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - @zhihui to investigate how to detect yardstick finishing - @zhihui to propose a desi

[opnfv-tech-discuss] [qtip] Sprint QTIP-D4 => QTIP-D5

QTIP runners, Sprint QTIP-D4 is completed with 7 out of 15 issues closed. See sprint report[1] for details In next sprint, we shall focus on 1. Create Collector and Reporter PoC 2. API server requirements and plan for Danube 3. CLI for implemented modules 4. Yardstick integration pro

Re: [opnfv-tech-discuss] [dovetail]Dovetail encryption for report

I thought report is normally public to read. But it is important to have digital signatures so that the content can be trusted. The algorithm is similar to encryption. My two cents. On Tue, Dec 27, 2016 at 10:38 AM Leo Wang wrote: > Hi all > > The report in plain-text is vulnerable from malici

Re: [opnfv-tech-discuss] [dovetail]Dovetail encryption for report

On Tue, Dec 27, 2016 at 3:54 PM Leo Wang wrote: > As i mentioned , someone did show their concern on the security of test > report, so dovetail will provide this optional parameter for them > > digital signature is used to identify the source and its integrity, and > surely it can raise the secur

[opnfv-tech-discuss] [qtip] Cancelled weekly meeting on 2017-01-02

QTIP runners, Next weekly meeting on 2017-01-02 is cancelled for New Year Holiday. Happy 2017 to all \o/ -- Yujun ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg] unit test strategy in test projects

Some of my ideas on unit test inline On Wed, Jan 4, 2017 at 1:26 AM wrote: > Hi > > First of all, all the best for 2017! > > we got an interesting discussion on unit tests in Functest this morning > and more specifically on how we should use them. > > see > > http://ircbot.wl.linuxfoundation.org

Re: [opnfv-tech-discuss] [test-wg] unit test strategy in test projects

Serena, Maybe the term `interface` fits better here. I agree with you that the target of unit test in Python is *module*. We ensure with unit test the existing interfaces of the module are not broken by new code and new interfaces implemented work as expected. The private methods (which does not

Re: [opnfv-tech-discuss] [test-wg] unit test strategy in test projects

somewhere or add more points if needed. Link: https://docs.google.com/presentation/d/1vFVLP1SRPaKL3b90wTlc6NuE6zyf5Q4FhbxcN12W4IA/edit?usp=sharing Thanks On Wed, Jan 4, 2017 at 12:12 PM, Yujun Zhang wrote: Serena, Maybe the term `interface` fits better here. I agree with you that the targ

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

rf Controller performance -> CPerf Performance trend analysis -> Bottleneck /Trevor *From:* Yujun Zhang [mailto:zhangyujun+...@gmail.com] *Sent:* Wednesday, December 21, 2016 6:36 AM *To:* Gaoliang (kubi) ; test-wg < test...@lists.opnfv.org> *Cc:* TECH-DISCUSS OPNFV ; Morgan Richom

[opnfv-tech-discuss] [qtip] Agenda for Weekly Meeting 2017-01-09

https://etherpad.opnfv.org/p/qtip-meetings-2017-01-09 copy to opnfv-user list since the main topic would be *intern bootcamp* QTIP project weekly meeting on 2017-01-09 time: UTC0730 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - zhihui to invest

[opnfv-tech-discuss] [infra][doctor] experimental trigger not working

Hi, infra experts We want to introduce a jenkins job trigger for experimental changes[1] A trigger is created for doctor project[2], but it seems not working as expected. When a new comment "check experimental" is added[3], no job is triggered[4] as expected. *Could anyone give some hint on how

Re: [opnfv-tech-discuss] [infra][doctor] experimental trigger not working

branch: '{branch}' > > > > or move trigger into job body rather than using macro. > > > > /Fatih > > > > *From: * on behalf of Yujun > Zhang > *Date: *Friday, 6 January 2017 at 08:02 > *To: *"opnfv-tech-discuss@lists.opnfv.org" &l

Re: [opnfv-tech-discuss] [infra][doctor] experimental trigger not working

y the > keyword check-experimental. > > If the values are not passed to the macros, they will not be updated by > jjb and stay as they are - {project} and {branch}. > > > > We verify jjb updates using jjb but this type of errors are not caught by > it. > > > > /Fa

Re: [opnfv-tech-discuss] [infra][doctor] experimental trigger not working

ut this type of errors are not caught by > it. > > > > /Fatih > > > > *From: *Yujun Zhang > *Date: *Friday, 6 January 2017 at 12:46 > *To: *Fatih Degirmenci , " > opnfv-tech-discuss@lists.opnfv.org" > *Subject: *Re: [opnfv-tech-discuss] [infra][doctor] experiment

[opnfv-tech-discuss] [qtip] Updated Agenda for Weekly Meeting 2017-01-09

atus https://build.opnfv.org/ci/view/qtip/ - new tasks in JIRA https://jira.opnfv.org/issues/?filter=11198 - AOB - On Fri, Jan 6, 2017 at 2:10 PM Yujun Zhang wrote: > https://etherpad.opnfv.org/p/qtip-meetings-2017-01-09 > > copy to opnfv-user list since the main topic wou

[opnfv-tech-discuss] [pinpoint] project release plan

Hi, Adi We are looking for an RCA service in OPNFV. It seems pinpoint[1] is dedicated for this purpose. May I have more information on the project progress and release plan? [1]: https://wiki.opnfv.org/display/pinpoint -- Yujun ___ opnfv-tech-discuss

Re: [opnfv-tech-discuss] [pinpoint] project release plan

nfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Yujun Zhang > *Sent:* Monday, 09 January, 2017 03:41 > *To:* TECH-DISCUSS OPNFV; Adi Molkho > *Subject:* [opnfv-tech-discuss] [pinpoint] project release plan > > > > Hi

Re: [opnfv-tech-discuss] [pharos] Including Documentation on the Wiki

An alternative solution is to use markdown instead of rst. Confluence supports Markdown inclusion quite well. See example page in QTIP[1][2] [1]: https://wiki.opnfv.org/display/qtip/Contributing [2]: https://git.opnfv.org/qtip/tree/CONTRIBUTING.md On Tue, Jan 10, 2017 at 8:37 AM Trevor Bramwell

Re: [opnfv-tech-discuss] Follow-up on the meetings wiki page discussion

Done for QTIP. See https://wiki.opnfv.org/display/meetings/QTIP Please check if this is the expected result. [image: Screen Shot 2017-01-11 at 3.38.32 PM.png] × Yujun On Wed, Jan 11, 2017 at 2:02 PM Raymond Paik wrote: > All, > > Following up on our conversation from the TSC call... > > As di

[opnfv-tech-discuss] [qtip] Agenda for Weekly Meeting 2017-01-16

https://etherpad.opnfv.org/p/qtip-meetings-2017-01-16 QTIP project weekly meeting on 2017-01-16 time: UTC0730 irc://#opnfv-qtip@freenode index: https://etherpad.opnfv.org/p/qtip-meetings Action followup - all review yardstick-qtip integration proposal if interested - Taseer update Prequis

Re: [opnfv-tech-discuss] [dovetail]Dovetail encryption for report

up and 3rd party lab, > > so would you guys take a time to review this idea? > > > Thank you both in advance ! > > > I’ve update the diagram with digital signature, and both encryption and > digital signature can be optional to fit in user’s demand > > for details,

Re: [opnfv-tech-discuss] [dovetail]Dovetail encryption for report

have a solution for that. On Jan 13, 2017, at 16:42, Yujun Zhang wrote: Based on my limited knowledge, a user can only sign the result with *his own* private key. It is not possible for him to modify a report signed by let's say *OPNFV release bot* and kept the original signature. On Fri, J

Re: [opnfv-tech-discuss] [opnfv-tsc] For the "quarterly projects health metrics" discussion on the TSC call

It seems some project title is missing in the diagram, e.g. armband, barometer, ... [image: Screen Shot 2017-01-17 at 8.48.55 AM.png] × [image: Screen Shot 2017-01-17 at 8.49.54 AM.png] On Tue, Jan 17, 2017 at 7:15 AM Raymond Paik wrote: > All, > > One of the agenda topics for this week's call

Re: [opnfv-tech-discuss] [opnfv-tsc] For the "quarterly projects health metrics" discussion on the TSC call

els... Let me know if > that's not the case. > > Thanks, > > Ray > > On Mon, Jan 16, 2017 at 4:51 PM, Yujun Zhang > wrote: > > It seems some project title is missing in the diagram, e.g. armband, > barometer, ... > > [image: Screen Shot 2017-01-17 at 8.48.5

[opnfv-tech-discuss] [qtip] Sprint QTIP-D5 to Sprint QTIP-D6

QTIP runners, We are moving forward to QTIP-D6 which shall focuses on - PoC for architecture evolution - compute QPI implementation - CLI evolution following the architecture changes - Starting API server design and implementation And possibly - integration with Yardstick In the last sprint QT

Re: [opnfv-tech-discuss] [Doctor] reset server state performance issues

+1 for notification from inspector. For inspector with RCA like Vitrage, it is quite straight forward to deduce the VM error from Host failure. Juvonen, Tomi (Nokia - FI/Espoo) 于2017年1月17日 周二18:52写道： > In my current APEX testing environment Doctor use case takes average about > 290ms (from detect

Re: [opnfv-tech-discuss] [doctor] CFP planning for OpenStack Summit and ONS

Quite interested in the performance topic and I'm willing to join the presentation a co-speaker :-) Updated in the etherpad. -- Yujun On Wed, Jan 18, 2017 at 12:37 AM Ryota Mibu wrote: > Hi, > > > As I mentioned, I created an etherpad page to have discussion for our CFPs. > > https://etherp

[opnfv-tech-discuss] [intern] bootcamp for intern projects

The first intern student in QTIP, Taseer Ahmed has created a wiki page[1] as an orientation for intern *candidates* of OPNFV QTIP project *before* application. Forwarded to mailing list since it could also be useful for other projects. [1]: https://wiki.opnfv.org/display/qtip/Bootcamp __

[opnfv-tech-discuss] [qtip] Cancelled weekly meeting on Jan 23 and Jan 30

QTIP runners, Next two weekly meetings will be cancelled for Spring Festival in China. See you on Feb 6th. -- Yujun ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [qtip][yardstick] Q&A on integration

Dear all I reviewed the meeting log[1] and it seems we have several questions to clarify. Feel free to comment. 1. how to integrate option 1: as a server like original proposal[2] option 2: as a module Both are OK to me, if it is YardStick's team to decide to integrate as a module, we need to r

Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

I think it is technically feasible. We added an experimental trigger for doctor project not long ago[1]. The trigger is similar to your requirement. [1]: https://gerrit.opnfv.org/gerrit/#/c/26839/4/jjb/global/releng-macros.yml On Tue, Jan 24, 2017 at 12:31 PM Chigang (Justin) wrote: > Hi, > >

Re: [opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP monitoring

That would be an interesting topic. We have already started something on inspector[1]. We may create one for monitor as well. [1]: https://jira.opnfv.org/browse/DOCTOR-73 On Wed, Jan 25, 2017 at 1:12 AM Aaron Smith wrote: > Hi, > Would there be interest in a separate meeting to discussion wh

Re: [opnfv-tech-discuss] Continuing the Quarterly Awards discussion

+1 for interns For voting, I would suggest keep it in TSC. I thought also about PTLs or community's voting. But PTLs may not have a global view of the activity in community and community's voting is likely ending as a competition on which project has most members... On Thu, Jan 26, 2017 at 8:31

Re: [opnfv-tech-discuss] Continuing the Quarterly Awards discussion

We may also consider recognition for *Leadership*. The candidates could be - Working group leader/coordinators - PTLs - Outstanding core developer who leads some in-project or cross-project subject On Thu, Jan 26, 2017 at 8:31 AM Raymond Paik wrote: > All, > > Following up on our d

  1   2   3   >