[opnfv-tech-discuss] [mano-wg] Release E priorities and MANO Project contents addressing EUAG pain points

[Prakash Ramchandran]

Hi all,

Please Join MANO WG meeting .

Meeting Times: Every Wednesday (7.00 am PST)  at 15.00 UTC, Other  Ad-hoc 
meeting as per Project requests

For IRC can use can use http://webchat.freenode.net/

IRC#opnfv-mano (meetbot is set for meeting minutes )

OPNFV MNAO WG Meeting

GOTOMEETING

1. Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/229632485
(in case of GTM fails join IRC using webchat link above and get the new GTM 
link/ meeting number)

2. Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States (Toll Free): 1 877 309 2073
United States: +1 (312) 757-3136

Access Code: 229-632-485

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


May 10th, Wednesday : 14.00 UTC /7.00 PDT  Meeting #30

1.Agenda Bashing

2. Release E  follow-ups on MANO projects plans and inputs from PTLs

  a. ONAP/OPEN-O Harmonization plans /Opera Readiness :  E-Release (Updates 
from Yingjun Li on what are the issues for deferrals)

  b. Orchestra has committed for  Build Deploy for E-Release and two JIRA 
tickets are opened (updates from Giuseppe)

  1.  
Orchestra-1
  2.  
Orchestra-2

  c. Write a Juju charm for installing Open Baton / Test Juju charm - (other 
inputs from Narinder)

  d. Are projects in MANO WG  addressing EUAG Pain 
Points? Discuss Compile by 
projects what each project is doing for the same for weekly Tech meetings.

  JOID plans to support OpenStack Ocata with noSDN scenario for OpenBaton in 
release-E to start with. If ODL support for charm is added later it may 
consider that for OpenBaton at that time.

  d. Review of other projects in MANO WG that have indicated intent to 
participate in E-Release include Domino, Parser, Models and Copper

3. Discussions on Open Source SBC use case from MANO for Design and Deployment  
for Dovetail

4. Events and planning MANO issues

Openstack 
(Boston)
 - Reports & OPNFV(Beijing) -plans 
and OPNFV Meetup (WSO2) and 
APIs (ONOS/ONAP)

5. Continuing discussions on VNF On-boarding, Packaging  best practices for 
MANO rationalization over OPNFV
Thanks
Prakash


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






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

Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

[Yuyang (Gabriel)]

Hi Alec,

Please see answers inline.

Thanks,
Gabriel


From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Tuesday, May 09, 2017 11:11 PM
To: Yuyang (Gabriel); morgan.richo...@orange.com; Cooper, Trevor; 
opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi Gabriel,



From: "Yuyang (Gabriel)" 
mailto:gabriel.yuy...@huawei.com>>
Date: Friday, May 5, 2017 at 12:06 AM
To: "Alec Hothan (ahothan)" mailto:ahot...@cisco.com>>, 
"morgan.richo...@orange.com" 
mailto:morgan.richo...@orange.com>>, "Cooper, 
Trevor" mailto:trevor.coo...@intel.com>>, 
"opnfv-tech-discuss@lists.opnfv.org" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>,
 "test...@lists.opnfv.org" 
mailto:test...@lists.opnfv.org>>
Subject: RE: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi Alec,

Please see my answers inline!

Thanks!
Gabriel

From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Friday, May 05, 2017 11:11 AM
To: Yuyang (Gabriel); 
morgan.richo...@orange.com; Cooper, Trevor; 
opnfv-tech-discuss@lists.opnfv.org; 
test...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi Gabriel,

Regarding TC1, do you have the results and original chart available somewhere 
(the chart in the picture and in the slides is kind of small).
Gabriel: We do not have the original results and chart now since this is one 
time result that we have when we do local test. We have discussed the results 
plotting within Testperf.
The test results will be shown in the community ELK maintained by bitergia in 
Q2.
Some results could be found in the community CI, e.g., 
https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-posca_stress_traffic-baremetal-daily-danube/5/console

[Alec] seems there are about 16 “runners” returning netperf results in a span 
of 10 minutes (at unequal interval) with ~941Mbps of throughput (presumably 
that would be TCP from VM guest user space to VM guest user space).

Gabriel: in TC1, no VM pair is created. 1 compute node is installed with 
netperf client and another is installed with netserver (TCP is used). The size 
of sending package and receiving package increases iteratively in the test. The 
sizes are configured as follows.
 
14
   tx_pkt_sizes: 64, 256, 1024, 4096, 8192, 16384, 32768, 65536
 
