Re: [opnfv-tech-discuss] [dovetail] proposal: information sharing with OpenStack RefStack and Interop people

[SerenaFeng(zte)]

Hi all,

Currently, I am working on the authentication of TestAPI, a simple one is
implemented
based on Refstack, if there are some help from Refstack would be very
grateful.
Which channel will the meeting be held, dovetail weekly meeting?

BRs
Serena

On Fri, May 19, 2017 at 4:48 PM Leo Wang  wrote:

> +1
>
>
>
> --
> *From:* Georg Kunz 
> *Sent:* Thursday, May 18, 2017 9:37 PM
> *To:* Dave Neary; Cooper, Trevor; Wenjing Chu;
> opnfv-tech-discuss@lists.opnfv.org
> *Cc:* Tianhongbo; z...@redhat.com; Fu Qiao; Leo Wang; 'Lincoln Lavoie';
> Jose Lausuch
>
> *Subject:* [dovetail] proposal: information sharing with OpenStack
> RefStack and Interop people
> Hi all,
>
> We are trying very hard to establish processes, guidelines and best
> practices for running the OPNFV certification program - on our own and with
> guidance from C&C. I believe we can much better leverage existing knowledge
> and experience from related communities. In this context, I'd like to make
> a proposal.
>
> As mentioned during last week's call, Jose and I had very insightful
> conversations with the relevant folks from the OpenStack certification
> domain: Catherine Diep (RefStack PTL), Egle Sigler (co-chair Interop
> working group) and Mark Voelker (co-chair Interop working group). We have
> developed a good relationship with them and they are willing and interested
> in sharing their experience in running the OpenStack certification /
> interop program with us.
>
> My proposal: I'd like to invite the aforementioned persons to one or two
> of our project meetings and let them share their experience, best practices
> and guidelines with us. Based on these insights, we can then define, adapt
> and optimize our own processes to suite our needs. The latter is important
> - I don't think we can simply adopt their existing processes, but we should
> learn about why existing processes in the OpenStack domain have evolved to
> their current form. The OpenStack certification program was started in 2013
> and officially launched in 2015 - so there was serious effort and time
> involved. We should try to build upon existing knowledge without having to
> go through the same learning phase as the OpenStack folks.
>
> This requires some thoughtful timing, of course: In the very short term
> future, we need to focus on finalizing the first iteration of the OPNFV
> certification program. My proposal is not intending to undermine this. On
> the contrary. However, the earlier we get additional insight, the better we
> can define our own processes.
>
> I don't want to put this on the agenda for tomorrow's meeting (for obvious
> reasons), but instead discuss this by email.
>
> @Wenjing / Hongbo: can we dedicate a future meeting to such a sharing
> session with the OpenStack folks?
>
> Best regards
> Georg
>
> > -Original Message-
> > From: Dave Neary [mailto:dne...@redhat.com ]
> > Sent: Thursday, May 18, 2017 9:54 PM
> > To: Cooper, Trevor ; Wenjing Chu
> > ; opnfv-tech-discuss@lists.opnfv.org
> > Cc: Tianhongbo ; z...@redhat.com; Fu
> > Qiao ; Leo Wang ;
> > 'Lincoln Lavoie' ; Georg Kunz
> > 
> > Subject: Re: [dovetail] Weekly meeting agenda for May 19
> >
> > Hi,
> >
> > My suspicion is that the entire meeting will be taken up with agenda
> items 2
> > and 3 from Wenjing.
> >
> > We need alignment around the test areas, and test case review. We also
> > need to clarify what, if anything, we need to get in terms of guidance
> from
> > C&C. I suggest inverting these agenda items, because the second will take
> > less time than the first.
> >
> > Thanks,
> > Dave.
> > On 05/18/2017 02:38 PM, Cooper, Trevor wrote:
> > > I would like to propose some topics ... a few minutes for each should
> be
> > > fine to decide if we can defer or need a decision
> > >
> > >
> > >
> > > -  H/w resources for Dovetail
> > >
> > > -  Dovetail artifact versions and release schemes
> > >
> > > -  Test catalog domains relevant to compliance
> > >
> > > -  Stability test criteria
> > >
> > >
> > >
> > > /Trevor
> > >
> > >
> > >
> > >
> > >
> > > *From:* Wenjing Chu [mailto:wenjing@huawei.com
> ]
> > > *Sent:* Wednesday, May 17, 2017 4:14 PM
> > > *To:* opnfv-tech-discuss@lists.opnfv.org
> > > *Cc:* Dave Neary ; Tianhongbo
> > > ; Cooper, Trevor
> > > ; z...@redhat.com; Fu Qiao
> > > ; Leo Wang ;
> > 'Lincoln
> > > Lavoie' ; Georg Kunz 
> > > *Subject:* [dovetail] Weekly meeting agenda for May 19
> > >
> > >
> > >
> > >
> > >
> > > Please comment if the following agenda makes sense:
> > >
> > >
> > >
> > > 1.   Welcome new committers and where we need immediate new
> > > contribution and attention
> > >
> > > 2.   Preparation for tsc review on 5/30
> > >
> > > 3.   Ask - what we need to ask from c&c and board? How should we
> > > take on the administrative side of tasks. Also the Danube addendum for
> > 5/22.
> > >
> > > 4.   Naming convention of test cases
> > >
> > > 5.   Vendor lab tes

Re: [opnfv-tech-discuss] [dovetail] Request for a slot in tomorrow's weekly call

[SerenaFeng(zte)]

Hi Srikanth & Tim,

Thanks for sharing the slides, I am also looking forward to having a copy.

BRs
Serena

On Tue, Aug 1, 2017 at 12:41 AM Srikanth Vavilapalli <
srikanth.vavilapa...@ericsson.com> wrote:

> Hi
>
>
>
> Attached the slide deck…
>
>
>
> Thanks
>
> Srikanth
>
>
>
> *From:* Zenghui Shi [mailto:z...@redhat.com]
> *Sent:* Sunday, July 30, 2017 7:31 PM
>
>
> *To:* Srikanth Vavilapalli 
> *Cc:* Wenjing Chu ; Tianhongbo <
> hongbo.tianhon...@huawei.com>; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [dovetail] Request for a slot in
> tomorrow's weekly call
>
>
>
> Hi Srikanth & Tim,
>
>
>
> Thanks for sharing the findings on test gaps in weekly dovetail meeting!
> Is it possible the slides can be shared so that anyone who's interested in
> can get to understand and follow-up on some of the test items?
>
> Regards,
> zenghui
>
>
>
> On Thu, Jul 27, 2017 at 11:18 PM, Srikanth Vavilapalli <
> srikanth.vavilapa...@ericsson.com> wrote:
>
> Hi
>
>
>
> In tomorrow’s weekly call, Tim and myself (from Ericsson) wanted to share
> our findings on test gaps in basic cloud capability, security and High
> availability areas.
>
>
>
> Can you plz add to the agenda if we can get some time for this?
>
>
>
> Thanks
>
> Srikanth
>
>
>
>
>
>
>
>
> ___
> 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] [dovetail] weekly call agenda 8/11

[SerenaFeng(zte)]

Hi,

FYI, I added ZTE to the table as offering an OPNFV distro POD for the beta
trial.

BR
Serena

On Fri, Aug 18, 2017 at 8:42 AM Tianhongbo 
wrote:

> Thanks
>
>
>
> Hongbo
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Cooper, Trevor
> *Sent:* 2017年8月18日 7:29
> *To:* Wenjing Chu ; Lincoln Lavoie <
> lylav...@iol.unh.edu>
>
>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> Done https://wiki.opnfv.org/display/dovetail/Dovetail+Beta
>
>
>
> Trevor
>
>
>
> *From:* Wenjing Chu [mailto:wenjing@huawei.com
> ]
> *Sent:* Thursday, August 17, 2017 9:53 AM
> *To:* Lincoln Lavoie 
> *Cc:* Cooper, Trevor ; SULLIVAN, BRYAN L (BRYAN
> L) ; Dave Urschatz <
> dave.ursch...@cengn.ca>; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> Very well said. Let me amend it. Thanks.
>
>
>
> Wenjing
>
>
>
> *From:* Lincoln Lavoie [mailto:lylav...@iol.unh.edu ]
>
> *Sent:* Thursday, August 17, 2017 5:31 AM
> *To:* Wenjing Chu 
> *Cc:* Cooper, Trevor ; SULLIVAN, BRYAN L (BRYAN
> L) ; Dave Urschatz <
> dave.ursch...@cengn.ca>; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> It's not suppose to be "only bugs from beta testers," but beta testers are
> expected to be the primary source of bug reports.  During the beta period,
> no new tests or features would be added, only bug fixes.
>
>
>
> Cheers,
> Lincoln
>
>
>
> On Thu, Aug 17, 2017 at 2:25 AM, Wenjing Chu 
> wrote:
>
> Trevor & Bryan,
>
>
>
> Thanks for the interest in participating in Beta. It’s great to see the
> leaders stepping up.
>
>
>
> I think the quoted line meant to say that bugs encountered in beta have
> priority and the immediate attention, esp. if/when we have to choose.
> Another point is that during beta we have interests in stability as well,
> fixing non-critical bugs already known before the beta may cause more harm
> than good. That’s how I understood it as a developer.
>
>
>
> Lincoln, do you like to add comment as it’s from one of your suggestions?
>
>
>
> We can discuss & rephrase it as appropriate.
>
>
>
> Wenjing
>
>
>
> *From:* Cooper, Trevor [mailto:trevor.coo...@intel.com]
> *Sent:* Wednesday, August 16, 2017 7:01 PM
> *To:* SULLIVAN, BRYAN L (BRYAN L) ;
> Wenjing Chu ; Dave Urschatz <
> dave.ursch...@cengn.ca>; Lincoln Lavoie 
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
>
>
> *Subject:* RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> I added Intel to the table as offering a Pharos POD for the beta trial.
>
>
>
> “Only bugs submitted by the beta testers will be reviewed and accepted
> during Beta” … why would we only fix bugs reported by beta testers? ALL
> reported bugs should be investigated and prioritized.
>
>
>
> /Trevor
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> ] *On Behalf Of *SULLIVAN,
> BRYAN L (BRYAN L)
> *Sent:* Wednesday, August 16, 2017 10:14 AM
> *To:* Wenjing Chu ; Dave Urschatz <
> dave.ursch...@cengn.ca>; Lincoln Lavoie 
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> I added the table for beta participants.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT&T
>
>
>
> *From:* Wenjing Chu [mailto:wenjing@huawei.com
> ]
> *Sent:* Monday, August 14, 2017 10:44 PM
> *To:* Dave Urschatz ; Lincoln Lavoie <
> lylav...@iol.unh.edu>; SULLIVAN, BRYAN L (BRYAN L) <
> bryan.sulli...@research.att.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> Here is the Beta test page:
> https://wiki.opnfv.org/display/dovetail/Dovetail+Beta
> 
>
> I think I summarized most of the comments I received so far. Please let me
> know if I missed anything. Additional comments welcome and we’ll discuss in
> this week’s call.
>
> Again, thanks Bryan and Lincoln for your suggestions.
>
>
>
> Dave,
>
> On your first two points, please refer to the above wiki page.
>
> For the third point, yes, current testing assumes Pharos pods for the
> system under test.
>
>
>
> Wenjing
>
>
>
> *From:* Wenjing Chu
> *Sent:* Monday, August 14, 2017 4:47 PM
> *To:* 'Dave Urschatz' ; Lincoln Lavoie <
> lylav...@iol.unh.edu>; SULLIVAN, BRYAN L (BRYAN L) <
> bryan.sulli...@research.att.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
>
>
> Just an ack that I’ll be populating a wiki page today incorporating
> discussions a

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[SerenaFeng(zte)]

Hi,

Thanks Julien!
Yes, I accept the nomination.

BRs
Serena

On Fri, Sep 8, 2017 at 10:37 PM Raymond Paik 
wrote:

> Thanks Julien...
>
> Serena, do you accept the nomination?
>
> Ray
>
>
> On Fri, Sep 8, 2017 at 6:50 AM, Julien  wrote:
>
>> Hi all,
>>
>> I would like to nominate Serena (ZTE) for the TSC at-large
>> election. She has done a great work in Functest, Releng and QTIP project.
>> As an active committer, she is in charge of TestAPI development, which is
>> consumed by more and more projects, from the basic data store to cli, web
>> portal and CI/CD procedure. She is also an active mentor in community, and
>> she has worked with intern in several projects. I believe she has enough
>> skills and capability for TSC member.
>>
>> BR/Julien
>>
>> Raymond Paik 于2017年9月4日周一 上午1:43写道：
>>
>>> All,
>>>
>>> I'm kicking off the nomination process for Committers-at-Large TSC
>>> (electing 5 members) plus the Committer Board (electing 1) elections.
>>>
>>> The list of eligible committers who can run for & vote in both elections
>>> are posted here, and I want to encourage all eligible committers to
>>> nominate community members who can represent the OPNFV technical community
>>> in both the TSC and the Board.  Self nominations are also welcome.   As I
>>> mentioned earlier in the week, I hope to see a diverse group of community
>>> members represented--in terms of geography, gender, projects,  service
>>> providers/vendors, etc.--in the nominations.
>>>
>>> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing
>>> lists by 5pm Pacific Time on September 8th (Friday).  You are welcome to
>>> reply to this email or if you're sending out a separate note, please
>>> include phrases like "Committer Board nomination" or "Committer-at-Large
>>> TSC nomination" in email subjects.  In nomination statements, please list
>>> the following information:
>>>
>>>- Which election (TSC vs. Board) the nomination is for
>>>- Name of the nominee
>>>- Organization
>>>- A brief description of nominee's qualifications
>>>
>>> As nominations are accepted, I will add them to this page
>>> .
>>> There will be separate Condorcet ballot for these two elections, and they
>>> will be sent out by September 11th.
>>>
>>> Thanks,
>>>
>>> Ray
>>>
>>> ___
>>> opnfv-tsc mailing list
>>> opnfv-...@lists.opnfv.org
>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>>>
>>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail] Dovetail team gerrit group

[SerenaFeng(zte)]

Hi Georg,

Would you please add me to the group?
My email used in Gerrit is: feng.xiao...@zte.com.cn

BRs
Serena

On Sat, Sep 9, 2017 at 2:21 AM Georg Kunz  wrote:

> Hi Dovetailers,
>
>
>
> As briefly discussed during today’s project meeting, I have created a
> group called “Dovetail Team” in Gerrit [1] to simplify adding reviewers to
> patches. Right now, the group contains the committers listed in the
> project’s INFO file [2]. However, I named the group “Dovetail Team” instead
> of “Dovetail Committers” to keep it open for everyone interested in
> reviewing our work.
>
>
>
> So, if you want to be included in this group, let me know (or maybe you
> can even add yourself using the link below).
>
>
>
> [1] https://gerrit.opnfv.org/gerrit/#/admin/groups/63,members
>
> [2]
> https://gerrit.opnfv.org/gerrit/gitweb?p=dovetail.git;a=blob;f=INFO;h=470b7ca884bcb76f73fee7ba7772fa857e1b0373;hb=refs/heads/master
>
>
>
> Cheers
>
> Georg
> ___
> 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] [qtip] New PTL of QTIP project

[SerenaFeng(zte)]

Congrats Zhihui.

I am sure you will be a great PTL just like Yujun.

BRs
Serena

On Tue, Oct 24, 2017 at 9:50 AM Yujun Zhang (ZTE) 
wrote:

> I am happy to announce that Zhihui Wu is elected as new PTL for QTIP
> project[1].
>
> Congratulations, Zhihui
>
> [1]: https://gerrit.opnfv.org/gerrit/#/c/45157/
>
> On Mon, Oct 16, 2017 at 9:13 AM Yujun Zhang (ZTE) <
> zhangyujun+...@gmail.com> wrote:
>
>> QTIP committers
>>
>> There have been no further nominations for the QTIP PTL position.
>> Therefore Zhihui Wu is the sole candidate.
>>
>> To provide a record of this and acknowledgement from QTIP committers
>> please vote on gerrit[1] indicating your approval/disapproval (+2, -2) for
>> Zhihui to take over as PTL effective from the Fraser release.
>>
>> [1]: https://gerrit.opnfv.org/gerrit/#/c/45157/
>>
>> On Mon, Oct 9, 2017 at 8:05 PM 吴之惠  wrote:
>>
>>>  I would like to accept the nomination for QTIP PTL and only hope that
>>> I can be an excellent PTL like Yujun. :-)
>>>
>>>
>>> Yujun Zhang (ZTE) 于2017年10月9日周一 下午4:32写道：
>>>
 All,

 I'm opening the nomination period for QTIP PTL election. You may
 nominate yourself or others *before Oct 15th*.

 I would like to nominate Zhihui WU (wu.zhih...@zte.com.cn) as new PTL
 for QTIP. She has been active in the project since D release and make a
 major contribution to it. I believe she will lead the project to a new
 level.

 --
 Yujun
 --
 Yujun Zhang

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

>>> --
>> Yujun Zhang
>>
> --
> Yujun Zhang
> ___
> 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] [Functest] PTL transfer

[SerenaFeng(zte)]

+1

On Tue, Nov 14, 2017 at 4:06 PM Wangwulin (Linda) 
wrote:

> +1
>
>
>
> *From:* Kosonen, Juha (Nokia - FI/Espoo) [mailto:juha.koso...@nokia.com]
> *Sent:* 2017年11月14日 14:39
> *To:* Tikkanen, Viktor (Nokia - FI/Espoo) ;
> Valentin Boucher ; Jose Lausuch <
> jalaus...@suse.com>; TSC OPNFV ; TECH-DISCUSS
> OPNFV ; OLLIVIER Cédric IMT/OLN <
> cedric.olliv...@orange.com>; Serena Feng ;
> Wangwulin (Linda) ; RICHOMME Morgan IMT/OLN <
> morgan.richo...@orange.com>; Helen Yao ; Meimei <
> mei...@huawei.com>
> *Subject:* Re: [Functest] PTL transfer
>
>
>
> +1
>
>
> --
>
> *From:* Tikkanen, Viktor (Nokia - FI/Espoo)
> *Sent:* Tuesday, November 14, 2017 07:05
> *To:* Valentin Boucher; Jose Lausuch; TSC OPNFV; TECH-DISCUSS OPNFV;
> OLLIVIER Cédric IMT/OLN; Serena Feng; wangwulin; Kosonen, Juha (Nokia -
> FI/Espoo); RICHOMME Morgan IMT/OLN; Helen Yao; Meimei
> *Subject:* RE: [Functest] PTL transfer
>
>
>
> +1
>
>
>
> *From:* Valentin Boucher [mailto:valentin.bouc...@kontron.com
> ]
> *Sent:* Monday, November 13, 2017 7:13 PM
> *To:* Jose Lausuch ; TSC OPNFV <
> opnfv-...@lists.opnfv.org>; TECH-DISCUSS OPNFV <
> opnfv-tech-discuss@lists.opnfv.org>; OLLIVIER Cédric IMT/OLN <
> cedric.olliv...@orange.com>; Serena Feng ;
> wangwulin ; Kosonen, Juha (Nokia - FI/Espoo) <
> juha.koso...@nokia.com>; RICHOMME Morgan IMT/OLN <
> morgan.richo...@orange.com>; Tikkanen, Viktor (Nokia - FI/Espoo) <
> viktor.tikka...@nokia.com>; Helen Yao ; Meimei <
> mei...@huawei.com>
> *Subject:* RE: [Functest] PTL transfer
>
>
>
> +1
>
>
>
> *From:* Jose Lausuch [mailto:jalaus...@suse.com ]
> *Sent:* 13 novembre 2017 04:19
> *To:* TSC OPNFV; TECH-DISCUSS OPNFV; OLLIVIER Cédric IMT/OLN; Serena
> Feng; wangwulin; Kosonen, Juha (Nokia - FI/Espoo); RICHOMME Morgan IMT/OLN;
> Valentin Boucher; viktor.tikka...@nokia.com; Helen Yao; Meimei
> *Subject:* [Functest] PTL transfer
>
>
>
> Hi,
>
>
>
> It has already been 2 releases being PTL of Functest, and it is time for
> me to transfer the role to other team members. It has been an honour
> holding this position trying to drive things in the right direction and I
> am very proud of the team and what we are achieving. This is not a goodbye
> as I will be still a committer and the interface to the TSC.
>
>
>
> After talking to the committers of the project, only one person has
> volunteered to take over this position, so there is no need for running
> formal elections. Therefore, I would like to propose Cedric Ollivier from
> Orange who is very active in the project and is helping it evolve with his
> good expertise as a software developer. His engagement in Functest and the
> whole community is very valuable and I believe he will fulfil the required
> expectations of the PTL role.
>
>
>
> Please Functest committers, vote (+1, 0 -1) answering to this email thread.
>
> Eligible voters are listed in the INFO file as committers:
> https://git.opnfv.org/functest/tree/INFO
>
>
>
> Regards,
>
> Jose
>
>
>
>
>
>
>
>
> ___
> 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 gerrit page update

[SerenaFeng(zte)]

+1 for both

Great to have the links, so no need to remember and input manually so many
URLs.

BRs
Serena

On Thu, Jan 18, 2018 at 12:36 AM Ryota Mibu  wrote:

> Julien,
>
>
>
>
>
> I mean the #2 propose is to add links on top of all pages in gerrit. And
> by those links, you can go JIRA, Wiki and other pages useful for
> developers. You can see it in ONAP and ODL gerrit which Trevor Bramwell is
> pointing [1,2].
>
>
>
>
>
> BR,
>
> Ryota
>
>
>
> *From:* Julien [mailto:julien...@gmail.com]
> *Sent:* Wednesday, January 17, 2018 12:12 AM
> *To:* Juvonen, Tomi (Nokia - FI/Espoo) 
> *Cc:* Mibu Ryota(壬生 亮太) ;
> opnfv-tech-discuss@lists.opnfv.org
> *Subject:* ##freemail## Re: [opnfv-tech-discuss] opnfv gerrit page update
>
>
>
> Hi Royta,
>
>
>
> +1 for the logo
>
>
>
> For links, I wonder shall we add a link to the website or add the links in
> each patch?
>
> In Gerrit, we can add "JIRA: PROJECT_NAEM-xxx" to track the Jira ticket. I
> don't know how to track others. It's useful to support in each patch.
>
>
>
>
>
> Juvonen, Tomi (Nokia - FI/Espoo) 于2018年1月16日周二 下午
> 3:07写道：
>
> +1
>
> I think this is a create idea. Already using too many open tabs in browser
> in daily work.
>
> Br,
> Tomi
>
> > -Original Message-
> > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-
> > boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
> > Sent: Monday, January 15, 2018 5:57 PM
> > To: opnfv-tech-discuss@lists.opnfv.org
> > Subject: [opnfv-tech-discuss] opnfv gerrit page update
> >
> > Hi OPNFV developers,
> >
> >
> > I'd like to gather comments on the following ideas for our gerrit page
> update
> > (https://gerrit.opnfv.org/gerrit/).
> >
> >   1. Logo in gerrit page
> >
> > Add OPNFV logo in our gerrit page, so that we can easily identify
> OPNFV gerrit
> > page among other gerrit pages of other upstream projects. Icon in
> browser tab
> > should be changed to OPNFV leaf logo as well.
> >
> >   2. Links to developer pages
> >
> > Add links to Jira, Jenkins, Artifacts and other developer pages.
> That will enable
> > developer to use the gerrit page as a main portal site for day-to-day
> > development, rather than Jira. What we can expect more is an increase of
> > reviews, which is very important in open source projects.
> >
> > I believe these proposals are bringing only benefits. But if there is a
> problem
> > with such updates, we need to know before bad things happen.
> >
> >
> > Thanks,
> > Ryota
> >
> > > -Original Message-
> > > From: Trevor Bramwell via RT [mailto:
> opnfv-helpd...@rt.linuxfoundation.org]
> > > Sent: Saturday, January 13, 2018 3:15 AM
> > > To: Mibu Ryota(壬生 亮太) 
> > > Subject: [OPNFV Helpdesk #50899] opnfv logo in gerrit page
> > >
> > > Hi Ryota,
> > >
> > > I think this is a great idea! It should probably be floated by the TSC
> first so we
> > don't surprise anyone with changes
> > > to the Gerrit UI.
> > >
> > > My idea would be to add not just the logo but also link to Jira,
> Jenkins,
> > Artifacts, etc.
> > >
> > > We actually do this for a couple other networking projects (ODL[1],
> ONAP[2],
> > etc.) so I definitely think they'll be receptive
> > > as it helps align us with the networking umbrella projects.
> > >
> > > Would you mind getting it added to the agenda for the next TSC call, or
> > starting a discussion on the mailing list, please?
> > >
> > > Regards,
> > > Trevor Bramwell
> > >
> > > [1] https://git.opendaylight.org/gerrit/#/q/status:open
> > > [2] https://gerrit.onap.org/r/#/q/status:open
> > >
> > > On Wed Jan 10 00:17:54 2018, r-m...@cq.jp.nec.com wrote:
> > > > Hi,
> > > >
> > > >
> > > > Could you add OPNFV logo(s) in our gerrit page?
> > > >
> > > > This will help many developers find out OPNVF gerrit tab in their
> > > > browser quickly, especially developers who uses other project's
> > > > gerrit.
> > > >
> > > > Note, this can be a low priority request. I don't know how other
> > > > developers think though.
> > > >
> > > >
> > > > I'm not sure how we can config, but [1] tells that we need to config
> > > > /etc/gitweb.conf file and set '$logo' and '$favicon'. My suggestion
> of
> > > > images is the following:
> > > >
> > > > [logo] https://www.opnfv.org/wp-
> > > > content/uploads/sites/12/2016/11/opnfv_logo_wp.png
> > > >
> > > > [favicon]
> > > >
> > https://pbs.twimg.com/profile_images/606521736071401472/iRMp9gPD_400x
> > 4
> > > > 00.jpg
> > > >
> > > >
> > > > [1] https://gerrit-review.googlesource.com/Documentation/config-
> > > > gitweb.html
> > > >
> > > >
> > > > BR,
> > > > 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
>
> _

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[SerenaFeng(zte)]

Hi David & Jack,

Thanks for mentioning the task, an interface for collecting deployment
results has been ready in TestAPI[1],
the Macro for pushing deployment result is also ready by Jelien[2], I
believe it will facilitate all the installers' work,
currently, Julien is working on pushing daisy results to TestAPI leveraging
that Macro, I think it will be finished soon.

And regarding how to show all the information in a table, I suggest we can
take a look at Jack's proposal first.

@Jack, a few comments:
1. what's the opinion of jenkins id?
2. for a scenario-installer combination, some will not run once in a
day(trigger multiple times or run in multiple pods),
in this case, a simple pass/fail will be too vague, and to facilitate
the support of data iteration, I would suggest
leveraging 8/9/10(8 passed, 9 triggered, 10total), delete the
final statistic line
3. how about adding a healthcheck column(functest-healthcheck test cases),
to see if the installer meets the milestone 3.0


[1]: https://gerrit.opnfv.org/gerrit/#/c/49895/
[2]: https://gerrit.opnfv.org/gerrit/#/c/48515/

BRs
Serena

On Mon, Jan 22, 2018 at 5:02 PM chenjiankun  wrote:

> Thanks, David.
>
>
>
> According your descriptions, I have created a demo table as below(wish I
> do not misunderstanding your meaning):
>
>
>
> *scenario *
>
> *date *
>
> *Jenkins *
>
> *Version *
>
> *Installer *
>
> *Deployment *
>
> *Functest *
>
> *yardstick *
>
> os-nosdn-nofeature-ha
>
> 2018-01-21
>
> Jenkins id
>
> euphrates
>
> compass
>
> pass
>
> pass
>
> pass
>
> 2018-01-21
>
> Jenkins id
>
> euphrates
>
> compass
>
> fail
>
> not trigger
>
> not trigger
>
> statistic
>
> 8/9/10
>
> (pass:8,triggered:9, total:10)
>
> 6/7/8
>
> 6/7/8
>
>
>
>
>
> This last line in table body is the statistics information, and lines
> above are the detailed information(and it can be folded).
>
> The score 8/9/10 is pass/triggered/total. Total means should run,
> triggered means actually run.
>
> Also we can add three filters:
>
>
>
> If you select installer as compass, then will show all data related to
> compass.
>
> Iterations means last x data points to be displayed.
>
>
>
> Does this table satisfied your requirements?
>
>
>
> BRs,
>
> Jack Chan
>
> *发件人:* David McBride [mailto:dmcbr...@linuxfoundation.org]
> *发送时间:* 2018年1月20日 3:07
> *收件人:* chenjiankun
> *抄送:* TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao,
> Sridhar; OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang (Gabriel);
> ALFRED C 'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com; Liyin
> (Ace); Wangwulin (Linda); georg.k...@ericsson.com; Serena Feng; Julien
> *主题:* Re: [opnfv-tech-discuss][test-wg]Requirements for test resources
> collection
>
>
>
> +Serena, Julien
>
>
>
> Thanks, Jack.
>
>1. Data reported per scenario (i.e., jenkins job, deployment,
>functest, yardstick, etc. displayed together for each scenario) instead of
>separate test silos.
>2. Include deployment results
>3. Include all Jenkins job results (failure to start, failure to
>complete, etc.)
>4. Clear date/time stamps for every data point
>5. Display the data above for the last x data points (e.g., 4, 5, 10 ?)
>6. Use an easy-to-understand, unified scoring method for all test
>frameworks.
>
> As I mentioned, yesterday, Julien and Serena have been working on this, as
> well.  Julien has developed a macro
>  to enable consolidation of
> all results per scenario. He is intending to use the Daisy installer as a
> platform to verify the macro, which then can be adapted to other installers.
>
>
>
> In addition, Serena has agreed to help manage an intern who can assist
> with the project.  I have an action to create an intern proposal for that
> purpose.
>
>
>
> David
>
>
>
> On Fri, Jan 19, 2018 at 1:23 AM, chenjiankun 
> wrote:
>
> Hi,
>
>
>
> As we discussed last test working group weekly meeting, we want to do test
> resources aggregation.
>
> We plan to offer a new friendly web portal which contain all existing test
> resource and more functions.
>
>
>
> I have a broad classification as bellow:
>
> 1.   Data analysis
>
> a) Reporting(existing, For release)
>
> b) Bitergia(existing)
>
> c) Grafana(existing, For detailed test results)
>
> d) ……(maybe we can develop more tools to show our detailed test
> results)
>
> 2.   Test working group information(What information you want to see
> from test working group? Test working group event? Event of each project?)
>
> 3.   Tools of each project(Need each project member to complete)
>
> 4.   ……(waiting for you to improve)
>
>
>
>
>
> This email is aim at collecting requirements for test resources, so if you
> have any idea about classification, existing tools(such as reporting), new
> functions you want, please do not hesitate to comment here.
>
> As Gabriel said, he will create a new wiki page for test resources
> collection, so you can also commen

Re: [opnfv-tech-discuss] [opnfv-tsc] [doctor] Stepping down

[SerenaFeng(zte)]

Hi Carlos,

Nice meeting you and traveling with you. Wishing you all the best in your
future.

BRs
Serena


On Tue, Jan 23, 2018 at 8:39 PM Ryota Mibu  wrote:

> Hi Carlos,
>
>
>
>
>
> Thank you for all your works in the project and taking polite way in
> leaving. Your resignation process is running at
> https://gerrit.opnfv.org/gerrit/50989 .
>
>
>
>
>
> Best regards,
>
> Ryota
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Juvonen, Tomi
> (Nokia - FI/Espoo)
> *Sent:* Tuesday, January 23, 2018 1:39 PM
> *To:* Carlos Gonçalves ;
> opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [doctor] Stepping down
>
>
>
> Hi Carlos,
>
>
>
> Thanks for your great effort to Doctor, we will surely be missing you. It
> has been very nice to work with you and hoping all the best with your new
> challenges.
>
>
>
> Currently have some Doctor design under work, so will not be in Dublin,
> but there will surely be event to catch that beer.
>
>
>
> Best regards,
>
> Tomi
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> ] *On Behalf Of *Carlos
> Gonçalves
> *Sent:* Monday, January 22, 2018 10:21 AM
> *To:* opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] [doctor] Stepping down
>
>
>
> Hi Doctor team, OPNFV TSC,
>
>
>
> Due to a change in my professional affiliation I stopped contributing to
> the project. I don't think my current position will realistically give me
> enough time to pursue other interests in OPNFV. Therefore, I would like to
> step down and resign from the role of committer.
>
>
>
> I would like to express my sincere gratitude for having had the
> opportunity to meet and work alongside many talented people in the Doctor
> project and in OPNFV in general.
>
>
>
> In case you're attending the OpenStack Rocky PTG in Dublin next month,
> drop me a note and let's grab a beer (or two).
>
>
>
> LinkedIn: https://www.linkedin.com/in/carloseduardogoncalves/
>
>
>
> All the best to you all!
>
>
>
> Cheers,
>
> Carlos
>
>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[SerenaFeng(zte)]

Hi Jack

Eventually, we hope all the installers push their deployment results to
TestAPI, in the current stage, we just leverage Daisy to have a try and
find a common framework to achieve that, we will promote it to other
installers soon after it works.

In terms of Jenkins id, almost all the installers leverage muti-job to
manage deployment and drive test projects. there is an entry job to control
all the jobs, such as daisy-os-nosdn-nofeature-ha-baremetal-daily-master
<https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-daily-master/>,
maybe we can leverage the combination of the Jenkins job and build_id
daisy-os-nosdn-nofeature-ha-baremetal-daily-master_185
<https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-daily-master/185/>(or
jest the Jenkins job) to link to the Jenkins. As for naming, instead of
'Jenkins' I would recommend using 'Job_name', because, in zuulv3, Jenkins
will be discarded, but the job idea will be left(maybe in some other way)

For the status show, if only show the last and latest *one* iteration,
simple pass/fail is fine, or else multi-results will be included, I don't
recommend that. Personally, my suggestion is either integrate last one
iteration into last x iterations, all use statistics to show the results,
or separate into two pages: the current status(simple pass/fail) and the
history statistic status(8/9/10).

For Functest health check, Sure, Functest reports per execution result per
test case separately, we can get them from TestAPI, there's no problem with
that. But for health check actually includes 3 test
cases(connection_check/api_check/snaps_health_check), we need to cope with
that carefully.


BRs
Serena

On Sat, Jan 27, 2018 at 11:42 PM Julien  wrote:

> Hi Jack,
>
> I have finished the macro, but it failed for a Jenkins plugin is missing.
> I cc the issue email to you, which will be discussed in the infra meeting.
>
> BR/Julien
>
> David McBride 于2018年1月27日周六 上午12:13写道：
>
>> +Julien
>>
>> Jack,
>>
>> I like the table format and the filtering options that you proposed.
>> Also +1 to Serena's suggestion to break out the health check data.
>>
>> I think that Julien is working on a Jenkins macro to enable the test API
>> to retrieve the "jenkins id".  Julien - please confirm.
>>
>> David
>>
>> On Tue, Jan 23, 2018 at 10:53 PM, chenjiankun 
>> wrote:
>>
>>> Hi Serena,
>>>
>>>
>>>
>>> Thanks for your information updating.
>>>
>>> I am so glad to see TestAPI is ready to collecting deployment results,
>>> and it would be much more convenient.
>>>
>>> One question: does all installer will push result to DB, or just Daisy
>>> for now?
>>>
>>>
>>>
>>> For the Jenkins id, it means a combination of deployment + functest +
>>> yardstick job. I am not sure if there are a ‘jenkins_id’ for now. This
>>> field is for identify the combination jobs.
>>>
>>> For the second comment, maybe there are some misunderstanding, as
>>> David’s requirements, we will show data last x iterations(not days), so I
>>> think there will be no such problems.
>>>
>>> For the healthcheck column, I totally agree with you. But maybe it will
>>> depend on functest to upload test result independently.
>>>
>>>
>>>
>>> What’s your opinions? @David, @Serena
>>>
>>>
>>>
>>> BRs,
>>>
>>> Jack Chan
>>>
>>>
>>>
>>> *发件人:* SerenaFeng(zte) [mailto:serena.feng.711+...@gmail.com]
>>> *发送时间:* 2018年1月22日 18:08
>>> *收件人:* chenjiankun
>>> *抄送:* David McBride; Serena Feng; TECH-DISCUSS OPNFV
>>> *主题:* Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources
>>> collection
>>>
>>>
>>>
>>> Hi David & Jack,
>>>
>>>
>>>
>>> Thanks for mentioning the task, an interface for collecting deployment
>>> results has been ready in TestAPI[1],
>>>
>>> the Macro for pushing deployment result is also ready by Jelien[2], I
>>> believe it will facilitate all the installers' work,
>>>
>>> currently, Julien is working on pushing daisy results to TestAPI
>>> leveraging that Macro, I think it will be finished soon.
>>>
>>>
>>>
>>> And regarding how to show all the information in a table, I suggest we
>>> can take a look at Jack's proposal first.
>>>
>>>
>>>
>>> @Jack, a few comments:
>>>
>>> 1. what's th

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[SerenaFeng(zte)]

Hi all，

In our case, a link back to jobs on Jenkins is necessary for the latest
iteration(s, for a short period), but for the very historical records, I
don't think it is needed, after all, in very few conditions, the user needs
to check the historical log, what they care more is the
success/fail/duration/faiure-reason...etc information, which are all
already included in the database. And we have already saved
start_date/stop_date to distinguish each test results.

Considering the cost and effort of saving the logs somewhere and
permanently, VS, our requirement, I think we can still leverage build_id
for the link work, there may be some wrong leading due to the two
aforementioned reasons, but we can take it as the tolerable mistake.

And personally comments:
- recreation of jobs
   very little possibility to do it
- migration to a new jenkins instance without preserving the build history
   it is quite impossible to do like that in an official usage

What do you think? @Jack @David @Fatih @Trevor

BUILD_TIMESTAMP is something we can leverage, currently, the
start_date/stop_date is generated based on the local time, the time is
quite inconsistent due to time zone and/or ntp server issues, @Trevor and
@Fatih, do you think it can solve our mis-date issues by using
BUILD_TIMESTAMP?


BRs
Serena

On Tue, Jan 30, 2018 at 4:19 PM Fatih Degirmenci <
fatih.degirme...@ericsson.com> wrote:

> Hi Jack,
>
> As Serena noted, all installers except Apex use same job structure; 1
> parent/upstream job starting and controlling the execution of the
> child/downstream jobs that do deployment, functest, and yardstick for a
> single scenario.
> A variable can be generated by parent job and passed to child jobs so you
> can have one variable to identify a full run in the end.
>
> This could be BUILD_TIMESTAMP as Trevor talked about below or something
> else as long as it is guaranteed to be unique within that installer or
> scenario.
> What is important here is how you intend to push data to database. If you
> will track results on installer level than there is very small possibility
> of having same timestamp for 2 separate runs if they start exactly at the
> same time on millisecond.
> In this case, UUID can be generated and used instead.
>
> Another thing I missed mentioning is that you intend to link back to jobs
> on Jenkins if I understood it correctly. We have build retention policy on
> Jenkins so after certain period or no of builds (X days or Y no of builds),
> they get deleted and you will have links pointing to non-existing logs.
> If you need to keep the logs then my suggestion would be to dump logs to
> somewhere that can also use the variable generated by the parent job so you
> have references to the things correctly.
>
> /Fatih
>
> On 2018-01-30, 08:22, "opnfv-tech-discuss-boun...@lists.opnfv.org on
> behalf of chenjiankun"  behalf of chenjiank...@huawei.com> wrote:
>
> Hi Fatih & Trevor,
>
> What we need is a new variable(like build_id) which can identify a
> combination of (Deployment + Functest + Yardstick) CI jobs. For example, if
> in one curtain scenario, we will run deployment job, Functest job and
> Yardstick job, and then their id will be the same.
> Since I am not familiar with the Jenkins, can you give us some
> suggestions?
> Or can you help us to add a new variable which can satisfy our
> requirements?
> Thanks in advance~
>
> BRs,
> Jack Chan
>
> -邮件原件-
> 发件人: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Trevor Bramwell
> 发送时间: 2018年1月30日 7:21
> 收件人: Fatih Degirmenci
> 抄送: Serena Feng; TECH-DISCUSS OPNFV
> 主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources
> collection
>
> Hi,
>
> Previous versions of Jenkins set BUILD_ID to the timestamp of the
> build but now BUILD_ID = BUILD_NUMBER.
>
> There are two plugins that appear to bring back
> 'BUILD_TIMESTAMP'[1][2].
>
> It also wouldn't be too hard to generate this as part of a build step
> and we could keep the format TIMESTAMP_FORMAT as a global variable.
>
> Regards,
> Trevor Bramwell
>
> [1] https://plugins.jenkins.io/build-timestamp
> [2] https://plugins.jenkins.io/zentimestamp
>
> On Tue, Jan 30, 2018 at 12:04:10AM +0100, Fatih Degirmenci wrote:
> > Hi,
> >
> > BUILD_ID should not be used for this type of purposes since it gets
> > reset when certain things happen such as
> >
> > - recreation of jobs
> > - migration to a new jenkins instance without preserving the build
> > history
> >
> > If any of these things happen

Re: [opnfv-tech-discuss] [dovetail] Nomination of PTL promotion for:

[SerenaFeng(zte)]

+1

On Fri, Feb 2, 2018 at 9:16 AM Leo Wang  wrote:

> +1
>
> LeoWang
> --
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org <
> opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Tianhongbo <
> hongbo.tianhon...@huawei.com>
> *Sent:* Thursday, February 1, 2018 11:13 AM
> *To:* Wenjing Chu; Tianhongbo; Dave Neary; Georg Kunz; 'Cooper, Trevor'; '
> z...@redhat.com'; Lincoln Lavoie; Wanglei (Leo, CCN); Fu Qiao
> *Cc:* 'opnfv-tech-discuss'
> *Subject:* [opnfv-tech-discuss] [dovetail] Nomination of PTL promotion
> for: 
>
>
> Hi all committers:
>
>
>
> Georg has made a great contribution as committer, and he is the only on
> candidate.
>
>
>
> His contribution link:
> https://gerrit.opnfv.org/gerrit/#/q/owner:georg.kunz%2540ericsson.com+status:merged
>
>
>
> Please vote for his new role of dovetail PTL(+1 or -1).
>
>
>
>
>
> Let me do it first, thanks
>
>
>
>
>
> +1
>
>
>
>
>
> hongbo
> ___
> 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] [TestResults DB] Cannot create pod in testresults db

[SerenaFeng(zte)]

Hi Mark,

Sorry for the inconvenience. After leveraging the authentication, swagger
page is no longer used for create/update/delete. Please use the new web
portal for creating the new pods: http://testresults.opnfv.org/test/#/pods

BRs
Serena

On Sat, Feb 3, 2018 at 5:57 AM Beierl, Mark  wrote:

