Re: [opnfv-tech-discuss] [release][gambia] MS1 - project release plans - May 11

[David McBride]

We're still working out details for the CD track, but for the time being,
assume that the requirement is the same.

David

On Mon, Apr 30, 2018 at 1:51 PM, Beierl, Mark  wrote:

> Hello, David.
>
> What does a release plan look like for the Continuous track?  Is it the
> same plan?
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Developer
> *Dell **EMC* | Cloud & Communication Service Provider Solution
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On Apr 30, 2018, at 16:09, David McBride 
> wrote:
>
> Team,
>
> We are approaching our first milestone for Gambia, MS1 - release plans.
> Please create your release plan, then complete the release plan summary
> 
> .
>
> Also, recall that MS1 marks the close of the intent-to-participate
> 
> window.  Please make sure that you've sent notification for your project.
>
> Let me know if you have any questions.  Thanks.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [release][gambia] MS1 - project release plans - May 11

[Beierl, Mark]

Hello, David.

What does a release plan look like for the Continuous track?  Is it the same 
plan?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Apr 30, 2018, at 16:09, David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:

Team,

We are approaching our first milestone for Gambia, MS1 - release plans.  Please 
create your release plan, then complete the release plan 
summary.

Also, recall that MS1 marks the close of the 
intent-to-participate
 window.  Please make sure that you've sent notification for your project.

Let me know if you have any questions.  Thanks.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-tech-discussion][Edge Cloud] minutes for weekly meeting on April 26

[David McBride]

Edge Cloud team,

Please remember that you still need to submit your intent-to-participate
notification to the TSC
 by
MS1 on May 11 if you intend to participate in the OPNFV Gambia release.
Also, recall that MS1 is the due date for your project release plan

.

Let me know if you have questions.

David

On Wed, Apr 25, 2018 at 10:14 PM, 赵奇慧  wrote:

> Hi team,
>
>
> Here is the summary for today's meeting.
>
> More detail: https://etherpad.opnfv.org/p/edge_cloud_meeting_minutes
>
> Our next meeting is on next *Wednesday. May. 2, UTC 13:00-14:00 *
>
> Zoom link: https://zoom.us/j/5014627785
>
>
>
> Minutes for meeting on April 26, 2018:
>
> 1.  Project progress
>
> a)   successfully launched Edge Cloud project in opnfv
>
> 2.  Meeting plan
>
> a)   Project meeting: every other Wednesday, at UTC 13:00-14:00
>
> b)   Alternative meeting: every other Thursday, at UTC 3:00-4:00
>
> *3.  **Initial committer sign up*
>
> a)   *Please remember go to our etherpad page to add your name and
> the things you want to contribute before May 4th*, when we need to report
> the final list to TSC.
>
> b)   Initial committer: be able to make output for the following 2
> releases, including docs or codes
>
> 4.  Project promotion plan
>
> *a)   *Build separate working teams to work on specific areas. *Please
> also add your name here if you are willing to lead and contribute to this
> team on following areas:*
>
>  i.Edge Cloud requirement analysis and
> architecture design
>
> ii.Cross community liaison, Progress and
> gap analysis for upstream communities and OPNFV projects
>
>   iii.scenario definition and implementation
>
>   iv.Testing stretagy and test case
> development
>
>
>
> Best,
>
> Qihui
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][gambia] MS1 - project release plans - May 11

[David McBride]

Team,

We are approaching our first milestone for Gambia, MS1 - release plans.
Please create your release plan, then complete the release plan summary
.

Also, recall that MS1 marks the close of the intent-to-participate

window.  Please make sure that you've sent notification for your project.

Let me know if you have any questions.  Thanks.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][fraser] Fraser 6.1 - May 25

[David McBride]

Team,

We have about 3.5 weeks until our first point release for Fraser on May 25.

Events:

   - May 23 - complete testing
   - May 24 - documentation updates / JIRA cleanup
   - May 25 - tagging
   

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

[Rao, Sridhar]

Let me connect with Testperf Team. Last time we worked with chenjiankun 
chenjiank...@huawei.com. I’ll reach out to him 
to get this issue fixed.

Regards,
Sridhar K. N. Rao (Ph. D)
Architect – SDN/NFV
+91-9900088064

From: Cooper, Trevor 
Sent: Friday, April 27, 2018 10:38 PM
To: Klozik, MartinX ; 'Mars Toktonaliev (Nokia - 
US/Irving)' ; Rao, Sridhar 
Cc: opnfv-tech-discuss@lists.opnfv.org; David McBride 

Subject: RE: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

HI Martin

