Re: [onap-tsc] MEF and ONAP coordination

[Alla Goldner]

We need to also coordinate our communication with both streams, even if we keep 
them separately as Open source and Standards activities.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2FF94.2647AD40]

From: John Strassner [mailto:straz...@gmail.com]
Sent: Tuesday, July 18, 2017 12:53 AM
To: Brian Hedstrom 
Cc: Alla Goldner ; t...@lists.onap.org
Subject: Re: [onap-tsc] MEF and ONAP coordination

I agree with Brian. In fact, the standards activities are a separate division 
from the open source work, though the two areas do talk to each other. :-)

regards,
John

On Mon, Jul 17, 2017 at 1:25 PM, Brian Hedstrom 
> 
wrote:
I think it depends upon how these two ONAP Coordination groups will be managed 
and executed.  MEF provides both standards activities and open source LSO 
activities.  If we merge them into the Standards activities, it might fall off 
the radar for the Open Source Coordination group.

Thanks
Brian

On Sun, Jul 16, 2017 at 4:16 AM, Alla Goldner 
> wrote:
Hi all,

Currently, ONAP/MEF coordination appears twice – both in standards and in Open 
source coordination 
(https://wiki.onap.org/display/DW/External+Standard+Coordination and 
https://wiki.onap.org/display/DW/External+Open+Source+Community+Coordination)

I believe it should be merged altogether to the standards section.

What do you think?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2FF94.2647AD40]

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



--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oamtechnologyconsulting.com
brian.hedst...@oamtechnologies.com
720-470-7091

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



--
regards,
John
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] [ptls][cli][msb][aaf] Review ONAPfunctionalites to support from CLI

[zhao.huabing]

Hi Kanagaraj,




Sure. 

Currently, we're mainly using the AAF weekly meeting to discuss the integration 
between AAF and MSB.

The conclusion of the last meeting is that AAF will add a Lua plugin which can 
provide centralized auth at the MSB external API  gateway.




I will add you in the loop for theurther discussion.




BR,

Huabing






Original Mail



Sender:  
To:   
CC:     
 
Date: 2017/07/17 21:51
Subject: Re: [onap-discuss] [onap-tsc] [ptls][cli][msb][aaf] Review 
ONAPfunctionalites to support from  CLI







Dear Huabing,


 


CLI project would depends on the MSB for service discovery and AAF for AA. So I 
have gone thru  the MSB release planning from wiki and found that your are 
planning to integrate AAF as one of the Auth service  provider in MSB.


IMO, It’s an right integration and as CLI also would get impacted (for AA), I 
would like to participate the discussion around this integration. Could you 
please keep me in the loop. Thanks.


 


Regards


Kanagaraj M


 


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



 



From: 杨艳 [mailto:yangya...@chinamobile.com] 
 Sent: Monday, July 17, 2017 9:27 AM
 To: Kanagaraj Manickam onap-disc...@lists.onap.org
 Cc: rk5...@att.com ah0...@intl.att.com gg2...@att.com es4...@att.com 
sw3...@att.com onap-tsc@lists.onap.org
 Subject: 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from 
CLI




 


Sorry for late response. There is no problem from my perspective.


 


Regards,


Yan



发件人: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] 
 发送时间: 2017年7月13日  22:41
 收件人: 杨艳 onap-disc...@lists.onap.org
 抄送: rk5...@att.com ah0...@intl.att.com gg2...@att.com es4...@att.com 
sw3...@att.com onap-tsc@lists.onap.org
 主题: RE: [onap-tsc] [ptls][cli] Review ONAP functionalites to  support from CLI




 


Hi Yan,


 


Thanks for reviewing.


I tried add related projects for every feature listed in the wiki. For example, 
VNFM and EMS are used by VFC but are on-boarded  using A/ESR, So mentioned 
VFC as well.


As it creates confusion on the project column, I updated the wiki to keep only 
the dependent project, which provides the functionalities.


Could you please review it once? Thanks.


 


Regards


Kanagaraj M


 


 


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



 



From: 杨艳 [mailto:yangya...@chinamobile.com] 
 Sent: Thursday, July 13, 2017 12:07 PM
 To: Kanagaraj Manickam onap-disc...@lists.onap.org
 Cc: rk5...@att.com ah0...@intl.att.com gg2...@att.com es4...@att.com 
sw3...@att.com onap-tsc@lists.onap.org
 Subject: 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from 
CLI




 


Hi Kanagaraj,


 


I read the wiki page you mentioned, for the External Resource Management part, 
VFC has been listed in the VNFM and EMS management, I’m not very clear what the 
meaning of the projects list here, but I would like to clarify that VF-C will 
only use the  information  of VNFM and  EMS as a consumer, such as url, user 
name, etc.


 


 


Regards,

[onap-tsc] What Do You Need From The July Developers Event?

[Kenny Paul]

The July Virtual Developers Event is next week and your contributions are what 
will drive all of these sessions.

As Phil Robb mentioned at the close of the PTL call this morning, we are 
looking to the community to suggest topics for discussion which we will use to 
build the agenda from.  Ideally these are areas where you need a deeper 
understanding of in order to make progress, or deep-dive information sharing in 
a particular area you wish to provide.  It is critically important to extract a 
list of questions/decisions/agreements that each project needs to close on so 
that they can successfully execute their development cycle for Amsterdam.  

The following wiki page has been created for this purpose: DISCUSSION TOPICS / 
QUESTIONS 

To to add a new topic please provide your project name and topic using the 
template provided on the wiki page. If there is a topic that you would like 
discussed, but you do not feel that you can lead it, please add the topic and 
indicate that you are "Interested in Attending", then indicate TBD as the 
"Topic Leader”. 

For any existing topic(s) you would like to lead and/or attend simply add your 
name to the list as appropriate.  

The page has been populated with a few topics based upon input we have already 
received.

Thank you in advance for your contributions and participation.

Best Regards, 
-kenny

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

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

Re: [onap-tsc] MEF and ONAP coordination

[John Strassner]

I agree with Brian. In fact, the standards activities are a separate
division from the open source work, though the two areas do talk to each
other. :-)

regards,
John

On Mon, Jul 17, 2017 at 1:25 PM, Brian Hedstrom <
brian.hedst...@oamtechnologies.com> wrote:

> I think it depends upon how these two ONAP Coordination groups will be
> managed and executed.  MEF provides both standards activities and open
> source LSO activities.  If we merge them into the Standards activities, it
> might fall off the radar for the Open Source Coordination group.
>
> Thanks
> Brian
>
> On Sun, Jul 16, 2017 at 4:16 AM, Alla Goldner 
> wrote:
>
>> Hi all,
>>
>>
>>
>> Currently, ONAP/MEF coordination appears twice – both in standards and in
>> Open source coordination (https://wiki.onap.org/display
>> /DW/External+Standard+Coordination and https://wiki.onap.org/display/
>> DW/External+Open+Source+Community+Coordination)
>>
>>
>>
>> I believe it should be merged altogether to the standards section.
>>
>>
>>
>> What do you think?
>>
>>
>>
>> Best regards,
>>
>>
>>
>> *Alla Goldner*
>>
>>
>>
>> Open Network Division
>>
>> Amdocs Technology
>>
>>
>>
>>
>>
>>
>> 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
>>
>>
>
>
> --
> Brian Hedstrom
> Founder/CEO
> OAM Technology Consulting LLC
> oamtechnologyconsulting.com
> brian.hedst...@oamtechnologies.com
> 720-470-7091 <(720)%20470-7091>
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
>


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

Re: [onap-tsc] MEF and ONAP coordination

[Brian Hedstrom]

I think it depends upon how these two ONAP Coordination groups will be
managed and executed.  MEF provides both standards activities and open
source LSO activities.  If we merge them into the Standards activities, it
might fall off the radar for the Open Source Coordination group.

Thanks
Brian

On Sun, Jul 16, 2017 at 4:16 AM, Alla Goldner 
wrote:

> Hi all,
>
>
>
> Currently, ONAP/MEF coordination appears twice – both in standards and in
> Open source coordination (https://wiki.onap.org/
> display/DW/External+Standard+Coordination and
> https://wiki.onap.org/display/DW/External+Open+Source+
> Community+Coordination)
>
>
>
> I believe it should be merged altogether to the standards section.
>
>
>
> What do you think?
>
>
>
> Best regards,
>
>
>
> *Alla Goldner*
>
>
>
> Open Network Division
>
> Amdocs Technology
>
>
>
>
>
>
> 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
>
>


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

Re: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project

[Amir Levy]

+1


-- amir

> On Jul 15, 2017, at 3:05 AM, Kenny Paul  wrote:
> 
> 
> In an effort to try and minimize the level of email traffic on this list this 
> approval was originally attempted this as a CIVS poll. Unfortunately quorum 
> was not achieved.
> As such I’m falling back to an email vote to provide members that did not 
> participate the opportunity to do so.
> 
> From the TSC Charter:
> 3.2.2 CommitterLifecycle
> 3.2.2.1 Adding Committers
> Initial Committers for a project will be specified at project creation
> Committer rights for a project are earned via contribution and community 
> trust. Committers for a project select and vote for new Committers for that 
> project, subject to TSC approval.
> New Committers for a project should have a demonstrable established history 
> of meritocratic contributions. 
> 
> TSC approval is requested for the following changes to the ONAP Portal 
> Platform Project: https://wiki.onap.org/display/DW/Portal+Platform+Project 
>   - Add "Sunder Tatta”(sta...@research.att.com) as a committer (Only a 
> single committer currently on the project) 
>   - Add a new repository “portal/sdk”
> 
> ACTION:
> I approve the committer addition (Vote +1, 0, -1) 
> I approve the repository addition (Vote +1, 0, -1)
> 
> 
> 
> Votes already cast are all in favor of approving both the committer and 
> repository additions.
> mg1...@att.com:   1   
> 
> 
> jamil.cha...@orange.com:  1   
> 
> 
> meng.zhaoxi...@zte.com.cn:1   
> 
> 
> aayush.bhatna...@ril.com: 1   
> 
> 
> stephen.terr...@ericsson.com: 1   
> 
> 
> ranny.ha...@nokia.com:1
> 
> 
> 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 mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [ptls][cli][msb][aaf] Review ONAP functionalites to support from CLI

[Kanagaraj Manickam]

Dear Huabing,

CLI project would depends on the MSB for service discovery and AAF for AA. So I 
have gone thru  the MSB release planning from wiki and found that your are 
planning to integrate AAF as one of the Auth service provider in MSB.
IMO, It’s an right integration and as CLI also would get impacted (for AA), I 
would like to participate the discussion around this integration. Could you 
please keep me in the loop. Thanks.

Regards
Kanagaraj M

***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

From: 杨艳 [mailto:yangya...@chinamobile.com]
Sent: Monday, July 17, 2017 9:27 AM
To: Kanagaraj Manickam; onap-disc...@lists.onap.org
Cc: rk5...@att.com; ah0...@intl.att.com; gg2...@att.com; es4...@att.com; 
sw3...@att.com; onap-tsc@lists.onap.org
Subject: 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from 
CLI

Sorry for late response. There is no problem from my perspective.

Regards,
Yan
发件人: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
发送时间: 2017年7月13日 22:41
收件人: 杨艳; onap-disc...@lists.onap.org
抄送: rk5...@att.com; 
ah0...@intl.att.com; 
gg2...@att.com; es4...@att.com; 
sw3...@att.com; 
onap-tsc@lists.onap.org
主题: RE: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from CLI

Hi Yan,

Thanks for reviewing.
I tried add related projects for every feature listed in the wiki. For example, 
VNFM and EMS are used by VFC but are on-boarded  using A/ESR, So mentioned 
VFC as well.
As it creates confusion on the project column, I updated the wiki to keep only 
the dependent project, which provides the functionalities.
Could you please review it once? Thanks.

Regards
Kanagaraj M


***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

From: 杨艳 [mailto:yangya...@chinamobile.com]
Sent: Thursday, July 13, 2017 12:07 PM
To: Kanagaraj Manickam; 
onap-disc...@lists.onap.org
Cc: rk5...@att.com; 
ah0...@intl.att.com; 
gg2...@att.com; es4...@att.com; 
sw3...@att.com; 
onap-tsc@lists.onap.org
Subject: 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from 
CLI

Hi Kanagaraj,

I read the wiki page you mentioned, for the External Resource Management part, 
VFC has been listed in the VNFM and EMS management, I’m not very clear what the 
meaning of the projects list here, but I would like to clarify that VF-C will 
only use the  information of VNFM and  EMS as a consumer, such as url, user 
name, etc.


Regards,
Yan
发件人: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] 代表 Kanagaraj Manickam
发送时间: 2017年7月12日 21:02
收件人: onap-disc...@lists.onap.org
抄送: rk5...@att.com; 
ah0...@intl.att.com; 
gg2...@att.com; es4...@att.com; 

Re: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from CLI

[Lando,Michael]

+Eden,Zahi


BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT 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


From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Wednesday, July 12, 2017 4:02 PM
To: onap-disc...@lists.onap.org
Cc: Gildas Lanilis ; onap-tsc@lists.onap.org; 
GLOVER, GREG L ; Lando,Michael ; WRIGHT, 
STEVEN A ; Ngueko, Gervais-Martial ; 
lxin...@vmware.com; denglin...@chinamobile.com; FORSYTH, JAMES 
; Yunxia Chen ; Hemli, Amichai 
; david.sauvag...@bell.ca; MAYER, ANDREW J 
; TALASILA, MANOOP ; TIMONEY, DAN 
; MAHER, RANDA ; denghui (L) 
; wangchen...@chinamobile.com; shen...@chinamobile.com; 
KOYA, RAMPRASAD ; pr...@linuxfoundation.org; Gildas Lanilis 
; denghu...@hotmail.com; 
stephen.terr...@ericsson.com; SUNDELOF, ERIK ; 
cc...@linuxfoundation.org; fu.guangr...@zte.com.cn; DRAGOSH, PAM 
; PUTHENPURA, SARAT ; JI, 
LUSHENG ; POND, MARK ; Seshu m 

Subject: [ptls][cli] Review ONAP functionalites to support from CLI

Dear PTLs,

From ONAP wiki, I have gone thru the Use-cases defined for release A and based 
on my understanding,
captured the minimum-required-top level functionalities in the wiki  
https://wiki.onap.org/display/DW/CLI+Functionalities

For each of the functionality, I tried to match them with respective project.
Could you please review them, provide your approvals/feedbacks. Thank you.

Regards
Kanagaraj M


***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

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

Re: [onap-tsc] TSC Members- Action Required Approval of changes to thePortal Platform Project

[Xinhui Li]

+1

Xinhui

From:  on behalf of 
"meng.zhaoxi...@zte.com.cn" 
Date: Monday, 17 July 2017 at 4:56 PM
To: "kp...@linuxfoundation.org" 
Cc: "sta...@research.att.com" , 
"onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] TSC Members- Action Required Approval of changes to 
thePortal Platform Project


[VOTE] +1








Original Mail
Sender:  ;
To:  ;
CC:  ;
Date: 2017/07/15 08:05
Subject: [onap-tsc] TSC Members- Action Required Approval of changes to 
thePortal Platform Project



In an effort to try and minimize the level of email traffic on this list this 
approval was originally attempted this as a CIVS poll. Unfortunately quorum was 
not achieved.
As such I’m falling back to an email vote to provide members that did not 
participate the opportunity to do so.

From the TSC Charter:
3.2.2 CommitterLifecycle
3.2.2.1 Adding Committers

· •Initial Committers for a project will be specified at project 
creation

· Committer rights for a project are earned via contribution and 
community trust. Committers for a project select and vote for new Committers 
for that project, subject to TSC approval.

· New Committers for a project should have a demonstrable established 
history of meritocratic contributions.

TSC approval is requested for the following changes to the ONAP Portal Platform 
Project: 
https://wiki.onap.org/display/DW/Portal+Platform+Project
- Add "Sunder Tatta”(sta...@research.att.com) 
as a committer (Only a single committer currently on the project)
- Add a new repository “portal/sdk”
ACTION:
I approve the committer addition (Vote +1, 0, -1)
I approve the repository addition (Vote +1, 0, -1)


Votes already cast are all in favor of approving both the committer and 
repository additions.
mg1...@att.com:

1

jamil.cha...@orange.com:

1

meng.zhaoxi...@zte.com.cn:

1

aayush.bhatna...@ril.com:

1

stephen.terr...@ericsson.com:

1

ranny.ha...@nokia.com:

1



Best Regards,
-kenny

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





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

Re: [onap-tsc] TSC Members- Action Required Approval of changes to thePortal Platform Project

[meng.zhaoxing1]

[VOTE] +1

















Original Mail



Sender:  
To:  
CC:  
Date: 2017/07/15 08:05
Subject: [onap-tsc] TSC Members- Action Required Approval of changes to 
thePortal Platform Project






In an effort to try and minimize the level of email traffic on this list this 
approval was originally attempted this as a CIVS poll. Unfortunately quorum was 
not achieved.

As such I’m falling back to an email vote to provide members that did not 
participate the opportunity to do so.

From the TSC Charter:
3.2.2 CommitterLifecycle3.2.2.1 Adding CommittersInitial Committers for a 
project will be specified at project creation

Committer rights for a project are earned via contribution and community trust. 
Committers for a project select and vote for new Committers for that project, 
subject to TSC approval.

New Committers for a project should have a demonstrable established history of 
meritocratic contributions. 

TSC approval is requested for the following changes to the ONAP Portal Platform 
Project: https://wiki.onap.org/display/DW/Portal+Platform+Project 
- Add "Sunder Tatta”(sta...@research.att.com) as a committer (Only a 
single committer currently on the project) 

- Add a new repository “portal/sdk”

ACTION:
I approve the committer addition (Vote +1, 0, -1)   

I approve the repository addition (Vote +1, 0, -1)
Votes already cast are all in favor of approving both the committer and 
repository additions.

mg1...@att.com:1jamil.cha...@orange.com:1meng.zhaoxi...@zte.com.cn:1aayush.bhatna...@ril.com:1stephen.terr...@ericsson.com:1ranny.ha...@nokia.com:1








Best Regards, -kennyKenny Paul,  Technical Program 
Managerkpaul@linuxfoundation.org510.766.5945___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project

[Dhananjay Pavgi]

+1

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png@01CE7323.F2727500]   [ONAP_logo_Sig]
www.techmahindra.com Platinum 
Member. Visit : http://www.onap.org

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Monday, July 17, 2017 1:16 PM
To: Lingli Deng ; 'Kenny Paul' 
; 'onap-tsc' 
Cc: 'TATTAVARADA, SUNDER' 
Subject: Re: [onap-tsc] TSC Members- Action Required Approval of changes to the 
Portal Platform Project

+1

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image004.png@01D2FEFF.940978D0]

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Monday, July 17, 2017 10:28 AM
To: 'Kenny Paul' >; 
'onap-tsc' >
Cc: 'TATTAVARADA, SUNDER' 
>
Subject: Re: [onap-tsc] TSC Members- Action Required Approval of changes to the 
Portal Platform Project

[VOTE] +1

Lingli

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: 2017年7月15日 8:05
To: onap-tsc >
Cc: TATTAVARADA, SUNDER 
>
Subject: [onap-tsc] TSC Members- Action Required Approval of changes to the 
Portal Platform Project


In an effort to try and minimize the level of email traffic on this list this 
approval was originally attempted this as a CIVS poll. Unfortunately quorum was 
not achieved.
As such I’m falling back to an email vote to provide members that did not 
participate the opportunity to do so.

From the TSC Charter:
3.2.2 CommitterLifecycle
3.2.2.1 Adding Committers

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

TSC approval is requested for the following changes to the ONAP Portal Platform 
Project: https://wiki.onap.org/display/DW/Portal+Platform+Project
   - Add "Sunder 
Tatta”(sta...@research.att.com) as a committer 
(Only a single committer currently on the project)
   - Add a new repository “portal/sdk”
ACTION:
I approve the committer addition (Vote +1, 0, -1)
I approve the repository addition (Vote +1, 0, -1)


Votes already cast are all in favor of approving both the committer and 
repository additions.
mg1...@att.com:

1

jamil.cha...@orange.com:

1

meng.zhaoxi...@zte.com.cn:

1

aayush.bhatna...@ril.com:

1

stephen.terr...@ericsson.com:

1

ranny.ha...@nokia.com:

1



Best Regards,
-kenny

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

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


Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


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

Re: [onap-tsc] TSC Members- Action Required Approval of changes to the Portal Platform Project

[Alla Goldner]

+1

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2FEE9.E8DBF510]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lingli Deng
Sent: Monday, July 17, 2017 10:28 AM
To: 'Kenny Paul' ; 'onap-tsc' 

Cc: 'TATTAVARADA, SUNDER' 
Subject: Re: [onap-tsc] TSC Members- Action Required Approval of changes to the 
Portal Platform Project

[VOTE] +1

Lingli

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: 2017年7月15日 8:05
To: onap-tsc >
Cc: TATTAVARADA, SUNDER 
>
Subject: [onap-tsc] TSC Members- Action Required Approval of changes to the 
Portal Platform Project


In an effort to try and minimize the level of email traffic on this list this 
approval was originally attempted this as a CIVS poll. Unfortunately quorum was 
not achieved.
As such I’m falling back to an email vote to provide members that did not 
participate the opportunity to do so.

From the TSC Charter:
3.2.2 CommitterLifecycle
3.2.2.1 Adding Committers

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

TSC approval is requested for the following changes to the ONAP Portal Platform 
Project: https://wiki.onap.org/display/DW/Portal+Platform+Project
   - Add "Sunder 
Tatta”(sta...@research.att.com) as a committer 
(Only a single committer currently on the project)
   - Add a new repository “portal/sdk”
ACTION:
I approve the committer addition (Vote +1, 0, -1)
I approve the repository addition (Vote +1, 0, -1)


Votes already cast are all in favor of approving both the committer and 
repository additions.
mg1...@att.com:

1

jamil.cha...@orange.com:

1

meng.zhaoxi...@zte.com.cn:

1

aayush.bhatna...@ril.com:

1

stephen.terr...@ericsson.com:

1

ranny.ha...@nokia.com:

1



Best Regards,
-kenny

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

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] Use case subcommittee - agenda for tomorrow's (17/07/2017) meeting

[Lingli Deng]

Hi Alla and team,

 

As you might already note, there is a wiki page that integration team
maintains for usecase related Q

It would be great to have it review and utilized as a track list for
remaining issues.

 

Thanks,

Lingli

 

From: onap-tsc-boun...@lists.onap.org
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: 2017年7月16日 22:22
To: onap-usecase...@lists.onap.org
Cc: onap-tsc 
Subject: [onap-tsc] Use case subcommittee - agenda for tomorrow's
(17/07/2017) meeting

 

Hi all,

 

Here is agenda for tomorrow’s Use case subcommittee meeting. R1 use cases
are of highest priority. We must see if/what is needed to complete use cases
interactions with a different projects this week. 

We will start going over R2 use case only if time permits.

PTLs of a different projects, please indicate before tomorrow’s meeting if
additional clarifications on R1 use cases are needed.

 

Please upload your suggested R2 use cases
https://wiki.onap.org/display/DW/Release+2+Use+Cases, so we can start some
offline discussions as well.

 

1.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required
actions (use cases leaders: vCPE: Kang Xi/Yoav Kluger/Jon Fannar, vVoLTE:
Yang Xe/Chengli Wang/Lingli Deng)
2.  R2 use cases: the initial proposals (list of those mentioned by a
different related email exchanges is here): 

a.  Network Function Change Management
b.  Enterprise vCPE
c.  SD-WAN
d.  SD-LAN
e.  5G

   i.  RAN
deployment

 ii.  E2E
Network Slicing

3.  AOB

 

For your information:

 

1.  No comments were received for Use case subcommittee flow of
operation as documented here
https://wiki.onap.org/display/DW/Usecase+subcommittee
 
2.  Meetings were held discussing use cases implementation with a
different projects. We will go over status of those meetings. List of points
from the last week is as following:

a.  vCPE: 

   i.  Still
under discussion?: 

1.  DCAE/Intel discussion to close packets’ format (please involve Alok
Gupta per his request) 
2.  Interactions with SDC will be further clarified AG> Status. 
3.  SDN-C functional extension will be discussed with SDN-C team 

 ii.
Meeting with SDN-C/SDC/SO covering vCPE service model by Gil Bullard is
scheduled for this Tuesday (relates to points 2 and 3 from the list above)

   iii.  Brian
Freeman started experimenting with onboarding a vCPE VNF with generic unix
machine  heat templates

 

b.  vVoLTE

   i.  There
is request to include model which drives the use case in the vVolTE use case
description

 ii.  A
question on whether vIMS+vEPC is enforced as a single request coming from SO
(i.e. as a single network service or not). It was clarified that it is up to
implementation, as VF-C can support it both ways. The corresponding
clarification should be included in the use case description

   iii.  Still
under discussion?: 

1.  SDC for design time functionality
2.  SDN-C interaction with 3rd party controller
3.  For overlay �C whether Openstack or hardware will be used �C
discussions with Brian Freeman are initiated

 

3.  Following doodle poll results, I sent dedicated mail yesterday. We
are moving to weekly meetings.

 

Best regards, 

 

Alla Goldner

 

Open Network Division 

Amdocs Technology

 

 



 

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] TSC Members- Action Required Approval of changes to the Portal Platform Project

[Lingli Deng]

[VOTE] +1

 

Lingli

 

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: 2017年7月15日 8:05
To: onap-tsc 
Cc: TATTAVARADA, SUNDER 
Subject: [onap-tsc] TSC Members- Action Required Approval of changes to the 
Portal Platform Project

 

 

In an effort to try and minimize the level of email traffic on this list this 
approval was originally attempted this as a CIVS poll. Unfortunately quorum was 
not achieved.

As such I’m falling back to an email vote to provide members that did not 
participate the opportunity to do so.

 

>From the TSC Charter:

3.2.2 CommitterLifecycle
3.2.2.1 Adding Committers

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

 

TSC approval is requested for the following changes to the ONAP Portal Platform 
Project: https://wiki.onap.org/display/DW/Portal+Platform+Project 

   - Add "Sunder Tatta”(sta...@research.att.com 
 ) as a committer (Only a single committer 
currently on the project) 

   - Add a new repository “portal/sdk”

ACTION:

I approve the committer addition (Vote +1, 0, -1)   

I approve the repository addition (Vote +1, 0, -1)

 

 

Votes already cast are all in favor of approving both the committer and 
repository additions.


mg1...@att.com  :

1



jamil.cha...@orange.com  :

1



meng.zhaoxi...@zte.com.cn  :

1



aayush.bhatna...@ril.com  :

1



stephen.terr...@ericsson.com  :

1



ranny.ha...@nokia.com  :

1



 

 

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