Re: [onap-tsc] [OOM] PTL election results

[Brian Freeman]

Congrats !

From: onap-rele...@lists.onap.org  On Behalf Of 
Sylvain Desbureaux via lists.onap.org
Sent: Tuesday, July 21, 2020 9:57 AM
To: onap-tsc@lists.onap.org
Cc: onap-rele...@lists.onap.org; Borislav Glozman 
; Mike Elliott ; 
Krzysztof Opasiak 
Subject: [Onap-release] [OOM] PTL election results

Dear TSC members,

All committers of OOM project have voted 
(https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_3584830cbf9b0f18).

I've been elected as PTL.

Thanks OOM committers for their confidence.

Best regards,
Sylvain Desbureaux

_



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 (#6831): https://lists.onap.org/g/onap-tsc/message/6831
Mute This Topic: https://lists.onap.org/mt/75703864/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] #aai Active and Available Inventory PTL Election Results

[Brian Freeman]

Thank you Jimmy for your leadership and for all the great support for 
integration.

Congratulations Bill !

Brian


From: onap-tsc@lists.onap.org  On Behalf Of PRESSLEY, 
VIVIAN A
Sent: Thursday, July 2, 2020 8:10 AM
To: FORSYTH, JAMES ; onap-tsc@lists.onap.org
Cc: EVANS, GLENN W ; REEHIL, WILLIAM E ; 
SAVOOR, RAJ ; REZVANI, MASOUD ; LU, DAVID H 
; LEFEVRE, CATHERINE 
Subject: Re: [onap-tsc] #aai Active and Available Inventory PTL Election Results

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Congratulations, Bill!  Looking forward to your tenure!

Thank you, Jimmy, for your excellent work as PTL and for successfully handing 
this over to Bill!

Viv

From: FORSYTH, JAMES mailto:jf2...@att.com>>
Sent: Thursday, July 2, 2020 7:40 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: EVANS, GLENN W mailto:ge2...@att.com>>; PRESSLEY, VIVIAN A 
mailto:vp1...@att.com>>; REEHIL, WILLIAM E 
mailto:wr1...@att.com>>; SAVOOR, RAJ 
mailto:rs1...@att.com>>
Subject: #aai Active and Available Inventory PTL Election Results

Dear ONAP TSC,

I have the pleasure of reporting that the AAI Committers have elected Bill 
Reehil to serve as PTL of the AAI project.

https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fb978eb928dcd561<https://urldefense.proofpoint.com/v2/url?u=https-3A__civs.cs.cornell.edu_cgi-2Dbin_results.pl-3Fid-3DE-5Ffb978eb928dcd561=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=EXOduYW4wlLoARLau7gfiyzGY4I_U0BER6KWi-FZ2KA=Qt0i96ldaQ2lll3ynnLmsVn344RnG__phwEMGga7FDU=>

I have updated the Voting Results 
History<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Voting-2BResults-2BHistory=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=EXOduYW4wlLoARLau7gfiyzGY4I_U0BER6KWi-FZ2KA=xHcMf_vEZG-8D4Leymg_-zboXk0njaWNj_M0zSjIB6M=>
 page, the Resources and 
Repositories<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=EXOduYW4wlLoARLau7gfiyzGY4I_U0BER6KWi-FZ2KA=wLxWlu44KskMEbwvAkgFWnoCT9EqkDZnvw14bMtirK0=>
 page, assigned the M1 tasks to Bill, and will send code reviews to update 
INFO.yaml files for the AAI repos.

Thank you for the opportunity to serve the project for 3 years as PTL – it has 
been a highlight of my career.

Jimmy Forsyth


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

View/Reply Online (#6658): https://lists.onap.org/g/onap-tsc/message/6658
Mute This Topic: https://lists.onap.org/mt/75256242/21656
Mute #aai: https://lists.onap.org/g/onap+onap-tsc/mutehashtag/aai
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] Lab closure clarification

[Brian Freeman]

Yipan,

Staring on Jan 6th seems like a very reasonable start date. We would plan for a 
week as you suggest just in case.
I assume all the data will be preserved (cinder volumes, vm’s and stacks etc) ?
Will we need to help gracefully shutdown things in advance ?

Probably need to have a planning session on anything we can do to help ensure 
success as tenants :)

David,

We need to make sure that M2/M3 is after Jan 14th . Right now per 
https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt I think its 
January 9th.

Brian




From: onap-tsc@lists.onap.org  On Behalf Of Yipan Deng
Sent: Friday, November 15, 2019 2:17 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Lab closure clarification

Hi David & TSC,

For Intel/Windriver Integration Lab located at Intel campus in Oregon, 
currently we are looking at moving the physical Lab starting from Jan. 6th, 
2020 for about a week (or shorter). During that period of time, there won’t be 
any remote access to the lab.

We tentatively shooting for this window considering the New Year holiday impact 
and believed this might create the least disruption to the ONAP community. 
Please feel free to let us know if you have different opinion and we are open 
for community feedbacks on lab move window.

Thanks,
Yipan
Intel ONAP/Akraino PM

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride
Sent: Friday, November 15, 2019 9:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Lab closure clarification

Who can provide detailed input about these events?

For both, we need to know:

  *   Start date
  *   Duration
  *   Degree of confidence in timing
  *   Scope of impact
David

On Thu, Nov 14, 2019 at 11:06 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Two different events but need to undertand the timing with the latest Frankfurt 
schedule to assess impact.

Brian


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
Paul
Sent: Thursday, November 14, 2019 2:02 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Lab closure clarification

From the minutes today Srini brought up the Intel lab closure in January.
Brian asked a schedule question resulting from the Windriver lab closure.

In this context, one in the same or 2 different events?

Thanks!
-kenny



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


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

View/Reply Online (#5650): https://lists.onap.org/g/onap-tsc/message/5650
Mute This Topic: https://lists.onap.org/mt/57995264/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] Integration PTL Election Results

[Brian Freeman]

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 (#5478): https://lists.onap.org/g/onap-tsc/message/5478
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]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] UPDATE 9/19 RE: Integration Blocking : Release Containers

[Brian Freeman]