15
   rx_pkt_sizes: 64, 256, 1024, 4096, 8192, 16384, 32768, 65536
   For each (tx_pkt_sizes, rx_pkt_sizes), the throughput is 
measured. The test will stop until it detects the traffic limit.
   The package size/interval could flexibly configured for 
different purposes. For the CI pipeline, we use the above setting mainly for 
time saving.

Do you also have a detailed description of the test:
Gabriel: I assume you ask detailed about TC3 here, since we only run TC1 on 
vPOD or bare mental POD.

[Alec] ok it was not clear that TC3 also does throughput testing.

Gabriel: Sorry for the unclear message here. In TC1, no VM pair 
is created. Netperf are installed on virtual/bare metal compute nodes.
In TC3, multiple VM pairs are expected, and only do ping test.


· what kind of packet gen you are running in the first VM and what kind 
of forwarder you are running in the second VM
Gabriel: For TC3, we use netperf to send packet and retransmit it in the second 
VM.

[Alec] so that would be netperf client in VM1 and netperf server in VM2, 
unidirectional traffic.

   Gabriel: First, sorry for misleading information and 
typos. Yes, for TC1, netperf and netserver are installed in separate compute 
node and TCP is used.


· what flavor
Gabriel: Bottlenecks calls yardstick to do each test, the flavor is specified 
in Yardstick, i.e., yardstick-flavor: nova flavor-create yardstick-flavor 100 
512 3 1.

· what vswitch was used
Gabriel: OVS is used. If you have any recommendation, please also inform us :)

[Alec] no special recommendation,


· how are the VMs placed (wrt compute node, numa node)
Gabriel: VMs are created by using heat client without specifying how and where 
to place

[opnfv-tech-discuss] [fuel]: Danube 2.0 offline Installation

[Congiu Roberto]

Hi guys,

I noticed that Danibe 2.0 is available.
I am wondering if in this release it's possible to deploy an HA environment 
with ODL (SFC purposes) with local repo.
I know that in Danube 1.0 there was a bug that did not allow this, because some 
packages were missing.
What is the situation now?


Thank you for your help,


Roberto

--
Telecom Italia | TIM
Roberto Congiu
Network Function Virtualization
Via G.Reiss Romoli 274, 10148 Torino
Office: +39 011 228 6469
Mobile: +39 335 7532462


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone 
indicate. La diffusione, copia o qualsiasi altra azione derivante dalla 
conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate 
ricevuto questo documento per errore siete cortesemente pregati di darne 
immediata comunicazione al mittente e di provvedere alla sua distruzione, 
Grazie.

This e-mail and any attachments is confidential and may contain privileged 
information intended for the addressee(s) only. Dissemination, copying, 
printing or use by anybody else is unauthorised. If you are not the intended 
recipient, please delete this message and any attachments and advise the sender 
by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

[Alec Hothan (ahothan)]

Hi Gabriel,



From: "Yuyang (Gabriel)" 
Date: Friday, May 5, 2017 at 12:06 AM
To: "Alec Hothan (ahothan)" , "morgan.richo...@orange.com" 
, "Cooper, Trevor" , 
"opnfv-tech-discuss@lists.opnfv.org" , 
"test...@lists.opnfv.org" 
Subject: RE: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi Alec,

Please see my answers inline!

Thanks!
Gabriel

From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Friday, May 05, 2017 11:11 AM
To: Yuyang (Gabriel); morgan.richo...@orange.com; Cooper, Trevor; 
opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi Gabriel,

Regarding TC1, do you have the results and original chart available somewhere 
(the chart in the picture and in the slides is kind of small).
Gabriel: We do not have the original results and chart now since this is one 
time result that we have when we do local test. We have discussed the results 
plotting within Testperf.
The test results will be shown in the community ELK maintained by bitergia in 
Q2.
Some results could be found in the community CI, e.g., 
https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-posca_stress_traffic-baremetal-daily-danube/5/console

[Alec] seems there are about 16 “runners” returning netperf results in a span 
of 10 minutes (at unequal interval) with ~941Mbps of throughput (presumably 
that would be TCP from VM guest user space to VM guest user space).



Do you also have a detailed description of the test:
Gabriel: I assume you ask detailed about TC3 here, since we only run TC1 on 
vPOD or bare mental POD.

[Alec] ok it was not clear that TC3 also does throughput testing.



· what kind of packet gen you are running in the first VM and what kind 
of forwarder you are running in the second VM
Gabriel: For TC3, we use netperf to send packet and retransmit it in the second 
VM.

[Alec] so that would be netperf client in VM1 and netperf server in VM2, 
unidirectional traffic.



