date:20170327

Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV Summit CFP

2017-03-27 Thread ltaback

Hi Gerald,
Would this project breakout be open to anyone? Is the preferred day on 
Wednesday or Thursday or could you have this meeting on Tuesday during Design 
Summit?

Lara

Lara Taback
949.466.8056
ltab...@linuxfoundation.org

> On Mar 27, 2017, at 2:38 AM, Kunzmann, Gerald  
> wrote:
> 
> Dear Brandon, OPNFV Events-Team,
> 
> If I want to reserve a room at the OPNFV summit for a project team meeting / 
> breakout session, do I also need to request this through the CfP page as 
> "breakout session"?
> 
> Best regards,
> Gerald
> 
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of yunhong jiang
> Sent: Dienstag, 21. März 2017 21:12
> To: Brandon Wick 
> Cc: opnfv-tech-dis. 
> Subject: Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV 
> Summit CFP
> 
> On Tue, 21 Mar 2017 12:55:25 -0700
> Brandon Wick  wrote:
> 
>> Hello Jiang,
>> 
>> Thanks for your question. Please send any future questions to
>> eve...@opnfv.org.
>> 
>> The Design Summit takes place June 12-13 and is where the OPNFV
>> technical community will convene to continue working on the E-Release
>> and have plenary sessions and project breakouts. It is very focused
>> on the OPNFV platform. The Summit Conference takes place Jun 14-15
>> and is for the wider NFV ecosystem, featuring keynotes, breakout
>> sessions, a technology showcase, networking opportunities, etc. This
>> is where the the breakouts will be structured into the six tracks.
>> Panels consist of 4 or more speakers in a single session. When in
>> doubt, we recommend you submit for the Summit conference as a
>> breakout session. From there, our track chairs will be able to make
>> further recommendations as needed.
> 
> Hi, Brandon,
>Thanks for the reply and it's clear now.
> 
> --jyh
> 
>> 
>> Best,
>> 
>> 
>> Brandon Wick
>> OPNFV Head of Marketing, The Linux Foundation
>> Mobile: +1.917.282.0960  Skype: wick.brandon
>> Email / Google Talk: bw...@linuxfoundation.org
>> 
>> *The OPNFV Summit CFP Closes 3/27!
>> *
>> 
>> On Tue, Mar 21, 2017 at 12:31 PM, yunhong jiang <
>> yunhong.ji...@linux.intel.com> wrote:
>> 
>>> Hi, Brandon,
>>>When I try to submit the CFP, I noticed there are two types of
>>> the session. One is for Design Summit session and one is for OPNFV
>>>Summit session. Are there any key differences of these two? I
>>>attended the Openstack summit before and they are quite
>>> different there.
>>> 
>>>Also on the Design Summit session, there are two formats called
>>>break out session and panel discussion. What's the difference of
>>>them? How should I decide which format should my session be?
>>> 
>>>Hope your guide on this, thanks!
>>> 
>>> -jyh
>>> 
>>> On Mon, 20 Mar 2017 07:24:43 -0700
>>> Brandon Wick  wrote:
>>> 
 OPNFV Technical Community:
 
 This is a reminder that the CFP for the OPNFV Summit
 , June
 12-15, Beijing, China, closes *Monday, March 27*. We encourage
 you to prepare and submit a proposal by the deadline. The six
 primary tracks are the following:
 
   - NFV Applications and Orchestration
   - Testing, Infrastructure, and DevOps
   - NFV Strategy and End User Stories
   - NFV Platform Requirements
   - Community and Upstream
   - Futures and Research
 
 *Access the CFP Here
 >> details>*
 
 We look forward to your submissions. If you have any questions,
 please email eve...@opnfv.org.
 
 Best,
 
 Brandon Wick
 OPNFV Head of Marketing, The Linux Foundation
 Mobile: +1.917.282.0960  Skype: wick.brandon
 Email / Google Talk: bw...@linuxfoundation.org
>>> 
>>> 
> 
> ___
> 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] Request to contribute to yardstick

2017-03-27 Thread Gaoliang (kubi)

Hi Jing,

Warmly welcome to Yardstick team:)
I’m very glad to know your team have used Yardstick to benchmark your Software 
and extend the framework. That would be a very good news for yardstick.
So I added you into Yardstick Contributors List[1], I will send the your 
attachment to Yardstick team to review.
Welcome to Join the Yardstick Weekly Meeting[2] to discuss:)

[1]  https://wiki.opnfv.org/display/yardstick/People
[2] https://wiki.opnfv.org/display/yardstick/Meetings

Regards,
Kubi
发件人: Zhang, Jing C. (Nokia - CA/Ottawa) [mailto:jing.c.zh...@nokia.com]
发送时间: 2017年3月28日 2:30
收件人: Gaoliang (kubi) 
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: Request to contribute to yardstick

Dear Yardstick,

We, Nokia Cloudband, have been using Yardstick to benchmark our Cloudband 
Intrastructure Software (CBIS) since Colorado is released last October, mainly 
in areas of throughput and latency.

We are big fans of the framework and have done a list of extenstions, our 
benchmarking results are well received by our partners and cusstomers.

I have attached a high level review of contents we propose to contribute, 
please review and let me know of your decisions. After this, we plan to move to 
the new Danube release when it becomes available.

Thank you and Best Regards

Jing


Jing Zhang
System Architect,
Cloudband, Nokia
External: +1-613-784-1839
OnNet: 2-825-1839



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

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

2017-03-27 Thread joehuang

Hello, Valentin,

Thank you very much for the clear expectation.

There is some challenge to put net3 directly between R1 and R2. If R1 and R2 
are centralized routers, then ext-net1 is the external network for R1, and net3 
could be router-interface-add to R1. Because R1 and R2 are centralized routers, 
it's possible to setup vxlan tunnel between R1 and R2 node, for the vxlan 
endpoints of R1 and R2 are fixed and limited.

But if R1 or R2 is DVR(distributed virtual router), then R1/R2 will be 
presented in many compute nodes, if net3 is attached to both R1 and R2, then 
almost all compute nodes will be involved to setup the tunnel for R1/R2, there 
are too many management messages for the tunnelig setup, and hard to manage so 
many point to point tunneling for R1/R2.

To reduce the tunneling endpoints between DVR routers, we have to use the 
centralized node for the DVR, which is used for north-south traffic, so net3 
should be only setup in the centralized node of DVR. But in Neutron networking 
mode, a router can only be attached to one external network, and only external 
network is determined in centralized node. If we want to support a general mode 
for east-west traffic between networks in different OpenStack, we have to 
address DVR and one external network constraint.

We understand the requirement to have north-south path in each OpenStack, while 
at the same to east-west traffic should also be enabled for networks. One spec 
has been prepared (and code will be available soon) to fulfill this demand:

https://review.openstack.org/#/c/448359/3/specs/pike/l3-networking-multi-NS-with-EW-enabled.rst


+---+ +--+
|   ext-net1| |   ext-net2   |
|  +---+---+| |+--+---+  |
|RegionOne || | RegionTwo |  |
|  +---+---+| |  ++--+   |
|  |  R1   || |  |  R2   |   |
|  +--++| |  +--++   |
| | net1| |net2 ||
| +---+--+---+-+| |   ++-+--+---+|
||   |  | || |   |
|  +-+-+ |  | ||  +--++  |
|  | Instance1 | |  | ||  | Instance2 |  |
|  +---+ |  | ||  +---+  |
|   ++--+   | bridge-net  |  +-+-+   |
|   | R3(1) ++ R3(2) |   |
|   +---+   | |  +---+   |
+---+ +--+
 Figure.1 Multiple external networks with east-west networking