> Hello, everyone.
>
> I'm trying to create a pod entry for flex-pod2 in the testresults db using
> the swagger API.  I'm logged in, but the post is returning HTTPError: HTTP
> 401: TestAPI id is not provided.  Here is the payload:
>
> {
>   "role": "",
>   "name": "flex-pod2",
>   "details": "5 bare metal servers",
>   "mode": "metal"
>  }
>
> And the full response from Swagger UI:
>
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1401,
> in _stack_context_handle_exception
> raise_exc_info((type, value, traceback))
>   File "/usr/local/lib/python2.7/dist-packages/tornado/stack_context.py",
> line 314, in wrapped
> ret = fn(*args, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1613,
> in future_complete
> f.result()
>   File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py",
> line 232, in result
> raise_exc_info(self._exc_info)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014,
> in run
> yielded = self.gen.throw(*exc_info)
>   File
> "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py",
> line 62, in wrapper
> ret = yield gen.coroutine(method)(self, *args, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008,
> in run
> value = future.result()
>   File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py",
> line 232, in result
> raise_exc_info(self._exc_info)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014,
> in run
> yielded = self.gen.throw(*exc_info)
>   File
> "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py",
> line 85, in wrap
> ret = yield gen.coroutine(xstep)(self, *args, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008,
> in run
> value = future.result()
>   File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py",
> line 232, in result
> raise_exc_info(self._exc_info)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014,
> in run
> yielded = self.gen.throw(*exc_info)
>   File
> "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py",
> line 100, in wrap
> ret = yield gen.coroutine(xstep)(self, *args, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008,
> in run
> value = future.result()
>   File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py",
> line 232, in result
> raise_exc_info(self._exc_info)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014,
> in run
> yielded = self.gen.throw(*exc_info)
>   File
> "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py",
> line 144, in wrap
> ret = yield gen.coroutine(xstep)(self, *args, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008,
> in run
> value = future.result()
>   File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py",
> line 232, in result
> raise_exc_info(self._exc_info)
>   File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 282,
> in wrapper
> yielded = next(result)
>   File
> "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py",
> line 27, in wrapper
> raises.Unauthorized(message.not_login())
>   File
> "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/raises.py",
> line 18, in __init__
> raise web.HTTPError(self.code, reason=reason)
> HTTPError: HTTP 401: TestAPI id is not provided
>
> Regards,
> Mark
>
> *Mark Beierl*
> SW System Sr Principal Developer
> *Dell **EMC* | Cloud & Communication Service Provider Solution
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> ___
> 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] Test Results Dashboard

[SerenaFeng(zte)]

Hi Bryan,

Thanks for pointing this out, one more comment I would like to add,
http://testresults.opnfv.org is not only leveraged in reporting dashboard,
it also accommodates TestAPI server(http://testresults.opnfv.org/test/
), grafana (http://testresults.opnfv.org/grafana), storperf(
http://testresults.opnfv.org/storperf/)... etc, some are not accessible or
provided, like landing-page/catalog/storperf, maybe in the near future we
will add dashboards for milestone management and deployment results
analysis which are under discussion now. Currently, there is no place to
list all the services supported in OPNFV test results ecosystem, and we
don't know how many and which services are provided in host
testresults.opnfv.org.

Based on the information above, instead of link
http://testresults.opnfv.org/ to reporting home page, how about making it
work as the entry point for all the testing services provided in host
testresults.opnfv.org, regulate and manage it code-based in our CI/CD
system? By doing this, reducing manual create/update/delete in
testresults.opnfv.org, which is very difficult to control and may induce
system crash, and moreover, it will be easily transplanted by the 3rd
party, let's say ONAP for example.

And sorry that my proposal may be adding other tiles to the URL.

Some other comment please see in lines.

BRs
Serena

On Tue, Feb 6, 2018 at 12:11 AM SULLIVAN, BRYAN L (BRYAN L) <
bryan.sulli...@research.att.com> wrote:

> Hi all,
>
>
>
> I see that the design of http://testresults.opnfv.org has evolved. Quick
> suggestions/questions.
>
>- Is it possible to reduce the size of the tiles in the UI? I don’t
>see how the tiles so large add a lot of value.
>- The info for past releases seems to be missing/broken
>
>Serena: AFAIK, reporting only analyze the latest status(last
10 days by default), so only active branch(CI running branch) will be
shown, so there's no display for Colorado and Danube.

>
>-
>- For master, the data is there (e.g.
>http://testresults.opnfv.org/master/functest/status-apex.html) but
>only for Apex
>
>Serena: Apex page serves as the default home page, we can
check http://testresults.opnfv.org/master/functest/status-xx(substitue xx
with daisy/joid..).html for other installers

>
>-
>- It takes a lot of clicks to get to the details. The presentation ala
>http://testresults.opnfv.org/master/functest/status-apex.html is
>really what we need to see, so is there a way to simply have the main page
>http://testresults.opnfv.org just present an outline view of the
>subpages for master (first), then the previous releases inreverse order?
>This would make the site easier to use.
>
>Serena: I cannot figure out what exactly you want for the
page layout.

FYI I am looking to bring the basic test results dashboard concept (status
> meter, trend graph, score, iterations, …) to the Acumos project’s CI/CD
> team. This is a valuable approach to tracking project status and the trend
> of build/tests, and it would be good to share the OPNFV expertise in this
> at the right time (at ONS would be great).
>
>
>
> Thanks,
>
> Bryan Sullivan | AT&T
>
>
> ___
> 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] [releng] Secrets in environment variables

[SerenaFeng(zte)]

Hi Luke & Julien,

I think the Credentials Binding plugin should have been installed since
ssh-key is leveraged to manage slave node, and previously, TestAPI intended
to employ it for the token check, but the privilege is not opened to
everyone, you need to contact @Trevor, Aric or Fatih for it.

BRs
Serena

On Thu, Mar 1, 2018 at 5:16 PM Julien  wrote:

> Hi Luke,
>
> Yes, you can inject a secret string in the jjb :
>
> wrappers:
>  - credentials-binding:
>  - zip-file:
> credential-id: b3e6f337-5d44-4f57-921c-1632d796caa6
> variable: CONFIG_ZIP
>  - file:
> credential-id: b3e6f337-5d44-4f57-921c-1632d796caab
> variable: config_file
>  - username-password:
> credential-id: b3e6f337-5d44-4f57-921c-1632d796caac
> variable: config_username_password
>  - text:
> credential-id: b3e6f337-5d44-4f57-921c-1632d796caad
> variable: config_text
>
> it supports file, text, username-password, etc. It can not be echo/cat
> during the CI execution.
> It requires a Credentials Binding plugin.
> @Trevor, Aric, can you double check is it installed already?
> We use this method to avoid API token leak issue in internal CI.
>
> [1], https://docs.openstack.org/infra/jenkins-job-builder/wrappers.html
> [2], https://wiki.jenkins.io/display/JENKINS/Credentials+Binding+Plugin
>
>
> Luke Hinds 于2018年2月20日周二 下午4:11写道：
>
>> Hi,
>>
>> Do we have the capability to handle (inject?) environment variable
>> secrets in our CI that are set during a build?
>>
>> I am looking at introducing virus total checks into anteater and this
>> needs an API key which we don't want to share in the open.
>>
>> Currently I have the code look for the key in the environment, rather
>> then a config file..is this workable?
>>
>> e.g...
>>
>> export VT_KEY=''
>> echo $VT_KEY
>> 
>> --
>> Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
>> e: lhi...@redhat.com | irc: lhinds @freenode | t: +44 12 52 36 2483
>> ___
>> 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] [test-wg] Re: About making reporting reusable

[SerenaFeng(zte)]

ay, it depends on the compelxity to setup.

Here the adaptations were relatively trivial.



/Morgan



Le mardi 24 avril 2018 à 09:09 +0000, SerenaFeng(zte) a écrit :

Hi both,



I am looking at reporting, hope to reuse it internally, but I find it is quite
hardcoded to OPNFV, so I am thinking about doing some improvement to make it
more reusable, and much easier to be migrated to other community or project, and
I know Morgan is trying to introduce reporting to ONAP now, I think the
improvement will benefit ONAP too. So my proposal is:



1. decouple static reporting from landingpage and catalog, as we will know they
are quite different projects, nothing interact, it is weird to couple them
together.



2. make the web pages rendered dynamically based on the configurations and
templates. the configuration(functest.yaml/master.yaml) determines which
project/version to show, the template(weather.template/trend.template)  work on
the webpage content. by doing this, it will be much easier to add new
version/project by providing the configurations without changing the source
code.



what do you think about this proposal? Since you both are the original author of
reporting, your opinion are very valuable to me.





BRs

Serena









_

 

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.




Sent with Mixmax___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [announce] moving on....

[SerenaFeng(zte)]

Hi Ray,
We will miss you very much.It's been great experience working with you. Thanks
for all your encouragement and guidance. You are really a very nice person. Wish
you the best at your new endeavor and hope to beer again in the future.
BRsSerena  





On Mon, Jun 18, 2018 3:31 AM, Raymond Paik rp...@linuxfoundation.org  wrote:
All,
I shared this news with some of the community members over the past several
days, and I wanted to notify the rest of the community.
I recently made a difficult decision to pursue a new opportunity outside of the
LF.  Having been involved in OPNFV since the formation days, the thought of
leaving the community isn't easy.  This is especially the case since I just
spent the entire week with many community members at ETSI during the Plugfest. 
I was again reminded that I'm part of a wonderful & motivated community.
My last day at the Linux Foundation is on June 22nd, and I'm working with both
Phil & Heather on transition plans so that things don't get dropped.
I sincerely hope that our paths will cross again.  I'm still going to be
involved in open source software, so I'm definitely not going too far.  Wherever
and whenever our paths cross, I hope we can share a drink soon
Regards,
Ray___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tsc] [opnfv-tech-discuss] The OPNFV Cloud Native working group proposal is being discussed in the TSC

[SerenaFeng(zte)]

Sounds great~
Please count me in~

On Tue, Aug 7, 2018 at 9:33 PM Ryota Mibu  wrote:

> Sounds nice, I’ll join the call.
>
>
>
> /Ryota
>
>
>
> *From:* HU, BIN [mailto:bh5...@att.com]
> *Sent:* Thursday, August 02, 2018 1:08 PM
> *To:* Wenjing Chu ; Tina Tsou ;
> Georg Kunz ; Gergely Csatari <
> gergely.csat...@nokia.com>; opnfv-tech-discuss@lists.opnfv.org
> *Cc:* jason.jiax...@gmail.com; fuq...@chinamobile.com; Stephen Wong <
> stephen.wo...@huawei.com>; brian.j.skerry ;
> Rossella Sblendido ; julienjut ;
> Fatih Degirmenci ; TSC OPNFV <
> opnfv-...@lists.opnfv.org>; Mibu Ryota(壬生 亮太) ;
> Sridhar K. N. Rao 
>
>
> *Subject:* RE: [opnfv-tech-discuss] The OPNFV Cloud Native working group
> proposal is being discussed in the TSC
>
>
>
> Wenjing,
>
>
>
> Sounds good, and count me in too.
>
>
>
> Let’s kick it off on 08/16 at technical community meeting time.
>
>
>
> Thank you
>
> Bin
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *Wenjing Chu
> *Sent:* Wednesday, August 1, 2018 5:31 PM
> *To:* Tina Tsou ; Georg Kunz ;
> Gergely Csatari ;
> opnfv-tech-discuss@lists.opnfv.org
> *Cc:* jason.jiax...@gmail.com; fuq...@chinamobile.com; Stephen Wong <
> stephen.wo...@huawei.com>; brian.j.skerry ;
> Rossella Sblendido ; julienjut ;
> Fatih Degirmenci ; TSC OPNFV <
> opnfv-...@lists.opnfv.org>; Ryota Mibu ; Sridhar K.
> N. Rao 
> *Subject:* Re: [opnfv-tech-discuss] The OPNFV Cloud Native working group
> proposal is being discussed in the TSC
>
>
>
> Thanks for all the interests… Please continue to let us know if you can
> participate or someone in your project can. We clearly want representation
> from container4nfv, installers that are producing k8s, edge cloud, data
> path, testing projects that are interested in cloud native testing … and
> all of you really.
>
>
>
> I’d propose that we use Bin’s meeting slot for a kickoff community meeting
> as a start and level setting, and choose how we want to meet in future. I’m
> taking time off myself next week, but August 16 works for me.
>
>
>
> Bin, would it be OK that we take the whole hour for August 16?
>
> And does that time work for everyone?
>
>
>
> Regards
>
> Wenjing
>
>
>
>
>
>
>
> *From:* Tina Tsou [mailto:tina.t...@arm.com ]
> *Sent:* Wednesday, August 01, 2018 3:13 PM
> *To:* Georg Kunz ; Gergely Csatari <
> gergely.csat...@nokia.com>; Wenjing Chu ;
> opnfv-tech-discuss@lists.opnfv.org
> *Cc:* jason.jiax...@gmail.com; fuq...@chinamobile.com; Stephen Wong <
> stephen.wo...@huawei.com>; brian.j.skerry ;
> Rossella Sblendido ; julienjut ;
> Fatih Degirmenci ; TSC OPNFV <
> opnfv-...@lists.opnfv.org>; Ryota Mibu ; Sridhar K.
> N. Rao 
> *Subject:* RE: [opnfv-tech-discuss] The OPNFV Cloud Native working group
> proposal is being discussed in the TSC
>
>
>
> Dear Wenjing,
>
>
>
> We discussed it before, I’m interested to participate in.
>
>
>
>
>
> Thank you,
>
> Tina Tsou
>
> Enterprise Architect
>
> Arm
>
> tina.t...@arm.com
>
> +1 (408)931-3833 <(408)%20931-3833>
>
>
>
> *From:* Georg Kunz 
> *Sent:* Wednesday, August 1, 2018 3:08 PM
> *To:* Gergely Csatari ; Wenjing Chu <
> wenjing@huawei.com>; opnfv-tech-discuss@lists.opnfv.org
> *Cc:* jason.jiax...@gmail.com; fuq...@chinamobile.com; Stephen Wong <
> stephen.wo...@huawei.com>; brian.j.skerry ;
> Rossella Sblendido ; julienjut ;
> Tina Tsou ; Fatih Degirmenci <
> fatih.degirme...@ericsson.com>; TSC OPNFV ;
> Ryota Mibu ; Sridhar K. N. Rao <
> sridhar@spirent.com>
> *Subject:* RE: [opnfv-tech-discuss] The OPNFV Cloud Native working group
> proposal is being discussed in the TSC
>
>
>
> Hi,
>
>
>
> Count me in, too.
>
>
>
> Best regards
>
> Georg
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *Gergely Csatari
> *Sent:* Wednesday, August 1, 2018 12:47 PM
> *To:* Wenjing Chu ;
> opnfv-tech-discuss@lists.opnfv.org
> *Cc:* jason.jiax...@gmail.com; fuq...@chinamobile.com; Stephen Wong <
> stephen.wo...@huawei.com>; Georg Kunz ;
> brian.j.skerry ; Rossella Sblendido <
> rsblend...@suse.com>; julienjut ; Tina Tsou <
> tina.t...@arm.com>; Fatih Degirmenci ; TSC
> OPNFV ; Ryota Mibu ;
> Sridhar K. N. Rao 
> *Subject:* Re: [opnfv-tech-discuss] The OPNFV Cloud Native working group
> proposal is being discussed in the TSC
>
>
>
> Hi,
>
>
>
> I would be happy to participate.
>
>
>
> Br,
>
> Gerg0
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *Wenjing Chu
> *Sent:* Tuesday, July 31, 2018 7:57 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Cc:* jason.jiax...@gmail.com; fuq...@chinamobile.com; Stephen Wong <
> stephen.wo...@huawei.com>; 'Georg Kunz' ;
> brian.j.skerry ; Rossella Sblendido <
> rsblend...@suse.com>; julienjut ; Tina Tsou <
> tina.t...@arm.com>; fatih.degirme...@ericsson.com; TSC OPNFV <
> opnfv-...@lists.opnfv.org>; Ryota Mibu ; Sridhar K.
> N. Rao 
> *Subject:* [opnfv-tech-discuss] The OPNFV Cloud Native working group
> proposal is 

Re: [opnfv-tech-discuss][dovetail]

[SerenaFeng(zte)]

Hi Dimitris,
First of all, thanks for your interest in Dovetail.
After looking at the failure information, I think the problem is because
192.168.37.205 is not accessible from functest-smoke container. I assume it is
the public or admin network, and the link from testing containers to OpenStack
via public & admin network plane are required by some testcases.
2018-08-16 10:13:35,982 - functest.core.singlevm - ERROR - cannot connect to
192.168.37.205
And after looking at env_config.sh, I think DOVETAIL_HOME env variable is
missing, I remember it is also required to be set in env_config.sh
To make the problem shooting easier and faster, I would suggest to running in
'debug' mode, which is add '-d' flag when starting the tests, such as 'dovetail
run --testsuite ovp.next -d'
Regarding the hosts.yaml, if there are some domains need to be parsed during the
testing, they are defined in this file, it will finally be parsed and put
into /etc/hosts in the testing container. You can reference the
hosts.yaml.sample for the schema.
for example if the following information is defined in hosts.yamlhosts_info:   
192.168.141.101:        - admin_ip        - public_ipthen in /etc/hosts of the
testing container, the following line will be added.    192.168.141.101 admin_ip
public_ip
Hope these information will help you~

BRsSerena





On Fri, Aug 17, 2018 3:39 PM, dimitris.tsiolakis d...@intracom-telecom.com 
wrote:
Hi Dovetailers,



I’m new at the dovetail I’m trying to run dovetail test  cases following the
latest instruction from testing_guide.rst  (
https://gerrit.opnfv.org/gerrit/#/c/60823/).



I created all mandatory files:

-    env_config.sh, ( this is mine looks like
http://paste.openstack.org/show/728164/) 

-    tempest_conf.yaml (same as the sample)

-   pod.yaml( https://paste.ubuntu.com/p/883N3Cmrx4/  I also use password
instead of id_rsa)

-   (I did not create the hosts.yaml since it is optional.)



When I run “dovetail run” test fails ( logs can be found here 
http://paste.openstack.org/show/728169/  )



I seems that the pod.yaml file is not correct and it cannot read the SUT info
but I cannot  Understand what is wrong.

Also the absence of hosts.yaml  file is raising a warning what is this file and
how should I update it?



Can you help me with the configuration and the execution?



Thank you in advance



Dimitris Tsiolakis

SDN  NFV Thessaloniki

_
Intracom Telecom
Marinou Antipa 41, Pilea-Thessaloniki,GR 57001
t:   +30 2310497389
f:   +30 2310497330

d...@intracom-telecom.com

www.intracom-telecom.com

















JOIN US

Mobile World Congress Americas

12-14 September
Los Angeles, USA



Gitex Technology Week

14-18 October
Dubai, UAE



FutureCom

15-18 October

Sao Paulo, Brazil



AfricaCom

13-15 November

Cape Town, S. Africa



Mobile World Congress

25-28 February 2019

Barcelona, Spain



Mobile World Congress Shanghai

26-28 June 2019
Shanghai, China



The information in this e-mail message and any attachments are intended only for
the individual or entity to whom it is addressed and may be confidential. If you
have received this transmission in error, and you are not an intended recipient,
be aware that any copying, disclosure, distribution or use of this transmission
or its contents is prohibited. Intracom Telecom and the sender accept no
liability for any loss, disruption or damage to your data or computer system
that may occur while using data contained in, or transmitted with, this email.
Views or opinions expressed in this message may be those of the author and may
not necessarily represent those of Intracom Telecom.






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21801): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21801
Mute This Topic: https://lists.opnfv.org/mt/24610481/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-