· what flavor
Gabriel: Bottlenecks calls yardstick to do each test, the flavor is specified 
in Yardstick, i.e., yardstick-flavor: nova flavor-create yardstick-flavor 100 
512 3 1.

· what vswitch was used
Gabriel: OVS is used. If you have any recommendation, please also inform us :)

[Alec] no special recommendation,


· how are the VMs placed (wrt compute node, numa node)
Gabriel: VMs are created by using heat client without specifying how and where 
to place them

· I assume the test will ramp up the number of VM pairs, if so how do 
you synchronize your VM starts/measurements (VMs don’t tend to all start the 
test at the same time due to the latency for bringing up individual VMs)
Gabriel: Yes, the VMs will not start to ping simultaneously. We can 
only simultaneously sent the request to create all the VMs, waiting for the 
creation and then to the ping operation.

· How do you track drop rate and latency across VM pairs
Gabriel: I assume you mean the packet drop rate and latency here. For these 
metrics, we use netperf to do the monitoring

[Alec] I was more interested in the throughput test. From what I can gather in 
the Jenkins log, it looks like there is no special synchronization between 
netperf clients, so they just start as soon as they’re able to send (and the 
server is ready).
The placement of the VMs does not seem to be tightly controlled, making it 
possible for some VM pairs to co-reside on the same compute node (which can 
impact the results)?
The unequal interval of the reporting shows that there is a phasing of the test 
start over time which makes it difficult to guarantee that the reported 
throughputs are all concurrent (they’re likely only partially overlapping).
So it is not easy to make good use of the results for concurrent VM to VM 
traffiic tests  those conditions.

I see from the summary below that this stress test demo is perhaps more geared 
towards control plane stress testing, What is called a “stack” is I think a VM 
pair.
Do you have the detailed log or results of these tests somewhere?


Thanks

   Alec





Gabriel: you could also do the test locally. For more information, please refer 
to the link below.
Bottlenecks Testing Guide: 
http://docs.opnfv.org/en/stable-danube/submodules/bottlenecks/docs/testing/developer/devguide/posca_guide.html



Thanks!

  Alec





From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "Yuyang (Gabriel)" 
mailto:gabriel.yuy...@huawei.com>>
Date: Thursday, May 4, 2017 at 7:48 PM
To: "morgan.richo...@orange.com" 
mailto:morgan.richo...@orange.com>>, "Cooper, 
Trevor" mailto:trevor.coo...@intel.com>>, 
"opnfv-tech-discuss@lists.opnfv.org" 
mailto:opnfv-tech-discus

Re: [opnfv-tech-discuss] [release][danube] OPNFV Danube 2.0 has been released

[Beierl, Mark]

Joining in here.  From the artifacts page [1], I see that Apex is released as 
an ISO.  Only JOID does not produce an ISO.

For the TripleO RPMs, they are built on the OPNFV CentOS slaves, so there is 
nothing proprietary there.  RPM is the upstream format for the TripleO project 
if I understand correctly.

Please forgive me if I mis-understood the concern.

[1] https://www.opnfv.org/software/downloads/release-archives/danube-1-0

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On May 9, 2017, at 00:12, Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:

Julien,

Based on the minutes, it says Arno will support iso and script based 
deployment, but too early to decide on packaging options for future releases 
(incl. Brahmaputra).

I'm not sure if I understand your concerns on RPMs from Apex.  Could you 
elaborate further?

Thanks,

Ray

On Mon, May 8, 2017 at 4:03 PM, Julien 
mailto:julien...@gmail.com>> wrote:
Hi David,

This issue has been discussed in the TSC meeting. I don't know this conclusion 
about "Packaging is a community decision made by the installer teams and the 
dependent scenario owners and project teams" is approved by TSC. I just 
remember ISO and source code are two alternatives.
"In particular, RPM is standard for Red Hat OSs"
If it is RHEL, it is licensed and not suitable. In OPNFV, we only use community 
version, ie. CentOS. If we release RPMs in Cent OS, shall we release deb 
packages for Ubuntu OS?

I'm sorry that I can not go to openstack summit.

There are some records in TSC meeting such as July 14th, 2015, and original 
link is: 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-14-14.00.html.

Regards,
Julien

David McBride 
mailto:dmcbr...@linuxfoundation.org>>于2017年5月8日周一 
下午11:38写道：
Hi Julien,

"Apex" is the project name for TripleO in OPNFV.  However, "TripleO" is the 
name of the installer.  Also, "TripleO" is well known outside of OPNFV, whereas 
"Apex" is unique to OPNFV.

