Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting

[Gadiyar, Rajesh]

+1 Good idea ☺

From:  on behalf of "GILBERT, MAZIN E (MAZIN 
E)" 
Date: Monday, June 12, 2017 at 2:01 PM
To: Kenny Paul 
Cc: "onap-disc...@lists.onap.org" , onap-tsc 

Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers 
Face-to-Face Meeting

I was not present for this discussion. We need to have a meeting around the 3rd 
week of
July to go through project by project progress. Phil and I discussed a virtual 
meeting
since folks will be too busy to travel, and some may not be able to.

Would like to get a sense from the TSC community if this is appropriate and more
convenient while voting for dates.

thanks
Mazin

On Jun 12, 2017, at 1:08 PM, Kenny Paul 
> wrote:

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt

Thank You.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
onap-discuss mailing list
onap-disc...@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM=8D2aZuG-pN820woJDvlHxyXQnkAsRt0bFjokAPWgc1E=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Invitation: ONAP Architecture Subcommittee Weekly Meeting @ Weekly from 08:00 to 09:00 on Tuesday (PDT) (christopher.don...@huawei.com)

[Christopher Donley (Chris)]

Dear Team,

Due to the OPNFV Summit, I need to cancel this week’s Architecture meeting.  
Our next call will focus on VF-C/APP-C, and several people critical to this 
discussion are unavailable this week.

We will resume our calls next week.

Chris

-Original Appointment-
From: ONAP Meetings and Events
Sent: Sunday, June 11, 2017 7:44 PM
Subject: Invitation: ONAP Architecture Subcommittee Weekly Meeting @ Weekly 
from 08:00 to 09:00 on Tuesday (PDT) (christopher.don...@huawei.com)
When: Tuesday, June 13, 2017 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/917511391


more details 
»

ONAP Architecture Subcommittee Weekly Meeting
Hi there,

ONAP Meeting 4 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/917511391
Or iPhone one-tap (US Toll): +16465588656,917511391# or +14086380968,917511391#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 917 511 391
International numbers available: 
https://zoom.us/zoomconference?m=RldTp0lAcFewk1ZIKtbiUPlr_puNua4X






When
Weekly from 08:00 to 09:00 on Tuesday Pacific Time

Where
https://zoom.us/j/917511391 
(map)

Calendar
christopher.don...@huawei.com

Who
•
Casey Cain - creator

•
onap-...@lists.onap.org

•
onap-tsc@lists.onap.org

•
christopher.don...@huawei.com



Going?   All events in this series:   
Yes
 - 
Maybe
 - 
No
more options 
»
Invitation from Google 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.
 << File: invite.ics >>

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [Modeling] The regular modeling teleconf of this week is cancelled

[denghui (L)]

Hello all

Due to OPNFV summit in Beijing, we would like to cancel this week teleconf.
Have a good free Tuesday morning or evening :)

Thanks,

Rittwiki & DENG Hui

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting

[Stephen Terrill]

Hi,

I would be supportive of this approach.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: 12 June 2017 23:02
To: Kenny Paul 
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers 
Face-to-Face Meeting

I was not present for this discussion. We need to have a meeting around the 3rd 
week of
July to go through project by project progress. Phil and I discussed a virtual 
meeting
since folks will be too busy to travel, and some may not be able to.

Would like to get a sense from the TSC community if this is appropriate and more
convenient while voting for dates.

thanks
Mazin

On Jun 12, 2017, at 1:08 PM, Kenny Paul 
> wrote:

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt

Thank You.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
onap-discuss mailing list
onap-disc...@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM=8D2aZuG-pN820woJDvlHxyXQnkAsRt0bFjokAPWgc1E=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting

[GILBERT, MAZIN E (MAZIN E)]

I was not present for this discussion. We need to have a meeting around the 3rd 
week of
July to go through project by project progress. Phil and I discussed a virtual 
meeting
since folks will be too busy to travel, and some may not be able to.

Would like to get a sense from the TSC community if this is appropriate and more
convenient while voting for dates.

thanks
Mazin

On Jun 12, 2017, at 1:08 PM, Kenny Paul 
> wrote:

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt

Thank You.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
onap-discuss mailing list
onap-disc...@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM=8D2aZuG-pN820woJDvlHxyXQnkAsRt0bFjokAPWgc1E=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] subcommittees

[Kenny Paul]

Hi Zhaoxing,

I will be reworking the wiki over the next couple of weeks. I will add this to 
the list of things to do.

Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

> On Jun 11, 2017, at 7:20 PM, meng.zhaoxi...@zte.com.cn wrote:
> 
> Hi,
> 
> 
> 
> I suggest moving the wiki pages of all the subcommittees under the TSC page. 
> So people can easily find them. 
> 
> 
> 
> Zhaoxing
> 
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Forward:Re: Comments about Holmes

[GILBERT, MAZIN E (MAZIN E)]

Ok. It would have been beneficial to have a deeper dive with the DCAE team and 
the architecture team so you understand the flow and architecture.
My view is not to allow this to run independently. They are serious efforts in 
terms of life cycle management, resource management,
reliability, etc that one needs to support for each of these components, and we 
can not repeat that work for each analytics service
provided by each contributor.

Hence DCAE tries to bring it all together and enable on boarding of different 
types of Microservices.


On Jun 11, 2017, at 11:18 PM, 
fu.guangr...@zte.com.cn wrote:


Hi Mazin,

We have discussed with Oliver and are now aware of that DCAE is an open 
platform that allows independent/external systems to be integrated with it. 
Based on this and to make Holmes more flexible, we proposed Holmes to be set up 
as a standalone project.

Being a standalone project does not mean that Holmes will not support DCAE. 
Holmes will expose DMaaP related APIs to the public and be released in the form 
of docker(s) so that it can be integrated with DCAE. Meanwhile, as an 
independent system, Holmes can also be run in standalone mode, which enables it 
to be connected or utilized by other systems in ONAP directly.

Regards,

Guangrong




Original Mail
Sender: zhaohuabing10201488
To: fuguangrong10144542;
CC: mengzhaoxing10024238;wangrui10208678;
Date: 2017/06/12 09:05
Subject: Forward：Re: [onap-tsc] Comments about Holmes


From:  GILBERT,MAZINE(MAZINE);
To:roberto.k...@orange.com; fuguangrong10144542;
Cc:t...@lists.onap.org;
Date:  2017-06-11 06:08:46
Subject:Re: [onap-tsc] Comments about Holmes


Guangdong


I realize the TSC arrived at a middle ground during the F2F meeting of having 
Holmes as a separate project. I have tried to share my views on this previously 
and it seems to have failed. DCAE is a framework for on operating big data 
Microservices. Holmes is an analytics Microservice, that is policy driven. The 
policies are set through Drools by the Policy engine, while the analytics is 
done by DCAE. DCAE and Policy have well defined protocols to help operate 
control loops. This design was done so that developers can build, test and 
deploy their own Microservices (correlations, predictions,, normalization, 
compressions, analytics, etc) without having to establish yet another 
independent component in ONAP.  There are numerous large-scale correlation 
engines adopted by many operators and vendors today. Holmes is one example. 
This flexibility in the design in ONAP. allows companies to plug and play their 
Microservices function without additional dependencies or software development. 
This approach is successful and how it is employed in AT




I strongly suggest you spend sometime to better understand how DCAE and 
open/close loops work in ONAP. It is very important that we enable 
disaggregation and flexibility so that developers can innovative quickly. I 
will rely heavily on the architecture subcommittee to ensure Holmes is properly 
disaggregated when used in ONAP.


Thanks and look forward to your contributions to R1.


Mazin




GetOutlook for 
iOS
_
From: roberto.k...@orange.com
Sent: Wednesday, June 7, 2017 11:29 AM
Subject: Re: [onap-tsc] Comments about Holmes
To: <   fu.guangr...@zte.com.cn>
Cc: <   t...@lists.onap.org>



Thanks for your comments. This will be discussed and decided at the TSC. Best 
regard. Roberto

De : fu.guangr...@zte.com.cn 
[mailto:fu.guangr...@zte.com.cn]
Envoyé : mercredi 7 juin 2017 16:42
À : KUNG Roberto OLN/QOP
Cc : t...@lists.onap.org
Objet : 答复: Comments about Holmes


Hi Roberto,



Thanks for your information.



For the overlap, I have to clarify again that although Holmes and Policy are 
both based on Drools, the goal of them is totally different. Holmes is targeted 
to find out the correlation among tens of thousands (even more) of alarms while 
Policy is aimed to which action should be taken to accomplish 
auto-scaling/auto-healing tasks. I think systems should be defined by what 
their functions rather than the technologies they adopt.



Besides, to make our systems easier to maintain, we have to hold on to the 
Single Responsibility Principle. If we merge Holmes with Policy, the logic of 
the policy rules will get much more complicated, which makes it rather hard to 
trace or fix the problem/bug if any occurs in the futher.



For the reasons above, I still suggest we make Holmes an independent 

Re: [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting

[SPATSCHECK, OLIVER (OLIVER)]

That’s not how I took the poll. I thought the question was “if it was decided 
that there was a meeting these would be possible days that work”.

I am wondering if we could make this a regional/virtual meeting. E.g. AT and 
a good number of the other ONAP members have quite elaborate teleconferencing 
rooms in multiple cities. I am wondering if we could meet locally and just use 
those teleconferencing rooms. In my experience this is pretty close to a real 
meeting (much much better then a zoom video meeting if you never have used one 
of those rooms …).

Just a thought.

Considering the tight schedule of the ONAP release I am pretty sure that a 
large fraction of the AT developers would not be able to make a F2F meeting 
in July. So the question in my mind is:  Is it more valuable to have a F2F 
meeting with only a fraction of the key developers present or a virtual meeting 
with everybody?


Oliver

On Jun 12, 2017, at 4:05 PM, Stephen Terrill 
> wrote:

Hi Paul, All,

One part of this poll that we were seeking feedback on was whether the 
developers in the project felt that it was of value to have a meeting in July 
for coordination other project etc – should the interpretation be that those 
who do not feel there is value answer “no” to all dates, and the ones that do 
select the dates that they can attend?

BR,

Steve

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: 12 June 2017 19:09
To: onap-disc...@lists.onap.org; onap-tsc 
>
Subject: [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt

Thank You.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=k6RRZKHW06SCuVKo287vNy6OnTesVvhtAExqgjZ2Jlw=LbYCxJRJjFJ2XOcJG6YgFS5oC7-ee113Exd1q1XY86s=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Face to Face meeting agreements

[Stephen Terrill]

And there was a vEPC (with APP-C) project proposed which I understood had to be 
further matured.

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of SPATSCHECK, OLIVER (OLIVER)
Sent: 12 June 2017 22:35
To: Kenny Paul 
Cc: onap-tsc 
Subject: Re: [onap-tsc] Face to Face meeting agreements


On Jun 12, 2017, at 4:31 PM, Kenny Paul 
> wrote:

All of the use cases were approved.


That’s not correct. The toy use case and the vEPC/voLTE use case were approved. 
The vCPE use case is still being worked with the deadline for all use cases 
being the TSC meeting this Thu.

Oliver
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Face to Face meeting agreements

[Gildas Lanilis]

One note regarding the Use Case.
During the F2F only the VoLTE use case was approved.
The vCPE use case was discussed but as no consensus was closed to be made the 
TSC asked the vCPE Use Case Team to refine the proposal. The vCPE Use Case Team 
has to formalize its new proposal by June 15.

Thanks,
Gildas
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Monday, June 12, 2017 1:32 PM
To: Brian Hedstrom
Cc: onap-tsc
Subject: Re: [onap-tsc] Face to Face meeting agreements

Hello Brian,

I certainly understand your frustration and I’d like to apologize for the 
absence of sufficiently detailed information being captured in the IRC.  There 
were a number of technical, logistical issues across the board and on my part 
specifically, some basic “ramping-up” challenges that impacted the quality note 
taking at thus event.

The recordings of the event along with the timestamps for specific topics can 
be found here: https://wiki.onap.org/display/DW/Presentations

The list of approved projects can be found here:
https://wiki.onap.org/display/DW/Approved+Projects

As far as you list of projects below, ESR and Network Function Change Mgmt were 
discussed and deferred. To the best of my knowledge, the others did not make it 
onto the agenda.

I will be doing some work on the wiki this week as it relates to project data 
that should help out.

All of the use cases were approved.

Please let me know if you have any additional questions.
Thanks for your patience.


Best Regards,
-kenny.

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

On Jun 9, 2017, at 12:06 PM, Brian Hedstrom 
> 
wrote:

In looking at the F2F Day 1 Meeting 
Notes,
 and reviewing the IRC channel for Day 
2
 (it appears the meeting wasn't closed with #endmeeting and a meeting minute 
link wasn't generated), I'm finding it difficult to see what motions were voted 
on and approved versus voted down. There is missing/incomplete information in 
those notes.

Will there be a report or wiki page created that captures what motions passed 
at the F2F meeting?

I could not find any details on whether these projects were voted on:

  *   Authentication and Authorization Framework
  *   DMaaP
  *   External System Register
  *   Network Function Change Management
  *   ONAP Extensibility
  *   ONAP University
  *   Open Lab
  *   SNIRO Optimization Framework
  *   VNF Validation Program (ONAP ICE)
  *   Common Frameworks
Also, I only found that VoLTE Use Case was approved, were the other use cases 
approved?


Thanks,

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

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Face to Face meeting agreements

[SPATSCHECK, OLIVER (OLIVER)]

On Jun 12, 2017, at 4:31 PM, Kenny Paul 
> wrote:

All of the use cases were approved.


That’s not correct. The toy use case and the vEPC/voLTE use case were approved. 
The vCPE use case is still being worked with the deadline for all use cases 
being the TSC meeting this Thu.

Oliver
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Network Function Change Management Project Proposal

[Stephen Terrill]

Hi Oliver,

I think that we are at a stage where we are setting a precedent with this type 
of problem, so we may try one approach and decide it was or was not a good 
idea.  Yes, I would suggest the use case approach for this for release 2, where 
the output of the use case work is an understanding of the needs expressed on 
different projects.

BR,

Steve

-Original Message-
From: SPATSCHECK, OLIVER (OLIVER) [mailto:spat...@research.att.com] 
Sent: 12 June 2017 17:00
To: Stephen Terrill 
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Network Function Change Management Project Proposal


Steve,

I think the actual code would be contributions to various other projects e.g. 
CMO needs workflows but I would think those would be additional features in SO 
not a separate orchestrator for CMO. So the CMO team members would likely also 
become contributors in other projects but we wouldn’t need a separate code base.

So I think what you are recommending is to work this as a use case for release 
2 ?

Oliver

> On Jun 10, 2017, at 8:07 AM  EDT, Stephen Terrill 
>  wrote:
> 
> Hi Oliver,
> 
> It might depend a little on the expected final intention. Is the final 
> expectation that there will be a new module required (I thought I'd heard 
> something about that could be the case), or whether it is expected that this 
> functionality is something that would be realised solely through additional 
> to the code produced by existing/already proposed projects?
> 
> If the former we could go and setup a project, if the latter is be leaning 
> towards use cases. 
> 
> We now need to keep in mind that the projects we start now don't have to be 
> aimed for the first release, but if there is a group interested and it 
> eventually plans to have a result I don't see why it couldn't start now if we 
> are clear on what it is to do. 
> 
> BR,
> 
> Steve
> 
> BR,
> 
> Steve. 
> 
> Sent from my Phone
> 
>> On 9 Jun 2017, at 11:23, SPATSCHECK, OLIVER (OLIVER) 
>>  wrote:
>> 
>> 
>> During the F2F meeting we discussed a project proposal on the topic. As this 
>> addresses workflows across components rather then build a component the 
>> question came up what form this should take. 4 options are proposed
>> 
>> 1. Make it a project and add a clear deliverable (e.g. Documentation) to the 
>> project proposal.
>> 2. Make this work part of the architecture subcommittee.
>> 3. Have a coordinator on this
>> 4. Make this a use case for r2
>> 
>> In my mind I don't like #2. as it removes the clear focus of this work.
>> 
>> The suggestion was made to ask the TSC on the mailing list for opinions.
>> 
>> So please advice.
>> 
>> Oliver
>> ___
>> ONAP-TSC mailing list
>> ONAP-TSC@lists.onap.org
>> https://lists.onap.org/mailman/listinfo/onap-tsc

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting

[Stephen Terrill]

Hi Paul, All,

One part of this poll that we were seeking feedback on was whether the 
developers in the project felt that it was of value to have a meeting in July 
for coordination other project etc - should the interpretation be that those 
who do not feel there is value answer "no" to all dates, and the ones that do 
select the dates that they can attend?

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: 12 June 2017 19:09
To: onap-disc...@lists.onap.org; onap-tsc 
Subject: [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt

Thank You.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] ONAP Release Naming Framework Election Has Concluded - Global Cities Wins

[HU, BIN]

Note sure how “Amsterdam” was there.

For the official record 
https://lists.onap.org/pipermail/onap-tsc/2017-May/000598.html, the original 
proposal was “Anchorage”.

I didn’t see any other proposal on the public mailing list.

The same holds true for “Casablanca”, “Fiji”, “Guiling” , “Juarez” and “Kyoto”. 
All of those have official public record in mailing list. Others don’t.

Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Monday, June 12, 2017 11:40 AM
To: Lisa Caywood ; Phil Robb 

Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [onap-discuss] [onap-tsc] ONAP Release Naming Framework Election 
Has Concluded - Global Cities Wins

Hi Lisa,

I understand the concerns you brought up. However, we need your immediate 
recommendations regarding the naming of our first release “Anchorage” or 
“Amsterdam”.
This is critical as we are using these names while discussing Release plan and 
in our tool chain.

[cid:image001.jpg@01D2E374.CFF977B0]

Thanks,
Gildas

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

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lisa Caywood
Sent: Wednesday, June 07, 2017 10:20 AM
To: Phil Robb
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: Re: [onap-tsc] ONAP Release Naming Framework Election Has Concluded - 
Global Cities Wins

For the record, Marketing had two concerns with Cities:

1) OpenStack also uses some cities, so we would need to ensure that our names 
do not overlap with theirs.

2) Visual elements (for launch banners and other branding assets) - many cities 
look like other big cities. We would want to ensure that each city picked has a 
widely recognized landmark to anchor on.

Obviously both of these are very manageable, just things to be aware of.

Regards, Lisa

On Wed, Jun 7, 2017 at 3:17 AM, Phil Robb 
> wrote:
Hello All:

The Release Naming Framework election has concluded and the winner is "Global 
Cities".
Result detailsHide details




1

2

3

4

5

1. Global Cities



-

106

117

130

147

2. Scientists



99

-

111

131

132

3. Music Composers



87

82

-

108

131

4. Philosophers



74

51

81

-

116

5. Zodiac Signs



55

62

63

73

-


Before we make it official, we need to run the idea by the Marketing Folks to 
make sure they have no issues with it.

I'll keep you posted.

Thanks to all of those folks that voted.  We had 210 votes all told.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc



--
Lisa Caywood
Director of Ecosystem Development | OpenDaylight Project | 
lcayw...@opendaylight.org | +1 408 857 3642
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting

[Kenny Paul]

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt 


Thank You.

Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Call for feedback about interaction with External Register System

[FREEMAN, BRIAN D]

This table is confusing since it is using the term SDN-C for both the ONAP SDNC 
and VIM sdn local controllers.
Its not clear to me that the sdn controllers are valid ESR end points since in 
fact we could be using BGP and non-rest api interfaces for some of the 
communication between controllers depending on the network function being used.

When the network function is associated with non-real time provisioning we also 
likely would not have a direct SDNC to local controller interface but rather 
use the HEAT /ARM template interfaces to communicate the information needed to 
the local controller on required networking (OS::Neutron for instance in HEAT)

Brian


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of li.z...@zte.com.cn
Sent: Sunday, June 11, 2017 10:11 PM
To: AGGARWAL, MANISHA ; KLEIN, REUBEN ; 
BURNS, COLIN ; l...@vmware.com; TIMONEY, DAN 
; parviz.yeg...@huawei.com; dewa...@gigaspaces.com; 
saw@huawei.com; SMOKOWSKI, STEVEN ; 
denglin...@chinamobile.com; dsha...@interwise.com; eden.ro...@att.com; 
zahi.kapel...@att.com; HEMLI, AMICHAI ; WEST, EARLE 

Cc: onap-tsc@lists.onap.org
Subject: [onap-tsc] Call for feedback about interaction with External Register 
System


Hi There,



After discussion about the ESR in the subgroup in the F2F meeting in Beijin. We 
got a consquence that ESR is necessary. But since we do not clear about the 
business detail of other projects, such as VID/Multi-VIM/VF-C/SO/SDN-C etc. So 
we may do not clear that which projects will interact with ESR or whether the 
project has seed code of the function which ESR supplies. This is why I am 
reaching out.



Here, I would like to emphasize about the scope of ESR again, and do some 
clarification about some points.

  1.  ESR will supplies both portal and API to 
manage(register/query/delete/update) the external system,  but will not deploy 
the external system. (Here external system means that the systems already 
exsist somewhere, but not included in ONAP, such as VIM/VNFM/EMS/vendor SDN 
controller)
  2.  ESR will check whether the external systems are reachable, but will not 
do the fault analysis.

For the project description and the scope of ESR, you may visit 
https://wiki.onap.org/pages/viewpage.action?pageId=5734948


The sequence diagram bellow shows what we think about the interaction between 
ESR and other components in high level. But we still need to confirm it with 
VID/A/Multi-VIM/SO/VF-C/APP-C/SDN-C team in the detail business scenario.

[cid:image001.png@01D2E36B.CB0E17F0]



Here I listed a table about the ONAP project and its related external systems 
(if I am wrong please correct me).



Project


Related external system


 Will interact with ESR(Yes/No)


VID


VIM/VNFM/EMS/SDNC

Yes


Multi-VIM


VIM

Yes


SDN-C


Vendor SDN controller

Yes


VF-C


VIM/VNFM/EMS/SDNC

Yes


SO


VIM/VNFM/EMS/SDNC

Yes


APP-C


EMS

Yes




Briefly, according to the comments about ESR in the F2F meeting in Beijin. I 
need you guys give a feedback about whether your components will interact with 
ESR about the external systems OR how the function of ESR is realized in your 
component( if you do have the function of ESR).



Thanks a lot.

LiZi











李滋 lizi



IT开发工程师 IT Development Engineer
网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central 
R＆D Institute/System Product


[cid:image002.gif@01D2E36B.CB0E17F0]

[cid:image003.gif@01D2E36B.CB0E17F0]
成都市高新区天府大道中段800号中兴通大厦
ZTE Corporation Building, No. 800 Middle Section Tianfu Avenue,
Chengdu, P..R.China, 610041
M: +86 15583405168
E: li.z...@zte.com.cn
www.zte.com.cn


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Network Function Change Management Project Proposal

[SPATSCHECK, OLIVER (OLIVER)]

Steve,

I think the actual code would be contributions to various other projects e.g. 
CMO needs workflows but I would think those would be additional features in SO 
not a separate orchestrator for CMO. So the CMO team members would likely also 
become contributors in other projects but we wouldn’t need a separate code base.

So I think what you are recommending is to work this as a use case for release 
2 ?

Oliver

> On Jun 10, 2017, at 8:07 AM  EDT, Stephen Terrill 
>  wrote:
> 
> Hi Oliver,
> 
> It might depend a little on the expected final intention. Is the final 
> expectation that there will be a new module required (I thought I'd heard 
> something about that could be the case), or whether it is expected that this 
> functionality is something that would be realised solely through additional 
> to the code produced by existing/already proposed projects?
> 
> If the former we could go and setup a project, if the latter is be leaning 
> towards use cases. 
> 
> We now need to keep in mind that the projects we start now don't have to be 
> aimed for the first release, but if there is a group interested and it 
> eventually plans to have a result I don't see why it couldn't start now if we 
> are clear on what it is to do. 
> 
> BR,
> 
> Steve
> 
> BR,
> 
> Steve. 
> 
> Sent from my Phone
> 
>> On 9 Jun 2017, at 11:23, SPATSCHECK, OLIVER (OLIVER) 
>>  wrote:
>> 
>> 
>> During the F2F meeting we discussed a project proposal on the topic. As this 
>> addresses workflows across components rather then build a component the 
>> question came up what form this should take. 4 options are proposed
>> 
>> 1. Make it a project and add a clear deliverable (e.g. Documentation) to the 
>> project proposal.
>> 2. Make this work part of the architecture subcommittee.
>> 3. Have a coordinator on this
>> 4. Make this a use case for r2
>> 
>> In my mind I don't like #2. as it removes the clear focus of this work.
>> 
>> The suggestion was made to ask the TSC on the mailing list for opinions.
>> 
>> So please advice.
>> 
>> Oliver
>> ___
>> ONAP-TSC mailing list
>> ONAP-TSC@lists.onap.org
>> https://lists.onap.org/mailman/listinfo/onap-tsc

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Final Preparation For ONAP Project Creation Reviews For June 8th and 9th

[Kenny Paul]

The zoom recordings and index have been posted to https://wiki.onap.org/display/DW/Presentations
Best Regards, -kennyKenny Paul,  Technical Program Managerkp...@linuxfoundation.org510.766.5945


On Jun 8, 2017, at 6:55 PM, Kenny Paul  wrote:Yes, I will get these posted on Friday.
Best Regards, -kennyKenny Paul,  Technical Program Managerkp...@linuxfoundation.org510.766.5945


On Jun 8, 2017, at 6:18 AM, PLATANIA, MARCO (MARCO)  wrote:Thanks, Kenny. Could you please share the link when ready? Thanks,Marco From: Kenny Paul Date: Thursday, June 8, 2017 at 5:38 AMTo: "PLATANIA, MARCO (MARCO)" Cc: Phil Robb , onap-tsc , "onap-disc...@lists.onap.org" Subject: Re: [onap-tsc] Final Preparation For ONAP Project Creation Reviews For June 8th and 9th Hello Marco,  We are recording audio which will be posted, with the caveat that there have been a number of sound quality issues with today’s session. Best Regards, -kennyKenny Paul,  Technical Program Managerkp...@linuxfoundation.org510.766.5945 On Jun 7, 2017, at 5:12 PM, PLATANIA, MARCO (MARCO)  wrote: Phil, Will the video recordings of the F2F sessions (especially those on the proposed projects) available to those that cannot attend in person? Thanks,Marco From:  on behalf of Phil Robb Date: Wednesday, June 7, 2017 at 1:34 AMTo: onap-tsc , "onap-disc...@lists.onap.org" Subject: [onap-tsc] Final Preparation For ONAP Project Creation Reviews For June 8th and 9th Hello ONAP Developer Community: I am looking very forward to seeing many of you tomorrow at our second Face to Face meeting hosted by China Mobile in Beijing. We will be attempting to get through as many Project Creation Reviews as possible during this two day event.  Given that we have around 30 project proposals and only about 6.5 hours allotted for the reviews we are going to need to be very efficient with our time. We have created a wiki page to break-down the Creation Review time slots into 15 minute intervals.  It is located here:https://wiki.onap.org/pages/viewpage.action?pageId=6590432 If you are a "Project Contact" for an ONAP project, and you want your project to be reviewed during Face to Face meeting, please find an empty time slot on that wiki page and enter your information there.** Please remember to have reviewed the "Initial Project Proposal Feedback From The TSC" page and ensure that the questions/comments raised there have been addressed in your project proposal.https://wiki.onap.org/display/DW/Initial+Project+Proposal+Feedback+From+the+TSC For ONAP TSC members, please re-review both the Project Feedback page, and the Project Proposal page for each project to be reviewed in preparation of the Creation Reviews.  If you have any questions, please do not hesitate to contact me. Best,. Phil.-- Phil RobbExecutive Director, OpenDaylight ProjectVP Operations - Networking & Orchestration, The Linux Foundation(O) 970-229-5949(M) 970-420-4292Skype: Phil.Robb___ONAP-TSC mailing listONAP-TSC@lists.onap.orghttps://lists.onap.org/mailman/listinfo/onap-tsc ___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Call for feedback about interaction with External Register System

[li.zi30]

Hi There,





After discussion about the ESR in the subgroup in the F2F meeting in Beijin. We 
got a consquence that ESR is necessary. But since we do not clear about the 
business detail of other projects, such as VID/Multi-VIM/VF-C/SO/SDN-C etc. So 
we may do not clear that which projects will interact with ESR or whether the 
project has seed code of the function which ESR supplies. This is why I am 
reaching out.





Here, I would like to emphasize about the scope of ESR again, and do some 
clarification about some points. 


ESR will supplies both portal and API to manage(register/query/delete/update) 
the external system,  but will not deploy the external system. (Here external 
system means that the systems already exsist somewhere, but not included in 
ONAP, such as VIM/VNFM/EMS/vendor SDN controller)


ESR will check whether the external systems are reachable, but will not do the 
fault analysis.


For the project description and the scope of ESR, you may visit 
https://wiki.onap.org/pages/viewpage.action?pageId=5734948 


The sequence diagram bellow shows what we think about the interaction between 
ESR and other components in high level. But we still need to confirm it with 
VID/A/Multi-VIM/SO/VF-C/APP-C/SDN-C team in the detail business scenario.








Here I listed a table about the ONAP project and its related external systems 
(if I am wrong please correct me). 









Project


Related external system


 Will interact with ESR(Yes/No)


VID


VIM/VNFM/EMS/SDNC

Yes
Multi-VIM


VIM

Yes
SDN-C


Vendor SDN controller

Yes
VF-C


VIM/VNFM/EMS/SDNC

Yes
SO


VIM/VNFM/EMS/SDNC

Yes
APP-C


EMS

Yes






Briefly, according to the comments about ESR in the F2F meeting in Beijin. I 
need you guys give a feedback about whether your components will interact with 
ESR about the external systems OR how the function of ESR is realized in your 
component( if you do have the function of ESR). 





Thanks a lot.


LiZi




















李滋 lizi






IT开发工程师 IT Development Engineer
网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central 
R＆D Institute/System Product









成都市高新区天府大道中段800号中兴通大厦
ZTE Corporation Building, No. 800 Middle Section Tianfu Avenue, 
Chengdu, P..R.China, 610041 
M: +86 15583405168 
E: li.z...@zte.com.cn 
www.zte.com.cn___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Call for feedback about interaction with External Register System

[li.zi30]

Hi There,





After discussion about the ESR in the subgroup in the F2F meeting in Beijin. We 
got a consquence that ESR is necessary. But since we do not clear about the 
business detail of other projects, such as VID/Multi-VIM/VF-C/SO/SDN-C etc. So 
we may do not clear that which projects will interact with ESR or whether the 
project has seed code of the function which ESR supplies. This is why I am 
reaching out.





Here, I would like to emphasize about the scope of ESR again, and do some 
clarification about some points. 


ESR will supplies both portal and API to manage(register/query/delete/update) 
the external system,  but will not deploy the external system. (Here external 
system means that the systems already exsist somewhere, but not included in 
ONAP, such as VIM/VNFM/EMS/vendor SDN controller)


ESR will check whether the external systems are reachable, but will not do the 
fault analysis.


For the project description and the scope of ESR, you may visit 
https://wiki.onap.org/pages/viewpage.action?pageId=5734948 


The sequence diagram bellow shows what we think about the interaction between 
ESR and other components in high level. But we still need to confirm it with 
VID/A/Multi-VIM/SO/VF-C/APP-C/SDN-C team in the detail business scenario.








Here I listed a table about the ONAP project and its related external systems 
(if I am wrong please correct me). 









Project


Related external system


 Will interact with ESR(Yes/No)


VID


VIM/VNFM/EMS/SDNC

Yes
Multi-VIM


VIM

Yes
SDN-C


Vendor SDN controller

Yes
VF-C


VIM/VNFM/EMS/SDNC

Yes
SO


VIM/VNFM/EMS/SDNC

Yes
APP-C


EMS

Yes






Briefly, according to the comments about ESR in the F2F meeting in Beijin. I 
need you guys give a feedback about whether your components will interact with 
ESR about the external systems OR how the function of ESR is realized in your 
component( if you do have the function of ESR). 





Thanks a lot.


LiZi




















李滋 lizi






IT开发工程师 IT Development
Engineer
网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central 
R＆D Institute/System Product









成都市高新区天府大道中段800号中兴通大厦
ZTE
Corporation Building, No. 800 Middle Section Tianfu Avenue, 
Chengdu, P..R.China, 610041 
M: +86 15583405168 
E: li.z...@zte.com.cn 
www.zte.com.cn___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Scheduling weekly meeting for DCAE

[JI, LUSHENG (LUSHENG)]

Hello Casey,

DCAE would like to schedule a weekly meeting for every Thursday 9:AM-10:00AM 
EDT, or 9PM-10PM Beijing Time, 6-7 PDT, etc.  Recurring starting from this 
week.  Could you please help adding the meeting on the community calendar?

Also we would like to request to use an ONAP shared Zoom account for hosting 
the call.  Could you please coordinate and let me know the details?

Thank you very much,

Lusheng Ji
ONAP DCAE
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Request - Call for interest ONAP Vulnerability sub-committee

[Stephen Terrill]

Hi,

In the last developer face to face event, we approved the vulnerability 
management procedures 
(https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management).  The purpose 
of this is to manage the reception  of a vulnerability until fix and 
communication.  Note, this is separate from the security team which will now 
focus on looking into more proactive activities around security for ONAP.

This will be a small team of 3-5 people (as it will work under embargo) to work 
with the projects to fix received notifications of vulnerabilities.  It will 
need a mix of people who know and are passionate about security, as well as 
people who know the code base and/or will be able to work with others to solve 
the vulnerabilities.

I am looking for people to help with working in this team, so if you are 
passionate about fixing vulnerabilities and security, have a good understanding 
of our code base(s) and the project leaders and/or have a good knowledge of 
security vulnerabilities, and can dedicate time for this activity - I would 
love to hear from you and your background.  With this email I am soliciting 
support for this with the idea of making a selection to propose to the TSC (the 
TSC should decide).  Responses before the close of Monday 19th July would be 
highly appreciated.

Note: emails directly to me appreciated, no need to broadcast to the entire 
list.

Best Regards,

Steve.


[Ericsson]

STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[http://www.ericsson.com/current_campaign]

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Weekly security coordinator report

[Stephen Terrill]

Regarding "If you are an ONAP coordinator, I would appreciate it if you could 
send out a progress report every week.".  Fully agree -  this is the 
expectation as per our charter, an email report to the TSC list as per the 
reporting frequency defined in the sub-committee definition.

BR,

Steve

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: 12 June 2017 04:46
To: Stephen Terrill 
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Weekly security coordinator report

Thanks Steve.

ONAP Coordinators,

If you are an ONAP coordinator, I would appreciate it if you could send out a 
progress report every week.

Mazin





On Jun 10, 2017, at 8:06 AM, Stephen Terrill 
> wrote:


Hi,

A little late, but here is the security coordinator report.

We have had  the vulnerability procedures approved by the TSC.  Now we are 
looking more into more proactive actions and have received a presentation 
regarding the cii badging program which we will now look at in more detail, and 
likely come with a proposal in this area to the TSC.

Best regards,

Steve.

Sent from my Phone___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc