Re: [onap-tsc] ONAP-vAccess Project Proposal - Open Source Access Manager for Wireline Access

[Lefevre, Catherine]

Dear TSC,

The ONAP-vAccess project proposal is now posted on the onap wiki
https://wiki.onap.org/display/DW/OpenSource+Access+Management

Best regards
Catherine

From: EL HOUMAIDI, MOUNIRE
Sent: Wednesday, November 29, 2017 2:50 PM
To: onap-tsc@lists.onap.org
Cc: EL HOUMAIDI, MOUNIRE ; Lefevre, Catherine 
; MCDONNELL, BLAINE 
Subject: ONAP-vAccess Project Proposal - Open Source Access Manager for 
Wireline Access

Dear Team,

ONAP-vAccess Project Proposal for the Beijing release.

Regards,
Mounire El Houmaidi
Director Member Technical Staff
Technology Design & Arch.
Advanced Fixed Access Systems
e-mail:  me4...@att.com<mailto:me4...@att.com>
Mobile:  404-394-2815

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

[onap-tsc] Beijing release participation - External API

[Lefevre, Catherine]

Dear TSC,



We would like to confirm that the External API Project will be contributing to 
the Beijing Release of ONAP.

While we are still forming our Beijing Project Plan and Scope, some Beijing 
candidate features for External API include:

·Alignment with MEF Legato and TM Forum APIs

·UML Models (Eclipse Papyrus), API definition (JSON Swagger), and agent 
code for:

o   License Usage

o   Service Catalog

o   Service Ordering

o   Service Inventory

o   Service State Management

o   Service Quality Management


Best regards

Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Beijing release participation - AAF/DMaaP

[Lefevre, Catherine]

Dear TSC,

This email is to formally notify the TSC and the ONAP community that the 
DMaaP/AAF projects plan to be part of the ONAP Beijing release.

Best regards
Catherine


Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Beijing release participation - DCAE

[Lefevre, Catherine]

Dear TSC,

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

Best regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Beijing release participation - APPC

[Lefevre, Catherine]

Dear TSC,

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

Best regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Amsterdam Release - Lesson Learned

[Lefevre, Catherine]

Dear TSC,

The "Amsterdam Release - Lesson Learned" is now posted:
https://wiki.onap.org/download/attachments/15997434/ONAP-Amsterdam%20Release%20Leasson%20Learned_V6.pptx?api=v2

Eric and I, we are looking forward to receiving feedback from the community

Many thanks and regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] [ccsdk]: New repos for CCSDK

[Lefevre, Catherine]

Dear ONAP TSC,

Would it be possible to get your vote off-line concerning this request?
This is also one of the CCSDK M2 milestone items that the CCSDK team needs to 
finalize as soon as possible.

Thanks in advance for your support.

Many thanks & regards
Catherine

From: "TIMONEY, DAN" mailto:dt5...@att.com>>
Date: Friday, July 28, 2017 at 11:44 AM
To: "gildas.lani...@huawei.com" 
mailto:gildas.lani...@huawei.com>>, 
"kp...@linuxfoundation.org" 
mailto:kp...@linuxfoundation.org>>
Subject: New repos for CCSDK

Gildas, Kenny:

The CCSDK team has identified a need for additional Gerrit repositories for 
ONAP release 1.  I added the new ones to the Resource and Repositories wiki 
page.  Here is the list:

dashboard

ccsdk/dashboard

org.onap.ccsdk.dashboard

Dashboard

utils

ccsdk/utils

org.onap.ccsdk.utils

Utilities

platform/blueprints

ccsdk/platform/blueprints

org.onap.ccsdk.platform.blueprints

Blueprints

platform/nbapi

ccsdk/platform/nbapi

org.onap.ccsdk.platform.nbapi

Northbound API

platform/plugins

ccsdk/platform/plugins

org.onap.ccsdk.platform.plugins

Platform plugins

distribution

ccsdk/distribution

org.onap.ccsdk.distribution

CCSDK distribution packaging (e.g. docker containers)



Can I ask you to please get the appropriate approval from the TSC (or let me 
know the procedure to do so myself, if that’s appropriate) so that we can get 
those repositories created?

Thanks!
Dan


Dan Timoney
Principal Technical Staff Member
AT&T
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873

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

Re: [onap-tsc] Migration to *.onap.org

[Lefevre, Catherine]

Good morning Stephen,

Thank you for your feedback.

I will definitively finalize the high level plan as requested and will organize 
a call accordingly in the coming days.
I will also consider Gildas' feedback based on the discussions we had with the 
LF Council.