Packaging is a community decision made by the installer teams and the dependent 
scenario owners and project teams.  So far, I've never heard any complaints 
from members or end users about packaging.  However, this topic might be worth 
bringing up at the EUAG in case there are some issues that I'm unaware of.

I think that having packaging for each installer that is appropriate and has 
community/user consensus is more important than forcing the same packaging 
across all installers (i.e. "consistency is the hobgoblin of little minds").  
In particular, RPM is standard for Red Hat OSs, therefore, it makes sense that 
TripleO would be released on RPM.

If you are at OpenStack this week, I'd be happy to discuss this with you 
further F2F.

David

On Sat, May 6, 2017 at 4:37 AM, Julien 
mailto:julien...@gmail.com>> wrote:
Hi David,

In our installer projects, there are Apex, Compass, Fuel, and Juju released in 
Danube. I wonder why use the name TripleO instead of Apex?

I have discussed at Arno and Brahmaputra about how to release OPNFV artifacts, 
and the conclusion is in ISO or source codes. Why release RPMs for Apex? It is 
different from other installers. The release content or list are different in 
OPNV download page. It is really strange.

BR,
Julien


David McBride 
mailto:dmcbr...@linuxfoundation.org>>于2017年5月6日周六 
上午5:20写道：
TSC members,

I'm pleased to let you know that OPNFV Danube 2.0 has been released.  Software 
and documentation may be accessed 
here.

Congratulations to everyone in the community that worked hard to make this 
happen.  Please let me know if you have questions or comments.

David

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



--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride

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

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

Re: [opnfv-tech-discuss] [summit] schedule for Design Summit

[Raymond Paik]

Yujun,

The goal is to publish the design summit schedule within a week.  Thanks
for your patience

Ray

On Mon, May 8, 2017 at 9:17 PM, Yujun Zhang (ZTE) 
wrote:

> Not sure which channel should I ask this question...
>
> It seems currently only the schedule of OPNFV summit is published[1].
>
> When will the schedule of *design summit* be released?
>
> [1]: http://events.linuxfoundation.org/events/
> opnfv-summit/program/schedule
>
> --
> 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

[opnfv-tech-discuss] [SFC] Weekly meeting canceled due to OpenStack Boston Summit

[Brady Allen Johnson]

Hello,

I will be traveling to the OpenStack Boston Summit and wont be able to host the 
meeting this week, so lets cancel it.

Regards,

Brady

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

Re: [opnfv-tech-discuss] [release][danube] OPNFV Danube 2.0 has been released

[Julien]

Hi Ray,

I just give one of these links,  and there are many records about this. I
don't remember the exact record about this for discussed years ago.

In our CI system, we use source code or ISO to deploy the environment from
installer and then perform the tests. I don't think there are changes for
this since brahmaputra. I don't know RPM method is covered by CI either.

Regards,
Julien



Raymond Paik 于2017年5月9日周二 下午12:13写道：

