[opnfv-tech-discuss] [IPv6] Project Meeting #67

[HU, BIN]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Maria Toe
 roe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Donald Hun
 ter (donaldh):MAILTO:dona...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jose Angel
  Lausuch:MAILTO:jalaus...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
DESCRIPTION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085\n+
 1 (312) 757-3126 / Access Code: 819-733-085\n\nHello team\,\n\nHere is the
  information of our IPv6 project meeting #67 to check the status update.\n
 \n-   When: Friday 7:00-8:00 PDT (14:00-15:00 UTC) September 15th\, 20
 17\no   Your local time\n-   Bridge: GoTo Meeting:
 \no   Web Conferencing: https://global.gotomeeting.com/join/819733085\
 no   Dial-in only:\n•   United States (Long distance): +1 (312) 
 757-3126 / Access Code: 819-733-085\n•   More phone numbers: https:/
 /global.gotomeeting.com/819733085/numbersdisplay.html\n-   Meeting pag
 e: https://wiki.opnfv.org/display/meetings/ipv6 for agenda and minutes\n- 
   Project wiki page: https://wiki.opnfv.org/display/ipv6/IPv6+Home for
  all information and resources related to IPv6 project\n\nLook forward to 
 working with everyone.\n\nThanks\nBin\n\n\n
SUMMARY;LANGUAGE=en-US:[IPv6] Project Meeting #67
DTSTART;TZID=Pacific Standard Time:20170915T07
DTEND;TZID=Pacific Standard Time:20170915T08
UID:04008200E00074C5B7101A82E0080096E9706223D301000
 01000CEDCAF291E6485429D0049EE138CD321
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170914T053955Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US: +1 (312) 757-3126 / Access Code: 819-733-085
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-85878815
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] 答复: [Functest] Installing and Running Functest in Transparent Proxy with Whitelists environment

[wangwulin]

Hi Srikanth,

I am wondering if you have succeeded launching functest container, and have 
trouble with functest env preparation. And which version of functest image did 
you use?


1)  If there is no trouble with docker engine installation for you, the two 
documentation links you mentioned are a little bit outdated.
Now offline is fully supported by functest master, so there is no need to 
access any URLs for the step “functest env prepare”.


2)  To enable run functest test cases, all the images required by tests should 
be downloaded beforehand via a shell file named download_images.sh [1] provided 
by functest. Please make sure these images URLs are included in your whitelist 
and put all the downloaded images in the dir /home/opnfv/functest/images inside 
functest container.


3)  Meanwhile, we are switching to the new Alpine images, please refer to [2] 
for detailed info.



[1]: https://git.opnfv.org/functest/tree/functest/ci/download_images.sh
[2]: https://wiki.opnfv.org/display/functest/Run+Alpine+Functest+containers


Best Regards,
Linda

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Srikanth Vavilapalli
发送时间: 2017年9月14日 2:33
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [Functest] Installing and Running Functest in 
Transparent Proxy with Whitelists environment

Hi

I am looking for some information in bringing up OPNFV Functest in a corporate 
proxy environment, where the proxy provides restricted internet connectivity 
based on the configured whitelist URLs.

I have looked at the Functest documentation wiki links [1] and [2], but they 
are not covering the above scenario.

In order to make the Functest work in the Proxy environment with whitelist, we 
need to know about the list of various domains or URLs that Functest would 
access during the installation and ENV prepare stages, such that we can 
configure upfront the Proxy with same list of URLs.

Can anyone plz let me know if this information is maintained in any functest 
wiki pages or appreciate if anyone from the community can share this 
information if they have tried Functest in such restricted environments in 
their own labs?


Thanks for your help.
Srikanth

[1] 
http://docs.opnfv.org/en/stable-danube/submodules/functest/docs/testing/user/configguide/index.html#proxy-support
[2] 
http://docs.opnfv.org/en/stable-danube/submodules/functest/docs/testing/user/configguide/index.html#docker-installation-on-centos-behind-http-proxy

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

[opnfv-tech-discuss] SFC Weekly meeting MoMs

[Manuel Buil]

Hello,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-09-13-14.01.html

As promised, here are the rest of issues which we could not cover
during the call:

#info issue #2 The time window we use to check if VMs are up is a bit
small. We need to increase it
#info I created a patch for this ==> https://gerrit.opnfv.org/gerrit/#/
c/41853/

#info issue #3 We need to provide the neutron source port id to the
vnffgd 
#info I created a patch to fix that: https://gerrit.opnfv.org/gerrit/#/
c/41849/

#info issue #4 there is a bug fixed in Pike which does not allow to
have input_data in the vnffgd templates
#link https://bugs.launchpad.net/tacker/+bug/1675672
#info It is fixed for pike. We should backport it and test

#info issue #5 ==> The new alpine functest container is missing the
sshpass package. We need it to access the VMs created by the test
#info patch to fix it ==> https://gerrit.opnfv.org/gerrit/#/c/41857/

#info issue #6: it is not possible to set the insecure flag when
creating the vim in tacker, so we must have valid certificates when
contacting tacker

Regards,
Manuel___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Functest] Installing and Running Functest in Transparent Proxy with Whitelists environment

[Srikanth Vavilapalli]

Hi

I am looking for some information in bringing up OPNFV Functest in a corporate 
proxy environment, where the proxy provides restricted internet connectivity 
based on the configured whitelist URLs.

I have looked at the Functest documentation wiki links [1] and [2], but they 
are not covering the above scenario.

In order to make the Functest work in the Proxy environment with whitelist, we 
need to know about the list of various domains or URLs that Functest would 
access during the installation and ENV prepare stages, such that we can 
configure upfront the Proxy with same list of URLs.

Can anyone plz let me know if this information is maintained in any functest 
wiki pages or appreciate if anyone from the community can share this 
information if they have tried Functest in such restricted environments in 
their own labs?


Thanks for your help.
Srikanth

[1] 
http://docs.opnfv.org/en/stable-danube/submodules/functest/docs/testing/user/configguide/index.html#proxy-support
[2] 
http://docs.opnfv.org/en/stable-danube/submodules/functest/docs/testing/user/configguide/index.html#docker-installation-on-centos-behind-http-proxy

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

Re: [opnfv-tech-discuss] [Pharos] Pharos lab for ARM band

[Trinath Somanchi]

Thanks Bob.

Can we have a lab with remote/Distributed ARM controller and compute nodes?



/Trinath

From: Bob Monkman 
Sent: Wednesday, September 13, 2017 8:44:52 PM
To: Alexandru Avadanii; Srikanth Lingala; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Shai Tsur; Gorja Gorja; Trinath Somanchi; Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

NXP team,

Alex is correct in that we do not yet have a plan of record for heterogeneous 
pods. But this has been discussed within Arm and we see it as a useful use case 
where controllers and compute nodes can be different architectures. We will 
seek to plan for this in 2018. I will reach out to your team regarding your 
immediate needs.

Regards,
Bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 8, 2017 9:23 AM
To: Srikanth Lingala ; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband ; Bob Monkman ; Shai 
Tsur ; Gorja Gorja ; Trinath Somanchi 
; Veera.reddy B 
Subject: RE: [Pharos] Pharos lab for ARM band

Hi,
We don’t have such patches, nor do we plan to support old Fuel any more.
We actually don’t intend to mix architectures for the new Fuel either, at least 
not in the near future.

If you want to support this use-case, you will have to implement it yourself.
I do think the new Fuel is friendlier to this scenario, but again, we never 
looked into it.

BR,
Alex


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 4:21 PM
To: Alexandru Avadanii; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur; Gorja Gorja; Trinath Somanchi; 
Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

OK…So, If I apply some patches to Fuel and rebuild Fuel ISO, can I deploy with 
mixed (x86 and aarch64) targets in Pharos POD?
If so, can you please point me to those patches?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 5:54 PM
To: Srikanth Lingala 
>; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband >; Bob 
Monkman >; Shai Tsur 
>; Gorja Gorja 
>; Trinath Somanchi 
>; Veera.reddy B 
>
Subject: RE: [Pharos] Pharos lab for ARM band

Hi,
That is correct, everything is now AArch64 in our PODs.

BR,
Alex