Best regards
Catherine

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Thursday, August 03, 2017 8:22 PM
To: Lefevre, Catherine ; onap-tsc@lists.onap.org
Subject: RE: Migration to *.onap.org

Hi Catherine,

I can understand the complexities (and this was confirmed internally for me).

I think that there are some basic things we need to cover, already mentioned by 
Gildas, such as removing commented references to what is considered 
proprietary, or owned,  code etc, even if that is not what you are addressing 
below.

What could be good to resolve the discussion is to at a high level, like you 
have, state down the high level options that we have with the associated risks. 
 E.g.
-Initial big bang migration
o   Start now:
§  Move all projects at once
·Advantage: Clean slate for R1
·Risk: several weeks to sort out, release 1 delay unmitigated risk.
§  Move projects one at a time
·Advantage:
o   Controlled migration
·Disadvantage
o   Implication for each project to reference old and new dependancies
o   Time to migration (could it be done by R1 Release)
o   Risk delay to R1 due to stablising after migration
§  Move projects after xxx (code freeze, ...?)
·
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 Lefevre, Catherine
Sent: 01 August 2017 14:07
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Migration to *.onap.org

Dear ONAP TSC,

I fully understand the request about the seed code to be migrated to *.onap.org.
Nevertheless I want to bring to your attention that this request will require 
significant effort (development, testing and infrastructure changes)

  *   Coordinate and update Maven dependencies and links
  *   Update namespaces as required
  *   Change the source code in order to align with *.onap.org for each 
impacted project
  *   Change the development scripts
  *   Review and update automated test cases
  *   Re-adjust the LF infrastructure accordingly, keeping the org.openecomp 
version in place until the end of migration
That way each project can control the pace of migration from org.openecomp -> 
org.onap : especially for the projects that are already based on the previous 
naming.

  *   Review and re-adjust build jobs to be approved by CI-Management project
  *   Create a temporary environment to perform the necessary code changes
  *   Plan the migration in order to avoid any drastic impact on the ONAP 
community
  *   Recreate new docker images and stabilize the complete ONAP Environment
  *   Etc.

Based on past experience (moving from *.att.com to *.openecomp.org), this 
effort can take up to several weeks until the ONAP release is completely 
stabilized
If we pursue in this direction then it is a major risk for our Amsterdam 
release to be completed on time.
We will need to review the scope of ONAP R1 based on our resource capacity.

Or we can develop a complete migration plan as part of our ONAP R1 commitments
And implement this migration in October as part of ONAP R2 preparation.

Is it something we can discuss during our next TSC meeting?

Thanks in advance for your consideration.

Many thanks & regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Migration to *.onap.org

[Lefevre, Catherine]

Dear ONAP TSC,

I fully understand the request about the seed code to be migrated to *.onap.org.
Nevertheless I want to bring to your attention that this request will require 
significant effort (development, testing and infrastructure changes)

·Coordinate and update Maven dependencies and links

·Update namespaces as required

·Change the source code in order to align with *.onap.org for each 
impacted project

·Change the development scripts

·Review and update automated test cases

·Re-adjust the LF infrastructure accordingly, keeping the org.openecomp 
version in place until the end of migration
That way each project can control the pace of migration from org.openecomp -> 
org.onap : especially for the projects that are already based on the previous 
naming.

·Review and re-adjust build jobs to be approved by CI-Management project

·Create a temporary environment to perform the necessary code changes

·Plan the migration in order to avoid any drastic impact on the ONAP 
community

·Recreate new docker images and stabilize the complete ONAP Environment

·Etc.

Based on past experience (moving from *.att.com to *.openecomp.org), this 
effort can take up to several weeks until the ONAP release is completely 
stabilized
If we pursue in this direction then it is a major risk for our Amsterdam 
release to be completed on time.
We will need to review the scope of ONAP R1 based on our resource capacity.

Or we can develop a complete migration plan as part of our ONAP R1 commitments
And implement this migration in October as part of ONAP R2 preparation.

Is it something we can discuss during our next TSC meeting?

Thanks in advance for your consideration.

Many thanks & regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Perform an assessment prior changing any source code repository name

[Lefevre, Catherine]

Dear TSC & Gildas,

If there is a need to change a source code repository name then I would like to 
request that the old source code repository should not be marked read only
until the toolchain/script modifications are successfully performed.

I also want to suggest consulting PTL and committers prior any change so they 
can provide a better assessment of any impact.
It will help to avoid issue like we have encountered after the 'mso' source 
code repository was changed to 'so'  (i.e. https://jira.onap.org/browse/SO-21)
Is it something we could track under our ONAP best practices?

Thanks in advance for your consideration.

Best regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Project Review in China

[Lefevre, Catherine]

Dear TSC,

We have a special request to ask you.
Several "Project Review" slots have been identified as part of the "ONAP 
Project Developer Event: June 8 - 9, 
2017"
Would it be possible to refine the calendar in order to highlight which project 
proposal(s) will be reviewed for each slot?

It will help us to ensure that the PTL and additional stakeholders will be able 
to attend remotely if it is not possible for them to attend in person

Thanks in advance for your consideration

Best regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

[Lefevre, Catherine]

Dear all,

It is great to see a lot of enthusiasm from different companies about their Lab 
Center proposals.
Per Lab Center (Physical Labs-CMCC, Reliance Jio, China Telecom,OPNFV, Orange & 
Open Labs-CMCC, China Telecom, Orange, WINLAB),
we need to understand what type of labs, the Lab center can support and what 
will be their scope.

We have identified at least 4 different labs as part of the Integration project 
(Integration (5/11/2017)):
• 1 lab non-resilient for Development Team (immediate)
• 1 lab resilient for CIST Team (immediate)
• 1 lab resilient for E2E Team (immediate)
• 1 lab resilient for S3P Team (medium term - dependencies on 
Performance KPIs; Limited Performance testing will be performed as part of ONAP 
R1).


Can we ensure that we can support all of these Development/Testing activities 
when the TSC will review the "Open Lab" and "Physical Labs" proposals?
Thank you.

Best regards
Catherine
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Gadiyar, Rajesh
Sent: Monday, May 29, 2017 4:57 AM
To: Chen Yan ; onap-tsc@lists.onap.org
Cc: Hellmann, Gil (Wind River) ; 
xiexj...@chinatelecom.cn
Subject: Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

+1

Hello ONAP TSC:

Intel is considering hosting a physical lab for ONAP as well. I have added our 
proposal to the document on Wiki: 
https://wiki.onap.org/display/DW/Physical+Labs
 to co-host with the OPNFV lab that we currently host.

--
Regards,
Rajesh

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of Chen Yan 
mailto:chenyan@chinatelecom.cn>>
Date: Thursday, May 25, 2017 at 6:39 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Cc: "xiexj...@chinatelecom.cn" 
mailto:xiexj...@chinatelecom.cn>>
Subject: Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

Dear TSC,

From the above discussions we learned the opinions of the ONAP members on Open 
Lab. As Xiaojun mentioned, China Telecom would like to provide a physical lab 
for ONAP. Actually,  in last year, China Telecom has already established a 
Physical Lab for Open-O mercury release, and finished the E2E connection test 
for vCPE extension use case.

In the near future, a Physical Lab is still important and necessary, especially 
for operators with intention to deploy operational systems to manage not only 
the NFV networks/VNFs but also PNFs.
China Telecom is going to introduce SDN techniques in our Backbone Network, 
e.g. Segment routing and TE. In this case, SDN enabled Physical Network and a 
corresponding Lab is our scope of works.

I would suggest to build up multiple labs, including Virtual labs and Physical 
labs, and solving connectivity issues under integration team/LF governance, in 
order to address on different use cases covering most of the operators 
interests.

Best Regards
Chen Yan

发件人: xiexj...@chinatelecom.cn 
[mailto:xiexj...@chinatelecom.cn]
发送时间: 2017年5月23日,星期二 09:56
收件人: Deng邓灵莉/Lingli; roberto.k...@orange.com; 
Haiby, Ranny (Nokia - US/San Jose USA); Christopher.Donley; 'Jason Hunt'; MAZIN 
E GILBERT; sunqiong.bri
抄送: tsc-priv...@lists.onap.org; SPATSCHECK, 
OLIVER \(OLIVER\); 'Yunxia Chen'
主题: Re: Re: [onap-tsc-private] Lab and Intgeration

China Telecom also has a lab for OPEN-O. Based on this lab, China Telecom is 
willing to provide a physical lab for ONAP too.

Best Regards,

Xiaojun

From: Lingli Deng
Date: 2017-05-23 09:05
To: roberto.k...@orange.com; 'Haiby, Ranny 
\(Nokia - US/San Jose USA\)'; 'Christopher Donley 
\(Chris\)'; 'Jason 
Hunt'; 
ma...@research.att.com
CC: tsc-private; 
spatsch; 'Yunxia 
Chen'
Subject: Re: [onap-tsc-private] Lab and Intgeration
China Mobile is willing to provide a physical lab too, based on the existing 
OPEN-O lab and do enhancement as needed.

Lingli

From: 
onap-tsc-private-boun...@lists.onap.org
 [mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of 
roberto.k...@orange.com
Sent: 2017年5月23日 8:28
To: Haiby, Ranny (Nokia - US/San Jose USA) 
mailto:ranny.ha...@nokia.com>>; Christopher Donley 
(Chris) mailto:christopher.don...@huawei.com>>; 
Jason Hunt mailto:djh...@us.ibm.com>>; 
ma...@research.att.co

[onap-tsc] Project Proposal: DMaaP

[Lefevre, Catherine]

Dear ONAP TSC,

We would like to formally propose the DMaaP project for ONAP.
The proposal wiki page, which includes details of the project description, 
project scope, and proposed repo names, can be found at:

DMaaP - Data Movement as a Platform
https://wiki.onap.org/pages/viewpage.action?pageId=3247130

The DMaaP team consists of representatives from AT&T.
Feel free to contact Ram Koya (rk5...@att.com)  if there are any issues or 
questions regarding the proposal.

Many thanks and regards
Catherine


Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] Project Proposal: AAF

[Lefevre, Catherine]

Dear ONAP TSC,

We would like to formally propose the AAF project for ONAP.
The proposal wiki page, which includes details of the project description, 
project scope, and proposed repo names, can be found at:

AAF-Authentication and Authorization Framework
https://wiki.onap.org/display/DW/Authentication+and+Authorization+Framework

The AAF team consists of representatives from AT&T.
Feel free to contact Ram Koya (rk5...@att.com)  if there are any issues or 
questions regarding the proposal.

Many thanks and regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

[onap-tsc] SDC Proposal project - Target: May 16th, 2017

[Lefevre, Catherine]

Dear TSC,

We would like to inform you that the 'SDC' proposal will be submitted by 
Tuesday May 16th.
We are currently in the process to assess the feasibility of additional 
feedback provided by the Huawei team.

Sorry for any inconvenience

Many thanks & regards
Catherine

Catherine Lefèvre
AT&T Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

Re: [onap-tsc] Seed code for Service Orchestrator

[Lefevre, Catherine]

Dear all,

I have discussed this morning with Steve Smokowski (who is part of the SO 
project proposal).
He confirmed that the MSO code base was discussed with Gil/Dewayne in terms of 
text and goals to be part of SO proposal.
A follow-up will be performed today with Dewayne in order to remove any 
confusion from the current proposal

Hope it helps.

Best regards
Catherine

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of eric.deb...@orange.com
Sent: Thursday, May 11, 2017 10:21 PM
To: Ed Warnicke ; ROSE, DANIEL V 
Cc: dewa...@gigaspaces.com; SPATSCHECK, OLIVER ; 
onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Seed code for Service Orchestrator

+1

De : Ed Warnicke [mailto:hagb...@gmail.com]
Envoyé : jeudi 11 mai 2017 22:17
À : ROSE, DANIEL V
Cc : SPATSCHECK, OLIVER; DEBEAU Eric IMT/OLN; 
dewa...@gigaspaces.com; 
onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Seed code for Service Orchestrator

In many other communities, as a matter of social norm, not governance, if one 
is going to edit a project proposal, it is considered good manners to ask the 
originator of a proposal before editing it in a substantive way.

Perhaps we should consider communicating this social norm withing the ONAP 
community to avoid confusion?

Ed

On Thu, May 11, 2017 at 4:11 PM, ROSE, DANIEL V 
mailto:dr6...@att.com>> wrote:
There has been a ton of change on the page in the last day: 
https://wiki.onap.org/pages/diffpagesbyversion.action?pageId=4719246&selectedPageVersions=29&selectedPageVersions=6

I hope everyone who needed to be involved has been involved because I didn't 
see much public discussion about this project on this mailing lists.

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

-Original Message-
From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org]
 On Behalf Of SPATSCHECK, OLIVER
Sent: Thursday, May 11, 2017 4:05 PM
To: eric.deb...@orange.com; 
dewa...@gigaspaces.com
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Seed code for Service Orchestrator

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


So am I.  I thought in the charter we had agreed that the MSO code base would 
be used for this. Similar to the 3 legacy Open-O components.

Was there any discussion on this anywhere?

Thx

Oliver

> On May 11, 2017, at 3:48 PM  EDT, 
> eric.deb...@orange.com wrote:
>
> Hello
>
> I am surprised to discover that open-o/gso is considered as the seed code for 
> the Service Orchestrator.
>
> As far as I know, we never decided such choice during the discussions last 
> week and it should be a TSC decision.
>
> Regards
>
> Eric
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC@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=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8&s=r3tAPP-TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw&e=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=D

[onap-tsc] DRAFT Technical Community Charter

[Lefevre, Catherine]

Dear all,

I have taken a look at ?ONAP TSC Charter DRAFT 6 6 Clean ? XXJ? document (I do 
not know if it is the latest version)

Here are some first comments:

?There are additional non-functional areas i.e. Operational 
requirements (monitoring tools, disaster recovery, alarm/event catalog, 
backup/restore strategy etc.) that we should consider.

?Will the Performance Coordinator also focus on KPIS/Telemetry, 
Scalability, dimensioning tool based on performance results etc.?

