Re: [opnfv-tech-discuss] [dovetall] Meeting Summary - 29 July 2016

[Tianhongbo]

Hi Chirs and Prakash.

Thanks for your effort.

I will update on the wiki page.

Best Regards

hongbo

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Christopher 
Price
Sent: 2016年7月30日 1:09
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [dovetall] Meeting Summary - 29 July 2016

Hi Folks,

I have started to capture thoughts on this wiki:  
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269

Action 1: Chris Price to spin wiki page for dovetail test case requirements and 
others can help to update it based on some structure which Chris can propose

Let’s capture our thoughts here and once we have a clear view on how this will 
fit together we can move to git/gerrit.  Consider it a free place to add and 
collaborate (try not to remove things) until nest weeks meeting.

/ Chris

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Prakash Ramchandran 
mailto:prakash.ramchand...@huawei.com>>
Date: Friday 29 July 2016 at 18:01
To: TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] OPNFV [Dovetall] Meeting Summary

Hi all,

Since Tianhongbo could not make to the Got meeting or IRC, the meeting was IRC 
only on #opnfv-meeting

Since the time ran past 8.00 due to late start besides wanted to summarize what 
can we retain from last 2-3 meetings besides today to consolidate Actionable 
Items and responsibilities...

meetbot to make sure we take proper minutes during meeting on irc..Thanks 
Prakash
 [08:06] <@collabot> Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.html
[08:06] <@collabot> Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.txt
[08:06] <@collabot> Log:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.log.html
[08:06]  #info ChrisPriceAB proposes that we start a wiki page to 
define test case requirements, structure, and the procedure for considering new 
tests.
[08:06]  I guess that didn't get minuted...
[08:06]  Thanks everyone, feels like we made progress

Please if you want it delegated to someone else please respond back

Maybe we can spin up a wiki page under dovetail to walk through our test case 
requiremenents. Happy to start that. 
(ChrisPriceAB,
 14:46:54)
Action 1: Chris Price to spin wiki page for dovetail test case requirements and 
others can help to update it based on some structure which Chris can propose
Action 2: Prakash will update the C&C guidance as listed below as request to 
Dovetail from C&C and we can debate it next week to
Action 3: Dave Neary to review and point any deviations we have here from the 
agreed scope of Dovetail and any concerns he has on SDNC, Installers etc. for 
use case testing or suggestions to help spirit of OPNFV to keep it Open to all
Action 4: Mathew Li - summarize IPv6  overlay (underlay out of scope for now) 
test efforts  that are taken up in different projects and consolidation of same 
for Dovetail once Chris Price spins the wiki with some structure to present

Here are my note from last  two meeting Action 2
Note C&C inputs to Dovetail  : Prakash has  summary of  C&C request as proposed 
by Chris Donley

· Chris Donley specified  directions to Dovetail stating that time is 
essence and we need to fit into plans to get Dovetail moving as the value for 
OPNFV by working with Compliance Verification Program (CVP) guidance.

· There was discussions on API vs. Use case (Blackbox) Approach.

· Since API from OPNFV projects are yet to be compiled and gap assessed 
with respect to ETSI TST APIs for many projects that have MANO implications, 
the baseline currently appears to be OPENSTACK + SDNC  and NB APIs are going to 
take time to settle.

· A black box approach with use cases in Release C that were taken up 
as part of roadmap and that will be addressed between SP & C&C while Dovetail 
should focus on use cases that were taken up in Release C under different 
projects.

· While OPNFV MANO Working group can address cross-project 
co-ordination , the testing can be based on Use cases with low bar to qualify 
at start and discussions moved to Dovetail framework and use cases to consider.

Dovetail framework  and use case discussions we had earlier can for now be 
expunged and revisit it after wiki is spun by Chris Price at next weekly 
meeting.

Thanks
Prakash




Prakash Ramchandran
[ogo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






___ opnfv-tech-discuss ma

[opnfv-tech-discuss] 答复: Functest feedback in Jenkins

[Lijun (Matthew)]

Hi

Good try.

Could this be run by command line without CI?

summary report are good dimensions, on the other hand, it hides some info.

in tempest, minimum/api/scenario/service tests are different category. We 
usually to use percentage for the same  test case pass rate by running it with 
number of times.

/MatthewLi

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Jose Lausuch
发送时间: 2016年7月29日 19:09
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] Functest feedback in Jenkins

Hi,

In order to provide a better user experience and useful feedback from the daily 
runs in Jenkins, these features have been implemented in Functest recently:

“Blocking flag” for each test case:
For each test case executed in Functest, there is a flag called “blocking” that 
can be set to True or False. If the test fails and the flag is set ‘true’, 
Functest will stop the execution of the rest of the tests in the daily loop 
exiting with error. If the test fails but the flag is set to false, it will 
mark the Job as failed, but it will allow the execution of the remaining test 
cases.
https://git.opnfv.org/cgit/functest/tree/ci/testcases.yaml
The purpose of this is to allow the critical test cases like the 
healthcheck/vping be a “gate” or a filter i.e. if you can’t create VMs, why 
should you bother in testing sfc or any other feature? Some other tests like 
Tempest, will allow the execution of the preceding tests even though if there 
is a failure.


Summary report:
Some of you gave us some feedback about the confusing output given by Functest 
in Jekins if a job has failed. This has been improved a lot, providing clear 
output messages to understand what is happening. But now you don’t even need to 
go through all that output, you just need to scroll  down and at the bottom of 
the page you will see the “Functest report” to check what has worked/failed 
along with some other useful information.
Example here: 
https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/261/console


Black listing tests in Tempest:
If you know that in a certain scenario/installer, a tempest test case fails, 
you can now blacklist the test case in this yaml:
https://git.opnfv.org/cgit/functest/tree/testcases/OpenStack/tempest/custom_tests/blacklist.txt
For example, for bgpvpn we have deactivated the tests that deal with floating 
ips due to lacking support for floating IPs in ODL VPNService (which will be 
fixed in the future).
So, if you know that a known bug will make a test case fail, you can add the 
test in this list and it will be skipped.
NOTE: this is not meant to avoid running tests that fail without a reason. It 
should be justified (known bug, feature lack of support, …).


You’ll see a lot of red in Jenkins, and that’s because Functest has become a 
bit more strict when giving the final status. It will only return blue if all 
the tests succeeded according to the defined success criteria, not only if the 
execution of the test script succeeded (even though the test failed).
For example:
https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/261/console
https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/260/console
The exit status is -1 because there was >0 failures in Tempest-smoke, and the 
success criteria for Tempest-smoke is 100%.

This strictness has been changed like this after some feedback collected from 
the community, in particular from the installer teams.



Thanks,

JOSE LAUSUCH
Senior Systems Designer
Ericsson

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

[opnfv-tech-discuss] Invitation: [SPC Polestar WG] OPNFV SPC Polestar WG Call Bi-Weekly @ Every 2 weeks from 10am to 11am on Thursday from Thu Aug 4 to Thu Dec 21, 2017 (CDT) (m...@linuxfoundation.org

[myu]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Chicago:20160804T10
DTEND;TZID=America/Chicago:20160804T11
RRULE:FREQ=WEEKLY;UNTIL=20171221T16Z;INTERVAL=2;BYDAY=TH
DTSTAMP:20160729T172514Z
ORGANIZER;CN=m...@linuxfoundation.org:mailto:m...@linuxfoundation.org
UID:gtu4th87smce07nmff81agr...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sandra.l.riv...@intel.com;X-NUM-GUESTS=0:mailto:sandra.l.rivera@int
 el.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jonne.soini...@nokia.com;X-NUM-GUESTS=0:mailto:jonne.soininen@nokia
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=prodip@hpe.com;X-NUM-GUESTS=0:mailto:prodip@hpe.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=john.v.he...@intel.com;X-NUM-GUESTS=0:mailto:john.v.he...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=bob.monk...@arm.com;X-NUM-GUESTS=0:mailto:bob.monk...@arm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=cyo...@clearpathnet.com;X-NUM-GUESTS=0:mailto:cyoung@clearpathnet.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=fbroc...@cisco.com;X-NUM-GUESTS=0:mailto:fbroc...@cisco.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=anthony.so...@huawei.com;X-NUM-GUESTS=0:mailto:anthony.soong@huawei
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=tf4...@att.com;X-NUM-GUESTS=0:mailto:tf4...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=m...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:m...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=pyeg...@juniper.net;X-NUM-GUESTS=0:mailto:pyeg...@juniper.net
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=christopher.pr...@ericsson.com;X-NUM-GUESTS=0:mailto:christopher.pr
 i...@ericsson.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;RSVP=TRU
 E;CN=Raymond Paik;X-NUM-GUESTS=0:mailto:rp...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=mc3...@att.com;X-NUM-GUESTS=0:mailto:mc3...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=paul...@emc.com;X-NUM-GUESTS=0:mailto:paul...@emc.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dick.c...@ztetx.com;X-NUM-GUESTS=0:mailto:dick.c...@ztetx.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
CREATED:20160729T153946Z
DESCRIPTION:OPNFV SPC Polestar Working Group Call Bi-weekly\n\nPlease join 
 my meeting from your computer\, tablet or smartphone.\nhttps://global.gotom
 eeting.com/join/976518869\n\n\nYou can also dial in using your phone.\nUnit
 ed States +1 (571) 317-3117\nUnited States (Toll-free): 1 866 899 4679\n\nA
 ccess Code: 976-518-869 \n\nMore phone numbers\nAustralia (Toll-free): 1 80
 0 189 049\nAustralia (Long distance): +61 2 8355 1039\nAustria (Toll-free):
  0 800 202144\nAustria (Long distance): +43 7 2088 1033\nBelgium (Toll-free
 ): 0 800 81382\nBelgium (Long distance): +32 (0) 28 93 7001\nBrazil (Toll-f
 ree): 0 800 047 4902\nBulgaria (Toll-free): 00800 120 4420\nCanada (Toll-fr
 ee): 1 888 299 1889\nCanada (Long distance): +1 (647) 497-9379\nChina (Toll
 -free): 4008 866143\nColombia (Toll-free): 01 800 012 9056\nCzech Republic 
 (Toll-free): 800 500443\nDenmark (Toll-free): 8025 3112\nDenmark (Long dist
 ance): +45 69 91 89 33\nFinland (Toll-free): 0 800 94503\nFinland (Long dis
 tance): +358 (0) 923 17 0555\nFrance (Toll-free): 0 805 541 043\nFrance (Lo
 ng distance): +33 (0) 170 950 585\nGermany (Toll-free): 0 800 723 5120\nGer
 many (Long distance): +49 (0) 692 5736 7303\nGreece (Toll-free): 00 800 441
 4 3554\nHong Kong (Toll-free): 30713171\nHungary (Toll-free): (06) 80 986 2
 58\nIceland (Toll-free): 800 9871\nIndia (Toll-free): 000 800 852 1424\nIre
 land (Toll-free): 1 800 946 534\nIreland (Long distance): +353 (0) 19 030 0
 50\nIsrael (Toll-free): 1 809 452 627\nItaly (Toll-free): 800 792498\nItaly
  (Long distance): +39 0 693 38 75 50\nJapan (Toll-free): 0 120 352 900\nKor
 ea\, Repu

[opnfv-tech-discuss] [dovetall] Meeting Summary - 29 July 2016

[Christopher Price]

Hi Folks,

 

I have started to capture thoughts on this wiki:  
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269 

 

Action 1: Chris Price to spin wiki page for dovetail test case requirements and 
others can help to update it based on some structure which Chris can propose

 

Let’s capture our thoughts here and once we have a clear view on how this will 
fit together we can move to git/gerrit.  Consider it a free place to add and 
collaborate (try not to remove things) until nest weeks meeting.

 

/ Chris

 

From:  on behalf of Prakash 
Ramchandran 
Date: Friday 29 July 2016 at 18:01
To: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] OPNFV [Dovetall] Meeting Summary

 

Hi all,

 

Since Tianhongbo could not make to the Got meeting or IRC, the meeting was IRC 
only on #opnfv-meeting

 

Since the time ran past 8.00 due to late start besides wanted to summarize what 
can we retain from last 2-3 meetings besides today to consolidate Actionable 
Items and responsibilities...

 

meetbot to make sure we take proper minutes during meeting on irc..Thanks 
Prakash

 [08:06] <@collabot> Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.html

[08:06] <@collabot> Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.txt

[08:06] <@collabot> Log:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.log.html

[08:06]  #info ChrisPriceAB proposes that we start a wiki page to 
define test case requirements, structure, and the procedure for considering new 
tests.

[08:06]  I guess that didn't get minuted...

[08:06]  Thanks everyone, feels like we made progress

 

Please if you want it delegated to someone else please respond back

 

Maybe we can spin up a wiki page under dovetail to walk through our test case 
requiremenents. Happy to start that. (ChrisPriceAB, 14:46:54)

Action 1: Chris Price to spin wiki page for dovetail test case requirements and 
others can help to update it based on some structure which Chris can propose

Action 2: Prakash will update the C&C guidance as listed below as request to 
Dovetail from C&C and we can debate it next week to 

Action 3: Dave Neary to review and point any deviations we have here from the 
agreed scope of Dovetail and any concerns he has on SDNC, Installers etc. for 
use case testing or suggestions to help spirit of OPNFV to keep it Open to all

Action 4: Mathew Li - summarize IPv6  overlay (underlay out of scope for now) 
test efforts  that are taken up in different projects and consolidation of same 
for Dovetail once Chris Price spins the wiki with some structure to present

 

Here are my note from last  two meeting Action 2

Note C&C inputs to Dovetail  : Prakash has  summary of  C&C request as proposed 
by Chris Donley

· Chris Donley specified  directions to Dovetail stating that time is 
essence and we need to fit into plans to get Dovetail moving as the value for 
OPNFV by working with Compliance Verification Program (CVP) guidance.

· There was discussions on API vs. Use case (Blackbox) Approach.

· Since API from OPNFV projects are yet to be compiled and gap assessed 
with respect to ETSI TST APIs for many projects that have MANO implications, 
the baseline currently appears to be OPENSTACK + SDNC  and NB APIs are going to 
take time to settle.

· A black box approach with use cases in Release C that were taken up 
as part of roadmap and that will be addressed between SP & C&C while Dovetail 
should focus on use cases that were taken up in Release C under different 
projects.

· While OPNFV MANO Working group can address cross-project 
co-ordination , the testing can be based on Use cases with low bar to qualify 
at start and discussions moved to Dovetail framework and use cases to consider.

 

Dovetail framework  and use case discussions we had earlier can for now be 
expunged and revisit it after wiki is spun by Chris Price at next weekly 
meeting.

 

Thanks

Prakash

 

 

 

 

Prakash Ramchandran

 R&D USA

FutureWei Technologies, Inc

Email: prakash.ramchand...@huawei.com

Work:  +1 (408) 330-5489

Mobile: +1 (408) 406-5810

2330 Central Expy, Santa Clara, CA 95050, USA

  

 

 

___ 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

[opnfv-tech-discuss] Agenda for the OPNFV August Board Meeting

[Raymond Paik]

All,

Below is the agenda for the OPNFV Board meeting on August 4th.

   - Introduction of new Board members/Ratification of email votes/Platinum
   member renewals update
   - TSC update
  - incl. vote on a resolution for the committers-at-large TSC election
   - Marketing committee update
   - Strategic Planning Committee update
  - incl. vote on a resolution for the SPC operational budget request
   - Certification & Complaince Committee upate
   - OPNFV Bylaws discussion
  - Silver Director elections when the number of nominees is less than
  or equal to the number of directors being elected
  - Continue discussion on the officers positions
   - Open CORD discussion

Thanks,

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

[opnfv-tech-discuss] [SPC Polestar Working Group]: Next Meeting 8AM Thurs, Aug 4 and Recurring Bi-weekly Call Details

[Min Yu]

*Time:* Thursday, 8:00AM Pacific Time
*Next Meeting Date*: August 4
*Frequency:* Recurring, Bi-weekly

Please join my meeting from your computer, tablet or smartphone.

   - https://global.gotomeeting.com/join/976518869
   -
   - You can also dial in using your phone.
   United States +1 (571) 317-3117
   United States (Toll-free): 1 866 899 4679

   Access Code: 976-518-869

   More phone numbers
   Australia (Toll-free): 1 800 189 049
   Australia (Long distance): +61 2 8355 1039
   Canada (Toll-free): 1 888 299 1889
   Canada (Long distance): +1 (647) 497-9379
   China (Toll-free): 4008 866143
   Czech Republic (Toll-free): 800 500443
   Denmark (Toll-free): 8025 3112
   Denmark (Long distance): +45 69 91 89 33
   Finland (Toll-free): 0 800 94503
   Finland (Long distance): +358 (0) 923 17 0555
   France (Toll-free): 0 805 541 043
   France (Long distance): +33 (0) 170 950 585
   Germany (Toll-free): 0 800 723 5120
   Germany (Long distance): +49 (0) 692 5736 7303
   Greece (Toll-free): 00 800 4414 3554
   Hong Kong (Toll-free): 30713171
   Hungary (Toll-free): (06) 80 986 258
   Iceland (Toll-free): 800 9871
   India (Toll-free): 000 800 852 1424
   Ireland (Toll-free): 1 800 946 534
   Ireland (Long distance): +353 (0) 19 030 050
   Italy (Toll-free): 800 792498
   Italy (Long distance): +39 0 693 38 75 50
   Japan (Toll-free): 0 120 352 900
   Korea, Republic of (Toll-free): 0806110880
   Netherlands (Toll-free): 0 800 022 6321
   Netherlands (Long distance): +31 (0) 208 080 208
   New Zealand (Toll-free): 0 800 47 0050
   New Zealand (Long distance): +64 9 925 0481
   Norway (Toll-free): 800 69 054
   Norway (Long distance): +47 21 54 82 21
   Poland (Toll-free): 00 800 1213978
   Portugal (Toll-free): 800 819 673
   Singapore (Toll-free): 800 101 2999
   South Africa (Toll-free): 0 800 555 449
   Spain (Toll-free): 800 900 578
   Spain (Long distance): +34 911 82 9890
   Sweden (Toll-free): 020 980 768
   Sweden (Long distance): +46 (0) 853 527 817
   Switzerland (Toll-free): 0 800 000 278
   Switzerland (Long distance): +41 (0) 435 0167 65
   Taiwan (Toll-free): 0 800 666 674
   United Kingdom (Toll-free): 0 800 389 5272
   United Kingdom (Long distance): +44 (0) 330 221 0099

   - First GoToMeeting? Try a test session: http://help.citrix.com/getready

--
Min Yu
Client Services Coordinator
The Linux Foundation
+1(530) 902-6464 (m)
m...@linuxfoundation.org
Skype: minyudecorah
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV [Dovetall] Meeting Summary

[Prakash Ramchandran]

Hi all,

Since Tianhongbo could not make to the Got meeting or IRC, the meeting was IRC 
only on #opnfv-meeting

Since the time ran past 8.00 due to late start besides wanted to summarize what 
can we retain from last 2-3 meetings besides today to consolidate Actionable 
Items and responsibilities...

meetbot to make sure we take proper minutes during meeting on irc..Thanks 
Prakash
 [08:06] <@collabot> Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.html
[08:06] <@collabot> Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.txt
[08:06] <@collabot> Log:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.log.html
[08:06]  #info ChrisPriceAB proposes that we start a wiki page to 
define test case requirements, structure, and the procedure for considering new 
tests.
[08:06]  I guess that didn't get minuted...
[08:06]  Thanks everyone, feels like we made progress

Please if you want it delegated to someone else please respond back

Maybe we can spin up a wiki page under dovetail to walk through our test case 
requiremenents. Happy to start that. 
(ChrisPriceAB,
 14:46:54)
Action 1: Chris Price to spin wiki page for dovetail test case requirements and 
others can help to update it based on some structure which Chris can propose
Action 2: Prakash will update the C&C guidance as listed below as request to 
Dovetail from C&C and we can debate it next week to
Action 3: Dave Neary to review and point any deviations we have here from the 
agreed scope of Dovetail and any concerns he has on SDNC, Installers etc. for 
use case testing or suggestions to help spirit of OPNFV to keep it Open to all
Action 4: Mathew Li - summarize IPv6  overlay (underlay out of scope for now) 
test efforts  that are taken up in different projects and consolidation of same 
for Dovetail once Chris Price spins the wiki with some structure to present

Here are my note from last  two meeting Action 2
Note C&C inputs to Dovetail  : Prakash has  summary of  C&C request as proposed 
by Chris Donley

* Chris Donley specified  directions to Dovetail stating that time is 
essence and we need to fit into plans to get Dovetail moving as the value for 
OPNFV by working with Compliance Verification Program (CVP) guidance.

* There was discussions on API vs. Use case (Blackbox) Approach.

* Since API from OPNFV projects are yet to be compiled and gap assessed 
with respect to ETSI TST APIs for many projects that have MANO implications, 
the baseline currently appears to be OPENSTACK + SDNC  and NB APIs are going to 
take time to settle.

* A black box approach with use cases in Release C that were taken up 
as part of roadmap and that will be addressed between SP & C&C while Dovetail 
should focus on use cases that were taken up in Release C under different 
projects.

* While OPNFV MANO Working group can address cross-project 
co-ordination , the testing can be based on Use cases with low bar to qualify 
at start and discussions moved to Dovetail framework and use cases to consider.

Dovetail framework  and use case discussions we had earlier can for now be 
expunged and revisit it after wiki is spun by Chris Price at next weekly 
meeting.

Thanks
Prakash




Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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

[opnfv-tech-discuss] Dovetail meeting has switched to #opnfv-meeting channel

[Yuyang (Gabriel)]

Hi,

Due to gotomeeting channel conflict, the dovetail weekly meeting has switched 
to #opnfv-meeting irc channel.
Please be noticed!

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

Re: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user guide/installation guide and configuration guide

[HU, BIN]

Great and thank you Ryota.

Bin
From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
Sent: Friday, July 29, 2016 2:58 AM
To: HU, BIN ; joehuang ; 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8 
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide

Hi,


Now, the doc-build job can run. Comment 'recheck' in under review changes and 
'remerge' in merged changes in case you don't have the job run against those 
changes.


Best,
Ryota

From: HU, BIN [mailto:bh5...@att.com]
Sent: Friday, July 29, 2016 1:15 PM
To: Mibu Ryota(壬生 亮太); joehuang; 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide

No wonder - I was wondering why my doc is still the old one even if the repo 
.rst has been updated.

Thank you for letting us know there is an issue in Jenkins configuration for 
doc build.

Thanks
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Thursday, July 28, 2016 8:52 PM
To: joehuang mailto:joehu...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8 mailto:ashishsingh...@gmail.com>>
Subject: Re: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide

Hi joehuang,


Yes, please change it to 'configurationguide' only in master branch.

FYI: we have an issue in Jenkins configuration for document build, so no docs 
build can run right now. But, I'll fix it ASAP.


Cheers,
Ryota

From: joehuang [mailto:joehu...@huawei.com]
Sent: Friday, July 29, 2016 12:46 PM
To: Mibu Ryota(壬生 亮太); 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide


Hello, Ryota,



I found that the folder name is different from the Release B:



Release C: Configuration 
Guide: 
/docs/configurationguide

Release B: Configuration 
Guide: 
/docs/configguide



Should we change the folder name from "configguide" which is for Releasse B to 
"configurationguide" in Release C?



Best Regards

Chaoyi Huang (joehuang)


From: Ryota Mibu [r-m...@cq.jp.nec.com]
Sent: 22 July 2016 20:10
To: joehuang; 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide
Hi,


We updated structure and templates in opnfvdocs.

You can find latest templates in opnfvdocs;

opnfvdocs/docs/configurationguide/configuration.options.render.rst
opnfvdocs/docs/configurationguide/scenario.description.rst

Also, please check https://wiki.opnfv.org/display/DOC/Documentation as well.

Note: we are still preparing and refining instructions and toolchain for 
documentation, please let me know if you have question and problems.


Best,
Ryota

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of joehuang
Sent: Friday, July 22, 2016 3:22 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide


Hello,



Could some one please provide the Colorado release documentation template for 
user guide/installation guide and configuration guide ? Thanks a lot.



Best Regards

Chaoyi Huang ( joehuang )
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: Bertrand Souville

[Manning, Serge [CTO]]

+1.

--Serge

On 7/29/16, 6:51 AM, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
Ryota Mibu"  wrote:

>Hi Doctor committers,
>
>
>I'd like to nominate Bertrand Souville to Doctor committer.
>
>He is so active in checking Doctor CI tests and patch reviews which are huge 
>helps for us, as we are tackling CI fixes. His +2 will accelerate our 
>development and debugging of Doctor tests.
>
>https://gerrit.opnfv.org/gerrit/#/q/r:souville%2540docomolab-euro.com
>
>Please reply "+1" if you support his promotion.
>
>
>Thanks,
>Ryota
>
>___
>opnfv-tech-discuss mailing list
>opnfv-tech-discuss@lists.opnfv.org
>https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss




This e-mail may contain Sprint proprietary information intended for the sole 
use of the recipient(s). Any use by others is prohibited. If you are not the 
intended recipient, please contact the sender and delete all copies of the 
message.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [releng] Promotion of Trevor Bramwell as committer

[Fatih Degirmenci]

Hi TSC,


Trevor has been nominated and accepted as committer to Releng with +1 from 7 
out of 8 Releng committers and there was no objection.


Helpdesk,


Please add Trevor to Releng submitters group on Gerrit. INFO file has been 
updated.


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

Re: [opnfv-tech-discuss] Functest feedback in Jenkins

[Christopher Price]

Really nice work guys.

Let's try and use this and see if it can help automate our d releases and 
reduce the effort involved in releasing.

/ Chris

Sent from my iPhone

> On Jul 29, 2016, at 13:09, Jose Lausuch  wrote:
> 
> Hi,
>  
> In order to provide a better user experience and useful feedback from the 
> daily runs in Jenkins, these features have been implemented in Functest 
> recently:
>  
> “Blocking flag” for each test case:
> For each test case executed in Functest, there is a flag called “blocking” 
> that can be set to True or False. If the test fails and the flag is set 
> ‘true’, Functest will stop the execution of the rest of the tests in the 
> daily loop exiting with error. If the test fails but the flag is set to 
> false, it will mark the Job as failed, but it will allow the execution of the 
> remaining test cases.
> https://git.opnfv.org/cgit/functest/tree/ci/testcases.yaml
> The purpose of this is to allow the critical test cases like the 
> healthcheck/vping be a “gate” or a filter i.e. if you can’t create VMs, why 
> should you bother in testing sfc or any other feature? Some other tests like 
> Tempest, will allow the execution of the preceding tests even though if there 
> is a failure.  
>  
>  
> Summary report:
> Some of you gave us some feedback about the confusing output given by 
> Functest in Jekins if a job has failed. This has been improved a lot, 
> providing clear output messages to understand what is happening. But now you 
> don’t even need to go through all that output, you just need to scroll  down 
> and at the bottom of the page you will see the “Functest report” to check 
> what has worked/failed along with some other useful information.
> Example here: 
> https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/261/console
>  
>  
> Black listing tests in Tempest:
> If you know that in a certain scenario/installer, a tempest test case fails, 
> you can now blacklist the test case in this yaml:
> https://git.opnfv.org/cgit/functest/tree/testcases/OpenStack/tempest/custom_tests/blacklist.txt
> For example, for bgpvpn we have deactivated the tests that deal with floating 
> ips due to lacking support for floating IPs in ODL VPNService (which will be 
> fixed in the future).
> So, if you know that a known bug will make a test case fail, you can add the 
> test in this list and it will be skipped.
> NOTE: this is not meant to avoid running tests that fail without a reason. It 
> should be justified (known bug, feature lack of support, …).
>  
>  
> You’ll see a lot of red in Jenkins, and that’s because Functest has become a 
> bit more strict when giving the final status. It will only return blue if all 
> the tests succeeded according to the defined success criteria, not only if 
> the execution of the test script succeeded (even though the test failed).
> For example:
> https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/261/console
> https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/260/console
> The exit status is -1 because there was >0 failures in Tempest-smoke, and the 
> success criteria for Tempest-smoke is 100%.
>  
> This strictness has been changed like this after some feedback collected from 
> the community, in particular from the installer teams.
>  
>  
>  
> Thanks,
>  
> JOSE LAUSUCH
> Senior Systems Designer 
> Ericsson
>  
> ___
> 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] [doctor] Nomination of Committer promotion for: Bertrand Souville

[Kunzmann, Gerald]

+1

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Carlos 
Goncalves
Sent: Freitag, 29. Juli 2016 13:57
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion 
for: Bertrand Souville

+1!

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: 29 July 2016 13:51
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: 
Bertrand Souville

Hi Doctor committers,


I'd like to nominate Bertrand Souville to Doctor committer.

He is so active in checking Doctor CI tests and patch reviews which are huge 
helps for us, as we are tackling CI fixes. His +2 will accelerate our 
development and debugging of Doctor tests.

https://gerrit.opnfv.org/gerrit/#/q/r:souville%2540docomolab-euro.com

Please reply "+1" if you support his promotion.


Thanks,
Ryota

___
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
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: Bertrand Souville

[Ulrich Kleber]

+1

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Carlos 
Goncalves
Sent: Friday, 29 July, 2016 13:57
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion 
for: Bertrand Souville

+1!

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: 29 July 2016 13:51
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: 
Bertrand Souville

Hi Doctor committers,


I'd like to nominate Bertrand Souville to Doctor committer.

He is so active in checking Doctor CI tests and patch reviews which are huge 
helps for us, as we are tackling CI fixes. His +2 will accelerate our 
development and debugging of Doctor tests.

https://gerrit.opnfv.org/gerrit/#/q/r:souville%2540docomolab-euro.com

Please reply "+1" if you support his promotion.


Thanks,
Ryota

___
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
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: Bertrand Souville

[Carlos Goncalves]

+1!

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: 29 July 2016 13:51
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: 
Bertrand Souville

Hi Doctor committers,


I'd like to nominate Bertrand Souville to Doctor committer.

He is so active in checking Doctor CI tests and patch reviews which are huge 
helps for us, as we are tackling CI fixes. His +2 will accelerate our 
development and debugging of Doctor tests.

https://gerrit.opnfv.org/gerrit/#/q/r:souville%2540docomolab-euro.com

Please reply "+1" if you support his promotion.


Thanks,
Ryota

___
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

[opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: Bertrand Souville

[Ryota Mibu]

Hi Doctor committers,


I'd like to nominate Bertrand Souville to Doctor committer.

He is so active in checking Doctor CI tests and patch reviews which are huge 
helps for us, as we are tackling CI fixes. His +2 will accelerate our 
development and debugging of Doctor tests.

https://gerrit.opnfv.org/gerrit/#/q/r:souville%2540docomolab-euro.com

Please reply "+1" if you support his promotion.


Thanks,
Ryota

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

[opnfv-tech-discuss] Functest feedback in Jenkins

[Jose Lausuch]

Hi,

In order to provide a better user experience and useful feedback from the daily 
runs in Jenkins, these features have been implemented in Functest recently:

"Blocking flag" for each test case:
For each test case executed in Functest, there is a flag called "blocking" that 
can be set to True or False. If the test fails and the flag is set 'true', 
Functest will stop the execution of the rest of the tests in the daily loop 
exiting with error. If the test fails but the flag is set to false, it will 
mark the Job as failed, but it will allow the execution of the remaining test 
cases.
https://git.opnfv.org/cgit/functest/tree/ci/testcases.yaml
The purpose of this is to allow the critical test cases like the 
healthcheck/vping be a "gate" or a filter i.e. if you can't create VMs, why 
should you bother in testing sfc or any other feature? Some other tests like 
Tempest, will allow the execution of the preceding tests even though if there 
is a failure.


Summary report:
Some of you gave us some feedback about the confusing output given by Functest 
in Jekins if a job has failed. This has been improved a lot, providing clear 
output messages to understand what is happening. But now you don't even need to 
go through all that output, you just need to scroll  down and at the bottom of 
the page you will see the "Functest report" to check what has worked/failed 
along with some other useful information.
Example here: 
https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/261/console


Black listing tests in Tempest:
If you know that in a certain scenario/installer, a tempest test case fails, 
you can now blacklist the test case in this yaml:
https://git.opnfv.org/cgit/functest/tree/testcases/OpenStack/tempest/custom_tests/blacklist.txt
For example, for bgpvpn we have deactivated the tests that deal with floating 
ips due to lacking support for floating IPs in ODL VPNService (which will be 
fixed in the future).
So, if you know that a known bug will make a test case fail, you can add the 
test in this list and it will be skipped.
NOTE: this is not meant to avoid running tests that fail without a reason. It 
should be justified (known bug, feature lack of support, ...).


You'll see a lot of red in Jenkins, and that's because Functest has become a 
bit more strict when giving the final status. It will only return blue if all 
the tests succeeded according to the defined success criteria, not only if the 
execution of the test script succeeded (even though the test failed).
For example:
https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/261/console
https://build.opnfv.org/ci/job/functest-fuel-baremetal-daily-master/260/console
The exit status is -1 because there was >0 failures in Tempest-smoke, and the 
success criteria for Tempest-smoke is 100%.

This strictness has been changed like this after some feedback collected from 
the community, in particular from the installer teams.



Thanks,

JOSE LAUSUCH
Senior Systems Designer
Ericsson

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

Re: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user guide/installation guide and configuration guide

[Ryota Mibu]

Hi,


Now, the doc-build job can run. Comment 'recheck' in under review changes and 
'remerge' in merged changes in case you don't have the job run against those 
changes.


Best,
Ryota

From: HU, BIN [mailto:bh5...@att.com]
Sent: Friday, July 29, 2016 1:15 PM
To: Mibu Ryota(壬生 亮太); joehuang; opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide

No wonder - I was wondering why my doc is still the old one even if the repo 
.rst has been updated.

Thank you for letting us know there is an issue in Jenkins configuration for 
doc build.

Thanks
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Thursday, July 28, 2016 8:52 PM
To: joehuang mailto:joehu...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8 mailto:ashishsingh...@gmail.com>>
Subject: Re: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide

Hi joehuang,


Yes, please change it to 'configurationguide' only in master branch.

FYI: we have an issue in Jenkins configuration for document build, so no docs 
build can run right now. But, I'll fix it ASAP.


Cheers,
Ryota

From: joehuang [mailto:joehu...@huawei.com]
Sent: Friday, July 29, 2016 12:46 PM
To: Mibu Ryota(壬生 亮太); 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide


Hello, Ryota,



I found that the folder name is different from the Release B:



Release C: Configuration 
Guide: 
/docs/configurationguide

Release B: Configuration 
Guide: 
/docs/configguide



Should we change the folder name from "configguide" which is for Releasse B to 
"configurationguide" in Release C?



Best Regards

Chaoyi Huang (joehuang)


From: Ryota Mibu [r-m...@cq.jp.nec.com]
Sent: 22 July 2016 20:10
To: joehuang; 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: RE: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide
Hi,


We updated structure and templates in opnfvdocs.

You can find latest templates in opnfvdocs;

opnfvdocs/docs/configurationguide/configuration.options.render.rst
opnfvdocs/docs/configurationguide/scenario.description.rst

Also, please check https://wiki.opnfv.org/display/DOC/Documentation as well.

Note: we are still preparing and refining instructions and toolchain for 
documentation, please let me know if you have question and problems.


Best,
Ryota

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of joehuang
Sent: Friday, July 22, 2016 3:22 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Cc: ashishsingh2k8
Subject: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user 
guide/installation guide and configuration guide


Hello,



Could some one please provide the Colorado release documentation template for 
user guide/installation guide and configuration guide ? Thanks a lot.



Best Regards

Chaoyi Huang ( joehuang )
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] 答复: Re: Including gerrit review as a method of performing Committer Promotion

[Christopher Price]

Hi Julien,

 

I think a nomination receiving a -2 is probably a good reason to start a dialog 
as to why rather than just ignoring the motion or making it not part of the 
process.

 

This could be seen as a potential improvement of the process, or of course a 
burden on the PTL. 

 

I would be surprised to see a committer nomination that would elicit a -2 and 
if that was the case it might be worth raising it to the TSC to gain an 
understanding of the reason/issues surrounding the nomination.  I would hope we 
did not need a process surrounding that and could accommodate, through common 
sense, the possibility of a -2.  

 

Your thoughts?

 

/ Chris

 

From:  on behalf of 

Date: Friday 29 July 2016 at 11:25
To: Yujun Zhang 
Cc: , TECH-DISCUSS OPNFV 
, TSC OPNFV 
Subject: [opnfv-tech-discuss] 答复: Re: Including gerrit review as a method of 
performing Committer Promotion

 

Hi All, 

Gerrit is used for code review and it can be of cause used for vote collecting 
from the members. I just want to mention that: 
even one "-2" will cause the patch can not be merged, and it can not be cleared 
even by submitted a new patchnet. 

Or, 
Every committer can submit a patchnet in the review, and leave the vote 
"±1，±2", which introduces tasks to the committers, but convenient for the PTL 
to trace the records. 
If the team has weekly meeting, irc vote mechanism can also be used and traced 
just like TSC meeting.

Regards, 
Julien 
  

 
  Julien(Jun) Zhang
 NFV Architect 
D206(D2028), R&D Building, ZTE Plaza, #889, Bibo RD, 
Pudong District, Shang Hai, P.R.China, 201203 
T:+86 21 68897791 M:+86 15317680806 F:+86 21 50801070 
E: zhang.ju...@zte.com.cn G: julien...@gmail.com
www.zte.com.cn, www.opnfv.org 






发件人: Yujun Zhang  
收件人: TSC OPNFV , 
抄送:TECH-DISCUSS OPNFV  
日期: 2016/07/29 09:03 
主题:Re: [opnfv-tech-discuss] Including gerrit review as a method of 
performing Committer Promotion 
发件人:opnfv-tech-discuss-boun...@lists.opnfv.org 




This is indeed a good idea. 

It would be also good if the content of INFO can be synchronized with gerrit 
group members. Then we can simple add the group as reviewer. 

My two cents

On Thu, Jul 28, 2016 at 4:52 PM Christopher Price 
 wrote: 
Hi TSC, 

  

On next week’s TSC call I would like to discuss the feasibility of using Gerrit 
as a method of collating votes on nominated committers for a project.  The 
general idea is that instead of using tech-discuss to collate votes the 
committers could vote via +2 on a patch to update the INFO file.  I have 
described this on the Committer promotions wiki page in italics 
https://wiki.opnfv.org/display/DEV/Committer+Promotions . 

  

At least to me this seems to me to be pretty straight forward.  

  

If there are no concerns with this and we agree with the text I’d like to 
simply run a vote on the next TSC call.  
https://wiki.opnfv.org/display/meetings/TSC#TSC-August2,2016 

I’m also happy to delay for further deliberation if there are concerns, this is 
not an urgent item rather a potential methodology improvement for our 
community. 

  

Regards, 

Chris 
___
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

___ 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

[opnfv-tech-discuss] 答复: Re: Including gerrit review as a method of performing Committer Promotion

[zhang . jun3g]

Hi All,

Gerrit is used for code review and it can be of cause used for vote 
collecting from the members. I just want to mention that:
even one "-2" will cause the patch can not be merged, and it can not be 
cleared even by submitted a new patchnet.

Or,
Every committer can submit a patchnet in the review, and leave the vote "
±1，±2", which introduces tasks to the committers, but convenient for 
the PTL to trace the records.
If the team has weekly meeting, irc vote mechanism can also be used and 
traced just like TSC meeting.

Regards,
Julien
 






  Julien(Jun) Zhang
  NFV Architect

D206(D2028), R&D Building, ZTE Plaza, #889, Bibo RD, 
Pudong District, Shang Hai, P.R.China, 201203 
T:+86 21 68897791 M:+86 15317680806 F:+86 21 50801070 
E: zhang.ju...@zte.com.cn G: julien...@gmail.com
www.zte.com.cn, www.opnfv.org 





发件人: Yujun Zhang 
收件人: TSC OPNFV , 
抄送:   TECH-DISCUSS OPNFV 
日期:   2016/07/29 09:03
主题:   Re: [opnfv-tech-discuss] Including gerrit review as a method of 
performing Committer Promotion
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org



This is indeed a good idea.

It would be also good if the content of INFO can be synchronized with 
gerrit group members. Then we can simple add the group as reviewer.

My two cents

On Thu, Jul 28, 2016 at 4:52 PM Christopher Price <
christopher.pr...@ericsson.com> wrote:
Hi TSC,
 
On next week’s TSC call I would like to discuss the feasibility of using 
Gerrit as a method of collating votes on nominated committers for a 
project.  The general idea is that instead of using tech-discuss to 
collate votes the committers could vote via +2 on a patch to update the 
INFO file.  I have described this on the Committer promotions wiki page in 
italics https://wiki.opnfv.org/display/DEV/Committer+Promotions .
 
At least to me this seems to me to be pretty straight forward.  
 
If there are no concerns with this and we agree with the text I’d like to 
simply run a vote on the next TSC call.  
https://wiki.opnfv.org/display/meetings/TSC#TSC-August2,2016 
I’m also happy to delay for further deliberation if there are concerns, 
this is not an urgent item rather a potential methodology improvement for 
our community.
 
Regards,
Chris
___
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


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

[opnfv-tech-discuss] 答复: Re: [fuel][new scenario][hugepage]Fuel configure hugepage with CI.

[zhang . jun3g]

Hi, Micheal and jyh,

It's great that you working on this.

Hugepage, Numa, Cpu pinning are common requirements in NFV application, 
which will be consumed by KVM, OVS and FD.IO projects in OPNFV. For a VNF,
it also has the same requirements even without KVM, OVS and FD.IO 
enhancement such as used in SR-IOV.

In OPNV, currently a scenario is defined by:
Installer(4)*sdntype(nosdn/odl_l2/odl_l3/opencontrail/onos)*feature(more 
and more)*ha(noha/ha).

There are too many scenarios now, and it will introduce tens of scenarios 
if we introduce hugepage as scenario factor. It will also cost too much 
work and too many hardware/CI resources. Shall we configure this feature 
in current scenarios other than add new scenarios. It can be a input 
parameter when triggering these scenarios.

This is a common requirement in Genesis, and let's have more discussion 
and implement it in Fuel. It will give an good example for other 
installers.


BR,
Julien


 






  Julien(Jun) Zhang
  NFV Architect

D206(D2028), R&D Building, ZTE Plaza, #889, Bibo RD, 
Pudong District, Shang Hai, P.R.China, 201203 
T:+86 21 68897791 M:+86 15317680806 F:+86 21 50801070 
E: zhang.ju...@zte.com.cn G: julien...@gmail.com
www.zte.com.cn, www.opnfv.org 





发件人: Michal Skalski 
收件人: yunhong jiang , 
抄送:   "opnfv-tech-discuss@lists.opnfv.org" 

日期:   2016/07/29 15:06
主题:   Re: [opnfv-tech-discuss] [fuel][new scenario][hugepage]Fuel 
configure hugepage with CI.
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org



Hi,

Yes, fuel support such configuration, we are currently working on pod 
configuration / existing scenario improvement:

https://jira.opnfv.org/browse/PHAROS-230
https://gerrit.opnfv.org/gerrit/#/c/17727/
https://gerrit.opnfv.org/gerrit/#/c/16913/ 

Regards,
Michal

On Fri, Jul 29, 2016 at 8:38 AM, yunhong jiang <
yunhong.ji...@linux.intel.com> wrote:
On Fri, 29 Jul 2016 14:22:07 +0800
wu.zhih...@zte.com.cn wrote:

> Hi fuel team，
>
> I notice that fuel@opnfv support hugepage configuration. ZTE-POD1
> want to configure hugepage with CI.

Hi, Zhihui
Thanks for sharing this information. To achieve good performance
and low latency with openstack, a lot of configuration is required,
like hugue page, CPU reservation, NUMA node (I gave a presentation
on openstack summit on this).

How can I check the fuel's support to these configuration? It will
be perfect if we can add such support to the scenario tests.

Thanks
--jyh
___
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


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

Re: [opnfv-tech-discuss] [fuel][new scenario][hugepage]Fuel configure hugepage with CI.

[Michal Skalski]

Hi,

Yes, fuel support such configuration, we are currently working on pod
configuration / existing scenario improvement:

https://jira.opnfv.org/browse/PHAROS-230
https://gerrit.opnfv.org/gerrit/#/c/17727/
https://gerrit.opnfv.org/gerrit/#/c/16913/

Regards,
Michal

On Fri, Jul 29, 2016 at 8:38 AM, yunhong jiang <
yunhong.ji...@linux.intel.com> wrote:

> On Fri, 29 Jul 2016 14:22:07 +0800
> wu.zhih...@zte.com.cn wrote:
>
> > Hi fuel team，
> >
> > I notice that fuel@opnfv support hugepage configuration. ZTE-POD1
> > want to configure hugepage with CI.
>
> Hi, Zhihui
> Thanks for sharing this information. To achieve good performance
> and low latency with openstack, a lot of configuration is required,
> like hugue page, CPU reservation, NUMA node (I gave a presentation
> on openstack summit on this).
>
> How can I check the fuel's support to these configuration? It will
> be perfect if we can add such support to the scenario tests.
>
> Thanks
> --jyh
> ___
> 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