[opnfv-tech-discuss] Canceled: [stor4nfv] Invitation: Stor4NFV weekly project meeting

2018-02-04 Thread Wang, Shane 
BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Wang, Shane":MAILTO:shane.w...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='opnfv-te
 ch-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Gohad, Tu
 shar":MAILTO:tushar.go...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Li, Xiaoy
 an":MAILTO:xiaoyan...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='wangzhen
 gy...@cmss.chinamobile.com':MAILTO:wangzhengy...@cmss.chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Ren, Qiao
 wei":MAILTO:qiaowei@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='wanghui7
 1...@huawei.com':MAILTO:wanghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='heluwei@
 huawei.com':MAILTO:helu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='luo.kexu
 e...@zte.com.cn':MAILTO:luo.ke...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='haomai@x
 sky.com':MAILTO:hao...@xsky.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='liuyuan@
 cmss.chinamobile.com':MAILTO:liuy...@cmss.chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='liujunwe
 i...@cmss.chinamobile.com':MAILTO:liujun...@cmss.chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Skerry, B
 rian J":MAILTO:brian.j.ske...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='huangzhi
 p...@huawei.com':MAILTO:huangzhip...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='haojingb
 o...@huawei.com':MAILTO:haojin...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='mark.bei
 e...@dell.com':MAILTO:mark.bei...@dell.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='xudk1@le
 novo.com':MAILTO:xu...@lenovo.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='gulj1@le
 novo.com':MAILTO:gu...@lenovo.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='xie.xing
 g...@zte.com.cn':MAILTO:xie.xing...@zte.com.cn
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Kedalagud
 de, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Canio Ci
 llis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Maria To
 eroe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Seiler, G
 lenn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'GUPTA, A
 LOK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Bernier,
  Daniel'":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Alan McN
 amee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Frattura
 , David'":MAILTO:david.fratt...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='George Z
 hao':MAILTO:george.y.z...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Gabor Ha
 lász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Vul, Alex"
 :MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Cathy Zh
 ang':MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Alam, Ta
 imoor'":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Piyush S
 arwal':MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Ahmed El
 bornou (amaged)':MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Wanghui 
 (Leon, IT)'":MAILTO:leon.wang...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Chigang 
 (Justin)':MAILTO:chig...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Cazares, 
 Luz":MAILTO:luz.caza...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-US:Happy Chinese New Year!\n\nHi there\,\n\nShane W
 ang is inviting you to a scheduled Zoom meeting.\nJoin from PC\, Mac\, Lin
 ux\, iOS or Android:

Re: [opnfv-tech-discuss] [ovn4nfv] Request for PODs

2018-02-04 Thread Julien 
Hi Trinath,

Your requirements is not clear enough, can you give more detail information:
1. For development test or CI test?
2. What's the current status of ovn scenario with installer Apex and JOID?

You can bring this topic to INFRA WG meeting on Monday.

Regards/Julien


Trinath Somanchi 于2018年2月2日周五 下午7:49写道：

> Hi POD teams –
>
>
>
> Please help me find vPODs  with APEX for development and testing.
>
>
>
>
>
> / Trinath Somanchi,
>
> NXP SDN/NFV Team.
>
>
>
>
>
>
>
> *From:* Trinath Somanchi
> *Sent:* Tuesday, January 16, 2018 12:04 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [ovn4nfv] Request for PODs
>
>
>
> Hi-
>
>
>
> For project OVN4NFV, to test OVN scenarios We require JOID or APEX based
> POD(s).
>
>
>
> Kindly please let me know the procedure to apply.
>
>
>
> Thanking you.
>
>
>
> /
>
>   Trinath Somanchi,
>
>NXP SDN/NFV Team.
>
>
> ___
> 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] Could ways of working with testing frameworks be improved when working with master?

2018-02-04 Thread Wangwulin (Linda) 

Hi Manuel,

I am sorry for the inconvenience that utils removal and some updates in 
Functest have brought in to sfc and other users. We understand your concern.

Some internals out of Functest have been removed without warning, mainly 
because Functest prefers feature/companion projects to be in charge of their 
own code, scripts and scenarios, rather than providing some common 
functionalies. To be honest, we could not know exactly every method consumed by 
feature projects, but if we did, we must have informed you in advance, just 
like the change of openstack_utils. Even though we double-checked if they were 
used, we cared more about functest internal tests and Releng jobs. 
Unfortunately Releng-XCI has been a bit ignored, as we are not sure where to 
check the sfc jobs on XCI.

However, it would not bother more if we could initiate a wiki page listing all 
the methods to be deprecated (as Cedric proposed ) and add all the potential 
users as reviewers ( a new group for reviewing could be created) when 
publishing the related patches, eg,. "TEST_DB_URL", creds rename and something 
like that.

Nice weekend :)

Best Regards,
Linda


--
王戊林 Linda
M: +86-18560046533
E: wangwu...@huawei.com
产品与解决方案-云核心网NFV研究部
Products & Solutions-NFV Research Dept,CCN
From:cedric.olliv...@orange.com
To:Manuel Buil,OPNFV-TECH-DISCUSS OPNFV,
Date:2018-02-03 00:33:27
Subject:Re: [opnfv-tech-discuss] Could ways of working with testing frameworks 
be improved when working with master?

No, “blocking innovation” was simply related to a possible inability to change 
our internal methods (timethis()) which are out of our Framework.
You highlighted a real problem: we need to remove obsolete utils which don’t 
meet our criteria and may be possibly reused by others.
Cleaning our tree could create side effects in OPNFV projects even if we mostly 
double check anyway.
Yes we should have warned about the next end user changes: TEST_DB_URL and 
creds (and we previously removed prepare_env).
For the previous release, we have simply updated a wiki page (Running Alpine 
container) for all the changes from an end-users POV.
https://wiki.opnfv.org/display/functest/Run+Alpine+Functest+containers
Why not creating a new wiki page for master as well.
But I consider gerrit as the best place simply because it would be delayed by 
mails or by wiki pages.
That may be considered as the cost to select master (it’s also the key 
challenges of XCI ; for instance odl mechanism driver and ODL neutron API may 
be temporarily incompatible if both are master).
The issue is raised because we simply updated Functest and Releng jobs to avoid 
breaking gate but that’s true that we forgot releng-xci.
But such changes rarely happened: here we are integrating the first Kubernetes 
testcases (creds) and we are preparing Xtesting.
Have a nice weekend,
Cédric
De : Manuel Buil [mailto:mb...@suse.com]
Envoyé : vendredi 2 février 2018 16:25
À : OLLIVIER Cédric IMT/OLN; OPNFV-TECH-DISCUSS OPNFV
Objet : Re: [opnfv-tech-discuss] Could ways of working with testing frameworks 
be improved when working with master?
Hi Cedric,
I probably expressed myself wrongly since you understood that I intent to block 
innovation and host SFC functions in functest but that is not my intention. My 
objective with this mail is to check if there exists (perhaps not), an 
efficient way for testing frameworks to communicate in advance important 
changes which will break things in the projects using those frameworks. I have 
a very good example: functest warned us during the Euphrates cycle that 
openstack_utils was not going to be maintained anymore and that we should stop 
using that and migrate to an alternative during the Fraser development cycle. 
You guys even suggested us an alternative (SNAPs). That was really helpful and 
we were able to plan the task accordingly in our SFC backlog and right now we 
are 100% compatible with SNAPs. Note that as far as I know, you haven't removed 
the openstack_utils yet (or at least we were able to use it while doing the 
migration).
However, during the last weeks, some functest changes broke our testing (apart 
from that function I mentioned as an example):
* It seems like the openrc file changed the name in the functest container and 
/home/opnfv/functest/conf/openstack.creds does not work anymore
* TEST_DB_URL is now an environment variable and cannot be consumed from the 
functest config file
To understand how to fix those, we had to go into the IRC channel and ping you. 
If this is only SFC guys doing it, I guess we could continue with option C, but 
if now more users start to work on master (XCI and APEX), I suspect the number 
pings you will receive will increase. And I guess the same will happen with 
yardstick, that's why I don't think this is a SFC <--> Functest issue but a 
more general ways of working issue.
Regards,
Manuel
On Fri, 2018-02-02 at