Many thanks & regards
Catherine
From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Ed Warnicke
Sent: Thursday, April 06, 2017 11:10 PM
To: SPATSCHECK, OLIVER 
Cc: onap-tsc 
Subject: Re: [onap-tsc] DRAFT Technical Community Charter

Oliver,

I suspect we may have to prune at some point.  I like getting the ideas out on 
the table to increase our available selections :)

Ed

On Thu, Apr 6, 2017 at 1:59 PM SPATSCHECK, OLIVER (OLIVER) mailto:spatsch at research.att.com>> wrote:
Ed,

as I like the idea of ?usability? (we actually have a metric in AT&T our OPS 
guys use to tell us how usable ECOMP is?) I am starting to worry how one 
coordinates all the coordinators to ensure we still end up writing code rather 
then just coordinate it.

Maybe I am overly pessimistic  but figured I point it out.

Oliver

On Apr 6, 2017, at 4:44 PM, Ed Warnicke mailto:hagbard at 
gmail.com>> wrote:


On Thu, Apr 6, 2017 at 11:19 AM, Haiby, Ranny (Nokia - US/San Jose USA) 
mailto:ranny.haiby at nokia.com>> wrote:
Thanks  Ed, Steve, Alla, Lingli, Phil, and Chris.

I suggest adding another coordinator - a "usability coordinator". The inherent 
complexity of each of the merged projects, the complex task of the merge and a 
community led by engineers may result in severe usability issues. We may end up 
with an amazingly architected software that may not be usable for mere mortals.

Usability of course is beyond the scope of any GUI, and touches all interfaces 
of the system.

The role of such coordinator will be to ensure any developed functionality 
meets certain usability rules and guidelines and does not break the overall end 
user experience.

This is an excellent idea :)

It actually sparks another idea :)  You seem to be focusing here on what might 
be termed "Runtime usability"... how easy is it to use the various interfaces 
of the system including GUI, I presume APIs, etc.  One situations I have often 
seen trip projects up is "Deployability"... basically... how easy (or hard) it 
is to 'deploy' the thing.  Some projects are insanely hard to deploy, some are 
easy.  My experience has been its has less to do with the complexity of the 
underlying problem than it does with the care the projects take in being easily 
deployable...  might be another good one to add to the list :)

Ed


Regards,

Ranny.

_
From: Danny Lin mailto:l...@vmware.com>>
Sent: Thursday, April 6, 2017 9:56 AM
Subject: Re: [onap-tsc] DRAFT Technical Community Charter
To: mailto:roberto.kung at orange.com>>
Cc: onap-tsc mailto:onap-tsc at lists.onap.org>>, 
mailto:xiexj.gd at chinatelecom.cn>>


Related to what is brought up below on project, I thought it would be great to 
hear the inputs regarding the charter of Architecture committee , the role of 
Architecture committee, where does it play in the lifecycle of the project, and 
how does it drive the architecture of ONAP in general (influence, or decide, or 
arbitration, etc)

Danny





Sent from my iPhone
On Apr 6, 2017, at 9:35 AM, "roberto.kung at orange.com" mailto:roberto.kung at orange.com>> 
wrote:
It is not clear for me how we create project with its resource. I assume the 
creation of projects will be the conclusion of the work of requirements on the 
architecture, based on the 11 modules that have been identified up to know. One 
project per module?

Once we have a list of tentative project, I assume that the TSC will ask for 
resources. As we don?t know yet who merits to be commiters, How are we going to 
choose them at the beginning? And consequently the PTL? May be at the beginning 
some interim organization base on volunteering.

I also find coordinators a good idea. May be it is redundant with commitees.

As for the subject of coordinations, it should be decided by the TSC. They may 
not last forever. For me the first subject of coordination is the architectural 
framework.

RK

De :onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at lists.onap.org]De la part de 
xiexj.gd at chinatelecom.cn
Envoy? : jeudi 6 avril 2017 10:57
? : Christopher.Donley; onap-tsc
Objet : Re: [onap-tsc] DRAFT Technical Community Charter

Thanks to Ed, Steve, Alla, Lingli, Phil, and Chris. It's comprehensive.

I've attached the document with some notes, and I hope these could help.

Regards,


Xiao