From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 11:48 AM
To: Alexandru Avadanii; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur; Gorja Gorja; Trinath Somanchi; 
Veera.reddy B
Subject: RE: [Pharos] Pharos lab for ARM band

Hi Alex,
Thanks for the details.
I viewed the following link for reference:
https://wiki.opnfv.org/display/pharos/Enea+Hosting

So, in the current ENEA Pharos lab, you are using ARM based machines as OS 
Controller nodes, Compute nodes and even Jump Host node. Not using any hybrid 
POD (with combination of x86 and ARM machines as nodes). Right?

Regards,
Srikanth.

From: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
Sent: Friday, September 08, 2017 12:49 AM
To: Srikanth Lingala 
>; 
opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband >; Bob 
Monkman >; Shai Tsur 
>
Subject: RE: [Pharos] Pharos lab for ARM band

Hi, Srikanth,
I’m glad to hear about new AArch64 hardware joining 

Re: [opnfv-tech-discuss] [opnfv-tsc] Commiters-at-Large TSC election

[Raymond Paik]

Bryan,

I just re-sent you the ballot for the TSC.  Let me know if you still don't
see it in the next hour or so.

As for the Board election, it turns out the email was sent out twice but
you're only going to be allowed to vote once so there shouldn't be
issues

Thanks,

Ray

On Wed, Sep 13, 2017 at 8:08 AM, SULLIVAN, BRYAN L (BRYAN L) <
bryan.sulli...@research.att.com> wrote:

> I think someone else also reported this issue... but I received two
> notices for the BOD election and none for the TSC election.
>
> On Sep 13, 2017, at 7:32 AM, Raymond Paik 
> wrote:
>
> All,
>
> Thanks to everyone who voted so far...
>
> If you have not voted yet, this is a reminder that the Committers-at-Large
> TSC election closes at 5pm Pacific Time this Friday (Sep. 15th).
>
> Cheers,
>
> Ray
>
> On Sun, Sep 10, 2017 at 9:44 PM, Raymond Paik 
> wrote:
>
>> All,
>>
>> For eligible committers
>> ,
>> you will be receiving an email from "Ray Paik (CIVS poll supervisor)" to cast
>> your vote to elect 5 Committers-at-Large TSC members.  Please note that
>> the email will not be coming from my Linux Foundation email address and if
>> you can't find the email (incl. in your spam folders), please let me know.
>>
>> You can find the complete list of nominees (listed alphabetically by
>> first name) on this page
>> .
>> The poll will close at 5pm Pacific Time on September 15th (Friday).
>>
>> Thanks,
>>
>> Ray
>>
>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> opnfv.org_mailman_listinfo_opnfv-2Dtsc=DwICAg=LFYZ-
> o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcU
> wMwT5Zs1Tnk=wC_VaikCJwbB4-jm2-Y3BsxlP8uFR_u2KGZbuz1zP-A=xjoSmGA4v-
> hDeUu8uowvQN1s4oRQlXasBGbIcPUkcxg=
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [mano-wg] Meeting #45 Summary - Focus VNF Onboarding and Orchestration using Heat

[Prakash Ramchandran]

Hi all,

Appreciate your participation in resolving release and best practices issues on 
VNF Onboarding. The review of ICE, VNF Onboarding using Heat and ONAP for OPNFV 
testing was well received. The summary of today mano-wg 
meeting
 for reference is included here. Please suggest any topics that may be of 
interest to you for using OPNFV with upstream MANO stacks for next meeting#46 
to be planned.


Thanks
Prakash

___
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-tsc] Commiters-at-Large TSC election

[SULLIVAN, BRYAN L (BRYAN L)]

I think someone else also reported this issue... but I received two notices for 
the BOD election and none for the TSC election.

On Sep 13, 2017, at 7:32 AM, Raymond Paik 
> wrote:

All,

Thanks to everyone who voted so far...

If you have not voted yet, this is a reminder that the Committers-at-Large TSC 
election closes at 5pm Pacific Time this Friday (Sep. 15th).

Cheers,

Ray

On Sun, Sep 10, 2017 at 9:44 PM, Raymond Paik 
> wrote:
All,

For eligible 
committers,
 you will be receiving an email from "Ray Paik (CIVS poll supervisor)" to cast 
your vote to elect 5 Committers-at-Large TSC members.  Please note that the 
email will not be coming from my Linux Foundation email address and if you 
can't find the email (incl. in your spam folders), please let me know.

You can find the complete list of nominees (listed alphabetically by first 
name) on this 
page.
  The poll will close at 5pm Pacific Time on September 15th (Friday).

Thanks,

Ray

___
opnfv-tsc mailing list
opnfv-...@lists.opnfv.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=wC_VaikCJwbB4-jm2-Y3BsxlP8uFR_u2KGZbuz1zP-A=xjoSmGA4v-hDeUu8uowvQN1s4oRQlXasBGbIcPUkcxg=
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Commiters-at-Large TSC election

[Raymond Paik]

All,

Thanks to everyone who voted so far...

If you have not voted yet, this is a reminder that the Committers-at-Large
TSC election closes at 5pm Pacific Time this Friday (Sep. 15th).

Cheers,

Ray

On Sun, Sep 10, 2017 at 9:44 PM, Raymond Paik 
wrote:

> All,
>
> For eligible committers
> ,
> you will be receiving an email from "Ray Paik (CIVS poll supervisor)" to cast
> your vote to elect 5 Committers-at-Large TSC members.  Please note that
> the email will not be coming from my Linux Foundation email address and if
> you can't find the email (incl. in your spam folders), please let me know.
>
> You can find the complete list of nominees (listed alphabetically by first
> name) on this page
> .  The
> poll will close at 5pm Pacific Time on September 15th (Friday).
>
> Thanks,
>
> Ray
>
___
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/Armband ODL scenario rename in Functest test results dashboard

[Alexandru Avadanii]

Hi, Venkat,
It depends on what installer branch you are using.
If you use Fuel Danube, the old naming should be used.
For Fuel master, the new naming should be used, but as Kubi pointed out, this 
might still need some work.

BR,
Alex

> -Original Message-
> From: Gaoliang (kubi) [mailto:jean.gaoli...@huawei.com]
> Sent: Wednesday, September 13, 2017 9:59 AM
> To: Ross Brattain
> Cc: opnfv-tech-discuss@lists.opnfv.org; vven...@codeaurora.org; Alexandru
> Avadanii; 'RICHOMME Morgan IMT/OLN'
> Subject: Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in
> Functest test results dashboard
> 
> Hi Ross,
> 
> Venkat's email reminder me that there are still some work for ODL scenario
> rename.
> 
> I saw you have upload a patch which is "add opnfv_os-odl-nofeature-
> noha_daily.yaml [1] for odl_l3 to odl rename"
> 
> And It seems that we also need to add opnfv_os-odl-nofeature-ha_daily.yaml to
> Yardstick repo for odl_l3 to odl rename .
> 
> [1] https://gerrit.opnfv.org/gerrit/#/c/40895/
> 
> Regards,
> 
> Kubi
> 
> -邮件原件-
> 发件人: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-
> boun...@lists.opnfv.org] 代表 vven...@codeaurora.org
> 发送时间: 2017年9月13日 13:52
> 收件人: 'Alexandru Avadanii' ; 'RICHOMME
> Morgan IMT/OLN' 
> 抄送: opnfv-tech-discuss@lists.opnfv.org
> 主题: Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest
> test results dashboard
> 
> Hi Alex,
> While your question is answered,
> Request you to clarify :  This is also exported to Yardstick, Functest 
> accordingly.
> I should feed there as os-odl-nofeature-ha say as an example or still 
> os-odl_l3-
> nofeature-ha ??
> 
> Thanks
> -Venkat
> 
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alexandru
> Avadanii
> Sent: Wednesday, September 13, 2017 4:50 AM
> To: RICHOMME Morgan IMT/OLN 
> Cc: opnfv-tech-discuss@lists.opnfv.org
> Subject: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest
> test results dashboard
> 
> Hi,
> Fuel and Armband projects renamed the ODL-L3 scenario to simply ODL, and
> dropped the ODL-L2 scenarios, as described in [1].
> I noticed that the Functest results dashboard pages [2, 3] still use the old
> naming scheme, although the new scenario is also listed.
> Would it be possible to cleanup obsolete scenarios?
> 
> Thank you,
> Alex
> 
> [1] https://jira.opnfv.org/browse/FUEL-279
> [2]
> http://testresults.opnfv.org/reporting/master/functest/status-f...@x86.html
> [3]
> http://testresults.opnfv.org/reporting/master/functest/status-fuel@aarch64.h
> tml
> 
> ___
> 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] [Reminder to Vote] OPNFV Committer Board Election