> Julien,
>
> Based on the minutes, it says Arno will support iso and script based
> deployment, but too early to decide on packaging options for future
> releases (incl. Brahmaputra).
>
> I'm not sure if I understand your concerns on RPMs from Apex.  Could you
> elaborate further?
>
> Thanks,
>
> Ray
>
> On Mon, May 8, 2017 at 4:03 PM, Julien  wrote:
>
>> Hi David,
>>
>> This issue has been discussed in the TSC meeting. I don't know this
>> conclusion about *"Packaging is a community decision made by the
>> installer teams and the dependent scenario owners and project teams"* is
>> approved by TSC. I just remember ISO and source code are two alternatives.
>> *"In particular, RPM is standard for Red Hat OSs"*
>> If it is RHEL, it is licensed and not suitable. In OPNFV, we only use
>> community version, ie. CentOS. If we release RPMs in Cent OS, shall we
>> release deb packages for Ubuntu OS?
>>
>> I'm sorry that I can not go to openstack summit.
>>
>> There are some records in TSC meeting such as July 14th, 2015, and
>> original link is:
>> http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-14-14.00.html
>> .
>>
>> Regards,
>> Julien
>>
>> David McBride 于2017年5月8日周一 下午11:38写道：
>>
>>> Hi Julien,
>>>
>>> "Apex" is the project name for TripleO in OPNFV.  However, "TripleO" is
>>> the name of the installer.  Also, "TripleO" is well known outside of OPNFV,
>>> whereas "Apex" is unique to OPNFV.
>>>
>>> Packaging is a community decision made by the installer teams and the
>>> dependent scenario owners and project teams.  So far, I've never heard any
>>> complaints from members or end users about packaging.  However, this topic
>>> might be worth bringing up at the EUAG in case there are some issues that
>>> I'm unaware of.
>>>
>>> I think that having packaging for each installer that is appropriate and
>>> has community/user consensus is more important than forcing the same
>>> packaging across all installers (i.e. "consistency is the hobgoblin of
>>> little minds").  In particular, RPM is standard for Red Hat OSs, therefore,
>>> it makes sense that TripleO would be released on RPM.
>>>
>>> If you are at OpenStack this week, I'd be happy to discuss this with you
>>> further F2F.
>>>
>>> David
>>>
>>> On Sat, May 6, 2017 at 4:37 AM, Julien  wrote:
>>>
 Hi David,

 In our installer projects, there are Apex, Compass, Fuel, and Juju
 released in Danube. I wonder why use the name TripleO instead of Apex?

 I have discussed at Arno and Brahmaputra about how to release OPNFV
 artifacts, and the conclusion is in ISO or source codes. Why release RPMs
 for Apex? It is different from other installers. The release content or
 list are different in OPNV download page. It is really strange.

 BR,
 Julien


 David McBride 于2017年5月6日周六 上午5:20写道：

> TSC members,
>
> I'm pleased to let you know that OPNFV Danube 2.0 has been released.
> Software and documentation may be accessed here
> .
>
> Congratulations to everyone in the community that worked hard to make
> this happen.  Please let me know if you have questions or comments.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>

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

Re: [opnfv-tech-discuss] OPNFV at OpenStack-Boston

[soth]

Hello all,

For people not being in Boston, is there any chance to attend some 
events or to have access to presented stuff?


BRs

Thomas


On 08/05/17 17:54, Raymond Paik wrote:
I forgot to mention that the Republic Ballroom for Tuesday is at the 
Sheraton Hotel, which is connected to the convention center...


Thanks,

Ray

On Sun, May 7, 2017 at 12:48 PM, Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:


All,

For those of you attending the OpenStack Summit this week, I
wanted to give a few quick reminders.

First, as part of OPNFV Open Source Days, we have a large meeting
room (Republic Ballroom) on Tuesday that we can use for meetings,
discussions, hacking, etc. Feel free to add your topics on the
wiki at
https://wiki.opnfv.org/display/EVNT/OPNFV+at+OpenStack+Summit+-+Boston


Secondly, OPNFV will also have a booth in the exhibit hall and we
still need community volunteers for several slots (ideally, we'd
like to have 2 people in the booth at all times).  If you have an
hour of two to spare during the week please add your name to the
above wiki page.

Thanks and look forward to seeing many of you in Boston.

Ray




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


--

Sounapoglou Thomas
Software Engineer

SDN- NFV Department
Thessaloniki Branch
INTRACOM TELECOM
Marinou Antypa 41
57001 Thermi, Thessaloniki, Greece
tel: +30 2310 497 332
fax: +30 2310 497 330
e-mail: _soth@intracom-telecom.com_ 
_www.intracom-telecom.com _


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.


___
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] [yardstick] Yardstick PTL Election

[morgan.richomme]

"Be a yardstick of quality. Some people aren't used to an environment
where excellence is expected" S.Jobs

Thanks to you and the yardstick team, more and more people are used to it.

Thanks for everything: great job from a great PTL!

Morgan

Le 05/05/2017 à 14:43, Gaoliang (kubi) a écrit :
>
> Hi All ,
>
>  
>
> To keep the team diversity, bring new ideas and energy, we have
> finalized the Yardstick PTL election process[1] with team(similar with
> Functest’s process).
>
>  
>
> We will start the Yardstick PTL election Process today, As the process
> described, “Calls for nomination will be open for a 2 weeks process”,
>  so we will end the nomination at May 19th
>
>  
>
> Election would be open to any Yardstick committer[2] (+2/-2) , Then we
> will have one week to vote with http://civs.cs.cornell.edu/
>
>  
>
> As I have been yardstick PTL for 2 release(C, D), I will step down
> once new PTL has been elected.  All nomination are warmly welcome,
> let’s make yardstick better and better
>
>  
>
> So Please feel free to nominate yourself and other committers before
> May 19th with this email thread.  Thanks J
>
>  
>
>  
>
> [1] https://wiki.opnfv.org/display/yardstick/Yardstick+PTL+Election
>
> [2] https://wiki.opnfv.org/display/yardstick/People
> 
>
>  
>
> Regards,
>
> Kubi
>
>
>
> ___
> test-wg mailing list
> test...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/test-wg


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