Latest status is on the wiki ( 
https://wiki.onap.org/display/DW/1%3A+El+Alto+Release+Integration+Test+Blocking+Issues)


  1.  RC0 containers
 *   SDNC/APPC : Self Release pyenv bug from last week affected ccsdk jars 
which was not detected till SDNC containers built. Had to restart the 
CCSDK/SDNC CCSDK/APPC release process.

i. M4 containers work 
with work arounds but will have to repeat tests

   ii. ETA is Thursday or 
Friday depending on commit buddy status

 *   OOF:   SNIRO/Homing available. CMSO waiting for bug fixes on health 
check
 *   All other RC0 containers appear to be available but still checking on 
a few process issues with OOM merges when Job Deployer was offline
 *   High priority bugs and finalized pair wise testing (PORTAL) will 
likely require new containers but that is expected.



  1.  Release branches
 *   Some projects have not cut the elalto branch yet - need help from 
Jim/David to police this
 *   OOM elalto branch needs to be soon but understand the impact
  2.  Testing
 *   Pairwise testing is almost complete but integration is aware of the 
open items and proceeding in parallel where we can
 *   Testing starting on some areas but SDNC RC0 container will require 
retesting
 *   Overall onboarding for  less complex cases are working.  An issue with 
vCPE allotted resource. Additional packages need to be checked.

i. Upgrade to SSL for 
SDC seems to be working for distribution clients so far.

 *   InstantiatevFWCL works up to policy-name update in DCAE - could be 
environment issue
 *   Environment Issues: Windriver continues to be under duress.  DCAE 
installation required major re-tuning of helm charts for SB04 while 
integration-release-daily installed without intervention.

i. Using Orange and E// 
Labs to validate fresh install (and DCAE install PASSED)

 *   Some projects (Modeling, CLI) still need to complete their pair wise 
testing and that is the bulk of the planned El Alto testing for them
  1.  Summary
 *   As stated we are 1 week behind

i. RC0 final containers 
expected by Friday

   ii. Longevity testing 
needs 1 week after testing completes

  iii. With resources 
involved in ONS/ONAP F2F we will not be able to close on 9/30.




Brian Freeman
(on behalf of the Integration Team)

From: FREEMAN, BRIAN D
Sent: Monday, September 16, 2019 9:42 AM
To: 'onap-tsc@lists.onap.org' 
Cc: 'RICHOMME Morgan TGI/OLN' ; PLATANIA, MARCO 
; ROSE, DANIEL V ; 'Prudence Au' 

Subject: RE: UPDATE 9/13 RE: Integration Blocking : Release Containers

VID had a regression bug on RequestID generation that blocked instantiate. New 
container released (5.0.3)

BLOCKING: LF Tooling:  Pyenv based projects still failing in LF tool chain - 
IT-17582   (Policy, Log  , Testsuite , OOF, SDNC)

LF Tooling:  User authentication issues on wiki and gerrit (IT-17598) also 
gerrit rejecting patch sets due to jira failed validation step

Portal- (music resolved) - pairwise testing need to complete before releasing 
dockers - Wed latest
Policy Pyenv LF Tooling problem   (portal sdk jar released) - 2.6.0
VID - 2.5.0 portal sdk right now : 2.6.0 deferred to next release - Portal to 
confirm that it is okay should be backwards compatible

CLAMP - 4.1.2  expected 9/17 (tommorrow)
CCSDK/SDNC/APPC - blocked by verify jobs are failing (pyenv problem)
OOF release blocked by pyenv - blocked by Music insert problem  (By EOD 
Tuesday) - staging release available
AAF - pending some data changes from projects - 16 ?

>From an integraiton standpoint we did not recover any ground from last week.

I estimate we are 1 week behind in integraiton testing of the Release and it is 
unlikley we will be able to recover with the time remaining in El Alto.

Brian






From: FREEMAN, BRIAN D
Sent: Friday, September 13, 2019 10:12 AM
To: 'onap-tsc@lists.onap.org' 
mailto:onap-tsc@lists.onap.org>>
Cc: 'RICHOMME Morgan TGI/OLN' 
mailto:morgan.richo...@orange.com>>; PLATANIA, 
MARCO mailto:plata...@research.att.com>>; ROSE, 
DANIEL V mailto:dr6...@att.com>>; Prudence Au 
mailto:prudence...@amdocs.com>>
Subject: UPDATE 9/13 RE: Integration Blocking : Release Containers


CI JobDeployer is back online (Thanks Eric/Morgan et al @Orange)

SO released 1.5.2 of their docker containers last night and the process 
completed this morning.

Policy released images that were not dependent on the portal/music issue.

MUSIC jars were released with help from LF yesterday and parents are now moving 
forward with their updates/releases.

CCSDK/SDNC/APPC still working through the

Re: [onap-tsc] UPDATE 9/13 RE: Integration Blocking : Release Containers

[Brian Freeman]

VID had a regression bug on RequestID generation that blocked instantiate. New 
container released (5.0.3)

BLOCKING: LF Tooling:  Pyenv based projects still failing in LF tool chain - 
IT-17582   (Policy, Log  , Testsuite , OOF, SDNC)

LF Tooling:  User authentication issues on wiki and gerrit (IT-17598) also 
gerrit rejecting patch sets due to jira failed validation step

Portal- (music resolved) - pairwise testing need to complete before releasing 
dockers - Wed latest
Policy Pyenv LF Tooling problem   (portal sdk jar released) - 2.6.0
VID - 2.5.0 portal sdk right now : 2.6.0 deferred to next release - Portal to 
confirm that it is okay should be backwards compatible

CLAMP - 4.1.2  expected 9/17 (tommorrow)
CCSDK/SDNC/APPC - blocked by verify jobs are failing (pyenv problem)
OOF release blocked by pyenv - blocked by Music insert problem  (By EOD 
Tuesday) - staging release available
AAF - pending some data changes from projects - 16 ?

>From an integraiton standpoint we did not recover any ground from last week.

I estimate we are 1 week behind in integraiton testing of the Release and it is 
unlikley we will be able to recover with the time remaining in El Alto.

Brian






From: FREEMAN, BRIAN D
Sent: Friday, September 13, 2019 10:12 AM
To: 'onap-tsc@lists.onap.org' 
Cc: 'RICHOMME Morgan TGI/OLN' ; PLATANIA, MARCO 
; ROSE, DANIEL V ; Prudence Au 

Subject: UPDATE 9/13 RE: Integration Blocking : Release Containers


CI JobDeployer is back online (Thanks Eric/Morgan et al @Orange)

SO released 1.5.2 of their docker containers last night and the process 
completed this morning.

Policy released images that were not dependent on the portal/music issue.

MUSIC jars were released with help from LF yesterday and parents are now moving 
forward with their updates/releases.

CCSDK/SDNC/APPC still working through the multi-step release process.  Had to 
restart the process due to an issue with the release process.

New item on python 2.7 support removal in LF tool chain being worked. Teams 
think they have a path to a solution (Morgan) but several python projects are 
affected (testsuite, log at least).

Brian


From: FREEMAN, BRIAN D
Sent: Thursday, September 12, 2019 9:43 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: RICHOMME Morgan TGI/OLN 
mailto:morgan.richo...@orange.com>>; PLATANIA, 
MARCO mailto:plata...@research.att.com>>
Subject: Integration Blocking : Release Containers

Jim,

The following El Alto Release Containers are still pending


  1.  SO
 *   1.5.1 is in nexus3 from August.
 *   1.5.2 Expected but there is no 1.5.2-SNAPSHOT-latest
  2.  OOF
 *   2 of 3 pods failing health check
 *   Onboard and Instantiate is not blocked
  3.  MUSIC/PORTAL and MUSIC/Policy
 *   Needs to release artifacts so parent projects can release containers
 *   Policy
 *   Portal
 *   Onboard and instantiate is not blocked
 *   Portal healtcheck failure being worked (false negative)
  4.  CCSDK/SDNC/APPC
 *   Update for resolution of mariadb jdbc client karaf issues.
 *   APPC parent project
 *   SDNC parent project


Brian


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

View/Reply Online (#5425): https://lists.onap.org/g/onap-tsc/message/5425
Mute This Topic: https://lists.onap.org/mt/34127664/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] UPDATE 9/13 RE: Integration Blocking : Release Containers

[Brian Freeman]

CI JobDeployer is back online (Thanks Eric/Morgan et al @Orange)

SO released 1.5.2 of their docker containers last night and the process 
completed this morning.

Policy released images that were not dependent on the portal/music issue.

MUSIC jars were released with help from LF yesterday and parents are now moving 
forward with their updates/releases.

CCSDK/SDNC/APPC still working through the multi-step release process.  Had to 
restart the process due to an issue with the release process.

New item on python 2.7 support removal in LF tool chain being worked. Teams 
think they have a path to a solution (Morgan) but several python projects are 
affected (testsuite, log at least).

Brian


From: FREEMAN, BRIAN D
Sent: Thursday, September 12, 2019 9:43 AM
To: onap-tsc@lists.onap.org
Cc: RICHOMME Morgan TGI/OLN ; PLATANIA, MARCO 

Subject: Integration Blocking : Release Containers

Jim,

The following El Alto Release Containers are still pending


  1.  SO
 *   1.5.1 is in nexus3 from August.
 *   1.5.2 Expected but there is no 1.5.2-SNAPSHOT-latest
  2.  OOF
 *   2 of 3 pods failing health check
 *   Onboard and Instantiate is not blocked
  3.  MUSIC/PORTAL and MUSIC/Policy
 *   Needs to release artifacts so parent projects can release containers
 *   Policy
 *   Portal
 *   Onboard and instantiate is not blocked
 *   Portal healtcheck failure being worked (false negative)
  4.  CCSDK/SDNC/APPC
 *   Update for resolution of mariadb jdbc client karaf issues.
 *   APPC parent project
 *   SDNC parent project


Brian


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

View/Reply Online (#5416): https://lists.onap.org/g/onap-tsc/message/5416
Mute This Topic: https://lists.onap.org/mt/34127664/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] Integration Blocking : Release Containers

[Brian Freeman]

Jim,

The following El Alto Release Containers are still pending


  1.  SO
 *   1.5.1 is in nexus3 from August.
 *   1.5.2 Expected but there is no 1.5.2-SNAPSHOT-latest
  2.  OOF
 *   2 of 3 pods failing health check
 *   Onboard and Instantiate is not blocked
  3.  MUSIC/PORTAL and MUSIC/Policy
 *   Needs to release artifacts so parent projects can release containers
 *   Policy
 *   Portal
 *   Onboard and instantiate is not blocked
 *   Portal healtcheck failure being worked (false negative)
  4.  CCSDK/SDNC/APPC
 *   Update for resolution of mariadb jdbc client karaf issues.
 *   APPC parent project
 *   SDNC parent project


Brian


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

View/Reply Online (#5413): https://lists.onap.org/g/onap-tsc/message/5413
Mute This Topic: https://lists.onap.org/mt/34115266/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] image_compare.20190909.R1.xlsx

[Brian Freeman]

Seshu,

For SO , I dont see a snapshot for 1.5.2. When are you planning to release ?

Brain


From: onap-tsc@lists.onap.org  On Behalf Of Jim Baker
Sent: Monday, September 09, 2019 7:02 PM
To: onap-tsc 
Subject: [onap-tsc] image_compare.20190909.R1.xlsx

Attention PTLs:
Please review the attached spreadsheet for your El Alto deliveries. If you have 
any updates, please let me know.
Jim

-- Forwarded message -
From: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Date: Mon, Sep 9, 2019 at 10:15 AM
Subject: image_compare.20190909.R1.xlsx
To: Jim Baker mailto:jba...@linuxfoundation.org>>, 
morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> 
mailto:morgan.richo...@orange.com>>
Cc: LEFEVRE, CATHERINE 
mailto:catherine.lefe...@intl.att.com>>

Use the Script tab.

This data is from oom:master on 9.9.2019 and nexus3 query to the release 
repository to check for Last-Modified date (which should be the same as Release 
date)

If there is a blank it means the nexus3 query failed – likely due to it not 
being resident on nexus3.

Its a new script so there may be missing images but I think it is generally 
accurate.

Could we send to ptl’s for update that were not provided on the call.

I will re-run this for next weeks PTL call..

Brian



--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


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

View/Reply Online (#5411): https://lists.onap.org/g/onap-tsc/message/5411
Mute This Topic: https://lists.onap.org/mt/34086265/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] Updated Event: Dublin Defect Scrub - end of week #cal-invite

[Brian]

Jim,

We can cancel these.

Brian


From: onap-tsc@lists.onap.org 
Sent: Friday, June 21, 2019 9:21 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Updated Event: Dublin Defect Scrub - end of week #cal-invite


Dublin Defect Scrub - end of week

When:
Friday, 7 June 2019
7:00am to 7:30am
(GMT-06:00) America/Denver
Repeats: Weekly on Friday, through Thursday, 20 June 2019

Where:
https://zoom.us/j/102357978<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_102357978=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=FHQxBe_e3WUmH3XL-KtseOse8R_xf6S6w0hG5no_Pjs=M5CHMaZ-FFDBGoDfv3FmXgtT2NaKNtbtvnRFs9gXRvk=>

Organizer:
jba...@linuxfoundation.org<mailto:jba...@linuxfoundation.org?subject=Re:%20Event:%20Dublin%20Defect%20Scrub%20-%20end%20of%20week>
 9702276007

Description:
Jim Baker (LFN) is inviting you to a scheduled Zoom meeting.

Topic: Dublin Defect Scrub - end of week
Time: Jun 7, 2019 6:00 AM Mountain Time (US and Canada)
Every week on Fri, until Jun 28, 2019, 4 occurrence(s)
Jun 7, 2019 6:00 AM
Jun 14, 2019 6:00 AM
Jun 21, 2019 6:00 AM
Jun 28, 2019 6:00 AM
Please download and import the following iCalendar (.ics) files to your 
calendar system.
Weekly: 
https://zoom.us/meeting/102357978/ics?icsToken=972c1c2065a517da5d04be58b5956486d9f2425296dae63ec6732ee6c2ec106a<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_meeting_102357978_ics-3FicsToken-3D972c1c2065a517da5d04be58b5956486d9f2425296dae63ec6732ee6c2ec106a=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=FHQxBe_e3WUmH3XL-KtseOse8R_xf6S6w0hG5no_Pjs=ELDWc7pTnrhCs3L9pkZpVZMLCNKs33alaEBViraNXiA=>

Join Zoom Meeting
https://zoom.us/j/102357978<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_102357978=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=FHQxBe_e3WUmH3XL-KtseOse8R_xf6S6w0hG5no_Pjs=M5CHMaZ-FFDBGoDfv3FmXgtT2NaKNtbtvnRFs9gXRvk=>

One tap mobile
+16699006833,,102357978# US (San Jose)
+16465588656,,102357978# US (New York)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
855 880 1246 US Toll-free
877 369 0926 US Toll-free
Meeting ID: 102 357 978
Find your local number: 
https://zoom.us/u/adoCBQyqvE<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_u_adoCBQyqvE=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=FHQxBe_e3WUmH3XL-KtseOse8R_xf6S6w0hG5no_Pjs=_yEjWqH739BX7oVVeDHPDqQS8Nl1b73nGnowzZhzFJ0=>



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

View/Reply Online (#5132): https://lists.onap.org/g/onap-tsc/message/5132
Mute This Topic: https://lists.onap.org/mt/32158327/21656
Mute #cal-invite: https://lists.onap.org/mk?hashtag=cal-invite=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] Slack?

[Brian]

Probably worth re-doing the survey since we have been using rocket-chat for 
some time and there may be feedback on how its working/not working for folks.

We need to move the rocket-chat we have to a better supported environment. 
Moving it to https://onap-integration.onap.org:443 in LF with SSL would be 
perhaps the next step.  We could do the setup/domain change with the current 
server and if that works migrate the server to LF or simply bring up a new 
instance in LF and let folks re-register on the new site.

We can not use the hosted version since its important that it be off onap.org 
for the corporate firewalls.  A non-descript hostname helps as well.

We did test ssl from APAC back in mid 2018 and it did work at that time.

Brian


From: onap-tsc@lists.onap.org  On Behalf Of LEFEVRE, 
CATHERINE
Sent: Friday, June 21, 2019 5:27 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Slack?

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Good morning Kenny,

Yes Slack is still in the 2019 Apps list blocked in China.
https://startuplivingchina.com/list-websites-apps-blocked-china/<https://urldefense.proofpoint.com/v2/url?u=https-3A__startuplivingchina.com_list-2Dwebsites-2Dapps-2Dblocked-2Dchina_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=yJt10uLxgNc9fcMprin8NcfOQdlj4VN4f2Ot4UzcjNc=NE8dQOmJ9H8XESieiy0enI32EqR4MZCrDMRzcZaJ6R4=>

I remember that you created a wiki page to collect feedback.
https://wiki.onap.org/display/DW/Permitted+External+Instant+Messaging+Platforms<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Permitted-2BExternal-2BInstant-2BMessaging-2BPlatforms=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=yJt10uLxgNc9fcMprin8NcfOQdlj4VN4f2Ot4UzcjNc=5n4Xzw1LmX2BJ0S9SjqOM7Ap90ylb9v-uqAqyHc1RDs=>

There was also a Survey performed last year about IM Tools – Another choice was 
HipChat (Atlassian IM).
Nevertheless HipChat moved to Slack.
https://www.atlassian.com/blog/announcements/new-atlassian-slack-partnership<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.atlassian.com_blog_announcements_new-2Datlassian-2Dslack-2Dpartnership=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=yJt10uLxgNc9fcMprin8NcfOQdlj4VN4f2Ot4UzcjNc=wiGZHr2l2HA6zRX9AxBdw8dGSmLCEjgxiBzPnEBAPDw=>

Survey: 
https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2018?preview=%2F25429038%2F25432122%2FONAP-IRC-Survey.pdf<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_VF2F-2BFeb.-2B5-2D8-252C-2B2018-3Fpreview-3D-252F25429038-252F25432122-252FONAP-2DIRC-2DSurvey.pdf=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=yJt10uLxgNc9fcMprin8NcfOQdlj4VN4f2Ot4UzcjNc=_5y-UYcNQtvJkCC6qsmADU_t7gvc6j0i70nBv2XADEE=>

[cid:image002.jpg@01D527F7.580ADD10]

Best 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: Wednesday, June 19, 2019 10:41 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Slack?

IIRC, it doesn’t work well in China: 
https://twitter.com/slackhq/status/968526959213936640<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_slackhq_status_968526959213936640=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=KPX7aWUQ-iDK-r4OvAISNzTIk58uI5Knk_9imMooK9w=hOBJn1AO1uPx6sYN4FXzhG0tFuNbT2yww5VvnADm_T0=>


On Jun 19, 2019, at 4:37 PM, Kenny Paul 
mailto:kp...@linuxfoundation.org>> wrote:

Can anyone please remind me again why Slack was deemed an undesirable IM 
solution for ONAP?

Thanks!
-kenny




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

View/Reply Online (#5129): https://lists.onap.org/g/onap-tsc/message/5129
Mute This Topic: https://lists.onap.org/mt/32131148/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-usecasesub] [Onap-release] ReadTheDoc is now repaired !

[Brian]

Integration will be cutting dublin branch after the 72 hour testing reports are 
completed (today :) )

Brian


From: onap-usecase...@lists.onap.org  On Behalf 
Of David Perez Caparros
Sent: Friday, June 21, 2019 3:56 AM
To: LEFEVRE, CATHERINE 
Cc: onap-tsc@lists.onap.org; onap-rele...@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: Re: [Onap-usecasesub] [Onap-release] ReadTheDoc is now repaired !

Hi Catherine,

regarding BBS, the doc was added to master branch, as there is no dublin branch 
yet in the integration project (as far as I know).

https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_usecases.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__onap.readthedocs.io_en_latest_submodules_integration.git_docs_docs-5Fusecases.html=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=8Q9eoltuRf1fBTvM1gfnM7ksPAVMl8TTe_IwB3ZK2Ds=pEN_2tPnvZCVxO9ZxuVwrf-WsLa61N7qVAmmgAP0-54=>

David


On 21 Jun 2019, at 09:44, Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>> wrote:

Dear ONAP Community,

Please check if your latest changes are now visible in the ReadTheDoc –version: 
Dublin.
https://onap.readthedocs.io/en/dublin/<https://urldefense.proofpoint.com/v2/url?u=https-3A__onap.readthedocs.io_en_dublin_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=8Q9eoltuRf1fBTvM1gfnM7ksPAVMl8TTe_IwB3ZK2Ds=gbxVHXqdjZshngrxaAsPSIgZx6ei0F8ZKM05juFk8vU=>

I also want to ask the Dublin “Owners” and PTLs to review carefully and to 
update the Dublin release note in alignment with the Dublin Release Integration 
Testing Status - 
https://onap.readthedocs.io/en/dublin/submodules/integration.git/docs/docs_usecases.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__onap.readthedocs.io_en_dublin_submodules_integration.git_docs_docs-5Fusecases.html=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=8Q9eoltuRf1fBTvM1gfnM7ksPAVMl8TTe_IwB3ZK2Ds=-6xYzrRoSVWr-qqSW0P80WUsUm9-ukLowpI05FNWGFU=>
We are missing new Dublin use case i.e. BBS;
Functional requirements and non-functional requirements - We need to remove 
vCPE with TOSCA since it has been descoped from Dublin, etc.
Casablanca Release Integration Testing Status Summary to be replaced by Dublin 
Release Integration Testing Status Summary

It is extremely important that the information in the ReadTheDoc is accurate to 
prevent misunderstanding

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 (#5128): https://lists.onap.org/g/onap-tsc/message/5128
Mute This Topic: https://lists.onap.org/mt/32156776/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] APPC reaches 80% line coverage 2/22/2019

[Brian]

Awesome !

From: CHO, TAKAMUNE
Sent: Friday, February 22, 2019 9:28 AM
To: Joss Armstrong ; Lathishbabu Ganesan 
; KUMAR, SUDARSHAN ; 
BABU, JEGADEESH ; driptaroop@in.ibm.com; Rajewski 
Łukasz - Korpo ; Osiński Tomasz 2 - Korpo 
; BRADY, PATRICK D ; ZINNIKAS, 
MICHAEL J ; JOG, VIDYA E ; HAHN III, JIM 

Cc: onap-tsc ; FREEMAN, BRIAN D ; 
LEFEVRE, CATHERINE ; Jim Baker 

Subject: APPC reaches 80% line coverage 2/22/2019

Dear APPC contributors,
CC: TSC members, Jim Baker

Today, APPC reaches 80% milestone line coverage. 
https://sonar.onap.org/component_measures?id=org.onap.appc%3Aappc

I would like to thanks for your tremendous effort to make this happened. 
Especially, Joss and Lathish from Ericsson. And Jim Hahn’s code review  APPC 
pumped up more than 20% code coverage from Nov 2018!! Without this effort, APPC 
can not have a better quality code. I will continue trying my best to work with 
you.

Thanks again!!

Taka Cho, APPC PTL


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

View/Reply Online (#4662): https://lists.onap.org/g/onap-tsc/message/4662
Mute This Topic: https://lists.onap.org/mt/29998500/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] [E] Re: [onap-discuss] [Onap-usecasesub] ONAP Casablanca Maintenance - The Release Note is now available !

[Brian]

Did you check docker-manifest.csv under integration ?

Brian


Sent via the Samsung Galaxy S8, an AT 5G Evolution smartphone


 Original message 
From: "Bharath Thiruveedula via Lists.Onap.Org" 

Date: 2/19/19 7:51 AM (GMT-05:00)
To: onap-discuss , david.perezcapar...@swisscom.com
Cc: "LEFEVRE, CATHERINE" , 
onap-rele...@lists.onap.org, onap-tsc@lists.onap.org, 
onap-sec...@lists.onap.org, onap-usecase...@lists.onap.org, 
onap-...@lists.onap.org, onap-modeling...@lists.onap.org
Subject: Re: [E] Re: [onap-discuss] [Onap-usecasesub] ONAP Casablanca 
Maintenance - The Release Note is now available !

Hi  Catherine/ David,

I have the same question. I can't see any new branch/tag created in OOM. I 
checked some of the docker tags in OOM Casablanca, it still points to docker 
image tag which is of Casablanca not of maintenance release.

Best Regards
Bharath T



On Tue, Feb 19, 2019 at 4:21 PM David Perez Caparros 
mailto:david.perezcapar...@swisscom.com>> 
wrote:
Hi Catherine,

can you please provide a pointer to the documentation on how to install that 
specific release?
e.g. should we just pull casablanca branch or the 3.0.1-ONAP tag? any specific 
version for demo artifacts (> 1.3.0)?

Thanks,
David

--
David Pérez Caparrós
Senior Innovation Engineer
Swisscom (Switzerland)
david.perezcapar...@swisscom.com<mailto:david.perezcapar...@swisscom.com>

On 18 Feb 2019, at 22:06, Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>> wrote:

Dear ONAP Community,

As you know, the ONAP Casablanca Maintenance Release was signed-off on January 
31st, 2019.

The focus of this maintenance release was to mainly address
•Documentation Improvement
•Security/Vulnerability issues
•Application Improvement
•Bug Fixes

The release note is now available on readthedocs: 
https://docs.onap.org/en/casablanca/release/#casablanca-maintenance-release-3-0-1<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.onap.org_en_casablanca_release_-23casablanca-2Dmaintenance-2Drelease-2D3-2D0-2D1=DwMGaQ=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw=eI3dU-c9NUE7R3eVJCrhPt08-PqYIDeshq9hmj1IXDE=_3LOinPcdUTnH79Bzq3II2D_eQfWV5sV8zaqUNUBRyY=>.

Feel free to give us any feedback on this maintenance release that you think 
would be relevant.

Thank you to all the teams that were part of the maintenance release.

Best 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 (#4641): https://lists.onap.org/g/onap-tsc/message/4641
Mute This Topic: https://lists.onap.org/mt/29917301/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

[Brian]

I dont think Disk space is really the main issue – its size of the image to 
download and boot and the memory consumption in the running image.

We arent running into issues with disk space in our environment but rather in 
memory consumption and to some extent the container init delays.

Brian




From: onap-tsc@lists.onap.org  On Behalf Of Tal Liron
Sent: Monday, February 11, 2019 11:56 AM
To: onap-discuss ; DESBUREAUX Sylvain TGI/OLN 

Cc: Chaker Al Hakim ; 
srinivasa.r.addepa...@intel.com; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Ubuntu and Alpine discussion

This conversation has gotten a little bit confusing. Let me try to organize and 
separate the core issues:

  1.  Disk space. If we want to reduce the ridiculous storage requirements for 
ONAP's container images, the solution is not to choose a tiny Linux 
distribution. Rather, the solution is to choose a single (or small set of) base 
image(s) for all ONAP container images. Because images are stored as deltas 
from the derived base image, then the size of that base image is quite 
negligible.
  2.  Choice of base distribution. ONAP provides reference images, but in the 
end production operations will very likely build their own after auditing 
selections of packages and even the source code. The ONAP project can make a 
best effort to pre-audit the selection, but in the end cannot provide neither a 
guarantee nor a warranty. That comes from the operating system vendor and other 
software vendors of packages like MariaDB, MongoDB, JDK, etc. The ONAP project 
should make it possible (and better yet: easy) for users to make that choice. I 
understand this as one of the goals of our CIA project. I think there's also 
some misunderstanding of the supportability of packages within the containers. 
Here's an example: if your host operating system is RHEL, but your container 
image is based on Alpine, then Red Hat cannot support any security 
vulnerabilities in those Alpine libraries. This includes OpenSSL as well as 
glib, systemd, etc. In the end, whatever ONAP chooses as base image is 
arbitrary as long as we allow users to make their own choice.
  3.  Technical dependencies on specific distributions. Does a certain ONAP 
image build against a specific version of a library included in a specific 
version of a specific distribution? This should be considered a bug, because it 
exactly disallows the freedom of users to choose a base distribution. Not only 
that, but it's a guarantee for maintenance nightmares in the future. What 
happens if the next version of that specific distribution changes the library? 
Who will make sure to refactor and allow for an upgrade of the base? And if you 
can't upgrade the base, the image will be stuck with an older and possibly 
broken/insecure library. There are many open source project plagued with this 
problem, e.g. stuck on Ubuntu 14.04. We need to make sure that we minimize 
these dependencies. There's also the option of building that specific 
dependency library from source for that ONAP image, but again we limit the 
ability for users to get support from a vendor.
There are some complications regarding point #3 that should be discussed. For 
example, many Linux distributions have switched to systemd in recent years, and 
that causes a major change in how they run (e.g. that's one main reason 
projects stuck on Ubuntu 14.04 have difficulty moving forward). If systemd is 
considered a standard for ONAP, then that limits the number of possible choices 
for base image. Likewise SELinux. We need to examine ONAP as a whole and make a 
list of these basic technical requirements from a base distribution.

On Mon, Feb 11, 2019 at 10:08 AM Sylvain Desbureaux 
mailto:sylvain.desbure...@orange.com>> wrote:
Hello Chaker,

Today,
The docker building image process of ONAP is at the very least messy (Morgan 
did a presentation at TSC meeting last Thursday on this point 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670=/6593670/54722733/onap_tests.pdf<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D6593670-26preview-3D_6593670_54722733_onap-5Ftests.pdf=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=gZSWqClUIfrznacZC3v84m2JsV0c31x8dhlCzfK61vw=ya2lBU-bwwCbzGp-Yy9O1RhXAff5CUPVUr8CLD51vt8=>)
 as we do not know what we test and even if it’s tested.

So the base image of an ONAP component doesn’t seems to be the most critical 
part on improving ONAP.
I would prefer to :

  *   Make reliable, consistent tests on any review that come
  *   Know what is tested
  *   Strengthen security by moving from root to another user in the docker 
images
  *   Slimify ONAP so the tests are faster

When we’ll arrive at that, I’ll be happy to see if we can make a consensus on 
base image.

Today, all I want to do is make small images per components. If a component is 
small on ubuntu/centOs/Debian/openSUSE, fine I won’t touch it.
If it’s not, I’ll m

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

[Brian]

Daniell,

One item I meant to reply to before.
Since ONAP is Apache 2.0 and ODL is EPL we dont think we can build a 
distribution on the ONAP side that removes “ODL projects like TSDR, SXP
and similar”.   It would be awesome if ONAP could build its own distro but I 
dont think we know how to do that without tainting.

We dont use those other projects but they are in the distro. It would be useful 
to have some mechanism to do a CII Badging friendly distribution or something.

Brian


From: Alexis de Talhouët 
Sent: Tuesday, January 22, 2019 4:29 PM
To: onap-tsc@lists.onap.org
Cc: TIMONEY, DAN ; Robert Varga ; FREEMAN, BRIAN D 

Subject: Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities




On Jan 22, 2019, at 3:48 PM, Daniel Farrell 
mailto:dfarr...@redhat.com>> wrote:


I have finally found the report and it's quite a few issues, so it's
hard to break them down.

First of all, I don't believe the list of issues flagged as coming from
OpenDaylight is accurate, as I compared the artifacts we are shipped in
karaf-0.8.3.

We also did not ship netty-4.0.30, we shipped 4.1.22.

We did not ship the following artifacts at all:
commons-fileupload
artemis-commons
faces-impl
sendgrid-java
netty-4.0.30 -- we are shipped 4.1.22.Final

I could not find a public repository for the SONATYPE advisories -- does
anyone have a pointer? Without that I cannot evaluate them...

We have upgraded org.bouncycastle in Oxygen SR4, so at least those two
CVEs have been fixed.

Finally, it seems that quite a few issues are affecting
ccsdk/distribution, which are coming from ODL projects like TSDR, SXP
and similar. I am not sure whether ONAP really uses them, so it may be
worthwhile to take a look at how the distribution is assembled.


Thanks Daniel for copying. Thanks Robert for the answer.

Brian, yes, Robert did reply with some preliminary answers. We should ingest 
them
and start triaging our list.
Also, we should look into how we could build a custom distro out of ODL 
released artifacts
specific for ONAP, as as pointed by Robert, we might not need everything. I 
actually think
we mostly need NETCONF, that I’m aware of.

I’ll follow-up w/ Dan Timoney and that.

Regards,
Alexis

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

View/Reply Online (#4590): https://lists.onap.org/g/onap-tsc/message/4590
Mute This Topic: https://lists.onap.org/mt/28708638/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: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

[Brian]

Alexis,

Did you get a reply ?

Brian


From: onap-tsc@lists.onap.org  On Behalf Of Alexis de 
Talhouet
Sent: Thursday, January 10, 2019 1:34 PM
To: Luke Hinds 
Cc: Michael Vorburger ; Stephen Kitt ; 
 ; Stephen Terrill 
; onap-tsc@lists.onap.org
Subject: Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

Luke, all

Following up on this. What is the current status?

Regards,
Alexis


On Dec 10, 2018, at 8:13 AM, Luke Hinds 
mailto:lhi...@redhat.com>> wrote:

Hi Alexis,

We can see your email and you will see replies as your email will be in the 
reply all list , a reply is till pending, but its on our desk so to speak.

I discussed this with Stephen this morning and a reply will follow. initial 
analysis shows that a good number of false positives are reported.

Regards,

Luke
On Mon, Dec 10, 2018 at 1:10 PM Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:
Everyone, Daniel,

So I did send the mail to ODL security list, but message is getting held 
waiting for “moderator approval”

Your mail to 'security' with the subject

   CII Badging - Vulnerabilities

Is being held until the list moderator can review it for approval.

The reason it is being held:

   Post by non-member to a members-only list

I don’t know if this is intended or not, but as there is no way to register to 
such list I’m wondering if I missed something..

Stephen T, in this case, I’m following ODL process are I’m reporting 
vulnerabilities to their project; vulnerabilities we have identified within 
ONAP as part of the CII Badging requirement.

Regards,
Alexis



On Dec 10, 2018, at 6:44 AM, Michael Vorburger 
mailto:vorbur...@redhat.com>> wrote:

Hello everyone,

It's great to see that we do have a working formal security vulnerability 
disclosure process in place in ODL.

I'll therefore let the members of that strucuture deal with this. If I can be 
of any help for anything specific, please reach out to me.

Tx,
M.
--
Michael Vorburger, Red Hat
vorbur...@redhat.com<mailto:vorbur...@redhat.com> | IRC: vorburger @freenode | 
~ = 
http://vorburger.ch<https://urldefense.proofpoint.com/v2/url?u=http-3A__vorburger.ch_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=lkut2Gd7rNtrI1s8KchApvgGCeHZMGyF5QMYF82Fyr0=_dHRF9scL5BKLaaXhGO0vos-bteexfJ9jJYjE8UbBj4=>


On Sun, Dec 9, 2018 at 2:52 AM Stephen Terrill 
mailto:stephen.terr...@ericsson.com>> wrote:
Hi,

Thanks. This maybe a good opportunity to point to this wiki for this process.  
https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BVulnerability-2BManagement=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=lkut2Gd7rNtrI1s8KchApvgGCeHZMGyF5QMYF82Fyr0=yLStnDSucQbFn9Nha7nLUfIEthbxB1QzhuZGTt1vwHU=>

This will be a good opportunity to test it out.

BR,

Steve

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
Paul
Sent: Friday 7 December 2018 22:15
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Daniel Farrell 
mailto:dfarr...@redhat.com>>
Cc: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>; 
mailto:t...@lists.opendaylight.org>> 
mailto:t...@lists.opendaylight.org>>
Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities

Perfect! Thanks Daniel!

Thanks!
-kenny


From: mailto:onap-tsc@lists.onap.org>> on behalf of 
Alexis de Talhouet mailto:adetalhoue...@gmail.com>>
Reply-To: mailto:onap-tsc@lists.onap.org>>
Date: Friday, December 7, 2018 at 12:58 PM
To: Daniel Farrell mailto:dfarr...@redhat.com>>
Cc: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>, 
"mailto:t...@lists.opendaylight.org>>" 
mailto:t...@lists.opendaylight.org>>, 
mailto:ONAP-TSC@lists.onap.org>>
Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities

Awesome. Thank you for the reminder Daniel. I’ll loop in that list.

Regards,
Alexis

On Dec 7, 2018, at 3:56 PM, Daniel Farrell 
mailto:dfarr...@redhat.com>> wrote:

No, this list is exactly meant for this type of secret information. It's the 
group of people the TSC has appointed as trusted to handle security issues. 
They will follow all the normal security embargo best practices.

Thanks,
Daniel
On Fri, Dec 7, 2018 at 9:52 PM Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:
Daniel,

Is the content of information provided through that mailing list publicly 
available? If yes, then I can’t provide the information to that list, as we 
don’t want to share publicly the vulnerabilities.

Alexis


On Dec 7, 2018, at 3:50 PM, Daniel Farrell 
mailto:dfarr...@redhat.com>> wrote:

Hey Alexis,

Reminder that we have a security response team that's meant to handle these 
types of things. Stephen is on the security response team, but you might still 
be better off sharing with that group 

Re: [onap-tsc] SDC Update

[Brian]

Michael,

I would like to take the opportunity to thank you for all your support and 
guidance as SDC PTL. It has truly been a pleasure to work with you and I wish 
you the best of luck on your future endeavors.

Brian


From: onap-disc...@lists.onap.org  On Behalf Of 
LANDO, MICHAEL
Sent: Thursday, November 29, 2018 6:53 PM
To: ONAP-TSC@lists.onap.org
Cc: 'onap-...@lists.onap.org' ; 
onap-disc...@lists.onap.org; MERKADO, TOMER ; 
NACHMIAS, LIOR ; 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: [onap-discuss] SDC Update

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
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 (#4244): https://lists.onap.org/g/onap-tsc/message/4244
Mute This Topic: https://lists.onap.org/mt/28504717/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 SDC PTL Election results

[Brian]

Congratulations Ofir !

Brian


From: onap-tsc@lists.onap.org  On Behalf Of Helen Chen
Sent: Tuesday, December 04, 2018 9:38 AM
To: SONSINO, OFIR ; NACHMIAS, LIOR 
; GITELMAN, TAL ; 
SHLOSBERG, YULI ; AMIT, IDAN 
; EMPOROPULO, VITALIY ; 
avraham.ga...@amdocs.com; oren...@amdocs.com; WEISS KEIDAR, EINAV 
; LEVI, ELI 
Cc: LEFEVRE, CATHERINE ; MERKADO, TOMER 
; onap-tsc ; onap-discuss 
; KAPELUTO, ZAHI 
Subject: Re: [onap-tsc] ONAP SDC PTL Election results

Congratulations Ofir !
Thank you Michael for your leadership and hardwork !
Helen Chen

Sent from HUAWEI AnyOffice
From:Ofir Sonsino
To:Nachmias, Lior,Gitelman, Tal,Shlosberg, Yuli,Amit, Idan,EMPOROPULO, 
VITALIY,Avi Gaffa,oren...@amdocs.com,WEISS KEIDAR, EINAV,Levi, Eli
Cc:Lefevre, Catherine,Merkado, Tomer,onap-tsc,onap-discuss,Kapeluto, Zahi
Date:2018-12-04 01:27:58
Subject:[onap-tsc] ONAP SDC PTL Election results

I closed the election poll after all committers had voted. The results can be 
viewed here:
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_72c725d867708cbe<https://urldefense.proofpoint.com/v2/url?u=https-3A__civs.cs.cornell.edu_cgi-2Dbin_results.pl-3Fid-3DE-5F72c725d867708cbe=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=dU5BbqHfdIteEQga0tHc09e6b3M0D9hz2vSOfmXPwtk=L2C4mT2WrIhCyoxPrjn-gIhzb-IXuzA0BD6YN6PVPiQ=>

I won the election, thank you for your support!

Ofir

From: Sonsino, Ofir
Sent: Sunday, December 02, 2018 9:53 PM
To: Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Lando,Michael 
mailto:michael.la...@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>>; Levi, Eli 
mailto:eli.l...@intl.att.com>>
Cc: Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
Merkado, Tomer mailto:tomer.merk...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; Kapeluto, Zahi 
mailto:zahi.kapel...@intl.att.com>>
Subject: Re: SDC PTL nomination

Hi eveyone,

You have just recieved an email for the poll.
Any committer who likes to nominate can add themselves to the poll options.

Thanks,
Ofir

Sent from my Samsung Galaxy smartphone.


 Original message 
From: "Nachmias, Lior" 
mailto:lior.nachm...@intl.att.com>>
Date: 12/2/18 10:38 (GMT+02:00)
To: "Sonsino, Ofir" 
mailto:ofir.sons...@intl.att.com>>, "Lando,Michael" 
mailto:michael.la...@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>>
Cc: "Lefevre, Catherine" 
mailto:catherine.lefe...@intl.att.com>>, 
"Merkado, Tomer" 
mailto:tomer.merk...@intl.att.com>>, 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>, "Kapeluto, 
Zahi" mailto:zahi.kapel...@intl.att.com>>
Subject: RE: SDC PTL nomination

Dear committers,

We would like to start the SDC PTL poll. Please update if we should wait for 
more PTL nominations at your earliest convenience.
Ofir has volunteered to send the PTL poll but If someone else (from SDC 
committers) prefers to run the poll you're welcome.

Regards,
Lior

From: Sonsino, Ofir
Sent: Friday, November 30, 2018 2:43 PM
To: Lando,Michael 
mailto:michael.la...@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>>
Cc: Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
Nachmias, Lior mailto:lior.nachm...@intl.att.com>>; 
Merkado, Tomer mailto:tomer.merk...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: SDC PTL nomination

Dear SDC committers,

I hereby present myself for the role of PTL of SDC.

Technological background:

1.   Worked in AT SDC development team for two years as software engineer.

2.   Well familiar with SDC design and main workflows developments.

3.   As VID PTL, I worked in ONAP VID development team for the last two 

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

[Brian]

Unfortunately I dont think TF is bring in new LFN companies but I could be 
wrong. LFN is pretty broad right now already.

Brian


From: onap-tsc@lists.onap.org  On Behalf Of Alla 
Goldner
Sent: Monday, November 05, 2018 8:55 AM
To: onap-tsc@lists.onap.org; Casey Cain 
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Hi,

As far as  I understand, membership (and the fees our companies psy) is in LFN, 
therefore if one more project becomes part of LFN, it would actually mean 
spreading the same amount of money amongst more projects i.e. each project gets 
less.
This, of course, may not be TRUE in case this new project brings some new 
not-yet-LFN-members.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D474E5.9841AA00]

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: Monday, November 05, 2018 3:43 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Casey Cain 
mailto:cc...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Thanks Steve for the comments.

As for my comments  regarding the budget they were my personal conclusion. it 
would be useful to know how the budget would be handled, not only for these 
specific project, but for any/all future projects.


Regards,
Chaker


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Sunday, November 04, 2018 7:48 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Casey Cain 
mailto:cc...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Hi Chaker,

Thanks for the good summary.

My assumption is that irrespective of this decision ONAP retains independence 
on how to relate to TF in terms of it being either another external controller 
or a technology that would bring benefit in ONAP. I don’t see that we would 
conclude on a common view of those before the feedback is required, however 
with the assumption of the independence on how to relate to or adopt I don’t 
foresee any reason not to move ahead.  I agree with the comments that it is 
critical that it becomes an open community etc, however I don’t see the ONAP 
project reviewing that part as that would be upto TAC.

I had one question though – the summary indicated that this would bring in more 
Funding – I do not understand that conclusion from an ONAP Project perspective 
(i.e. inclusion of TF will not automatically result in neither more funding to 
LF nor to the project unless it comes with additional membership which I 
couldn’t see reported).

BR,

Steve

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: Saturday 3 November 2018 17:55
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Casey Cain 
mailto:cc...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Hello TSC members and proxies,

Attached please find a draft version to the TF Proposal for inclusion in the 
LFN TAC.

I also  added  all the email exchanges related to this topic so that we are all 
reading the same threads.

Once I  have a community agreement on this proposal  I will  add it to the jira 
as a supporting document

I propose we do the review via  email as It might be too challenging to get a 
timeslot that is convenient to all the members and in time for next weeks vote

Please review and comment.

Regards,
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: Friday, October 26, 2018 12:27 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Casey Cain 
mailto:cc...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Good afternoon/morning Chaker, Srini, Casey,

Thank you Chaker to take the lead on this action item.

Thank you both for your feedback.
The request from the TAC team was not to review the Tungsten Fabric proposal in 
the context of ONAP projects, but to review it as being part of LFN.

Casey – feel free to add any comment in case of I have miscaptured the TAC 
request

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 Chaker Al Hakim
Sent: Thursday, October 25, 2018 6:12 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Hi Srini,

Thanks for your input..

I am actually very familiar with TF (Contrail)  from my previous life. However, 
I did volunt

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

[Brian]

We are in the review cycle for the TF official inclusion and the ONAP TSC Chair 
votes for the ONAP community on the LFN TAC so ... Chaker volunteered to do the 
analysis for ONAP Community on how we should vote.

I think this come up next Wednesday for a vote in LFN TAC.

Brian


From: onap-tsc@lists.onap.org  On Behalf Of Chaker Al 
Hakim
Sent: Thursday, November 01, 2018 6:44 PM
To: onap-tsc@lists.onap.org
Cc: Casey Cain 
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Thanks Phil.

Perhaps we should put this effort on hold until everyone has had a chance to 
weigh in on it.

Regards,
Chaker



From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, November 01, 2018 1:36 PM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Cc: Casey Cain mailto:cc...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Hello All:

A slight correction to Mazin's input.

The request isn't associated with TF changing it's state.  This is actually 
part of the "re-induction" review.  When TF went through it's original 
induction earlier in the year (starting in March), the Governing Board 
requested that an Induction Process be created and documented for any/all new 
projects seeking to join LFN so that all reviews would be consistent and 
equitable.  The TAC at that time requested to lead the creation of that process 
from the Governing Board (GB) and that request was granted.  The TAC then 
determined that it would take until September or so before it would be complete 
with the creation of the process.  That left the TF project in limbo for a 
signification period of time.  So the GB in June "Conditionally Approved" the 
induction of TF into LFN with the requirement that TF go through a re-induction 
once the Induction process was in place.  The TAC finished their work and 
produced the following two artifacts to guide inductions [0][1].

The TF project has filled out the Data Template here [2].

I'm not sure exactly what the TAC's request is to the ONAP community.  For 
that, I defer to Casey and Cathrine as I was unable to attend the meeting where 
this request was apparently made.

I hope this helps.

[0]https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/lfn-process-rtd-verify-any/26/html/lifecycle/project_data_template.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__logs.opendaylight.org_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_lfn-2Dprocess-2Drtd-2Dverify-2Dany_26_html_lifecycle_project-5Fdata-5Ftemplate.html=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=bxr2kSi8nhOWNIi0jqhp-SUJAqLB9PN47pWlPIdd_M0=-GZ7ye4PDVDdZHfgbzulOT8Wq87SAJwg9bdTvy5bI4o=>
[1]https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/lfn-process-rtd-verify-any/26/html/principles.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__logs.opendaylight.org_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_lfn-2Dprocess-2Drtd-2Dverify-2Dany_26_html_principles.html=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=bxr2kSi8nhOWNIi0jqhp-SUJAqLB9PN47pWlPIdd_M0=3JjFl4A4DL9r8N4aJNsR6mnwTSC4CqFlSKGa4cYN2Yw=>
[2]https://gerrit.linuxfoundation.org/infra/#/c/12880/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.linuxfoundation.org_infra_-23_c_12880_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=bxr2kSi8nhOWNIi0jqhp-SUJAqLB9PN47pWlPIdd_M0=9pFfLgxdytpVt209u6rzqU9sg_0iUWyoeg7odEoSD-I=>

Best,

Phil.


On Thu, Nov 1, 2018 at 10:57 AM Chaker Al Hakim 
mailto:chaker.al.ha...@huawei.com>> wrote:
Thanks Mazin, that’s helpful.

So the question now seems to be more related to the process of promoting a 
project from incubation state to become a  fully approved LFN project.
If that’s the case then we would need to also look at 1) how other projects 
were promoted in the past, perhaps we can use (Akraino or Acumos as an example) 
 2) funding and resources and 3) impact on overall budget.

The other option is to collectively decide that a new process is needed to 
address this case, and to also address similar cases in the future, and would 
be considered a LFN governance item that the GB should take up

Regards,
Chaker


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] On Behalf Of 
GILBERT, MAZIN E (MAZIN E)
Sent: Thursday, November 01, 2018 8:17 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: Casey Cain mailto:cc...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Review Tungsten Fabric proposal (formely OpenContrail) 
#tac

Chaker,

My understanding that TF is an incubation project. Remember projects have 
different  lifecycle under LFN.
TF needs to become an approved full project for it to be like ONAP.

Phil or Kenny can provide the official position here.

Mazin


On Nov 1, 2018, at 1:03

Re: [onap-tsc] Issue with Beijing installation on Orange Openlab

[Brian]

Sylvain,

The IP address can be modified pretty easily but  10.0.11.1 is the assigned IP 
in the dns zone files for the message router – its on the OAM LAN setup by 
ONAP’s heat based install.

For instance in ueb-listener config (for SDC model distribution)

org.onap.ccsdk.sli.northbound.uebclient.msg-bus-address=10.0.11.1,10.0.11.1

Is the problem you are identifying that you are putting your DMaaP outside of 
the onap_oam network or using a different onap address scheme in HEAT 
deployments ?

Brian


From: ONAP-TSC@lists.onap.org  On Behalf Of Sylvain 
Desbureaux
Sent: Thursday, July 19, 2018 11:25 AM
To: ONAP-TSC@lists.onap.org
Subject: [onap-tsc] Issue with Beijing installation on Orange Openlab

Hello,
As requested by Eric, here’s current issue we’ve been facing so far when trying 
to install Beijing release (via HEAT) :

  *   Hardcoded message router IP address on SO (SO-731), AAI(AAI-1391), 
SDNC(SDNC-398), APPC (not yet jira issue created)
  *   SDC use a DNS entry that’s commented by default
  *   OOF doesn’t work as expected (MUSIC issue? Trying to understand ongoing)
  *   SO supports only keystone identity v2 (SO-18), which is removed on last 
OpenStack version (Queens). I don’t see  how to use multicloud instead of 
direct SO access
  *   Undocumented “complex” creation that’s mandatory to create a VIM into 
multicloud

We are rolling back to OpenStack Pike so I’ll tests more deeply after

Regards

--
[cid:image001.png@01D33D23.D1353070]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.com_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=DAXwXl2iAo_98JV6WrL6NFmXuIoSI2iDjBcvpv59jbk=RRCAVDLm-NexS3y5xtAAI7igr-oxzEK7qLhS2AHloU4=>

Sylvain Desbureaux
Senior Automation Architect
ORANGE/IMT/OLN/CNC/NCA/SINA

Fixe : +33 2 96 07 13 80 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__monsi.sso.francetelecom.fr_index.asp-3Ftarget-3Dhttp-253A-252F-252Fclicvoice.sso.francetelecom.fr-252FClicvoiceV2-252FToolBar.do-253Faction-253Ddefault-2526rootservice-253DSIGNATURE-2526to-253D-2B33-25202-252096-252007-252013-252080=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=DAXwXl2iAo_98JV6WrL6NFmXuIoSI2iDjBcvpv59jbk=BErq0r-0emWazfK4bimIn98gZKVGIeoJ1i07dY2MJK0=>
Mobile : +33 6 71 17 25 57 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__monsi.sso.francetelecom.fr_index.asp-3Ftarget-3Dhttp-253A-252F-252Fclicvoice.sso.francetelecom.fr-252FClicvoiceV2-252FToolBar.do-253Faction-253Ddefault-2526rootservice-253DSIGNATURE-2526to-253D-2B33-25206-252071-252017-252025-252057=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=DAXwXl2iAo_98JV6WrL6NFmXuIoSI2iDjBcvpv59jbk=LO1r5FRBxBzA2z4Rmiih-DDdAOHxat9lZ5oEk51f744=>
sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>


_



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 (#3466): https://lists.onap.org/g/ONAP-TSC/message/3466
Mute This Topic: https://lists.onap.org/mt/23745252/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss][onap-tsc][OOM] PTL Election for OOM

[Brian]

+1 since David isnt running. :)

Brian


From: ONAP-TSC@lists.onap.org  On Behalf Of David 
Sauvageau
Sent: Wednesday, July 18, 2018 2:41 PM
To: ELLIOTT, MICHAEL ; onap-disc...@lists.onap.org; 
ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss][onap-tsc][OOM] PTL Election for OOM

+1

From: Mike Elliott mailto:mike.elli...@amdocs.com>>
Date: Wednesday, July 18, 2018 at 1:52 PM
To: "Sauvageau, David" 
mailto:david.sauvag...@bell.ca>>, 
"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][onap-tsc][OOM] PTL Election for OOM

Dear ONAP OOM Committers,

I would like to nominate myself as Project Technical Lead (PTL) for the ONAP 
Operations Manager (OOM) project.

I have been a very active member of the OOM project since its inception. Active 
in both its architecture and as a top committer on the project. Over the last 
year, I standardized the Helm chart template for the ONAP community and 
delivered many of the Helm charts on behalf of the project teams. I also held a 
number of workshops, education and debugging sessions with the project teams 
and worked very closely with the integration team to help ensure the successful 
delivery of ONAP on OOM in the Beijing release.

We have a fantastic team and a great community, with a lot of smart, 
experienced and dedicated people. I’m really looking forward to working with 
this team to deliver on Casablanca and beyond!  And I would very much like to 
do that as your PTL.

Thanks very much for your consideration,
Mike Elliott


From: mailto:ONAP-TSC@lists.onap.org>> on behalf of 
David Sauvageau mailto:david.sauvag...@bell.ca>>
Date: Tuesday, July 10, 2018 at 1:45 PM
To: "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: [onap-discuss][onap-tsc][OOM] PTL Election for OOM

Dear ONAP OOM Committers,

As mandated by ONAP process, PTL elections must be held at least once a year.   
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=n2-kGaXG13tB7TNTlG111RSjN9yHryVH0pmcqldQ_-A=LNr8it7S9acQ7zJsa0tW--Tmv1yS2n9wKPXMbXZBGIo=>

If you are interested in the Integration PTL position.  Please reply to all to 
do self-nomination.

We will close the self-nomination window by 23:59 PDT July 18th, Wednesday, 
2018.  Further instructions will be sent out to the committers on the election 
procedure.  The final result will be announced on the ONAP lists before the end 
of this week.

Regards,
David Sauvageau


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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=n2-kGaXG13tB7TNTlG111RSjN9yHryVH0pmcqldQ_-A=-CZPm-BKldNDJPhIF0rHfqWZ4fp-AoVh7LPOeQU-P64=>


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

View/Reply Online (#3432): https://lists.onap.org/g/ONAP-TSC/message/3432
Mute This Topic: https://lists.onap.org/mt/23219123/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 Helpdesk #58470] Jira issues - again

[Brian]

I suspect its the smart search that is eating up client memory/cpu trying to do 
things but that is just a guess since its really really slow until it decides 
that the text I am entering doesnt match anything when creating a new JIRA 
ticket.

Brian


-Original Message-
From: ONAP-TSC@lists.onap.org  On Behalf Of Jessica 
Wagantall via RT
Sent: Wednesday, July 18, 2018 1:25 PM
Cc: liam.fal...@ericsson.com; kp...@linuxfoundation.org; 
ONAP-TSC@lists.onap.org; r...@linuxfoundation.org; LEFEVRE, CATHERINE 

Subject: [onap-tsc] [ONAP Helpdesk #58470] Jira issues - again

Adding some notes from Ryan on his recent investigation:

-
Looking through the jira logs for this user (djtimoney), I find no evidence of 
timeouts or other errors. sar says the system is not under any load at the time 
of the problem. The jira logs show nothing particularly unusual in usage. All 
the pages that I see the user visiting appear snappy for me. The project of 
interest is SDNC-395 and the user is probably in the agile view.
Some swap is still being used, however, so I boosted the system ram from 8G to 
12G
I'm unsure that this will be a fix since I can't replicate the problem, but it 
should help.

-

Thanks!
Jess

On Wed Jul 18 12:36:03 2018, liam.fal...@ericsson.com wrote:
> Hi All,
> 
> Don't know if this is helpful. Jira seems to be at its worst from
> about 11:00-15:00 UTC (One advantage of local time being ~UTC here).
> My speculation is that during these hours people in the east are
> finishing their day, people in Europe are in the middle of the day and
> people on the east coast of the Americas are starting their day,
> therefore during those four hours we have the heaviest load on Jira.
> 
> Best Regards
> Liam
> 
> On 18/07/2018, 17:24, "ONAP-TSC@lists.onap.org on behalf of Jessica
> Wagantall via RT"  helpd...@rt.linuxfoundation.org> wrote:
> 
> Adding Ryan
> 
> Dear Ryan,
> 
> From the stats we are capturing, were you able to detect any
> inconsistencies during
> the morning today?
> 
> Also, yesterday at 8:30 am PT time looks like Pam reported the same
> issue too.
> 
> Thanks a ton!
> Jess
> 
> On Wed Jul 18 08:51:18 2018, dt5...@att.com wrote:
> > LF IT,
> >
> > For the second consecutive week, I find myself unable to prepare for
> > my weekly SDNC project meeting because Jira freezing and not applying
> > updates.  I opened a ticket on this last week as well (see attached).
> > I will appreciate if you can address this issue at your earliest
> > convenience.  It is frankly already too late to help for this
> > morning’s call, but it would be good if I can at least follow up from
> > my meeting with updates later today.
> >
> > Thanks!
> > Dan
> >
> > --
> > Dan Timoney
> > SDN-CP Development
> > ONAP Project Technical Lead : CCSDK and SDNC
> >
> > Please go to  D2 ECOMP Release Planning
> > Wiki<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home>
> > for D2 ECOMP Project In-take, 2016 Release Planning, Change
> > Management, and find key Release Planning Contact Information.
> >
> 
> 
> 
> 
> 
> 
> 
> 







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

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

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[Brian Hedstrom]

Regarding the following statement:
*For modelspec doc, the committers: lingli deng, donghu, hanyanan, shitao
li, maopeng zhang, Rittwik Jana, Sandeep Shah, Zhaoxing Meng, Zhong heliu*

I don't feel this is an accurate list.  Since there is a lot of confusion
about what's being done under the Modeling Project versus the Modeling
Subcommittee, I feel that the list of committers above is omitting all the
committers who've been working on the various Information Models and Data
Models (for example, the VNF Package Model Sub-project efforts).  And as my
earlier email asked, I'm not clear what is meant by modelspec.  Our
committed resource, Jessie, for example has made significant model
contributions, in addition to several resources from AT (among others as
well).

Thanks
Brian

On Thu, Jul 5, 2018 at 8:44 PM, denghui (L)  wrote:

> Hi Mazin
>
>
>
> Inline please == >
>
>
>
> *From:* GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
> *Sent:* Friday, July 6, 2018 6:58 AM
> *To:* denghui (L) 
> *Cc:* onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
> *Subject:* Re: [onap-discuss] [onap-tsc] PTL Election announcement for
> ONAP modeling project
>
>
>
> Thanks Deng.
>
>
>
> Still need more clarification.
>
>
>
> 1. Are you running the Chair election for the Modeling subcommittee as
> well.
>
> If so, please make a clear distinction between that and the project PTL
> election.
>
> == > I have already sent email yesterday , there will be different
> election for committee and project,
>
> The community recommend to finish it by the end of Aug. we will do it.
>
>
>
> 2. I am concerned that the definition of committers is cloudy here.
>
> You have docs and you have code. Committers who write codes
>
> are not necessarily qualified to review and write code.
>
> Therefore, it is important that you have a PTL who is qualified to commit
>
> and understand code as well.
>
> == > current Gerrit repos has already distinguished them for different
> right:
>
> For toscaparser repo, the committers : maopeng zhao, Rittwik Jana, Serban
> Jora, Zhaoxing Meng.
>
> For modelspec doc, the committers: lingli deng, donghu, hanyanan, shitao
> li, maopeng zhang, Rittwik Jana, Sandeep Shah, Zhaoxing Meng, Zhong heliu
>
> For who will be PTL, let committers to decide.
>
>
>
> Thanks a lot
>
>
>
> DENG Hui
>
>
>
> Appreciate the clarification.
>
> Mazin
>
>
>
>
>
>
>
>
>
> On Jul 5, 2018, at 9:48 AM, denghui (L)  wrote:
>
>
>
> Hi Mazin
>
>
>
> I guess that you know that PTL couldn’t remove the committer, I sent email
> to every committer after Release 1,
>
> two of them email’s are not reachable, one agree to step down, so that’s
> the reason we removed 3 of them after the vote of all committers.
>
> Others replied and said that they would like to continue.
>
>
>
> Current committers are not only for tosca parser , but also for modelspec.
>
>
>
> Thanks a lot
>
>
>
> DENG Hui
>
>
>
> *From:* GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com
> ]
> *Sent:* Thursday, July 5, 2018 9:20 PM
> *To:* denghui (L) 
> *Cc:* onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
> *Subject:* Re: [onap-discuss] [onap-tsc] PTL Election announcement for
> ONAP modeling project
>
>
>
> Thanks. I am assuming the project is based on the repo that is supporting
> the Tosca Parsers,
>
> and you are tracking active committers.
>
>
>
> Are you holding an election at the same time for the Chair subcommittee?
>
>
>
> Mazin
>
>
>
>
>
> On Jul 5, 2018, at 8:21 AM, denghui (L)  wrote:
>
>
>
> Mazin
>
>
>
> Yes it is modeling project PTL election other than modeling subcommittee.
>
>
>
> You may have missed below email which does have the link to repositories
>
> https://wiki.onap.org/display/DW/Resources+and+Repositories#
> ResourcesandRepositories-Modeling
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA=>
>
> the committers in modeling project are:
>
> Hui Deng
>
> Shitao Li
>
> Rittwik Jana
>
> Bruce Thompson
>
> Maopeng Zhang
>
> Zhaoxing Meng
>
> Amir Levy
>
> Arthur Berezin
>
> Sandeep Shah
>
> Ling Li
>
> Liuhe Zhong
>
> Yannan Han
>
> Hu Dong
>
> Serban Jora
>
> Lingli Deng
>
>
>
> I did send email to helpdesk to remove 3 o

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[Brian Hedstrom]

Deng,
What do you mean by "modelspec"?  The modeling project has the following
scope and deliverables (I don't see Modeling Specifications listed which I
thought was part of the Modeling Subcommittee):
Also, I didn't see your response to Mazin's question: *Are you holding an
election at the same time for the Chair subcommittee?*
Scope:

   - Modeling tools and converters
   - Code - parsers (unified API interfaces) and tools (translators)
   - Support Use cases of ONAP: vCPE, vVoLTE, vFW, et al.

Deliverables for release 1

Parsers and translators:

   - Tosca Parsers
   - YANG Parsers
   - Tosca to Heat
   - YANG to Tosca


Thanks
Brian

On Thu, Jul 5, 2018 at 7:48 AM, denghui (L)  wrote:

> Hi Mazin
>
>
>
> I guess that you know that PTL couldn’t remove the committer, I sent email
> to every committer after Release 1,
>
> two of them email’s are not reachable, one agree to step down, so that’s
> the reason we removed 3 of them after the vote of all committers.
>
> Others replied and said that they would like to continue.
>
>
>
> Current committers are not only for tosca parser , but also for modelspec.
>
>
>
> Thanks a lot
>
>
>
> DENG Hui
>
>
>
> *From:* GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
> *Sent:* Thursday, July 5, 2018 9:20 PM
>
> *To:* denghui (L) 
> *Cc:* onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
> *Subject:* Re: [onap-discuss] [onap-tsc] PTL Election announcement for
> ONAP modeling project
>
>
>
> Thanks. I am assuming the project is based on the repo that is supporting
> the Tosca Parsers,
>
> and you are tracking active committers.
>
>
>
> Are you holding an election at the same time for the Chair subcommittee?
>
>
>
> Mazin
>
>
>
>
>
> On Jul 5, 2018, at 8:21 AM, denghui (L)  wrote:
>
>
>
> Mazin
>
>
>
> Yes it is modeling project PTL election other than modeling subcommittee.
>
>
>
> You may have missed below email which does have the link to repositories
>
> https://wiki.onap.org/display/DW/Resources+and+Repositories#
> ResourcesandRepositories-Modeling
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA=>
>
> the committers in modeling project are:
>
> Hui Deng
>
> Shitao Li
>
> Rittwik Jana
>
> Bruce Thompson
>
> Maopeng Zhang
>
> Zhaoxing Meng
>
> Amir Levy
>
> Arthur Berezin
>
> Sandeep Shah
>
> Ling Li
>
> Liuhe Zhong
>
> Yannan Han
>
> Hu Dong
>
> Serban Jora
>
> Lingli Deng
>
>
>
> I did send email to helpdesk to remove 3 of them from the list before
> based on the confirmation of project:
>
> Bruce Thompson
>
> Arthur Berezin
>
> Ling Li
>
>
>
> It seems that they are still here, I will send again to helpdesk
>
> So the final qualified committers are:
>
> Hui Deng
>
> Shitao Li
>
> Rittwik Jana
>
> Maopeng Zhang
>
> Zhaoxing Meng
>
> Amir Levy
>
> Sandeep Shah
>
> Liuhe Zhong
>
> Yannan Han
>
> Hu Dong
>
> Serban Jora
>
> Lingli Deng
>
>
>
> Thanks for your checking
>
> Best regards,
>
>
>
> DENG Hui
>
>
>
>
>
> *From:* GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com
> ]
> *Sent:* Thursday, July 5, 2018 7:35 PM
> *To:* denghui (L) 
> *Cc:* onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
> *Subject:* Re: [onap-discuss] [onap-tsc] PTL Election announcement for
> ONAP modeling project
>
>
>
> Deng,
>
>
>
> I appreciate you holding an election for the PTL.
>
>
>
> For the modeling project PTL election, we need each Chair to ensure they
> have vetted all
>
> active committers before any election is taking place. Can you share the
> list of
>
> active committers.
>
>
>
> As outlined in the website the issue is different for the subcommittee
> modeling Chair.
>
>
>
> It seems that you are initiating a PTL election and not a subcommittee
> modeling Chair election.
>
> Please confirm, and share the list of active Committers who will be voting
> for the new PTL.
>
>
>
> thanks
>
> mazin
>
>
>
>
>
>
>
>
>
>
>
>
> On Jul 4, 2018, at 2:14 AM, denghui (L)  wrote:
>
>
>
> Dear ONAP Community and ONAP TSC,
>
>
>
> As mandated by ONAP process, PTL elections must be held at least once a
> year.
>
> You can read more details here: https

Re: [onap-tsc] Confirming Context of TSC Structure Vote

[FREEMAN, BRIAN D]

Kenny,

We have about 14 people on the bridge is the calendar invite wrong ?

Brian


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, March 15, 2018 8:59 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Confirming Context of TSC Structure Vote

(bcc’d to onap-tsc-vote)

I received an email overnight pointing out the following error:

“Steady State” is defined in Section 2,b,ii as is documented below.
The modification required to Section 2,b,i  is to the “Startup Period”.
I am closing the current vote, and we will discuss this at the TSC meeting.


Best Regards,
-kenny
On Mar 14, 2018, at 2:24 PM, Kenny Paul 
<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> wrote:

Having received no responses to this email, since we have not yet formalized a 
release plan for Casablanca, and since need a date rather than a release name 
as the criteria (since release dates are subject to change), I am putting 
forward the vote as follows:

The TSC approves modifying the “Steady State” definition in Section 2,b,i of 
the ONAP Technical Charter to be September 30, 2018.

THIS IS JUST THE INTENT AND LANGUAGE, IT IS NOT THE VOTE ITSELF.  The formal 
vote will occur on the onap-tsc-vote alias, not here.
A plus-one, minus-one, or zero here on this issue is null and void.

This will extend the TSC’s decision making timeline on the composition and 
election process for the ONAP TSC by a full quarter from what is currently 
reflected in the ONAP Technical Charter and 6 months from the original date 
established in the ONAP charter when the project was launched.

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


On Mar 8, 2018, at 12:47 PM, Kenny Paul 
<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> wrote:

Following up from today’s TSC Meeting on the TSC Composition discussion. 
Section 2 of the ONAP Technical Charter reads as follows:

b. TSC Voting Members

  i. “Startup Period”: From date of creation of the ONAP Project a Series of LF 
Projects, LLC (“Project Launch”) until June 30, 2018 (such period the “Startup 
Period”), the TSC voting members will consist of one appointee from each 
organization listed as having TSC appointees on 
ONAP.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.org_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=q20tjxs5gAaeVvLg3oc3GVNxvWq7z0VEXTTmRfYaFdo=nh2eL3VLrJei_VHmEmbS8-ksfGYgToHfBQd4wwhm4Vs=>.
 All TSC voting members will be listed on 
ONAP.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.org_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=q20tjxs5gAaeVvLg3oc3GVNxvWq7z0VEXTTmRfYaFdo=nh2eL3VLrJei_VHmEmbS8-ksfGYgToHfBQd4wwhm4Vs=>.

  ii. “Steady State”: After the Startup Period, the size, makeup and procedure 
for determining voting members of the TSC will be as determined by the TSC and 
documented on the ONAP web site.

A couple things of note here directly relevant to this morning’s discussion:
- First at the TSC’s request the original “Steady State” cutover to a 
meritocratic based TSC was previously changed from the end of this month to 
June 30 to avoid disrupting the Beijing release.  Changing this again would 
require amending the ONAP Technical Charter.

- Second, limitations were established to maintain the TSC membership at its 
current level until the “Steady State” structure and elections. Opening this up 
to all include TSC membership from any LFN Platinum member that is not already 
represented on the ONAP TSC in advance of the “Steady State” elections will 
require an amendment to the ONAP Technical Charter.  My personal recommendation 
is to keep the status quo on this item.

- Finally although we had 19 Platinum Member reps appointed to the TSC, there 
were only 18 TSC members ever listed on the web 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.onap.org_about_tsc=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=q20tjxs5gAaeVvLg3oc3GVNxvWq7z0VEXTTmRfYaFdo=W6wFPcd7KZxeC5ucGgc8Kn38NvUTvhPCroHYgX55480=>
  - our requests to the remaining Platinum member for a pic/bio info from were 
never answered and therefore nothing was ever posted. (Also there has been 
little to no participation since the 1st or 2nd meeting for what it is worth.)

So in summary, the current size of the TSC based upon the ONAP Technical 
Charter (effective Jan. 1st) is 18 members and will remain so until the TSC 
sets the Steady State structure by June 30th, or amends the Technical Charter 
to do something different.

Having provided that background my understanding of today’s proposal is for the 
TSC to stay “as-is” until after Casablanca.

THIS IS TO ENSURE CLARIFICATION OF THE INTENT AND LANGUAGE, NOT THE VOTE 
ITSELF.  The formal vote will occur on the

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

[Brian Hedstrom]

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

Thanks
Brian

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

> Hello modeling subcommittee,
>
>
>
> Many Thanks to Jessie’s kind presentation on GitHub for Papyrus model.
>
> https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
>
> https://wiki.onap.org/download/attachments/16003450/
> GitHub%20for%20Papyrus%20Model.pptx?api=v2
>
>
>
> Due to time limitation, we would like to discussion in the list together
> with the communities whether, how and when we should move to Github to
> manage the modeling spec update process.
>
>
>
> Thanks a lot for your advice
>
> Best regards,
>
>
>
> DENG Hui
>



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

Re: [onap-tsc] 答复: Re: ONAP VoLTE SDC call

[FREEMAN, BRIAN D]

If you look at the SLI-API tutorial for VoLTE on the wiki you can get a sense 
of how this is accomplished. Here a set node is used but all the value’s could 
references to context memory variables.

Device.* schema is defined by the adaptor (in this case the DC Gateway vendor’s 
API)









As an example (final parameter-name have not been selected) we might get this 
input


{

"parameter-name": "volte-wan-activate.dca_name",

"string-value": "dcA-east"

},

{

"parameter-name": "volte-wan-activate.dcb_name",

"string-value": "dcB-west"

},


The DG would lookup dcA-east and determine that the ip address of the 
controller was 10.0.1.0 and dcB-east was 10.0.2.0 (or FQDNs etc) and that the 
dcA router ID was:
'CBB702C3-6789-1234-A5AD-000A’

The DG would assign a WAN VNI from resource assignment, assign import and 
export route targets from resource assignment , calculate names from 
source/destination data like the device.description, etc.

Input variables from the call from SO would also be mapped.

Then the paramters to the adaptor could be









To be clear device.* comes from the adaptor and probably would be something 
more specific than device but the leaf names would likely match the parameters 
in the API call to the 3rd party controller.

Dc_connection.* and service_data.* are from the northbound service model and 
network data model in context memory.

Using the SLI-API and an emulator we can build and test the adaptor and the DG 
in advance of having the rest of the assets available.

The actual parameter names need to be specified so that SO can provide the 
correct rpc into SDNC but that is not dependent on the actual names used in the 
adaptor node – the DG maps from the service model parameters into those adaptor 
specific (device) parameters.

Brian


From: FREEMAN, BRIAN D
Sent: Tuesday, August 08, 2017 8:35 AM
To: huang.zhuo...@zte.com.cn
Cc: SHADMI, DAVID <ds2...@att.com>; TIMONEY, DAN <dt5...@att.com>; 
seshu.kuma...@huawei.com; KAPELUTO, ZAHI <zk0...@intl.att.com>; 
onap-disc...@lists.onap.org; ROZIN, EDEN <er4...@intl.att.com>; 
onap-tsc@lists.onap.org
Subject: RE: Re: [onap-tsc]答复: Re: ONAP VoLTE SDC call

The adaptor should define its inputs as parameters in the adaptor node.

The schema for those paramters can be defined by the adaptor/vendor.

The directed graph will map from the WAN model into the vendor specific mode in 
the adaptor.

We are going to recomend using a model called the GENERIC-RESOURCE-API that has 
a name/value pair list of the parameters and we will pull the paramters of 
interface from that API to populate the inputs to the adaptor node.

Brian


From: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn> 
[mailto:huang.zhuo...@zte.com.cn]
Sent: Tuesday, August 08, 2017 7:30 AM
To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>
Cc: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; TIMONEY, DAN 
<dt5...@att.com<mailto:dt5...@att.com>>; 
seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>; KAPELUTO, ZAHI 
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; ROZIN, EDEN 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: 答复: Re: [onap-tsc]答复: Re: ONAP VoLTE SDC call


Hi, Brian

Maybe here is the old question. Is there a common model for WAN description 
in SDN-C? If no, where should SDN-C get the input of adapter?

Thank you!











黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.


[cid:image001.gif@01D31024.C456DB50]

[cid:image002.gif@01D31024.C456DB50]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=HOWZLahe1mXKqDImjc3B5fipcPdDraflmcdTzJ3nQjU=8zUbLA_YesMd1uo2vKgT-1smH1jDAHKSGQPIqz6Dc3Y=>


原始邮件
发件人： <bf1...@att.com<mailto:bf1...@att.com>>;
收件人：黄卓垚10112215; <ds2...@att.com<mailto:ds2...@att.com>>; 
<dt5...@att.com<mailto:dt5...@att.com>>; 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>;
抄送人： <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>; 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.o

Re: [onap-tsc] 答复: Re: ONAP VoLTE SDC call

[FREEMAN, BRIAN D]

The adaptor should define its inputs as parameters in the adaptor node.

The schema for those paramters can be defined by the adaptor/vendor.

The directed graph will map from the WAN model into the vendor specific mode in 
the adaptor.

We are going to recomend using a model called the GENERIC-RESOURCE-API that has 
a name/value pair list of the parameters and we will pull the paramters of 
interface from that API to populate the inputs to the adaptor node.

Brian


From: huang.zhuo...@zte.com.cn [mailto:huang.zhuo...@zte.com.cn]
Sent: Tuesday, August 08, 2017 7:30 AM
To: FREEMAN, BRIAN D <bf1...@att.com>
Cc: SHADMI, DAVID <ds2...@att.com>; TIMONEY, DAN <dt5...@att.com>; 
seshu.kuma...@huawei.com; KAPELUTO, ZAHI <zk0...@intl.att.com>; 
onap-disc...@lists.onap.org; ROZIN, EDEN <er4...@intl.att.com>; 
onap-tsc@lists.onap.org
Subject: 答复: Re: [onap-tsc]答复: Re: ONAP VoLTE SDC call


Hi, Brian

Maybe here is the old question. Is there a common model for WAN description 
in SDN-C? If no, where should SDN-C get the input of adapter?

Thank you!











黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.


[cid:image001.gif@01D31021.34BA5BF0]

[cid:image002.gif@01D31021.34BA5BF0]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=HOWZLahe1mXKqDImjc3B5fipcPdDraflmcdTzJ3nQjU=8zUbLA_YesMd1uo2vKgT-1smH1jDAHKSGQPIqz6Dc3Y=>


原始邮件
发件人： <bf1...@att.com<mailto:bf1...@att.com>>;
收件人：黄卓垚10112215; <ds2...@att.com<mailto:ds2...@att.com>>; 
<dt5...@att.com<mailto:dt5...@att.com>>; 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>;
抄送人： <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>; 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>;
日 期 ：2017年08月07日 23:09
主 题 ：Re: [onap-tsc]答复: Re:  ONAP VoLTE SDC call


“be placed manually according to specific apdator”

The 3rd party adaptor needs the yang model as part of its development so it 
isnt needed from SDC its needed as part of the adaptor development.


I dont know if there is value in providing the yang model in the CSAR since its 
already going to be available on the controller as part of the adaptor that 
would be more Dan Timoney’s call and he probably has a better view of the 
overall  SDC to SDNC flow anyway.

Brian


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
Sent: Monday, August 07, 2017 7:12 AM
To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; TIMONEY, DAN 
<dt5...@att.com<mailto:dt5...@att.com>>; 
seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; KAPELUTO, 
ZAHI <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; ROZIN, EDEN 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] 答复: Re: ONAP VoLTE SDC call


Hi,  David, Dan and seshu



   Some questions about how WAN service descriptor works with SO and SDN-C:

  1.  How does SDN-C import the YANG file describing NBI of 3rd controller? By 
Json from SO? Or be placed manually according to specific apdator? Or by other 
ways?
  2.  What kind of infomation should be contained in the interface between SO 
and SDN-C? YANG describing NBI of 3rd controller? CSAR of WAN descriptor? 
Information sending to 3rd controller? Or something else?
  3.  SDN-C receive CSAR from SDC?
  4.  SO is responsible for abstracting YANG from CSAR which is discribing the 
NBI of 3rd controller?
  5.  How to import the YANG describing NBI of 3rd controller into CSAR?



I suggest that we should discuss this topic outside the SDC call on Monday.  Do 
you have any good idea about suitable time for the discussion?



Thank you all!









黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy  & IT-IT Dept.


[cid:image001.gif@01D31021.34BA5BF0]

[cid:image002.gif@01D31021.34BA5BF0]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86  755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.co

Re: [onap-tsc] 答复: Re: ONAP VoLTE SDC call

[FREEMAN, BRIAN D]

“be placed manually according to specific apdator”

The 3rd party adaptor needs the yang model as part of its development so it 
isnt needed from SDC its needed as part of the adaptor development.


I dont know if there is value in providing the yang model in the CSAR since its 
already going to be available on the controller as part of the adaptor that 
would be more Dan Timoney’s call and he probably has a better view of the 
overall SDC to SDNC flow anyway.

Brian


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of huang.zhuo...@zte.com.cn
Sent: Monday, August 07, 2017 7:12 AM
To: SHADMI, DAVID <ds2...@att.com>; TIMONEY, DAN <dt5...@att.com>; 
seshu.kuma...@huawei.com
Cc: onap-disc...@lists.onap.org; KAPELUTO, ZAHI <zk0...@intl.att.com>; ROZIN, 
EDEN <er4...@intl.att.com>; onap-tsc@lists.onap.org
Subject: [onap-tsc] 答复: Re: ONAP VoLTE SDC call


Hi,  David, Dan and seshu



   Some questions about how WAN service descriptor works with SO and SDN-C:

  1.  How does SDN-C import the YANG file describing NBI of 3rd controller? By 
Json from SO? Or be placed manually according to specific apdator? Or by other 
ways?
  2.  What kind of infomation should be contained in the interface between SO 
and SDN-C? YANG describing NBI of 3rd controller? CSAR of WAN descriptor? 
Information sending to 3rd controller? Or something else?
  3.  SDN-C receive CSAR from SDC?
  4.  SO is responsible for abstracting YANG from CSAR which is discribing the 
NBI of 3rd controller?
  5.  How to import the YANG describing NBI of 3rd controller into CSAR?



I suggest that we should discuss this topic outside the SDC call on Monday.  Do 
you have any good idea about suitable time for the discussion?



Thank you all!









黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.


[cid:image001.gif@01D30F6D.7FC0A5A0]

[cid:image002.gif@01D30F6D.7FC0A5A0]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=FUaOnuThGoi7rszuMjB5A44hZAWX0ak0as-MAyXrNNw=fE5ujy53EYv0-ASEIaLvHBom0jzRvgi4ocNdpKeIErk=>


原始邮件
发件人：黄卓垚10112215
收件人： <ds2...@att.com<mailto:ds2...@att.com>>; 
<dtimo...@att.com<mailto:dtimo...@att.com>>; 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>;
抄送人：袁越10008526; <er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>; 
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;
日 期 ：2017年08月05日 16:45
主 题 ：答复: Re: [onap-tsc] ONAP VoLTE SDC call



There are some issues about how WAN service descriptor works with SO and SDN-C 
might need to be clarified. I suggest should we have a discussion on Monday 
8:00 PM UTC on these issues first? If this time is not suitable for everyone, 
please choose a better time for discussion.



Thank you all!











黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.


[cid:image001.gif@01D30F6D.7FC0A5A0]

[cid:image002.gif@01D30F6D.7FC0A5A0]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=FUaOnuThGoi7rszuMjB5A44hZAWX0ak0as-MAyXrNNw=fE5ujy53EYv0-ASEIaLvHBom0jzRvgi4ocNdpKeIErk=>






发件人： <ds2...@att.com<mailto:ds2...@att.com>>;
收件人：袁越10008526;黄卓垚10112215;
抄送人： <er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>; 
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;
日 期 ：2017年08月05日 01:27
主 题 ：Re: [onap-tsc] ONAP VoLTE SDC call


Can we use the SDC call on Monday 8am PDT to discuss the WAN service descriptor?

Thanks,
David

From: yuan@zte.com.cn<mailto:yuan@zte.com.cn> 
[mailto:yuan@zte.com.cn]
Sent: Thursday, August 03, 2017 10:49 PM
To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; 
huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
Cc: denghu...@huawei.com<mailto:denghu...@huawei.com>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>;

[onap-tsc] SDC VoLTE - Recommendation to focus on Plan A

[FREEMAN, BRIAN D]

ONAP TSC,

After reviewing the feedback on the TOSCA support for VoLTE Use Case there is a 
path, with help from the community, to implement Plan A.  Plan A is a single 
SDC application that would support both HEAT and TOSCA artifact imports which 
is the fundamental vision of merging the two projects. While it is not without 
some risk, it is the right solution. Alternate plans would result in two SDC's 
and in fact require more work to implement that would detract from success on 
plan A.  If we are serious that success for ONAP is that it is a platform for 
future service provider services then we must address the hard problems of 
software integration and collectively focus on the success of the combined 
platform. SDC as the front door for service creation is arguably the most 
important to get right. I'm confident that with help from the community we can 
make Plan A work for Amsterdam and by focusing on that plan we can focus the 
resources and increase our comfort that we will meet the Amsterdam release date.

I would like the TSC to approve focusing on Plan A for the SDC TOSCA support.

Respectfully,

Brian Freeman



From: LANDO, MICHAEL
Sent: Tuesday, August 01, 2017 7:33 AM
To: 'onap-disc...@lists.onap.org' <onap-disc...@lists.onap.org>
Cc: SHADMI, DAVID <ds2...@att.com>; KAPELUTO, ZAHI <zk0...@intl.att.com>; 
ROZIN, EDEN <er4...@intl.att.com>; SACKS, ZOHAR <zohar.sa...@amdocs.com>; 
EMPOROPULO, VITALIY <vitaliy.emporop...@amdocs.com>; SHTRAICHMAN, LIRON 
<liron.shtraich...@amdocs.com>; LEFEVRE, CATHERINE <cl6...@intl.att.com>; 
SPATSCHECK, OLIVER <spat...@research.att.com>; FREEMAN, BRIAN D 
<bf1...@att.com>; zhao.huab...@zte.com.cn
Subject: SDC volte use case support information

Hi,
The Presentations and CSAR's from the current discussion on VOLTE support in 
SDC are now available under our meeting notes.
https://wiki.onap.org/display/DW/SDC+2017-07-31+Meeting+notes




BR,

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


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

Re: [onap-tsc] MEF and ONAP coordination

[Brian Hedstrom]

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

Thanks
Brian

On Sun, Jul 16, 2017 at 4:16 AM, Alla Goldner <alla.gold...@amdocs.com>
wrote:

> Hi all,
>
>
>
> Currently, ONAP/MEF coordination appears twice – both in standards and in
> Open source coordination (https://wiki.onap.org/
> display/DW/External+Standard+Coordination and
> https://wiki.onap.org/display/DW/External+Open+Source+
> Community+Coordination)
>
>
>
> I believe it should be merged altogether to the standards section.
>
>
>
> What do you think?
>
>
>
> Best regards,
>
>
>
> *Alla Goldner*
>
>
>
> Open Network Division
>
> Amdocs Technology
>
>
>
>
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
>
> _______
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
>


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

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

[FREEMAN, BRIAN D]

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

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

Brian


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of li.z...@zte.com.cn
Sent: Sunday, June 11, 2017 10:11 PM
To: AGGARWAL, MANISHA <amani...@att.com>; KLEIN, REUBEN <rk1...@att.com>; 
BURNS, COLIN <coli...@amdocs.com>; l...@vmware.com; TIMONEY, DAN 
<dt5...@att.com>; parviz.yeg...@huawei.com; dewa...@gigaspaces.com; 
saw@huawei.com; SMOKOWSKI, STEVEN <ss8...@att.com>; 
denglin...@chinamobile.com; dsha...@interwise.com; eden.ro...@att.com; 
zahi.kapel...@att.com; HEMLI, AMICHAI <ah0...@intl.att.com>; WEST, EARLE 
<ew8...@att.com>
Cc: onap-tsc@lists.onap.org
Subject: [onap-tsc] Call for feedback about interaction with External Register 
System


Hi There,



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



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

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

For the project description and the scope of ESR, you may visit 
https://wiki.onap.org/pages/viewpage.action?pageId=5734948<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D5734948=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=gvXZeOHCFFd2yu5oHWLlYHL773lfoQpu0MPrXr9CmAc=be337xMew-E381bDS4dpP6E3RHo-ltD1zMxkQ2xYKuk=>


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

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



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



Project


Related external system


 Will interact with ESR(Yes/No)


VID


VIM/VNFM/EMS/SDNC

Yes


Multi-VIM


VIM

Yes


SDN-C


Vendor SDN controller

Yes


VF-C


VIM/VNFM/EMS/SDNC

Yes


SO


VIM/VNFM/EMS/SDNC

Yes


APP-C


EMS

Yes




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



Thanks a lot.

LiZi











李滋 lizi



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


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

[cid:image003.gif@01D2E36B.CB0E17F0]
成都市高新区天府大道中段800号中兴通大厦
ZTE Corporation Building, No. 800 Middle Section Tianfu Avenue,
Chengdu, P..R.China, 610041
M: +86 15583405168
E: li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=gvXZeOHCFFd2yu5oHWLlYHL773lfoQpu0MPrXr9CmAc=rvpfeB1fqj4yzswyYXubix7GC0jRnwOeuXQbbtxrVmI=>


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

[onap-tsc] Face to Face meeting agreements

[Brian Hedstrom]

In looking at the F2F Day 1 Meeting Notes
<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-08-01.38.html>,
and reviewing the IRC channel for Day 2
<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-09-01.07.log.txt>
(it appears the meeting wasn't closed with #endmeeting and a meeting minute
link wasn't generated), I'm finding it difficult to see what motions were
voted on and approved versus voted down. There is missing/incomplete
information in those notes.

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

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

   - Authentication and Authorization Framework
   - DMaaP
   - External System Register
   - Network Function Change Management
   - ONAP Extensibility
   - ONAP University
   - Open Lab
   - SNIRO Optimization Framework
   - VNF Validation Program (ONAP ICE)
   - Common Frameworks

Also, I only found that VoLTE Use Case was approved, were the other use
cases approved?

Thanks,

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

Re: [onap-tsc] Project Proposal: ONAP CLI

[FREEMAN, BRIAN D]

Scripting is useful but shell scripts that wrap curl  functions are the method 
we are pushing folks towards. Separate CLI and REST API’s are generally a 
waste. With automation we see less pressure to have a CLI and more a need to be 
able to get the work done and CURL/POSTMAN are the tools of the new devops 
environment.

Brian

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Dhananjay Pavgi
Sent: Tuesday, May 09, 2017 6:32 AM
To: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>; t...@lists.onap.org
Subject: Re: [onap-tsc] Project Proposal: ONAP CLI

Thanks. Don’t agree with the comment on GUI can’t be used in DevOps. Wonder how 
CLI would be easier in any which ways to work with clumsy yaml/TOSCA files. CLI 
was good for short service commands.

While it would still make sense to have it for VNFs; for some of the reasons 
sighted below. For Network Automation Platform like ONAP; still ponder over 
it’s necessity.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png@01CE7323.F2727500]   [ONAP_logo_Sig]
www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_=DwMFbw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=ncRngcZpXka2jMSmL1oJGt4w1hL19yXmHBVERs05SNw=Zu_mS4NKhmNLm4tuW1BV3uizS5cAdpEYQkPdFGvAaVs=>
 Platinum Member. Visit : 
http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_=DwMFbw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=ncRngcZpXka2jMSmL1oJGt4w1hL19yXmHBVERs05SNw=FE7k_tXBoEXofY-ciKQkRTncgzJdWRKjiUxeeTE_3es=>

From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, May 09, 2017 7:37 PM
To: Dhananjay Pavgi 
<dp00476...@techmahindra.com<mailto:dp00476...@techmahindra.com>>; 
t...@lists.onap.org<mailto:t...@lists.onap.org>
Subject: RE: Project Proposal: ONAP CLI

Thanks for sharing your comments. Pls find my inputs below:

CLI has its own advantages over GUI in following aspects:

  1.  ONAP Continuous integration (CI), where we want to perform various ONAP 
operations, CLI will be very handy option. This is applicable to 3rd party CI 
as well.
  2.  While GUI is the preferred interface for end-user, back-end operators and 
 admin always prefer CLI (it’s an industry trend !) as its simpler, faster.
  3.  Installation scripting, VNF boot scripting with ONAP.
  4.  Dev testing … integration testing.
  5.  OSS/BSS products would want to perform any automation on top of ONAP, it 
could go either with CLI or SDK.
In short, GUI can’t be used in devops environment, and CLI fills the gap.

In addition, CLI provides an alternate option to GUI,  for operating back ONAP 
functionalities.

And to feel the importance of CLI, Pls refer some existing active automation 
projects in industry, given here:

  1.  OpenStack heat provides  CLI ‘openstack stack’
  2.  Cloudify provides CLI ‘cfy’
  3.  ODL provides CLI with different commands

So IMHO,

  *   CLI does compliment GUI and does not defeat it.
  *   Considering ONAP as platform, CLI should be part of it.

Regards
Kanagaraj M

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

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

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Tuesday, May 09, 2017 2:09 PM
To: Kanagaraj Manickam; t...@lists.onap.org<mailto:t...@lists.onap.org>
Subject: RE: Project Proposal: ONAP CLI

Do we really need CLI. Defeats the purpose of automation and GUI/Portals made 
available at each layer.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png@01CE7323.F2727500]   [ONAP_logo_Sig]
www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_=DwMFbw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=ncRngcZpXka2jMSmL1oJGt4w1hL19yXmHBVERs05SNw=Zu_mS4NKhmNLm4tuW1BV3uizS5cAdpEYQkPdFGvAaVs=>
 Platinum Member. Visit : 
http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_=DwMFbw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw

[onap-tsc] [onap-discuss] Some questions regarding Controllers in ONAP Architecture

[FREEMAN, BRIAN D]

David,

This is one of those service provider options.

Today, we use APPC for Openstack operations like 
start/stop/restart/migrate/evacuate/etc?  even for L3 VNF because we liked 
having all the Ppenstack operations in one controller (a vCE and vSBC look the 
same for operations like stop/stop the VM). We tie that into our closed loop 
and our change management functions.

The functions that APPC uses (both northbound and southbound) could work on an 
SDNC instance (they advantage of the common platform) but we haven?t seen the 
need yet. Generally we have used APPC as both a L4-L7 configuration manager as 
well as a (L2-L7 ) cloud VNF Manager. SDNC has L2/L3 configuration, signaling , 
L0/L1 interface and in some instances our neutron agent for cloud networking.

Since SDNC can call APPC functions through REST (or through the call node if 
they were co-resident) we haven?t worried too much about the VNF manager 
boundary. This also stems from the fact that most L2/L3 VNFs are relatively 
simple compared to the L4-L7 VNFs we see in vIMS and vEPC.

That being said if a service provider had strong desires to separate them then 
it would be feasible to use the VNF Manager functions out of SDNC but would 
require some integration work (karaf feature bundle dependencies).

Out of the box in ONAP, APPC is the one listening on DMaaP/MR for events and 
has the adapter  (cdp-pal) to talk to Openstack so I would recommend using APPC 
in that mode.

Brian




From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Sauvageau, David
Sent: Wednesday, April 19, 2017 5:16 PM
To: ROSE, DANIEL V ; Dhananjay Pavgi ; HU, BIN ; onap-tsc at lists.onap.org; 
onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Some questions regarding Controllers in 
ONAP Architecture

Hi Daniel.

For clarification, in the context of an L3 router.

[onap-tsc] ONAP Project Developer Event Agenda

[Brian Hedstrom]

During the TSC Meeting last week it was mentioned that a small team would
be constructed to define and finalize the May F2F agenda.  Is this team
open to non Platinum Members?  Can anyone volunteer to be a part of this
team?

Thanks,

-- 
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oamtechnologyconsulting.com
brian.hedstrom at oamtechnologies.com
720-470-7091
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170417/a01b512e/attachment.html>

[onap-tsc] Charter

[Brian Hedstrom]

If the Charter extends beyond the technical steering committee, to other
committees, sub-committees and working groups, the name should reflect that
such as ONAP Charter.  If the ONAP organization will have other
"non-Technical" committees, such as a Marketing Committee, where they would
have a different Charter, then perhaps be more explicit around ONAP
Technical Committee Charter (and likewise ONAP Marketing Committee
Charter). This model assumes sub-committees, working groups and projects
fall under one of the main Committees such as Technical, Marketing, etc.

On Mon, Apr 10, 2017 at 12:35 PM, Stephen Terrill <
stephen.terrill at ericsson.com> wrote:

> Hi All,
>
>
>
> In the F2F TSC regarding the charter, there as an item that we should take
> to the mailing list.
>
>
>
> Charter name:  Should we call the charter ?Technical Steering Committee
> Charter? or ?Technical Community Charter?.  Note: The second option puts
> the emphasis on the community and the TSC is helping to ensure the
> operations for the community.
>
>
>
> Please, opinions welcome as we are drafting the updates during this week.
>
>
>
> Best Regards,
>
>
>
> Steve.
>
>
>
>
>
> [image: Ericsson] <http://www.ericsson.com/>
>
> *STEPHEN TERRILL *
> Technology Specialist
> DUIC, Systems and Technology
> Development Unit IP & Cloud
>
> Business Unit, IT & Cloud Products
>
>
> *Ericsson*
> Ericsson R Center, via de los Poblados 13
> 28033, Madrid, Spain
> Phone +34 339 3005
> Mobile +34 609 168 515 <+34%20609%2016%2085%2015>
> Stephen.Terrill at ericsson.com
> www.ericsson.com
>
>
>
> [image: http://www.ericsson.com/current_campaign]
> <http://www.ericsson.com/current_campaign>
>
>
>
> Legal entity: Ericsson Espa?a S.A, compay registration number
> ESA288568603. This Communication is Confidential. We only send and receive
> email on the basis of the terms set out at www.ericsson.com/email_
> disclaimer
>
>
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC at lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
>


-- 
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oamtechnologyconsulting.com
brian.hedstrom at oamtechnologies.com
720-470-7091
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/dbe6b9cd/attachment.html>

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

[FREEMAN, BRIAN D]

Phil,

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

Seems like late May is the best choice.

Brian


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

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

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

Best,

Phil.

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

Mazin


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

Hi,

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

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




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



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


Regards,
Jason Hunt
Executive Software Architect, IBM

Phone: +1-314-749-7422<tel:(314)%20749-7422>
Email: djhunt at us.ibm.com<mailto:djhunt at us.ibm.com>
Twitter: @DJHunt

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
http://www.amdocs.com/email_disclaimer.asp<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.amdocs.com_email-5Fdisclaimer.asp=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=pWx34SC5QQYkRu4Z4BEm-m601cmnrt_UCTzLc-mEasc=iwVSlz3RgKnxLI2t4XgoxAI0c2dVWUPfnYLFRGet5A8=>
 ___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=2qDBFz2Nv5zgbgGhmfgoTxcCj1Ntr9uHlZiAwO8crRY=8uqc15bz1wtUR93A0ju8YOS31o3_Y4FlodYtyVG3NyE=


___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=pWx34SC5QQYkRu4Z4BEm-m601cmnrt_UCTzLc-mEasc=TbqDyjwz22axW_YYjwxv4nzccZY8BoaX3OJMdTRB_7I=>



--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170331/73602322/attachment-0001.html>