Sorry I just saw your email … well it confirms what I mentioned yesterday. 
Looks like somebody needs to dig a bit deeper. Sridhar who do you recommend to 
look into this?

Trevor

From: Klozik, MartinX
Sent: Wednesday, April 25, 2018 11:19 PM
To: Klozik, MartinX 
mailto:martinx.klo...@intel.com>>; David McBride 
mailto:dmcbr...@linuxfoundation.org>>; Cooper, 
Trevor mailto:trevor.coo...@intel.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
mailto:mars.toktonal...@nokia.com>>; Rao, Sridhar 
mailto:sridhar@spirent.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

Hi,

so there are still no results at Fraser reporting page, even after successful 
run of Fraser specific daily job.

I’ve checked that :

  1.  VSPERF successfully reported test results from fraser as PASSed:

http://testresults.opnfv.org/test/api/v1/results?project=vsperf&build_tag=jenkins-vswitchperf-daily-fraser-7

  1.  The code takes into account version from the build tag

https://git.opnfv.org/releng-testresults/tree/reporting/reporting/vsperf/reporting-status.py#n31

Can anybody have a more detailed look, to check what is going on?

Note: I can see, that reporting pages for Euphrates and Master do not work at 
all for VSPERF and some other projects too.

Best Regards,
Martin


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Klozik, 
MartinX
Sent: Tuesday, April 24, 2018 9:06 AM
To: David McBride 
mailto:dmcbr...@linuxfoundation.org>>; Cooper, 
Trevor mailto:trevor.coo...@intel.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

Due to issues with IXIA licenses, the vsperf CI was not working since 01/2018. 
Thus it was never executed for Fraser and there aren’t any results to be 
displayed.

Once CI run for master branch will finish successfully, then execution of 
Fraser CI daily job can be triggered manually. After that results should be 
visible at reporting page.

Regards,
Martin

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Tuesday, April 24, 2018 5:23 AM
To: Cooper, Trevor mailto:trevor.coo...@intel.com>>
Cc: Klozik, MartinX 
mailto:martinx.klo...@intel.com>>; Rao, Sridhar 
mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

What's going on with the VSPerf test results page?

http://testresults.opnfv.org/reporting/fraser/vsperf/reporting.html

On Mon, Apr 23, 2018 at 2:48 PM, Cooper, Trevor 
mailto:trevor.coo...@intel.com>> wrote:
Looks like CI is back in business, was able to resolve license issues through a 
Webex session with Ixia looking at log files :)

Trevor

From: Cooper, Trevor
Sent: Friday, March 30, 2018 2:44 PM
To: Klozik, MartinX 
mailto:martinx.klo...@intel.com>>; Rao, Sridhar 
mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Cc: 'ALFRED C 'MORTON (AL)'' mailto:acmor...@att.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com) 
mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com) 
mailto:bmich...@redhat.com>>; Elias, RichardX 
mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) mailto:ahot...@cisco.com>>; 
eddie.arr...@huawei.com
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Hi Sridhar, Martin

I have installed new Ixia licenses in POD 12 and updated the tickets. I had to 
restart node-3 too and triggered the Jenkins daily job. Looks like OVS_vanilla 
test just failed to execute. Can you take a look? 
https://build.opnfv.org/ci/view/vswitchperf/job/vswitchperf-daily-master/lastBuild/console

/Trevor



From: Klozik, MartinX
Sent: Wednesday, February 28, 2018 4:00 AM
To: Rao, Sridhar mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org

[opnfv-tech-discuss] [OVN4NFV] Weekly Meeting (1st May 2018) - Cancelled

[Trinath Somanchi]

Hi OVN4NFV team-

This weeks meeting is cancelled.

If you have any work items to discuss, please reply this mail.

/Trinath | NXP
___
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]Requirements for test resources collection

[Julien]

Hi,

For we don't have enough resources for Jenkins logs or other reasons, for
example, they are not valuable any more, the Jenkins system may delete some
of the historical records. Someday, you may find that the record indicated
by build_id won't exist in the future. It is OK if it does not exist in my
opinion.

Julien,
BR

David McBride 于2018年4月26日周四 上午11:53写道：

> Hi Jack,
>
> Sorry for the slow response.  I've been busy with the Fraser release.
>
> Comments
>
>1. I didn't understand point 1 about the build_id.  I thought that was
>the purpose of the Jenkins macro that Julien developed.  What am I missing?
>2. I'd like to see Health Check broken out as a separate column from
>Functest.
>3. The installer drop-down just lists "Fuel".  We need to include both
>Fuel@x86 and Fuel@aarm64.
>
> Thanks for your effort in pushing this forward.
>
> David
>
>
> On Sun, Apr 22, 2018 at 8:49 PM, Chenjiankun (JackChan) <
> chenjiank...@huawei.com> wrote:
>
>> Hi David,
>>
>>
>>
>> As discussed in the previous Email, I have create a first version of
>> scenario results table(we can call it gating reporting J), see:
>>
>>  http://116.66.187.136:9998/index.html
>>
>> Patch see:
>>
>>  https://gerrit.opnfv.org/gerrit/#/c/56179/
>>
>>
>>
>> For now, I have added four filters:
>>
>> 1.   Scenario
>>
>> 2.   Version
>>
>> 3.   Installer
>>
>> 4.   Iteration(we will query the last 10 days data, the default
>> iteration is 10, if all record is more than 10, it will only 10 record)
>>
>>
>>
>> For now, we still have some problems to solve:
>>
>> 1. build_id(Jenkins id), we don’t have a unified ID to mark the
>> whole Jenkins jobs(deployment + functest + yardstick), for now, I use the
>> build_tag(e.g. jenkins-functest-fuel-baremetal-daily-master-131, the
>> project:functest and installer:fuel are in build_tag) to index, so we can
>> only show the functest result.
>>
>> 2.   Jenkins job results, depend on build_id, we can’t show all
>> results(deployment + functest + yardstick, only functest for now). And each
>> projects need to upload their results(UNTRIGGERED, PASS, FAIL).
>>
>> 3.   Deployment results, for now, only daisy upload its deployment
>> result, we need ask each installer to upload deployment results, only
>> build_id ready, we can show all results.
>>
>> 4.   Statistic results, depend on projects upload their results
>>
>>
>>
>> It is the first version, we will add more functions step by step after
>> the above issue solved.
>>
>> @All, if you have any suggestions, please let me know.
>>
>>
>>
>> BRs,
>>
>> Jack Chan
>>
>>
>>
>> *发件人:* chenjiankun
>> *发送时间:* 2018年1月22日 17:02
>> *收件人:* 'David McBride'
>> *抄送:* TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao,
>> Sridhar; OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang
>> (Gabriel); ALFRED C 'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com;
>> Liyin (Ace); Wangwulin (Linda); georg.k...@ericsson.com; Serena Feng;
>> Julien
>> *主题:* RE: [opnfv-tech-discuss][test-wg]Requirements for test resources
>> collection
>>
>>
>>
>> Thanks, David.
>>
>>
>>
>> According your descriptions, I have created a demo table as below(wish I
>> do not misunderstanding your meaning):
>>
>>
>>
>> *scenario *
>>
>> *date *
>>
>> *Jenkins *
>>
>> *Version *
>>
>> *Installer *
>>
>> *Deployment *
>>
>> *Functest *
>>
>> *yardstick *
>>
>> os-nosdn-nofeature-ha
>>
>> 2018-01-21
>>
>> Jenkins id
>>
>> euphrates
>>
>> compass
>>
>> pass
>>
>> pass
>>
>> pass
>>
>> 2018-01-21
>>
>> Jenkins id
>>
>> euphrates
>>
>> compass
>>
>> fail
>>
>> not trigger
>>
>> not trigger
>>
>> statistic
>>
>> 8/9/10
>>
>> (pass:8,triggered:9, total:10)
>>
>> 6/7/8
>>
>> 6/7/8
>>
>>
>>
>>
>>
>> This last line in table body is the statistics information, and lines
>> above are the detailed information(and it can be folded).
>>
>> The score 8/9/10 is pass/triggered/total. Total means should run,
>> triggered means actually run.
>>
>> Also we can add three filters:
>>
>>
>>
>> If you select installer as compass, then will show all data related to
>> compass.
>>
>> Iterations means last x data points to be displayed.
>>
>>
>>
>> Does this table satisfied your requirements?
>>
>>
>>
>> BRs,
>>
>> Jack Chan
>>
>> *发件人:* David McBride [mailto:dmcbr...@linuxfoundation.org
>> ]
>> *发送时间:* 2018年1月20日 3:07
>> *收件人:* chenjiankun
>> *抄送:* TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao,
>> Sridhar; OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang
>> (Gabriel); ALFRED C 'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com;
>> Liyin (Ace); Wangwulin (Linda); georg.k...@ericsson.com; Serena Feng;
>> Julien
>> *主题:* Re: [opnfv-tech-discuss][test-wg]Requirements for test resources
>> collection
>>
>>
>>
>> +Serena, Julien
>>
>>
>>
>> Thanks, Jack.
>>
>>1. Data reported per scenario (i.e., jenkins job, deployment,
>>functest, yardstick, etc. displayed together for each scenario) instead of
>>separate test silos.
>>