Instance1 and Instance2 still only have one network interface. But we introduce 
a logical router R3(1), R3(2) and bridge-net for east-west traffic between 
OpenStack clouds, that means cross OpenStack cloud traffic will totally 
separated from traffic inside one OpenStack cloud and north-south traffic. 
bridge-net is the external network of R3(1) and R3(2).

The traffic will goes out like this:

Now, north-south traffic of Instance1 and Instance2 work like follows::

Instance1 -> net1 -> R1 -> ext-net1
Instance2 -> net2 -> R2 -> ext-net2

Only one hop for north-south traffic.

East-west traffic between Instance1 and Instance2 work like follows::

Instance1 <-> net1 <-> R3(1) <-> bridge-net <-> R3(2) <-> net2 <-> Instance2

Two hops for cross OpenStack east-west traffic.


Of course Tricircle can help to realize this topology with networking 
automation:

The logical topology in central Neutron where Tricircle plugin will work look 
like as follows:

 ext-net1 ext-net2
+---+  +--+---+
| |
+---+---+++--+
|  R1   ||  R2   |
+--+++--++
   | net1  net2 |
   +---+--+---++  ++-+--+---+
  |   || |
+-+-+ ||  +--++
| Instance1 | ||  | Instance2 |
+---+ ||  +---+
+-++--+
|   R3|
+-+

Figure.2 Logical topology in central Neutron

It's easy to create a such topology with the help of Tricircle. For more 
detail, you can refer to the spec:

https://review.openstack.org/#/c/448359/3/specs/pike/l3-networking-multi-NS-with-EW-enabled.rst


Please note that R1 R2 and R3 are only logical routers, the total traffic 
handled by router R1, R2 and R3 for the instances are same as the topology you 
provided.

We can prioritize this feature in Tricricle, so that it can be available to be 
used in the PoC in OPNFV Beijing Summit. Currently one video conference APP is 
planned to be used in the PoC, would you support to

Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

2017-03-27 Thread Addepalli, Srinivasa R

Hi,

Main advantage of Unikernels is that  they enable on-demand bring up (JITSU).  
If  we go with traditional schedulers such as NOVA, Kubernetes to bring up 
unikernels,  this benefit is masked.  I think this WG scope needs to be 
expanded to integrated approach of using both traditional schedulers with JITSU 
kind of schedulers.  For example, in case of unikernels, traditional schedulers 
can choose the compute node, transfer the image to selected compute node,  get 
the configuration updated in the image to make it immutable at run time, but 
not bring up.   JITSU sitting in the compute node can bring up upon event (eg. 
Packet). I hope that this capability is very important to show the benefits of 
unikernels.  Let me know if you want this to be in scope (which I like to see)  
and I can send some thought slides on this.

Thanks
Srini

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Amar Kapadia
Sent: Monday, March 27, 2017 1:20 PM
To: Dave Neary 
Cc: Wassim Haddad ; 
opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of 
OpenRetriever(OR) Project as NGVS is merging into OR

The goal of NGVS is to look at scheduler enhancements or a new scheduler to 
support containers, VMs and unikernels with static and serverless scheduling 
(I'm skipping a bunch of details). It's possible that we might come to the 
conclusion that Nova with enhancements is the right answer, or that a COE 
(container orchestration engine) is a better option. Given that our primary 
goal is around what I mentioned, and not so much around enhancing the 
functionality of existing VM centric scheduling, joining OR seems like a better 
fit...

Thanks,
Amar

On Mon, Mar 27, 2017 at 7:14 AM, Dave Neary 
> wrote:
Hi,

I saw the scope of NGVS was primarily focussed on containers, but it
occurred to me that there is an opportunity to retune the project to
define instance scheduling requirements for OpenStack in general -
essentially, use the project as a vehicle for evolving the Nova scheduler.

Is this not the plan? If it is, the merger with OpenRetriever might not
help move towards that goal, as it creates an impression that this is
entirely container focussed.

Thanks,
Dave.

On 03/27/2017 09:58 AM, HU, BIN wrote:
> Adding opnfv-tsc mailing list too.
>
>
>
> *From:*jiaxuan 
> [mailto:jiax...@chinamobile.com]
> *Sent:* Monday, March 27, 2017 6:37 AM
> *To:* 
> opnfv-tech-discuss@lists.opnfv.org
> *Cc:* 'Amar Kapadia' 
> >; HU, BIN 
> >
> *Subject:* [opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR)
> Project as NGVS is merging into OR
>
>
>
> After a good talk with Nextgen VIM Scheduler (NGVS) project, we decide
> to expand the scope of OpenRetriever(OR) and let NGVS merge into OR.
> NGVS will be as a sub-project of OR.
>
> TSC need community to revised the changes of OR’s scope for 2 weeks.
> Then bring to TSC for review and approval.
>
>
>
> Scope:
>
> OR focuses on how non-virtual-machine based VNF run in NFV. It includes
> container and unikernels. The target of this project is let VNF can run
> on any platform including OpenStack, Kubernetes, Mesos and so on. The
> project doesn’t cover the internal architecture of a VNF.
>
>
>
> 1.  Add Kuryr and Magnum into installers
>
>
>
> 2.  Container for NFV. The main function is to increase the performance
> of container and container platform.
>
>
>
> 3.  Set up an environment which can support container and unikernel.
>
>
>
> 4.  A new scheduler that can schedule a mix of all three types (virtual
> machine, container, unikernel) of instances.
>
>
>
> 5.  Analyse the gap for OpenStack, Installer, Kubernetes, MANO.
>
>
>
>
>
> Key work items include:
>
> 1. Documentation:
>
>
>
> 1) The requirement of OpenStack, Installer, Kubernetes, MANO
>
>
>
> 2) The requirement of Nextgen VIM Scheduler.
>
>
>
> 3) The user guide: Set up an environment which can support container
> and unikernels.
>
>
>
> 2. Scripts : Common scripts to let container be integrated into OPNFV
>
>
>
> 3. Testing:  Provide for Functest , Yardstick etc.
>
>
>
>
>
> Committers and Contributors:
>
> Project Leader: Xuan Jia ( 
> jiax...@chinamobile.com
> >)
>
> Committer:
>
>  Csatari, Gergely ( 
> gergely.csat...@nokia.com
> > )
>
>  Lijun ( matthew.li...@huawei.com
> > )
>
>  Xuan Jia (

Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

2017-03-27 Thread Amar Kapadia

The goal of NGVS is to look at scheduler enhancements or a new scheduler to
support containers, VMs and unikernels with static and serverless
scheduling (I'm skipping a bunch of details). It's possible that we might
come to the conclusion that Nova with enhancements is the right answer, or
that a COE (container orchestration engine) is a better option. Given that
our primary goal is around what I mentioned, and not so much around
enhancing the functionality of existing VM centric scheduling, joining OR
seems like a better fit...

Thanks,
Amar


On Mon, Mar 27, 2017 at 7:14 AM, Dave Neary  wrote:

> Hi,
>
> I saw the scope of NGVS was primarily focussed on containers, but it
> occurred to me that there is an opportunity to retune the project to
> define instance scheduling requirements for OpenStack in general -
> essentially, use the project as a vehicle for evolving the Nova scheduler.
>
> Is this not the plan? If it is, the merger with OpenRetriever might not
> help move towards that goal, as it creates an impression that this is
> entirely container focussed.
>
> Thanks,
> Dave.
>
> On 03/27/2017 09:58 AM, HU, BIN wrote:
> > Adding opnfv-tsc mailing list too.
> >
> >
> >
> > *From:*jiaxuan [mailto:jiax...@chinamobile.com]
> > *Sent:* Monday, March 27, 2017 6:37 AM
> > *To:* opnfv-tech-discuss@lists.opnfv.org
> > *Cc:* 'Amar Kapadia' ; HU, BIN <
> bh5...@att.com>
> > *Subject:* [opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR)
> > Project as NGVS is merging into OR
> >
> >
> >
> > After a good talk with Nextgen VIM Scheduler (NGVS) project, we decide
> > to expand the scope of OpenRetriever(OR) and let NGVS merge into OR.
> > NGVS will be as a sub-project of OR.
> >
> > TSC need community to revised the changes of OR’s scope for 2 weeks.
> > Then bring to TSC for review and approval.
> >
> >
> >
> > Scope:
> >
> > OR focuses on how non-virtual-machine based VNF run in NFV. It includes
> > container and unikernels. The target of this project is let VNF can run
> > on any platform including OpenStack, Kubernetes, Mesos and so on. The
> > project doesn’t cover the internal architecture of a VNF.
> >
> >
> >
> > 1.  Add Kuryr and Magnum into installers
> >
> >
> >
> > 2.  Container for NFV. The main function is to increase the performance
> > of container and container platform.
> >
> >
> >
> > 3.  Set up an environment which can support container and unikernel.
> >
> >
> >
> > 4.  A new scheduler that can schedule a mix of all three types (virtual
> > machine, container, unikernel) of instances.
> >
> >
> >
> > 5.  Analyse the gap for OpenStack, Installer, Kubernetes, MANO.
> >
> >
> >
> >
> >
> > Key work items include:
> >
> > 1. Documentation:
> >
> >
> >
> > 1) The requirement of OpenStack, Installer, Kubernetes, MANO
> >
> >
> >
> > 2) The requirement of Nextgen VIM Scheduler.
> >
> >
> >
> > 3) The user guide: Set up an environment which can support container
> > and unikernels.
> >
> >
> >
> > 2. Scripts : Common scripts to let container be integrated into OPNFV
> >
> >
> >
> > 3. Testing:  Provide for Functest , Yardstick etc.
> >
> >
> >
> >
> >
> > Committers and Contributors:
> >
> > Project Leader: Xuan Jia ( jiax...@chinamobile.com
> > )
> >
> > Committer:
> >
> >  Csatari, Gergely ( gergely.csat...@nokia.com
> >  )
> >
> >  Lijun ( matthew.li...@huawei.com
> >  )
> >
> >  Xuan Jia ( jiax...@chinamobile.com
> >  )
> >
> >  Peng Yu ( yu.pen...@zte.com.cn  )
> >
> >  Wassim Haddad ( wassim.had...@ericsson.com
> >  )
> >
> >  Heikki Mahkonen ( heikki.mahko...@ericsson.com
> >  )
> >
> >  Amar Kapadia ( akapa...@aarnanetworks.com
> >  )
> >
> >  Sriram Rupanagunta ( srupanagu...@gmail.com
> >  )
> >
> > Contributors:
> >
> >  Guo Ruijing ( ruijing@intel.com 
> )
> >
> >  Srinivasa Addepalli (srinivasa.r.addepa...@intel.com
> >  )
> >
> >  Pradip Rawat (pradipkum...@biarca.com
> >  )
> >
> >  Ganesh Kaila (gane...@biarca.com  )
> >
> >
> >
> >
> >
> > Planned deliverables:
> >
> > 1. Documentation and User Guide
> >
> >
> >
> > 2. Scripts.
> >
> >
> >
> >
> >
> > Proposed Released Schedule:
> >
> > 1. NGVS is completed by E-release
> >
> >
> >
> > 2. Gap analysis and requirement documentation by E-release
> >
> >
> >
> > 3. Integration scripts for container by E-release
> >
> >
> >
> >
> >
> > Initial proposal:
> >
> > NGVS Proposal
> > (https://wiki.opnfv.org/pages/viewpage.action?pageId=10290307 )
> >
> > OpenRetriver

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][euphrates] Intent-to-Participate window for Euphrates

2017-03-27 Thread Reddy, Raghuveer

Hi David,
KVM4NFV project intends to participate in the Euphrates release.
Thanks,
-Raghu

From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Sunday, March 26, 2017 6:57 PM
To: TECH-DISCUSS OPNFV ; 
opnfv-project-leads ; TSC OPNFV 

Subject: [opnfv-tsc] [release][euphrates] Intent-to-Participate window for 
Euphrates

Team,

I'm excited to announce that the intent-to-participate window will open on 
Monday, March 27, and will remain open until 5 p.m. on April 24 (MS1).

The process is documented 
here, 
but essentially just requires sending an email to the TSC mailing list.  Note 
that your project must have been approved by the TSC before you may join a 
release.

Once you have stated your intent to participate, you must complete your release 
planning by MS1 on April 24.  This includes completing the release plan 
summary.

Please let me know if you have any questions.

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

[opnfv-tech-discuss] Join us for a Reception at Levi's Stadium on April 3rd

2017-03-27 Thread Brandon Wick

OPNFV Technical Community:

We invite you to join OPNFV and the open source networking communities for
an evening reception at Levi's Stadium, a short walk from the Santa Clara
Convention Center. Meet representatives and community members from OPNFV,
OpenDaylight, OpenStack, Fd.io and ONAP along with our sponsors Serro,
Juniper, and Inocybe. Light food and drinks will be provided. *Space is
limited - *please RSVP * to reserve
your spot! *Note: We will be playing the NCAA Mens Basketball final as well!

*Open Source Community Reception*

Sponsored by Serro, Juniper, and Inocybe
Date: Monday, April 3
Time: 6:00 - 10:00 pm
Location: Levi's Stadium, Yahoo! Fantasy Football Lounge
See the walking map 

Please send any questions to eve...@opnfv.org and we hope to see you there!

Best,

Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org

*OPNFV Summit CFP closes April 10!
*
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Meetings

2017-03-27 Thread Jack Morgan


  
  
OPNFV,
  
As some of Europe changed time zones over the
  weekend, I think its good to revisit how to
  track meetings in OPNFV. This is what I have documented
  for myself...


I. GoToMeeting (GTM) accounts


(1) For meetings starting during odd-number hours
Pacific Time (e.g. 5am, 7am, 9am,
11am, or 1:30am etc.)
  

https://global.gotomeeting.com/join/144838637




(2) For meetings starting during even-number hours
Pacific Time (e.g. 6am, 8am, 10am,
or 4:30pm, etc.)
https://global.gotomeeting.com/join/819733085
  
If you are using some other GTM meeting besides the above
  (see below), you might migrate to one of these. GTM accounts can
  be confusing. LF only has two GTM accounts which contain multiple
  meetings within them (listed below). Using a meeting within the
  same account, will cause any other meeting within that account to
  end as you can only have one meeting per account at a time. 

Even though it says Pacific Time
above, most people are not following this. It might be good for
TSC to make a "ruling" here as we don't have a standard way of
doing things in practice. 


  Here are the meetings I found...
  
  #1 Account:
  
  OPNFV Tech Projects Meetings (primary meeting)
  
  Can we remove these?
  OPNFV plugfest biweekly meeting
  HA project meeting
  Promise Team Meeting
  Openstack based VNFFG Bi-Weekly Meeting
  Escalator Weekly Meeting @ Winter
  OPNFV Test & Performance working group
  ONOSFW Bi-Weekly meeting
  opnfv-bottlenecks
  RS Team Weekly Meeting
  Doctor Team Meeting
  Nanocell GW NFV产品测试周会
  Pinpoint Team Meeting
  Movie weekly meeting
  Yardstick Work Meeting
  eNFV Bi-Weekly Call
  Multisite weekly meeting
  OPNFV_Connectivity Services LSO weekly meeting
  OPNFV NetReady weekly meeting
  ARM Band Project Meeting
  Genesis weekly meeting
  OPNFV Domino Weekly Meetings
  OPNFV Bootstrap/GetStarted weekly team meeting
  Prediction Weekly Meeting
  Escalator Weekly Meeting
  Qtip meeting
  JOID weekly
  OpenStack BP discussion for service chaining (VNFFG)
  dpacc weekly meeting (Europe)
  dpacc weekly meeting (America)
  Octopus weekly meeting
  OPNFV Parser Project Weekly Meeting
  StorPerf Team Meeting
  Copper/Models Project Meeting
  Dovetail weekly meeting
  Compass4nfv Weekly Meeting
  Test bi-weekly meeting
  Security Group Meeting
  NetReady
  OPNFV Test & Performance Working group (APAC)
  OPNFV MANO Workgroup meeting
  dpacc weekly meeting
  Functest
  VSPERF weekly meeting
  
  
  
  #2 Account:
  
  OPNFV Tech Projects2 Meetings (primary meeting)
  
Can we remove these?
  NFV Hypervisors-KVM weekly team meeting
  Promise team meeting
  Barometer Weekly Call Tuesdays
  NetReady weekly meeting
  Dovetail weekly meeting
  OVSNFV Weekly Mondays 6am Pacific
  VSPERF weekly meeting



II. Tracking your meetings
  
I know of three possible places to document your meetings
  details. Its important to do so so others don't schedule a meeting
  on top of your meeting. I'm going to use the Infra WG as an
  example.

  1) Meetings space in wiki (link)
You should have a wiki page for your project/group and
  documenting your meeting details there. For Infra WG, we have this
  wiki page:
  https://wiki.opnfv.org/display/meetings/Infra+Working+Group+Meeting

  2) Meetings calendar (link)
You should add an event for your meeting to this group calendar.
  This should be the default location everyone goes to confirm there
  is no other meeting at the time you would like to have your
  meeting. You would add an event based on the type of meeting. For
  example, IRC only, GTM, Blue Jeans, WebEX, etc

  3) Your project space
You might also have meeting details in your own project/group
  wiki space. For Infra WG, we have this page:
  https://wiki.opnfv.org/display/INF/Infra+Working+Group


I know everyone is busy, but let's make an effort to keep track
  our meetings and use the correct GTM account (if you use GTM). Its
  no fun to have your GTM session closed because another meeting is
  using the same GMT account at the same time.  



Thanks,
-- 
Jack Morgan
OPNFV Pharos Intel Lab
  

___
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][euphrates] Intent-to-Participate Moon

2017-03-27 Thread ruan.he

Hi Davide and Hi all,
Moon project intends to participate in the Euphrates release. We will work on 
the security management of different functions and upstream some parts to 
OpenStack, OpenDaylight, etc.
Best Regards,
Ruan HE

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: lundi 27 mars 2017 03:57
To: TECH-DISCUSS OPNFV; opnfv-project-leads; TSC OPNFV
Subject: [opnfv-tech-discuss] [release][euphrates] Intent-to-Participate window 
for Euphrates

Team,

I'm excited to announce that the intent-to-participate window will open on 
Monday, March 27, and will remain open until 5 p.m. on April 24 (MS1).

The process is documented 
here, 
but essentially just requires sending an email to the TSC mailing list.  Note 
that your project must have been approved by the TSC before you may join a 
release.

Once you have stated your intent to participate, you must complete your release 
planning by MS1 on April 24.  This includes completing the release plan 
summary.

Please let me know if you have any questions.

David

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

_

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

Re: [opnfv-tech-discuss] Euphrates release project proposal: CORD

2017-03-27 Thread HU, BIN

This is on the agenda too.

Thanks
Bin
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Monday, March 27, 2017 8:11 AM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: [opnfv-tech-discuss] Euphrates release project proposal: CORD

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hi all,

Please see https://wiki.opnfv.org/display/PROJ/CORD for the proposal of the 
CORD deployment project for OPNFV. This is intended to start in the Euphrates 
release.
We can have a discussion here or at 
https://techdiscuss.opnfv.org/t/cord-new-opnfv-project-proposal/93.
Indications of support and as contributors for the project are welcome. If you 
want to contribute, please ensure that you have the time to be active - we can 
discuss the types of roles and activity expectations if you are interested.

We are planning to bring this for approval to the TSC ASAP, so we need to get 
on the Technical Community call agenda ASAP (this week).

Thanks,
Bryan Sullivan | AT

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

[opnfv-tech-discuss] Euphrates release project proposal: CORD

2017-03-27 Thread SULLIVAN, BRYAN L

Hi all,

Please see https://wiki.opnfv.org/display/PROJ/CORD for the proposal of the 
CORD deployment project for OPNFV. This is intended to start in the Euphrates 
release.
We can have a discussion here or at 
https://techdiscuss.opnfv.org/t/cord-new-opnfv-project-proposal/93.
Indications of support and as contributors for the project are welcome. If you 
want to contribute, please ensure that you have the time to be active - we can 
discuss the types of roles and activity expectations if you are interested.

We are planning to bring this for approval to the TSC ASAP, so we need to get 
on the Technical Community call agenda ASAP (this week).

Thanks,
Bryan Sullivan | AT

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

Re: [opnfv-tech-discuss] Euphrates release project proposal: Armada

2017-03-27 Thread HU, BIN

I have put it as the 1st agenda item this Thursday

From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Monday, March 27, 2017 7:26 AM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: [opnfv-tsc] Euphrates release project proposal: Armada

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hi all,

Please see 
https://wiki.opnfv.org/display/PROJ/Armada
 for the proposal of a new installer project for OPNFV. This is intended to 
start in the Euphrates release.
We can have a discussion here or at 
https://techdiscuss.opnfv.org/t/armada-new-opnfv-installer-project-proposal/92.
Indications of support and as contributors for the project are welcome. If you 
want to contribute, please ensure that you have the time to be active - we can 
discuss the types of roles and activity expectations if you are interested.

We are planning to bring this for approval to the TSC ASAP, so we need to get 
on the Technical Community call agenda ASAP (this week).

Thanks,
Bryan Sullivan | AT

___
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][ovs-opnfv] Scenario status and meeting today.

2017-03-27 Thread Thomas F Herbert




On 03/27/2017 10:16 AM, O Mahony, Billy wrote:


Hi Tom,

Yes, the clocks changed in Europe at the weekend and I forgot that 
Outlook talks in local time.



OK, 1500 hours local time Ireland is fine.


Can we synch, if required, via email?

/Billy

*From:*Thomas F Herbert [mailto:therb...@redhat.com]
*Sent:* Monday, March 27, 2017 3:10 PM
*To:* opnfv-tech-discuss@lists.opnfv.org; Gray, Mark D 
; O Mahony, Billy 

*Cc:* David McBride 
*Subject:* [opnfv][ovs-opnfv] Scenario status and meeting today.

I thought today's meeting was at 1400 UTC.

I updated scenario status page. Releng patch was merged Friday which 
adds 3 Apex DPDK scenarios to master Friday. Hasn't been cherry-picked 
to Danube yet. I updated scenario page, 
https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status.


--Tom

--
*Thomas F Herbert*
SDN Group
Office of Technology
*Red Hat*



--
*Thomas F Herbert*
SDN Group
Office of Technology
*Red Hat*
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Euphrates release project proposal: Armada

2017-03-27 Thread SULLIVAN, BRYAN L

Hi all,

Please see https://wiki.opnfv.org/display/PROJ/Armada for the proposal of a new 
installer project for OPNFV. This is intended to start in the Euphrates release.
We can have a discussion here or at 
https://techdiscuss.opnfv.org/t/armada-new-opnfv-installer-project-proposal/92.
Indications of support and as contributors for the project are welcome. If you 
want to contribute, please ensure that you have the time to be active - we can 
discuss the types of roles and activity expectations if you are interested.

We are planning to bring this for approval to the TSC ASAP, so we need to get 
on the Technical Community call agenda ASAP (this week).

Thanks,
Bryan Sullivan | AT

___
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][ovs-opnfv] Scenario status and meeting today.

2017-03-27 Thread O Mahony, Billy

Hi Tom,

Yes, the clocks changed in Europe at the weekend and I forgot that Outlook 
talks in local time.

Can we synch, if required, via email?

/Billy

From: Thomas F Herbert [mailto:therb...@redhat.com]
Sent: Monday, March 27, 2017 3:10 PM
To: opnfv-tech-discuss@lists.opnfv.org; Gray, Mark D ; O 
Mahony, Billy 
Cc: David McBride 
Subject: [opnfv][ovs-opnfv] Scenario status and meeting today.


I thought today's meeting was at 1400 UTC.

I updated scenario status page. Releng patch was merged Friday which adds 3 
Apex DPDK scenarios to master Friday. Hasn't been cherry-picked to Danube yet. 
I updated scenario page, 
https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status.



--Tom

--
Thomas F Herbert
SDN Group
Office of Technology
Red Hat
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

2017-03-27 Thread Dave Neary

Hi,

I saw the scope of NGVS was primarily focussed on containers, but it
occurred to me that there is an opportunity to retune the project to
define instance scheduling requirements for OpenStack in general -
essentially, use the project as a vehicle for evolving the Nova scheduler.

Is this not the plan? If it is, the merger with OpenRetriever might not
help move towards that goal, as it creates an impression that this is
entirely container focussed.

Thanks,
Dave.

On 03/27/2017 09:58 AM, HU, BIN wrote:
> Adding opnfv-tsc mailing list too.
> 
>  
> 
> *From:*jiaxuan [mailto:jiax...@chinamobile.com]
> *Sent:* Monday, March 27, 2017 6:37 AM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Cc:* 'Amar Kapadia' ; HU, BIN 
> *Subject:* [opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR)
> Project as NGVS is merging into OR
> 
>  
> 
> After a good talk with Nextgen VIM Scheduler (NGVS) project, we decide
> to expand the scope of OpenRetriever(OR) and let NGVS merge into OR.
> NGVS will be as a sub-project of OR.
> 
> TSC need community to revised the changes of OR’s scope for 2 weeks.
> Then bring to TSC for review and approval.
> 
>  
> 
> Scope:
> 
> OR focuses on how non-virtual-machine based VNF run in NFV. It includes
> container and unikernels. The target of this project is let VNF can run
> on any platform including OpenStack, Kubernetes, Mesos and so on. The
> project doesn’t cover the internal architecture of a VNF.
> 
>  
> 
> 1.  Add Kuryr and Magnum into installers
> 
>  
> 
> 2.  Container for NFV. The main function is to increase the performance
> of container and container platform.
> 
>  
> 
> 3.  Set up an environment which can support container and unikernel.
> 
>  
> 
> 4.  A new scheduler that can schedule a mix of all three types (virtual
> machine, container, unikernel) of instances.
> 
>  
> 
> 5.  Analyse the gap for OpenStack, Installer, Kubernetes, MANO.
> 
>  
> 
>  
> 
> Key work items include:
> 
> 1. Documentation:
> 
>  
> 
> 1) The requirement of OpenStack, Installer, Kubernetes, MANO
> 
>  
> 
> 2) The requirement of Nextgen VIM Scheduler.
> 
>  
> 
> 3) The user guide: Set up an environment which can support container
> and unikernels.
> 
>  
> 
> 2. Scripts : Common scripts to let container be integrated into OPNFV
> 
>  
> 
> 3. Testing:  Provide for Functest , Yardstick etc.
> 
>  
> 
>  
> 
> Committers and Contributors:   
> 
> Project Leader: Xuan Jia ( jiax...@chinamobile.com
> )
> 
> Committer:
> 
>  Csatari, Gergely ( gergely.csat...@nokia.com
>  ) 
> 
>  Lijun ( matthew.li...@huawei.com
>  )
> 
>  Xuan Jia ( jiax...@chinamobile.com
>  )
> 
>  Peng Yu ( yu.pen...@zte.com.cn  )
> 
>  Wassim Haddad ( wassim.had...@ericsson.com
>  )
> 
>  Heikki Mahkonen ( heikki.mahko...@ericsson.com
>  )
> 
>  Amar Kapadia ( akapa...@aarnanetworks.com
>  )
> 
>  Sriram Rupanagunta ( srupanagu...@gmail.com
>  )
> 
> Contributors:
> 
>  Guo Ruijing ( ruijing@intel.com  )
> 
>  Srinivasa Addepalli (srinivasa.r.addepa...@intel.com
>  )
> 
>  Pradip Rawat (pradipkum...@biarca.com
>  )
> 
>  Ganesh Kaila (gane...@biarca.com  )
> 
>  
> 
>  
> 
> Planned deliverables:
> 
> 1. Documentation and User Guide
> 
>  
> 
> 2. Scripts.
> 
>  
> 
>  
> 
> Proposed Released Schedule:
> 
> 1. NGVS is completed by E-release
> 
>  
> 
> 2. Gap analysis and requirement documentation by E-release
> 
>  
> 
> 3. Integration scripts for container by E-release
> 
>  
> 
>  
> 
> Initial proposal:
> 
> NGVS Proposal
> (https://wiki.opnfv.org/pages/viewpage.action?pageId=10290307 )
> 
> OpenRetriver Proposal
> (https://wiki.opnfv.org/display/PROJ/Project+Proposals+OpenRetriever )
> 
>  
> 
> If you have any question ,please follow this email. Thanks
> 
>  
> 
> Xuan Jia
> 
> Mobile: (+86) 13811000575
> 
> E-mail: jiax...@chinamobile.com 
> 
>  
> 
> 
> 
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [opnfv][ovs-opnfv] Scenario status and meeting today.

2017-03-27 Thread Thomas F Herbert


I thought today's meeting was at 1400 UTC.

I updated scenario status page. Releng patch was merged Friday which 
adds 3 Apex DPDK scenarios to master Friday. Hasn't been cherry-picked 
to Danube yet. I updated scenario page, 
https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status.



--Tom


--
*Thomas F Herbert*
SDN Group
Office of Technology
*Red Hat*
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

2017-03-27 Thread HU, BIN

Adding opnfv-tsc mailing list too.

From: jiaxuan [mailto:jiax...@chinamobile.com]
Sent: Monday, March 27, 2017 6:37 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: 'Amar Kapadia' ; HU, BIN 
Subject: [opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR) Project 
as NGVS is merging into OR

After a good talk with Nextgen VIM Scheduler (NGVS) project, we decide to 
expand the scope of OpenRetriever(OR) and let NGVS merge into OR. NGVS will be 
as a sub-project of OR.

TSC need community to revised the changes of OR's scope for 2 weeks. Then bring 
to TSC for review and approval.

Scope:

OR focuses on how non-virtual-machine based VNF run in NFV. It includes 
container and unikernels. The target of this project is let VNF can run on any 
platform including OpenStack, Kubernetes, Mesos and so on. The project doesn't 
cover the internal architecture of a VNF.

1.  Add Kuryr and Magnum into installers

2.  Container for NFV. The main function is to increase the performance of 
container and container platform.

3.  Set up an environment which can support container and unikernel.

4.  A new scheduler that can schedule a mix of all three types (virtual 
machine, container, unikernel) of instances.

5.  Analyse the gap for OpenStack, Installer, Kubernetes, MANO.

Key work items include:

1. Documentation:

1) The requirement of OpenStack, Installer, Kubernetes, MANO

2) The requirement of Nextgen VIM Scheduler.

3) The user guide: Set up an environment which can support container and 
unikernels.

2. Scripts : Common scripts to let container be integrated into OPNFV

3. Testing:  Provide for Functest , Yardstick etc.

Committers and Contributors:

Project Leader: Xuan Jia ( 
jiax...@chinamobile.com)

Committer:

 Csatari, Gergely ( 
gergely.csat...@nokia.com )

 Lijun ( matthew.li...@huawei.com )

 Xuan Jia ( jiax...@chinamobile.com )

 Peng Yu ( yu.pen...@zte.com.cn )

 Wassim Haddad ( 
wassim.had...@ericsson.com )

 Heikki Mahkonen ( 
heikki.mahko...@ericsson.com )

 Amar Kapadia ( 
akapa...@aarnanetworks.com )

 Sriram Rupanagunta ( 
srupanagu...@gmail.com )

Contributors:

 Guo Ruijing ( ruijing@intel.com )

 Srinivasa Addepalli 
(srinivasa.r.addepa...@intel.com )

 Pradip Rawat (pradipkum...@biarca.com )

 Ganesh Kaila (gane...@biarca.com )

Planned deliverables:

1. Documentation and User Guide

2. Scripts.

Proposed Released Schedule:

1. NGVS is completed by E-release

2. Gap analysis and requirement documentation by E-release

3. Integration scripts for container by E-release

Initial proposal:

NGVS Proposal (https://wiki.opnfv.org/pages/viewpage.action?pageId=10290307 )

OpenRetriver Proposal 
(https://wiki.opnfv.org/display/PROJ/Project+Proposals+OpenRetriever )

If you have any question ,please follow this email. Thanks

Xuan Jia

Mobile: (+86) 13811000575

E-mail: jiax...@chinamobile.com

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

[opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

2017-03-27 Thread jiaxuan

After a good talk with Nextgen VIM Scheduler (NGVS) project, we decide to
expand the scope of OpenRetriever(OR) and let NGVS merge into OR. NGVS will
be as a sub-project of OR.

TSC need community to revised the changes of OR's scope for 2 weeks. Then
bring to TSC for review and approval.

 

Scope:

OR focuses on how non-virtual-machine based VNF run in NFV. It includes
container and unikernels. The target of this project is let VNF can run on
any platform including OpenStack, Kubernetes, Mesos and so on. The project
doesn't cover the internal architecture of a VNF. 

 

1.  Add Kuryr and Magnum into installers

 

2.  Container for NFV. The main function is to increase the performance of
container and container platform. 

 

3.  Set up an environment which can support container and unikernel. 

 

4.  A new scheduler that can schedule a mix of all three types (virtual
machine, container, unikernel) of instances. 

 

5.  Analyse the gap for OpenStack, Installer, Kubernetes, MANO.

 

 

Key work items include:

1. Documentation: 

 

1) The requirement of OpenStack, Installer, Kubernetes, MANO 

 

2) The requirement of Nextgen VIM Scheduler.

 

3) The user guide: Set up an environment which can support container and
unikernels.

 

2. Scripts : Common scripts to let container be integrated into OPNFV

 

3. Testing:  Provide for Functest , Yardstick etc.

 

 

Committers and Contributors:

Project Leader: Xuan Jia ( jiax...@chinamobile.com
 )

Committer: 

 Csatari, Gergely ( gergely.csat...@nokia.com
  ) 

 Lijun ( matthew.li...@huawei.com 
)

 Xuan Jia ( jiax...@chinamobile.com 
)

 Peng Yu ( yu.pen...@zte.com.cn   )

 Wassim Haddad ( wassim.had...@ericsson.com
  )

 Heikki Mahkonen ( heikki.mahko...@ericsson.com
  )

 Amar Kapadia ( akapa...@aarnanetworks.com
  )

 Sriram Rupanagunta ( srupanagu...@gmail.com
  )

Contributors:

 Guo Ruijing ( ruijing@intel.com   )

 Srinivasa Addepalli (srinivasa.r.addepa...@intel.com
  )

 Pradip Rawat (pradipkum...@biarca.com
  )

 Ganesh Kaila (gane...@biarca.com   )

 

 

Planned deliverables: 

1. Documentation and User Guide

 

2. Scripts. 

 

 

Proposed Released Schedule:

1. NGVS is completed by E-release

 

2. Gap analysis and requirement documentation by E-release

 

3. Integration scripts for container by E-release

 

 

Initial proposal:

NGVS Proposal (https://wiki.opnfv.org/pages/viewpage.action?pageId=10290307
)

OpenRetriver Proposal
(https://wiki.opnfv.org/display/PROJ/Project+Proposals+OpenRetriever )

 

If you have any question ,please follow this email. Thanks 

 

Xuan Jia

Mobile: (+86) 13811000575

E-mail: jiax...@chinamobile.com

 

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

[opnfv-tech-discuss] [ovsnfv] Weekly Meeting

2017-03-27 Thread O Mahony, Billy

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="O Mahony, Billy":MAILTO:billy.o.mah...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Daniel Sm
 ith':MAILTO:daniel.sm...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Hesham El
 Bakoury':MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Paul-Andr
 e Raymond':MAILTO:paul-andre.raym...@nexius.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Skip Boot
 h (ebooth)':MAILTO:ebo...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Winn, Sea
 n'":MAILTO:sean.w...@emc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Matt Gill
 ies (mgillies)':MAILTO:mgill...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tim Dalto
 n':MAILTO:t.dal...@networkfx.net
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alan McNa
 mee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sen, Prod
 ip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Agarwal, 
 Anshu'":MAILTO:anshu.agar...@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Phil Chen
 ':MAILTO:phil.c...@citrix.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Nicolas B
 OUTHORS':MAILTO:nicolas.bouth...@qosmos.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='forerunne
 r...@etri.re.kr':MAILTO:forerun...@etri.re.kr
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'DRUTA, DA
 N'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='jamil.cha
 w...@orange.com':MAILTO:jamil.cha...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tal Baren
 boim':MAILTO:t...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Bharat Bh
 ushan':MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Venkatesan
 , Venky":MAILTO:venky.venkate...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'CHIOSI, M
 ARGARET T'":MAILTO:mc3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Radhakris
 hnan Govindan':MAILTO:gradh...@sandvine.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Palacharl
 a, Paparao'":MAILTO:paparao.palacha...@us.fujitsu.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Duarte Car
 doso, Igor":MAILTO:igor.duarte.card...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='guo bingl
 i':MAILTO:gblal...@hotmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Levine, I
 dit'":MAILTO:idit.lev...@emc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Scott Man
 sfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Thomas F.
  Herbert':MAILTO:thomasfherb...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Henry Fou
 rie':MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Mario Tor
 recillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Damena, M
 ichael Melesse'":MAILTO:michael.mel.dam...@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tahhan, Ma
 ryam":MAILTO:maryam.tah...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Huangkun 
 (Gareth, Cloud OS)'":MAILTO:gareth.hu...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ryan Davi
 s':MAILTO:ryan.da...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Sun, Jimin
 g":MAILTO:jiming@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ian Wells
  (iawells)':MAILTO:iawe...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Bishnoi, 
 Sandeep (Nokia - US)'":MAILTO:sandeep.bish...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=kevin@caoi
 mhin.net:MAILTO:ke...@caoimhin.net

[opnfv-tech-discuss] Models & Domino Joint Meeting

2017-03-27 Thread Ulas Kozat

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Ulas Kozat:MAILTO:ulas.ko...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tsc@
 lists.opnfv.org:MAILTO:opnfv-...@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Arthur Ber
 ezin:MAILTO:art...@gigaspaces.com
DESCRIPTION;LANGUAGE=en-US:When: Occurs every Monday effective 4/4/2016 fro
 m 6:00 AM to 7:00 AM (UTC-08:00) Pacific Time (US & Canada).\nWhere: https
 ://global.gotomeeting.com/join/530705469\n\nNote: The GMT offset above doe
 s not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n
 \nWe merge the meeting time for Models and Domino projects on Monday morni
 ng in this time slot.\n\n\n\nUse the following GoToMeeting link to join th
 e meeting:\n\n\n\nhttps://global.gotomeeting.com/join/530705469\n\nUS (Tol
 l-free) 1-866-899-4679\n\nAccess code 530-705-469\n\n\n\nMeeting Agenda:\n
 \nhttps://wiki.opnfv.org/display/domino/Meeting+Agenda\n\n\n\nRegards\,\n\
 n\n\nUlas\n\n\n\n\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO;WKST=SU
EXDATE;TZID=Pacific Standard Time:20160704T06,20161226T06,20170102T
 06
SUMMARY;LANGUAGE=en-US:[opnfv-tech-discuss] Models & Domino Joint Meeting
DTSTART;TZID=Pacific Standard Time:20160404T06
DTEND;TZID=Pacific Standard Time:20160404T07
UID:04008200E00074C5B7101A82E008402C5737058CD101000
 010008F27563EB4CB8E4289B55D8B4E6A64DF
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170327T133057Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:10
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/530705469
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:2049001440
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VEVENT
SUMMARY:[opnfv-tech-discuss] Models & Domino Joint Meeting
DTSTART;TZID=Pacific Standard Time:20160404T06
DTEND;TZID=Pacific Standard Time:20160404T07
UID:04008200E00074C5B7101A82E008402C5737058CD101000
 010008F27563EB4CB8E4289B55D8B4E6A64DF
RECURRENCE-ID;TZID=Pacific Standard Time:20160404T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170327T133057Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:10
LOCATION:https://global.gotomeeting.com/join/530705469
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:2049001440
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[opnfv-tech-discuss] Models & Domino Joint Meeting
DTSTART;TZID=Pacific Standard Time:20160425T06
DTEND;TZID=Pacific Standard Time:20160425T07
UID:04008200E00074C5B7101A82E008402C5737058CD101000
 010008F27563EB4CB8E4289B55D8B4E6A64DF
RECURRENCE-ID;TZID=Pacific Standard Time:20160425T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170327T133057Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:10
LOCATION:https://global.gotomeeting.com/join/530705469
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:2049001440
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[opnfv-tech-discuss] Models & Domino Joint Meeting
DTSTART;TZID=Pacific Standard Time:20160516T06
DTEND;TZID=Pacific Standard Time:20160516T07
UID:04008200E00074C5B7101A82E008402C5737058CD101000
 010008F27563EB4CB8E4289B55D8B4E6A64DF
RECURRENCE-ID;TZID=Pacific Standard Time:20160516T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170327T133057Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:10
LOCATION:https://global.gotomeeting.com/join/530705469
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:2049001440
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:[opnfv-tech-discuss] Models & Domino Joint Meeting
DTSTART;TZID=Pacific Standard Time:20160530T06
DTEND;TZID=Pacific Standard

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

2017-03-27 Thread valentin.boucher

Hi Chaoyi,

Each clearwater vm can have 1 interface (signaling + management) or 2 
interfaces (1 for signaling and 1 for management). See clearwater documentation 
=> 
Link.

Currently, We have only tested clearwater multisite deployement with 1 
interface per VM. For this configuration, the "North South Networking via 
Multiple External Networks" Tricircle network scenario is interesting. But 
changes would have to be made to bring it closer to the needs.

+-+   +-+
|  RegionOne  |   |  RegionTwo  |
| |   | |
| ext_net1|   | ext_net2|
|   +-+-+ |   |   +-+-+ |
| |   |   | |   |
| |   |   | |   |
|  +--+--+|   |  +--+--+|
|  | || net3  |  | ||
|  | R1  |---| R2  ||
|  | ||   |  | ||
|  +--+--+|   |  +--+--+|
| |   |   | |   |
| |   |   | |   |
| +---+-+-+   |   | +---+-+-+   |
| net1  | |   | net2  | |
|   | |   |   | |
|  ++--+  |   |  ++--+  |
|  | Instance1 |  |   |  | Instance2 |  |
|  +---+  |   |  +---+  |
| |   | |
+-+   +-+

I think the way is to put a network between R1 and R2 instead of instance1 and 
instance2. Thereby, Instance1 can communicate to instance2 with his net1 ip 
trough the net3 network. But, also with the external componants (like sip 
client etc.) with a floating ip on ext_net1 or 2.

BR,
Valentin Boucher

De : joehuang [joehu...@huawei.com]
Envoyé : jeudi 23 mars 2017 14:53
À : BOUCHER Valentin IMT/OLN; Soni, Anand Kumar via opnfv-tech-discuss; 
Morales, Victor; Meimei
Objet : RE: 答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Valentin,

The networking topology is very clear from the picture.

If we want to make vIMS clearwater as close as to the production deployment in 
OpenStack multisite environment, what's the better networking proposal, for 
example, how many interfaces for one VM, i.e, how many network planes, how to 
process the north-south traffic, is SNAT/FIP needed?

Would like to check whether Tricircle networking automation can fulfill the 
demands for vIMS clearwater multi-site deployment.

Tricircle already supports several typical networking topology in 
https://docs.openstack.org/developer/tricircle/networking-guide.html#networking-scenario
 ( please note that VxLAN based bridge network between routers, VxLAN based 
cross OpenStack L2 network will be released in pike-1 by the end of next week )

And one more typical topology is expected to be released in pike-2: L3 
networking to support multiple north-south with east-west enabled: 
https://review.openstack.org/#/c/448359/

Best Regards
Chaoyi Huang (joehuang)

From: valentin.bouc...@orange.com [valentin.bouc...@orange.com]
Sent: 23 March 2017 0:03
To: joehuang; Soni, Anand Kumar via opnfv-tech-discuss; Morales, Victor; Meimei
Subject: RE:答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hello, Chaoyi,

Oh ok, no problem.

 ~12 VMs with 2 Go and 1 VM with 4 Go per site

VNF networking:

  *   Only one network interface on each VM
  *   Communication between each local site network must be allowed without any 
NAT/PAT or floating ip.
  *   So, Each local VM must be able to communicate with the remote VM with his 
local ip.
  *   For the moment we use a openvpn tunnel to do that and the openvpn vms 
acts as router between local and remote networks (see the picture in 
attachment).

The goal is to replace openvpn tunnel with a better solution like bgp-mpls or 
other thing.

BR,
Valentin


De : joehuang [joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 14:17
À : BOUCHER Valentin IMT/OLN; Soni, Anand Kumar via opnfv-tech-discuss; 
Morales, Victor; Meimei
Objet : 答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across 
VIM

Hello, Valentin,

Very pleased to know the practice,
and very keen to discuss about it in more detail f2f.
But unfortuntealy I am not able to attend the
plugfest in Paris, could you please provide
reference material especial VNF's networking
topology, and then find a way for more detail disucssion.

BR
Chaoyi Huang(joehuang)

Sent from HUAWEI AnyOffice
发件人：valentin.bouc...@orange.com
收件人：黄朝意,Soni, Anand Kumar via opnfv-tech-discuss,Morales, Victor,梅玫
时间：2017-03-16 19:04:22
主题:RE:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

Last summer, In Orange Labs, we implemented vIMS ClearWater on a multi-site

Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV Summit CFP

2017-03-27 Thread Kunzmann, Gerald

Dear Brandon, OPNFV Events-Team,

If I want to reserve a room at the OPNFV summit for a project team meeting / 
breakout session, do I also need to request this through the CfP page as 
"breakout session"?

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of yunhong jiang
Sent: Dienstag, 21. März 2017 21:12
To: Brandon Wick 
Cc: opnfv-tech-dis. 
Subject: Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV 
Summit CFP

On Tue, 21 Mar 2017 12:55:25 -0700
Brandon Wick  wrote:

> Hello Jiang,
> 
> Thanks for your question. Please send any future questions to
> eve...@opnfv.org.
> 
> The Design Summit takes place June 12-13 and is where the OPNFV
> technical community will convene to continue working on the E-Release
> and have plenary sessions and project breakouts. It is very focused
> on the OPNFV platform. The Summit Conference takes place Jun 14-15
> and is for the wider NFV ecosystem, featuring keynotes, breakout
> sessions, a technology showcase, networking opportunities, etc. This
> is where the the breakouts will be structured into the six tracks.
> Panels consist of 4 or more speakers in a single session. When in
> doubt, we recommend you submit for the Summit conference as a
> breakout session. From there, our track chairs will be able to make
> further recommendations as needed.

Hi, Brandon,
Thanks for the reply and it's clear now.

--jyh

> 
> Best,
> 
> 
> Brandon Wick
> OPNFV Head of Marketing, The Linux Foundation
> Mobile: +1.917.282.0960  Skype: wick.brandon
> Email / Google Talk: bw...@linuxfoundation.org
> 
> *The OPNFV Summit CFP Closes 3/27!
> *
> 
> On Tue, Mar 21, 2017 at 12:31 PM, yunhong jiang <
> yunhong.ji...@linux.intel.com> wrote:
> 
> > Hi, Brandon,
> > When I try to submit the CFP, I noticed there are two types of
> > the session. One is for Design Summit session and one is for OPNFV
> > Summit session. Are there any key differences of these two? I
> > attended the Openstack summit before and they are quite
> > different there.
> >
> > Also on the Design Summit session, there are two formats called
> > break out session and panel discussion. What's the difference of
> > them? How should I decide which format should my session be?
> >
> > Hope your guide on this, thanks!
> >
> > -jyh
> >
> > On Mon, 20 Mar 2017 07:24:43 -0700
> > Brandon Wick  wrote:
> >
> > > OPNFV Technical Community:
> > >
> > > This is a reminder that the CFP for the OPNFV Summit
> > > , June
> > > 12-15, Beijing, China, closes *Monday, March 27*. We encourage
> > > you to prepare and submit a proposal by the deadline. The six
> > > primary tracks are the following:
> > >
> > >- NFV Applications and Orchestration
> > >- Testing, Infrastructure, and DevOps
> > >- NFV Strategy and End User Stories
> > >- NFV Platform Requirements
> > >- Community and Upstream
> > >- Futures and Research
> > >
> > > *Access the CFP Here
> > >  > details>*
> > >
> > > We look forward to your submissions. If you have any questions,
> > > please email eve...@opnfv.org.
> > >
> > > Best,
> > >
> > > Brandon Wick
> > > OPNFV Head of Marketing, The Linux Foundation
> > > Mobile: +1.917.282.0960  Skype: wick.brandon
> > > Email / Google Talk: bw...@linuxfoundation.org
> >
> >

___
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] OPNFV Promise meeting

2017-03-27 Thread Kunzmann, Gerald

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The Promise team holds a meeting on (biweekly). 
 We use GoToMeeting for audio and IRC for meeting minutes. For further deta
 ils please see: https://wiki.opnfv.org/display/meetings/Promise+Team+Meeti
 ngs\n\nIRC channel: #opnfv-promise\nGoToMeeting: https://global.go
 tomeeting.com/join/144838637\n\n
RRULE:FREQ=WEEKLY;UNTIL=20171026T11Z;INTERVAL=2;BYDAY=TH;WKST=MO
SUMMARY;LANGUAGE=en-US:OPNFV Promise meeting
DTSTART;TZID=UTC:20170330T11
DTEND;TZID=UTC:20170330T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170327T090853Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/144838637
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][euphrates] Intent-to-Participate - Promise

2017-03-27 Thread Kunzmann, Gerald

Dear David, all,

Promise project intends to participate in the upcoming release. Our work will 
mainly focus on upstream development in OpenStack Blazar project. We will also 
do maintenance work on the existing code –where needed- to ensure test cases 
are passing.

Best regards,
Gerald

From: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Montag, 27. März 2017 03:57
To: TECH-DISCUSS OPNFV ; 
opnfv-project-leads ; TSC OPNFV 

Cc: Raymond Paik ; Tapio Tallgren 

Subject: [opnfv-project-leads] [release][euphrates] Intent-to-Participate 
window for Euphrates

Team,

I'm excited to announce that the intent-to-participate window will open on 
Monday, March 27, and will remain open until 5 p.m. on April 24 (MS1).

The process is documented 
here, 
but essentially just requires sending an email to the TSC mailing list.  Note 
that your project must have been approved by the TSC before you may join a 
release.

Once you have stated your intent to participate, you must complete your release 
planning by MS1 on April 24.  This includes completing the release plan 
summary.

Please let me know if you have any questions.

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

Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV Summit CFP

Re: [opnfv-tech-discuss] Request to contribute to yardstick

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][euphrates] Intent-to-Participate window for Euphrates

[opnfv-tech-discuss] Join us for a Reception at Levi's Stadium on April 3rd

[opnfv-tech-discuss] OPNFV Meetings

Re: [opnfv-tech-discuss] [release][euphrates] Intent-to-Participate Moon

Re: [opnfv-tech-discuss] Euphrates release project proposal: CORD

[opnfv-tech-discuss] Euphrates release project proposal: CORD

Re: [opnfv-tech-discuss] Euphrates release project proposal: Armada

Re: [opnfv-tech-discuss] [opnfv][ovs-opnfv] Scenario status and meeting today.

[opnfv-tech-discuss] Euphrates release project proposal: Armada

Re: [opnfv-tech-discuss] [opnfv][ovs-opnfv] Scenario status and meeting today.

Re: [opnfv-tech-discuss] [opnfv-tsc] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

[opnfv-tech-discuss] [opnfv][ovs-opnfv] Scenario status and meeting today.

Re: [opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

[opnfv-tech-discuss] Expanding the scope of OpenRetriever(OR) Project as NGVS is merging into OR

[opnfv-tech-discuss] [ovsnfv] Weekly Meeting

[opnfv-tech-discuss] Models & Domino Joint Meeting

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV Summit CFP

[opnfv-tech-discuss] OPNFV Promise meeting

[opnfv-tech-discuss] [release][euphrates] Intent-to-Participate - Promise

25 matches

Site Navigation

Mail list logo

Footer information