Re: [onap-tsc] Leaving AT - ONAP SON Use Case

[Srini]

Hi Shankar,

It was pleasure working with you on OOF during R3/R4 timeframe. Yes, I guess 
our paths will cross again.
Wish you the best in your future role.

Srini

From: onap-tsc@lists.onap.org  On Behalf Of 
SHANKARANARAYANAN, N K
Sent: Thursday, July 8, 2021 6:34 AM
To: Lefevre, Catherine ; David McBride 
; Kenny Paul ; 
bw...@linuxfoundation.org; swaminathan.seetharama...@gmail.com; 
krishna.moort...@wipro.com; 'Sandeep Shah' ; VARMA, VIKAS 
R ; niranjana@wipro.com; dilipmaili...@gmail.com; Cheung, 
Ben (Nokia - US/Murray Hill) ; Chaker Al-Hakim 
; Toine Siebelink ; 
TIMONEY, DAN ; HAHN III, JIM ; VENKATESH KUMAR, 
VIJAY ; alla.gold...@amdocs.com; VAN BRAKLE, TRACY L 
; CLAPP, GEORGE H ; martin.skorupski 
; 
'hanif.kukka...@highstreet-technologies.com' 
; Ivan Seskar 
; r...@winlab.rutgers.edu; 
morgan.richo...@orange.com; John Keeney ; Perala, Timo 
(Nokia - FI/Espoo) ; MAYER, ANDREW J ; 
ahila.panda...@wipro.com; 'saravanan@wipro.com' ; 
'kamel.i...@ericsson.com' ; Horn, Linda (Nokia - 
US/Murray Hill) ; tony.finne...@ericsson.com; 
onap-tsc@lists.onap.org; FREEMAN, BRIAN D 
Cc: nkshan...@gmail.com
Subject: [onap-tsc] Leaving AT - ONAP SON Use Case


Hello folks,



I would like to let you know that I will be leaving AT Tomorrow July 9 is my 
last day.

This is not really a goodbye since I expect to remain active in ONAP after a 
short vacation.

Our commitments in the 5G SON use case are on track, and Krishna Moorthy will 
manage the work.

We have discussed this and see no issues.



I am proud of what our SON use case team has achieved since the early days of 
Casablanca release.

We have developed a very solid foundation for ONAP-based SON, using centralized

PCI and ANR applications as concrete examples. We had a strong and early focus 
on being aligned with ORAN/3GPP

yang models and interfaces. The solution includes flows for FM/PM/CM 
notifications from the RAN, and a methodology

for incorporating AI/ML, and we did our integration testing at the new Rutgers 
ONAP lab.

We are thankful for the contributions from all the team members and the support 
from

the TSC, PTLs, Arch / UseCase committees, and Rutgers Winlab.



I will be joining another company and plan to remain active in the ONAP/ORAN 
space with the same objectives,

which is to foster an open ONAP platform for mobile networks which is aligned 
with ORAN.

I will share more information once I am established in that new role.

I look forward to working with all of you!



Please use my personal email nkshan...@gmail.com<mailto:nkshan...@gmail.com> to 
reach me.



Thank you!



N. K. Shankar




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7986): https://lists.onap.org/g/onap-tsc/message/7986
Mute This Topic: https://lists.onap.org/mt/84068099/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [OOM] Removal of "AAF SSHSM"

[Srini]

Hi Sylvain,

No objection from our side as it was never integrated to secure the CA 
certificate.

Thanks
Srini


From: onap-tsc@lists.onap.org  On Behalf Of Sylvain 
Desbureaux via lists.onap.org
Sent: Monday, May 17, 2021 5:54 AM
To: onap-tsc 
Cc: onap-rele...@lists.onap.org
Subject: [onap-tsc] [OOM] Removal of "AAF SSHSM"

Hello,
AAF is in maintenance mode.
In AAF, we actually have 3 separate components:
* AAF "authz" (the one used for retrieving certificates)
* AAF "SMS" (the one used by OOF for now in order to store some sensitive datas)
* AAF SSHSM which is not used AFAIK (it seems to configure TPM part but I don't 
see it used)

AAF SSHSM is failing at every gating / daily deployments and the fix is not 
simple.
As it's not used, I'd like to remove it from OOM.

Is there any objection?

regards,
Sylvain

_



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.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7850): https://lists.onap.org/g/onap-tsc/message/7850
Mute This Topic: https://lists.onap.org/mt/82885713/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Good Bye (though not yet fully:-))

[Srini]

Hi Swami,

We did not work together, but I saw your work on network slicing. Quite 
impressive.
I am sure ONAP community will miss you.

Wish you the best in your future endeavors.

Thanks
Srini


From: onap-...@lists.onap.org  On Behalf Of 
Swaminathan via lists.onap.org
Sent: Tuesday, May 11, 2021 6:54 AM
To: Lefevre, Catherine ; David McBride 
; Kenny Paul 
; Brandon Wick 
; SHANKARANARAYANAN, N K ; 
PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN ; 'Seshu m' 
; VENKATESH KUMAR, VIJAY ; 'TIMONEY, 
DAN' ; CLAPP, GEORGE H (GEORGE H) ; 
DRAGOSH, PAMELA L (PAM) ; 
morgan.richo...@orange.com; 'Chaker Al-Hakim' ; 
alla.gold...@amdocs.com; Ranny Haiby ; Perala, Timo 
(Nokia - FI/Espoo) ; John Keeney ; 
'Martin Skorupski' ; VARMA, VIKAS 
R ; oskar.malm ; 'BLANDFORD, SCOTT' 
; Michela Bevilacqua ; Andy 
Mayer ; LinMeng ; 'Cheung, Ben 
(Nokia - US/Murray Hill' ; onap-discuss 
; onap-tsc@lists.onap.org; 
onap-...@lists.onap.org; andreas-geiss...@telekom.de; HAHN III, JIM 
; 'VAN BRAKLE, TRACY L' 
Cc: swaminathan.seetharama...@gmail.com; mason_hol...@yahoo.com
Subject: [onap-oof] Good Bye (though not yet fully:-))

Hi All,

I will be leaving Wipro (my present organization) tomorrow. However, I will 
still continue to provide support for some ONAP activities at least until end 
of next week.

It has been a really great journey since 2018 to know about ONAP and then start 
contributing in a small way. Personally & professionally it has been an 
enriching experience, and it was really wonderful to collaborate with so many 
experts and knowledgeable folks across various organizations. I will certainly 
miss some of the technical discussions, though I will be in touch at least with 
some of you to continue the discussions offline

Sincere thanks to Catherine, the TSC and to all the folks who have provided 
support & guidance, as well as to the members of OOF SON and E2E Network 
Slicing use case teams.

I will in particular miss the interactions with Shankar N K, Lin and members of 
our use case teams 

My personal mail id: 
swaminathan.seetharama...@gmail.com<mailto:swaminathan.seetharama...@gmail.com> 
& mason_hol...@yahoo.com<mailto:mason_hol...@yahoo.com> (I will also update my 
LF profile shortly).

The world is small, so perhaps our paths will cross again sometime in the 
future - until then, Good Bye!, L'hitraot, Adios, Au revoir, do widzenia, 再见, 
Auf Wiedersehen, hoşça kal 

Regards,

Swami.


Sensitivity: Internal & Restricted
'The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com<http://www.wipro.com>'



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7843): https://lists.onap.org/g/onap-tsc/message/7843
Mute This Topic: https://lists.onap.org/mt/82746503/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] ONAP Architecture Subcommittee Vice Chair Elections (New Position)

[Srini]

+1

From: onap-tsc@lists.onap.org  On Behalf Of Ranny 
Haiby (Samsung) via lists.onap.org
Sent: Wednesday, March 10, 2021 9:37 AM
To: onap-tsc@lists.onap.org; Chaker Al-Hakim ; 
onap-arc ; Byung-Woo Jun 
Subject: Re: [onap-tsc] ONAP Architecture Subcommittee Vice Chair Elections 
(New Position)

+1

Ranny.


From: mailto:onap-tsc@lists.onap.org>> on behalf of 
"seshu kumar m via lists.onap.org" 
mailto:seshu.kumar.m=huawei@lists.onap.org>>
Reply-To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Date: Wednesday, March 10, 2021 at 5:34 AM
To: Chaker Al-Hakim 
mailto:chaker.al.ha...@futurewei.com>>, onap-arc 
mailto:onap-...@lists.onap.org>>, Byung-Woo Jun 
mailto:byung-woo@est.tech>>, onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] ONAP Architecture Subcommittee Vice Chair Elections 
(New Position)
Resent-From: mailto:ranny.ha...@samsung.com>>

+1.
--
Thanks and Regards,
M Seshu Kumar
Lead Architect,
P, Cloud Network OSDT,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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:Chaker Al-Hakim 
mailto:chaker.al.ha...@futurewei.com>>
To:Chaker Al-Hakim 
mailto:chaker.al.ha...@futurewei.com>>;onap-arc 
mailto:onap-...@lists.onap.org>>;Byung-Woo Jun 
mailto:byung-woo@est.tech>>
Cc:onap-tsc mailto:onap-tsc@lists.onap.org>>
Date:2021-03-10 16:55:33
Subject:Re: [onap-tsc] ONAP Architecture Subcommittee Vice Chair Elections (New 
Position)

Dear all,

The nomination phase for the Vice Chair position has passed.
As of the deadline of  Mar 9, 2021, only candidate,  @Byung-Woo 
Jun, has self-nominated.

As there was only one candidate for the VC position, I am requesting that the 
TSC approve the result.

Regards,
Chaker

From: onap-...@lists.onap.org 
mailto:onap-...@lists.onap.org>> On Behalf Of Chaker 
Al-Hakim via lists.onap.org
Sent: Wednesday, March 03, 2021 11:34 AM
To: onap-...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: [Onap-arc] ONAP Architecture Subcommittee Vice Chair Elections (New 
Position)

Dear Architecture Subcommittee members,

As per the attached email below that was sent on Jan 26,2021 - Now that the 
Architecture Subcommittee elections for the Chairmanship position have 
concluded. I am kicking off the call for the
Architecture Subcommittee Vice Chair nominations.

The self-nomination phase will start with the receipt of this announcement  and 
will end on Mach 9, 2021 at 5PM EST.

If you ae interested in self-nominating for this position please “Reply All” 
with your intention.  You are also encouraged to include a biography and 
statement of intent on
why you would be a good fit to hold this position.

Regards,
Chaker


From: onap-...@lists.onap.org 
mailto:onap-...@lists.onap.org>> On Behalf Of Chaker 
Al-Hakim via lists.onap.org
Sent: Tuesday, January 26, 2021 2:50 PM
To: onap-...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: [Onap-arc] Annual ONAP Architecture Subcommittee Chair Elections

Dear Architecture Subcommittee members,

As was discussed during the Jan-26-2021 Architecture Subcommittee weekly 
meeting and per the Community Election Process found here: 

Re: [onap-tsc] Moving on...

[Srini]

Hi Davide,

It is great knowing you and enjoyed our little chats with Ramki and you.  Yes, 
I hope our paths cross again.

Wish you the best in your future job.

Thanks
Srini


From: onap-tsc@lists.onap.org  On Behalf Of Davide 
Cherubini via lists.onap.org
Sent: Friday, March 5, 2021 6:20 AM
To: lfn-bo...@lists.lfnetworking.org; lfn-...@lists.lfnetworking.org Calendar 
; lfn-...@lists.lfnetworking.org; 
lfn-...@lists.lfnetworking.org; onap-tsc@lists.onap.org
Subject: [onap-tsc] Moving on...

Dear LFN Board, TAC, SPC and Community Members,

First of all my apologies for this long overdue email…

It is with heavy heart and mixed emotions that I have decided to step down from 
all my LFN duties and the ONAP TSC to pursue a new Job opportunity.

As I look back on the growth of the LFN communities in terms of individuals and 
companies actively contributing to it, I feel very proud to be part of such an 
amazing community (ONAP Community will always have a special place in my heart) 
and to have met and worked with so many talented and knowledgeable individuals 
who genuinely want to do the right thing for the overall industry and that I am 
honoured to call “friends”. I am certainly going to miss that but I am also 
hopeful that our paths will cross again in the near future.

I am adding my LinkedIn profile below along with my private email, so we can 
stay in touch.

All the best and stay safe,
Davide

LinkedIn: https://www.linkedin.com/in/dadecher/
Private Email: davide.cherubi...@gmail.com<mailto:davide.cherubi...@gmail.com>


[signature_1339592281]<http://vodafone.com/>
Davide Cherubini
Principal Engineer
Network as a Platform Team
Group Network

Babbage House, The Connection, Newbury, Berkshire RG14 2FN
+44 7770 700172

davide.cherub...@vodafone.com<mailto:davide.cherub...@vodafone.com>
vodafone.com<http://vodafone.com/>

The future is exciting.
Ready?






C2 General



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7578): https://lists.onap.org/g/onap-tsc/message/7578
Mute This Topic: https://lists.onap.org/mt/81103351/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [Onap-arc] [onap-tsc] ArchCom: Weekly Meeting agenda for Tuesday Sep 01, 2020 - Any Agenda Topics?

[Srini]

You may want to look at https://vitess.io/

This supports both MYSQL and MariaDB databases.

Thanks
Srini


From: onap-...@lists.onap.org  On Behalf Of Sunder 
TATTAVARADA,
Sent: Monday, August 31, 2020 6:50 AM
To: onap-tsc@lists.onap.org; onap-...@lists.onap.org
Subject: Re: [Onap-arc] [onap-tsc] ArchCom: Weekly Meeting agenda for Tuesday 
Sep 01, 2020 - Any Agenda Topics?

Hello Chaker,

Would it be possible to discuss the best path forward for "scaling out" on 
MariaDB or any RDBMS system being used in ONAP?

There are two approaches:
Master-Master model (allows clients to write to any nodes of the cluster)
Master-Slave model with failover (Supports reads from multiple nodes but writes 
to just one node) - May require Application teams to refactor code to handle 
this.

Are there any recommendations from Architecture team and/or any solutions 
already in place?

Thanks,
Sunder Tattavarada
Portal PTL

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Chaker 
Al-Hakim
Sent: Friday, August 28, 2020 5:20 PM
To: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] ArchCom: Weekly Meeting agenda for Tuesday Sep 01, 2020 - 
Any Agenda Topics?


Hello Team,

If you have any topics that you would like to present or discuss, please let me 
know.

Regards,
Chaker




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#7025): https://lists.onap.org/g/onap-tsc/message/7025
Mute This Topic: https://lists.onap.org/mt/76534137/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Few committers from Intel

[Srini]

Hi,

We have few committers from Intel in various projects.  Few Engineers are no 
longer with Intel.
As per guidance from PTLs, I am sending this email.

Please remove following committer permissions for following:


  *   Kiran Kamineni from AAF
  *   Dileep Ranganathan from OOF
  *   Itohan Upkonmwan from CLI

Thanks
Srini


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#6416): https://lists.onap.org/g/onap-tsc/message/6416
Mute This Topic: https://lists.onap.org/mt/74380720/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] moving to another role in VMware

[Srini]

Hi Ramki,

Sad to see you go.

I wish you the best in your new role.

Thanks
Srini


From: onap-...@lists.onap.org  On Behalf Of ramki 
krishnan
Sent: Friday, April 24, 2020 9:23 AM
To: onap-tsc@lists.onap.org; onap-...@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: [Onap-arc] moving to another role in VMware

Dear TSC, All,

I really enjoyed my last few years in ONAP working closely with the smartest 
people in the industry. I am moving to a new role in VMware in the area of 
Distributed Ledgers/Blockchain and no longer be able to continue with my Edge 
Coordinator role in ONAP. Wishing you all and ONAP my heartfelt success!

Thanks,
Ramki


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#6203): https://lists.onap.org/g/onap-tsc/message/6203
Mute This Topic: https://lists.onap.org/mt/73244858/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing development work

[Srini]

Hi Eric,

Just to be on the same page:


  1.  Application life cycle management on K8s Clusters is taken care by 
following micro-services
 *   K8s Plugin Service in Multi Cloud project (new development)
 *   Mongo DB & etcd (Non-ONAP open source)
 *   SDC Client in Multi-Cloud (New development)
 *   SDC modifications
 *   SO modification
 *   Multi-Cloud broker modifications.
  2.  ONAP4K8s is one recipe and useful for greenfield (e.g Enterprises and 
Industry 4.0) deployments. It has following
 *   K8s Plugin Service in Multi Cloud project
 *   Security Micro-services (SMS, Vault, TPM related)
 *   Mongo DB & etcd (Non-ONAP open source)

>From the beginning, we wanted to make sure that everything we do is modular 
>and can be deployed standalone fashion,  keeping micro-service architecture 
>principles in mind.
ONAP4K8s recipe need not be used if the intention is to use along with rest of 
ONAP (SDC, SO, AAF, OOF etc...). We have both models supported (standalone or 
integrated).
ONAP4K8s is mainly for greenfield scenarios.

If the term 'ONAP' in ONAP4K8s is confusing, we can rename this recipe as 
something else.  I think based on another email on similar subject, you seem to 
be implying that if people are not using some components such as SDC, SO, AAF 
are not used, then it should not be called as ONAP. If this is the concern,  we 
don't mind removing ONAP4K8s page altogether and put it in places (such as 
Akraino/ICN) where it is being used.  Let us know.

Is the concern/confusion that we are not using OOM for this profile? If this is 
the concern, we do have plans to ensure that OOM is leveraged for creating the 
profile with above services as in (2).  But at this time, OOM granularity is 
selection of projects, but not micro-services in each project. Hence, we 
created something to move forward.

Thanks
Srini


From: onap-cnf-taskfo...@lists.onap.org  On 
Behalf Of Eric Debeau via lists.onap.org
Sent: Wednesday, April 22, 2020 11:51 AM
To: onap-cnf-taskfo...@lists.onap.org; ranny.ha...@samsung.com; 
catherine.lefe...@intl.att.com; onap-tsc@lists.onap.org
Subject: Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and 
existing development work

Hi

I participated this afternoon to the various sessions around CNF where there is 
a lot of activities for this long journey towards managing CNF.

However, I am still confused about the communication about ONAP4K8S and the 
statement that we should rely on ONAP4K8S to manage CNF in ONAP.

We can not state that ONAP4K8 is an ONAP profile. Based on the code available 
on the ONAP repo 
https://git.onap.org/multicloud/k8s/tree/deployments/helm/onap4k8s, we can see 
that ONAP4K8S is not using existing ONAP project. There is a dedicated chart 
for the deployment not reusing existing ONAP ones (managed by OOM project):
https://git.onap.org/multicloud/k8s/tree/deployments/helm/onap4k8s. It is only 
based on one Docker from multicoud project (multicloud-ks), mongodb, etcd and 
other common components with no reference to existing official ONAP charts 
defined in OOM repo.

I have no problem if we consider it clearly as a PoC, but we can not claim that 
is an ONAP profile and the way we communicate on ONAP4K8S is not clear an is 
very confusing.

As an example of "ONAP profile", we can find one for 5G slicing use-case where 
the use-case team has defined an optimized subset of ONAP components for their 
slicing use-case: 
https://git.onap.org/oom/tree/kubernetes/onap/resources/overrides/onap-5g-network-slicing.yaml

We really need to clarify this topic.

Best Regards

Eric

De : 
onap-cnf-taskfo...@lists.onap.org<mailto:onap-cnf-taskfo...@lists.onap.org> 
[onap-cnf-taskfo...@lists.onap.org] de la part de Ranny Haiby (Samsung) via 
lists.onap.org [ranny.haiby=samsung@lists.onap.org]
Envoyé : mardi 21 avril 2020 01:56
À : 
onap-cnf-taskfo...@lists.onap.org<mailto:onap-cnf-taskfo...@lists.onap.org>; 
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>
Objet : Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing 
development work
Hi Catherine,

Thanks for defining the scope of WS7. I admit it was not clear to me before, 
and now it makes much sense.

One thing If I may suggest - the phrasing of "Initial experimentations with 
basic CNF(s)..." sounds a bit non-committal, as if we are not sure if and when 
we want to support CNFs. How about "Incremental improvements to accommodate for 
CNF(s) in order to validate..."

Regards,

Ranny.


From: 
mailto:onap-cnf-taskfo...@lists.onap.org>> 
on behalf of Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>>
Reply-To: 
"onap-cnf-taskfo...@lists.onap.org<mailto:onap-cnf-taskfo...@lists.onap.org>" 
mailto:onap-cnf-taskfo...@lists.onap.org>>, 
"catherine.lefe...@intl.att.com<mailto:catherine.lefe...@

Re: [onap-tsc] Vote by TSC on proposed exception process

[Srini]

+1

From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul
Sent: Thursday, February 20, 2020 10:57 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Vote by TSC on proposed exception process

As mentioned on the TSC call today, this email will serve as the vote –
Please respond with a +1, 0 or -1
-kenny

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride
Sent: Wednesday, February 19, 2020 12:13 PM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] Vote by TSC on proposed exception process

Team,

Just a reminder that the TSC will be voting on the proposed exception process 
on Thursday, Feb 19.

If you have not yet reviewed the process, please take a few minutes to examine 
the following links:

  *   Form
  *   Process
Let me know if you have any questions.

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5952): https://lists.onap.org/g/onap-tsc/message/5952
Mute This Topic: https://lists.onap.org/mt/71404800/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Suggestion to delay M4 milestone of R6 to End of March

[Srini]

Hi,

M2/M3 milestone is delayed.

Coronovirus seems to have some impact  on meeting some deliverables.

My request is to postpone the M4 milestone (Code completion) by 3 weeks to End 
of March.

Thanks
Srini





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5906): https://lists.onap.org/g/onap-tsc/message/5906
Mute This Topic: https://lists.onap.org/mt/71029899/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Emergency AAF Committer Promotions

[Srini]

+1

From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul
Sent: Tuesday, January 21, 2020 7:52 AM
To: onap-tsc-v...@lists.onap.org
Subject: [onap-tsc] Emergency AAF Committer Promotions

(bcc to onap-tsc for visibility)

Due to a last minute scheduling conflict in Prague the ONAP TSC meeting 
scheduled for Thursday , January 16 had to be cancelled.   The TSC members 
present had a brief discussion following the final session on two critical 
votes. The first vote was regarding active Committer availability on the AAF 
project. The critical concern was that contributions to AAF were not being 
merged in a timely fashion, thus placing three other ONAP projects dependent on 
AAF changes at risk.   A quorum of the TSC was established and the following 
vote was initiated:

#VOTE Does the TSC approve the temporary promotion of  Pawel Baniewski (Nokia), 
 Gerard Nugent (Ericsson) and John Franey (AT) to be a AAF Committers 
timebound to the Frankfurt release? +1, 0 -1
The vote was unanimous among those present (table below) which is sufficient 
for approval. If TSC members that were not in attendance would like to register 
their vote, please respond to this message in onap-tsc-vote with your +1, 0, -1 
by January  24.
There was also consensus that AAF dependencies should be deprecated in the 
Guilin or Honolulu releases, but any formal discussion on this topic was tabled 
for a future TSC meeting.

company
Vote
Contact info
Bell Canada
1
Alexis de Talhouët (proxy Olivier Phenix )
AMDOCS
1
Alla Goldner
Deutsche Telekom
Andreas Geissler
WindRiver
Bin Yang
AT
1
Catherine Lefevre
Ericsson
1
Ciaran Johnston
Vodafone
1
Davide Cherubini
Orange
1
Eric Debeau
IBM
1
Jason Hunt
China Mobile
1
Lingli Deng
Turk Telecom
Murat Tupcu
Reliance Jio
Ning So
Samsung
1
Ranny Haiby
Huawei
1
Seshu Kumar M
Intel
Srini Addepalli
Nokia
1
Timo Perala
Verizon
Viswa Kumar Skand Priya
China Telecom
ZongHe Huang

Thanks!
-kenny




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5855): https://lists.onap.org/g/onap-tsc/message/5855
Mute This Topic: https://lists.onap.org/mt/69959219/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Happy New Year & Welcome Back !

[Srini]

Hi Catherine,

Thank you. Happy new year to all of you too.

Thanks
Srini


From: onap-tsc@lists.onap.org  On Behalf Of Catherine 
LEFEVRE
Sent: Monday, January 6, 2020 3:28 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Happy New Year & Welcome Back !

[cid:image001.jpg@01D5C467.7BFAFEA0]

Dear ONAP Community,

On behalf of the ONAP TSC, Best Wishes to You and to Your family !
I hope you all had a wonderful and enjoyable holiday, and very deserving time 
off with your family and friends.

I am looking forward to working with each of you in 2020 to move our ONAP 
Community forward to be the best in the software and technology industry, and 
to deliver impactful ONAP Releases in 2020.

I am also looking forward to meeting you F2F in Prague next week in order to 
collect your feedback, your suggestion and your new idea.
Looking at the OPNFV/ONAP/CNTT Prague Event Schedule, our ONAP Program 
Committee Members have prepared a great agenda.
Have a look at it - 
https://wiki.lfnetworking.org/pages/viewpage.action?pageId=25364127

Kind regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT Labs - Network Cloud and SDN Platform Integration
SDN Platform & Systems
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair

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
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.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5808): https://lists.onap.org/g/onap-tsc/message/5808
Mute This Topic: https://lists.onap.org/mt/69462746/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] ONAP TSC Chair Nominations 2019

[Srini]

Congratulations Catherine. Well deserved!
On Dec 10, 2019, at 7:42 AM, Davide Cherubini  
wrote:


Congratulations @Catherine LEFEVRE!

Davide

From:  on behalf of Kenny Paul 

Reply to: "onap-tsc@lists.onap.org" 
Date: Friday, 6 December 2019 at 20:44
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] ONAP TSC Chair Nominations 2019

Congratulations to Catherine on being reelected as our ONAP TSC Chair!
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4356f527d488649e
I will be setting up the Vice-Chair elections shortly.

-kenny

From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Monday, December 2, 2019 12:29 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP TSC Chair Nominations 2019

There is only one candidate for the ONAP TSC Chair election: Catherine LeFevre 
(AT).

Ballots have been distributed to TSC members.  Voting ends 12:30 pacific 
Friday, Dec. 6

Thanks!
-kenny


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5761): https://lists.onap.org/g/onap-tsc/message/5761
Mute This Topic: https://lists.onap.org/mt/61193921/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Courtesy update regarding the ONAP TSC Elections

[Srini]

Hi Steve,

You are one of the key people in success of ONAP so far.  Your last statement 
is encouraging, expect for ‘as time allows’ . I hope you will continue to lead 
and help in ONAP architecture.

Thanks
Srini


From: onap-tsc@lists.onap.org  On Behalf Of Stephen 
Terrill via Lists.Onap.Org
Sent: Monday, November 4, 2019 8:08 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Courtesy update regarding the ONAP TSC Elections

Dear All,

I wanted to take a few moments to share a few words.  As you know I have been 
involved with the ONAP journey from the TSC perspective (architecture and 
SECCOM  as well) from its inception and have seen the creation and growth of 
this community which has been an amazing journey.  We see that as part of this 
journey, ONAP is now moving to a phase with ever increasing relevance for 
product development, and as such we want to adjust our contribution to the 
community (TSC) steering accordingly.For this purpose I am very happy that 
Ciaran has stepped up to self nominate as I have been working with him for 
quite some time and I am sure, if elected, he will do a great job - and indeed 
he has also been my stand-in a number of times.  I wanted to add – this is not 
an exit but a transformation - my intention to remain involved, but from 
another supporting perspective as time allows.

Best Regards,

Steve

[http://www.ericsson.com]<http://www.ericsson.com/>

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com<http://www.ericsson.com/>

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

Our commitment to Technology for 
Good<http://www.ericsson.com/thecompany/sustainability-corporateresponsibility> 
and Diversity and 
Inclusion<http://www.ericsson.com/thecompany/diversity-inclusion> contributes 
to positive change.
Follow us on: Facebook<https://www.facebook.com/ericsson> 
LinkedIn<https://www.linkedin.com/company/ericsson> 
Twitter<https://twitter.com/Ericsson>

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer<https://www.ericsson.com/en/legal/privacy/email-disclaimer>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5578): https://lists.onap.org/g/onap-tsc/message/5578
Mute This Topic: https://lists.onap.org/mt/41267004/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] 转发: Soliciting input for ONAP AI status report

[Srini]

Hi Lingli,

There are many “Big Data AI analytics frameworks” in Industry – Some open 
source and some commercial.
Akraino ICN BP family has one analytics framework – It is called “Distributed 
Analytics” framework. Some times, ICN also uses the term DaaS.
Akraino ICN family, currently is including ONAP4K8S for Multi-site/Cluster 
orchestration.
So, a requirement for  ONAP team to facilitate deployment  “Distributed 
Analytics” framework and analytics applications leveraging this “Distributed 
Analytics” framework.  ONAP4K8S team also felt that this is good test case to 
show the upcoming capabilities of ONAP R6.
Since there is a good synergy, both the communities will be working tighter. It 
is going to be win-win for both the communities

As part of this joint effort, new integration test case (use case) is added in 
R6.
There could be additional items that may get identified in ONAP and those will 
need to be taken care.

Some details are here:
https://wiki.onap.org/pages/viewpage.action?pageId=71831998

Let me know if you need any more information and in any other format.

Thanks
Srini





From: onap-tsc@lists.onap.org  On Behalf Of Lingli Deng
Sent: Friday, October 18, 2019 3:34 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] 转发: Soliciting input for ONAP AI status report



发件人: Lingli Deng [mailto:denglin...@chinamobile.com]
发送时间: 2019年10月18日 18:23
收件人: 'onap-tsc@lists.onap.org'
抄送: 'Addepalli, Srinivasa R'; 'BEGWANI, VIMAL'; 'Stephen Terrill'
主题: Soliciting input for ONAP AI status report

Hi community,

I am writing to soliciting input and volunteers for the ONAP status report on 
AI scheduled on Oct. 31 TSC call.
If you are currently working on this track and willing to share it with the 
community, please kindly reply this email by Friday and we will form a small 
editing team to kick off the drafting next week.

Thanks,
Lingli


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5499): https://lists.onap.org/g/onap-tsc/message/5499
Mute This Topic: https://lists.onap.org/mt/35013115/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Integration PTL Election Results

[Srini]

Congratulations Morgan!!

Srini

From: onap-tsc@lists.onap.org  On Behalf Of Brian 
Freeman
Sent: Wednesday, October 16, 2019 5:29 AM
To: 'onap-tsc@lists.onap.org' ; Jim Baker 
; 'David McBride' 
Cc: 'morgan.richo...@orange.com' ; LEFEVRE, 
CATHERINE 
Subject: [onap-tsc] Integration PTL Election Results


Dear ONAP TSC,

Please find the ONAP Integration  project's PTL election details below:

Election result:
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_5ab5a1fc695d987b


Morgan Richomme is the new Integration PTL.

Congratulations Morgan !

Brian Freeman
(Temporary Integration PTL)




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5480): https://lists.onap.org/g/onap-tsc/message/5480
Mute This Topic: https://lists.onap.org/mt/34559623/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] next week meeting and preparations for pre-ONS ONAP meeting

[Srini]

Hi Alla,

I could not join today.  We will bring proposals on following:

-K8S based Cloud region support (Ritu/Srini):  Status and R5 plans

-Distributed Analytics as a service (Dileep/Srini) : Status and R5 Plans

-Hardware Platform Awareness (Alex or Srini):  Status and R5 plans

Thanks
Srini


From: onap-usecase...@lists.onap.org [mailto:onap-usecase...@lists.onap.org] On 
Behalf Of Alla Goldner
Sent: Wednesday, March 20, 2019 8:59 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Subject: [Onap-usecasesub] next week meeting and preparations for pre-ONS ONAP 
meeting

Hi all,

As discussed during today's call, the next week's Monday meeting will be 
dedicated for the preparations to pre-ONS ONAP f2f.

BTW, for the remote attendants, there will be possibility to connect, details 
will be provided later.


  1.  Usecase subcommittee meeting will be mostly dedicated to presentations of 
El Alto planned use cases/functional requirements extensions. Each owner - 
Please prepare 2-3 slides with bullets of what you planned (only planned, not 
committed at this stage) extensions. New use cases/functional requirements 
authors - please do the same and please contact me in case of any questions.
  2.  Joint subcommittees meeting: 2 topics were proposed for discussion:

  *   Modularity/TOSCA task force status (Alex, please prepare material)
  *   Controllers (APPC, SDNC) evolution
Additionally, Fred (VZ) is working with EUAG to see if there are any proactive 
requirements for El Alto to be brought and presented during the meeting, in 
that case time will be dedicated for this.

Best Regards, Alla
This email and the information contained herein is proprietary and confidential 
and subject to the Amdocs Email Terms of Service, which you may review at 
https://www.amdocs.com/about/email-terms-of-service


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4775): https://lists.onap.org/g/onap-tsc/message/4775
Mute This Topic: https://lists.onap.org/mt/30523725/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] ONAP DDF + OPNFV Plugfest Now Complete

[Srini]

Yes. Very well written and lot of good information.

Srini


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Friday, March 8, 2019 2:55 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP DDF + OPNFV Plugfest Now Complete

Great job Brandon & Amar’s Team !

Eric – the link is here: 
https://www.lfnetworking.org/wp-content/uploads/sites/55/2019/03/ONAP_DDF_OPNFV_Plugfest_Report_030719.pdf

You can indeed access to it via wiki.onap.org

[cid:image002.jpg@01D4D57B.5240D020]

Best regards
Catherine


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4712): https://lists.onap.org/g/onap-tsc/message/4712
Mute This Topic: https://lists.onap.org/mt/30306948/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] Ubuntu and Alpine discussion

[Srini]

I agree with Chaker.

At this time, the understanding is that all projects are expected to move to 
Alpine (with special exception) is not same across many.  If that is the indeed 
the intention, it needs to be brought to TSC again so that TSC can make 
informed decision.

Thanks
Srini


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Chaker Al Hakim
Sent: Monday, February 11, 2019 7:03 AM
To: sylvain.desbure...@orange.com; Addepalli, Srinivasa R 
; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Ubuntu and Alpine discussion

Hello Sylvain,

I appreciate your detailed reply..

I am not sure if you were on the call when this topic was discussed. My point 
was not whether I favor one Linux distribution over other Linux distributions,. 
It was related to whether a specific distribution is commercially supported. As 
I mentioned in my previous email, f the goal of the Footprint Optimization 
project is to support all of the ONAP components, including all of their 
dependencies, packages, re-certification efforts, etc… on Alpine Linux then 
let’s make that very clear, ask for another TSC approval and document it in the 
ONAP wiki so that we are all on board

Regards,
Chaker

From: sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com> 
[mailto:sylvain.desbure...@orange.com]
Sent: Monday, February 11, 2019 8:29 AM
To: Chaker Al Hakim 
mailto:chaker.al.ha...@huawei.com>>; 
srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>; 
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-discuss] [onap-tsc] Ubuntu and Alpine discussion

Hello Chaker and Srini,

First of all, I want to thank you to propose yourself to rebuild ONAP docker 
images in order to shrink their sizes. We’re only 2 guys doing that today 
(Frank Sandoval and myself) so multiplying by two the workforce is great news.

SDNC and AAI have been done, Frank is working on DMaaP and I’m starting Portal 
as of today. So you can pick any image from 
https://wiki.onap.org/display/DW/CIA+Dublin+Release+Planning (Robot or SO for 
example). We want also to make a second pass on already done images to shrink 
more so you can also review and propose enhancements to the ones already done.

Welcome on board!

For the base image, you can use Alpine or Ubuntu at your preference.


As there are opinions against Alpine, I would like to share my views:

  *   Alpine is “vendor neutral”. If we decide to mandate ubuntu for example, I 
imagine that Canonical competitors could disagree and push their own images
  *   There have been some concerns (see  Ramki email for example) about using 
musl library and not glibc. Musl libc (https://www.musl-libc.org/) is now the 
default library for OpenWRT and is also used as replacement of uclibc (and 
glibc) in embedded Real time Linux images. So, we wouldn’t be the only one 
using it.
  *   Another building block of Alpine is busybox (https://www.busybox.net/) 
which is used in a lot of embedded devices (such as Modem router) so again 
we’re not the only ones (there are billions of device using it).
  *   On the security side, clair scanner (https://github.com/coreos/clair/) is 
a vulnerability tool from CoreOS (now part of RedHat) designerd for container 
security audit. You can embed it in your CI. Here’s an example of container 
scan (python script on top of Alpine) and you can see there are no known 
vulnerabilities : 
https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci-mqtt-trigger/security/dashboard

At the very least, this discussion shows a need for simplifying docker build 
process in order to tend to have a “simple” way to move from base image XXX to 
base image YYY.

Now, to know what’s the state of OOM as of today (master deployment of ONAP 
using docker-staging file from integration team, counting 284 containers):
ONAP images using :

  *   Debian/Ubuntu: 98
  *   Alpine: 61
  *   CentOS/rpm or yum based distro: 21
  *   Busybox: 3 (actually a lot more as many jobs are using busybox)
  *   Unknown: 1

Please be aware that mileage may vary (+/- 10 range I think) (it’s a 
“bruteforce” script and there may be / are images counted more than once but 
it’s what’s on my deployment today) and I counted “only” images from 
“nexus3.onap.org”.

So there’s no clear dominant base image and so claiming for “ubuntu only” or 
“alpine only” is inappropriate.
---
Sylvain Desbureaux

De : Chaker Al Hakim 
mailto:chaker.al.ha...@huawei.com>>
Date : vendredi 8 février 2019 à 15:34
À : "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, DESBUREAUX 
Sylvain TGI/OLN 
mailto:sylvain.desbure...@orange.com>>, 
"srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>" 
mailto:srinivasa.r.addepa...@inte

Re: [onap-tsc] Ubuntu and Alpine discussion

[Srini]

Hi Adolfo,

“Having said that, projects that can clearly demonstrate that they can't 
migrate to Alpine should be given the opportunity to request an exception and 
do the work themselves.
“

This is the point that raised the discussion in TSC. Above statement seem to 
indicate that the goal for ONAP is to move to Alpine. So far, my impression was 
that ONAP would be supported on both Ubuntu and Alpine.  Hence the discussion 
today.

Since Alpine is not supported commercially, it is always be a challenge for few 
to adopt ONAP as is.
Ubuntu is open source with commercial support. Now that Ubuntu also has thin 
version, adopting Ubuntu thin image as base package would address concerns 
related to size as well as support.  Moreover Ubuntu has big eco-system too and 
many packages get tested against Ubuntu.
Since ONAP is also tested so far on Ubuntu based containers, I think work for 
ONAP teams also would be relatively lesser if we go with Ubuntu minimal image.

I have not tried Ubuntu thin image. Again, my 2 cents on studying Ubuntu 
minimal image and its applicability.


Srini

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Adolfo Perez-Duran
Sent: Thursday, February 7, 2019 12:06 PM
To: onap-tsc@lists.onap.org
Cc: onap-disc...@lists.onap.org
Subject: Re: [onap-tsc] Ubuntu and Alpine discussion

Hi Srini,

Thanks for joining the discussion.

On October 8, 2018 PTLs discussed and agree to using Alpine as the base image 
for footprint minimization.

Because images are immutable, once dependencies and libraries are mapped there 
should not be any perceptible difference introduced by the base image.

It may be fair to assume that integration testing occurs (should occur?) at the 
service (API) level, regardless of what base image was used to create a 
container.

Some projects, such as SO and AAF, had already adopted --on their own-- Alpine 
as their base image.

Also, the CIA team has already engaged a number of teams in the Dublin scope 
and has contributed patches to migrate to Alpine.

Having said that, projects that can clearly demonstrate that they can't migrate 
to Alpine should be given the opportunity to request an exception and do the 
work themselves.

There is a lot of work to be done (finding common base images that can be used 
across projects, multi-stage builds, CI/CD parameterization, etc). Migrating to 
a small  base image is only the first step. I encourage you to bring a 
contribution and help us realize the long term goals.

Adolfo

On Thu, Feb 7, 2019 at 12:25 PM Srini 
mailto:srinivasa.r.addepa...@intel.com>> wrote:
Hi,

In today TSC this discussion came up on challenges in integration testing on 
both Ubuntu based ONAP and Alpine based ONAP.

Ubuntu releases minimal Ubuntu for containers in July, 2018.

According to https://blog.ubuntu.com/2018/07/09/minimal-ubuntu-released


-29Mbytes of docker image size.

-It is  based 18.04 (LTS ) – Long terms support availability.

-Minimal security attack surface

-Faster speed to bringup.

It seems to be providing best of both worlds


-Ubuntu, which ONAP has been basing on so far.  Also, supported by 
Canonical.

-Less disk size and faster bootup.

-Supports multiple architecture (ARM, x86, PPC etc…)

Some more info from dockerhub: 
https://github.com/docker-library/repo-info/blob/master/repos/ubuntu/remote/18.10.md

Thanks
Srini






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4584): https://lists.onap.org/g/onap-tsc/message/4584
Mute This Topic: https://lists.onap.org/mt/29693473/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Ubuntu and Alpine discussion

[Srini]

Hi,

In today TSC this discussion came up on challenges in integration testing on 
both Ubuntu based ONAP and Alpine based ONAP.

Ubuntu releases minimal Ubuntu for containers in July, 2018.

According to https://blog.ubuntu.com/2018/07/09/minimal-ubuntu-released


-29Mbytes of docker image size.

-It is  based 18.04 (LTS ) - Long terms support availability.

-Minimal security attack surface

-Faster speed to bringup.

It seems to be providing best of both worlds


-Ubuntu, which ONAP has been basing on so far.  Also, supported by 
Canonical.

-Less disk size and faster bootup.

-Supports multiple architecture (ARM, x86, PPC etc...)

Some more info from dockerhub: 
https://github.com/docker-library/repo-info/blob/master/repos/ubuntu/remote/18.10.md

Thanks
Srini





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4582): https://lists.onap.org/g/onap-tsc/message/4582
Mute This Topic: https://lists.onap.org/mt/29693473/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Looking for input on the Next ONAP Winter DDF #poll

[Srini]

Either

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Thursday, January 24, 2019 2:21 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Looking for input on the Next ONAP Winter DDF #poll


A new poll has been created:

For next winter's DDF we are trying to line things up well in advance in a way 
that follows both the budgetary and collaborative objectives of the LFN Board.
Please select the choice that would work better for you.

Note- this is a poll, not a discussion. Yes, we are aware that neither of these 
date choices are particularly ideal.

1. December 16 - 20, 2019
2. January 6 - 10, 2020
3. Either

Vote Now


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4514): https://lists.onap.org/g/onap-tsc/message/4514
Mute This Topic: https://lists.onap.org/mt/29531064/21656
Mute #poll: https://lists.onap.org/mk?hashtag=poll=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Data Lake

[Srini]

Just to add some more information:


-Apache Kafka added Authorization and ACLs functionality 
(http://kafka.apache.org/documentation/#securoty_authz) which allows providing 
configurable access control to external entities that need access to Kafka 
topics..

-Kafka Operator (https://github.com/strimzi/strimzi-kafka-operator) 
made it simple to create ACLs using Kubernetes resources.

Both of above technologies/features can be added.

>From the workflow perspective, there are two operations by the ONAP user:


-Register external Kafka entity (In this case, external data like is a 
kafka client)

-Unregister the entity.

It is similar to the way cloud-regions are registered via ESR. Records can be 
added to A DB.
One can provide GUI/CLI to make it simple for ONAP-users to add these in A

As part of registration, one can add users or certificate names and topic they 
are allowed to subscribe to.  When external entity registered in A, it can 
trigger the kafka operator to add the ACL records.

With this,  each data lake can be brought up outside of ONAP and register that 
with A by ONAP-User. Once that happens, data lake can get hold of any 
messages produced on the topic and can store in its databases and provide any 
analytics.

Thanks
Srini


From: Addepalli, Srinivasa R
Sent: Thursday, January 17, 2019 2:12 PM
To: onap-tsc@lists.onap.org
Subject: RE: Data Lake

My view is that data lakes (this one or any other data lake) can be considered 
as external entities (can be brought up ONAP like any other VNFs or via some 
other mechanisms). That includes feeder and UI.

>From ONAP perspective, we need to ensure that Kafka bus is accessible by third 
>party systems, that is,  authenticated registration of third party systems and 
>RBAC on topics etc...

Since this datalake is specific to ONAP monitoring, I guess it is required that 
all modules send all its telemetry data and transaction data to Kafka.  In my 
view, ideal thing is to do this integration from ISTIO side car.

Thanks
Srini


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Thursday, January 17, 2019 1:19 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Data Lake

Hi All,

During the TSC discussion today on the data lake; the discussion was leading 
towards considering the data lake feeder as part of DCAE.  Upon further 
reflection, I was wondering whether we should also consider including it as 
part of DMAAP as an alternative option.  Just for consideration.

BR,

Steve

[http://www.ericsson.com]<http://www.ericsson.com/>

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com<http://www.ericsson.com/>

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

Our commitment to Technology for 
Good<http://www.ericsson.com/thecompany/sustainability-corporateresponsibility> 
and Diversity and 
Inclusion<http://www.ericsson.com/thecompany/diversity-inclusion> contributes 
to positive change.
Follow us on: Facebook<https://www.facebook.com/ericsson> 
LinkedIn<https://www.linkedin.com/company/ericsson> 
Twitter<https://twitter.com/Ericsson>

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer<https://www.ericsson.com/en/legal/privacy/email-disclaimer>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4492): https://lists.onap.org/g/onap-tsc/message/4492
Mute This Topic: https://lists.onap.org/mt/29189968/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Data Lake

[Srini]

My view is that data lakes (this one or any other data lake) can be considered 
as external entities (can be brought up ONAP like any other VNFs or via some 
other mechanisms). That includes feeder and UI.

>From ONAP perspective, we need to ensure that Kafka bus is accessible by third 
>party systems, that is,  authenticated registration of third party systems and 
>RBAC on topics etc...

Since this datalake is specific to ONAP monitoring, I guess it is required that 
all modules send all its telemetry data and transaction data to Kafka.  In my 
view, ideal thing is to do this integration from ISTIO side car.

Thanks
Srini


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Thursday, January 17, 2019 1:19 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Data Lake

Hi All,

During the TSC discussion today on the data lake; the discussion was leading 
towards considering the data lake feeder as part of DCAE.  Upon further 
reflection, I was wondering whether we should also consider including it as 
part of DMAAP as an alternative option.  Just for consideration.

BR,

Steve

[http://www.ericsson.com]<http://www.ericsson.com/>

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com<http://www.ericsson.com/>

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

Our commitment to Technology for 
Good<http://www.ericsson.com/thecompany/sustainability-corporateresponsibility> 
and Diversity and 
Inclusion<http://www.ericsson.com/thecompany/diversity-inclusion> contributes 
to positive change.
Follow us on: Facebook<https://www.facebook.com/ericsson> 
LinkedIn<https://www.linkedin.com/company/ericsson> 
Twitter<https://twitter.com/Ericsson>

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer<https://www.ericsson.com/en/legal/privacy/email-disclaimer>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4486): https://lists.onap.org/g/onap-tsc/message/4486
Mute This Topic: https://lists.onap.org/mt/29189968/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Dublin Release - TSC Prioritization (Latest Updates)

[Srini]

Hi Steve,

I did not understand the response. You meant to reply to some other email?

Thanks
Srini


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Monday, January 14, 2019 8:33 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Dublin Release - TSC Prioritization (Latest Updates)

Hmmm, don’t know.  I know he was looking at S3P, but I am not aware of what he 
was looking at for xNFs and PNFs.

On 14 Jan 2019, at 14:51, Srini 
mailto:srinivasa.r.addepa...@intel.com>> wrote:
Hi,

On this “#5 Distributed Analytics as a Service (Phase 1) – Request raised by 
the Control Loop Subcommittee to get additional information”

In phase1, we will not be able to get to the stage of integrating with CLAMP or 
DCAE framework. In phase1, intention is to develop charts needed for big data 
analytics framework and prove that one set of charts can be used to create 
multiple instances in various sites.

At the same time, During first 3 months of this year, intention is to figure 
out the architecture direction for distributed functions  in general and then 
figure out the path for distributed analytics. Ramki is starting these 
discussion first in edge-automation working group as a task force for 
architecture committee. Goal is to provide architecture direction during ONS.

Hi Pam,

We (Dileep, Ramki or I) can present in any upcoming ‘Control Loop Subcommittee’ 
meetings on phase1 scope.  Please let us know which day work for you.

Thanks
Srini



From: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> 
[mailto:onap-...@lists.onap.org] On Behalf Of Catherine LEFEVRE
Sent: Monday, January 14, 2019 4:02 AM
To: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Subject: [Onap-arc] Dublin Release - TSC Prioritization (Latest Updates)
Importance: High

Good morning/afternoon/morning ONAP Community,

The latest TSC Prioritization spreadsheet (v11) has been uploaded: 
https://wiki.onap.org/display/DW/Dublin+Release+Requirements
I have also enhanced the Dublin Release Requirements wiki page accordingly.

I would like to share additional feedback/action items captured during the 
APAC/EMEA/US sessions organized last week and this morning:

#1 S3P requirements will be presented by Jason Hunt during the PTL call (1/14): 
https://wiki.onap.org/pages/viewpage.action?pageId=16003367
#2 vFW enhancements: Marco to confirm if APPC is impacted or not
#3 Consistent ID of a Cloud Region – OOF PTL to reply to Bing Yang
#4 Change Management Dublin Extensions – Use Case Owner (Ajay Mahimkar) to 
review the flows based on Architecture feedback and to discuss with VID/SDC PTLs
#5 Distributed Analytics as a Service (Phase 1) – Request raised by the Control 
Loop Subcommittee to get additional information
#6 Modularity –Use Case Owner (John NG/Seshu) to contact SDC PTL (Ofir)
#7 ETSI Alignment (SO plug-in) - Use Case Owner (Fred, Ciaran) to contact SDC 
PTL (Ofir)
#8 PNF/xNF will be presented by Jason Hunt during the PTL call (1/14)

The following items are currently “NO GO”:
#1 OSAM/PNF – no clarification has been provided to PTLs
#2  S3P - Service Mesh (ISTIO) except if covered by Extra Resource
#3 Tosca Task Force – PTLs are requesting additional information about the 5 
requirements
#4 Allotted Network Function – no clarification has been provided to PTLs
#5 - S3P Manageability - Logging capabilities – no clarification has been 
provided to PTLs

If I have miscaptured or missed anything then I would like to invite you to 
update the wiki page accordingly.
https://wiki.onap.org/display/DW/Dublin+Release+Requirements

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT Labs – Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>

TEXTING and DRIVING… It Can Wait

AT
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



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this grou

Re: [onap-tsc] Dublin Release - TSC Prioritization (Latest Updates)

[Srini]

Hi,

On this "#5 Distributed Analytics as a Service (Phase 1) - Request raised by 
the Control Loop Subcommittee to get additional information"

In phase1, we will not be able to get to the stage of integrating with CLAMP or 
DCAE framework. In phase1, intention is to develop charts needed for big data 
analytics framework and prove that one set of charts can be used to create 
multiple instances in various sites.

At the same time, During first 3 months of this year, intention is to figure 
out the architecture direction for distributed functions  in general and then 
figure out the path for distributed analytics. Ramki is starting these 
discussion first in edge-automation working group as a task force for 
architecture committee. Goal is to provide architecture direction during ONS.

Hi Pam,

We (Dileep, Ramki or I) can present in any upcoming 'Control Loop Subcommittee' 
meetings on phase1 scope.  Please let us know which day work for you.

Thanks
Srini



From: onap-...@lists.onap.org [mailto:onap-...@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Monday, January 14, 2019 4:02 AM
To: onap-rele...@lists.onap.org; onap-tsc@lists.onap.org; 
onap-...@lists.onap.org; onap-sec...@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: [Onap-arc] Dublin Release - TSC Prioritization (Latest Updates)
Importance: High

Good morning/afternoon/morning ONAP Community,

The latest TSC Prioritization spreadsheet (v11) has been uploaded: 
https://wiki.onap.org/display/DW/Dublin+Release+Requirements
I have also enhanced the Dublin Release Requirements wiki page accordingly.

I would like to share additional feedback/action items captured during the 
APAC/EMEA/US sessions organized last week and this morning:

#1 S3P requirements will be presented by Jason Hunt during the PTL call (1/14): 
https://wiki.onap.org/pages/viewpage.action?pageId=16003367
#2 vFW enhancements: Marco to confirm if APPC is impacted or not
#3 Consistent ID of a Cloud Region - OOF PTL to reply to Bing Yang
#4 Change Management Dublin Extensions - Use Case Owner (Ajay Mahimkar) to 
review the flows based on Architecture feedback and to discuss with VID/SDC PTLs
#5 Distributed Analytics as a Service (Phase 1) - Request raised by the Control 
Loop Subcommittee to get additional information
#6 Modularity -Use Case Owner (John NG/Seshu) to contact SDC PTL (Ofir)
#7 ETSI Alignment (SO plug-in) - Use Case Owner (Fred, Ciaran) to contact SDC 
PTL (Ofir)
#8 PNF/xNF will be presented by Jason Hunt during the PTL call (1/14)

The following items are currently "NO GO":
#1 OSAM/PNF - no clarification has been provided to PTLs
#2  S3P - Service Mesh (ISTIO) except if covered by Extra Resource
#3 Tosca Task Force - PTLs are requesting additional information about the 5 
requirements
#4 Allotted Network Function - no clarification has been provided to PTLs
#5 - S3P Manageability - Logging capabilities - no clarification has been 
provided to PTLs

If I have miscaptured or missed anything then I would like to invite you to 
update the wiki page accordingly.
https://wiki.onap.org/display/DW/Dublin+Release+Requirements

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>

TEXTING and DRIVING... It Can Wait

AT
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



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4461): https://lists.onap.org/g/onap-tsc/message/4461
Mute This Topic: https://lists.onap.org/mt/29078411/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] SDC Update

[Srini]

Hi Michael,

It was nice knowing. I wish you the best in your future endeavors.

Srini

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of Lior Nachmias
Sent: Sunday, December 2, 2018 12:32 AM
To: Lando,Michael ; ONAP-TSC@lists.onap.org
Cc: 'onap-...@lists.onap.org' ; 
onap-disc...@lists.onap.org; Merkado, Tomer ; 
Sonsino, Ofir ; Gitelman, Tal 
; Shlosberg, Yuli ; 
Amit, Idan ; EMPOROPULO, VITALIY 
; Avi Gaffa ; 
oren...@amdocs.com; WEISS KEIDAR, EINAV ; 
halfon@amdocs.com; Lefevre, Catherine ; 
micla...@gmail.com
Subject: Re: [onap-discuss] SDC Update

Michael,

On behalf of AT SDC team I would like to thank you for your all your efforts 
and dedication.
Good luck on your new journey.

Regards,
Lior

From: Lando,Michael
Sent: Friday, November 30, 2018 1:53 AM
To: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Cc: 'onap-...@lists.onap.org' 
mailto:onap-...@lists.onap.org>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; Merkado, Tomer 
mailto:tomer.merk...@intl.att.com>>; Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Sonsino, Ofir 
mailto:ofir.sons...@intl.att.com>>; Gitelman, Tal 
mailto:tal.gitel...@intl.att.com>>; Shlosberg, Yuli 
mailto:yuli.shlosb...@intl.att.com>>; Amit, Idan 
mailto:idan.a...@intl.att.com>>; EMPOROPULO, VITALIY 
mailto:vitaliy.emporop...@amdocs.com>>; Avi 
Gaffa mailto:avraham.ga...@amdocs.com>>; 
oren...@amdocs.com<mailto:oren...@amdocs.com>; WEISS KEIDAR, EINAV 
mailto:einav.we...@amdocs.com>>; 
halfon@amdocs.com<mailto:halfon@amdocs.com>; Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
micla...@gmail.com<mailto:micla...@gmail.com>
Subject: SDC Update

Hello,

I Would like to submit my resignation from the PTL position in SDC,
As I am leaving my compony I will no Longer be able to participate in the 
Project.

The committers for SDC are already aware of this change.

With this notification I would also like to open the nominations to replace me 
as the SDC PTL.









BR,

[Michael Lando]

AT Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com<mailto:michael.la...@intl.att.com>



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4215): https://lists.onap.org/g/onap-tsc/message/4215
Mute This Topic: https://lists.onap.org/mt/28560646/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] Location for usecase specific files modules/scripts/artifacts

[Srini]

Thanks Marco for your feedback and support.

Srini


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, November 30, 2018 2:26 PM
To: Addepalli, Srinivasa R ; 
'onap-disc...@lists.onap.org' ; 
'eric.deb...@orange.com' ; 'onap-tsc@lists.onap.org' 
; Kishore, Akhila 
Subject: Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

That’s good for me. You can put that in [demo]/vnfs

Marco

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Friday, November 30, 2018 at 1:04 PM
To: "'onap-disc...@lists.onap.org'" 
mailto:onap-disc...@lists.onap.org>>, 
"'eric.deb...@orange.com'" 
mailto:eric.deb...@orange.com>>, 
"'onap-tsc@lists.onap.org'" 
mailto:onap-tsc@lists.onap.org>>, "PLATANIA, MARCO 
(MARCO)" mailto:plata...@research.att.com>>, 
"Kishore, Akhila" mailto:akhila.kish...@intel.com>>
Subject: RE: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi Marco and integration team,

This is one thought we have on directory structure in demo repository for K8S 
use cases.


·K8Susecases>

o   EdgeXFoundry>

§  Flavor1>

·Artifacts>

o   Helm Charts>

o   Service>

o   Values.yaml (overriding parameter values)

o   Day0config>

§  

§  

·

·

·…. (multiple metadata and configuration file)

§  ….

o   OOF policies>

§  HPA policies>

§  ….

·Scripts> (For automation)

·Modules> (use case specific modules – binaries/simple source to run 
E2E use case)

·DGs> (use case specific DGs)

·Drools-programs>

§  Flavor2>

o   vFirewall>

o   analytics-standard>

o   analytics-minimal>

o   analytics-app-1>

Does that sound reasonable for the integration team?

Thanks
Srini


From: Addepalli, Srinivasa R
Sent: Thursday, November 29, 2018 1:23 PM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
eric.deb...@orange.com<mailto:eric.deb...@orange.com>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>
Subject: RE: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Yes. Good example there on CCVPN specific DG.

These are of some of the things, which are in ONAP project repositories, give 
an impression to outsiders that ONAP has use-case specific code.

In my view, it is best to put CCVPN DG  in CCVPN usecase specific 
repo/directory.

Another example, which I can think of for usecases we are working on is to put 
Drools policies that are specific to usecase.

Thanks
Srini


From: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> 
[mailto:onap-disc...@lists.onap.org] On Behalf Of Eric Debeau
Sent: Thursday, November 29, 2018 12:16 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hello Srini

That is a good point you raised

I think that we should clarify where to put the various use-case artifacts in 
ONAP.

We have some artifacts in demo (eg Heat   for VNF to be used in various 
use-cases: vFW, vCPE and some specific code for VNF)
We have some specific DG in SNDC project (eg CC-VPN)
A place to put global use-case information in doc project (only vFW)
…

And a lot, lot, lot  of material in the wiki

Yet another topic to solve at TSC level.

Best Regards

Eric


De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] De la part de Srini
Envoyé : jeudi 29 novembre 2018 20:53
À : PLATANIA, MARCO (MARCO); 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Objet : Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Srini

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 11:46 AM
To: Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
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-discuss] Location for usecase specific files 
modules/scripts/artifacts

Same standard procedure as every other repository. It’s managed by the 
Integration Team, so committers are myself, Gary Wu, Helen, Yang Xu and others 
I suppose.

Marco

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 1:24 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plat

Re: [onap-tsc] [onap-discuss] Location for usecase specific files modules/scripts/artifacts

[Srini]

Hi Marco and integration team,

This is one thought we have on directory structure in demo repository for K8S 
use cases.


·K8Susecases>

o   EdgeXFoundry>

§  Flavor1>

·Artifacts>

o   Helm Charts>

o   Service>

o   Values.yaml (overriding parameter values)

o   Day0config>

§  

§  

·

·

·…. (multiple metadata and configuration file)

§  ….

o   OOF policies>

§  HPA policies>

§  ….

·Scripts> (For automation)

·Modules> (use case specific modules – binaries/simple source to run 
E2E use case)

·DGs> (use case specific DGs)

·Drools-programs>

§  Flavor2>

o   vFirewall>

o   analytics-standard>

o   analytics-minimal>

o   analytics-app-1>

Does that sound reasonable for the integration team?

Thanks
Srini


From: Addepalli, Srinivasa R
Sent: Thursday, November 29, 2018 1:23 PM
To: onap-disc...@lists.onap.org; eric.deb...@orange.com; 
onap-tsc@lists.onap.org; PLATANIA, MARCO (MARCO) 
Subject: RE: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Yes. Good example there on CCVPN specific DG.

These are of some of the things, which are in ONAP project repositories, give 
an impression to outsiders that ONAP has use-case specific code.

In my view, it is best to put CCVPN DG  in CCVPN usecase specific 
repo/directory.

Another example, which I can think of for usecases we are working on is to put 
Drools policies that are specific to usecase.

Thanks
Srini


From: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> 
[mailto:onap-disc...@lists.onap.org] On Behalf Of Eric Debeau
Sent: Thursday, November 29, 2018 12:16 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hello Srini

That is a good point you raised

I think that we should clarify where to put the various use-case artifacts in 
ONAP.

We have some artifacts in demo (eg Heat   for VNF to be used in various 
use-cases: vFW, vCPE and some specific code for VNF)
We have some specific DG in SNDC project (eg CC-VPN)
A place to put global use-case information in doc project (only vFW)
…

And a lot, lot, lot  of material in the wiki

Yet another topic to solve at TSC level.

Best Regards

Eric


De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] De la part de Srini
Envoyé : jeudi 29 novembre 2018 20:53
À : PLATANIA, MARCO (MARCO); 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Objet : Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Srini

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 11:46 AM
To: Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
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-discuss] Location for usecase specific files 
modules/scripts/artifacts

Same standard procedure as every other repository. It’s managed by the 
Integration Team, so committers are myself, Gary Wu, Helen, Yang Xu and others 
I suppose.

Marco

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 1:24 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Yes, intention is not to add any ONAP component related code/patches in usecase 
directory.

Demo repository:  Does it go through same merging process? If so, who are 
committers and reviewers for this?

Thanks
Srini


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 10:10 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; Addepalli, 
Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi Srini,

A few use cases use the Demo repository to store Heat templates, scripts, and 
VNF-specific code, as you noticed. The same repo could be used by your use case 
too. Note that Demo doesn’t host any ONAP component

Re: [onap-tsc] [onap-discuss] Location for usecase specific files modules/scripts/artifacts

[Srini]

Yes. Good example there on CCVPN specific DG.

These are of some of the things, which are in ONAP project repositories, give 
an impression to outsiders that ONAP has use-case specific code.

In my view, it is best to put CCVPN DG  in CCVPN usecase specific 
repo/directory.

Another example, which I can think of for usecases we are working on is to put 
Drools policies that are specific to usecase.

Thanks
Srini


From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of Eric Debeau
Sent: Thursday, November 29, 2018 12:16 PM
To: onap-tsc@lists.onap.org; PLATANIA, MARCO (MARCO) 
; onap-disc...@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hello Srini

That is a good point you raised

I think that we should clarify where to put the various use-case artifacts in 
ONAP.

We have some artifacts in demo (eg Heat   for VNF to be used in various 
use-cases: vFW, vCPE and some specific code for VNF)
We have some specific DG in SNDC project (eg CC-VPN)
A place to put global use-case information in doc project (only vFW)
…

And a lot, lot, lot  of material in the wiki

Yet another topic to solve at TSC level.

Best Regards

Eric


De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] De la part de Srini
Envoyé : jeudi 29 novembre 2018 20:53
À : PLATANIA, MARCO (MARCO); 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Objet : Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Srini

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 11:46 AM
To: Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
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-discuss] Location for usecase specific files 
modules/scripts/artifacts

Same standard procedure as every other repository. It’s managed by the 
Integration Team, so committers are myself, Gary Wu, Helen, Yang Xu and others 
I suppose.

Marco

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 1:24 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Yes, intention is not to add any ONAP component related code/patches in usecase 
directory.

Demo repository:  Does it go through same merging process? If so, who are 
committers and reviewers for this?

Thanks
Srini


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 10:10 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; Addepalli, 
Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi Srini,

A few use cases use the Demo repository to store Heat templates, scripts, and 
VNF-specific code, as you noticed. The same repo could be used by your use case 
too. Note that Demo doesn’t host any ONAP component code. For that, other repos 
are used.

Not sure what CCVPN and VoLTE do.

Marco

From: mailto:onap-disc...@lists.onap.org>> on 
behalf of Srini 
mailto:srinivasa.r.addepa...@intel.com>>
Reply-To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 12:57 PM
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>
Subject: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi,


For “K8S based Cloud-region support” work, we intend to prove  with three use 
cases


-Deploying EdgeXFoundry

-Deploying vFirewall using K8S

-Deploying Service assurance framework and apps.

These requires creation of artifacts, some scripts and even possibly some 
usecase specific modules.
Where do usecase specific files put in ONAP?
Main intention is that anybody in community can run these usecases and hence 
wa

Re: [onap-tsc] [onap-discuss] Location for usecase specific files modules/scripts/artifacts

[Srini]

Thanks Marco.

Srini

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 11:46 AM
To: Addepalli, Srinivasa R ; 
onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Same standard procedure as every other repository. It’s managed by the 
Integration Team, so committers are myself, Gary Wu, Helen, Yang Xu and others 
I suppose.

Marco

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 1:24 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Yes, intention is not to add any ONAP component related code/patches in usecase 
directory.

Demo repository:  Does it go through same merging process? If so, who are 
committers and reviewers for this?

Thanks
Srini


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 10:10 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; Addepalli, 
Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi Srini,

A few use cases use the Demo repository to store Heat templates, scripts, and 
VNF-specific code, as you noticed. The same repo could be used by your use case 
too. Note that Demo doesn’t host any ONAP component code. For that, other repos 
are used.

Not sure what CCVPN and VoLTE do.

Marco

From: mailto:onap-disc...@lists.onap.org>> on 
behalf of Srini 
mailto:srinivasa.r.addepa...@intel.com>>
Reply-To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 12:57 PM
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>
Subject: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi,


For “K8S based Cloud-region support” work, we intend to prove  with three use 
cases


-Deploying EdgeXFoundry

-Deploying vFirewall using K8S

-Deploying Service assurance framework and apps.

These requires creation of artifacts, some scripts and even possibly some 
usecase specific modules.
Where do usecase specific files put in ONAP?
Main intention is that anybody in community can run these usecases and hence 
want to put all usecase specific files in ONAP for them to easily access them.

I see demo repository for vCPE, vFW and vDNS.
Is this the right place for all other usecases?
BTW, I don’t see any files related to CCVPN, VoLTE usecase. Are they placed 
elsewhere?

Any guidance from the TSC/community is appreciated.

Thanks
Srini





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4200): https://lists.onap.org/g/onap-tsc/message/4200
Mute This Topic: https://lists.onap.org/mt/28501718/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] Location for usecase specific files modules/scripts/artifacts

[Srini]

Thanks Marco.

Yes, intention is not to add any ONAP component related code/patches in usecase 
directory.

Demo repository:  Does it go through same merging process? If so, who are 
committers and reviewers for this?

Thanks
Srini


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 10:10 AM
To: onap-disc...@lists.onap.org; Addepalli, Srinivasa R 
; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi Srini,

A few use cases use the Demo repository to store Heat templates, scripts, and 
VNF-specific code, as you noticed. The same repo could be used by your use case 
too. Note that Demo doesn’t host any ONAP component code. For that, other repos 
are used.

Not sure what CCVPN and VoLTE do.

Marco

From: mailto:onap-disc...@lists.onap.org>> on 
behalf of Srini 
mailto:srinivasa.r.addepa...@intel.com>>
Reply-To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 12:57 PM
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>
Subject: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi,


For “K8S based Cloud-region support” work, we intend to prove  with three use 
cases


-Deploying EdgeXFoundry

-Deploying vFirewall using K8S

-Deploying Service assurance framework and apps.

These requires creation of artifacts, some scripts and even possibly some 
usecase specific modules.
Where do usecase specific files put in ONAP?
Main intention is that anybody in community can run these usecases and hence 
want to put all usecase specific files in ONAP for them to easily access them.

I see demo repository for vCPE, vFW and vDNS.
Is this the right place for all other usecases?
BTW, I don’t see any files related to CCVPN, VoLTE usecase. Are they placed 
elsewhere?

Any guidance from the TSC/community is appreciated.

Thanks
Srini





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4198): https://lists.onap.org/g/onap-tsc/message/4198
Mute This Topic: https://lists.onap.org/mt/28501718/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Location for usecase specific files modules/scripts/artifacts

[Srini]

Hi,


For "K8S based Cloud-region support" work, we intend to prove  with three use 
cases


-Deploying EdgeXFoundry

-Deploying vFirewall using K8S

-Deploying Service assurance framework and apps.

These requires creation of artifacts, some scripts and even possibly some 
usecase specific modules.
Where do usecase specific files put in ONAP?
Main intention is that anybody in community can run these usecases and hence 
want to put all usecase specific files in ONAP for them to easily access them.

I see demo repository for vCPE, vFW and vDNS.
Is this the right place for all other usecases?
BTW, I don't see any files related to CCVPN, VoLTE usecase. Are they placed 
elsewhere?

Any guidance from the TSC/community is appreciated.

Thanks
Srini




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4196): https://lists.onap.org/g/onap-tsc/message/4196
Mute This Topic: https://lists.onap.org/mt/28501599/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) #tac

[Srini]

Hi Catherine and Chaker,

My 2 cents.

There are two contexts I guess feedback is given.

Usage of TF in ONAP: TF in many ways similar to ODL in terms of role and 
capabilities. ODL is chosen by ONAP as base for CCSDK/SDNC/APPC. Is TAC asking 
to see whether TF can be leveraged by ONAP in place of ODL?

Using TF in sites as site level SDN controller : In case of Openstack based 
sites, it is really up to the site administrator and from ONAP perspective it 
is  transparent as ONAP leverages Neutron API.  In case of K8S based sites, 
there is some support required in ONAP (Multi-Cloud) based on SDN controller 
chosen at the site. K8S Multi-Cloud intend to support OVN, flannel, SRIOV-NIC 
based networks initially (R4) and get community feedback on other networking 
controllers (Yes, we see requests coming to us to support Contiv and TF, but 
the decision to be made at right time based on interest from SPs on the site 
level SDN controllers).

Thanks
Srini


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Chaker Al Hakim
Sent: Thursday, October 25, 2018 8:41 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Hi Catherine,

Please count me unless you have found a lead already.

Thanks,
Chaker


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Catherine LEFEVRE
Sent: Thursday, October 25, 2018 5:07 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) #tac
Importance: High

Dear TSC (or proxy),

We have been requested by the TAC to review the Tungsten Fabric proposal.
I have added the links related to this proposal to the JIRA TSC-41 task.

I need somebody to take the lead regarding this activity.
Can one of you assign this task to herself/himself while the others can post 
any feedback to the JIRA ticket? thanks
Due Date: Nov 5th, 2018 End of your Day?
https://jira.onap.org/browse/TSC-41

Thanks in advance for your support.

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


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
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



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3985): https://lists.onap.org/g/onap-tsc/message/3985
Mute This Topic: https://lists.onap.org/mt/27630566/21656
Mute #tac: https://lists.onap.org/mk?hashtag=tac=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Usecase subcommittee - agenda for 15/10/2018

[Srini]

Hi Alla,

"Kubernetes based Cloud-region support " was approved in R3 to start initial 
work and make it as a functional requirement in R4.  Like to have 15 minutes to 
provide status, talk about R4 items and projects that may get impacted.

Thanks
Srini


From: onap-usecase...@lists.onap.org [mailto:onap-usecase...@lists.onap.org] On 
Behalf Of Alla Goldner
Sent: Friday, October 12, 2018 10:55 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: [Onap-usecasesub] Usecase subcommittee - agenda for 15/10/2018

Hi all,

The agenda for the upcoming Monday meeting is:


1.  Presentation of Bell requirements for Dublin

2.  Presentation of Edge Automation plans for Dublin

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D462C5.12119AD0]

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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3903): https://lists.onap.org/g/onap-tsc/message/3903
Mute This Topic: https://lists.onap.org/mt/27272972/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Edge Automation working group proposal

[Srini]

Hi Pasi and all,

Thank  you for the input. I sent one response to Catherine. Our emails crossed.

This group is trying to gather requirements(such as MEC, Distributed analytics, 
scaling, security, regulatory,  constrained environments),  figure out the 
architecture with ONAP to meet those requirements, identify gaps and feed them 
to various existing subcommittees. I agree that much of the output (can be new) 
 that comes out of Edge group may be generic in nature.

Team is also very flexible in listening for ideas on best way to take this 
forward - Status Quo as it is today (working group under use case subcommittee 
with additional coordinator position),  Edge subcommittee or a task force under 
TSC. The term 'task force' does not appeal to me as it appears that it is for a 
task and give impression that it is temporary.

I don't want to get ahead of what the edge group plans to present in TSC :).  I 
think team will get chance to present this  in next TSC and we can go from 
there.

Thanks
Srini

[cid:image001.png@01D46209.17E37F80]

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Pasi Vaananen
Sent: Friday, October 12, 2018 8:01 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Edge Automation working group proposal




On 10/12/2018 07:30 AM, Catherine LEFEVRE wrote:
Good morning Srini,

Thank you for sharing the work that has been accomplished by the "Edge 
Automation" working group.

One of our major ONAP Community challenges is the prioritization of our 
activities.
I am concerned that the creation of a 6th subcommittee will increase the 
complexity we are already facing today
to determine what can be accomplished on a release basis considering our 
development/testing capacity and then to deliver our commitments on time and 
quality.

Have you explored the possibility that the "Edge Automation" working group 
could be part of one of the existing subcommittees i.e. Architecture or Use 
Case subcommittees
even if dedicated sessions/task force activities are organized related to this 
topic ?

+1 - what is fundamentally required to enable edge use cases with ONAP services 
with minimal duplication of efforts / maximum re-use are enabling architectural 
changes, not entirely new "thing" on the side.

As such, IMHO, this would be a better fit as an Architecture subcommittee 
related task force.

Best regards,

Pasi

Best regards
Catherine
From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Srini
Sent: Thursday, October 11, 2018 1:31 AM
To: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: [onap-tsc] Edge Automation working group proposal

Hi TSC,

As you all know, Edge automation working group is formed in April/May of this 
year as ADHOC group. Its intention is to  identify ONAP requirements that arise 
from supporting various kinds of edges/edge applications  and propose those 
requirements as functional,  closed loop, security, architecture inputs to 
various subcommittees.  This is being co-chaired by Ramki and Raghu. This group 
meets on weekly basis and continue to attract multiple stake holders.

Tomorrow, Ramki & Raghu are presenting a proposal to take Edge automation 
working group to next level to bring industry-wide visibility and visibility 
within the ONAP community.  Formalization of the group in ONAP charter is the 
step the group wants to propose tomorrow.

Please see the proposal here:  
https://wiki.onap.org/display/DW/Edge+Sub-committee+creation+proposal<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Edge-2BSub-2Dcommittee-2Bcreation-2Bproposal=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=aowlSSV3c29kMC_TzkQzurCs88DAw9YnFDMNS8PyBtk=T7fbofIwugI2fd1YCOsbebJVrEa-Ertu19evct8ETjY=>
Presentation deck here:  
https://wiki.onap.org/download/attachments/28379482/ONAP-edge-proposal-v1.pptx?api=v2<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_download_attachments_28379482_ONAP-2Dedge-2Dproposal-2Dv1.pptx-3Fapi-3Dv2=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=aowlSSV3c29kMC_TzkQzurCs88DAw9YnFDMNS8PyBtk=GbUBODPE46f4yK_2eC4KoMSgYuiUlZEEZURVWR0_mNg=>

Looking forward to your support.

Thanks
Srini






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3898): https://lists.onap.org/g/onap-tsc/message/3898
Mute This Topic: https://lists.onap.org/mt/27216848/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

[Srini]

+1 (on API change)

Thanks
Srini


From: onap-tsc-v...@lists.onap.org [mailto:onap-tsc-v...@lists.onap.org] On 
Behalf Of Catherine LEFEVRE
Sent: Friday, October 12, 2018 3:41 AM
To: onap-tsc@lists.onap.org; onap-tsc-v...@lists.onap.org
Cc: onap-discuss ; Seshu m 
; TIMONEY, DAN 
Subject: Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between 
SO and SDNC
Importance: High

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
·Andreas Geissler (DT)
·Ranny Haiby, Nokia
·David Sauvageau, Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT
·Eric Debeau, Orange
·Jason Hunt, IBM
·Srinivasa Addepalli, Intel
·Murat Turpcu,turk telekom
·Ning So, Reliance Jio
·Lingli Deng, CMCC
·Alla Goldner, Amdocs
·Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·Stephen Terrill, Ericsson
·Susana Sabater, Vodafone
·Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3897): https://lists.onap.org/g/onap-tsc/message/3897
Mute This Topic: https://lists.onap.org/mt/27271291/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Edge Automation working group proposal

[Srini]

Hi Catherine,

Thank you for the email.

Based on the discussions in last edge-automation working group and also the 
slide deck, the working model is no different from current model. That is, 
output of this group will be fed as another input to various other 
subcommittees. So, there is no additional complexity.   Group is only asking to 
increase the visibility in ONAP member companies as well as to other edge 
related open source projects/standard-bodies by making official ONAP entity. 
Also, group provided two options. 1. Making it subcommittee 2. Increase 
visibility by other means + creating coordinator position.  Group preference is 
option 1.  But, it is up to TSC to decide.

Just for easy reference, I am adding the picture from the presentation deck.  
This is the working model now and continue to be working model even after 
making it as subcommittee.

[cid:image001.png@01D46201.A7A7FA40]



From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Friday, October 12, 2018 4:31 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Edge Automation working group proposal

Good morning Srini,

Thank you for sharing the work that has been accomplished by the "Edge 
Automation" working group.

One of our major ONAP Community challenges is the prioritization of our 
activities.
I am concerned that the creation of a 6th subcommittee will increase the 
complexity we are already facing today
to determine what can be accomplished on a release basis considering our 
development/testing capacity and then to deliver our commitments on time and 
quality.

Have you explored the possibility that the "Edge Automation" working group 
could be part of one of the existing subcommittees i.e. Architecture or Use 
Case subcommittees
even if dedicated sessions/task force activities are organized related to this 
topic ?

Best regards
Catherine
From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Srini
Sent: Thursday, October 11, 2018 1:31 AM
To: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: [onap-tsc] Edge Automation working group proposal

Hi TSC,

As you all know, Edge automation working group is formed in April/May of this 
year as ADHOC group. Its intention is to  identify ONAP requirements that arise 
from supporting various kinds of edges/edge applications  and propose those 
requirements as functional,  closed loop, security, architecture inputs to 
various subcommittees.  This is being co-chaired by Ramki and Raghu. This group 
meets on weekly basis and continue to attract multiple stake holders.

Tomorrow, Ramki & Raghu are presenting a proposal to take Edge automation 
working group to next level to bring industry-wide visibility and visibility 
within the ONAP community.  Formalization of the group in ONAP charter is the 
step the group wants to propose tomorrow.

Please see the proposal here:  
https://wiki.onap.org/display/DW/Edge+Sub-committee+creation+proposal<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Edge-2BSub-2Dcommittee-2Bcreation-2Bproposal=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=aowlSSV3c29kMC_TzkQzurCs88DAw9YnFDMNS8PyBtk=T7fbofIwugI2fd1YCOsbebJVrEa-Ertu19evct8ETjY=>
Presentation deck here:  
https://wiki.onap.org/download/attachments/28379482/ONAP-edge-proposal-v1.pptx?api=v2<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_download_attachments_28379482_ONAP-2Dedge-2Dproposal-2Dv1.pptx-3Fapi-3Dv2=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=aowlSSV3c29kMC_TzkQzurCs88DAw9YnFDMNS8PyBtk=GbUBODPE46f4yK_2eC4KoMSgYuiUlZEEZURVWR0_mNg=>

Looking forward to your support.

Thanks
Srini





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3895): https://lists.onap.org/g/onap-tsc/message/3895
Mute This Topic: https://lists.onap.org/mt/27216848/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Edge Automation working group proposal

[Srini]

Hi TSC,

As you all know, Edge automation working group is formed in April/May of this 
year as ADHOC group. Its intention is to  identify ONAP requirements that arise 
from supporting various kinds of edges/edge applications  and propose those 
requirements as functional,  closed loop, security, architecture inputs to 
various subcommittees.  This is being co-chaired by Ramki and Raghu. This group 
meets on weekly basis and continue to attract multiple stake holders.

Tomorrow, Ramki & Raghu are presenting a proposal to take Edge automation 
working group to next level to bring industry-wide visibility and visibility 
within the ONAP community.  Formalization of the group in ONAP charter is the 
step the group wants to propose tomorrow.

Please see the proposal here:  
https://wiki.onap.org/display/DW/Edge+Sub-committee+creation+proposal
Presentation deck here:  
https://wiki.onap.org/download/attachments/28379482/ONAP-edge-proposal-v1.pptx?api=v2

Looking forward to your support.

Thanks
Srini




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3870): https://lists.onap.org/g/onap-tsc/message/3870
Mute This Topic: https://lists.onap.org/mt/27216848/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] TSC Seat Vanacy

[Srini]

We also need to consider two cases


1.  Where a  TSC member moves from one company to another company that has 
TSC representative already.

2.  Where a TSC member moves from one company to another that does not have 
TSC representative.

1st case is simple and it can be considered as TSC member resigning.
2nd case is complex. Would there be an election? Or would that member continues 
to be in TSC.  Since we have 1 member per company limitation, it is fair to 
consider this also as a resignation.

Thanks
Srini



From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Sunday, September 23, 2018 2:59 PM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] TSC Seat Vanacy

Hi,

To this effect.  An appointed size was agreed.  I think it makes sense to run a 
new election for that seat – continuing with the previous voting list does not 
take into account the current situation, as the voting was in the context of an 
earlier situation:

We need to take into account two situations as I see it:
-Any TSC member is no longer able to support the role
-The TSC member that can no longer support the role is a chair or vice 
chair.
-We need to cater for the appointed positions as well.

To this effect, can we amend the community charter as follows:
-Add to section 4.2.3:
o   4.2.3.3 TSC member abdication
§  In the event of a TSC member no longer being able to continue being a member 
of the TSC:
·If the TSC position was from an operator, the operator may appoint a 
member that fulfils the criteria of being an active member; if that is not 
feasible then the operator may appoint any member.  If this is not done, then 
the seat is considered vacant.  (Additional amendment to consider: If the TSC 
member that abdicated continues as an active member from the same company, then 
the TSC seat is considered vacant (I am not stronge on this, it just to avoid 
using this clause as a means to replace TSC members).
·If the TSC position is from one of the elected positions, an election 
for that single position is held.  The conditions of the election are the same 
as for any TSC election.
§  If the said position was of that of a TSC chair or vice-chair, then the TSC 
chair or vice chair position will undergo a re-election after the successful 
appointment of the new TSC member.
§  When the next General TSC election is held, the said TSC position will also 
be included in the general TSC election.

BR,

Steve

From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> 
mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Frank 
Brockners via Lists.Onap.Org
Sent: Sunday, September 23, 2018 7:19 PM
To: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-tsc] TSC Seat Vanacy

Hi Kenny,

Thanks for the summary. As a community member, I’d prefer if the TSC would 
quickly amend the current charter to cover the case of TSC members stepping 
down from their role. Any other approach would be a shot from the hip – and 
might be in conflict to the ultimate policy that the TSC would come up with. 
The amendment should cover the considerations that you list below, especially 
the fact that the TSC now consists of elected members and not representatives 
of parties, companies, etc. In that, a TSC differs from most of the 
parliaments, where members often represent parties, so that successors are 
automatically picked from a list.

Regards,
Frank

From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> 
mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Kenny 
Paul
Sent: Sonntag, 23. September 2018 18:43
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] TSC Seat Vanacy

I wanted to follow up on the discussion regarding a special election due to 
Chris taking a new job.  One of the first questions asked was, "What does the 
Charter say?"  Neither the Charter or Community Document says anything about a 
vacancy. In the absence of any specific language, the default should be to 
honor what language there is.  Currently the Community Document says:

4.1.1.2 Size and Structure
The TSC shall consist of eighteen (18) seats
Nine (9) seats on the TSC are to be reserved for Operators
Only one (1) person from any company, or group of related companies (as defined 
in section 4.4.4.1) may be a member at any given time.

As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.

There were a several alternatives to a special election which have been 
suggested. While it is well within the TSC's right to pursue any of these 
alternatives, all must be thoroughly scrutinized through the lens of fairness, 
trust, and responsibility to the community.


  *   Leaving the seat vacant until the next election cycle
It took 6 months to debate and vote on membe

Re: [onap-tsc] TSC Seat Vanacy

[Srini]

Hi Kenny,

On this
“
As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.
“

Is the authorization being requested for entire TSC (all 18 seats) election or 
only for the seat being vacated by Chris?

Thanks
Srini


From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Sunday, September 23, 2018 9:43 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] TSC Seat Vanacy

I wanted to follow up on the discussion regarding a special election due to 
Chris taking a new job.  One of the first questions asked was, "What does the 
Charter say?"  Neither the Charter or Community Document says anything about a 
vacancy. In the absence of any specific language, the default should be to 
honor what language there is.  Currently the Community Document says:

4.1.1.2 Size and Structure
The TSC shall consist of eighteen (18) seats
Nine (9) seats on the TSC are to be reserved for Operators
Only one (1) person from any company, or group of related companies (as defined 
in section 4.4.4.1) may be a member at any given time.

As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.

There were a several alternatives to a special election which have been 
suggested. While it is well within the TSC's right to pursue any of these 
alternatives, all must be thoroughly scrutinized through the lens of fairness, 
trust, and responsibility to the community.


  *   Leaving the seat vacant until the next election cycle
It took 6 months to debate and vote on membership criteria, and another full 
month to run an election. Leaving the seat vacant until the next scheduled 
election implies that after all that work the TSC doesn't care about being 
fully functional.  This would be a huge hit to the community's trust of the TSC.


  *   Delay any decision on an election until the TSC amends the Community 
Document to address how to handle a vacancy
This is marginally better than leaving the seat vacant, because who knows how 
long amending the Community Document might take. I would encourage the TSC to 
take up amending the Community Document to cover one or more of the operational 
and governance gaps that exist, however it is unfair to the ONAP community to 
hold the recently vacated seat hostage to those discussions.


  *   Have Chris appoint his replacement
When the TSC was comprised of only appointed individuals doing this would have 
been fine course of action. In fact, there were a couple instances back in 
March where this occurred. Now that we have moved from an appointed TSC to an 
elected TSC, such an appointment by a member is completely inappropriate.


  *   Make the next runner up in the August election the new TSC member
While true the seat does not belong to Huawei, it would be exceeding unfair to 
them, especially as the 2nd largest contributor to the Project, to suddenly be 
out in the cold with absolutely no chance to even compete for a seat they once 
held.

I don't like creating work for myself and a TCS election is indeed a great deal 
of work. The thought of having to run a new election is mind-numbing but I 
welcome it gladly because it is absolutely the right thing to do.

I recommend a one week nomination period, and a one week voting period. (The 
prior election was lengthened to two + two specifically to accommodate summer 
vacations).  I am at ONS-Europe this week and out the first week of October on 
family business. The earliest I can commit to kicking off the process (after 
revalidating qualified Active Community Members) would be Oct. 11th, putting 
the close of the election on Oct. 25.

Please let me know your thoughts.
Best Regards,
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>, 510.766.5945
San Francisco Bay Area, Pacific Time Zone




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3739): https://lists.onap.org/g/ONAP-TSC/message/3739
Mute This Topic: https://lists.onap.org/mt/26151620/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Srini]

Hi,

I would like to self-nominate for a seat on the  ONAP TSC.

I have been working on ONAP and related areas since September,2017 when I 
started my current role as ONAP chief architect in Intel.  I have been 
technically/strategically leading group of ONAP engineers within Intel to 
contribute to ONAP releases. Some of my contributions include architecture of

-Policy based HPA feature in OOF, Multi-Cloud & A

-Secret Management Service to secure the ONAP secrets such as passwords

-CA Private key security using PKCS11 with Hardware root of trust.

-Distributed KV Store for configuration.

-Kubernetes plugin to do LCM of containerized VNFs and orchestrate both 
VMs & containers.

-ISTIO based Service mesh technology for ONAP.

-Many edge automation activities : ONAP offload to regional 
controllers,  Secure connectivity via IPSEC between ONAP and Edge locations and 
Aggregation of node statistics to site granularity.

I have led many big technical projects in my career and had been working in 
NFV/SDN world for last 6 years. ONAP success is my major goal of my current 
role. With my experience in open source, networking , security, edge, micro 
services and service mesh technologies, I am confident that I will 
contribute/collaborate technically/strategically with rest of the community and 
be a constructive technical contributor/architect to the ONAP project.

Short Bio:
Srini Addepalli has over 22+ years of experience in networking and security. He 
has been in Intel for last 3 years working as Sr. Principal Engineer & Senior 
Architect.  In his current role, he technically leads the software engineering 
& architecture activities related to network orchestration and 
network/infrastructure security with specific focus on  ONAP, edge and 
Kubernetes.Previously he worked in many roles including CTO of a network 
security software company Intoto Inc (acquired by Freescale), Fellow & Chief 
architect at Freescale leading advanced technology group. In his previous jobs, 
he was instrumental in strategy & creation of UTM solutions, autonomous 
acceleration of L3, L4, IPsec, Openflow, & Cloud RAN functions, network 
security/packet-processing software solutions and infrastructure security 
solutions.

My Bitergia statistics are: 
https://onap.biterg.io/goto/89070a01240d07735ab8d8292a5ff29d

Thanks
Srini
(Srinivasa Addepalli)


From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Tuesday, July 17, 2018 5:03 PM
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: Anyone from the ONAP community with twenty (20) or 
more measurable contributions during the previous 12-month period, inclusive of 
code merged, code reviews performed, wiki page edits, or JIRA activities



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Membe

[onap-tsc] Golang based applications - Code coverage

[Srini]

Hi Amy,

As per discussions today in TSC about code coverage:

https://wiki.onap.org/display/DW/Code+Coverage+for+Secret+Management+Service

Above link has information about code coverage of SMS.
Also, it has information about code coverage for any golang based applications.

We will send C/C++ based code coverage tools we have used in my next email 
(once I collect all the information in a wiki page).

Thanks
Srini



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3505): https://lists.onap.org/g/ONAP-TSC/message/3505
Mute This Topic: https://lists.onap.org/mt/23824708/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Casablanca Architecture presentation question

[Srini]

Hi Chris,

+1 on John's comments.

Some additional comments/questions.

Up to Slide 5 to 8 are recommendations from ARC subcommittee.
Are all recommendations are committed in Casablanca by various projects?
If not, it is good to call the ones out that are not  committed in Casablanca.

Specifically interested in

- Whether GVNFM and Plugin S-VNFM would be supported in SO in 
Casablanca.

- Whether all relevant projects understand SOL004 CSAR in Casablanca.  
And if security of TOSCA CSAR intend to be supported in Casablanca.

Thanks
Srini

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
John Q
Sent: Thursday, July 19, 2018 6:26 AM
To: ONAP-TSC@lists.onap.org; christopher.don...@huawei.com
Subject: [onap-tsc] Casablanca Architecture presentation question


Hi Chris

Thanks for pulling this together.  Two quick observation/questions



 The work on the standards alignment could be clearer on where it is impacting 
on Casablanca. On Slide 8 it is easy to miss the targeted SOL003 VNFM plugin 
for SO.



I just have a quick question should the slide from 9 onwards reflect the 
proposed changes in Casablanca? If so the VNFM plug-in to SO could be better 
reflected in 10 and 11. I would suggest reflecting that the VNF LCM interface 
that SO consumes is SOL003 on slide 10 and 11.



Regards

 John



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3469): https://lists.onap.org/g/ONAP-TSC/message/3469
Mute This Topic: https://lists.onap.org/mt/23744385/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc][onap-discuss]Questions about Security Requirements for Casablanca: is CADI the only option to enable RBAC?

[Srini]

Hi Bin,

As Ramki mentioned in the wiki page, ISTIO CA and ISTIO RBAC may be good enough 
for Multi-Cloud.  But to be sure, it is good to know from Multi-Cloud team on 
what kind of APIs are present and what kind of restrictions the team thinks it 
should provide to various consumers of Multi-Cloud.   If the access rules are 
based on the URI & HTTP request header values, then ISTIO RBAC is good enough. 
But, if the access rules are based on HTTP body data, then you need to rethink 
about ISTIO RBAC or rethink about putting that data part of URI and HTTP 
request header.

Thanks
Srini




From: Yang, Bin mailto:bin.y...@windriver.com>>
Sent: Wednesday, June 27, 2018 5:57 AM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: [onap-tsc][onap-discuss]Questions about Security Requirements for 
Casablanca: is CADI the only option to enable RBAC?

Dear TSC and Security Subcommittee,

As part of S3P requirement, the CII Silver badge requires:
*Level 2: CII Silver badge, plus:
-All internal/external system communications shall be able to be 
encrypted.
-All internal/external service calls shall have common role-based 
access control and authorization with CADI

If I understand correctly, CADI is an SDK/framework from AAF. And integration 
with CADI needs AAF SDK which is only available with java binding, is that 
correct?

As you know some ONAP projects are python based and it is a great 
challenge/burden for us to develop a python based CADI SDK. So this could be a 
risk need TSC/Security subcommittee's attention, especially in case that TSC 
makes it a mandatory requirement for Casablanca.

On the other hand, I am wondering what is the real intention with this security 
requirement. If the role-based access control is the key pursuit, then we 
should explore other alternatives.
Before diving into the specific alternatives, I would like touch a little bit 
the different requirements between a "Role" for end-user and "Role" for 
internal service entities.

  *   A role for end-user could be dynamically maintained/assigned since the 
end-users are created/deleted/updated during run-time. In that case some UI is 
needed and I guess this is what AAF/CADI is doing, correct?
  *   A role for service-entity is another story. The role for a service-entity 
should be designed at day 0 and configured during deployment time. And should 
be kept intact during the life cycle of the whole system (ONAP in this case). 
Hence there is no need to create/update/delete the role for a service-entity.

If my understanding/assumption is correct, I believe those services which does 
not expose API/UI to end-users should control the access based on the "role for 
service-entity" because their API consumers are service-entities, not end-users.
e.g. MultiCloud services's consumers are SO/VFC/APPC/etc. No end-user should 
access the MulitCloud APIs directly. Hence the access control based on the 
"role for service-entity" should be enough and will be provisioned during 
deployment.
In this case ISTIO's RBAC could be an alternative, which fullfil the 
requirement of RBAC, while offering following beneficts:
   1, leverage the ongoing effort with regarding to ISTIO for 
service mesh.
   2, Reuse the same infrastructure to fulfill requirement w.r.t. 
"All internal/external system communications shall be able to be encrypted"
3, OOM/Kubernetes based/managed, easy to configure/maintain.
   4, Projects are not impacted at all, no code change, no API 
change, etc. No SDK development/integration needed.


This is my 2 cents.  Please let me know if I got anything wrong/incomplete.

Thanks.


Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3217): https://lists.onap.org/g/ONAP-TSC/message/3217
Mute This Topic: https://lists.onap.org/mt/22707999/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] ONAP TSC Composition - TSC Members, please provide your input

[Srini]

Hi,

I also had similar question for option 1:  Are the operator appointed TSC 
members are over and beyond base TSC size mentioned?

On TSC voting timeline: Can this be conducted in August time frame to give 
chance for current TSC members (who are on summer vacation) to contest?

Thanks
Srini


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Jason Hunt
Sent: Wednesday, June 20, 2018 5:11 PM
To: Phil Robb 
Cc: onap-tsc 
Subject: Re: [onap-tsc] ONAP TSC Composition - TSC Members, please provide your 
input

Thanks, Phil, for the writeup.  I think this addresses some of the concerns on 
our two previous proposals.

Just for clarity:

- Under option 1, in the 2018 exception, are any "appointments" in addition to 
the 17 base TSC member size?  If so, please clarify.

- Under option 2, is the second election done before or after the base TSC 
election?  Are those two at-large seats in addition to the 17 base seats?  Is 
there any difference in separate elections vs. just looking at the base 
election and taking the top 2 vote-getters that were excluded because of the 1 
per company cap?


Regards,
Jason Hunt
Distinguished Engineer, IBM

Phone: 314-749-7422
Email: djh...@us.ibm.com<mailto:djh...@us.ibm.com>
Twitter: @DJHunt




From:Phil Robb 
mailto:pr...@linuxfoundation.org>>
To:Jason Hunt mailto:djh...@us.ibm.com>>
Cc:onap-tsc mailto:onap-tsc@lists.onap.org>>
Date:06/20/2018 04:46 PM
Subject:Re: [onap-tsc] ONAP TSC Composition - TSC Members, please 
provide your input




Hello TSC Members:

We had a discussion on TSC Composition during the Casablanca Developer Forum on 
Tuesday.  During that discussion Stephen Terrill and Chris Donley elaborated on 
the proposal provided by Jason in this email thread.  During the discussion, 
this approach was received relatively well by those in the room.  I asked 
Stephen and Chris to write up the proposal so that we could add it to this 
thread.  The proposal follows:
=
Definitions:

Service Provider: AT, Bell, CMCC, China Telecom, Orange, Reliance Jio, Turk 
Telecom, Verizon, Vodafone

Active Contributor: Active contributors are determined based on contributions 
to Git, Gerrit, Jira, and Confluence Require 20 contributions in total over a 
12-month period, counting any of patches merged, reviews made, Wiki page edits, 
and JIRA activities:

Option 1:

  *   Base TSC Size: 17
  *   Base TSC selection is  performed through​ ​one big ranked vote conducted 
via CIVS
  *   ​Eligibility ​to apply/run​: Active contributors
  *   ​Eligibility​ to Vote: Active contributors
  *   Base Company Cap: 1 ​TSC Member ​per company

  *   The following is valid for the year of 2018
 *   If a service provider (defined above) ​does not have any staff member 
who is eligible to run for the​ election under the criteria above, that service 
provider may appoint a person to the TSC .
 *   If a service provider has one or more staff members that are eligible 
to run for the election, they are encouraged to do so.  If no eligible person 
wins a TSC spot in the election, then the company may appoint the highest 
relatively ranked staff member from the election to the TSC.
 *   If a service provider does have one or more staff members that are 
eligible to run but choose not to, then that service provider​ may not appoint 
a person to the TSC.

  *   If a TSC member is absent​ (​and does not ​provide a proxy) for 3 
consecutive meetings, that person is removed from the TSC.  The person may 
request to be reinstated by the TSC​.  In such an event the TSC may approve the 
reinstatement by a simple majority vote.​
 Option 2:

Option 1 with the following modifications
A separate election is proposed for 2 community at large members with the same 
criteria and process for the Base TSC election with the exception that this is 
not subject to the one person per company rule.

After the election, there is no difference between Base TSC or a member 
appointed by other means.
==

​Please provide your questions and/or feedback on this proposal.  We will 
discuss this at the TSC meeting tomorrow​.

Best regards,

Phil.


On Tue, Jun 19, 2018 at 11:01 AM, Phil Robb 
mailto:pr...@linuxfoundation.org>> wrote:
Hi Jason:

I think your proposal works fine as well.  I will caution the TSC that with a 
cap of one person per company, we will have a dynamic where qualified people 
from our participating organizations, both operators and vendors, will possibly 
choose not to run for the TSC because they don't want to compete for the one 
TSC slot with other, often higher ranking, coworker(s).  So for some 
organizations it will be a more meritocratic selection, and for other 
organizations it will be more like an appointment.

We are adding a session this afternoon to talk through the TSC composition, in 
part because there has not been ver