Re: [onap-discuss] [arc] CCVPN use case Time Application

[Christopher Donley (Chris)]

I have you on the agenda.  CCVPN is second – you will be in the first hour.  
That's between 10-11 pm China time.  
https://zoom.us/j/813762782

Chris

From: LinMeng mailto:menglin...@chinamobile.com>>
Date: Sunday, June 10, 2018 at 8:02 PM
To: Chris Donley 
mailto:christopher.don...@huawei.com>>
Cc: "onap-usecase...@lists.onap.org" 
mailto:onap-usecase...@lists.onap.org>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, 邓灵莉 
mailto:denglin...@chinamobile.com>>
Subject: [arc] CCVPN use case Time Application

Hi Chris,
We want to applicate a time slot for about 30mins to talk about the 
architecture of CCVPN on ONAP-ARC meeting.
Please tell us what time is OK for us.
Thanks!

---
孟琳
人工智能和智慧运营研发中心
中国移动通信有限公司研究院
中国北京市西城区宣武门西大街32号（100053）

Meng Lin
Center of AI and Intelligent Operation R
China Mobile Research Institute
No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China

Mobile: +86 13810012241
Email: menglin...@chinamobile.com
-



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

Re: [onap-discuss] [onap-tsc] [Onap-usecasesub] [**EXTERNAL**] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

[Christopher Donley (Chris)]

Agreed.  This appears to be a significant change to the existing architecture, 
and should be discussed with the wider community.  Let me know when you're 
ready, and I'll allocate a slot on the agenda.

Chris

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>
Date: Wednesday, May 30, 2018 at 10:14 AM
To: "VAN BRAKLE, TRACY L" mailto:tv8...@att.com>>, Parviz 
Yegani mailto:parviz.yeg...@huawei.com>>, 
"Ranganathan, Raghu" mailto:rra...@ciena.com>>
Cc: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, "TIMONEY, 
DAN" mailto:dt5...@att.com>>, "SMITH JR., PAUL" 
mailto:ps7...@att.com>>, 
"onap-usecase...@lists.onap.org" 
mailto:onap-usecase...@lists.onap.org>>, 
onap-tsc mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-tsc] [Onap-usecasesub] [**EXTERNAL**] The summary of Usecase 
subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements 
endorsement

Hi,

The current practice we have is that these are taken in the Tuesday 
Architecture meetings as is done with other use cases with architecture 
considerations.

Chris?

BR,

Steve


From: onap-tsc-boun...@lists.onap.org 
mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of VAN BRAKLE, TRACY L
Sent: Wednesday, May 30, 2018 12:15 PM
To: Parviz Yegani mailto:parviz.yeg...@huawei.com>>; 
Ranganathan, Raghu mailto:rra...@ciena.com>>
Cc: TIMONEY, DAN mailto:dt5...@att.com>>; SMITH JR., PAUL 
mailto:ps7...@att.com>>; onap-tsc 
mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: Re: [onap-tsc] [Onap-usecasesub] [**EXTERNAL**] The summary of Usecase 
subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements 
endorsement

Parviz,
Raghu,

Please join the weekly SDN-R call (see below) to discuss this topic.

We can allow 15 or 20 minutes on the agenda for the call today, May 30th, or 
for the call next week, June 6th  - just let me know your preference.

Thank you in advance,

Tracy

Tracy Van Brakle mailto:vanbra...@att.com>>
AT Labs - Wireless Network Architecture and Design
+1 732.420.3003  office
+1 732.306.2387  cell


[sdnr] team meeting (updated Apr. 3, 2018)
When

Weekly from 9am to 10am on Wednesday from Wed Apr 4 to Wed Mar 13, 2019 Pacific 
Time

Where

https://zoom.us/j/502876187
 
(map)

Calendar

tv8...@att.com






From:onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of Parviz Yegani
Sent: Wednesday, May 30, 2018 2:03 AM
To: Ranganathan, Raghu mailto:rra...@ciena.com>>
Cc: TIMONEY, DAN mailto:dt5...@att.com>>; onap-tsc 
mailto:onap-...@lists.onap.org>>; Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
onap-discuss@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: Re: [Onap-usecasesub] [**EXTERNAL**] [onap-tsc] The summary of Usecase 
subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements 
endorsement

Hi Raghu,

I think we need to have a call to discuss SDN-R and it’s relation to SDN-C. 
I’ll be happy to send an invite for this.

How about Thursday, 1:00PM Pacific?

Regards,
Parviz

---
PARVIZ YEGANI, PhD
Chief SDN/NFV Architect
CTO Office, Cloud Network Solutions

FutureWei Technologies, Inc.
2330 Central Express Way
Santa Clara, CA 95050, USA
Phone: +1 (408) 330-4668
Mobile : +1 (408) 759-1973
parviz.yeg...@huawei.com



From: Ranganathan, Raghu [mailto:rra...@ciena.com]
Sent: Tuesday, May 22, 2018 5:39 PM
To: Parviz Yegani mailto:parviz.yeg...@huawei.com>>
Cc: TIMONEY, DAN mailto:dt5...@att.com>>; Alla Goldner 
mailto:alla.gold...@amdocs.com>>; Vladimir Yanover 
(vyanover) mailto:vyano...@cisco.com>>; Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
SHANKARANARAYANAN, N K 
mailto:shan...@research.att.com>>; 
onap-usecase...@lists.onap.org; 
onap-discuss@lists.onap.org; onap-tsc 
mailto:onap-...@lists.onap.org>>
Subject: Re: [**EXTERNAL**] [Onap-usecasesub] [onap-tsc] The summary of Usecase 

[onap-discuss] [vnfsdk] tomorrow's meeting (5/18) cancelled

[Christopher Donley (Chris)]

Team,

Tomorrow's VNFSDK meeting is cancelled.  We can handle this week's update via 
email.

  1.  The TSC voted to postpone RC2 and the release by 2 weeks, so RC2 has now 
been moved to 5/31 and the Beijing release to 6/7.
  2.  We are ready for RC2.  In the extra two weeks, please look over 
documentation and complete any bug fixes.
  3.  On next week's call, I'd like to review Casablanca planning.
  4.  For people who are ready to start work on Casablanca, let me know.  Since 
we are almost finished with Beijing, we can cut a Beijing branch and keep 
working on master for Casablanca.  I just created the dovetail-integration 
branch today so Moshe can keep working on Casablanca features, and we can do 
the same for other repos, as well.  If you want to pursue this, send me an 
email so that I can work with LF IT.

Thanks,
Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] [ARCH] Request scope change review: POMBA introduction in Logging project for Casablanca

[Christopher Donley (Chris)]

Michael,

Yes, we can move you to an early slot on the 29th.

Chris

From: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>
Date: Monday, May 14, 2018 at 6:55 AM
To: Chris Donley 
<christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: RE: [onap-tsc] [ARCH] Request scope change review: POMBA introduction 
in Logging project for Casablanca

Chris,
Can we delay the scope change meeting for logging until next week – the 
22nd.
I understand the Architecture team is at a conference next week – so likely 
we will do this scope change on the 29th in 2 weeks.
Can I request the first hour – as we have our logging meeting in the 2nd 
hour of the Arch meeting
Thank you
/michael

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Friday, May 11, 2018 9:41 AM
To: Christopher Donley (Chris) 
<christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-tsc] [ARCH] Request scope change review: POMBA introduction in 
Logging project for Casablanca

Chris,
   Hi, the logging project would like to introduce a proposed scope change for 
Casablanca – we would like to pass these adjustments by the architecture 
subcommittee and the community before meeting the use case subcommittee.

https://wiki.onap.org/display/DW/POMBA
The expanded clickable team member list is on the sub page
https://wiki.onap.org/display/DW/Logging+Scope+Change+for+POMBA+seed+code#LoggingScopeChangeforPOMBAseedcode-Teammembers

  I would expect 15 min.

  1.  Jon Fannar Karlsson Taylor and Sharon Chisholm will be presenting
  2.  Heads up review of the architecture proposal, the new microservices, new 
API capabilities provided by the audit, any overlap with other projects, 
requirements on other projects and use case discussion



   This meeting is separate from the ongoing review of the Logging 
specification and implementation under the following that we discussed at last 
week’s Architecture meeting
https://jira.onap.org/browse/ONAPARC-148

   Let us know if there are any additional requirements.
   Thank you
/michael


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ARCH] Request scope change review: Logging specification changes for Casablanca

[Christopher Donley (Chris)]

Michael,

I put you down for a 10-minute slot.

Chris

From: Michael O'Brien >
Date: Monday, May 7, 2018 at 7:12 AM
To: "'onap-discuss@lists.onap.org'" 
>
Cc: Chris Donley 
>
Subject: [ARCH] Request scope change review: Logging specification changes for 
Casablanca

Chris,
   Hi, the logging team has been meeting for about 5 weeks finalizing the 
logging specification proposed for Casablanca – we would like to pass these 
adjustments by the architecture subcommittee and the community.
https://wiki.onap.org/pages/viewpage.action?pageId=28378955


   We would like a couple meetings if possible – I would expect 5-10 min.

  1.  Heads up review of the spec and the diff  from Beijing - the MDC and 
Marker changes and proposed EPICs for Casablanca – would like to get this up 
for discussion earlier.
  2.  Demo: When we have some concrete running demo code finished and have 
prioritized/sized and agreed on the Casablanca epics – we could do another 
review the week after if possible. Discuss impact to teams, working with teams 
to implement, staged migration…


Team, Luke Parker, Shishir Thakore, Sanjay Agraharam, Neal Chatterley, Dave 
Williamson, Lee Bresleau, Xuan Liu, Horace Ip, Bob Ferro, David Bainbridge, 
Jimmy Forsyth.

   Thank you
/michael


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [VNFSDK] New bridge

[Christopher Donley (Chris)]

Hi there,

Chris Donley is inviting you to a scheduled Zoom meeting.

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

Or iPhone one-tap :
US: +16465588656,,656499378# or +16699006833,,656499378#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833
Meeting ID: 656 499 378
International numbers available: https://zoom.us/u/cwODr78Jc

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

Re: [onap-discuss] [onap-tsc] Action Plan towards Casablanca

[Christopher Donley (Chris)]

Mazin,

As we discussed, please make sure that we follow the charter in proposing the 
end-user advisory committee (I.e, formal documentation of the purpose, scope, 
membership, etc) so that the TSC can review and vote on it. I think it’s a good 
idea, but I want to see the details and make sure we follow our documented 
procedure.

Thanks,
Chris


From: GILBERT, MAZIN E (MAZIN E)
To: Alla Goldner;
Cc: onap-discuss@lists.onap.org; onap-usecase...@lists.onap.org; 
onap-...@lists.onap.org P;
Subject: Re: [onap-tsc] [onap-discuss] Action Plan towards Casablanca
Time: 2018-03-30 17:57:00


Thanks Alla for the summary.

Here is what we agreed to at the TSC meeting.
There are three work plans for Casablanca. The theme is increase deployability 
of ONAP.

1. Functional requirements and use cases. We agreed to establish an end-user 
advisory committee that will be driven by the equivalent of product managers 
across operators who will help to set priorties that can accelerate 
deployability of ONAP. The work of your committee on use cases and 5G 
solutioning will help to provide options for the end-user advisory committee.

2. Platform Evolution. This includes some of your list items
a. S3P new target (including code coverage)
b. Backward compatibility
c. Improve modularity and simplicity of using ONAP.

3. Broader learning and education of ONAP.
The Education committee will develop a proposal for weekly Webinars.

I am working to assemble 1. My hope is to have 3-4 operators signed up next 
week so they can meet with your team and get the work started.
Phil will make that committee official as a subgroup under LFN end-user 
advisory committee. Until then, let’s not slow down.

We also discussed what we want to accomplish prior to the Beijing meeting in 
June. We will discuss that further at the TSC meeting this week,
and also vote on the release planning for Casablanca.

Great progress by the team on Beijing. Most projects hit M4 already. Momentum 
is amazing.

Mazin

On Mar 30, 2018, at 5:03 AM, Alla Goldner 
> wrote:

Hi all,

I re-attach the picture which describes high level priorities as discussed 
during the meeting called by me on Wednesday evening. I understand this was 
discussed in details also during the TSC meeting.

What we had on the table was:

1.   Leftovers from Beijing remained from :
a.   Functional requirements (PNF, Scaling, Change Management, HPA)
b.  Leftovers from S3P support
2.   New S3P requirements
3.   All new use cases and requirements coming to Casablanca (you could see 
the variety during our meeting on Monday)
4.   A different projects proposed extensions
5.   Possibly, new projects potentially proposed for Casablanca
6.   Architecture evolution related modifications

Clearly, this whole scope will not be accomplished in a single Release, this is 
why we needed to see what would be areas of priorities.
Clearly, we may get additional input from the Service Providers, as discussed, 
but in the mean time, in order to make progress, let’s assume these are the 
priorities.

Now, in order to do constructive work and move forward towards Casablanca 
Release, specifically for Usecase subcommittee, we need to see what ongoing 
work matches the Deployability goal as defined and, additionally, extract 
generic functional requirements from the use cases brought to the table/see if 
some requirements brought to the table can be generalized.

I identify the following areas for our activities out of proposed prioritized 
areas:

1.   Leftovers of functional requirements from Beijing – as scope is pretty 
clear, I would say that at this point the required actions are:
a.   Have a detailed list of functionality proposed to move to Casablanca
b.  Negotiate with involved projects on this functionality and resources 
assigned to these activities

2.   All 5G related requirements:
a.   A realistic plan of what can be implemented in Casablanca (a subset of 
functionality discussed so far), based on available/emulated VNFs/PNFs, 3GPP 
standards’ availability etc. with flows, needed resources, affected modules

3.   All external controllers related activities – this work should be 
generalized and common principle should be developed on what we bring to 
Casablanca in such a way that it can be utilized by several use cases. Some 
initial work on this was also done in Beijing.
a.   A concrete proposal on what we bring to Casablanca should be worked on 
and brought

I suggested end of April as a deadline for the conditional approval of the 
scope as discussed above. (Conditional is because some more detailed 
discussions with the projects after this may rule out/or add some of the 
requirements/functionalities.

For that, we need to get your revised high level proposals per (2) and (3) by 
our April 9th meeting. Please talk to me in case of any questions.

Best regards,

Alla Goldner

Open 

[onap-discuss] [VNFSDK] Update

[Christopher Donley (Chris)]

Team,

Tomorrow’s meeting is cancelled due to travel/holidays/face-to-face modeling 
meeting.  I’ll provide status via email in lieu of a meeting.

  1.  We passed our M4 review.  Great job team!  Special thanks to all of you 
putting in long hours and submitting updates this week. It is much appreciated.
  2.  Special thanks to Kailun who started work on function tests last week and 
submitted a large update in time for the code freeze (and passed the code 
coverage requirement).  Great work!
  3.  The LFN Board approved creation of the LFN Compliance Verification 
Committee (CVP) to offer cross-project compliance/verification tests.  This 
opens the door to use vnfsdk for verification testing after the Casablanca 
release.
  4.  The TSC discussed the focus for the Casablanca release today: 
Deployability.  One of the top priorities for the release is VNF 
packaging/onboarding, so we will have increased importance in the next release. 
 We’ll be responsible for aligning with the VNF requirements, integrating the 
ice tools with the marketplace, increased integration with SDC, and perhaps 
increased integration with OPNFV functional tests.  By the end of Casablanca, 
we should be able to use VNFSDK in the OVP program (or whatever it’s called) to 
offer Verified logos to compliant VNFs.
  5.  I spoke with AT about increased integration with SDC in the next 
release.  We may want to consider making our marketplace/refrepo more modular 
so SDC can use it as a test framework for their vendor engagement testing (and 
not using our marketplace portal). Let’s think about this some more as we get 
ready for Casablanca.
  6.  Several people approached me about hosting VNFSDK, or offering a 
third-party marketplace.  We may get some more people joining our calls in the 
next few weeks.
  7.  Next week, we need to work with SDC on pairwise testing.

Great job team!

Thanks,
Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] FW: M4 Code Freeze for Beijing Release

[Christopher Donley (Chris)]

FYI

From: 
>
 on behalf of Gildas Lanilis 
>
Date: Thursday, March 22, 2018 at 3:52 PM
To: onap-release 
>
Cc: Phil Robb >, 
"onap-...@lists.onap.org" 
>, Steve Winslow 
>
Subject: [Onap-release] M4 Code Freeze for Beijing Release

Hi PTLs,

M4 Code Freeze review for Beijing Release is coming and will be hold on March 
29 at 7 am PDT during the weekly TSC Meeting.
Please make it possible to join the bridge or send out a delegate. TSC may have 
questions on which we expect timely responses.


1.   As usual, please make a copy and fill out the M4 
template.
 I would appreciate if you could fill it out by COB on Tuesday, March 27. Early 
is even better so we have time to clarify items (if necessary).

2.   At M1, the teams have made commitments in regards to Platform Maturity 
and Functional requirements. The commitments were all recorded in a central 
wiki page. As M4 Code freeze is coming, the community needs to understand where 
the teams stand in regards to these commitments and such the request is you 
update accordingly the column labelled “R4 result” for Platform 
Maturity 
(Level achieved 1-4) and Functional 
Requirements 
(Yes/No answer). Please answer by the intent the team had to develop these 
commitments, not by the outcome of integration testing which we have not 
performed yet.   I know we are not living in a perfect world, some defects will 
come out of the testing and collectively we will address them. The critical 
point is to create awareness in case some of these commitments would not be in 
the scope of Beijing Release.

3.   The community will be also looking at:

a.   Code Coverage for each Java and Python repo in the scope of Beijing 
Release. 50% line code coverage is the target in 
Sonar. In case you are facing 
difficulty in seeing your code coverage in Sonar, please create a LF ticket and 
CC me.

b.  CSIT testing: check that all the CSIT pass in 
Jenkins.

c.   CLM Nexus-IQ report: All critical (level 8-9) license issues addressed 
and all critical (level 7-10) security issue either fixed or properly 
documented in wiki by using 
template. These 
templates will be used as a reference point from your components Release Notes.

d.  The pending commits older than 36 
hours. By pending we mean a 
commit on which no activity happened during the last 36 business hours. Back 
and forth reviews is seen as activity and does not count as pending. Skin in 
the game matter ☺.

e.  Keep the Risk you have identified in centralized table 
up-to-date. The world in 
changing fast. In case a risk will not become an issue, update its status to 
“Not occurred”. In case a risk materialized and became an issue, update its 
status to “In-process”.

I will be attending ONS next week and will be glad to seat with you to address 
any questions you may have. For those who cannot make it to ONS, if needed let 
me know and I will open a Zoom meeting on first come first served.
Let me know if you have any questions.

Wish us all the best in making this reality.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

___
Onap-release mailing list
onap-rele...@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-release
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 转发: I made some update on a few page in TSC v2.0

[Christopher Donley (Chris)]

Thank you for the feedback.  I will compile everyone’s comments and take them 
back to the project teams, the Tiger Team, and the ARC following the completion 
of the vote.

Chris

From: meng.zhaoxi...@zte.com.cn [mailto:meng.zhaoxi...@zte.com.cn]
Sent: Sunday, February 11, 2018 4:40 PM
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; 
yangya...@chinamobile.com; Seshu m <seshu.kuma...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] 转发: I made some update on a few page in TSC v2.0


Hi Chris, Seshu,

There are two some issues in the Architecture slides



* P8: The contents of left-top part and right-bottom part are inconsistent, 
there is one more in the left-top

There are 4 provided interferes at the left-top while 3 at the right-bottom.

*P9: "network" should be removed

Then consumed model of SO is "service descriptor" rather than "network service 
descriptor"



BR,

Zhaoxing


原始邮件
发件人：YanYang <yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>>
收件人：'Christopher Donley (Chris)' 
<christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>'Seshu m' 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>
抄送人：onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
日 期 ：2018年02月11日 18:31
主 题 ：[onap-discuss] 转发: I made some update on a few page in TSC v2.0
___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss
Hi Chris,

I found the updates last week from SO PTL Seshu on slide page 8 and 9 in the 
attachment haven’t been merged into the 
https://wiki.onap.org/pages/viewpage.action?pageId=25431301
Would you consider updating the slides for TSC voting?

Best Regards,
Yan
发件人: Seshu m [mailto:seshu.kuma...@huawei.com]
发送时间: 2018年2月6日 19:19
收件人: Yan Yang; Christopher Donley (Chris); 'Lingli Deng'; Zengjianguo (OSS 
Design)
抄送: yangxu (H); Lishitao; 
zhang.maope...@zte.com.cn<mailto:zhang.maope...@zte.com.cn>; 'shentao'; 
liuyueli...@chinamobile.com<mailto:liuyueli...@chinamobile.com>; denghui (L); 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
yuan@zte.com.cn<mailto:yuan@zte.com.cn>; Chaker Al Hakim
主题: RE: I made some update on a few page in TSC v2.0

Hi
Please find the clarifications and updates for the SO on Page 8 and Page 9.



Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.
[Company_logo]

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!



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

Re: [onap-discuss] I made some update on a few page in TSC v2.0

[Christopher Donley (Chris)]

Yan,

Thank you for your comments.  I’d like to hold off until the vote is complete, 
and then address all comments at once so that we can review with all the 
stakeholders �C PTLs/project teams, Tiger Team, and ARC. If needed, we will put 
together a dot-release as soon as possible.

Chris

From: Yan Yang [mailto:yangya...@chinamobile.com]
Sent: Sunday, February 11, 2018 2:29 AM
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; Seshu m 
<seshu.kuma...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: 转发: I made some update on a few page in TSC v2.0

Hi Chris,

I found the updates last week from SO PTL Seshu on slide page 8 and 9 in the 
attachment haven’t been merged into the 
https://wiki.onap.org/pages/viewpage.action?pageId=25431301
Would you consider updating the slides for TSC voting?

Best Regards,
Yan
发件人: Seshu m [mailto:seshu.kuma...@huawei.com]
发送时间: 2018年2月6日 19:19
收件人: Yan Yang; Christopher Donley (Chris); 'Lingli Deng'; Zengjianguo (OSS 
Design)
抄送: yangxu (H); Lishitao; 
zhang.maope...@zte.com.cn<mailto:zhang.maope...@zte.com.cn>; 'shentao'; 
liuyueli...@chinamobile.com<mailto:liuyueli...@chinamobile.com>; denghui (L); 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
yuan@zte.com.cn<mailto:yuan@zte.com.cn>; Chaker Al Hakim
主题: RE: I made some update on a few page in TSC v2.0

Hi
Please find the clarifications and updates for the SO on Page 8 and Page 9.



Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.
[Company_logo]

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!

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

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

[Christopher Donley (Chris)]

+1

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Gadiyar, Rajesh
Sent: Wednesday, January 17, 2018 10:11 PM
To: aayush.bhatna...@ril.com; lxin...@vmware.com; rx1...@att.com; 
onap-...@lists.onap.org; kp...@linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-tsc] Committer Promotion Request for [appc]

+1

--
Regards,
Rajesh

From: > 
on behalf of "aayush.bhatna...@ril.com" 
>
Date: Wednesday, January 17, 2018 at 10:09 PM
To: "lxin...@vmware.com" 
>, 
"rx1...@att.com" 
>, 
"onap-...@lists.onap.org" 
>, 
"kp...@linuxfoundation.org" 
>
Cc: "onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-tsc] Committer Promotion Request for [appc]

+1

Regards

Aayush


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Xinhui Li
Sent: 18 January 2018 04:48
To: MAHER, RANDA; onap-...@lists.onap.org; 
Kenny Paul
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

+ 1

Xinhui

From: > 
on behalf of "MAHER, RANDA" >
Date: Wednesday, January 17, 2018 at 11:54 AM
To: "onap-...@lists.onap.org" 
>, Kenny Paul 
>
Cc: "onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-tsc] Committer Promotion Request for [appc]

Hello TSC, Kenny:

Any chance we can get this committer promotion approved over email?
I have put this on the agenda for this week’s TSC meeting, but with M1 review, 
not sure we will get to it.

I have recorded five +1 thus far


  1.  Dhananjay Pavgi
  2.  Mazin Gilbert
  3.  Jamil Chawki
  4.  Alla Goldner
  5.  Stephen Terrill

Thanks, Randa

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Friday, January 12, 2018 4:28 AM
To: MAHER, RANDA >; 
onap-...@lists.onap.org
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] Committer Promotion Request for [appc]

+1

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of MAHER, RANDA
Sent: 12 January 2018 00:58
To: onap-...@lists.onap.org
Cc: onap-discuss@lists.onap.org
Subject: [onap-tsc] Committer Promotion Request for [appc]

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vnfsdk] repo plan

[Christopher Donley (Chris)]

Good point.  So far, SDC hasn't committed to delivering the code in the Beijing 
release, so let's hold off on that for now.

Also FYI, I updated Jira stories associated with each of our epics and made a 
first pass at prioritization.  Please take a look and feel free to update.

Chris

From: Lu, Lianhao [mailto:lianhao...@intel.com]
Sent: Monday, January 15, 2018 6:36 PM
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; 
onap-discuss@lists.onap.org
Subject: RE: [vnfsdk] repo plan

Do we need new repos for those tools coming from SDC? i.e. license tools and 
heat-tosca translater?

Best Refgards,
-Lianhao

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Christopher Donley 
(Chris)
Sent: Tuesday, January 16, 2018 2:14 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [vnfsdk] repo plan

Team,

As we discussed on Friday, we'll need some new repos for vnfsdk.  Since we need 
to ask for TSC approval for new repos, I want to make sure we have everything 
we expect to need for Beijing before I ask.  I'm planning to request the 
following:

*Dovetail-integration for integration with the OPNFV Dovetail tool

*Ice for ICE tools
I also propose that we rename "compliance" to "ves-agent", since that's what 
we're using it for.

Comments/feedback? Anything missing?  Please let me know by Weds so that I can 
ask the TSC to approve our new repos.

Thanks,
Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] repo plan

[Christopher Donley (Chris)]

Team,

As we discussed on Friday, we'll need some new repos for vnfsdk.  Since we need 
to ask for TSC approval for new repos, I want to make sure we have everything 
we expect to need for Beijing before I ask.  I'm planning to request the 
following:

*Dovetail-integration for integration with the OPNFV Dovetail tool

*Ice for ICE tools
I also propose that we rename "compliance" to "ves-agent", since that's what 
we're using it for.

Comments/feedback? Anything missing?  Please let me know by Weds so that I can 
ask the TSC to approve our new repos.

Thanks,
Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] [sdc] [vvp] Finalize SDC/VNFSDK/VVP alignment for R2

[Christopher Donley (Chris)]

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=Christopher Donley (Chris):MAILTO:christopher.don...@huawei.co
 m
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SHADMI, DA
 VID":MAILTO:ds2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SUNDELOF, 
 ERIK":MAILTO:es4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="LANDO, MIC
 HAEL":MAILTO:ml6...@intl.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Hi there\,\n\nChris Donley is inviting you to a 
 scheduled Zoom meeting.\n\nJoin from PC\, Mac\, Linux\, iOS or Android: ht
 tps://zoom.us/j/592865439\n\nOr iPhone one-tap :\nUS: +16699006833\,\,
 592865439#  or +16465588656\,\,592865439#\nOr Telephone:\nDial(for hig
 her quality\, dial a number based on your current location):\nUS: 
 +1 669 900 6833  or +1 646 558 8656\nMeeting ID: 592 865 439\nInte
 rnational numbers available: https://zoom.us/zoomconference?m=lbmxWULpHre6
 vn4zIB3ZLY6LoEgVnnjE\n\n\n\n
SUMMARY;LANGUAGE=en-US:[vnfsdk] [sdc] [vvp] Finalize SDC/VNFSDK/VVP alignme
 nt for R2
DTSTART;TZID=Pacific Standard Time:20180110T10
DTEND;TZID=Pacific Standard Time:20180110T11
UID:04008200E00074C5B7101A82E008F0A8D2408288D301000
 0100031BF3136530B094AB73C4B6BBF345CDE
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180108T211234Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/592865439
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1997019106
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] Review Release Planning docs

[Christopher Donley (Chris)]

Team,

I've updated our VNFSDK release planning materials on the wiki.  
https://wiki.onap.org/pages/viewpage.action?pageId=20875497.  Please review and 
suggest any updates.  Also, feel free to update any Jira tickets, if necessary. 
I'd like to finalize our plan by our call this Friday.

Thanks,
Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Invitation: [vnfsdk] Weekly Meeting @ Weekly from 6am to 7am on Friday (PDT) (christopher.don...@huawei.com)

[Christopher Donley (Chris)]

Reminder: tomorrow’s VNFSDK meeting is cancelled.  Our next meeting is 12/22.

-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Monday, July 17, 2017 5:37 PM
To: ONAP Meetings and Events; Christopher Donley (Chris); 
onap-discuss@lists.onap.org; alex@intel.com
Subject: Invitation: [vnfsdk] Weekly Meeting @ Weekly from 6am to 7am on Friday 
(PDT) (christopher.don...@huawei.com)
When: Friday, December 15, 2017 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/454599760


more details 
»<https://www.google.com/calendar/event?action=VIEW=cDBqaHRiczlmMHA4cjRtNjJvcmlxOXZkbGcgY2hyaXN0b3BoZXIuZG9ubGV5QGh1YXdlaS5jb20=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZmRmNzczM2M3ODAyZjA1NTVjZjNlNzE2ZDdjMGE5ZWJmYjM2ZmI4YQ=America/Los_Angeles=en>

[vnfsdk] Weekly Meeting
Hi there,

Chris Donley is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/454599760<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F454599760=D=2=AFQjCNE7fJgi8M2HMVsv8Na1reofMb00gQ>

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

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 454 599 760
International numbers available: 
https://zoom.us/zoomconference?m=viiAIbYha1FHOg4qZy9wY3LoQsy9Ut2P<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3DviiAIbYha1FHOg4qZy9wY3LoQsy9Ut2P=D=2=AFQjCNG7TTnldCMEIHuDmndNh9bG48NKlA>

When
Weekly from 6am to 7am on Friday Pacific Time

Where
https://zoom.us/j/454599760 
(map<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F454599760=D=2=AFQjCNE7fJgi8M2HMVsv8Na1reofMb00gQ>)

Calendar
christopher.don...@huawei.com

Who
•
kp...@linuxfoundation.org - creator

•
christopher.don...@huawei.com

•
onap-discuss@lists.onap.org

•
alex@intel.com



Going?   All events in this series:   
Yes<https://www.google.com/calendar/event?action=RESPOND=cDBqaHRiczlmMHA4cjRtNjJvcmlxOXZkbGcgY2hyaXN0b3BoZXIuZG9ubGV5QGh1YXdlaS5jb20=1=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZmRmNzczM2M3ODAyZjA1NTVjZjNlNzE2ZDdjMGE5ZWJmYjM2ZmI4YQ=America/Los_Angeles=en>
 - 
Maybe<https://www.google.com/calendar/event?action=RESPOND=cDBqaHRiczlmMHA4cjRtNjJvcmlxOXZkbGcgY2hyaXN0b3BoZXIuZG9ubGV5QGh1YXdlaS5jb20=3=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZmRmNzczM2M3ODAyZjA1NTVjZjNlNzE2ZDdjMGE5ZWJmYjM2ZmI4YQ=America/Los_Angeles=en>
 - 