[Min Yu]

Quick reminder -- if you have not yet voted in the OPNFV Committer Board
election, please do so at your earliest convenience (voting will close at 5pm
PT on Friday, September 15th).

Each eligible voter
 was
sent one unique ballot via email.  You can search for this which would have
been sent from c...@cs.cornell.edu on September 11.  This contains the
unique link for you to cast your vote.

Thanks,
Min

--
Min Yu
Senior Operations Analyst
The Linux Foundation
+1(530) 902-6464 (m)
m...@linuxfoundation.org
Skype: minyudecorah

On Mon, Sep 11, 2017 at 8:46 AM, Min Yu  wrote:

> All,
>
> For eligible committers
> ,
> you will be receiving an email from "Min Yu (CIVS poll supervisor)" to cast
> your vote to elect 1 Committer Board member.  Please note that the email
> will not be coming from my Linux Foundation email address and if you can't
> find the email (incl. in your spam folders), please let me know.
>
> You can find the complete list of nominees (listed alphabetically by first
> name) on this page
> .
> The poll will close at 5pm Pacific Time on September 15th (Friday).
>
> Thanks,
> Min
> --
> Min Yu
> Senior Operations Analyst
> The Linux Foundation
> +1(530) 902-6464 <(530)%20902-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] Canceled: Weekly SNAPS-OO Technical Discussion

[Steven Pisarski]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Mountain Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Steven Pisarski:MAILTO:s.pisar...@cablelabs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:I will be cancelling this meeting as I will be o
 ut on PTO for the next couple of weeks. I will be scheduling another serie
 s after my return so we can begin planning for the F release.\n\nBest\,\nS
 teve\n\n\n\nHello\,\n\nPlease join our weekly technical discussion for the
  SNAPS-OO project. If you cannot attend\, please feel free to send your fe
 ature requests directly to me.\n\nBest regards\,\nSteve Pisarski\nArchitec
 t\nCableLabs\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://cable
 labs.zoom.us/j/314610225\n\nOr iPhone one-tap (US Toll): +16465588656\,314
 610225# or +14086380968\,314610225#\n\nOr Telephone:\nDial: +1 646 558 865
 6 (US Toll) or +1 408 638 0968 (US Toll)\n+971 4 550 8389 (United Arab Emi
 rates Toll)\n(010) 87833177 (China Toll)\n+62 21 2188 9017 (Indonesia Toll
 )\n+91 22 62 192 563 (India Toll)\n+91 22 71 279 163 (India Toll)\n+63 239
 5 3500 (Philippines Toll)\n+66 60 003 5790 (Thailand Toll)\n+886 277 417 4
 73 (Taiwan Toll)\n+84 8 4458 2373 (Vietnam Toll)\n+1 855 880 1246 (US Toll
  Free)\n+1 877 369 0926 (US Toll Free)\nMeeting ID: 314 610 225\nInternati
 onal numbers available: https://cablelabs.zoom.us/zoomconference?m=Tzbe-cS
 aiGiwP4ayLCpsevbFjE3dZ_xx\n\nOr an H.323/SIP room system:\nH.323:\n162.255
 .37.11 (US West)\n162.255.36.11 (US East)\n221.122.88.195 (China)\n115.114
 .131.7 (India)\n213.19.144.110 (EMEA)\nMeeting ID: 314 610 225\n\nSIP: 314
 610...@zoomcrc.com\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;WKST=SU
EXDATE;TZID=Mountain Standard Time:20170329T073000,20170405T073000,20170426
 T073000
UID:A6B3D2AA-9A4E-4D79-B577-9AD2903332C2
SUMMARY;LANGUAGE=en-US:Canceled: Weekly SNAPS-OO Technical Discussion
DTSTART;TZID=Mountain Standard Time:20170315T073000
DTEND;TZID=Mountain Standard Time:20170315T083000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170913T135905Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:5
LOCATION;LANGUAGE=en-US:https://cablelabs.zoom.us/j/314610225
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:2115194895
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Cancelled: Weekly SNAPS-OO Technical Discussion @ Wednesday, 15 March 2017

[Steven Pisarski]

MAR


15









"Weekly SNAPS-OO Technical Discussion" has been cancelled









When

   



Wednesday, 15 March 2017
01:30 PM to 02:30 PM 
 (GMT) Greenwich Mean Time - Dublin / Edinburgh / Lisbon / London 

This event repeats every week on Wednesday.








 Where



https://cablelabs.zoom.us/j/314610225




   

Message



Hello,



Please join our weekly technical discussion for the SNAPS-OO project. If you cannot attend, please feel free to send your feature requests directly to me.



Best regards,

Steve Pisarski

Architect

CableLabs



Join from PC, Mac, Linux, iOS or Android: https://cablelabs.zoom.us/j/314610225



Or iPhone one-tap (US Toll): +16465588656,314610225# or +14086380968,314610225#



Or Telephone:

Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)

+971 4 550 8389 (United Arab Emirates Toll)

(010) 87833177 (China Toll)

+62 21 2188 9017 (Indonesia Toll)

+91 22 62 192 563 (India Toll)

+91 22 71 279 163 (India Toll)

+63 2395 3500 (Philippines Toll)

+66 60 003 5790 (Thailand Toll)

+886 277 417 473 (Taiwan Toll)

+84 8 4458 2373 (Vietnam Toll)

+1 855 880 1246 (US Toll Free)

+1 877 369 0926 (US Toll Free)

Meeting ID: 314 610 225

International numbers available: https://cablelabs.zoom.us/zoomconference?m=Tzbe-cSaiGiwP4ayLCpsevbFjE3dZ_xx



Or an H.323/SIP room system:

H.323:

162.255.37.11 (US West)

162.255.36.11 (US East)

221.122.88.195 (China)

115.114.131.7 (India)

213.19.144.110 (EMEA)

Meeting ID: 314 610 225



SIP: 314610...@zoomcrc.com







 

   





 This event invitation was sent from   Yahoo Calendar






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

[opnfv-tech-discuss] Cancelled: Weekly SNAPS-OO Technical Discussion @ Wednesday, 15 March 2017

[Steven Pisarski]

MAR


15









"Weekly SNAPS-OO Technical Discussion" has been cancelled









When

   



Wednesday, 15 March 2017
01:30 PM to 02:30 PM 
 (GMT) Greenwich Mean Time - Dublin / Edinburgh / Lisbon / London 

This event repeats every week on Wednesday.








 Where



https://cablelabs.zoom.us/j/314610225




   

Message



Hello,



Please join our weekly technical discussion for the SNAPS-OO project. If you cannot attend, please feel free to send your feature requests directly to me.



Best regards,

Steve Pisarski

Architect

CableLabs



Join from PC, Mac, Linux, iOS or Android: https://cablelabs.zoom.us/j/314610225



Or iPhone one-tap (US Toll): +16465588656,314610225# or +14086380968,314610225#



Or Telephone:

Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)

+971 4 550 8389 (United Arab Emirates Toll)

(010) 87833177 (China Toll)

+62 21 2188 9017 (Indonesia Toll)

+91 22 62 192 563 (India Toll)

+91 22 71 279 163 (India Toll)

+63 2395 3500 (Philippines Toll)

+66 60 003 5790 (Thailand Toll)

+886 277 417 473 (Taiwan Toll)

+84 8 4458 2373 (Vietnam Toll)

+1 855 880 1246 (US Toll Free)

+1 877 369 0926 (US Toll Free)

Meeting ID: 314 610 225

International numbers available: https://cablelabs.zoom.us/zoomconference?m=Tzbe-cSaiGiwP4ayLCpsevbFjE3dZ_xx



Or an H.323/SIP room system:

H.323:

162.255.37.11 (US West)

162.255.36.11 (US East)

221.122.88.195 (China)

115.114.131.7 (India)

213.19.144.110 (EMEA)

Meeting ID: 314 610 225



SIP: 314610...@zoomcrc.com







 

   





 This event invitation was sent from   Yahoo Calendar






invite.ics
Description: application/ics
___
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/Armband ODL scenario rename in Functest test results dashboard

[Gaoliang (kubi)]

Hi Ross,

Venkat's email reminder me that there are still some work for ODL scenario 
rename.

I saw you have upload a patch which is "add 
opnfv_os-odl-nofeature-noha_daily.yaml [1] for odl_l3 to odl rename" 

And It seems that we also need to add opnfv_os-odl-nofeature-ha_daily.yaml to 
Yardstick repo for odl_l3 to odl rename .

[1] https://gerrit.opnfv.org/gerrit/#/c/40895/

Regards,

Kubi

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 vven...@codeaurora.org
发送时间: 2017年9月13日 13:52
收件人: 'Alexandru Avadanii' ; 'RICHOMME Morgan 
IMT/OLN' 
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test 
results dashboard

Hi Alex,
While your question is answered,
Request you to clarify :  This is also exported to Yardstick, Functest 
accordingly. I should feed there as os-odl-nofeature-ha say as an example or 
still os-odl_l3-nofeature-ha ??

Thanks
-Venkat

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alexandru 
Avadanii
Sent: Wednesday, September 13, 2017 4:50 AM
To: RICHOMME Morgan IMT/OLN 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test 
results dashboard

Hi,
Fuel and Armband projects renamed the ODL-L3 scenario to simply ODL, and 
dropped the ODL-L2 scenarios, as described in [1].
I noticed that the Functest results dashboard pages [2, 3] still use the old 
naming scheme, although the new scenario is also listed.
Would it be possible to cleanup obsolete scenarios?

Thank you,
Alex

[1] https://jira.opnfv.org/browse/FUEL-279
[2]
http://testresults.opnfv.org/reporting/master/functest/status-f...@x86.html
[3]
http://testresults.opnfv.org/reporting/master/functest/status-fuel@aarch64.h
tml

___
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] [OPNFV] [OpenStack] resilency/stress/long duration/robustness testing synchro

[Yuyang (Gabriel)]

Hi Ghanshyam and Ildiko,



Firstly, sorry for the late response. I have just finished reading from the 
links you provided.

It is very excited for me knowing that tempest could consider stress testing as 
part of OpenStack QA.

In OPNFV, we start to plan stress testing from last release. It would be more 
excited for me if we could cooperate on this kind of testing.

I have added a summary of our resiliency/stress/robustness/long duration 
testing activities in https://etherpad.openstack.org/p/qa-queens-ptg (as agreed 
in OPNFV testing group) and hoped it could form some foundation for our further 
discussion.



I also put the summary below, please feel free to contact me if there is any 
doubt/comment/question.



In OPNFV Danube (OS Newton) release, OPNFV testing working group (Testperf) 
decides to extend the OPNFV testing scope by introducing basic stress test 
cases. There are 5 test cases discussed. Different from the destructive test 
(HA) that OpenStack QA team have considered, these test cases are basically 
designed from load stress perspective instead of redundancy perspective. In 
Danube, Bottlenecks project (OPNFV system limit testing project) and Yardstick 
project (OPNFV performance test project for NFVI and VNF) jointly implemented 2 
of them (concurrently create/destroy VM pairs and do ping, system throughput 
limit) while Bottlenecks acts as the load manager calling yardstick to execute 
each test iteration. These tests are designed to test for breaking points and 
provide level of confidence of the system to users. More details could be found 
at

a)   
https://wiki.opnfv.org/display/bottlenecks/Stress+Testing+over+OPNFV+Platform

b)   
https://wiki.opnfv.org/download/attachments/2926539/Testing%20over%20Long%20Duration%20POD.pptx?version=2=1502943821000=v2



Stress test cases for OPNFV Euphrates (OS Ocata) release can be seen as 
extension/enhancement of those in D release. These test cases are under 
degugging in Bottlenecks/Yardstick repo (Bottlenecks as load manager while 
Yardstick execute each test iteration):

a)   VNF scale out/up tests (also plan to measure storage usage 
simultaneously): https://wiki.opnfv.org/pages/viewpage.action?pageId=12390101

b)   Life-cycle event with throughputs (measure NFVI to support concurrent 
network usage from different VM pairs): 
https://wiki.opnfv.org/display/DEV/Intern+Project%3A+Baseline+Stress+Test+Case+for+Bottlenecks+E+Release



In OPNFV E release, we also plan to do long duration test over OS Ocata. A 
separate CI pipe testing OPNFV XCI (OSA) is proposed to accomplish the job. We 
have applied specific pod for the testing. Detailed proposal could be found at:

a)   https://wiki.opnfv.org/display/testing/Euphrates+Testing+needs

b)   
https://wiki.opnfv.org/download/attachments/2926539/testing%20evolution%20v1_4.pptx?version=1=1503937629000=v2

c)   
https://wiki.opnfv.org/download/attachments/2926539/Testing%20over%20Long%20Duration%20POD.pptx?version=2=1502943821000=v2

The long duration test is supposed to be started when OPNFV E release is 
published.

Bottlenecks plans to add a monitoring module for these tests: 
https://wiki.opnfv.org/display/DEV/Intern+Project%3A+Monitoring+Stress+Testing+for+Bottlenecks+E+Release



ps. @Testperf please add if there is anything missing



Waiting for your reply,

Gabriel





-Original Message-
From: Ghanshyam Mann [mailto:ghanshyamm...@gmail.com]
Sent: Tuesday, August 29, 2017 10:12 AM
To: Ildiko Vancsa
Cc: RICHOMME Morgan IMT/OLN; Andrea Frittoli; test...@lists.opnfv.org; Yuyang 
(Gabriel); Pierre Lynch
Subject: Re: [OPNFV] [OpenStack] resilency/stress/long duration/robustness 
testing synchro



Thanks ildiko for adding in ML.



From OpenStack QA perspective, we have some scope limitation of adding the 
tests in Tempest repo but it can be done as separate repo similar to other 
similar kind of testing (RBAC testing).



Good things is that we do have common testing framework and plugin mechanism to 
implement more broader testing as separate QA/other community projects. I am 
pasting few quick link to get overview of OpenStack QA projects :



Current Scope of Tempest and Plugin framework.

- https://docs.openstack.org/tempest/latest/field_guide/index.html

- https://docs.openstack.org/tempest/latest/plugin.html



Next plan:

1. Tacker Tempest Pugin:

I am planing to add Tacker Tempest plugin framework in PTG and 
further my team will start adding the suitable Scenario tests. We are doing NFV 
PoC in NEC with manually testing. Our next goal is to automate that testing 
which can be useful in open way.



2. Stress Testing:

Tempest used to have stress tests but it is being moved out of Tempest due 
to scope limitation. Currently it is in private repo but this can be added as 
QA projects. I remember someone asked about this in Boston but never followed 
up. Further it can be extended to include NFV related stress testing also. Link 

Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test results dashboard

[morgan.richomme]

Hi

functest reporting shows what it is in test DB
if you see odl_l3, it means that odl_l3 scenarios have been triggerred 
over the last 10 days in CI


https://build.opnfv.org/ci/view/functest/job/functest-fuel-armband-virtual-daily-master/31/console

if only odl scenario are triggereg, reference to odl_l2 or odl_l3 will 
disappear automatically


/Morgan

On 13/09/2017 01:19, Alexandru Avadanii wrote:

Hi,
Fuel and Armband projects renamed the ODL-L3 scenario to simply ODL, and 
dropped the ODL-L2 scenarios, as described in [1].
I noticed that the Functest results dashboard pages [2, 3] still use the old 
naming scheme, although the new scenario is also listed.
Would it be possible to cleanup obsolete scenarios?

Thank you,
Alex

[1] https://jira.opnfv.org/browse/FUEL-279
[2] http://testresults.opnfv.org/reporting/master/functest/status-f...@x86.html
[3] 
http://testresults.opnfv.org/reporting/master/functest/status-f...@aarch64.html



--
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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