from:"denghui \(L\)"

Re: [onap-tsc] [onap-discuss] 答复：Re: Modelling discussion on Friday May 5th

2017-05-01 Thread denghui (L)

Brian

This is well said here, what we are proposing is what you are suggesting here, 
to align with multiple data modelling based ETSI NFV UML information modeling,
That is also all about opendeployment doing today.

Thanks

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Brian Hedstrom
Sent: Tuesday, April 25, 2017 12:41 AM
To: zhao.huabing 
Cc: JANA, RITTWIK (RITTWIK) ; onap-discuss 
; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] 答复：Re: Modelling discussion on Friday 
May 5th

The way to put all these different data models under a single umbrella is to 
create a UML<https://en.wikipedia.org/wiki/Unified_Modeling_Language> 
Information Model using Eclipse/Papyrus (as an open source tool).
Unified Modeling Language (UML) is a standard syntax for describing the 
architectural design of a system

  *   Object Management Group (OMG) & ISO standard
  *   Originated from object-oriented software development methods
UML includes many diagrams types to graphically represent parts of a system’s 
model, including

  *   Structural Views: The static nature of the system using objects, 
attributes and relationships (e.g., information or components that must be 
present in the system). This includes class diagrams and component diagrams.
  *   Behavioral: The dynamic nature of the system through collaboration of 
objects and state changes (e.g., activities performed by the system). This 
includes use case diagrams, sequence diagrams, state machines.
UML is protocol agnostic and therefore these "Information Models" are protocol 
agnostic.

UML models can then be transformed into protocol specific data models such as 
YANG, XML, SMIv2, etc.

Creating a UML Information Model allows data cohesion across the various 
interfaces in the system.  Using Interface 
Realizations<http://www.uml-diagrams.org/realization.html>, specific interfaces 
can be modeled.  In fact, an interface Information Model could be transformed 
into multiple data models to support multiple management protocols.

Therefore, the focus first is on building a UML Information Model, then once 
that's approved by the organization, then data models and encodings can be 
generated based on the chosen interface protocols.

Thanks,
Brian

On Sun, Apr 23, 2017 at 5:13 AM, 
mailto:zhao.huab...@zte.com.cn>> wrote:
Hi Brijesh,

You brought up a great topic, we may need to converge at the same aspect, but 
for different aspects, there are different modelling languages which can better 
meet the specific requirement of that aspect, and they are very complementary.

For example, TOSCA(Heat is another, come with openstack) is a good choice for 
the topology modelling of cloud application , YANG can be used for the 
configuration model( normally using for L2 L3, can be used for L4-L7 as well), 
and BPMN is good at workflow orchestration.

It's difficult to put all these different modelling capabilities in a single 
data model or using an unique DSL, and we don't need to. But It's possible to 
make them work together smoothly under a unified umbrella system to accomplish 
the automated close loop and I'm glad to see ONAP has already make a very good 
start at that job.

Thanks,
Huabing
原始邮件
发件人: BrijeshKhandelwal;
收件人:GILBERT, MAZIN E (MAZIN E); denghui (L); JANA,RITTWIK (RITTWIK); 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>;
日期: 2017-04-22 11:56:56
主题:Re: [onap-discuss] [onap-tsc] Modelling discussion on Friday May 5th
Greetings,

Adding some thoughts on information model:
Orchestration need to interoperate among different interfaces, which in turn 
need to deal with very different payloads in form of YAML, YANG, JSON  etc. 
There will be lots of data processing among these models to process complete 
service. Handling these templates in orchestrator will impose limitations on 
capability and performance of orchestrator.
So, there should have standardized data model for smooth processing among 
orchestration steps.

Probably first time, orchestration is composing 3 different worlds of Network, 
Infra, IT, with different tunes of YANG, YAML, JSON/XML.
Is there a play to develop standardized data models for orchestration, which 
will meet needs of each area? Is TOSCA sufficient? Or need some extended JSON 
data models?


-Brijesh

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>]
 On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: Thursday, April 20, 2017 8:30 AM
To: denghui (L); JANA, RITTWIK (RITTWIK)
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Modelling discussion on Friday May 5th

Rittwik, Deng,

This is grea

[onap-tsc] ONAP Architecture Overview Slides

2017-04-12 Thread denghui (L)

Could we get other slides from mini summit?

Thanks

DENG Hui

From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Wednesday, April 12, 2017 4:34 PM
To: onap-tsc at lists.onap.org
Cc: 'BEGWANI, VIMAL'
Subject: [onap-tsc] ONAP Architecture Overview Slides

Hi all,

Attached are the slides used in the Architecture Overview presentation last 
Thursday.
Only one minor correction is made from VNF-C to VF-C on Page 6, in accordance 
to ONAP Charter.
It is intended to serve as a starting point for our next level architecture 
discussion.

Please kindly share with us your comments and suggestions.

Thanks,
Vimal & Lingli
-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] ONAP Architecture Overview Slides

2017-04-13 Thread denghui (L)

Thank you, Lingli,

It really helps a lot

DENG Hui



From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Thursday, April 13, 2017 9:37 AM
To: denghui (L); onap-tsc at lists.onap.org
Cc: 'BEGWANI, VIMAL'
Subject: RE: [onap-tsc] ONAP Architecture Overview Slides

Hi guys,

We managed to add a link for the ONAP at ONS2017 activities to the ONAP wiki, 
and uploaded all the slides from my side there.
Please refer to: https://wiki.onap.org/display/DW/ONAP at ONS2017
Would encourage other presenters/panelists consider uploading and sharing there 
too.

Thanks,
Lingli

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: 2017?4?12? 16:38
To: Lingli Deng mailto:denglingli at 
chinamobile.com>>; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>
Cc: 'BEGWANI, VIMAL' mailto:vb1946 at att.com>>
Subject: RE: [onap-tsc] ONAP Architecture Overview Slides

Could we get other slides from mini summit?

Thanks

DENG Hui

From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at 
lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli 
Deng
Sent: Wednesday, April 12, 2017 4:34 PM
To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>
Cc: 'BEGWANI, VIMAL'
Subject: [onap-tsc] ONAP Architecture Overview Slides

Hi all,

Attached are the slides used in the Architecture Overview presentation last 
Thursday.
Only one minor correction is made from VNF-C to VF-C on Page 6, in accordance 
to ONAP Charter.
It is intended to serve as a starting point for our next level architecture 
discussion.

Please kindly share with us your comments and suggestions.

Thanks,
Vimal & Lingli
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170413/8a4cac01/attachment-0001.html>

[onap-tsc] More complex OPEN ECOMP demo

2017-04-14 Thread denghui (L)

Hi Brian,



After last week?s ONAP TSC meeting, we discussed extending the OpenECOMP demo 
to more fully demonstrate the functionality of the code you are contributing.  
You asked what we would find useful.  After discussing it with our team, we 
would like to request that your kind help to extend the current use case to 
exercise all 8 OpenECOMP modules. It would be helpful if the demo would show 
both the creation of the overlay network and instantiation of the VNF ? 
ideally, across multiple data centers (although one is OK if multi-DC is too 
challenging), and using more than one VNF (see below).



[cid:image001.png at 01D2B475.FB7B2290]



Specifically, we?d like to see how you:

1.  Use ASDC to create all the TOSCA models and all the artifacts for the 
Use Case VNF

2.  Demonstrate how the BPEL recipe was created and distributed

3.  Show how the DG graph(s) for the Use Case is created and response for 
what

4.  Create all the config filles and artifacts for Data Collection, 
Analytics and policy rules

5.  Upload the DG, network topology files,  Service topology files, YANG 
model,  DG DCAE and policy files  to ASDC

6.  Distribute the all the above files and artifacts using ASDC to all the 
OpenECOMP components

7.  Show how SDN-C creates/configures the network

a. overlay (e.g., VXLAN, etc.)

b. underlay

8.  Show how the APP-C for the Use Case is created

a. For more than one VNF

9.  Show how the APP-C package is added to the Service catalog and how it I 
made available to the VID

10.   Use VID to invoke the Use Case APP-C

11.   Show how the Use Case VNF get orchestrated by doing the following:

a. Update A&AI with the available resources

b. Trigger MSO to execute the BPEL recipe

c. Trigger SDN-C to create all the required network by executing the DG

d. Update content in A&AI

e. Create and Execute the HEAT template

f.  Verify that all the resources were inventoried successfully

12.   Verify Data collection

13.   Verify the analytics/policy

14.   Demonstrate autoscaling and redundancy

15.   Last but not least, execute the stop service command which should cleanly 
stop the VNF and reclaim all the resources including IP addresses and VMs and 
storage.



If you can?t demonstrate all of these areas in the short-term, would you please 
clarify which ones you could?

For example, if OpenECOMP can?t establish the underlay, would you please call 
that out, and we can set it up manually before we run the demo.

Thanks again for your kind help

Best regards,



Deng Hui



-Original Message-
From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Friday, April 07, 2017 4:35 AM
To: Alexis de Talhou?t; onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] Upgrade from ODL Beryllium to Boron



Alexis,



What would be the best mechanism to communicate this type of thing ? As we push 
our Feb and June 2017 code updates into ONAP repositories there will be more 
version changes of external open source ?





Would a notice on this list be enough or should there be another tool/process 
used ?



We are open to what would be better for the community ?



Brian





-Original Message-

From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
Alexis de Talhou?t

Sent: Thursday, April 06, 2017 3:49 PM

To: onap-discuss at lists.onap.org

Subject: [onap-discuss] Upgrade from ODL Beryllium to Boron



Hello guys,



I?ve seen that recently you?ve upgraded ODL?s version.



APPC

https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Da41533fb0a79e7399f7bf0ba53a1211c67e50d04&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=yqEiYEqq3lumI3bdXWz4Rxa5GynG3EX_2qUzZvFrOvo&e=

https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Dda976a9c10cca4249e97f6629eb17cd52a7e4955&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=0xrdhJsf90kPIdSWhe-l0tULo2Ve3nyPyNnuVInmDRM&e=

SDNC

https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2905_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=vxs3n-9zqJjaSFCFICdqvEm505UT6YK3cOTbvS0bIvY&e=

https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2907_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=4p__SxAqsG_N6wlgXGfZdFX-A-DyYyBMymL6SqHJeXY&e=
  (plugins) 
https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2901_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_

[onap-tsc] Modelling discussion on Friday

2017-04-20 Thread denghui (L)

Hello all

We are happy to let you know that we are hosting a modeling session on Friday
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT&T Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] Modelling discussion on Friday May 5th

2017-04-20 Thread denghui (L)

Hello all

We are happy to let you know that we are hosting a modeling session on Friday, 
May 5th, AT&T Lab.
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT&T Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] Modelling discussion on Friday May 5th

2017-04-25 Thread denghui (L)

Thinh

Modelling discussion will cover large scope of ONAP beyond VNFD/SD, you are 
welcome to join.

Thanks

DENG Hui

From: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyen...@nokia.com]
Sent: Friday, April 21, 2017 1:29 AM
To: denghui (L); onap-tsc at lists.onap.org; onap-discuss at lists.onap.org
Cc: JANA, RITTWIK (RITTWIK)
Subject: RE: Modelling discussion on Friday May 5th

Hi Rittwik and DENG,

Is modeling discussion covering network service and VNF descriptors? Or it is 
broader to cover all of the ONAP functions?

Yes, I am planning to attend.

Thinh

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
denghui (L)
Sent: Thursday, April 20, 2017 3:35 AM
To: denghui (L) mailto:denghui12 at huawei.com>>; 
onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; onap-discuss at 
lists.onap.org<mailto:onap-discuss at lists.onap.org>
Cc: JANA, RITTWIK (RITTWIK) mailto:rjana at 
research.att.com>>
Subject: [onap-discuss] Modelling discussion on Friday May 5th

Hello all

We are happy to let you know that we are hosting a modeling session on Friday, 
May 5th, AT&T Lab.
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT&T Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170425/3ae6e2bd/attachment.html>

[onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th

2017-04-25 Thread denghui (L)

Danny

Thanks for your suggestions, TSC will arrange the agenda of those days, we try 
our best to discuss it on Friday.
You are more than welcome to join us.

Thanks

DENG Hui

From: Danny Lin [mailto:l...@vmware.com]
Sent: Friday, April 21, 2017 1:38 AM
To: denghui (L); onap-tsc at lists.onap.org; onap-discuss at lists.onap.org; 
JANA, RITTWIK (RITTWIK)
Subject: Re: [onap-discuss] Modelling discussion on Friday May 5th

Hui and Rittwik,

If possible, can we see these topics can be spread out through Tuesday to 
Thursday? That might provide opportunity for broader participation as some 
might leave on Friday.

I plan to attend on Friday.

Danny

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
denghui (L)
Sent: Thursday, April 20, 2017 3:35 AM
To: denghui (L) mailto:denghui12 at huawei.com>>; 
onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; onap-discuss at 
lists.onap.org<mailto:onap-discuss at lists.onap.org>
Cc: JANA, RITTWIK (RITTWIK) mailto:rjana at 
research.att.com>>
Subject: [onap-discuss] Modelling discussion on Friday May 5th

Hello all

We are happy to let you know that we are hosting a modeling session on Friday, 
May 5th, AT&T Lab.
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT&T Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170425/1755662f/attachment.html>

[onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th

2017-04-26 Thread denghui (L)

Thanks Amir for your recommendation,

I read through OPEN-O mailing list, they were discussing which training 
material is best,
https://lists.open-o.org/pipermail/openo-tsc/2017-April/002063.html

from their discussion, OASIS Tosca NFV editor recommend below link from oasis 
official website.
https://www.oasis-open.org/committees/document.php?document_id=60354&wg_abbrev=tosca

Best regards,

DENG Hui

From: Amir Levy [mailto:a...@gigaspaces.com]
Sent: Friday, April 21, 2017 4:52 AM
To: denghui (L)
Cc: onap-tsc at lists.onap.org; Nguyenphu, Thinh (Nokia - US/Irving); 
onap-discuss at lists.onap.org; JANA, RITTWIK (RITTWIK); Michael Brenner; Nati 
Shalom
Subject: Re: [onap-discuss] Modelling discussion on Friday May 5th

Thanks DENG for leading this initiative.

I would love to share few quick links to prepare for this meeting:

We have a two parts video that provides TOSCA in practice training : Part 1: 
https://www.youtube.com/watch?v=aMkqLI6o-58 and  
https://www.youtube.com/watch?v=6xGmpi--7-A

And Michael Brenner for ETSI/NFV and TOSCA has recently drafted a in-depth 
comparison between model-driven and task-driven workflows: 
http://getcloudify.org/brochures/tosca-workflows-Apr-2017.pdf

? amir

amir at gigaspaces.com<mailto:amir at gigaspaces.com> +1 408 916 8572

On Apr 20, 2017, at 10:29 AM, Nguyenphu, Thinh (Nokia - US/Irving) 
mailto:thinh.nguyenphu at nokia.com>> wrote:

Hi Rittwik and DENG,

Is modeling discussion covering network service and VNF descriptors? Or it is 
broader to cover all of the ONAP functions?

Yes, I am planning to attend.

Thinh

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
denghui (L)
Sent: Thursday, April 20, 2017 3:35 AM
To: denghui (L) mailto:denghui12 at huawei.com>>; 
onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; onap-discuss at 
lists.onap.org<mailto:onap-discuss at lists.onap.org>
Cc: JANA, RITTWIK (RITTWIK) mailto:rjana at 
research.att.com>>
Subject: [onap-discuss] Modelling discussion on Friday May 5th

Hello all

We are happy to let you know that we are hosting a modeling session on Friday, 
May 5th, AT&T Lab.
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT&T Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
___
onap-discuss mailing list
onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170426/c29495e4/attachment-0001.html>

[onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th

2017-04-26 Thread denghui (L)

Hi Michael,

Thanks for your suggestion, workflow is already covered in the Shitao?s 
session, they will discuss

1)   OPENCOMP Workflow

2)   OPEN-O Workflow.

Best regards,

DENG Hui

From: Michael Brenner [mailto:mich...@gigaspaces.com]
Sent: Friday, April 21, 2017 7:14 AM
To: Amir Levy
Cc: JANA, RITTWIK (RITTWIK); Nguyenphu, Thinh (Nokia - US/Irving); denghui (L); 
onap-discuss at lists.onap.org; Nati Shalom; onap-tsc at lists.onap.org
Subject: Re: [onap-discuss] Modelling discussion on Friday May 5th


I'll be happy to attend and take part in the discussion and would like to 
suggest to add workflows to the agenda ...a topic which I offer to moderate.
Best regards,
Michael
On Apr 20, 2017 4:51 PM, "Amir Levy" mailto:amir at 
gigaspaces.com>> wrote:
Thanks DENG for leading this initiative.

I would love to share few quick links to prepare for this meeting:

We have a two parts video that provides TOSCA in practice training : Part 1: 
https://www.youtube.com/watch?v=aMkqLI6o-58 and  
https://www.youtube.com/watch?v=6xGmpi--7-A

And Michael Brenner for ETSI/NFV and TOSCA has recently drafted a in-depth 
comparison between model-driven and task-driven workflows: 
http://getcloudify.org/brochures/tosca-workflows-Apr-2017.pdf

? amir

amir at gigaspaces.com<mailto:amir at gigaspaces.com> +1 408 916 
8572

On Apr 20, 2017, at 10:29 AM, Nguyenphu, Thinh (Nokia - US/Irving) 
mailto:thinh.nguyenphu at nokia.com>> wrote:

Hi Rittwik and DENG,

Is modeling discussion covering network service and VNF descriptors? Or it is 
broader to cover all of the ONAP functions?

Yes, I am planning to attend.

Thinh

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
denghui (L)
Sent: Thursday, April 20, 2017 3:35 AM
To: denghui (L) mailto:denghui12 at huawei.com>>; 
onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; onap-discuss at 
lists.onap.org<mailto:onap-discuss at lists.onap.org>
Cc: JANA, RITTWIK (RITTWIK) mailto:rjana at 
research.att.com>>
Subject: [onap-discuss] Modelling discussion on Friday May 5th

Hello all

We are happy to let you know that we are hosting a modeling session on Friday, 
May 5th, AT&T Lab.
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT&T Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
___
onap-discuss mailing list
onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170426/ddece182/attachment-0001.html>

[onap-tsc] the content of ONAP

2017-03-27 Thread denghui (L)

Dear Robert

I agree most of your thoughts , very insightful,  Just  one comment below 
please,

-It is able to onboard external VNFs with "moderate" adaptations. To have VNF 
strictly ecomp compliant may be tough and not possible in the beginning, 
especially for VNF with EMS with very advanced features (in RAN for instance). 
ONAP will help design VNF to be ONAP compliant. In some case, the EMS itself 
could be considered as a VNF.  It should be done under the ETSI/Mano framework. 
ONAP is a way to close ETSI/Mano options or lack of Stage 3 specifications. It 
is important to allow ?in house? VNF (that is developed by operators service 
designers) or to have 3rd party VNF, with a healthful industry of VNF 
suppliers, in a smooth market place.
== > Agree with you here to align with ETSI NFV, I think that VNF-C project is 
the right approach to support your idea which cover VNF with advanced feature 
like (IMS/RAN/EPC). The start point is that you could let Orange people getting 
familiar how OPENO code to implement NFVO with Tosca NFV profile.

Best regards,

DENG Hui

From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at 
lists.onap.org] On Behalf Of roberto.k...@orange.com
Sent: Monday, March 27, 2017 6:16 AM
To: tsc at lists.onap.org
Subject: [onap-tsc] the content of ONAP

Dear TSC members,

Here is a small contribution for thoughts to the TSC. I have already shared 
this informally with some of you.

The TSC is its bootstrap process, setting up its organization. The TSC has not 
yet discussed about any content (we just have a list of modules which the TSC 
must formally approved to work with the appropriated creation of workstreams). 
Today, we have 2 set of codes that we need to merge in some way. Certainly by 
playing with these codes, our Opensource community will find ways to merge them.

Internally in Orange we start to have some technical views, may be superficial 
as we know ecomp a little bit, and we have not played yet with Open-O code. We 
would like to understand where to put our resources for the community, as we 
would like to commit at least 5 to 10 people full time.

I would like the TSC to consider the need to have a kind of ?ONAP Framework? 
workstream that would regroup (may be even define) the main principles of ONAP. 
This would clarify ONAP structure and objectives, so that it becomes clear to 
everybody where and how to contribute.

I have tried to make an ONAP Framework strawman.

-It is holistic (from design to run). Allows CI/CD. Allows to close the loop 
with operation that can use ONAP to define its services (in addition to service 
designer and security): this is important for operators, to be agile like a web 
player.

-It is interoperable with major industry initiatives (OPNFV, ODL, OStack on the 
'lower' part; TMForum for Data model and APIS on the 'higher' part): this is 
important for operators to be able to introduce ONAP within our legacies, 
whatever the type of Operator (small, medium, large, multi country operations).

-It is able to onboard external VNFs with "moderate" adaptations. To have VNF 
strictly ecomp compliant may be tough and not possible in the beginning, 
especially for VNF with EMS with very advanced features (in RAN for instance). 
ONAP will help design VNF to be ONAP compliant. In some case, the EMS itself 
could be considered as a VNF.  It should be done under the ETSI/Mano framework. 
ONAP is a way to close ETSI/Mano options or lack of Stage 3 specifications. It 
is important to allow ?in house? VNF (that is developed by operators service 
designers) or to have 3rd party VNF, with a healthful industry of VNF 
suppliers, in a smooth market place.

There are some global technical principles that could be aggreed:
-metamodels based (tools needed to simplify/structure modeling TMF SID based 
/Tosca / Workflow description)
-policies (be able to introduce policy engine).
-Have a clear orchestration architecture: global orchestration even to legacy 
(so called hybrid mode ; through Yang + restful API). Hierachy of 
Orchestrations with clear responsibility (MSO is stateless, while below we can 
have evolving controllers stateful -with Trouble Shooting capabilities). 
Ability to introduce new controllers (if need be).
-Very big importance of Active Inventory (necessary for the Run, for roll 
backing, for Trouble shooting).
-The most important part of ONAP is event monitoring: ability to define, 
capture, collect events and to react.
-All design done through a single design tool.
Etc...

If we agree on the framework, the identification of modules, and what to do 
with each of them would be easier in the TSC to define roadmaps and what could 
be the first release of ONAP. By the way this first release should be available 
in 2017.

Hope this contribution is useful. This could be discussed at the ONS summit 
beginning of april but as many TSC members will not be able to attend, this 
should more formally discussed for our first F2F meeting i

[onap-tsc] May face-to-face: NA location?

2017-03-31 Thread denghui (L)

Phil,

As Brian said here, as feedback before, if we decide the 1st week of May, 
Canada is not a good choice as well, NJ in US would be better choice.

Thanks

DENG Hui

From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Saturday, April 01, 2017 12:46 AM
To: Phil Robb ; GILBERT, MAZIN E 
Cc: tsc at lists.onap.org
Subject: Re: [onap-tsc] May face-to-face: NA location?

Phil,

The feedback I thought I saw was that Canada was no better than US.

Seems like late May is the best choice.

Brian


From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Friday, March 31, 2017 12:43 PM
To: GILBERT, MAZIN E mailto:mazin at 
research.att.com>>
Cc: tsc at lists.onap.org
Subject: Re: [onap-tsc] May face-to-face: NA location?

We had members from China indicate that getting visa's to the U.S./ were very 
slow, and/or being flat out rejected.  So for the first week of May selection, 
I think we need to do Vancouver as the ability to get a Canadian Visa is much 
better/faster than the U.S.

If we do the meeting in late May, then New Jersey could be a viable option, but 
as mentioned earlier if we pick late May, then we delay our jump-start of the 
community as well as position the first face to face too close to the second 
face to face which is tentatively planned for June in China.

Best,

Phil.

On Fri, Mar 31, 2017 at 8:52 AM, GILBERT, MAZIN E (MAZIN E) mailto:mazin at research.att.com>> wrote:
I believe we agreed that if North America is selected then it would be NJ.
We will find out later today.

Mazin


On Mar 31, 2017, at 10:46 AM, GOLDNER, ALLA mailto:alla.goldner at amdocs.com>> wrote:

Hi,

Amdocs would also prefer New Jersey in the US/Toronto in Canada as a location, 
if possible ? as we have National Holidays ending the day before the meeting, 
travel time is critical, and getting to Vancouver takes many hours more?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Jason Hunt
Sent: Friday, March 31, 2017 5:20 PM
To: tsc at lists.onap.org
Subject: [onap-tsc] May face-to-face: NA location?



Perhaps I'm the only one that is confused on the May face-to-face meeting.  I 
thought based on yesterday's TSC meeting that we were looking to have the North 
American location be in New Jersey, with Mazin's offer to host.  But Annie 
posted on the Doodle poll that the North American location is Vancouver?


Regards,
Jason Hunt
Executive Software Architect, IBM

Phone: +1-314-749-7422
Email: djhunt at us.ibm.com
Twitter: @DJHunt

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
http://www.amdocs.com/email_disclaimer.asp
 ___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=2qDBFz2Nv5zgbgGhmfgoTxcCj1Ntr9uHlZiAwO8crRY&s=8uqc15bz1wtUR93A0ju8YOS31o3_Y4FlodYtyVG3NyE&e=


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



--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] [Modeling]Start Poll Modeling weekly teleconf time

2017-05-11 Thread denghui (L)

Hello all

Please help to do doodle for our regular weekly teleconf time, we are going to 
close the doodle until this Sunday, EDT 10AM
http://doodle.com/poll/itpu466itrriqerc

Thanks a lot

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

[onap-tsc] Project Proposal: Modeling

2017-05-11 Thread denghui (L)

Dear TSC,

We would like to formally propose ONAP project for Modeling.
The proposal wiki page, which includes details of the project description, 
project scopes, and proposed repo names, can be found at: 
https://wiki.onap.org/display/DW/Modeling

The Modeling team consists of representatives from AT&T, Huawei, China Mobile, 
Cisco, ZTE, Gigaspaces, Amdocs, Nokia, IBM, Windriver, Intel, Techmahindra, 
Ciena

Regards,

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

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

2017-05-26 Thread denghui (L)

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] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 7:55 AM
To: Christopher Donley (Chris); onap-tsc@lists.onap.org; 
onap-disc...@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] On Behalf Of Christopher Donley (Chris)
Sent: 2017年5月27日 7:44
To: onap-tsc@lists.onap.org; 
onap-disc...@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&modificationDate=1493761356000&api=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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

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

2017-05-30 Thread denghui (L)

Michael

Modeling project is on Tuesday, TOSCA NFV adhoc is on Wednesday, there is no 
confliction
Thanks

DENG Hui


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Michael Brenner
Sent: Wednesday, May 31, 2017 5:33 AM
To: Lingli Deng
Cc: onap-discuss; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Lingli,

Can we try to move this slot? It conflicts weekly with the TOSCA NFV ad-hoc 
group, which was set like this long ago (9-11 EDT).

Thanks,
Michael

On Mon, May 29, 2017 at 10:55 PM, Lingli Deng 
mailto:denglin...@chinamobile.com>> wrote:
Hi Andrei,

You can find the information on the modeling project proposal wiki page as 
follows:

Collaboration:
•Meeting every wed 9:00/10:00 EDT, 6:00/7:00 PDT, 15:00/16:00 CET, 9:00/10:00PM 
Beijing
•IRC - https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23onap-modeling

Lingli

From: Andrei Kojukhov 
[mailto:andrei.kojuk...@amdocs.com]
Sent: 2017年5月27日 16:01
To: Lingli Deng 
mailto:denglin...@chinamobile.com>>; 'Christopher 
Donley (Chris)' 
mailto:christopher.don...@huawei.com>>; 
onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: RE: [onap-tsc] ONAP Architecture subcommittee kickoff

Hi Lingli,

Where can I find the info about the modelling weekly calls?

Tks,

Andrei

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 2:55 AM
To: 'Christopher Donley (Chris)' 
mailto:christopher.don...@huawei.com>>; 
onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: Re: [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] On Behalf Of Christopher Donley (Chris)
Sent: 2017年5月27日 7:44
To: onap-tsc@lists.onap.org; 
onap-disc...@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&modificationDate=1493761356000&api=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
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-disc...@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss



--
Michael Brenner, Chief Architect NFV

[图像已被发件人删除。]



M: +1-732-895-5772

http://getcloudify.org

@cloudifysource

[图像已被发件人删除。]  [图像已被发件人删除。] 
   [图像已被发件人删除。] 
   [图像已被发件人删除。] 




[图像已被发件人删除。]

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

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

2017-05-30 Thread denghui (L)

Hi Thinh, and all

Thank you, I just updated the webpage:  Meeting every Tuesday 9:00/10:00 EDT, 
6:00/7:00 PDT, 15:00/16:00 CET, 9:00/10:00PM Beijing –
Once this project is formally approved, we will apply for formal zoom bridge 
from LF asap since the limitation of attendees is still 40.

Best regards,

DENG Hui

From: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyen...@nokia.com]
Sent: Wednesday, May 31, 2017 9:20 AM
To: denghui (L); Michael Brenner; Lingli Deng
Cc: onap-discuss; onap-tsc@lists.onap.org
Subject: RE: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Hi Deng Hui,

The confusion is from wiki project page, which it is still showing older 
information: “Meeting every wed 9:00/10:00 EDT, 6:00/7:00 PDT, 15:00/16:00 CET, 
9:00/10:00PM Beijing “
Thinh

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Tuesday, May 30, 2017 8:08 PM
To: Michael Brenner mailto:mich...@gigaspaces.com>>; 
Lingli Deng mailto:denglin...@chinamobile.com>>
Cc: onap-discuss 
mailto:onap-disc...@lists.onap.org>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Michael

Modeling project is on Tuesday, TOSCA NFV adhoc is on Wednesday, there is no 
confliction
Thanks

DENG Hui


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 Brenner
Sent: Wednesday, May 31, 2017 5:33 AM
To: Lingli Deng
Cc: onap-discuss; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Lingli,

Can we try to move this slot? It conflicts weekly with the TOSCA NFV ad-hoc 
group, which was set like this long ago (9-11 EDT).

Thanks,
Michael

On Mon, May 29, 2017 at 10:55 PM, Lingli Deng 
mailto:denglin...@chinamobile.com>> wrote:
Hi Andrei,

You can find the information on the modeling project proposal wiki page as 
follows:

Collaboration:
•Meeting every wed 9:00/10:00 EDT, 6:00/7:00 PDT, 15:00/16:00 CET, 9:00/10:00PM 
Beijing
•IRC - https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23onap-modeling

Lingli

From: Andrei Kojukhov 
[mailto:andrei.kojuk...@amdocs.com<mailto:andrei.kojuk...@amdocs.com>]
Sent: 2017年5月27日 16:01
To: Lingli Deng 
mailto:denglin...@chinamobile.com>>; 'Christopher 
Donley (Chris)' 
mailto:christopher.don...@huawei.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: RE: [onap-tsc] ONAP Architecture subcommittee kickoff

Hi Lingli,

Where can I find the info about the modelling weekly calls?

Tks,

Andrei

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 2:55 AM
To: 'Christopher Donley (Chris)' 
mailto:christopher.don...@huawei.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: Re: [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-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@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&modificationDate=1493761356000&api=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

[onap-tsc] Modeling subcommittee proposal

2017-06-09 Thread denghui (L)

Hello all

Based on the modeling project subgroup discussion, we propose Modeling 
subcommittee for TSC review,
we separate the scope of modeling project for tools, modeling subcommittee for 
modeling specifications across the projects.
https://wiki.onap.org/display/DW/ONAP+Modeling+sub-committee

Thanks a lot for review

Best regards,

DENG Hui


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

[onap-tsc] Weekly standard coordinator report

2017-06-11 Thread denghui (L)

Hello TSC and all,

For standard coordinator:

1)  Internally, we had a proposal to build modeling subcommittee for TSC to 
approve:

https://wiki.onap.org/display/DW/ONAP+Modeling+sub-committee



2)  Externally, I would suggest that once all projects have been approved 
and architecture had some progress, then will open call for expertise to each 
standard body ASAP.

Thanks for checking

DENG Hui
___
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

2017-06-12 Thread 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] Modeling subcommittee proposal

2017-06-14 Thread denghui (L)

Hello all.

Thanks Chris Donley for kindly help to simplified the wording on the wiki page,
If that is possible, we would like to request an approval in tomorrow during 
TSC meeting
https://wiki.onap.org/display/DW/Modeling+sub-committee

Best regards,

DENG Hui

From: denghui (L)
Sent: Friday, June 9, 2017 4:13 PM
To: 'onap-disc...@lists.onap.org' 
Cc: onap-tsc 
Subject: Modeling subcommittee proposal

Hello all

Based on the modeling project subgroup discussion, we propose Modeling 
subcommittee for TSC review,
we separate the scope of modeling project for tools, modeling subcommittee for 
modeling specifications across the projects.
https://wiki.onap.org/display/DW/ONAP+Modeling+sub-committee

Thanks a lot for review

Best regards,

DENG Hui


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

Re: [onap-tsc] Modeling subcommittee proposal

2017-06-14 Thread denghui (L)

Hi Stephen,

As discussed in last time breakout session, the intention is both, for open 
source project, we don't have guideline, it is more standard's way like 3GPP or 
ETSI, it will delay at least our release for 3 or 6 months without modeling 
spec.
I will update other 2 revisions tomorrow, thanks a lot for your comments

DENG Hui

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Wednesday, June 14, 2017 7:13 PM
To: denghui (L) ; onap-disc...@lists.onap.org
Cc: onap-tsc 
Subject: RE: Modeling subcommittee proposal

Hi Deng hui,

Regarding the modelling delivery, is this expectation in line with the 
expectation from the projects about who publishes what, and how do you see that 
working?  In the expected deliverables, is it the information models or data 
models or both?

Could I suggest a few wording changes in the scope.  I understand the 
intention, but they could be interpreated more broadly.
*Purpose:
*Publish Guidelines 
  -> publish modelling guidelines
*Facilitate model reviews
*Publish models
*Curate approved models (model lifecycle management, e.g., versioning)
*Coordinate adoption/use across projects -> 
coordinate model adoption/use across projects
*Alignment with industry standards-> 
Alignment with industry standards for modelling.
Scope:
-I thought that parsers were the responsibility of the ONAP modelling 
project, not the sub-committee?
BR,

Steve


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: 14 June 2017 12:06
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Modeling subcommittee proposal

Hello all.

Thanks Chris Donley for kindly help to simplified the wording on the wiki page,
If that is possible, we would like to request an approval in tomorrow during 
TSC meeting
https://wiki.onap.org/display/DW/Modeling+sub-committee

Best regards,

DENG Hui

From: denghui (L)
Sent: Friday, June 9, 2017 4:13 PM
To: 'onap-disc...@lists.onap.org' 
mailto:onap-disc...@lists.onap.org>>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Modeling subcommittee proposal

Hello all

Based on the modeling project subgroup discussion, we propose Modeling 
subcommittee for TSC review,
we separate the scope of modeling project for tools, modeling subcommittee for 
modeling specifications across the projects.
https://wiki.onap.org/display/DW/ONAP+Modeling+sub-committee

Thanks a lot for review

Best regards,

DENG Hui


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

[onap-tsc] [Modeling] Modeling teleconf this week is cancelled

2017-06-19 Thread denghui (L)

Hello all

Due to Linux Conference in China this week, there are many people who needs to 
attend and present, so we have to cancel it again this week.

Best regards,

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

[onap-tsc] Call for Self-Nominations for Modeling Project PTL

2017-06-20 Thread denghui (L)

Hello all

The Modeling project is soliciting self nominations for its Project Technical 
Lead. Per TSC instructions, nominees should be from those listed as committers 
on the Modeling project proposal approved by the ONAP TSC 
(https://wiki.onap.org/pages/viewpage.action?pageId=3247202). The nomination 
period will end on Thursday, June 22. PDT

To nominate, please send an email to the onap-discuss list, stating your 
interest, and a short bio for helping people to know you better.
After the nomination period is closed, a voting poll will be set up for vote 
collection.

Thanks,

Rittwik & Denghui

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

[onap-tsc] Modeling subcommittee is calling for contributors

2017-06-20 Thread denghui (L)

Hello all

Last week TSC teleconf, Modeling subcommittee was just approved by TSC.
We just created a membership page for Modeling Subcommittee, this is open to 
everybody,
please kindly help to volunteer and put your name under the page
https://wiki.onap.org/display/DW/Members

thanks a lot for your kind help
Best regards,

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

Re: [onap-tsc] [onap-discuss] Call for Self-Nominations for Modeling Project PTL

2017-06-20 Thread denghui (L)

Rajesh,

Sorry for late, was swamped by both OPNFV and LinuxCon in Beijing.
I just put the webpage for members of modeling project,  after couple of days, 
we will call for nominations of the chairs.

Thanks a lot for your remindness
Best regards,

DENG Hui

From: Gadiyar, Rajesh [mailto:rajesh.gadi...@intel.com]
Sent: Tuesday, June 20, 2017 9:30 PM
To: denghui (L) ; onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Cc: Vul, Alex ; Elzur, Uri 
Subject: Re: [onap-discuss] Call for Self-Nominations for Modeling Project PTL

Hello Deng and Rittwik – How about the Modeling sub-committee as we had 
discussed at Beijing F2F? Are you inviting nominees to lead the Modeling 
sub-committee as well?

Regards,
Rajesh


From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "denghui (L)" mailto:denghu...@huawei.com>>
Date: Tuesday, June 20, 2017 at 8:53 AM
To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-discuss] Call for Self-Nominations for Modeling Project PTL

Hello all

The Modeling project is soliciting self nominations for its Project Technical 
Lead. Per TSC instructions, nominees should be from those listed as committers 
on the Modeling project proposal approved by the ONAP TSC 
(https://wiki.onap.org/pages/viewpage.action?pageId=3247202). The nomination 
period will end on Thursday, June 22. PDT

To nominate, please send an email to the onap-discuss list, stating your 
interest, and a short bio for helping people to know you better.
After the nomination period is closed, a voting poll will be set up for vote 
collection.

Thanks,

Rittwik & Denghui

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

Re: [onap-tsc] Name Releases Finalized

2017-06-21 Thread denghui (L)

I guess "has not endorsed" below is a typo?

DENG Hui

-Original Message-
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: Wednesday, June 21, 2017 8:40 PM
To: t...@lists.onap.org
Subject: [onap-tsc] Name Releases Finalized

Dear ONAP Team

As most of you know that the major city names received the highest votes from 
the TSC community for ONAP name releases.
I am happy to inform you that the marketing team has not endorsed the names of 
the first two releases of our ONAP Platform.

The Nov17 A Release will be called Amsterdam The May18 B Release will be called 
Beijing

Both are visually distinctive and attractive cities.

We will fold those names in our release planning going forward.

Thanks
Mazin

___
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

[onap-tsc] [Modeling] PTL self-nomination

2017-06-22 Thread denghui (L)

Dear Modeling committers,

I'd like to nominate myself as Project Technical Lead (PTL) for the Modeling 
project.

Deng HuiI has been heavily involved in ONAP/OPENO process and projects 
creation, especially in the topic of modeling., and he worked as Principal 
staff between 2007 and 2016 in China Mobile, joined Huawei and working on NFV 
related topic quite recently. He acted as the co-chair of IETF MIF working 
group. And he was the board of director of WBA(Wireless Broadband Alliance) 
between 2012-2014, acted as the board of director of OPNFV between 2014-2016 
and 1st board of chairman of OPEN-O project in Linux Foundation.

I look forward to working with everyone in the ONAP community.  Thanks for your 
consideration.

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

[onap-tsc] Standard Coordinator Update

2017-06-22 Thread denghui (L)

Hello all

We have created a “members” wiki page under modeling subcommittee
https://wiki.onap.org/display/DW/Members
there are about 30 people volunteer to become members of this subcommittee,

we will start to call for self-nomination of chair after today TSC teleconf.

External organization contact will wait for more time to get start

Thanks for your checking

DENG Hui


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Ed Warnicke
Sent: Thursday, June 22, 2017 3:12 AM
To: onap-tsc 
Subject: [onap-tsc] External Open Source Coordinator Update

We have begun tracking engagements as well as contacts between ONAP and other 
Open Source Communities here:

https://wiki.onap.org/display/DW/External+Open+Source+Community+Coordination

in order to facilitate their identification so members of the ONAP community 
who need to work with those communities can find them easily.  Members of the 
ONAP community who have contacts with external Open Source communities are 
encouraged to list themselves and there engagements there.

Of particular interest this week is the addition of a general pointer for 
ONAP/OpNFV collaboration.

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

[onap-tsc] [Modeling]The result of PTL election of modeling project

2017-06-27 Thread denghui (L)

Hello all

I would like to share the result of PTL election of modeling project, Deng Hui 
is only one candidate and got 17 “+1”
So Deng Hui win this election, thanks a lot for your support

Best regards,

DENG Hui


From: denghui (L) [mailto:denghu...@huawei.com]
Sent: 2017年6月25日 22:42
To: JANA, RITTWIK (RITTWIK) 
mailto:rj...@research.att.com>>; 
alex@intel.com<mailto:alex@intel.com>; 
a...@gigaspaces.com<mailto:a...@gigaspaces.com>; 
andr...@amdocs.com<mailto:andr...@amdocs.com>; 
art...@gigaspaces.com<mailto:art...@gigaspaces.com>; 
bru...@cisco.com<mailto:bru...@cisco.com>; 
wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>; 
ethanly...@vmware.com<mailto:ethanly...@vmware.com>; 
don...@raisecom.com<mailto:don...@raisecom.com>; 
ll...@chinatelecom.cn<mailto:ll...@chinatelecom.cn>; 
denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>; 
zhonghe...@boco.com.cn<mailto:zhonghe...@boco.com.cn>; 
zhang.maope...@zte.com.cn<mailto:zhang.maope...@zte.com.cn>; 
ss00473...@techmahindra.com<mailto:ss00473...@techmahindra.com>; Lishitao 
mailto:lishi...@huawei.com>>; 
thinh.nguyen...@nokia.com<mailto:thinh.nguyen...@nokia.com>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
shiyb...@chinatelecom.cn<mailto:shiyb...@chinatelecom.cn>; 
hanya...@raisecom.com<mailto:hanya...@raisecom.com>; 
yangyuan...@boco.com.cn<mailto:yangyuan...@boco.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>
Cc: Kenny Paul mailto:kp...@linuxfoundation.org>>; 
Casey Cain mailto:cc...@linuxfoundation.org>>; Phil 
Robb mailto:pr...@linuxfoundation.org>>
Subject: ONAP Modeling project PTL election

Hello all

In order to NOT generating so much traffic in TSC list, I am sending this email 
to committers and LF only, will close the vote at 8am EDT, June 27th, Tuesday,
will disclose the election result to the TSC list once we finished.

Upon closing our self-nomination period, we have only one candidate: Hui Deng
Committers, if you support Hui Deng for PTL, please send “+1”, if you don’t, 
please send “-1”, if you are neutral, please send “0”

Thanks a lot for your kind help
Best regards,

DENG Hui

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

Re: [onap-tsc] [onap-discuss] [Modeling]The result of PTL election of modeling project

2017-06-27 Thread denghui (L)

Thank you, Michael,

DENG Hui

From: Michael Brenner [mailto:mich...@gigaspaces.com]
Sent: Tuesday, June 27, 2017 8:52 PM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [Modeling]The result of PTL election of modeling 
project

Congratulations!
Michael

On Tue, Jun 27, 2017 at 8:10 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hello all

I would like to share the result of PTL election of modeling project, Deng Hui 
is only one candidate and got 17 “+1”
So Deng Hui win this election, thanks a lot for your support

Best regards,

DENG Hui


From: denghui (L) [mailto:denghu...@huawei.com]
Sent: 2017年6月25日 22:42
To: JANA, RITTWIK (RITTWIK) 
mailto:rj...@research.att.com>>; 
alex@intel.com<mailto:alex@intel.com>; 
a...@gigaspaces.com<mailto:a...@gigaspaces.com>; 
andr...@amdocs.com<mailto:andr...@amdocs.com>; 
art...@gigaspaces.com<mailto:art...@gigaspaces.com>; 
bru...@cisco.com<mailto:bru...@cisco.com>; 
wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>; 
ethanly...@vmware.com<mailto:ethanly...@vmware.com>; 
don...@raisecom.com<mailto:don...@raisecom.com>; 
ll...@chinatelecom.cn<mailto:ll...@chinatelecom.cn>; 
denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>; 
zhonghe...@boco.com.cn<mailto:zhonghe...@boco.com.cn>; 
zhang.maope...@zte.com.cn<mailto:zhang.maope...@zte.com.cn>; 
ss00473...@techmahindra.com<mailto:ss00473...@techmahindra.com>; Lishitao 
mailto:lishi...@huawei.com>>; 
thinh.nguyen...@nokia.com<mailto:thinh.nguyen...@nokia.com>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
shiyb...@chinatelecom.cn<mailto:shiyb...@chinatelecom.cn>; 
hanya...@raisecom.com<mailto:hanya...@raisecom.com>; 
yangyuan...@boco.com.cn<mailto:yangyuan...@boco.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>
Cc: Kenny Paul mailto:kp...@linuxfoundation.org>>; 
Casey Cain mailto:cc...@linuxfoundation.org>>; Phil 
Robb mailto:pr...@linuxfoundation.org>>
Subject: ONAP Modeling project PTL election

Hello all

In order to NOT generating so much traffic in TSC list, I am sending this email 
to committers and LF only, will close the vote at 8am EDT, June 27th, Tuesday,
will disclose the election result to the TSC list once we finished.

Upon closing our self-nomination period, we have only one candidate: Hui Deng
Committers, if you support Hui Deng for PTL, please send “+1”, if you don’t, 
please send “-1”, if you are neutral, please send “0”

Thanks a lot for your kind help
Best regards,

DENG Hui


___
onap-discuss mailing list
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss



--
Michael Brenner, Chief Architect NFV

[图像已被发件人删除。]



M: +1-732-895-5772

http://getcloudify.org<http://getcloudify.org?utm_source=signaturesatori&utm_medium=email&utm_campaign=Cloudify%204.0%20Webinar>

@cloudifysource

[图像已被发件人删除。]<https://twitter.com/CloudifySource>  [图像已被发件人删除。] 
<https://www.linkedin.com/company-beta/17918192/>   [图像已被发件人删除。] 
<https://github.com/cloudify-cosmo>   [图像已被发件人删除。] 
<https://www.youtube.com/cloudifysource>



[图像已被发件人删除。]<http://getcloudify.org/webinars/the-new-cloudify-4.html?utm_source=signaturesatori&utm_medium=email&utm_campaign=Cloudify%204.0%20Webinar>

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

[onap-tsc] Standard coordinator update

2017-06-29 Thread denghui (L)

Hi Mazin and Phil,

Due to some confliction, I won't be able to attend today teleconf, summary of 
my report below:

Report of Standard/SDO:

1)  For external: SDO delegate will get started once most related PTL been 
elected,  the plan is to contact with PTL and call for volunteers next week

2)  For internal: Current most standard related work is Modeling part, will 
delegate this work to Modeling subcommittee

Report of Modeling Group update.

1)  Modeling Project and Modeling subcommittee will have teleconf every 
other week, it means one week for modeling project, then the next week will be 
for modeling subcommittee, they will use the same bridge to avoid the 
confusion, since they are almost the same people.

2)  Modeling subcommittee have called for members for 1 week, and I have 
contacted Kenny Paul from LF to start the process of nomination and election 
ASAP. Thanks to Kenny for kind help

Best regards,

DENG Hui

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

[onap-tsc] [Modeling] today's teleconf is cancelled

2017-07-04 Thread denghui (L)

Hello all

Since we have less than 20 people for today teleconf, and we were planning to 
present about modeling spec but there were no SDC people here today.

So we have to cancel today's teleconf, let's do it next Tuesday. Apologize for 
not familiar with US national holiday.

Thanks a lot

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

[onap-tsc] [Modeling] Modeling Subcommittee self-nomination

2017-07-05 Thread denghui (L)

Dear Modeling subcommittee members,

I'd like to nominate myself as the chairperson for the Modeling Subcommittee.

Deng HuiI has been heavily involved in ONAP/OPENO process and projects 
creation, especially in the topic of modeling., and he worked as Principal 
staff between 2007 and 2016 in China Mobile, joined Huawei and working on NFV 
related topic quite recently. He acted as the co-chair of IETF MIF working 
group. And he was the board of director of WBA(Wireless Broadband Alliance) 
between 2012-2014, acted as the board of director of OPNFV between 2014-2016 
and 1st board of chairman of OPEN-O project in Linux Foundation.

In order to better align modeling project and modeling subcommittee, and based 
on past experience of standard about modeling specification
I look forward to working with everyone in the ONAP community.  Many thanks for 
your consideration.

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

[onap-tsc] [modeling] Please vote for chairperson of Modeling Subcommittee

2017-07-06 Thread denghui (L)

Hello, Modelling members,

There is only one candidate for modeling subcommittee: Hui Deng

If you support Please help to vote "+1",
If you are neutral, please vote "0",
If you don't please respond  "-1"

Members are listed here: https://wiki.onap.org/display/DW/Members

Thanks a lot

DENG Hui

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

[onap-tsc] Removing the committer based on the charter

2017-07-07 Thread denghui (L)

Hi Mazin and TSC

From our current charter approved:
https://wiki.onap.org/pages/viewpage.action?pageId=4719160&preview=%2F4719160%2F4719377%2FONAP+TSC+Charter+APPROVED+7+1+CLEAN.pdf

3.2.2.3 Removing Committers
A Committer may voluntarily resign from a project by making a public request to 
the PTL to resign (via the project and ONAP-TSC email lists).
A Committer for a project who is disruptive, or has been inactive on that 
project for an extended period (e.g., six or more months) may have his or her 
Committer status revoked by the project‟s Project Technical Leader (PTL) or by 
2/3 super-majority vote of the project’s committers.
The Project Technical Leader is responsible for informing the Technical 
Steering Committee (TSC) of any committers who are removed or resign via the 
ONAP-TSC email list.
Former committers removed for reasons other than being disruptive may be listed 
as „Emeritus Committers‟.  That title expresses gratitude for their service, 
but conveys none of the privileges of being a Committer.

I would like to get advice from our TSC how PTL could handle this, what’s the 
legal process to handle this.

I also think that this issue won’t interfere with moving forward to our 1st 
release before TSC guide us how to handle this

Thanks a lot

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

Re: [onap-tsc] Removing the committer based on the charter

2017-07-08 Thread denghui (L)

Hi Steve

Modeling project has already limited the number of each company to 2.

Thanks

DENG Hui

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Sunday, July 9, 2017 1:18 AM
To: denghui (L) ; onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: RE: Removing the committer based on the charter

Hi Deng,

I agree that the text could be clearer about how to handle the project 
formation phase, however the interpretation that we could go with was what was 
discussed in the last TSC, the PTL solicits commitment from the committers and 
is that is not forthcoming than the interpretation of “or has been inactive on 
that project for an extended period (e.g. six or more months)” is that the 
contributor is not going to be active in the next six months.  Then there is 
the guidance of the number per company, in such a case the PTL could request 
that the company decides who could volunteerly removes themselves.

Best Regards,

Steve

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: 07 July 2017 17:20
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: [onap-discuss] Removing the committer based on the charter

Hi Mazin and TSC

From our current charter approved:
https://wiki.onap.org/pages/viewpage.action?pageId=4719160&preview=%2F4719160%2F4719377%2FONAP+TSC+Charter+APPROVED+7+1+CLEAN.pdf

3.2.2.3 Removing Committers
A Committer may voluntarily resign from a project by making a public request to 
the PTL to resign (via the project and ONAP-TSC email lists).
A Committer for a project who is disruptive, or has been inactive on that 
project for an extended period (e.g., six or more months) may have his or her 
Committer status revoked by the project‟s Project Technical Leader (PTL) or by 
2/3 super-majority vote of the project’s committers.
The Project Technical Leader is responsible for informing the Technical 
Steering Committee (TSC) of any committers who are removed or resign via the 
ONAP-TSC email list.
Former committers removed for reasons other than being disruptive may be listed 
as „Emeritus Committers‟.  That title expresses gratitude for their service, 
but conveys none of the privileges of being a Committer.

I would like to get advice from our TSC how PTL could handle this, what’s the 
legal process to handle this.

I also think that this issue won’t interfere with moving forward to our 1st 
release before TSC guide us how to handle this

Thanks a lot

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

Re: [onap-tsc] 答复: Irregularities in the Use Case Subcommittee Chair Election

2017-07-10 Thread denghui (L)

Current statement from LF hurts Lingli since she won only 5 votes, people will 
suspect she drove those illegal 5 votes.
Opening up that 5 illegal vote will give innocence to not only Lingli but also 
for those who didn’t ask for exceptional vote.

I also expect this open source community could do something transparent to 
protect the weak.

Thanks

DENG Hui

发件人: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] 代表 Lingli Deng
发送时间: 2017年7月10日 7:58
收件人: 'Phil Robb'; 'Ed Warnicke'
抄送: 'onap-tsc'
主题: Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair Election

Phil and all,

I also agree that it is important to make up for the loopholes in the TSC 
charter, but I think the correction of irregularities is the key to building a 
truly trusting environment. Without this basic openness and fairness, the 
prosperity and success of the open source community is at high risk.

Since when the voting is initiated, it was made clear that the vote would be 
carried out with reference to a specific version of membership. And hence all 
the new members, which China Mobile added later, did not ask to vote, but 
planned to participate in subsequent discussions. I strongly urge the LF to 
clarify the voting results, remove five votes that did not meet the clearly 
stated qualifications in the voting initiation email therefore gained unfair 
advantage to those who obeyed the regulations, and make the necessary public 
warning to the subject (individual or company).

Firstly, it is normal and healthy that there must be different opinions in any 
open organization composed of many members. Therefore, it is necessary to agree 
as far as possible on clear and unambiguous rules to specify how to reach 
consensus when the dispute arises, including the formation of the rule itself, 
the election of officials, the resolution on a specific topic, and so on.
Second, one has to admit that any pre-established rules or statutes are not 
likely to enumerate all the possible situations in a complete reality. In other 
words, there is always a gray area where the rule cannot be covered. It is also 
a normal and inevitable phenomenon that someone has taken advantage of these 
loopholes or gray areas. When it is found that such a situation has occurred 
and that it should be stopped in the future, it is necessary but not sufficient 
to prevent the recurrence of such a phenomenon by simply amending the rule to 
make up for deficiencies in the rules.

Third, the respect for the rule itself and the faithful implementation of the 
resolution of a group formed by a process that is in accordance with the rules 
are the premises of any rule. In an organization that is composed of complex 
members, it is essential that its members, especially its leadership, in the 
process of practice, show respect the existing rules rather than disrupt the 
implementation of the rules. Especially if unacceptable violations to existing 
rules/agreement happens, if no correction is made, but blindly blame and amend 
the rule itself, even if they have the perfect rules in theory (that covers 
every situation in reality), these rules will be useless.

Fourth, In the handling of this specific case, the core of the problem cannot 
be solved and the undesirable behavior will be undoubtedly happening again, if 
we only focus on the amendments to the TSC Charter, rather than emphasizing and 
establishing the spirit of the community to really respect and defend TSC 
Charter. Who will respect and implement the rules/agreement, if the violation 
of the rules will not be subject to any necessary warning, and once there is a 
problem, in any case can modify the existing rules at any time?

Therefore, it is my firm belief that the correction of irregularities is the 
key to truly building a trust environment. Without this basic openness and 
fairness, the prosperity and success of the open source community will be at 
high risk. With this incident, I am personally involved and deeply troubled. As 
a candidate, I am under no obligation to accept unwarranted suspicion. I 
believe that all members who were voting in accordance with the rules regularly 
have the right to call for rectification of their own respect for the rules.

Therefore, I strongly call for resolute redress of those violations of the 
rules and the necessary public warnings of such behavior. We need more 
transparency and fairness in this community.
Thanks,
Lingli


From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: 2017年7月7日 23:47
To: Ed Warnicke mailto:hagb...@gmail.com>>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair 
Election

Hi Ed and Bob:

Given that the Subcommittees we are talking about are technical subcommittees 
serving at the pleasure of the TSC, I suggest

[onap-tsc] Call for volunteer to external standard coordination

2017-07-10 Thread denghui (L)

Hello all

I have created a page for external standard coordination, if you have resource 
to attend both ONAP and standard, and expertise in this area, please kindly 
help to volunteer
https://wiki.onap.org/display/DW/External+Standard+Coordination

thanks a lot for your help
Best regards,

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

Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair Election

2017-07-12 Thread denghui (L)

Hi Phil

You have done well to defense the transparency of open source culture, thank you

Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Wednesday, July 12, 2017 9:20 AM
To: Lingli Deng 
Cc: onap-tsc 
Subject: Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair 
Election

Hello Lingli and the ONAP development community:

First of all, please accept my apology for putting everyone in this position in 
the first place with regard to the election for the Use Case Subcommittee Chair 
position.  The irregularity stemming from the fact that some new members to the 
sub committee were added to the vote, and some were not is a clear operational 
error on the part of the Linux Foundation support team.  We won't let that 
happen again.

Further comments and clarifications are inline below

On Sun, Jul 9, 2017 at 4:58 PM, Lingli Deng 
mailto:denglin...@chinamobile.com>> wrote:
Phil and all,

I also agree that it is important to make up for the loopholes in the TSC 
charter, but I think the correction of irregularities is the key to building a 
truly trusting environment. Without this basic openness and fairness, the 
prosperity and success of the open source community is at high risk.

Since when the voting is initiated, it was made clear that the vote would be 
carried out with reference to a specific version of membership. And hence all 
the new members, which China Mobile added later, did not ask to vote, but 
planned to participate in subsequent discussions. I strongly urge the LF to 
clarify the voting results, remove five votes that did not meet the clearly 
stated qualifications in the voting initiation email therefore gained unfair 
advantage to those who obeyed the regulations, and make the necessary public 
warning to the subject (individual or company).

Lingli, you note that "when the voting is initiated, it was made clear that 
the vote would be carried out with reference to a specific version of 
membership".  I don't think this is actually true.  I believe the email you are 
referencing is here: 
https://lists.onap.org/mailman/private/onap-usecasesub/2017-June/15.html
While it does state that the source of the vote was taken from version 58 of 
the Use Case Subcommittee wiki page, it does not state that those are the only 
people allowed to vote.

I have worked in communities, OpenDaylight being one of them, where new members 
to a constituency are allowed to vote while an election is in process.  I have 
also worked in communities, where this is not allowed.  Hence, I do believe the 
rule needs to be specified if the community feels strongly one way or another.  
Such a rule is not articulated in the ONAP TSC Charter, in the Use Case 
Subcommittee Charter, nor is it articulated in the kick-off email of the 
Chairperson Election.  Regardless, the inconsistent implementation of allowing 
some new members to vote, but not all new members to vote is (as I mentioned 
above) an operational error on the LF, and we recognize and apologize for that.

Now, as for clarifying the voting results.  I am sorry but we are unable to do 
that.  The vote was set up as anonymous within the CIVS voting system and as a 
result, we *do not know* how the 5 added voters actually voted.  The output 
that we received, along with every other member who was invited to vote, shows 
the overall result, but it does not show the detailed ballot reporting and it 
keeps the actual voter information anonymous.  That URL is here for reference:  
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_0acddbd223a75b25

I am however able to tell you the companies from which the 5 new voters came.  
4 came from Gigaspaces and 1 came from Orange.  But again, these 5 did not do 
anything wrong by making the request to be added to the vote.  We, the LF, 
should have either told those 5 that we were not allowing new voters, or we, 
the LF should have automatically included all new members to the sub-committee 
in the vote up until the voting ended.  I.e. in the absence of a clear rule 
from the TSC or subcommittee, the LF makes our best guess at the desire of the 
community, communicates that to the community, and implements it *consistently* 
across all participants.  We, the LF did not do that in this instance.

Firstly, it is normal and healthy that there must be different opinions in any 
open organization composed of many members. Therefore, it is necessary to agree 
as far as possible on clear and unambiguous rules to specify how to reach 
consensus when the dispute arises, including the formation of the rule itself, 
the election of officials, the resolution on a specific topic, and so on.
Yes, I totally agree.

Second, one has to admit that any pre-established rules or statutes are not 
likely to enumerate all the possible situations in a complete reality. In other 
words, there is always a gray area where the rule cannot be covere

[onap-tsc] [modeling] remove some committers and add some contributors

2017-07-18 Thread denghui (L)

Hello all,

After one to one engagement, some of people have decided to move from the 
committers to contributors, some of them would like to join the contributors.
Please kindly help to check the latest version.
https://wiki.onap.org/display/DW/Resources+and+Repositories

Thanks a lot

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

Re: [onap-tsc] Solicit PTL feedback for ONAP RESTful API Design Specification//Fw:[ptls] proposed topic for the next week's PTL meeting

2017-07-19 Thread denghui (L)

Hi Huabing

I have sent a separate email cc to  ZTE ETSI representative, she could help you 
to download those files.
Thanks a lot

DENG Hui

From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Wednesday, July 19, 2017 4:48 PM
To: stephen.terr...@ericsson.com
Cc: gg2...@att.com; ml6...@intl.att.com; sw3...@att.com; Kanagaraj Manickam; 
gn4...@intl.att.com; lxin...@vmware.com; denglin...@chinamobile.com; 
jf2...@att.com; Yunxia Chen; ah0...@intl.att.com; david.sauvag...@bell.ca; 
am8...@att.com; talas...@research.att.com; dtimo...@att.com; rx1...@att.com; 
denghui (L); wangchen...@chinamobile.com; shen...@chinamobile.com; 
rk5...@att.com; pr...@linuxfoundation.org; Gildas Lanilis; 
denghu...@hotmail.com; es4...@att.com; cc...@linuxfoundation.org; 
fu.guangr...@zte.com.cn; pdrag...@research.att.com; sa...@research.att.com; 
l...@research.att.com; mp...@amdocs.com; Seshu m; onap-tsc@lists.onap.org
Subject: Re:RE: Solicit PTL feedback for ONAP RESTful API Design 
Specification//Fw:[onap-tsc][ptls] proposed topic for the next week's PTL 
meeting


Hi Stephen,

Thanks for your thoughtful feedback.



Unfortunately, I don't have access to the SOL draft, But I think we definitely 
should avoid potential misalignment with ETSI. If anyone who involved in ETSI 
SOL could help review this, I will very appreciate it.



The ONAP RESTful API Design Specification can start with some fundamental 
principles like the URI construct and versioning and it's open for discussion 
and will evolve along with ONAP development, if there is anything is not 
consistent with ETSI SOL, we should change it.



Below is the response specificly regrading your comments

E.g. this proposes hyphons “-“ where ETSI propose underscore “_”

Huabing: My personal opinion is that “-” may be more reasonable, I would be 
great if we know the reasoning behind ETSI SOL, However, to avoid potential 
misalignment with ETSI, I marked this item as TBD.



For security reasons, should we use HTTPS instead of HTTP.

Huabing: I added this item to the specification.



Also, on the theme of the token, we would probably needs some explanation 
around the handling of the token – i.e. who generates it, how is it validated 
etc.

Huabing: this item is a general rule rather than implementation description. 
The token should be generated and validated by ONAP auth component such as AAF.



In versioning, is the compatibility for minor revisions only? (i.e. major 
revisions may not be or?)

Huabing:  It's covered.

· Major version: The version used in the URI and denotes breaking 
changes to the API. Internally, a new major version implies creating a new API 
and the version number is used to route to the correct implementation.

· Minor and Patch versions: These are transparent to the client and 
used internally for backward-compatible updates. They should be reflected in 
the swagger files to inform clients about a new functionality or a bug fix.



Regarding versioning, we should describe the behavior regarding version 
negotiation/discovery, i.e. if the client supports x.1.2 and the server 
supports x.1.1 should the client fallback  to x.1.1 or is it assumed that the 
server politely ignores what it doesn’t understand.

Huabing: It's covered as as start point, it's an important capability but we 
may not have time to implement it at Amsterdam release.

· Version discovery (Optional)

Need to be discussed: Should ONAP adopt a version discovery mechanism like 
OpenStack?  :https://wiki.openstack.org/wiki/VersionDiscovery



What is the recommendation if the “verb” cannot be mapped granularly enough to 
Post/get/put/delete?  (e.g. “tell bailey to come” “tell bailey to sit” “Clean 
bailey”, “tell bailey to bark”, … etc.

Huabing: It's not covered now, it's a start point and can evolve along with 
ONAP development.



Thanks,

Huabing


Original Mail
Sender:  mailto:stephen.terr...@ericsson.com>>;
To: zhaohuabing10201488; mailto:gg2...@att.com>>; 
mailto:ml6...@intl.att.com>>; 
mailto:sw3...@att.com>>; 
mailto:kanagaraj.manic...@huawei.com>>; 
mailto:gn4...@intl.att.com>>; 
mailto:lxin...@vmware.com>>; 
mailto:denglin...@chinamobile.com>>; 
mailto:jf2...@att.com>>; 
mailto:helen.c...@huawei.com>>; 
mailto:ah0...@intl.att.com>>; 
mailto:david.sauvag...@bell.ca>>; 
mailto:am8...@att.com>>; 
mailto:talas...@research.att.com>>; 
mailto:dtimo...@att.com>>; 
mailto:rx1...@att.com>>; 
mailto:denghu...@huawei.com>>; 
mailto:wangchen...@chinamobile.com>>; 
mailto:shen...@chinamobile.com>>; 
mailto:rk5...@att.com>>; 
mailto:pr...@linuxfoundation.org>>; 
mailto:gildas.lani...@huawei.com>>; 
mailto:denghu...@hotmail.com>>; 
mailto:es4...@att.com>>; 
mailto:cc...@linuxfoundation.org>>;FuGuangRong10144542;
 mailto:pdrag...@research.att.com>>; 
mai

[onap-tsc] [modeling] Specification sub page and Developers Event

2017-07-20 Thread denghui (L)

Hello all

I have created an sub page for modeling specification:
https://wiki.onap.org/display/DW/ONAP+Modeling+specification

and also added modeling subcommittee meeting request to below link,
https://wiki.onap.org/pages/viewpage.action?pageId=8232264

please add your name there for the participants list:

Best regards,

DENG Hui

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

Re: [onap-tsc] [onap-discuss] Architecture Progress

2017-07-22 Thread denghui (L)

Hi all

I guess that people are confusing about the interface of VNF  with ONAP 
architecture,
Interface between VNF and ONAP is quite simple : Heat(ECOMP) or TOSCA(OPEN-O), 
it has nothing with architecture discussion.

I agree with Chris's suggestion here, either you need to understand the 
implementation or join architecture call.

Best regards,

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Saturday, July 22, 2017 1:56 PM
To: Pasi Vaananen ; onap-disc...@lists.onap.org
Cc: onap-tsc 
Subject: Re: [onap-discuss] Architecture Progress

Hi Pasi, Jamil, Chris, all,

I fully agree with Pasi's view.
When we started this work ,the assumption was that whatever our merged 
architecture will look like internally, we should deliver a single set of 
interfaces between the VNFs and ONAP.
And this is not what we are having right now with R1 proposed architecture.
Also, indeed, if we allow interfaces' divergence for R1, it is going to be hard 
to reverse later. One possible outcome is that some of VNF vendors would want 
to wait until the divergences are resolved. The other possible outcome is that 
we continue proceeding with 2 different tracks within ONAP - one coming from 
Open-O and the other one coming from ecomp, and each one of VNF vendors making 
a decision which track they want/need to support, in some cases having a need 
to support both thus doubling the effort. The latter is clearly not the optimal 
way forward, and not what we want to achieve with ONAP, we should try to see 
how we avoid it at least in a longer term, in my view. The former may be 
significantly improved and timelines may be shortened, if we manage to work on 
it effectively now and provide the shortest path to get there from the current 
state - and Vimal's proposal of target merged architecture looks like a great 
step towards it, preserving all functionality coming from APPC and VF-C, but 
making a single set of external interfaces. I think we should give a very high 
priority to those discussions and handle them now, in parallel to R1 work.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3031B.44C0C240]

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pasi Vaananen
Sent: Friday, July 21, 2017 11:15 PM
To: onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] Architecture Progress


Hi Jamil,

In ONAP F2F in New Jersey, there was what I thought was "agreement" that there 
is to be only one set of VNFDs / interfaces for ONAP. If that is strictly 
enforced (like I think it should be, as these collectively form the "interface" 
between the VNF vendors and ONAP - if the overlap would be e.g. on NS level 
descriptors, it would not be as bad, as those could be considered to be system 
internal and therefore not as much of inter-operability problem), then having 
two parallel implementations means that they would need to do exactly the same 
things, and be essentially "indistinguishable" from each other even on their 
behaviors associated with these descriptors and interfaces.

Obviously, strict enforcement of this would imply about 100% overlap on the 
associated development, testing, etc. activities (minus any sharing of code 
between the teams). And, in addition, coordination between the two teams to 
accomplish the required level of agreement in absence of the independent / 
detailed specification that is to be implemented, which would further slow 
things down.

If ONAP community chooses to allow divergence here for r1, it is going to be 
hard to reverse later (assuming that someone would pick sides and actually 
deploy the result - more likely outcome is that VNF vendors would want to wait 
until the divergences are resolved, i.e. R2 at the earliest per current 
"plan"). It is also going to be difficult to "push back" on e.g. ETSI and OASIS 
on descriptors etc. if ONAP community itself cant get into one opinion on what 
to push.

I like Vimal's "Target Merged Architecture" slide #3 at high level - what is 
the shortest path to get there from the current state ?

Regards,

Pasi

On 07/21/2017 03:09 PM, jamil.cha...@orange.com 
wrote:
Hi Chris
I have participated partially to the last 2 meetings, my position was 
represented by Vimal. We need time to analyse the output before to take a 
position and as you know the subcommittee is consultative and we need to 
discuss the output in the TSC.
I think we have clearly Identified overlap between 2 approches and there is a 
high risk to not have a useful Rel-1 as we have many changes  on the technical 
components in addition to 2 different VNF guidelines.

Regards
Jamil



Cordialement
Jamil
Le 21 juil. 2017 à 20:17, Christopher Donley (Chris) 
mailto:christopher.don...@huawei.com>> a écrit :
Dear Jamil,

Re: [onap-tsc] [onap-discuss] Architecture Progress

2017-07-23 Thread denghui (L)

Just clarify one important thing here, GNVFM is in the scope of ONAP, no on the 
side of VNF vendors.

Inline please == >

From: Pasi Vaananen [mailto:pvaan...@redhat.com]
Sent: Saturday, July 22, 2017 8:53 PM
To: denghui (L) ; Alla Goldner ; 
onap-disc...@lists.onap.org
Cc: onap-tsc 
Subject: Re: [onap-discuss] Architecture Progress

I respectfully disagree, at least based on what has been said / presented in 
the meetings and written down on the present documents:

"Interface between VNF and ONAP is quite simple :"

Given that this has been under discussion for multiple years now, I would not 
say there is anything simple about it.

Interface to VNFs is also not limited to templates only - it also includes all 
run-time APIs and other interfaces towards "G-VNFM" style functionality (i.e. 
in support of VNF and VNFCI LCM operations). Collectively, VNF package and 
*all* artifacts thereof, as well as all interfaces that are exercised by the 
VNF and its associated component instances towards ONAP form the "interface" 
between ONAP and VNF vendor. As the majority of functions related to these 
interfaces and descriptors is implemented in the APP-C or VF-C, if we have 
single set of these, then both need to do the same thing, or functionality 
would need to be somehow split between the two. Right now, as already 
documented in Chris's email, most of the VNF LCM operations between the APP-C 
and VF-C have full overlap.

== > as said in the beginning, GVNFM  is in the scope of ONAP, its south bound 
interface (interface with VNF) is not matter with architecture.

"Heat(ECOMP)"

Heat is primarily interface to specific VIM, i.e. OpenStack. It is true that 
current APP-C uses Heat Orchestration Templates. However, the discussion is not 
the past state but on the future direction of the system, including direction 
of descriptors and APIs, and their implementation or at this point 
implementations. The current approved APP-C project proposal 
here<https://wiki.onap.org/pages/viewpage.action?pageId=3246996> states:

  *   APPC model will be based on ONAP TOSCA and Yang containing a dependency 
model, LCM recipes, configuration templates, policies etc.
  *   APPC provides multi-protocol southbound plugins, including support for 
NETCONF, Chef via a Chef Server, and Ansible and ability to operate through 
vendor specific VNFM/EMS via adaptation through a plugin.

At least the "ONAP TOSCA" (VNFD), Yang, potentially policies, and "etc.", 
Chef/Ansible, and S-VNFM interfaces from the above list are "interfaces" or 
touch-points that VNF vendors would need to integrate with (in addition to DCAE 
metrics/events interfaces which indirectly ultimately are associated with 
policy / controller actions as well).
== > If you are strongly believing in one interface to VNF, then you could go 
to VNF requirement or VNFSDK project, and strongly suggest to remove Heat 
support over there.

As far as I can tell from the project description, there is currently no 
implementation of the "sideways" APIs of ETSI architecture reference model 
between the VNF/EM and the "G-VNFM" function equivalent of APP-C, beyond of the 
indirect actions that can be taken through events received through e.g. 
VES/DCAE. For example, there is no implementation of ETSI SOL style API for VNF 
to directly call to request  "scale some component group out to level 'x'". 
However, there is "NBI" APIs for these operations, but it is not clear (at 
least from description) whether those are allowed to be invoked by the VNFs 
themselves (and if so, how) or ONAP internal subsystems only (if it is set of 
REST APIs, those could be exposed to VNFs as well, but whether that is not very 
clear from the current APP-C context diagram).

"TOSCA(OPEN-O)"

Obviously, the Open-O implementation came with their definition of TOSCA 
artifacts, in this context for VNFDs, and I am aware that those have been 
brought as input to ONAP along with the seed code to support implementation. 
However, from the approved VF-C project proposal 
here<https://wiki.onap.org/pages/viewpage.action?pageId=3246989>  VF-C does for 
the VNFM LCM functions:

  *   support VNF lifecycle management based on the ONAP tosca and yang data 
model and workflow

  *   VNFM Component,

  *   compliant with ETSI NFV MANO architecture and information model
  *   providing full life cycle management and FCAPS for VNFs which do not 
require a vendor VNFM,
  *   providing interface and work with DCAE and Policy for Close Loop 
Automation.

  *   How does this align with external standards/specifications?
  *   VF-C takes the following specifications as a reference.
 *   APIs/Interfaces: ETSI NFV IFA 007, ETSI NFV IFA 008, ETSI NFV SOL 005 
- additional API may be required
 *   Information/data models: ETSI NFV IFA 015, ETSI NFV SOL 001, ETSI NFV 
SO

[onap-tsc] [SDC][MODELING][SO][VFC][SDNC][A&AI][MULTIVIM]ONAP VoLTE SDC call on wednesday

2017-08-01 Thread denghui (L)

Please help to forward it, thanks a lot

DENG Hui
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN
VERSION:2.0
METHOD:PUBLISH
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
CLASS:PUBLIC
CREATED:20170801T153958Z
DESCRIPTION:Hello all\n\nThis is for discussion ONAP VoLTE SDC call.\nONAP 
	Meeting 5 is inviting you to a scheduled Zoom meeting. \nJoin from PC\, Ma
	c\, Linux\, iOS or Android: https://zoom.us/j/137904496  \nOr iPhone one-tap (US Toll): +14086380968\,13
	7904496# or +16465588656\,137904496#\nOr Telephone:\nDial: +1 408 638 0968
	 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 137 904 496\nInternat
	ional numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAK
	Lio5vDnd9JYqUR_a  \n\nThanks a lot\n\nDENG Hui\n
DTEND;TZID="China Standard Time":20170802T23
DTSTAMP:20170801T153958Z
DTSTART;TZID="China Standard Time":20170802T22
LAST-MODIFIED:20170801T153958Z
LOCATION:https://zoom.us/j/137904496
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=zh-cn:ONAP VoLTE SDC call
TRANSP:OPAQUE
UID:04008200E00074C5B7101A82E008D0CE9D731F0BD301000
	010006833155E45E3B34AB8373F4F0AA812F3
X-ALT-DESC;FMTTYPE=text/html:\n\n\n\n\n\n\n\n\nHello all\n\n\n\nThis is for discussion ONAP VoLTE SDC call.\n\n<
	P DIR=LTR>ONAP Meeting 5 is inviting you to a scheduled Zoom 
	meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Andro
	id: https://www.google.co
	m/url?q=https%3A%2F%2Fzoom.us%2Fj%2F137904496&\;sa=D&\;usd=2&\;us
	g=AFQjCNHWLm-MNCNZh9JQ8TByZ7QBGA_nzQ">https://zoom.
	us/j/137904496\n\nOr
	 iPhone one-tap (US Toll): +14086380968\,137904496# or +16465588656\,13790
	4496#\n\nOr Telephone:\nDial: +1 408 638 0968 (US 
	Toll) or +1 646 558 8656 
	(US Toll)\nMeeting ID: 137 904 496\nInternational numbers availabl
	e: https://www.google.com
	/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXByAKLio5vD
	nd9JYqUR_a&\;sa=D&\;usd=2&\;usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOM
	A">https://zoom.us/zoomconference?m=mi-ad1sMLWlXByA
	KLio5vDnd9JYqUR_a\n\n\n\nThanks a lot\n\nDENG Hui\n\n\n
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-AUTOFILLLOCATION:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] ONAP VoLTE SDC call

2017-08-01 Thread denghui (L)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=denghui (L):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-disc...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc:M
 AILTO:onap-tsc@lists.onap.org
DESCRIPTION;LANGUAGE=zh-CN:Hello all\n\nThis is for discussion ONAP VoLTE S
 DC call.\n\nONAP Meeting 5 is inviting you to a scheduled Zoom meeting.\nJ
 oin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/137904496\nOr iPhone one-tap (US Toll): +1
 4086380968\,137904496# or +16465588656\,137904496#\nOr Telephone:\nDial: +
 1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 137 904
  496\nInternational numbers available: https://zoom.us/zoomconference?m=mi
 -ad1sMLWlXByAKLio5vDnd9JYqUR_a<https://www.google.com/url?q=https%3A%2F%2F
 zoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXByAKLio5vDnd9JYqUR_a&sa=D&usd=2
 &usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOMA>\n\nThanks a lot\n\nDENG Hui\n\n
SUMMARY;LANGUAGE=zh-CN:ONAP VoLTE SDC call
DTSTART;TZID=China Standard Time:20170802T22
DTEND;TZID=China Standard Time:20170802T23
UID:04008200E00074C5B7101A82E008D0CE9D731F0BD301000
 010006833155E45E3B34AB8373F4F0AA812F3
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170801T154347Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://zoom.us/j/137904496
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1172408289
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] ETSI NFV API Conventions, wiki page, and more available [modeling]

2017-08-01 Thread denghui (L)

Hi Thinh

I have created  a page for recommended SPECs from SDOs.
https://wiki.onap.org/display/DW/Recommended+specs+from+SDOs

Please help to fill in the spread sheet.

If other SDOs also have such intention, please follow that page as well

Thanks a lot

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Nguyenphu, Thinh (Nokia - US/Irving)
Sent: Wednesday, August 2, 2017 6:20 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ETSI NFV API Conventions, wiki page, and more available

Hello,

Couple week ago, there was a discussion on this list about RESTful API Design 
Specification.  I am happy to report that the ETSI NFV SOL REST API Conventions 
document is available, 
https://nfvwiki.etsi.org/images/NFVSOL(17)50r4_ETSI_NFV_SOL_REST_API_Conventions.pdf.
 This document covers naming conventions, data and URI structures, supported 
content formats, message flows convention and tools, common error situations, 
etc.  This document really help SOL working group during our API specification 
design and development across multiple interfaces to ensure consistency design 
and implementation.

I recommending members to take a look, and development your own conventions for 
ONAP APIs across projects. The goal is to avoid any conflicting convention or 
design principle, etc.

For an overview of ETSI NFV IFA and SOL specifications (published and latest 
drafts), tutorial presentations, and webinar, please visit this wiki page, 
https://nfvwiki.etsi.org/index.php?title=NFVSolutions

For modeling, ETSI NFV has produce UML Modeling Guideline, Papyrus Guidelines, 
NFV Information Model, and IFA011 (VNFD) and IFA014 (NSD).  The links is 
available either at wiki page or attached presentation.

Finally, enclosed attachment is the presentation that presented to VNF Package 
sub-project last Friday.

To Deng Hui,
Would please create a SDO wiki page to record these above information and 
future updates. Thanks

Regards,
Thinh

Thinh Nguyenphu
Nokia Networks
thinh.nguyen...@nokia.com
+1 817-313-5189

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

[onap-tsc] ONAP VoLTE SDC call

2017-08-02 Thread denghui (L)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=denghui (L):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-disc...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc:M
 AILTO:onap-tsc@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Lando,Mich
 ael":MAILTO:ml6...@intl.att.com
DESCRIPTION;LANGUAGE=zh-CN:Hello all\n\nThis is for discussion ONAP VoLTE S
 DC call.\n\nONAP Meeting 5 is inviting you to a scheduled Zoom meeting.\nJ
 oin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/137904496\nOr iPhone one-tap (US Toll): +1
 4086380968\,137904496# or +16465588656\,137904496#\nOr Telephone:\nDial: +
 1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 137 904
  496\nInternational numbers available: https://zoom.us/zoomconference?m=mi
 -ad1sMLWlXByAKLio5vDnd9JYqUR_a<https://www.google.com/url?q=https%3A%2F%2F
 zoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXByAKLio5vDnd9JYqUR_a&sa=D&usd=2
 &usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOMA>\n\nThanks a lot\n\nDENG Hui\n\n\n
SUMMARY;LANGUAGE=zh-CN:ONAP VoLTE SDC call
DTSTART;TZID=China Standard Time:20170803T21
DTEND;TZID=China Standard Time:20170803T22
UID:04008200E00074C5B7101A82E008D016015B630CD301000
 010008DF90ACB247CE949A4809568084C6996
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170803T062023Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://zoom.us/j/137904496
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1736673249
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on VoLTE use case

2017-08-03 Thread denghui (L)

Hello all

After 3 days continuous teleconf during modeling subcommittee, we finally made 
concensus on this. Thanks everybody.
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

1) SDC team will start to support service composition from R2
2) agree the hack solution, SDC will confirm it in 3 hours
3) ZTE will propose tosca based SD-WAN solution to SDC for review and will also 
coordinate with SDNC project.
4) modeling committee will start to work on IM and DM as soon as possible

Best regards,

DENG Hui

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

Re: [onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on VoLTE use case

2017-08-03 Thread denghui (L)

Hi Alex,

Multiple projects feels that we need to decide which path we are going to take 
since there are two different IM candidates on the table

Thanks

DENG Hui


From: Vul, Alex [mailto:alex@intel.com]
Sent: Thursday, August 3, 2017 11:36 PM
To: denghui (L) ; onap-disc...@lists.onap.org; onap-tsc 

Subject: RE: [onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on 
VoLTE use case

Hi,

Can you elaborate on what #4 means?

Thanks,

Alex Vul
Intel Corporation


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, August 3, 2017 8:34 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on VoLTE 
use case

Hello all

After 3 days continuous teleconf during modeling subcommittee, we finally made 
concensus on this. Thanks everybody.
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

1) SDC team will start to support service composition from R2
2) agree the hack solution, SDC will confirm it in 3 hours
3) ZTE will propose tosca based SD-WAN solution to SDC for review and will also 
coordinate with SDNC project.
4) modeling committee will start to work on IM and DM as soon as possible

Best regards,

DENG Hui

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

Re: [onap-tsc] [onap-discuss] ONAP VoLTE SDC call

2017-08-03 Thread denghui (L)

Thanks, David and Michael,

Let’s move on based on the consensus we have achieved for R1, will do R2 
together asap.

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lando,Michael
Sent: Friday, August 4, 2017 3:42 AM
To: onap-disc...@lists.onap.org; onap-tsc 
Cc: Kapeluto, Zahi ; Rozin, Eden ; 
Michael Brenner 
Subject: Re: [onap-tsc] [onap-discuss] ONAP VoLTE SDC call

Since we were able to agree on a solution using SDC.

I suggest we do not move forward with the addition of the VNF-DESIGNE code to 
the SDC repository.

I think the resource of the community can be spent on contributing to SDC and 
helping us reach R1 successfully.


BR,

Michael Lando
SDC PTL
AT&T Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com<mailto:ml6...@intl.att.com>


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Rozin, Eden
Sent: Thursday, August 03, 2017 10:00 PM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Michael 
Brenner mailto:mich...@cloudify.co>>; SHADMI, DAVID 
mailto:ds2...@att.com>>
Cc: Kapeluto, Zahi mailto:zk0...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-discuss] ONAP VoLTE SDC call

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Very nice outcome indeed; 10x to all involved. Now we need to deliver.

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Thursday, August 03, 2017 9:14 PM
To: Michael Brenner mailto:mich...@cloudify.co>>; SHADMI, 
DAVID mailto:ds2...@att.com>>
Cc: Kapeluto, Zahi mailto:zk0...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>; Rozin, Eden 
mailto:er4...@intl.att.com>>
Subject: RE: [onap-discuss] ONAP VoLTE SDC call

+1!

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael Brenner
Sent: 03 August 2017 20:05
To: SHADMI, DAVID mailto:ds2...@att.com>>
Cc: KAPELUTO, ZAHI mailto:zk0...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>; ROZIN, EDEN 
mailto:er4...@intl.att.com>>
Subject: Re: [onap-discuss] ONAP VoLTE SDC call

Good outcome!
Michael

On Thu, Aug 3, 2017 at 1:51 PM, SHADMI, DAVID 
mailto:ds2...@att.com>> wrote:
All,

SDC can support SO suggestion for VoLTE service design presented in th call.

With that, I believe we concluded the discussion about the different options, 
and we are moving forward with Option A.
1.  SDC supports onboarding the vIMS and vEPC validated (VNF SDK) VNFs.
2.  vIMS, vEPC, and WAN services design in SDC.
3.  VoLTE service design in SDC.
4.  Distribution of the 4 services to SO, SDNC, VF-C, A&AI.

Regards,
David

-Original Appointment-
From: LANDO, MICHAEL On Behalf Of denghui (L)
Sent: Thursday, August 03, 2017 5:09 AM
To: denghui (L); KAPELUTO, ZAHI; SHADMI, DAVID; ROZIN, EDEN; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc; 
Lando,Michael
Subject: FW: ONAP VoLTE SDC call
When: Thursday, August 03, 2017 9:00 PM-10:00 PM (UTC+08:00) Beijing, 
Chongqing, Hong Kong, Urumqi.
Where: 
https://zoom.us/j/137904496<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_137904496&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=5dr94prXH2Bs3fZkzpVsASPcH93hpNUM-tY-Nz-yrlM&m=AFijJhC8vPMUMs4BJhJj3lSRrzgVTbKfACsMyPyO4Zg&s=wDdkvtT7GUymtRQIp9objIvjGkPMmkMRzOT_mHTU8IE&e=>




-Original Appointment-
From: denghui (L) [mailto:denghu...@huawei.com]
Sent: Thursday, August 03, 2017 9:20 AM
To: denghui (L); 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc; 
Lando,Michael
Subject: ONAP VoLTE SDC call
When: Thursday, August 03, 2017 9:00 PM-10:00 PM (UTC+08:00) Beijing, 
Chongqing, Hong Kong, Urumqi.
Where: 
https://zoom.us/j/137904496<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_137904496&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=5dr94prXH2Bs3fZkzpVsASPcH93hpNUM-tY-Nz-yrlM&m=AFijJhC8vPMUMs4BJhJj3lSRrzgVTbKfACsMyPyO4Zg&s=wDdkvtT7GUymtRQIp9objIvjGkPMmkMRzOT_mHTU8IE&e=>


Hello all

This is for discussion ONAP VoLTE SDC call.
ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/137904496<https://urldef

[onap-tsc] [modeling] tomorrow call agenda

2017-08-07 Thread denghui (L)

Hello all

Agenda will be

1)  Repo of TOSCA PARSERs and FOSS progress

2)  SD Template proposals discussion from SO/VFC and SDC.

Thanks a lot

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

Re: [onap-tsc] [modeling] tomorrow call agenda

2017-08-07 Thread denghui (L)

1st part is modeling project,
And because modeling committee has too many things to handle, we have to add 
more meeting time to discuss key R1 issue.

From: Vul, Alex [mailto:alex@intel.com]
Sent: Tuesday, August 08, 2017 12:24 AM
To: denghui (L); onap-disc...@lists.onap.org; onap-tsc
Cc: Rittwik Jana
Subject: RE: [modeling] tomorrow call agenda

Is this going to be a modeling subcommittee or a project meeting?

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Monday, August 7, 2017 9:00 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: Rittwik Jana mailto:rittwik.j...@gmail.com>>
Subject: [onap-discuss] [modeling] tomorrow call agenda

Hello all

Agenda will be

1)  Repo of TOSCA PARSERs and FOSS progress

2)  SD Template proposals discussion from SO/VFC and SDC.

Thanks a lot

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

[onap-tsc] [modeling][sdc][vfc][so][vnfsdk][sdnc][uui] Agenda of modeling project/subcommittee for tomorrow teleconf

2017-08-21 Thread denghui (L)

Hello all

This Thursday is the deadline for freezing of API, normally it means freezing 
of modeling spec for R1. We can't always delay until the deadline for code 
freezing :)
even tomorrow was planned for modeling project, we will borrow most time from 
modeling project to discuss the status of interface and modeling spec, to check 
whether we need additional call in this week.


1)  Modeling project, (only 1 tosca parser is on the repo for VFC, UUI 
hasn't confirmed yet)



2)  Check the status of interface and modeling spec

Interfaces

a)   VNFSDK-SDC

b)   SDC-SO

c)SDC-VFC

d)   SO-VFC

e)   SO-SDNC
Modeling specs
1.a) VNFD (skip for R1?)
1.b) SD
1.c) NSD
1.d) WAN spec
1.e) vnf package (skip for R1)



3)  ONAP modeling namespace

Thanks a lot

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

Re: [onap-tsc] Please Pick The Sessions You Want To Attend in Paris

2017-09-12 Thread denghui (L)

Hi Kenny,

How could people add theirs name?

1)  Leader will under each topic create a new "Interested: " to let people 
input their name

2)  at the bottom of page to add name and interested topics list?

Thanks a lot for your instruction
Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Tuesday, September 12, 2017 5:06 PM
To: onap-disc...@lists.onap.org; onap-tsc 
Subject: [onap-tsc] Please Pick The Sessions You Want To Attend in Paris

Please remember to go to the Topics page and start adding your name to the 
specific topics you would be primarily interested in.  We will use the level of 
interest in a particular topic to help us with scheduling and setting the 
agenda for Paris.

https://wiki.onap.org/display/DW/September+26-28+Topics

Thanks!

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

[onap-tsc] [modeling] ECOMP IM and DM uploaded

2017-09-14 Thread denghui (L)

Hello all,

Thanks Rittwik kindly help, those two Doc have been uploaded under 20170912 
Meeting Minutes
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

please help to review and be prepared for next week presentation

Best regards,

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

[onap-tsc] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

2017-09-27 Thread denghui (L)

Hello all

We haven't finished yesterday session, let's continue 10:30-11:30 this morning 
in the meeting room (Algebre), 2nd floor.
Agenda would be :

1)  SDC feedback to VNF modeling

2)  VFC feedback to VNF modeling

3)  Summary of VNF Modeling

4)  OSM modeling comparison

Apologies to US remote attendees, we couldn't conflict with TSC meeting in the 
afternoon.

Thanks a lot for your attending
Best regards,

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

Re: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

2017-09-27 Thread denghui (L)

Alex,

we have already heard yesterday feedback from Chris Donley Andy, VNFSDK & 
Architecture, ,
and now we need to move on and would expect more from the implementers side.

Thanks

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, September 27, 2017 9:45 AM
To: denghui (L) ; onap-disc...@lists.onap.org; onap-tsc 

Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Hi,

I don't see how we the critical mass to do this. If you want the feedback to be 
heard, you need to include the people who are working on the VNF models, 
including those who are leading the work - Chris, Andy, others. Chris is on 
stage presenting. Andy is asleep...

My two cents,

Alex

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, September 27, 2017 12:32 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

Hello all

We haven't finished yesterday session, let's continue 10:30-11:30 this morning 
in the meeting room (Algebre), 2nd floor.
Agenda would be :

1)  SDC feedback to VNF modeling

2)  VFC feedback to VNF modeling

3)  Summary of VNF Modeling

4)  OSM modeling comparison

Apologies to US remote attendees, we couldn't conflict with TSC meeting in the 
afternoon.

Thanks a lot for your attending
Best regards,

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

Re: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

2017-09-27 Thread denghui (L)

Andrei and Alex

Our key modeling implementers will not be available with enough time this 
afternoon after TSC meeting, that will be really hard to discuss it.
So we have no choice only this morning

Thanks for your understanding

DENG Hui


From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com]
Sent: Wednesday, September 27, 2017 10:05 AM
To: Vul, Alex ; denghui (L) ; 
onap-disc...@lists.onap.org; onap-tsc 
Subject: RE: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Dear Deng Hui,

I would also keep the meeting as it was originally planned later today so the 
VNF-SDK Modeling team will be involved.

BR

Andrei

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Vul, Alex
Sent: Wednesday, September 27, 2017 9:58 AM
To: denghui (L) mailto:denghu...@huawei.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Deng Hui,

The R2 VNF modeling work is being led by Andy as part of the VNF SDK project 
being driven by Chris. I think it would be good for the folks who doing the 
model definition to actually hear the inputs... :) Otherwise, I don't see the 
point...

Kind regards,

Alex

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: Wednesday, September 27, 2017 12:50 AM
To: Vul, Alex mailto:alex@intel.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Alex,

we have already heard yesterday feedback from Chris Donley Andy, VNFSDK & 
Architecture, ,
and now we need to move on and would expect more from the implementers side.

Thanks

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, September 27, 2017 9:45 AM
To: denghui (L) mailto:denghu...@huawei.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Hi,

I don't see how we the critical mass to do this. If you want the feedback to be 
heard, you need to include the people who are working on the VNF models, 
including those who are leading the work - Chris, Andy, others. Chris is on 
stage presenting. Andy is asleep...

My two cents,

Alex

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, September 27, 2017 12:32 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

Hello all

We haven't finished yesterday session, let's continue 10:30-11:30 this morning 
in the meeting room (Algebre), 2nd floor.
Agenda would be :

1)  SDC feedback to VNF modeling

2)  VFC feedback to VNF modeling

3)  Summary of VNF Modeling

4)  OSM modeling comparison

Apologies to US remote attendees, we couldn't conflict with TSC meeting in the 
afternoon.

Thanks a lot for your attending
Best regards,

DENG Hui
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

2017-09-27 Thread denghui (L)

Hello all ,

Even we have more than 20 people in the room, but we decide to postpone to this 
afternoon 5:30-6:30
I will revise the wiki page accordingly

Hope it is good for everybody,

Thanks

DENG Hui

From: denghui (L)
Sent: Wednesday, September 27, 2017 10:22 AM
To: 'Andrei Kojukhov' ; Vul, Alex 
; onap-disc...@lists.onap.org; onap-tsc 

Subject: RE: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Andrei and Alex

Our key modeling implementers will not be available with enough time this 
afternoon after TSC meeting, that will be really hard to discuss it.
So we have no choice only this morning

Thanks for your understanding

DENG Hui


From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com]
Sent: Wednesday, September 27, 2017 10:05 AM
To: Vul, Alex mailto:alex@intel.com>>; denghui (L) 
mailto:denghu...@huawei.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Dear Deng Hui,

I would also keep the meeting as it was originally planned later today so the 
VNF-SDK Modeling team will be involved.

BR

Andrei

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Vul, Alex
Sent: Wednesday, September 27, 2017 9:58 AM
To: denghui (L) mailto:denghu...@huawei.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Deng Hui,

The R2 VNF modeling work is being led by Andy as part of the VNF SDK project 
being driven by Chris. I think it would be good for the folks who doing the 
model definition to actually hear the inputs... :) Otherwise, I don't see the 
point...

Kind regards,

Alex

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: Wednesday, September 27, 2017 12:50 AM
To: Vul, Alex mailto:alex@intel.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Alex,

we have already heard yesterday feedback from Chris Donley Andy, VNFSDK & 
Architecture, ,
and now we need to move on and would expect more from the implementers side.

Thanks

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, September 27, 2017 9:45 AM
To: denghui (L) mailto:denghu...@huawei.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Hi,

I don't see how we the critical mass to do this. If you want the feedback to be 
heard, you need to include the people who are working on the VNF models, 
including those who are leading the work - Chris, Andy, others. Chris is on 
stage presenting. Andy is asleep...

My two cents,

Alex

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, September 27, 2017 12:32 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

Hello all

We haven't finished yesterday session, let's continue 10:30-11:30 this morning 
in the meeting room (Algebre), 2nd floor.
Agenda would be :

1)  SDC feedback to VNF modeling

2)  VFC feedback to VNF modeling

3)  Summary of VNF Modeling

4)  OSM modeling comparison

Apologies to US remote attendees, we couldn't conflict with TSC meeting in the 
afternoon.

Thanks a lot for your attending
Best regards,

DENG Hui
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [modeling]zoom number for now

2017-09-27 Thread denghui (L)

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

[onap-tsc] [Modeling] Session this afternoon will start on time at 3pm

2017-09-28 Thread denghui (L)

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

[onap-tsc] [modeling] teleconf of modeling project/subcommittee this week is cancelled

2017-10-02 Thread denghui (L)

Hello all

You might know that 1 billion Chinese people are taking vocation this week all 
together, so considering the hard life in china are not easy, please allow us 
to cancel this week teleconf for modeling project.

Hi Kenny, would you mind to kindly help us to send meeting cancel to the list? 
Thanks a lot for your kind help again

Best regards,

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

[onap-tsc] External SDOs session slides during last week event

2017-10-02 Thread denghui (L)

Hello all

Below link include the slides presented during last week,
https://wiki.onap.org/display/DW/External+SDOs+session+in+Developer+event+in+September

Many thanks to those who kindly help to present in our event

Best regards,

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

[onap-tsc] [modeling] modeling design principals and guideline

2017-10-08 Thread denghui (L)

Hello all

Based on the summary of our F2F meeting, please send your suggestions to David, 
Lingli and Rittwik asap within this week.
They agree to kindly help to coordinate this work, many thanks for their help

-By Oct 15: set guidelines and principals
*Methodology of developing R2 IM/DM
*e.g. create a high-level class diagram, specify how to add extensions, 
and how to define namespaces
*E.g. best efforts to derive from TOSCA Simple Profile 1.2 normaltives


Best regards,

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

[onap-tsc] [Modeling] Invite comments on modeling design principles and guideline

2017-10-10 Thread denghui (L)

Hello all,

We have create a page which list the modeling design principles and guidelines 
for R2+ as below
https://wiki.onap.org/display/DW/ONAP+Modeling+Design+Principles+and+Guidelines

Many thanks to Rittwik, David and Lingli for initial contribution,
and there were some comments and revision from last Modeling teleconf.

We plan to close this on Oct. 15, this Sunday, please kindly help to post your 
comments either this thread or on the wiki page.

Thanks again
Best regards,

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

[onap-tsc] [Modeling] Invite comments on modeling design principles and guideline

2017-10-13 Thread denghui (L)

This is reminder, deadline will be this Sunday.

Thanks a lot

DENG Hui

From: denghui (L)
Sent: Wednesday, October 11, 2017 3:24 AM
To: onap-discuss ; onap-tsc 

Subject: [Modeling] Invite comments on modeling design principles and guideline

Hello all,

We have create a page which list the modeling design principles and guidelines 
for R2+ as below
https://wiki.onap.org/display/DW/ONAP+Modeling+Design+Principles+and+Guidelines

Many thanks to Rittwik, David and Lingli for initial contribution,
and there were some comments and revision from last Modeling teleconf.

We plan to close this on Oct. 15, this Sunday, please kindly help to post your 
comments either this thread or on the wiki page.

Thanks again
Best regards,

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

[onap-tsc] [modeling] RE: ARC Call this week

2017-10-15 Thread denghui (L)

Hello all

Just remind that is the invite to modeling subcommittee, in the Arc call next 
Tuesday, they will discuss about external controller issue,
Please help to attend it,

Thanks a lot

DENG Hui
From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Sunday, October 15, 2017 8:45 PM
To: Christopher Donley (Chris) 
mailto:christopher.don...@huawei.com>>; 
onap-...@lists.onap.org; 
onap-tsc@lists.onap.org
Cc: Nagarajan, Ramesh A. 
mailto:ramesh.a.nagara...@accenture.com>>
Subject: Re: [Onap-arc] ARC Call this week

Thanks, Chris,

Just to highlight that we also ask modelling subcommittee representatives and 
all relevant projects representatives to participate as Ramesh will present 
External Controller concept. The relevant slides are uploaded under 
https://wiki.onap.org/display/DW/ONAP+external+controller+integration

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3460B.B7218C10]

From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: Sunday, October 15, 2017 3:35 PM
To: onap-...@lists.onap.org
Subject: [Onap-arc] ARC Call this week

Team,

Steve Terrill will host the ARC call this week, as I'll be on a plane during 
our call.

We have two topics on the preliminary agenda:

*R2 architecture (Parviz)

*External Controller (Alla)

Chris
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
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-usecasesub] [Onap-arc] [External] Re: External controller support in BeijingRelease

2017-10-16 Thread denghui (L)

Ramesh,

I am not sure whether there is liaison from the board level, but from TSC 
level, we do have officer other than liaison , opensource doesn’t have official 
liaison procedure, there are volunteers only below:
https://wiki.onap.org/display/DW/External+Standard+Coordination

thanks

DENG Hui

From: onap-usecasesub-boun...@lists.onap.org 
[mailto:onap-usecasesub-boun...@lists.onap.org] On Behalf Of Nagarajan, Ramesh 
A.
Sent: Monday, October 16, 2017 11:50 PM
To: Vladimir Yanover (vyanover); Alla Goldner; zhang.maope...@zte.com.cn
Cc: onap-...@lists.onap.org; onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: Re: [Onap-usecasesub] [Onap-arc] [External] Re: [onap-tsc] External 
controller support in BeijingRelease

Vladimir,

I am not sure if you realized that the list on slide 4 is hyperlinked to the 
standard/industry initiative. Each of this has more detail on the specific 
operations/APIs, did not want to regurgitate it here. MEF material is, however, 
not open to non-MEF members. But it seems there is an official liason now 
between ONAP and MEF, so perhaps we can get the detailed APIs ? (not sure who 
the liason is from ONAP side ..).

Ramesh.

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Monday, October 16, 2017 6:19 AM
To: Nagarajan, Ramesh A. 
mailto:ramesh.a.nagara...@accenture.com>>; 
Alla Goldner mailto:alla.gold...@amdocs.com>>; 
zhang.maope...@zte.com.cn
Cc: onap-...@lists.onap.org; 
onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: RE: [Onap-arc] [External] Re: [Onap-usecasesub] [onap-tsc] External 
controller support in BeijingRelease

Ramesh,

Thanks for more data in the slide 4. However this does not really answer my 
question.
The question is which abstraction(s), you suggest, should be supported by the 
“external controller”  For example, which (types of) operations the “external 
controller“ is supposed to support?
A good example is slide 16 showing that the SD-WAN controller supports Presto 
and Adagio in case of MEF, which already provides some hints. There may be 
several additional abstractions supported by the SD-WAN controller – all right, 
just need to list them.
Then let me ask same question about so called “External Controller”: what 
operations the “external controller“ is supposed to support? The list of forums 
does not help. Is it slide 6 to help? Probably not. What is “Domain Controller” 
e.g. in case of the RAN domain? What kind of RAN abstraction it is assumed to 
support? Where is it defined?

Thanks
Vladimir

From: Nagarajan, Ramesh A. [mailto:ramesh.a.nagara...@accenture.com]
Sent: Sunday, October 15, 2017 8:14 AM
To: Vladimir Yanover (vyanover) 
mailto:vyano...@cisco.com>>; Alla Goldner 
mailto:alla.gold...@amdocs.com>>; 
zhang.maope...@zte.com.cn
Cc: onap-...@lists.onap.org; 
onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: RE: [Onap-arc] [External] Re: [Onap-usecasesub] [onap-tsc] External 
controller support in BeijingRelease

Hi All,

Please find the updated slides on the link below

https://wiki.onap.org/display/DW/ONAP+external+controller+integration

Vladimir, Per your question, please find some current/emerging standards for 
domain abstractions in slide 4 and other parts of the deck.

Ramesh.

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Sunday, October 15, 2017 12:13 AM
To: Nagarajan, Ramesh A. 
mailto:ramesh.a.nagara...@accenture.com>>; 
Alla Goldner mailto:alla.gold...@amdocs.com>>; 
zhang.maope...@zte.com.cn
Cc: onap-...@lists.onap.org; 
onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: RE: [Onap-arc] [External] Re: [Onap-usecasesub] [onap-tsc] External 
controller support in BeijingRelease

Dear Colleagues,
The question “what is the abstraction of external controller” is another form 
of the question “what the external controller is” or, if you will, “what this 
discussion is about”.
Until this question is answered, how anything can be done about the “external 
controller”?
The original presentation on SD-WAN refers to several particular abstractions 
of the SD-WAN controller that should be covered. If these abstractions are well 
defined (I did not check), for SD-WAN that’s enough. However extending this 
further, necessaril

[onap-tsc] Weekly Report from modeling subcommittee

2017-10-18 Thread denghui (L)

Hi

This week we reviewed the modeling design principle and guideline, the draft 
version has been review for 1st round, hope we could finalize it based on 2nd 
round review in this week.
One of core idea is ONAP R2+ modeling will use SDC DM and ECOMP IM as the 
starting point

Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Thursday, October 19, 2017 4:12 AM
To: onap-tsc@lists.onap.org P 
Cc: onap-sec...@lists.onap.org
Subject: [onap-tsc] Weekly Report from security subcommittee

Hi,

Here is the report from the security sub-committee to the TSC.

This week we reviewed more updates to the S3P requirements from a security 
perspective to align on the per release text from the security sub-committee 
perspective (the per project was fine).

Discussions on how to use coverity for the static code scanning continue

The topic of credential management is progressing.  The idea is to firm up the 
proposal for recommendation promptly.  The current proposal can be found in 
section 2 of 
https://wiki.onap.org/display/DW/ONAP+security+Recomendation+Developement . 
Comments from the community are most appreciated.

Best Regards,

Steve.

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

Ericsson
Ericsson R&D 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 Report from modeling subcommittee

2017-10-18 Thread denghui (L)

Hi

The slide is always on the wiki page
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

DENG hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Thursday, October 19, 2017 9:54 AM
To: denghui (L) ; onap-tsc@lists.onap.org; onap-discuss 

Subject: RE: Weekly Report from modeling subcommittee

Hi,

Can you please publish the slides that were shown during the meeting?

Thanks in advance,

Alex

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, October 18, 2017 6:52 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-discuss 
mailto:onap-disc...@lists.onap.org>>
Subject: [onap-tsc] Weekly Report from modeling subcommittee

Hi

This week we reviewed the modeling design principle and guideline, the draft 
version has been review for 1st round, hope we could finalize it based on 2nd 
round review in this week.
One of core idea is ONAP R2+ modeling will use SDC DM and ECOMP IM as the 
starting point

Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Thursday, October 19, 2017 4:12 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> P 
mailto:onap-tsc@lists.onap.org>>
Cc: onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>
Subject: [onap-tsc] Weekly Report from security subcommittee

Hi,

Here is the report from the security sub-committee to the TSC.

This week we reviewed more updates to the S3P requirements from a security 
perspective to align on the per release text from the security sub-committee 
perspective (the per project was fine).

Discussions on how to use coverity for the static code scanning continue

The topic of credential management is progressing.  The idea is to firm up the 
proposal for recommendation promptly.  The current proposal can be found in 
section 2 of 
https://wiki.onap.org/display/DW/ONAP+security+Recomendation+Developement . 
Comments from the community are most appreciated.

Best Regards,

Steve.

[?? Ericsson]<http://www.ericsson.com/>
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R&D Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>
www.ericsson.com<http://www.ericsson.com>

[?? 
http://www.ericsson.com/current_campaign]<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<http://www.ericsson.com/email_disclaimer>

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

[onap-tsc] [modeling]RE: Usecase subcommittee meeting 23/10/2017 (wide discussion of Network Slicing)

2017-10-20 Thread denghui (L)

This is a reminder email to modeling subcommittee, 5G use case would like to 
invite modeling subcommittee to join their discussion next week,

Thanks

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Friday, October 20, 2017 5:43 PM
To: onap-usecase...@lists.onap.org; onap-...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: [onap-tsc] Usecase subcommittee meeting 23/10/2017 (wide discussion of 
Network Slicing)

Hi all,

Here is agenda for Monday’s meeting.

1.   Short overview of R1 vVoLTE and R-vCPE status and needs

2.   Beijing Release, 5G and network slicing – the next level of details. 
We invite architecture and modelling subcommittees representatives along with a 
different projects representatives to participate and provide their view and 
comments

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.jpg@01D349CC.C14ECF80]


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

[onap-tsc] Beijing release participation - ONAP Modeling

2017-10-25 Thread denghui (L)

Dear TSC,

This email is to formally notify ONAP TSC and community that the Onap modeling 
project plans to be part of the ONAP Beijing release.

Regards,

DENG Hui



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

[onap-tsc] [Modeling] ONAP Modeling workshop proposal

2017-11-02 Thread denghui (L)

Hello all

Modeling subcommittee is in the very tight schedule, plan to have R2 modeling 
ready by December and intends to call for feedback from SDOs and identify 
potential cooperation areas. And many SDOs propose to collaborate with ONAP 
such as MEF/TMF/ETSI NFV, and in order to avoid the confliction with other 
sessions in Forum, propose to have 1 day workshop right after Forum.

Program could be:
u ONAP modeling overview
u SDOs input & feedback
u Collaboration discussion

Time: Dec. 14th 2017 (Thursday ）
Location: Because Intel and Cablelabs can’t host it on Thursday, suggest Huawei 
office in Santa Clara

Please kindly help to feedback by the end of this Friday, we are seeking for 
whether there is a serious issue or not.

Thanks a lot for your contribution
Best regards,

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

[onap-tsc] [Modeling] ONAP Modeling workshop proposal -- doodle poll

2017-11-02 Thread denghui (L)

Hello all

I created a doodle poll to check it again:
https://doodle.com/poll/8m5nhagvqkfw2uag

thanks a lot for your input.

Best regards,

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Thursday, November 2, 2017 11:56 PM
To: denghui (L) ; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Cc: 'Rittwik Jana' 
Subject: RE: [Modeling] ONAP Modeling workshop proposal

Hi,

I think this is a really good idea, provided the workshop participants are 
up-to-speed on what we have been doing, where we need to be going and can hit 
the ground running. As you said, time is of the essence…

Kind regards,

Alex Vul
Intel Corporation

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, November 2, 2017 8:50 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: 'Rittwik Jana' mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [Modeling] ONAP Modeling workshop proposal

Hello all

Modeling subcommittee is in the very tight schedule, plan to have R2 modeling 
ready by December and intends to call for feedback from SDOs and identify 
potential cooperation areas. And many SDOs propose to collaborate with ONAP 
such as MEF/TMF/ETSI NFV, and in order to avoid the confliction with other 
sessions in Forum, propose to have 1 day workshop right after Forum.

Program could be:
u ONAP modeling overview
u SDOs input & feedback
u Collaboration discussion

Time: Dec. 14th 2017 (Thursday ）
Location: Because Intel and Cablelabs can’t host it on Thursday, suggest Huawei 
office in Santa Clara

Please kindly help to feedback by the end of this Friday, we are seeking for 
whether there is a serious issue or not.

Thanks a lot for your contribution
Best regards,

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

[onap-tsc] [modeling] ONAP Modeling workshop final decision

2017-11-03 Thread denghui (L)

Hello all

According to doodle poll, there are 25 people prefer Thursday and 10 people 
prefer Tuesday. https://doodle.com/poll/8m5nhagvqkfw2uag

Because time is so urgent, thanks TSC meeting suggestion, let's do below 
arrangement:

1)  Half day or 2 hours ONAP modeling workshop on Tuesday ( For those 
people's topic who are not able to attend Thursday workshop)

2)  1 day ONAP modeling workshop on Thursday

I do believe more people will attend this workshop, will setup the registration 
page asap to accommodate the meeting room and Lunch on Thursday.

Thanks a lot for your attendance
Best regards,

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

[onap-tsc] Beijing release participation - Modeling

2017-11-06 Thread denghui (L)

Dear TSC,

This email is to formally notify the TSC and the ONAP community that Modeling 
Project plans to be a part of the ONAP Beijing release.

Thanks,

DENG Hui

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

[onap-tsc] [modeling] Please help to register ONAP Modeling workshop on Dec. 14th Thursday

2017-11-06 Thread denghui (L)

Hello all

Please don't do poll any more , just register here:
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+20171214+Registration+Page

Please register before Dec. 8th, registrations will be closed on that day. The 
room will be only limited to 50 people.
If we reach that number before that Dec. 8th, then the registration page will 
also be closed.


Please indicate if your have any food preference like Vegetarian, or others,

if you don't want disclose it on the webpage, please email to me 
(denghu...@huawei.com) and May 
(may.c...@huawei.com)

Thanks a lot for your attendance
Best regards,

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

[onap-tsc] Report from ONAP modeling Sub-committee

2017-11-16 Thread denghui (L)

Hi,

Here is the report from the ONAP modeling sub-committee.

In the last two weeks,  modeling subcommittee is mostly working on R2+ 
information and  Data modeling
-Setup workspace for modeling discussion:  (Based on wiki and email 
which will help to resolve language communication issue) 
https://wiki.onap.org/pages/viewpage.action?pageId=16004181
-Once get consensuses on IM and DM , the spec proposal will be moved to 
clean version of each Model.
-Starting from ECOMP IM and SDC DM for R2+ Modeling, try to align ECOMP 
with SDC DM as much as possible.
-Create a wiki page for R2+ Modeling related M3 checking point 
discussion  https://wiki.onap.org/pages/viewpage.action?pageId=16006078
-Create a wiki page for R2+ Modeling naming convention discussion  
https://wiki.onap.org/pages/viewpage.action?pageId=16006107

Thanks for your checking

BR,

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

[onap-tsc] [modeling] today modeling teleconf is cancelled.

2017-11-28 Thread denghui (L)

Hello all

Apologize for not considering thanks giving holiday, lots of people are still 
not yet return back, so we will cancel this week teleconf.

Best regards,

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

[onap-tsc] [Modeling] Modeling session today

2017-12-13 Thread denghui (L)

Hello all

This is the day before tomorrow workshop, today session related to modeling 
will be :


1)  11:20 Considerations of Modelling Evolution in ONAP 

Michela Bevilacqua
Room: Auditorium


2)  1:45pm- 3:15pm Modeling subcommittee for R2+ SPEC

Room: 152

Agenda:

DM - David (30min)

IM/DM progress report -Lingli (20min)

IM new proposal, - Kevin (30min)


3)  3:30 - 4:15

Modeling NFV Deployment Flavor discussion
Room: 175


4)  4:15 - 4:50 Deployment Flavor for NFV Modeling - Challenges and Trends 


Pyria T.G

Room: 152

Anyway, we have workshop tomorrow,
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+20171214+Registration+Page

Thanks a lot for your attendance
Best regards,

DENG Hui

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

[onap-tsc] [Modeling] Modeling session today - Update

2017-12-13 Thread denghui (L)

Hello all



There is one mistake, updated again

1)  11:20 Considerations of Modelling Evolution in ONAP 


Michela Bevilacqua

Room: Auditorium

https://onapbeijing2017.sched.com/event/D5pe/considerations-of-modelling-evolution-in-onap


2)  1:45pm- 3:15pm Modeling subcommittee for R2+ SPEC
https://onapbeijing2017.sched.com/event/D7Kv/modeling-subcommittee-for-r2model

Room: 152

Agenda:

DM - David (30min)

IM/DM progress report -Lingli (20min)

IM new proposal, - Kevin (30min)


3)  3:30 - 4:15

Modeling NFV Deployment Flavor discussion

https://onapbeijing2017.sched.com/event/00c8844e7f69f2ef7a12b1f359792d39/Modeling+Deployment+Flavor+in+Modeling+Subcommittee
Room: 174


4)  4:15 - 4:50 Deployment Flavor for NFV Modeling - Challenges and Trends 

https://onapbeijing2017.sched.com/event/DAHm

Pyria T.G

Room: 152

Anyway, we have workshop tomorrow,
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+20171214+Registration+Page

Thanks a lot for your attendance
Best regards,

DENG Hui

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

[onap-tsc] [modeling]Zoom ID for ONAP modeling workshop

2017-12-14 Thread denghui (L)

Hello all

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/349619781
 Or iPhone one-tap : US: +16699006833,,349619781# or +16465588656,,349619781# 
Or Telephone: Dial(for higher quality, dial a number based on your current 
location)? US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll 
Free) or +1 855 880 1246 (Toll Free) Meeting ID: 349 619 781 International 
numbers available: 
https://zoom.us/zoomconference?m=LF_IFaE8tqx1uINPhUk2FGmc_M9ohwO1

Thanks

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

[onap-tsc] [modeling] ONAP modeling workshop program

2017-12-14 Thread denghui (L)

Hello all

There is a small change to let Kevin present first about IM then let SDO to 
discuss it later.
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+Program

Thanks a lot

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

[onap-tsc] SDO slides in ONAP Forum this week

2017-12-14 Thread denghui (L)

Hello all

Please check the enclosed slide for SDOs, thanks a lot for your checking
https://wiki.onap.org/display/DW/External+SDO+session+in+ONAP+Forum+Dec.+12th%2C+2017

Really thanks MEF/TMF/ETSI NFV/OASIS TOSCA/IETF/ONF for kind help

Thursday workshop slide will be posted on Thursday program page.

Best regards,

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

[onap-tsc] [modeling] ONAP Modeling workshop notes

2017-12-18 Thread denghui (L)

Hello All

ONAP Modeling workshop minutes

1   Service IM: back to service(customer facing service)/service 
component(resource facing service, e.g. network service)/resource/resource 
component layering class diagram, not using composite/decorative pattern for 
Beijing, translate into papyrus format based on agreed clean version.

2   Resource IM: For design time model, agreed to work on a subset of 
IFA011 for Beijing (i.e. remove internalCP as show in the discussion page), 
agreed to add hierarchy for CP inheritance, agreed to work on the latest 
version of IFA011 (v2.3.1). For run time model, agreed to refactor some of the 
attributes (e.g., ip addresses).

3   Design time DM: Agreed on Service and Resource hierarchy, while both 
service and resource can leverage substitution mapping mechanism to realize 
self-recursion aggregation or composition relations if needed by the IM.

4   Runtime DM A&AI will update NFV related API? in order to align with 
Information model, and notify the related project accordingly

5   Agreed to work on a concrete example to show how ONAP IM maps to ONAP 
DM.

6   R2 will be based on TOSCA simple profile 1.1 other than 1.2, but may 
need to consider some special feature of 1.2 if needed by the use case

7   Each DF should be described in a single TOSCA Service template (VNFD) 
and considered as a single VNF, in Beijing release, one VNF package will only 
contain one VNFD

8   R2+ Modeling spec naming convention will use the low camel for 
attribute names, will consider to add naming convention check during M1/M4

9   WiKi will be used for Modeling spec intermediate version,  Readthedoc 
will be used for published version

10Michela volunteer to start to work on the common terminologies for ONAP 
modeling

11Modeling spec will be migrate to Papyrus asap, needs to decide version 
number and setup the timeline to proceed it

12Use Jira/backlog to track the work asap

Thanks for your checking
Best regards

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

[onap-tsc] [modeling] ONAP modeling tool Papyrus trianing session

2018-01-04 Thread denghui (L)

Hello all

We are very honor to invite Nigel Davis to give a tutorial about Papyrus which 
will be used for ONAP Info modeling.
Since Modeling subcommittee is full of schedule every week. We arrange this 
tutorial on this Friday VNFSDK Modeling sub-team session.
https://wiki.onap.org/display/DW/2017-12-22+Meeting+notes

Andy, could you kind help to post zoom ID and time here?

Please come and join us
Best regards,

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

[onap-tsc] remove the committer whose email is invalid

2018-01-17 Thread denghui (L)

Hello all

Does anybody know that I could remove the committer if that email address is 
not valid anymore?

Thanks a lot for your advice

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

[onap-tsc] [modeling] the training videos of Papyrus have been updated

2018-01-19 Thread denghui (L)

Hello all

Many thanks to Nigel who has kindly help to update all videos, please feel free 
to study them online.
https://wiki.onap.org/display/DW/Modeling+tools

Best regards,

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

[onap-tsc] [modeling] Whether How and when we should move to Github for modeling spec update process

2018-01-31 Thread denghui (L)

Hello modeling subcommittee,

Many Thanks to Jessie's kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

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

[onap-tsc] [modeling]Modeling call next week

2018-02-02 Thread denghui (L)

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)
Let me know if you have any other suggestions.

Thanks a lot

DENG Hui

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

Re: [onap-tsc] [modeling]Modeling call next week

2018-02-02 Thread denghui (L)

Hi Kenny

From latest program: https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2017
We are starting from 9:30am eastern time , which is 10:30pm Beijing time

Thanks  a lot for your reminder

Best regards,

DENG Hui

From: Kenny Paul [mailto:kp...@linuxfoundation.org]
Sent: Saturday, February 3, 2018 3:29 AM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org P 
; Rittwik Jana ; 邓灵莉 

Subject: Re: [modeling]Modeling call next week

Hi Deng,
I'll cxl next week's call even though these requests should always be routed 
throgh the wiki page
Meeting Requests, Changes, Hosting & 
Recording<https://wiki.onap.org/pages/viewpage.action?pageId=8231933>

I don’t understand the sentence that follows however. Not sure if this is a 
request for a change, or what the intent is.
>> we will have our modeling subcommittee session on Wednesday 9am eastern 
>> time, 10pm Beijing time.

Thanks!

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
510.766.5945


On Feb 2, 2018, at 4:46 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)

Let me know if you have any other suggestions.



Thanks a lot



DENG Hui



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

Re: [onap-tsc] [modeling] Whether How and when we should move to Github for modeling spec update process

2018-02-05 Thread denghui (L)

Hi Brian

Yes, could you kindly help to do it under modeling tools wiki page?

Thanks a lot for your help
Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Friday, February 2, 2018 11:12 PM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org P 
; jessie jewitt 
Subject: Re: [modeling] Whether How and when we should move to Github for 
modeling spec update process

Hi Deng,
I'm in favor of using Git for model development.
Do we want to add a Poll page to the wiki to track participant voting on this 
topic?

Thanks
Brian

On Wed, Jan 31, 2018 at 7:31 PM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hello modeling subcommittee,

Many Thanks to Jessie’s kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

DENG Hui



--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology<http://oam.technology>
brian.hedst...@oamtechnologies.com<mailto: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] [modeling] 20180213 modeling subcommittee Meeting Minutes

2018-02-13 Thread denghui (L)

Hello all

Modeling subcommittee has been questioned when will our modeling DM spec come 
out, below are our meeting minutes this week.

Hi Kenny, We are going to cancel next week modeling subcommittee call due to 
china new year, thanks a lot for your help

-
20180213 modeling subcommittee Meeting agenda and Minutes
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

1)  Resource IM YANG Xu
there is no consensus whether we need to follow ETSI NFV naming convention or 
change into ONAP naming.
Two polls will be set to decide the naming convention and future meeting time. 
The polls close on Feb 28th.
https://wiki.onap.org/display/DW/Meeting+Time+Poll
https://wiki.onap.org/display/DW/Naming+Convention+Poll

2)  Data modeling Anatoly Katzman
DENG Hui: modeling subcommittee have to finalize the 1st draft version by M3 
deadline, in this case, we need to allow solutions only 1 week, and make the 
decision on Feb. 28th.
DENG Hui: there are two solutions on the table now: Monolithic VDU design and 
TOSCA NFV profile, we are not make decision today, but would get basic impress 
what company would like to follow:
Vendors:
1) Ericsson  vote for  of ETSI NFV Profile
2) ZTE   vote for  ETSI SOL NFV profile
3) Huawei vote for  ETSI NFV profile
4) Nokia --no one on call
5) Netcracker (Priya TG) vote for ETSI NFV Profile
Operators:
1) AT&T: Monolithic VDU
2) China Mobile: lacking information to do an informed comparison hence no 
strong opinion to any specific proposal currently. The options on the table 
should firstly meet the requirement as a unified DM in the community with 
consistency to the IM and implementable in Beijing release cadence with vendors 
support. It would be better if we could align with SDO in the same time.
Next step:
a) check whether we have 3rd solution or not in a week
b) make decision on Feb.27th

3) Modeling tool poll(Jessie)
1) use github for papyrus revision
fine from IM's team (Kevin, Andy, Lingli, and YANG Xu)
Anyway, polling will end by the end of Feb.

Best regards,

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

[onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI NFV ISG

2018-02-22 Thread denghui (L)

Hello all

Based on email discussion, enclosed draft liaison from modeling subcommittee to 
ETSI NFV ISG is as the enclosed.

Thanks a lot for you review

Best regards,

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

Re: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI NFV ISG

2018-02-24 Thread denghui (L)

Hi Steven

Your suggestion sounds reasonable, I will do wiki and send an informal email to 
the ETSI NFV list before next Monday

Best regards,

DENG Hui

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Friday, February 23, 2018 4:07 PM
To: denghui (L) ; onap-disc...@lists.onap.org; onap-tsc 

Cc: Rittwik Jana 
Subject: RE: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to 
ETSI NFV ISG

Hi Deng,

In the previous TSC when there was a discussion about liaisons it was pointed 
out that some work was required as there is no liaison relationship 
established, I guess that hasn't happened.  When it comes to the liaisons that 
say "please take consideration of my work" they don't mean much as the real 
work has to be driven by the work items etc by the participants there.  I 
assume that the goal of the LS is to have a place to raise the issue of 
evolution of the specs.  You could acthieve that by having a status wiki in 
modelling and a friendly informal email to the etsi lists pointing to it.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, February 22, 2018 1:23 PM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: Rittwik Jana mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI 
NFV ISG

Hello all

Based on email discussion, enclosed draft liaison from modeling subcommittee to 
ETSI NFV ISG is as the enclosed.

Thanks a lot for you review

Best regards,

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

Re: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI NFV ISG

2018-02-24 Thread denghui (L)

Hello modelers

Below page has been created:
https://wiki.onap.org/display/DW/20180225+Progress+summary

feel free to comment if any update are needed.

Thanks a lot

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of denghui (L)
Sent: Sunday, February 25, 2018 8:48 AM
To: Stephen Terrill ; 
onap-disc...@lists.onap.org; onap-tsc 
Cc: Rittwik Jana 
Subject: Re: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to 
ETSI NFV ISG

Hi Steven

Your suggestion sounds reasonable, I will do wiki and send an informal email to 
the ETSI NFV list before next Monday

Best regards,

DENG Hui

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Friday, February 23, 2018 4:07 PM
To: denghui (L) mailto:denghu...@huawei.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: Rittwik Jana mailto:rittwik.j...@gmail.com>>
Subject: RE: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to 
ETSI NFV ISG

Hi Deng,

In the previous TSC when there was a discussion about liaisons it was pointed 
out that some work was required as there is no liaison relationship 
established, I guess that hasn't happened.  When it comes to the liaisons that 
say "please take consideration of my work" they don't mean much as the real 
work has to be driven by the work items etc by the participants there.  I 
assume that the goal of the LS is to have a place to raise the issue of 
evolution of the specs.  You could acthieve that by having a status wiki in 
modelling and a friendly informal email to the etsi lists pointing to it.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, February 22, 2018 1:23 PM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: Rittwik Jana mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI 
NFV ISG

Hello all

Based on email discussion, enclosed draft liaison from modeling subcommittee to 
ETSI NFV ISG is as the enclosed.

Thanks a lot for you review

Best regards,

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

[onap-tsc] [modeling] ONAP modeling subcommittee call meeting minutes

2018-02-27 Thread denghui (L)

Hello all

The meeting minutes is here:
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings
copy below

I am sending out poll on day of modeling workshop today

Best regards,

DENG Hui
20180227 Meeting agenda and Minutes

Deadline for modeling spec is M3: Mar. 7th

Implementation of model spec will be before M4

Modeling workshop is needed during ONS 2018, poll on Sunday or Friday

1)DM:   Anatoly Katzman (Anatoly is absent due to traveling, Deng 
Hui help to lead the discussion)

1.1) AT&T suggest to keep Heat support , agreed

1.2) two tosca proposal on the table

   a) 
https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile

   b) 
https://wiki.onap.org/display/DW/Data+Model+Compliance+with+ETSI

Consensus a) will be R2, b) will be a new proposal for R3+  (Intel question 
whether we need b) proposal)

   Intel: support SOL001/TOSCA NFV DM or code contributor

   ARM: support SOL001

   AT&T(Andy) support TOSCA NFV DM for onboarding,  along with Heat

   Nokia:  support SOL001, code contributor(check)

   Ericsson: support SOL 001/TOSCA NFV DM ,code(check)

   Netcracker?

   Huawei support SOL001/TOSCA NFV DM code contributor

   ZTE:  support SOL001/TOSCA NFV DM code contributor

   China Mobile support TOSCA NFV DM code contributor

Comments:

a) current ONAP IM is more than IFA 11, we need to follow ONAP spec

b) China Mobile question on SOL001 IPR issue, OASIS TOSCA is more IPR 
friendly.

2)Resource IM: Xu Yang

  community agreed to do majority vote for the not agreed attributes in the 
end.

  YANG Xu will organize the call on wednesday and thursday, then put vote 
spreedsheet on the wiki about the left issues. End of vote will be Monday

  company who disagree with some attbiutes will be recorded



3)Service IM:Lingli Deng/Maopeng Zhang

  Lingli and Maopeng will make R2 proposal asap.



4) Others (no time to discuss)

  Parser:Atul Purohit

  Modeling tools: Nigel Davis,

  Modeling spec Papyrus: Jessie Jewitt

  A&AI James Forsyth

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

[onap-tsc] [modeling]Poll on modeling workshop in ONS 2018

2018-02-27 Thread denghui (L)

Hello all

Please cast your vote on the date of workshop for modeling workshop in ONS 2018
https://doodle.com/poll/a95qs5bg5fwmskdg

Thanks a lot

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

1 2 3 >

1 - 100 of 200 matches

Mail list logo