No<https://www.google.com/calendar/event?action=RESPOND=cDBqaHRiczlmMHA4cjRtNjJvcmlxOXZkbGcgY2hyaXN0b3BoZXIuZG9ubGV5QGh1YXdlaS5jb20=2=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZmRmNzczM2M3ODAyZjA1NTVjZjNlNzE2ZDdjMGE5ZWJmYjM2ZmI4YQ=America/Los_Angeles=en>
more options 
»<https://www.google.com/calendar/event?action=VIEW=cDBqaHRiczlmMHA4cjRtNjJvcmlxOXZkbGcgY2hyaXN0b3BoZXIuZG9ubGV5QGh1YXdlaS5jb20=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZmRmNzczM2M3ODAyZjA1NTVjZjNlNzE2ZDdjMGE5ZWJmYjM2ZmI4YQ=America/Los_Angeles=en>
Invitation from Google Calendar<https://www.google.com/calendar/>

You are receiving this courtesy email at the account 
christopher.don...@huawei.com because you are an attendee of this event.
To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More<https://support.google.com/calendar/answer/37135#forwarding>.


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

Re: [onap-discuss] [vnfsdk] VNF SDK Meeting tomorrow (11/17/17) is CANCELLED

[Christopher Donley (Chris)]

Team,

We successfully released VNFSDK as part of Amsterdam yesterday. Congratulations!

Instead of a meeting today, I’d like to start discussion through email on 
several topics:

·committer promotion(s)

·Planning for maintenance release (Amsterdam 1.0.1)

·Planning for Beijing release

committer promotion
Several people have asked about the committer promotion process.  Essentially, 
we need to discuss promotions as a team and conduct a vote of the committers.  
Once we complete the vote, we ask the TSC to approve our decision.

3.2.2.1 Adding Committers

 *   Initial Committers for a project will be specified at project creation
 *   Committer rights for a project are earned via contribution and 
community trust. Committers for a project select and vote for new Committers 
for that project, subject to TSC approval.
 *   New Committers for a project should have a demonstrable established 
history of meritocratic contributions

I would like to open up the promotion process by soliciting criteria and 
nominations.  One source of data is bitergia, which shows code added and 
modified.
Author

Commits

Projects

Added Lines

Removed Lines

Avg. Files

Murali Mohan Murthy Potham

117

1

3,730

808,243

49.991

Harry Huang

49

1

1,265

1,346

1.245

Avinash S

35

1

10,867

700,332

120.629

Chris Donley

32

1

5,508

856

1.875

Gary Wu

11

1

6

6

0.545

GOKUL SINGARAJU

9

1

45,526

87

21.333

Jessica Wagantall

7

1

5

5

0.714

Lianhao Lu

7

1

636

55

3.857

Eric Debeau

5

1

928

939

2.4

Morgan Richomme

4

1

558

562

2













However, this does not show confluence activity or other project activities 
(such as in the vnf modeling subteam). How should we measure them to 
demonstrate “meritocratic contributions”?

Planning for maintenance release
There will be an Amsterdam maintenance release in mid-January.  While the 
criteria and process have not been published yet, I believe it’s for bug fixes 
only.  I think we’ll have a window until mid-Dec to work on highest, high, and 
medium bugs.  After mid-December, we will probably be limited to high/highest 
bugs and results of pair testing and integration testing.  We have a handful of 
medium bugs in the queue.  Aside from those, are there other things we should 
consider?

Planning for Beijing
We’ve talked about a few aspects already (image store, updating code to reflect 
the new model, etc.) .  In addition, I spoke with David Shadmi from AT about 
possible ways to get better alignment with SDC and VVP in Beijing.  We’d like 
to set up a joint meeting after Thanksgiving (look for something around 11/29), 
and a follow-up at the developer summit in December.   What else should we 
consider?  Please continue to circulate ideas on the wiki and via email – we’ll 
review in two weeks.

Note that next week’s meeting is also cancelled due to the Thanksgiving holiday 
in the US.

Chris

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Brian Hedstrom
Sent: Thursday, November 16, 2017 1:47 PM
To: onap-discuss 
Subject: [onap-discuss] [vnfsdk] VNF SDK Meeting tomorrow (11/17/17) is 
CANCELLED

Hi Team,
Chris would like to cancel tomorrow's meeting and hold it via email.  Look for 
an email from Chris later tonight or tomorrow.

Thanks,

--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oamtechnologyconsulting.com
brian.hedst...@oamtechnologies.com
720-470-7091
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

[Christopher Donley (Chris)]

The architecture subcommittee is working on the high-level architecture.  See 
http://onap.readthedocs.io/en/latest/guides/onap-developer/architecture/onap-architecture.html

Projects themselves are publishing the more detailed architecture, APIs, etc. 
on readthedocs.

Chris

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Vladimir Yanover (vyanover)
Sent: Tuesday, November 14, 2017 6:32 AM
To: jamil.cha...@orange.com
Cc: onap-discuss ; Lisa Caywood 
; onap-tsc 
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

And where this intention / timeline is captured?
Thanks
Vladimir

From: jamil.cha...@orange.com 
[mailto:jamil.cha...@orange.com]
Sent: Tuesday, November 14, 2017 4:29 PM
To: Vladimir Yanover (vyanover) >
Subject: RE: [onap-tsc] Official ONAP Architecture Slide

It should be part of  the Release Amsterdam documentation …

De : Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Envoyé : mardi 14 novembre 2017 15:27
À : CHAWKI Jamil IMT/OLN
Cc : Kenny Paul; onap-discuss; onap-tsc; Lisa Caywood
Objet : RE: [onap-tsc] Official ONAP Architecture Slide

How is it related to my question on the timeline for delivery of specification 
with certain level of details?
Thanks
Vladimir

From: jamil.cha...@orange.com 
[mailto:jamil.cha...@orange.com]
Sent: Tuesday, November 14, 2017 4:16 PM
To: Vladimir Yanover (vyanover) >
Cc: Kenny Paul >; 
onap-discuss >; 
onap-tsc >; Lisa 
Caywood >
Subject: RE: [onap-tsc] Official ONAP Architecture Slide

Yes this is in the Scope of the Architecture subcommittee
https://wiki.onap.org/display/DW/Goals

De : Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Envoyé : mardi 14 novembre 2017 14:55
À : CHAWKI Jamil IMT/OLN
Cc : Kenny Paul; onap-discuss; onap-tsc; Lisa Caywood
Objet : RE: [onap-tsc] Official ONAP Architecture Slide

Thanks, Jamil. I like the diagram. My question was

Is there an intention / timeline for delivery of specifications with the level 
of details as e.g. in OpenStack (ETSI NFV, …)?

Vladimir

From: jamil.cha...@orange.com 
[mailto:jamil.cha...@orange.com]
Sent: Tuesday, November 14, 2017 3:45 PM
To: Vladimir Yanover (vyanover) >
Cc: Kenny Paul >; 
onap-discuss >; 
onap-tsc >; Lisa 
Caywood >
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hi Vladimir
The diagram is more a technical overview of onap components.
Regards
Jamil

Le 14 nov. 2017 à 11:25, Vladimir Yanover (vyanover) 
> a écrit :
Hello, Kenny
Thanks for sharing the Architecture diagram.
I will appreciate if you help me with a question that I have on the ONAP 
architecture documentation.
Consider potential products to be integrated into the ONAP system itself, 
interfacing to its components such as the Policy Framework and SDN-C Controller.
For such integration, the published Architecture diagram lacks many details 
that normally are provided in the architecture specifications, such as 3GPP TS 
23.501 or ETSI GS NFV 002. It’s functional description of every component, 
interfaces between the components, operations that can be executed over these 
interfaces etc. Examples from open source communities: the OpenStack’s 
Conceptual architecture 
https://docs.openstack.org/mitaka/install-guide-rdo/common/get_started_conceptual_architecture.html
 and Networking architecture at 
https://docs.openstack.org/security-guide/networking/architecture.html#.

Here is my question: is there an intention / timeline for delivery of 
specifications with this level of details?

Thanks
Vladimir Yanover (Cisco)


From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: Tuesday, November 14, 2017 3:13 AM
To: onap-discuss 
>; onap-tsc 
>
Cc: Lisa Caywood 
>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Should be fixed. I’ve been using Confluence since 

Re: [onap-discuss] [vnfsdk] - DB transactions

[Christopher Donley (Chris)]

Please don't add any new features until after Amsterdam is released.  We can 
look at this as part of Beijing - feel free to add it to the planning page in 
the meantime, and we'll review it as part of R2 planning.

Chris

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley
Sent: Tuesday, November 07, 2017 4:47 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [vnfsdk] - DB transactions

Hi
I noticed that we don't use transactions in marketplace portal.
I would like to develop and add it to the project.
I plan to introduce spring and leverage the tools it provides.
This will also be beneficial in the future when we add security to the portal
What do you think?

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] Passed M4

[Christopher Donley (Chris)]

Dear Team,

We have officially passed the M4 milestone on Thursday. Congratulations, and 
thanks for all of your hard work.

Now that we have passed the code freeze, we need to be focusing on testing, 
quality improvements, and documentation through November.  At this point, 
please participate in the Integration testing activities and identify any bugs. 
 No new code can be introduced (other than bug fixes).

Thanks,
Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled: [vnfsdk] VNF SDK weekly meeting

[Christopher Donley (Chris)]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Christopher Donley (Chris):MAILTO:christopher.don...@huawei.co
 m
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tina Tsou:
 MAILTO:tina.t...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'NGUYEN, T
 OAN T'":MAILTO:tn2...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Daniel Si
 lverthorn':MAILTO:daniel.silverth...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ran Polla
 k':MAILTO:ran.pol...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Casem Majd
  (Cas Majd):MAILTO:cas.m...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Johanne M
 ayer':MAILTO:johanne.ma...@oracle.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Schatzber
 g, Gershon'":MAILTO:gershon.schatzb...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alex Dalt
 rini (adaltrin)':MAILTO:adalt...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='amir@giga
 spaces.com':MAILTO:a...@gigaspaces.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Yang, Bin
 '":MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Parviz Yeg
 ani:MAILTO:parviz.yeg...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Iwata, At
 sushi'":MAILTO:atsushi.iw...@necam.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'SPATSCHEC
 K, OLIVER  (OLIVER)'":MAILTO:spat...@research.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lingli De
 ng':MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tomer Bar
  David':MAILTO:tomer.bar-da...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Karin Arn
 old':MAILTO:karin.arn...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Josef Rei
 singer':MAILTO:josef.reisin...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Marc.Fied
 l...@telekom.de':MAILTO:marc.fied...@telekom.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Suresh Ba
 bu Nekkalapudi':MAILTO:snekkalap...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Stephen L
 anthier':MAILTO:stephen.lanth...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ethan Lyn
 n':MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Xinhui Li
 ':MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Michael O
 'Brien':MAILTO:frank.obr...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Eli Willi
 ams (eliwill)':MAILTO:eliw...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Deepak Mi
 chael (demichae)':MAILTO:demic...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'TABEDZKI,
  RICHARD'":MAILTO:rt0...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Lando,Mic
 hael'":MAILTO:ml6...@intl.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Nazir, Fa
 wad'":MAILTO:fawad.na...@team.telstra.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'SINGARAJU
 , GOKUL'":MAILTO:gs2...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Johnson, 
 Dan 1. (Nokia - US/Naperville)'":MAILTO:dan.1.john...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Varhegyi,
  Tamas (Nokia - HU/Budapest)'":MAILTO:tamas.varhe...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Steve Hal
 gren':MAILTO:steve.halg...@oracle.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jaco Four
 ie':MAILTO:jaco.fou...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PAR

Re: [onap-discuss] R2 non-functional requirements

[Christopher Donley (Chris)]

Also, the recordings from the call are posted on the wiki: 
https://wiki.onap.org/display/DW/Joint+meetings.

Chris
From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Thursday, September 07, 2017 11:43 AM
To: onap-...@lists.onap.org P ; 
onap-discuss@lists.onap.org; onap-usecase...@lists.onap.org; 
onap-...@lists.onap.org
Subject: [Onap-arc] R2 non-functional requirements

Hi all,

As a result of discussions we had in Usecase subcommittee and during our joint 
meeting with Architecture subcommittee today, the following wiki page was 
created 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements .

This would list all non-functional requirements (i.e. not coming directly from 
a different use cases e.g. credentials usage, performance, resiliency, testing 
requirements etc.). These non-functional requirements are playing key role in 
building a stable, "Enterprise grade" ONAP platform.

Members of Architecture and Usecase subcommittees, the whole ONAP community - 
please fill in requirements' candidates for R2, we will then review and 
prioritize.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3281F.7EDCC090]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vnfsdk] VNF SDK weekly meeting

[Christopher Donley (Chris)]

Thanks to everyone for participating on today's call. The recording is now 
available, and has been posted to the wiki. 
https://wiki.onap.org/download/attachments/13600471/zoom_0.mp4?version=1=1503698495607=v2

I want to check consensus from the call to make sure we all have a common 
understanding.  We are looking for common ground on the CSAR format for R1 that 
can be supported by VNFSDK, SDC, VFC, and the VoLTE VNFs.  We heard two 
presentations, and there was a consensus to base the CSAR format on SOL-004.  
There was a difference of opinion as to whether to support Option 1 (including 
a metadata directory) or Option 2 (including a manifest file but no data 
directory).  Long term, we heard interest in Option 2, but several of the 
developers across several projects mentioned that they would have trouble 
implementing it for R1, and that Option 1 could be more readily adopted.

Accordingly, we agreed:
*   We will support Option 1 in R1 across VNFSDK, SDC, and VFC.
*   The VNFSDK modeling subproject will develop a guideline on the 
long-term direction before the end of the release. It will be based on SOL-004. 
Part of the guideline should include a transition plan (if necessary)
*   We will coordinate between VNFSDK, SDC, and VFC to support the 
guideline in the R2 timeframe.

Please let me know if I missed or misstated anything.

Thanks,
Chris

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

Re: [onap-discuss] Clarifying VNFSDK<->SDC

[Christopher Donley (Chris)]

Thanks David.  I want to confirm that we will supply some developers to 
implement the API between our projects (steps 4-6). I'll supply contact 
information shortly. Do you need any help with the TOSCA parser, as well?

We appreciate your help getting us started.

Chris

From: SHADMI, DAVID [mailto:ds2...@att.com]
Sent: Tuesday, August 22, 2017 1:49 PM
To: Murali p <mural...@huawei.com>; Christopher Donley (Chris) 
<christopher.don...@huawei.com>; HALFON, TAL <half...@amdocs.com>; LANDO, 
MICHAEL <ml6...@intl.att.com>
Cc: Gaoweitao (Victor, MANO) <victor@huawei.com>; Vul, Alex 
<alex@intel.com>; LU, TINGTING <tl2...@att.com>; onap-discuss@lists.onap.org
Subject: RE: Clarifying VNFSDK<->SDC

Hi,

I am adding Tal Halfon (Amdocs) who could provide more detailed information 
about the actual flows.

Onboarding flow - Marketplace option (user scenario):

  1.  SDC user selects "Onboard" option (upper bar) and presented with 
Onboarding Workplace
  2.  SDC user selects "Onboard VNF" (new Option in R1)
  3.  SDC user selects either to upload a VNF package file or to "Browse 
Marketplace"
  4.  SDC user selects to "Browse Marketplace" and presented with a list of 
validated VNFs
SDC user can search/sort Marketplace according to:

 *   VNF Name
 *   Vendor Name
 *   Keywords
  1.  SDC user selects VNF and VNF information is presented
  2.  SDC user downloads VNF
  3.  SDC user is presented with a screen with the information from the VNF 
package (VNF Name, Vendor, Version)
  4.  SDC user adds service provider information (license model, category) to 
the VNF

Steps 1-3 and 7-8 are the same for manual upload of VNF TOSCA package and would 
be implemented by Tal's team.
The integration between SDC and Market Place are steps 4-6 which include some 
UI development (can reuse some of SDC existing screens), integration with 
Market Place API, and integration with SDC import TOSCA API being implemented 
by Tal's team.

@Tal - could you please advise on the proposed flow and help the SDKVNF team 
with the code and information to implement the integration with the Market 
Place?
@Michael - could you please help with SDC environment setup?

Thanks,
David


From: Murali p [mailto:mural...@huawei.com]
Sent: Tuesday, August 22, 2017 5:42 AM
To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; Christopher Donley 
(Chris) <christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>
Cc: Gaoweitao (Victor, MANO) 
<victor@huawei.com<mailto:victor@huawei.com>>; Vul, Alex 
<alex@intel.com<mailto:alex@intel.com>>; LU, TINGTING 
<tl2...@att.com<mailto:tl2...@att.com>>; LANDO, MICHAEL 
<ml6...@intl.att.com<mailto:ml6...@intl.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: Clarifying VNFSDK<->SDC

David,

Please clarify and guide us on  the below integration of SDC and Market Place.

Steps in current ONAP VF create:

1)  Create License
2)  Define VSP
3)  Define VF ==> Import the VNF packages from Market place

Market Place:
1)  I find the below step is where we can download , query and search for 
VNF packages from Market place to SDC for onboarding.
2)  All the information mentioned (Name, vendor, category, version  is 
available ) along with CSAR.
3)  Can somebody help to locate the code, where we can embed this 
functionality and how to set up development/debug environment for SDC at least 
for this functionality?
4)  The functionality will be made optional by providing a check box 
"Import from Market Place".

User scenario:
1)  User directly import VF -(CSAR file) (Step 3).
2)  User click the check box ("Import from Market Place")
3)  SDC queries all or some VNF (based on search criteria) and display.
4)  User can either select "Import or Download". In both cases the package 
is downloaded

along with required metadata field and passed to VF create API.


[cid:image001.png@01D31B5E.6CDD8910]


From: SHADMI, DAVID [mailto:ds2...@att.com]
Sent: 18 August 2017 23:50
To: Christopher Donley (Chris) 
<christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>
Cc: Murali p <mural...@huawei.com<mailto:mural...@huawei.com>>; Gaoweitao 
(Victor, MANO) <victor@huawei.com<mailto:victor@huawei.com>>; Vul, Alex 
<alex@intel.com<mailto:alex@intel.com>>; LU, TINGTING 
<tl2...@att.com<mailto:tl2...@att.com>>; LANDO, MICHAEL 
<ml6...@intl.att.com<mailto:ml6...@intl.att.com>>
Subject: RE: Clarifying VNFSDK<->SO for R1

Hi Chris,

We have this task in our backlog for R1. However, it is has lower priority 
compared to other tasks for SDC core development team and therefore I can't 
guarantee it would get into R

[onap-discuss] Joint Architecture/Use Case meeting

[Christopher Donley (Chris)]

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=Christopher Donley (Chris):MAILTO:christopher.don...@huawei.co
 m
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alla Goldn
 er:MAILTO:alla.gold...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-arc@l
 ists.onap.org:MAILTO:onap-...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-useca
 se...@lists.onap.org:MAILTO:onap-usecase...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc@l
 ists.onap.org:MAILTO:onap-...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='onap-disc
 u...@lists.onap.org':MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Dear Architecture and Use Case subcommittees\,\n
 \nAlla and I would like to continue our joint ARC/Use Case meetings on Sep
 tember 7 at 1300 UTC. Please see the Zoom invitation below.\n\nChris & All
 a\n\n---\n\nHi there\,\n\n
 Chris Donley & Alla Goldner are inviting you to a scheduled Zoom meeting.\
 n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/43748053
 5\n\nOr iPhone one-tap (US Toll):  +16465588656\,\,437480535# or +16468769
 923\,\,437480535#\n\nOr Telephone:\nDial: +1 646 558 8656 (US Toll) or
  +1 646 876 9923 (US Toll)\nMeeting ID: 437 480 535\nInternational
  numbers available: https://zoom.us/zoomconference?m=mnKk1YCEnSSOS9SnLxFy2
 Tnd9JYqUR_a\n\n\n\n
SUMMARY;LANGUAGE=en-US:Joint Architecture/Use Case meeting
DTSTART;TZID=Pacific Standard Time:20170907T06
DTEND;TZID=Pacific Standard Time:20170907T07
UID:04008200E00074C5B7101A82E00810F4D9887B16D301000
 010003133856474F68041B8DB4146A73975DD
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170816T173635Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/437480535
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1871742945
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Usecase/Arch subcommittees joint meeting on Wednesday

[Christopher Donley (Chris)]

Thanks to all who joined today's joint ARC/usecase meeting.  The Zoom recording 
is now available 
https://zoom.us/recording/play/EZc2tN4iOTpsqZzkywoCrsdQg9kLjKSOshwnzG9dvQAfb1CesU8N3sHqvkWyaU0a

Chris

From: onap-arc-boun...@lists.onap.org [mailto:onap-arc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Tuesday, August 08, 2017 10:25 AM
To: onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 'onap-discuss@lists.onap.org' 
; onap-...@lists.onap.org
Subject: Re: [Onap-arc] Usecase/Arch subcommittees joint meeting on Wednesday

Hi all,

Please find here the updated agenda with preliminary questions received from 
Architecture subcommittee (thanks, Chris!):

1.Usecase subcommittee will present R1 use cases (Yoav/Kang - vCPE, 
Chengli/Yang - vVoLTE) and provide brief overview of R2 discussions, including 
emphasizing ONAP Platform Capabilities

2.Architecture subcommittee will present and highlight differences 
between R1 and R2 foreseen architecture, so Usecase subcommittee 
representatives can ask on that and its potential impact on use cases 
implementation, and also raise relevant issues.

3.Architecture subcommittee will ask their use case related 
questions:
-  would the use case(s) require multi-site support?
-  multi-region/multi-domain/federation?
-  Multi-national?
-  Do we need to consider enhanced networking features (e.g., 
underlays)?
-  Can individual use cases be built from same components? (common 
APIs/models)
-  What are the challenges from the first set of use cases?
-  What technical debt have you identified?
-  Clarify business drivers and capabilities of the use cases
-  What are the functional commonalities between the use cases? Are 
there generic elements where we should focus?

Usecase subcommittee members, please try to come to the meeting prepared with 
responses, as our meeting time is limited; would also be good to start 
communicating some of the responses by emails sent both to Usecase and to 
Architecture subcommittee.

This is start of our dialogue which will continue towards R2, as we move on 
with use cases definition and architecture definition. We will also discuss 
format and frequency of our join meetings going forward.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31100.6269CF10]

From: Alla Goldner
Sent: Monday, August 07, 2017 10:35 PM
To: onap-usecase...@lists.onap.org; Yoav 
Kluger >; 'Kang Xi' 
>; 'Chengli Wang' 
>; 'Yang Xu 
(Yang, Fixed Network)' >; 
'Yunxia Chen' >
Cc: GILBERT, MAZIN E (MAZIN E) 
>; Phil Robb 
>; 'Kenny Paul' 
>; 
onap-...@lists.onap.org
Subject: Usecase/Arch subcommittees joint meeting on Wednesday

Hi all,

After speaking with Chris, here is our proposal for the joint meeting on 
Wednesday:


1.  Usecase subcommittee will present R1 use cases (Yoav/Kang - vCPE, 
Chengli/Yang - vVoLTE), mostly concentrated on ONAP Platform capabilities



2.  Usecase subcommittee members are encouraged to ask questions/provide 
demands on potential functionality to be supported for the next releases


3.  Architecture subcommittee will present and highlight differences 
between R1 and R2 foreseen architecture, so Usecase subcommittee 
representatives can ask on that and its potential impact on use cases 
implementation, and also raise relevant issues.



4.  Architecture subcommittee will ask their use case related questions


5.  Both Usecase and Architecture subcommittee members are encouraged to 
send out their questions in advance, in order to make our discussions more 
effective.


This is start of our dialogue which will continue towards R2, as we move on 
with use cases definition and architecture definition. We will also discuss 
format and frequency of our join meetings going forward.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31100.6269CF10]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] FW: Joint Architecture/Use Case meeting

[Christopher Donley (Chris)]

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=Christopher Donley (Chris);SENT-BY="MAILTO:Alla.Goldner@amdocs.
 com":MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc@l
 ists.onap.org:MAILTO:onap-...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='onap-disc
 u...@lists.onap.org':MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:\n\n\n\n-Original Appointment-\nFrom: Ch
 ristopher Donley (Chris) [mailto:christopher.don...@huawei.com]\nSent: Tue
 sday\, August 01\, 2017 12:59 AM\nTo: Christopher Donley (Chris)\; onap-ar
 c...@lists.onap.org\; onap-usecase...@lists.onap.org\; Alla Goldner\nCc: onap
 -tsc\nSubject: Joint Architecture/Use Case meeting\nWhen: Wednesday\, Augu
 st 09\, 2017 7:00 AM-8:00 AM (UTC-08:00) Pacific Time (US & Canada).\nWher
 e: https://zoom.us/j/793175295\n\n\nDear Architecture and Use Case Subcomm
 ittees\,\n\nWe will hold a joint ARC/Use Case meeting on Wednesday\, Augus
 t 9 at 1400 UTC to synchronize on architectural impacts of proposed use ca
 se flows for R2.  We want to use this joint meeting to help refine both th
 e use cases and the architecture.\n\nWe hope you can join us.\n\nChris & A
 lla\n\n-\n\n\nHi there\,\n\nChris Donley is inviti
 ng you to a scheduled Zoom meeting.\n\nJoin from PC\, Mac\, Linux\, iOS or
  Android: https://zoom.us/j/793175295\n\nOr iPhone one-tap (US Toll):  +16
 465588656\,\,793175295# or +14086380968\,\,793175295#\n\nOr Telephone:\n  
   Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\nMeetin
 g ID: 793 175 295\nInternational numbers available: https://zoom.us/zo
 omconference?m=sTOKi0Gvq4vo3lRdpmPlJMUYmKzDUNuq\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:FW: Joint Architecture/Use Case meeting
DTSTART;TZID=Pacific Standard Time:20170809T07
DTEND;TZID=Pacific Standard Time:20170809T08
UID:04008200E00074C5B7101A82E0089065B58B0D0AD301000
 0100034A9633E578FEC40AF785F33AF47BD5C
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170731T215901Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/793175295
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1350531041
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk][sdc] discuss CSAR and API coordination for R1

[Christopher Donley (Chris)]

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=Christopher Donley (Chris):MAILTO:christopher.don...@huawei.co
 m
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MAYER, AND
 REW J":MAILTO:am8...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SHADMI, DA
 VID":MAILTO:ds2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Gaoweitao 
 (Victor, MANO)":MAILTO:victor@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tim Taylor
  (timtayl):MAILTO:timt...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Pugaczewsk
 i, Jack":MAILTO:jack.pugaczew...@centurylink.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tina Tsou:
 MAILTO:tina.t...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ramki Kris
 hnan:MAILTO:ram...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=brian.heds
 t...@oamtechnologies.com:MAILTO:brian.hedst...@oamtechnologies.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SPATSCHECK
 , OLIVER  (OLIVER)":MAILTO:spat...@research.att.com
DESCRIPTION;LANGUAGE=en-US:Hi there\,\n\nChris Donley is inviting you to a 
 scheduled Zoom meeting.\n\nJoin from PC\, Mac\, Linux\, iOS or Android: ht
 tps://zoom.us/j/597602947\n\nOr iPhone one-tap (US Toll):  +16465588656\,\
 ,597602947# or +14086380968\,\,597602947#\n\nOr Telephone:\nDial: +1 6
 46 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\nMeeting ID: 597 60
 2 947\nInternational numbers available: https://zoom.us/zoomconference
 ?m=p_5otMlALzgGFQaQluuI4LK_0dP7WPfp\n\n\n\n
SUMMARY;LANGUAGE=en-US:[vnfsdk][sdc] discuss CSAR and API coordination for 
 R1
DTSTART;TZID=Pacific Standard Time:20170814T08
DTEND;TZID=Pacific Standard Time:20170814T09
UID:04008200E00074C5B7101A82E008B0BCAF09870FD301000
 01000EE805B3A14B7CD4D8B2B60C35D7A29FA
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170807T221141Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://zoom.us/j/597602947
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:912754657
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vnfsdk][sdc] VNF SDK/SDC alignment

[Christopher Donley (Chris)]

David,

During the 3-hour windows we have available, I'm available Monday 8-9 or 
Wednesday 6-7 or 8-9 Pacific time.  Will any of those work?

Chris

From: SHADMI, DAVID [mailto:ds2...@att.com]
Sent: Thursday, August 03, 2017 10:00 AM
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; LU, TINGTING 
<tl2...@att.com>; onap-discuss@lists.onap.org; 'Tina Tsou' <tina.t...@arm.com>; 
Halfon Tal <halfon@amdocs.com>
Cc: Murali p <mural...@huawei.com>; Gaoweitao (Victor, MANO) 
<victor@huawei.com>; ROZIN, EDEN <er4...@intl.att.com>; 'Pujar, Rashmi' 
<rashmi.pu...@bell.ca>; SOMASUNDARAM, PRABHURAM <ps7...@att.com>; 'Pugaczewski, 
Jack' <jack.pugaczew...@centurylink.com>; 'Sandeep Shah2' 
<ss00473...@techmahindra.com>; GUPTA, ALOK <ag1...@att.com>; Parviz Yegani 
<parviz.yeg...@huawei.com>; Casem Majd (Cas Majd) <cas.m...@huawei.com>; 
OBRIEN, FRANK MICHAEL <frank.obr...@amdocs.com>; SILVERTHORN, DANIEL 
<daniel.silverth...@amdocs.com>; ZHANG, MAX <maxzh...@research.att.com>; Karin 
Arnold <karin.arn...@de.ibm.com>; Abinash Vishwakarma 
<abinash.vishwaka...@netcracker.com>; KAPELUTO, ZAHI <zk0...@intl.att.com>; 
LEFEVRE, CATHERINE <cl6...@intl.att.com>; Gadiyar, Rajesh 
<rajesh.gadi...@intel.com>; Tim Taylor (timtayl) <timt...@cisco.com>; Marisa S 
Viveros <vive...@us.ibm.com>; Vul, Alex <alex@intel.com>; TABEDZKI, RICHARD 
<rt0...@att.com>; Chen, Wei D <wei.d.c...@intel.com>; Yang, Vivien 
<vivien.y...@intel.com>; Alex Daltrini (adaltrin) <adalt...@cisco.com>; 
EMPOROPULO, VITALIY <vitaliy.emporop...@amdocs.com>; Xinhui Li 
<lxin...@vmware.com>
Subject: RE: [vnfsdk][sdc] VNF SDK/SDC alignment

Hi Chris,

Can we meet early next week to continue the VNFSDK/SDC integration discussion?
The items I would like to discuss are:

  1.  CSAR structure
  2.  Continue the market place API discussions for R1

Thanks,
David

From: Christopher Donley (Chris) [mailto:christopher.don...@huawei.com]
Sent: Wednesday, August 02, 2017 1:02 PM
To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; LU, TINGTING 
<tl2...@att.com<mailto:tl2...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 'Tina Tsou' 
<tina.t...@arm.com<mailto:tina.t...@arm.com>>
Cc: Murali p <mural...@huawei.com<mailto:mural...@huawei.com>>; Gaoweitao 
(Victor, MANO) <victor@huawei.com<mailto:victor@huawei.com>>; ROZIN, 
EDEN <er4...@intl.att.com<mailto:er4...@intl.att.com>>; 'Pujar, Rashmi' 
<rashmi.pu...@bell.ca<mailto:rashmi.pu...@bell.ca>>; SOMASUNDARAM, PRABHURAM 
<ps7...@att.com<mailto:ps7...@att.com>>; 'Pugaczewski, Jack' 
<jack.pugaczew...@centurylink.com<mailto:jack.pugaczew...@centurylink.com>>; 
'Sandeep Shah2' 
<ss00473...@techmahindra.com<mailto:ss00473...@techmahindra.com>>; GUPTA, ALOK 
<ag1...@att.com<mailto:ag1...@att.com>>; Parviz Yegani 
<parviz.yeg...@huawei.com<mailto:parviz.yeg...@huawei.com>>; Casem Majd (Cas 
Majd) <cas.m...@huawei.com<mailto:cas.m...@huawei.com>>; OBRIEN, FRANK MICHAEL 
<frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; SILVERTHORN, DANIEL 
<daniel.silverth...@amdocs.com<mailto:daniel.silverth...@amdocs.com>>; ZHANG, 
MAX <maxzh...@research.att.com<mailto:maxzh...@research.att.com>>; Karin Arnold 
<karin.arn...@de.ibm.com<mailto:karin.arn...@de.ibm.com>>; Abinash Vishwakarma 
<abinash.vishwaka...@netcracker.com<mailto:abinash.vishwaka...@netcracker.com>>;
 KAPELUTO, ZAHI <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; LEFEVRE, 
CATHERINE <cl6...@intl.att.com<mailto:cl6...@intl.att.com>>; Gadiyar, Rajesh 
<rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; Tim Taylor 
(timtayl) <timt...@cisco.com<mailto:timt...@cisco.com>>; Marisa S Viveros 
<vive...@us.ibm.com<mailto:vive...@us.ibm.com>>; Vul, Alex 
<alex@intel.com<mailto:alex@intel.com>>; TABEDZKI, RICHARD 
<rt0...@att.com<mailto:rt0...@att.com>>; Chen, Wei D 
<wei.d.c...@intel.com<mailto:wei.d.c...@intel.com>>; Yang, Vivien 
<vivien.y...@intel.com<mailto:vivien.y...@intel.com>>; Alex Daltrini (adaltrin) 
<adalt...@cisco.com<mailto:adalt...@cisco.com>>; EMPOROPULO, VITALIY 
<vitaliy.emporop...@amdocs.com<mailto:vitaliy.emporop...@amdocs.com>>; Xinhui 
Li <lxin...@vmware.com<mailto:lxin...@vmware.com>>
Subject: RE: [vnfsdk][sdc] VNF SDK/SDC alignment

Thanks to everyone who attended the VNFSDK/SDC meeting.  Zoom meeting 
recordings have been posted on the wiki: 
https://wiki.onap.org/pages/viewpage.action?pageId=11927730<https://u

[onap-discuss] [vnfsdk][sdc] Extra security subcommiittee / VNFSDK / SDC meeting

[Christopher Donley (Chris)]

--- Begin Message ---
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Romance Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Stephen Terrill:MAILTO:stephen.terr...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-secco
 m...@lists.onap.org:MAILTO:onap-sec...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-sdnc@
 lists.onap.org:MAILTO:onap-s...@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nThis is a call for an extra meeting betw
 een the Security sub-committee\, VFNSDK project and SDC project.  Chris pl
 ease foreward to the VNFSDK team.\n\nThe agenda:\n   *   Proposal around S
 DK infrastructure and signing of VNFs.\n\nThe zoom details will follow lat
 er – Kenny could you help out on this one please for this once off meeti
 ng.\n\nBest Regards\,\n\nSteve\n
SUMMARY;LANGUAGE=en-US:Extra security subcommiittee / VNFSDK / SDC meeting
DTSTART;TZID=Romance Standard Time:20170810T15
DTEND;TZID=Romance Standard Time:20170810T16
UID:04008200E00074C5B7101A82E008C0EC316AD60BD301000
 01000B0AF9FEA355CD84981F518DF4DCEC763
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170802T193258Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:Will come later
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-377321503
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
--- End Message ---
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk][sdc] VNF SDK/SDC alignment

[Christopher Donley (Chris)]

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=Christopher Donley (Chris):MAILTO:christopher.don...@huawei.co
 m
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SHADMI, DA
 VID":MAILTO:ds2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="LU, TINGTI
 NG":MAILTO:tl2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tina Tsou:
 MAILTO:tina.t...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Murali p:M
 AILTO:mural...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Gaoweitao 
 (Victor, MANO)":MAILTO:victor@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="ROZIN, EDE
 N":MAILTO:er4...@intl.att.com
DESCRIPTION;LANGUAGE=en-US:Sync between SDC and VNF SDK\n\n
 _\nFrom: SHADMI\, DAVID [mailto:ds2...@att.com
 ]\nSent: Tuesday\, August 01\, 2017 2:02 PM\nTo: Christopher Donley (Chris
 ) <christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>>\; 
 LU\, TINGTING <tl2...@att.com<mailto:tl2...@att.com>>\nCc: Murali p >\; Gaoweitao (Victor\, MANO) >\; ROZIN\, EDEN >\nSubject: RE: VNF SDK sub-proje
 cts\n\n\nHi\,\n\nCan we meet 8-9am Pacific (10-11am Central)?\n\nThanks\,\
 nDavid\n\n\nHi there\,\n\nChris Donley is inviting you to a scheduled Zoom
  meeting.\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/
 j/979433593\n\nOr iPhone one-tap (US Toll):  +16465588656\,\,979433593# or
  +14086380968\,\,979433593#\n\nOr Telephone:\nDial: +1 646 558 8656 (U
 S Toll) or +1 408 638 0968 (US Toll)\nMeeting ID: 979 433 593\nInt
 ernational numbers available: https://zoom.us/zoomconference?m=6LFSoCFAnFN
 uNQsfNKvHc5vVRqaosy_V\n\n\n\n
SUMMARY;LANGUAGE=en-US:[vnfsdk][sdc] VNF SDK/SDC alignment
DTSTART;TZID=Pacific Standard Time:20170802T08
DTEND;TZID=Pacific Standard Time:20170802T09
UID:04008200E00074C5B7101A82E008002932F0D40AD301000
 01000967F573006903A42B89D84D173EFE3EC
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170801T214620Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/979433593
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:46237665
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Architecture Progress

[Christopher Donley (Chris)]

Dear Jamil,

Thank you for sharing.  I'd like to invite you to present your concerns 
regarding the Release 2+ framework on Tuesday's ARC call so that we can 
consider them as a committee. Would 30 minutes be sufficient?

Regarding Release 1, we are a week out from the functionality freeze milestone. 
 We have heard from the projects that their R1 plans are locked in, and any 
significant changes will delay the release, which is why the committee agreed 
to proceed with the baseline.  We don't want to put undue risk on the release 
date.  However, the projects are aware of the longer-term target, and did agree 
to look at their code and try to identify any "baby steps" they could take in 
that direction for the Amsterdam release.

Chris

From: jamil.cha...@orange.com [mailto:jamil.cha...@orange.com]
Sent: Thursday, July 27, 2017 9:46 AM
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; Thomas Nadeau 
<thomas.nad...@amdocs.com>; Alla Goldner <alla.gold...@amdocs.com>; Pasi 
Vaananen <pvaan...@redhat.com>; onap-discuss@lists.onap.org; Phil Robb 
<pr...@linuxfoundation.org>; kp...@linuxfoundation.org; MAZIN E GILBERT 
(ma...@research.att.com) <ma...@research.att.com>; vb1...@att.com; 'BARTOLI, 
PAUL D' (pb2...@att.com) <pb2...@att.com>
Cc: onap-tsc <onap-...@lists.onap.org>
Subject: RE: [onap-discuss] Architecture Progress
Importance: High

Dear Chris and ONAP community
I understand and appreciate your leadership of this subcommittee to align 
different position and I would to clarify some points:

1- Yes the VFC is mentioned in the ONAP charter but without any explanation 
about the functionality of this component which to my knowledge it is not part 
of the Open-o and we have discovered it during the ONS 2017. Comparing to 
Ecomp, we have a clear documented white paper describing overall architecture 
and technical components.

2- Concerning the AT /China Mobile agreement, I would like to clarify 
that ONAP is a merge between the OpenEcomp project proposal supported by some 
members and the Open-O project and not an AT/China Mobile project. Phil and 
Kenny I would like you as LF to clarify this point as my understanding the ONAP 
project is governed by a clear charter  and not by some company agreement or 
discussion.

3- I would like to remember the community that the TSC decision, during the 
last F2F meeting in China, was to approve the APPC, VFC and SO provisionally 
waiting  an alignment from the architecture point of view  : the TSC approved 
the VF-C (APPC/SO) Projects as an incubation projects within ONAP provisional 
on alignment with the overall architecture if such dependencies are identified

http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-08-01.38.log.html

http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-09-01.07.html

4- My expectation was to have a feedback from the architecture subcommittee 
to the TSC on this alignment and to have a final approval of these 3 projects. 
Phil and Kenny I would like to raise this question during the next TSC meeting 
and also to indicate in the wiki that these 3 projects are provisionally 
approved.

5- We have clearly identified an overlapping problem between APP-C, VF-C 
and between VF-C and SO (as VF-C is also an NFVO) and the conclusion was to 
wait Rel-2  or Rel-3 in order to find a solution. This will mean that we have a 
high risk to not deliver a useful Rel-1 and this risk was clearly viewed during 
the virtual meeting discussion on DCAE and SDC.

6- I think we have a time to converge rapidly our view by merging  APPC and 
VFC and having one integrated orchestrator, as proposed by Vimal,  before to be 
late.
The industry is waiting our Rel-1 and unfortunately, as Justin Paul said in his 
Linkedin post, ONAP leads, but its not over 'til the fat lady sings... and we 
may not have any song ...
https://www.linkedin.com/pulse/nfv-orchestration-onap-leads-its-over-til-fat-lady-sings-paul?trk=v-feed=v-feed=urn%3Ali%3Apage%3Ad_flagship3_search_srp_content%3B19yY4VKdyLkiQWwvYF88Qg%3D%3D

Regards
Jamil

De : onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Christopher Donley 
(Chris)
Envoyé : lundi 24 juillet 2017 23:40
À : Thomas Nadeau; Alla Goldner; Pasi Vaananen; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc : onap-tsc
Objet : Re: [onap-tsc] [onap-discuss] Architecture Progress

Tom,

I fully agree with your comments about top-down management. The architecture 
subcommittee is here to support and advise the projects, not command the 
projects.  I also agree with your point about this being a desired target 
state.  But I want to clarify that the projects have been involved in the 
creation of the long-term architecture.  This has not been an isolated exercise.

I'd like to 

Re: [onap-discuss] Architecture Progress

[Christopher Donley (Chris)]

Dear Jamil,

I'd like to invite you to participate in our ARC calls.  We generally meet 
Tuesdays from 1400-1600 UTC (but we'll have to adjust next week due to the 
developer meeting).  We have considered multiple presentations over the last 
four weeks (including the one you referenced), and after careful discussion, we 
aligned on the release 1 and release 2 functional architecture I shared.  I 
held consensus checks on each of the last two calls and did not hear dissenting 
opinions from the high level approach. The version of the diagram that I shared 
represents the community consensus from Tuesday's call.  If you have concerns, 
please share them during the meeting. I'll be happy to reserve a slot on the 
agenda.

Chris

From: jamil.cha...@orange.com [mailto:jamil.cha...@orange.com]
Sent: Friday, July 21, 2017 8:59 AM
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; 
onap-...@lists.onap.org; onap-discuss@lists.onap.org
Cc: onap-...@lists.onap.org
Subject: RE: Architecture Progress

Dear Chris
Thank you for your work and the presentation, we can say that this is a first 
step but we have not agreed on the architecture mentioned in your slide as 
Vimal presented another architecture (consigned by AT, Amdocs and Orange).
Regards
Jamil


De : onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Christopher Donley 
(Chris)
Envoyé : jeudi 20 juillet 2017 22:05
À : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Objet : [onap-tsc] Architecture Progress

Dear ONAP Technical Community,

I'd like to update you on progress from the Architecture Committee.

*For Amsterdam, we agreed to use the current architecture, as discussed 
since ONS.  This is to reduce risk of late changes to the project teams, who 
have built their plans based on the current baseline.

*Longer-term, starting with Release 2, we reached consensus on an 
approach to resolve the APP-C/VF-C challenge.  We are developing a three-layer 
orchestrator/controller functional architecture, with service 
orchestration/resource orchestration/controllers.  Note that this functional 
architecture does not imply a project structure.  Between now and the beginning 
of the R2 planning cycle, the team will drill down to the next level of detail 
on interfaces and project alignment, and then the projects will map code into 
the architecture to guide R2 plans. Cross-project discussions have already 
begun, and will continue over the coming weeks.  Meeting logistics will be sent 
to the ONAP-discuss email list for those who are interested in participating.

I have attached a set of diagrams that we reviewed in the Architecture 
Committee to illustrate both the R1 and R2 architecture.  Note that in the R2 
slide, since we are focused on the functional architecture and not the 
projects, we removed some of the boxes listing projects that support ONAP, but 
don't provide interfaces or data flows through the system.

For those interested in more detail, we will discuss this during the developer 
meeting next week.

Chris


_



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.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] developer commitments

[Christopher Donley (Chris)]

Team,

Thanks to everyone who responded with your commitment to VNF SDK so far.  I 
have included the list below.  If you haven't yet responded, or if I missed 
your email, would you please let me know where you want to contribute (or if 
you're only monitoring and not planning to contribute)?

Thanks,
Chris

VNF SDK

model

pkgtools

validation

documentation

refrepo

compliance

Unknown

Andy 40-50%

Lianhao 50%

Murali

Victor 50%

Zongbiao Li

Yuanxing 50%

Dave Chen 25%

Ting 15%

Ting 15%

Amir Levy

Lianhao 20%

Alex Vul

Andrei 50%

Chengli Wang

PM: Tina

Erik Sundelof

PTL: Chris

Fari Behi


Wenyao Guan


Stephen Gooch


Eddy Raineri


Eric Debeau


Helen Chen


Gary Wu


Oleg Kaplan


Trevor Cooper


Brian Hedstrom


Thinh Nguyenphu


Huabing Zhao


Zygmunt Lozinski


Don Levy


Amy Zwarico


Suresh Nekkalapudi


Gershon Schatzberg


Ranny Haiby


maopeng zhang


Steven Wright


Yang Xu


Bruce Thompson


John Strassner


Joe Zhang


Xin Lu


Zhong Quan


Dileep Ranganathan


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

Re: [onap-discuss] Use Case Subcommittee Flow

[Christopher Donley (Chris)]

I think we need to differentiate between short-term and long-term.

Short-term, we have a fairly good sense of the starting architecture and the 
general flows through the system, so the proposed artifacts to be handed over 
from UC to ARC make sense.  

Longer-term, however, we need a slight change.  Let's say we're adding a new 
controller such as an IoT Controller or blockchain or something else that 
requires a more significant change to the architecture.  In that case, I would 
expect the UC to define the "use case flow" between components/vnfs included in 
the use case, but ARC would define the "onap flows" between modules. 
Technically, that's part of the ARC charter: "This functional architecture 
helps inform relationships and interaction between functional modules, which 
may include high level information flows between the modules supporting the use 
case(s) driving each release."

Since we have several conditionally-approved projects waiting on input from the 
ARC, our meetings for the next couple of weeks (probably until M1) are going to 
be focused on resolving those questions, starting with VF-C/APP-C.  I think the 
ARC would be able to look at interfaces between M1 and M2, and then work with 
the projects to review their alignment between M2 and M3.  Accordingly, I 
suggest that each project populate its user stories without relying on 
interface principles (the PTLs between dependent projects should talk), and ARC 
will circle back to support projects with 7 and 8 before M2, particularly if 
there are any contentious or confusing issues.

Chris

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SPATSCHECK, OLIVER 
(OLIVER)
Sent: Monday, June 19, 2017 12:33 PM
To: Yunxia Chen
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Use Case Subcommittee Flow

OK.  

So are we following this for release 1.?

If yes we completed step 5 ( I guess we are official still voting on vCPE but 
we did get the majority number of votes already so it is bound to pass…).

That would mean step 6. has to kick in. 

Is the architecture subcommittee willing to step up to this?   As we need to 
have user stories for the projects by the end of the month the architecture 
subcommittee would have to close on this really this week so the projects can 
start on assessing the impact and writing user stories.

Chris any comments?

If we are following a different process for release one who is doing the work 
required in step 6.?

Thx

Oliver

> On Jun 19, 2017, at 3:10 PM  EDT, Yunxia Chen  wrote:
> 
> Thanks Alla and Yoav to put it together. Since Integration team will make 
> automatic CI/CD far before the real release, I suggest that they get involved 
> asap: the more they understand the use case, the more they could develop the 
> testing cases. And most importantly they define the gating use case.
>  
> I suggest to make some minor adjust on the flow:
>  
> 1.   Use case subcommittee discuses new use cases
> 2.Use case subcommittee produces use case flow diagrams, ONAP 
> flow diagrams, and suggests potential PNFs / VNFs
> 3.Use case subcommittee gets feedback from the potentially 
> effected projects including integration team on feasibility
> 4.Iterate back to 2.
> 5.TSC approval
> 6.Architecture subcommittee defines the general new/modified 
> interfaces principles, based on approved use cases
> 7.Projects define their extended functionality and their external 
> APIs, following those principles.
> 8.Detailed per-component flows are defined and projects write their 
> user stories / implement them; Integration team will work with use case 
> subcommittee continues to accompany the use case development, review 
> epics/user stories, answer questions, etc. (behave as system engineers for 
> the use case) through test start date.
> 9.Integration team will define the gating use case based on step 8; 
> and finalize the PNFs / VNFs selection, with the help of use case 
> subcommittee, architecture subcommittee, PTLs with ONAP projects
> 10.  TSC approval the gating use case.
> 11.  Integration project leads (coordinates) effort to get the gating 
> use case tested, repaired, and verified, and the results will be documented. 
>  
> Regards,
> Helen Chen
>  
> On 6/19/17, 11:39 AM, "onap-discuss-boun...@lists.onap.org on behalf of Alla 
> Goldner"  alla.gold...@amdocs.com> wrote:
>  
> Hi Yoav, Oliver, Steve, all,
> 
> Firstly, I believe we need to distinguish R1 from any future release. The 
> methodology we build here would be good to work with in the future releases, 
> but not immediately.
> For our immediate R1 work we need to quickly start interaction between 
> the use cases teams, the integration team and the projects, 

Re: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

[Christopher Donley (Chris)]

Team,

Just to clarify, this is a one-time meeting proposal.  There were limited slots 
next week, and this is the best I could find.  Next week, we will discuss 
recurring meeting times for future meetings.

Chris
From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Friday, May 26, 2017 5:17 PM
To: denghui (L); Christopher Donley (Chris); onap-...@lists.onap.org; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Hui,

Thanks for the clarification.
Sorry for the confusion.

Lingli

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: 2017年5月27日 8:12
To: Lingli Deng <denglin...@chinamobile.com>; Christopher Donley (Chris) 
<christopher.don...@huawei.com>; onap-...@lists.onap.org; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Lingli,

It doesn’t conflict with modeling (PDT 6-7AM), architecture will be PDT 8-9AM

Best regards,

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 7:55 AM
To: Christopher Donley (Chris); 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Hi Chris,

Thanks for the arrangements.

I am interested to join but found a conflict with modeling weekly calls.
Will the suggested time slot be used for subsequent routine calls or is it only 
a one-time suggestion?
Since I expect several people including myself to be regularly attending both 
meeting series, would you consider the possibility that we might reschedule it 
to another slot?

Thanks again,
Lingli

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: 2017年5月27日 7:44
To: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-tsc] ONAP Architecture subcommittee kickoff

Dear ONAP community,

This is a call-for-participation message for our newly created architecture 
subcommittee.

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.  Preliminary 
agenda includes:

  *   Introductions
  *   Discuss subcommittee goals, roles, purpose, processes/tools/communication 
mechanisms, and formation next steps
  *   Recurring meeting dates/times
  *   Discuss the starting point and open issues 
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Evolution%2005022017_v7.pptx?version=1=1493761356000=v2)
  *   As time permits, continue the SO-APP-C-VF-C discussion


For those interested in joining, here are the logistics:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

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

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 525 972 941
International numbers available: 
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Architecture subcommittee kickoff

[Christopher Donley (Chris)]

Dear ONAP community,

This is a call-for-participation message for our newly created architecture 
subcommittee.

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.  Preliminary 
agenda includes:

*Introductions

*Discuss subcommittee goals, roles, purpose, 
processes/tools/communication mechanisms, and formation next steps

*Recurring meeting dates/times

*Discuss the starting point and open issues 
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Evolution%2005022017_v7.pptx?version=1=1493761356000=v2)

*As time permits, continue the SO-APP-C-VF-C discussion


For those interested in joining, here are the logistics:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

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

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 525 972 941
International numbers available: 
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

Chris
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss