Re: [Onap-lf-announce] [onap-tsc] [onap-discuss] Gerrit 3.2 Upgrade - Monday Sep 21 1:00PM PT

[TIMONEY, DAN]

I’m getting an error from the LF SSO page when I try to sign in to Gerrit now.

Sent from MyOwn, an AT BYOD solution.

From: "Multanen, Eric W" 
mailto:eric.w.multa...@intel.com>>
Date: Monday, September 21, 2020 at 6:03:07 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org" 
mailto:onap-disc...@lists.onap.org>>
Cc: "onap-release" 
mailto:onap-rele...@lists.onap.org>>, 
"onap-lf-annou...@lists.onap.org" 
mailto:onap-lf-annou...@lists.onap.org>>
Subject: Re: [Onap-lf-announce] [onap-tsc] [onap-discuss] Gerrit 3.2 Upgrade - 
Monday Sep 21 1:00PM PT

I’ve heard a couple reports just now of problems pushing to gerrit – due to: No 
Contributor Agreement on file  …
Has there been a change in this area?

From: onap-tsc@lists.onap.org  On Behalf Of Jessica 
Wagantall
Sent: Monday, September 21, 2020 2:26 PM
To: onap-disc...@lists.onap.org; Jessica Wagantall 

Cc: onap-tsc ; onap-release 
; onap-lf-annou...@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] Gerrit 3.2 Upgrade - Monday Sep 21 
1:00PM PT

This is now completed!

And we are back on track.

Thanks!
Jess

On Mon, Sep 21, 2020 at 2:24 PM Jessica Wagantall via 
lists.onap.org
 
mailto:linuxfoundation@lists.onap.org>>
 wrote:
Hi Team..

We are still working on this migration. If there are no issues we should be 
able to complete soon.

Thanks so much for your patience!
Jess

On Mon, Sep 21, 2020 at 1:12 PM Jessica Wagantall via 
lists.onap.org
 
mailto:linuxfoundation@lists.onap.org>>
 wrote:
Hi Team..

Small reminder.
This maintenance will be happening soon

Thanks!
Jess

On Fri, Sep 18, 2020 at 2:09 PM Jessica Wagantall via 
lists.onap.org
 
mailto:linuxfoundation@lists.onap.org>>
 wrote:
Dear ONAP team.

Gerrit's 3.2 Upgrade will be happening this Monday Sep 21 1:00PM PT time.
Jenkins will be set to shutdown mode and Gerrit will not be available for 1 hr.

Please let me know for any issues.
Will send a notice before this happens

Thanks!
Jess



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7095): https://lists.onap.org/g/onap-tsc/message/7095
Mute This Topic: https://lists.onap.org/mt/77003629/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] Committer Promotion Request for #sdnc

[TIMONEY, DAN]

Catherine,

Thanks!  I’ll make that update.  Also, I need to remove another committer 
(Prabhuram Somasundaram), who has moved on to another company/project, so I’ll 
make that change as well.

Dan

From: "LEFEVRE, CATHERINE" 
Date: Monday, August 10, 2020 at 11:36 AM
To: "TIMONEY, DAN" , "onap-tsc@lists.onap.org" 

Subject: RE: Committer Promotion Request for #sdnc

Good afternoon Dan,

I have reviewed your request.
May I ask you to take an action to remove “Parviz Yegani” based on your 
feedback from the wiki and from the INFO.yaml? Thank you

Looking at the contributions provided by Herbert and Michael, I approve your 
promotion’s requests

Congratulations Herbert & Michael !

Best regards
Catherine

From: "TIMONEY, DAN" mailto:dt5...@att.com>>
Date: Friday, August 7, 2020 at 1:31 PM
To: 
"infrastructure-coordina...@onap.org<mailto:infrastructure-coordina...@onap.org>"
 
mailto:infrastructure-coordina...@onap.org>>
Subject: Committer Promotion Request for #sdnc

The existing active committers on the SDNC project have voted to promote 
Herbert Eiselt and Michael Dürre as a committers on the SDNC project. Herbert 
and Michael have both been strong contributors to the project for several 
releases and we are confident they will make an excellent committers.

Please note that SDNC currently has only 2 active committers (myself and David 
Stilwell), both from AT  Herbert and Michael both work for Highstreet 
Technologies.  Thus, their promotions will allow us to improve our diversity.

The committer promotion requests are on the wiki at :
Herbert:  
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+SDNC+-+Herbert+Eiselt.
Michael: 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+SDNC+-+Michael+Durre

Thank you in advance for your consideration,

Dan Timoney
ONAP SDNC Project Technical Lead


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

View/Reply Online (#6954): https://lists.onap.org/g/onap-tsc/message/6954
Mute This Topic: https://lists.onap.org/mt/76106821/21656
Mute #sdnc: https://lists.onap.org/g/onap+onap-tsc/mutehashtag/sdnc
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] Project maturity review for SDNC update

[TIMONEY, DAN]

TSC, Jason:

I updated the Project Maturity Review page for SDNC to address comments posted:

https://wiki.onap.org/display/DW/Project+Maturity+Review+for+SDNC

This project is currently in “revert” status.  I would appreciate your 
re-review.

Thanks!
Dan Timoney
PTL – ONAP CCSDK and SDNC projects


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

View/Reply Online (#6923): https://lists.onap.org/g/onap-tsc/message/6923
Mute This Topic: https://lists.onap.org/mt/75965015/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-release] [Maintenance Release]Status Update

[TIMONEY, DAN]

Sylvain, all:

I wanted to provide an update on the 2 SDNC issues noted below:

   - July 23th: Issue between SDC and SDNC (we don't see SDNC "ack" the 
reception of distribution) 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-652346521/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D652346521_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwQF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=qsa4LJzl93jRDHAZip-h8GC8aa2g7Es3nx-5XtSzxiE=>).
 I tried to restart but always the same issue
Jira SDNC-1309 (https://jira.onap.org/browse/SDNC-1309) opened for this.
 I didn’t see any reference in the debug.log here to a distribution to SDNC, 
but I did see distributions to CDS.  Is that what you’re referring to?  Or are 
you saying there should have been a distribution that isn’t listed?

   - July 24th: Issue on SDNC (preload data doesn't seems to be here but we 
have a 200 OK when uploading) 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-654306232/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D654306232_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=N5pCbrdUj3HPaq7a8yr2tBwFRWmBrCjPD3Pu1icMZaw=>).
 I tried to restart but always the same issue
Jira SDNC-1308 
(https://jira.onap.org/browse/SDNC-1308) opened for this.
This is most likely a timing issue.  In the OpenDaylight platform, data writes 
occur after the response is returned – so if a GET is done right after a POST, 
it sometimes is not yet found.  This can be corrected via a design change, but 
it is a significant amount of work and this particular API has been deprecated. 
 I believe this is already addressed in GENERIC-RESOURCE-API – which replaces 
VNF-API.  So I would prefer to document this as a known issue in El Alto and 
leave it unresolved.

Thanks!
Dan

From: "TIMONEY, DAN" 
Date: Monday, July 27, 2020 at 10:14 AM
To: "sylvain.desbure...@orange.com" , "Nowak, 
Damian (Nokia - PL/Wroclaw)" , 
"onap-tsc@lists.onap.org" , "LEFEVRE, CATHERINE" 
, "dmcbr...@linuxfoundation.org" 

Cc: "CLOSSET, CHRISTOPHE" , "SONSINO, OFIR" 
, "seshu.kuma...@huawei.com" 
, "onap-rele...@lists.onap.org" 
, DEBEAU Eric TGI/OLN , 
RICHOMME Morgan TGI/OLN , HARDY Thierry TGI/OLN 
, "BONKUR, VENKAT" , "FREEMAN, BRIAN 
D" , RAJEWSKI Lukasz O-PL , 
"SMOKOWSKI, STEVEN" , ELENA KULESHOV , "SHAH, 
SANDEEP" , "TATTAVARADA, SUNDER" , 
"Nowak, Damian (Nokia - PL/Wroclaw)" , Krzysztof 
Opasiak 
Subject: Re: [onap-tsc] [Onap-release] [Maintenance Release]Status Update

Sylvain,

I don’t see Jiras associated with the 2 SDNC issues below.   I’ll create Jiras, 
although I would appreciate in the future if the person reporting the issue 
does so in Jira so it does not get missed in the deluge of emails we all get.

Thanks!
Dan




From: "sylvain.desbure...@orange.com" 
Date: Friday, July 24, 2020 at 3:26 AM
To: "Nowak, Damian (Nokia - PL/Wroclaw)" , 
"onap-tsc@lists.onap.org" , "LEFEVRE, CATHERINE" 
, "dmcbr...@linuxfoundation.org" 

Cc: "CLOSSET, CHRISTOPHE" , "SONSINO, OFIR" 
, "TIMONEY, DAN" , 
"seshu.kuma...@huawei.com" , 
"onap-rele...@lists.onap.org" , DEBEAU Eric 
TGI/OLN , RICHOMME Morgan TGI/OLN 
, HARDY Thierry TGI/OLN , 
"BONKUR, VENKAT" , "FREEMAN, BRIAN D" , 
RAJEWSKI Lukasz O-PL , "SMOKOWSKI, STEVEN" 
, ELENA KULESHOV , "SHAH, SANDEEP" 
, "TATTAVARADA, SUNDER" , "Nowak, 
Damian (Nokia - PL/Wroclaw)" , Krzysztof Opasiak 

Subject: RE:[onap-tsc] [Onap-release] [Maintenance Release]Status Update

Hello,
here's a quick report on last attempts on El Alto

* A fix for Portal issue has been delivered and merged. We'll see on next 
dailies if it works (knowing that I'm OOO today and Morgan is back August 3rd)
* e2e instanciation issues:
- July 17th, 18th, 20th and 21th: issue on SO openstack adapter 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-648089267/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D648089267_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=KeYqnRR8LJK_Js8S-TXVLwdj_a-mpl1UaOoq6HDqQVE=>)
 --> partial logs sent to SO team but I forgot to retrieve the full logs :(
- July

[onap-tsc] 2020 CCSDK PTL Election

[TIMONEY, DAN]

TSC,

It is my pleasure to inform you that the annual election for CCSDK PTL has 
completed and I have been elected to another term as CCSDK PTL.  I’ve updated 
the Votiing Results History wiki page 
(https://wiki.onap.org/display/DW/Voting+Results+History) accordingly.

Thank you, as always, for your support!

Dan Timoney

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

View/Reply Online (#6901): https://lists.onap.org/g/onap-tsc/message/6901
Mute This Topic: https://lists.onap.org/mt/75849046/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-release] [Maintenance Release]Status Update

[TIMONEY, DAN]

Sylvain,

I don’t see Jiras associated with the 2 SDNC issues below.   I’ll create Jiras, 
although I would appreciate in the future if the person reporting the issue 
does so in Jira so it does not get missed in the deluge of emails we all get.

Thanks!
Dan




From: "sylvain.desbure...@orange.com" 
Date: Friday, July 24, 2020 at 3:26 AM
To: "Nowak, Damian (Nokia - PL/Wroclaw)" , 
"onap-tsc@lists.onap.org" , "LEFEVRE, CATHERINE" 
, "dmcbr...@linuxfoundation.org" 

Cc: "CLOSSET, CHRISTOPHE" , "SONSINO, OFIR" 
, "TIMONEY, DAN" , 
"seshu.kuma...@huawei.com" , 
"onap-rele...@lists.onap.org" , DEBEAU Eric 
TGI/OLN , RICHOMME Morgan TGI/OLN 
, HARDY Thierry TGI/OLN , 
"BONKUR, VENKAT" , "FREEMAN, BRIAN D" , 
RAJEWSKI Lukasz O-PL , "SMOKOWSKI, STEVEN" 
, ELENA KULESHOV , "SHAH, SANDEEP" 
, "TATTAVARADA, SUNDER" , "Nowak, 
Damian (Nokia - PL/Wroclaw)" , Krzysztof Opasiak 

Subject: RE:[onap-tsc] [Onap-release] [Maintenance Release]Status Update

Hello,
here's a quick report on last attempts on El Alto

* A fix for Portal issue has been delivered and merged. We'll see on next 
dailies if it works (knowing that I'm OOO today and Morgan is back August 3rd)
* e2e instanciation issues:
- July 17th, 18th, 20th and 21th: issue on SO openstack adapter 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-648089267/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D648089267_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=KeYqnRR8LJK_Js8S-TXVLwdj_a-mpl1UaOoq6HDqQVE=>)
 --> partial logs sent to SO team but I forgot to retrieve the full logs :(
- July 22th: issue on SDC onboarding 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-650005168/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D650005168_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwQF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=dk7ufN9Tk3Jyj-N8GbHZ9B9c5-D_MvPOObniawf7UkE=>).
 I tried to restart but always the same issue
   - July 23th: Issue between SDC and SDNC (we don't see SDNC "ack" the 
reception of distribution) 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-652346521/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D652346521_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwQF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=qsa4LJzl93jRDHAZip-h8GC8aa2g7Es3nx-5XtSzxiE=>).
 I tried to restart but always the same issue
   - July 24th: Issue on SDNC (preload data doesn't seems to be here but we 
have a 200 OK when uploading) 
(https://gating-results.onap.eu/results/onap_daily_pod4_elalto-654306232/smoke-usecases/basic_vm/xtesting.debug.log<https://urldefense.proofpoint.com/v2/url?u=https-3A__gating-2Dresults.onap.eu_results_onap-5Fdaily-5Fpod4-5Felalto-2D654306232_smoke-2Dusecases_basic-5Fvm_xtesting.debug.log=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=mWnyDvuPV2dJXBxM-f7vJEwiUlXn6Kf03eRbshtDKvw=N5pCbrdUj3HPaq7a8yr2tBwFRWmBrCjPD3Pu1icMZaw=>).
 I tried to restart but always the same issue

So e2e tests are quite buggy and fails at different steps, making it hard to 
debug.

Regards,
Sylvain


De : Nowak, Damian (Nokia - PL/Wroclaw) [damian.no...@nokia.com]
Envoyé : mercredi 22 juillet 2020 17:08
À : onap-tsc@lists.onap.org; onap-rele...@lists.onap.org; DESBUREAUX Sylvain 
TGI/OLN; sylvain.desbureaux+...@gmail.com
Cc : onap-...@lists.onap.org
Objet : RE: [onap-tsc] [Onap-release] [Maintenance Release]Status Update
Dears,

Regarding the El Alto Maintenance Release, well, it`s definitely not ready…
We`re observing the following issues in our test environment:

1.   Portal is not responding to requests (we see it is unable to load 
externally defined roles to the internal Portal DB).
We reinstalled Portal from the 5.0.1-ONAP tag, and the issue is resolved --> 
Means EL Alto MR Portal comes with a Bug.

2.   APPC is not really working properly in El Alto MR (checked-out 
2020-07-22).
It looks like APPC is not really responding to calls from CDT, and it is not 
responding to calls from Swagger API UI.

Are You observing these issues in Your test-systems too?
I can understand, that not everyone is using APPC, but I think, quite anyone is 
using Portal…

Rgds,
Damian
http://nok.it/onap<https://urldefense.proofpoint.com/v2/url?u=http-3A__nok.it_onap=DwMF-g=L

[onap-tsc] CCSDK PTL 2020 Election

[TIMONEY, DAN]

CCSDK PTL committers,

You should have received an email with Subject line “Poll: CCSDK PTL Election 
2020” for this year’s PTL election.  I’m the only candidate running, but the 
ONAP rules still require a formal election.  Please vote by COB next Tuesday 
7/28.

Thanks!
Dan

From: "TIMONEY, DAN" 
Date: Friday, July 17, 2020 at 4:17 PM
To: "LUCAS, JACK" , "HU, JUN NICOLAS" 
, "gaurav.agra...@huawei.com" , 
"brindasa...@in.ibm.com" , "SMOKOWSKI, KEVIN" 
, "kaggar...@in.ibm.com" 
Cc: "onap-tsc@lists.onap.org" 
Subject: Re: [ccsdk] Call for nominations for CCSDK PTL 2020

CCSDK committers,

I would like to nominate myself for the position of CCSDK PTL.

I has been my honor to serve as CCSDK PTL for the past 3 years and I look 
forward to continuing to build on the excellent work this community has 
achieved!

Thank you for your consideration,

Dan

From: "TIMONEY, DAN" 
Date: Friday, July 17, 2020 at 4:13 PM
To: "LUCAS, JACK" , "HU, JUN NICOLAS" 
, "gaurav.agra...@huawei.com" , 
"brindasa...@in.ibm.com" , "SMOKOWSKI, KEVIN" 
, "kaggar...@in.ibm.com" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [ccsdk] Call for nominations for CCSDK PTL 2020

CCSDK committers,

It is time for our annual PTL election.

The process is described on the ONAP wiki page at the following link:

https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Please reply to this email If you would like to self-nominate.  Nominations are 
due by 5 PM EDT on Tuesday, July 21.

Thanks!
Dan

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

View/Reply Online (#6884): https://lists.onap.org/g/onap-tsc/message/6884
Mute This Topic: https://lists.onap.org/mt/75751811/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] [sdnc] Call for nominations for SDNC PTL

[TIMONEY, DAN]

SDNC committers,

I would like to nominate myself for the position of SDNC PTL.

I has been my honor to serve as SDNC PTL for the past 3 years and I look 
forward to continuing to build on the excellent work this community has 
achieved!

Thank you for your consideration,

Dan


From: "TIMONEY, DAN" 
Date: Friday, July 17, 2020 at 4:19 PM
To: DAVE STILWELL , "SOMASUNDARAM, PRABHURAM" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [sdnc] Call for nominations for SDNC PTL

SDNC committers,

It is time for our annual PTL election.

The process is described on the ONAP wiki page at the following link:

https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Please reply to this email If you would like to self-nominate.  Nominations are 
due by 5 PM EDT on Tuesday, July 21.

Thanks!
Dan


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

View/Reply Online (#6802): https://lists.onap.org/g/onap-tsc/message/6802
Mute This Topic: https://lists.onap.org/mt/75620551/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] [sdnc] Call for nominations for SDNC PTL

[TIMONEY, DAN]

SDNC committers,

It is time for our annual PTL election.

The process is described on the ONAP wiki page at the following link:

https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Please reply to this email If you would like to self-nominate.  Nominations are 
due by 5 PM EDT on Tuesday, July 21.

Thanks!
Dan


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

View/Reply Online (#6801): https://lists.onap.org/g/onap-tsc/message/6801
Mute This Topic: https://lists.onap.org/mt/75620551/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] [ccsdk] Call for nominations for CCSDK PTL 2020

[TIMONEY, DAN]

CCSDK committers,

I would like to nominate myself for the position of CCSDK PTL.

I has been my honor to serve as CCSDK PTL for the past 3 years and I look 
forward to continuing to build on the excellent work this community has 
achieved!

Thank you for your consideration,

Dan

From: "TIMONEY, DAN" 
Date: Friday, July 17, 2020 at 4:13 PM
To: "LUCAS, JACK" , "HU, JUN NICOLAS" 
, "gaurav.agra...@huawei.com" , 
"brindasa...@in.ibm.com" , "SMOKOWSKI, KEVIN" 
, "kaggar...@in.ibm.com" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [ccsdk] Call for nominations for CCSDK PTL 2020

CCSDK committers,

It is time for our annual PTL election.

The process is described on the ONAP wiki page at the following link:

https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Please reply to this email If you would like to self-nominate.  Nominations are 
due by 5 PM EDT on Tuesday, July 21.

Thanks!
Dan

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

View/Reply Online (#6800): https://lists.onap.org/g/onap-tsc/message/6800
Mute This Topic: https://lists.onap.org/mt/75620465/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] [ccsdk] Call for nominations for CCSDK PTL 2020

[TIMONEY, DAN]

CCSDK committers,

It is time for our annual PTL election.

The process is described on the ONAP wiki page at the following link:

https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Please reply to this email If you would like to self-nominate.  Nominations are 
due by 5 PM EDT on Tuesday, July 21.

Thanks!
Dan

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

View/Reply Online (#6799): https://lists.onap.org/g/onap-tsc/message/6799
Mute This Topic: https://lists.onap.org/mt/75620465/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-ptl] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

[TIMONEY, DAN]

David,

I actually replied to that other thread (see attached) with a link to the Jira 
query listing the CCSDK and SDNC Jira tickets for the El Alto and Frankfurt 
maintenance releases.  There are quite a few fixes for CDS that we were asked 
by downstream users to include in El Alto so they could ingest them in their 
deployments – so yes, we would like to include those.  I went through all the 
changes merged to our El Alto branch since the release and made sure that all 
the associated Jiras are tagged appropriately – so that should be a complete 
list.

Dan

From:  on behalf of David McBride 

Reply-To: "onap-...@lists.onap.org" , 
"dmcbr...@linuxfoundation.org" 
Date: Wednesday, July 15, 2020 at 4:40 PM
To: Krzysztof Opasiak 
Cc: "TIMONEY, DAN" , "sylvain.desbure...@orange.com" 
, "LEFEVRE, CATHERINE" 
, "LUCAS, JACK" , 
"HERNANDEZ-HERRERO, JORGE" , "fiachra.corco...@est.tech" 
, "marek.szwalkiew...@external.t-mobile.pl" 
, "LUNANUOVA, DOMINIC" 
, "DETERME, SEBASTIEN" , 
"PARTHASARATHY, RAMESH" , "seshu.kuma...@huawei.com" 
, "DRAGOSH, PAM" , 
"SONSINO, OFIR" , "MALAKOV, YURIY" , 
"onap-...@lists.onap.org" , "onap-tsc@lists.onap.org" 
, DEBEAU Eric TGI/OLN , 
RICHOMME Morgan TGI/OLN 
Subject: Re: [onap-ptl] [ONAP][Maintenance Releases] What's onboarded from an 
OOM point of view

Dan,

In particular, there are about 24 CCSDK issues that are planned for the El Alto 
maintenance release that I didn't see in Sylvain's list (see Matched tab).  
Please let me know whether those should be included, or not.

David

On Wed, Jul 15, 2020 at 1:36 PM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Thanks for starting this thread.  I'd like to use this discussion to reconcile 
the different views on the content of the maintenance releases.

I took all of the Jira issues referenced in this thread and put them into two 
spreadsheets; one for El Alto, and one for Frankfurt.  Each spreadsheet has two 
tabs:  "Matched" and "Not Matched". All of the issues in Jira that are labeled 
for the maintenance release are shown in the left hand column on the "Matched" 
tab.  In the columns to the right are where the labeled issues in Jira match 
with an issue cited by one of you.

The "Not Matched" tab shows issues that one of you cited, that are not 
currently labeled for the maintenance release.

I'm happy to take all of the "Not Matched" issues and apply the maintenance 
release label to them, en masse.

What I would like for you to do is to look at the issues in the left-hand 
column on the "Matched" tab, that are not matched by an issue in this email, 
and consider whether they should be included, or excluded.

David

On Wed, Jul 15, 2020 at 11:25 AM Krzysztof Opasiak 
mailto:k.opas...@samsung.com>> wrote:


On 15.07.2020 20:08, TIMONEY, DAN wrote:
> Krzysztof,
>
> For Guilin, instead of certInitializer, how about if we change dgbuilder to 
> use http instead of https and use it as a trial for using an ingress 
> controller instead of a node port?  Since dgbuilder is a design time tool 
> primarily, it's pretty isolated and low risk- and then we'll have one less 
> cert to have to worry about maintaining.

Well as long as it is exposed to the outside world it should be https.
So we can either:

1) Change its type to ClusterIP if doesn't have to be exposed.
2) Keep it https;)

>
> For Frankfurt, could we cherry pick that same change?   If so, I'm happy to 
> make that a priority if you can provide some pointers on how to switch from 
> using a node port to ingress controller for the dgbuilder service, and then I 
> can make that change once the right way.

Actually there is nothing to do from OOM perspective apart from enabling
ingress;)

All the ingress configuration (with SSL passthrough) is already there.
The only thing that you need to do is to make sure that dgbuilder can
actually work with ingress which means that there is no hardcoded urls etc

>  Otherwise, I'm happy to install those certs in the Frankfurt branch like 
> Sylvain did for us for the CDS py-executor pod recently.

That's exactly what I've been talking about:)

>
>
> Dan
>
> -Original Message-
> From: Krzysztof Opasiak mailto:k.opas...@samsung.com>>
> Sent: Wednesday, July 15, 2020 12:25 PM
> To: TIMONEY, DAN mailto:dt5...@att.com>>; 
> sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>; 
> dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; LEFEVRE, 
> CATHERINE 
> mailto:catherine.lefe...@intl.att.com>>
> Cc: LUCAS, JACK mailto:jflu...@research.att.com>>; 
> HERNANDEZ-HERRERO, JORGE mailto:jh1...@att.com>>; 
>

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

[TIMONEY, DAN]

Krzysztof,

For Guilin, instead of certInitializer, how about if we change dgbuilder to use 
http instead of https and use it as a trial for using an ingress controller 
instead of a node port?  Since dgbuilder is a design time tool primarily, it's 
pretty isolated and low risk- and then we'll have one less cert to have to 
worry about maintaining.

For Frankfurt, could we cherry pick that same change?   If so, I'm happy to 
make that a priority if you can provide some pointers on how to switch from 
using a node port to ingress controller for the dgbuilder service, and then I 
can make that change once the right way.  Otherwise, I'm happy to install those 
certs in the Frankfurt branch like Sylvain did for us for the CDS py-executor 
pod recently.


Dan

-Original Message-
From: Krzysztof Opasiak  
Sent: Wednesday, July 15, 2020 12:25 PM
To: TIMONEY, DAN ; sylvain.desbure...@orange.com; 
dmcbr...@linuxfoundation.org; LEFEVRE, CATHERINE 

Cc: LUCAS, JACK ; HERNANDEZ-HERRERO, JORGE 
; fiachra.corco...@est.tech; 
marek.szwalkiew...@external.t-mobile.pl; LUNANUOVA, DOMINIC 
; DETERME, SEBASTIEN ; 
PARTHASARATHY, RAMESH ; seshu.kuma...@huawei.com; DRAGOSH, PAM 
; SONSINO, OFIR ; 
MALAKOV, YURIY ; onap-...@lists.onap.org; 
onap-tsc@lists.onap.org; DEBEAU Eric TGI/OLN ; RICHOMME 
Morgan TGI/OLN 
Subject: Re: [ONAP][Maintenance Releases] What's onboarded from an OOM point of 
view



On 15.07.2020 15:04, TIMONEY, DAN wrote:
> David, Sylvain, Catherine:
> 
> The changes in CCSDK and SDNC for the Frankfurt maintenance release are 
> marked in the ONAP jira with the frankfurt_maintenance_release_1 tag.  I 
> created a shared query for (hopefully) easy reference:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_issues_-3Ffilter-3D12419=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI=4Nul3p0kn2KxOXVCPL4xVGlFlrWpt3VNRgPDCAQYSII=
>   
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D74340a1b-2D29aff678-2D74358154-2D0cc47a31cdbc-2D22b3eeadf7f1f882-26q-3D1-26u-3Dhttps-253A-252F-252Fjira.onap.org-252Fissues-252F-253Ffilter-253D12419=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI=QDGPcOWtfGOeizUdcir51R5V1Yc3oEwQPIgQOmM9ixU=
>  >
> 
> The changes in CCSDK and SDNC for the El Alto maintenance release are 
> also marked in the ONAP Jira, with the El_Alto_Maintenance_1 tag.  I 
> created a shared query for that one as well:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_issues_-3Ffilter-3D12418=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI=AbrzXZdr8B95ujLKCzkdAmOjJogP8TItzzNc80ld9tM=
>   
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3Db340f9b6-2Deedb05d5-2Db34172f9-2D0cc47a31cdbc-2Dac7d3148487fbdee-26q-3D1-26u-3Dhttps-253A-252F-252Fjira.onap.org-252Fissues-252F-253Ffilter-253D12418=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI=PRLrhmi-d8XFKWM7Z770hrjID117o1AXW6cuOs9WDB8=
>  >
> 
> There are 2 new issues in that list that I added in order to address the 
> expired certificate in dgbuilder that Morgan brought to our attention 
> (thanks for that!).  I’m in the process of creating a new docker to 
> address that issue and would like to include that in this maintenance 
> release if we can.

El Alto - I'm fine with docker

Frankfurt - would be great to have it in OOM repo instead

master - use certInitializer

> 
> Thanks!
> 
> Dan
> 
> *From: *"sylvain.desbure...@orange.com" 
> *Date: *Friday, July 10, 2020 at 5:17 AM
> *To: *"dmcbr...@linuxfoundation.org" , 
> "LEFEVRE, CATHERINE" 
> *Cc: *"LUCAS, JACK" , "HERNANDEZ-HERRERO, 
> JORGE" , "fiachra.corco...@est.tech" 
> , "marek.szwalkiew...@external.t-mobile.pl" 
> , "LUNANUOVA, DOMINIC" 
> , "DETERME, SEBASTIEN" 
> , "PARTHASARATHY, RAMESH" 
> , "seshu.kuma...@huawei.com" , 
> "TIMONEY, DAN" , "DRAGOSH, PAM" 
> , "SONSINO, OFIR" 
> , "MALAKOV, YURIY" , 
> "onap-...@lists.onap.org" , 
> "onap-tsc@lists.onap.org" , DEBEAU Eric TGI/OLN 
> , RICHOMME Morgan TGI/OLN 
> , Krzysztof Opasiak 
> *Subject: *[ONAP][Maintenance Releases] What's onboarded from an OOM 
> point of view
> 
> Hi David and Catherine,
> 
> Following yesterday's call, here's what I see from OOM code point of 
> view on our maintenance releases.
> It's my view as of today, we may see new merge request coming, 
> especially for the (not announced) Frankfurt Maintenance Release.
> 
> # El Alto
> 
> 24 commits have (will for 2)

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

[TIMONEY, DAN]

David, Sylvain, Catherine:

The changes in CCSDK and SDNC for the Frankfurt maintenance release are marked 
in the ONAP jira with the frankfurt_maintenance_release_1 tag.  I created a 
shared query for (hopefully) easy reference:

https://jira.onap.org/issues/?filter=12419


The changes in CCSDK and SDNC for the El Alto maintenance release are also 
marked in the ONAP Jira, with the El_Alto_Maintenance_1 tag.  I created a 
shared query for that one as well:
https://jira.onap.org/issues/?filter=12418

There are 2 new issues in that list that I added in order to address the 
expired certificate in dgbuilder that Morgan brought to our attention (thanks 
for that!).  I’m in the process of creating a new docker to address that issue 
and would like to include that in this maintenance release if we can.

Thanks!
Dan


From: "sylvain.desbure...@orange.com" 
Date: Friday, July 10, 2020 at 5:17 AM
To: "dmcbr...@linuxfoundation.org" , "LEFEVRE, 
CATHERINE" 
Cc: "LUCAS, JACK" , "HERNANDEZ-HERRERO, JORGE" 
, "fiachra.corco...@est.tech" , 
"marek.szwalkiew...@external.t-mobile.pl" 
, "LUNANUOVA, DOMINIC" 
, "DETERME, SEBASTIEN" , 
"PARTHASARATHY, RAMESH" , "seshu.kuma...@huawei.com" 
, "TIMONEY, DAN" , "DRAGOSH, PAM" 
, "SONSINO, OFIR" , 
"MALAKOV, YURIY" , "onap-...@lists.onap.org" 
, "onap-tsc@lists.onap.org" , 
DEBEAU Eric TGI/OLN , RICHOMME Morgan TGI/OLN 
, Krzysztof Opasiak 
Subject: [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Hi David and Catherine,

Following yesterday's call, here's what I see from OOM code point of view on 
our maintenance releases.
It's my view as of today, we may see new merge request coming, especially for 
the (not announced) Frankfurt Maintenance Release.

# El Alto

24 commits have (will for 2) been applied to El Alto branch since last 
maintenance release:

The following commits include code change in parent repo, so digging between 
the two release is needed in order to know
what changed:
* Update policy brmsgw to point to latest versions (POLICY-2171)
  BRMS_DEPENDENCY_VERSION: 1.4.2 -> 1.5.3
  BRMS_MODELS_DEPENDENCY_VERSION: 2.0.2 -> 2.1.4
* [DMaaP DR] New certs fro ElAlto images (DMAAP-1421)
  onap/dmaap/datarouter-node: 2.1.2 -> 2.2.0
  onap/dmaap/datarouter-prov: 2.1.2 -> 2.2.0
* Update DCAE certs for El Alto (DCAEGEN2-2206)
  onap/org.onap.dcaegen2.deployments.tls-init-container: 1.0.3 -> 1.0.4
* Update CDS image version for elalto to 0.6.5 (OOM-2336)
  onap/ccsdk-blueprintsprocessor: 0.6.3 -> 0.6.5
  onap/ccsdk-commandexecutor: 0.6.3 -> 0.6.5
  onap/ccsdk-sdclistener: 0.6.3 -> 0.6.5
  onap/ccsdk-cds-ui-server: 0.6.3 -> 0.6.5
* [POLICY] new elato images (POLICY-2519)
  onap/policy-pe: 1.5.2 -> 1.5.3
  onap/policy-pdpd-cl: 1.5.3 -> 1.5.4
  onap/policy-apex-pdp: 2.2.2 -> 2.2.3
  onap/policy-api: 2.1.2 -> 2.1.3
  onap/policy-distribution: 2.2.1 -> 2.2.2
  onap/policy-pap: 2.1.2 -> 2.1.3
  onap/policy-xacml-pdp: 2.1.2 -> 2.1.3
* use new image with updated certs (DMAAP-1424)
  onap/dmaap/dmaap-bc: 1.1.5 -> 1.1.9
  onap/dmaap/dbc-client: 1.0.9 -> 1.1.9
* [SDC] Update sdc images for ElAlto (SDC-3199) (*** NOT YET MERGED ***)
  onap/sdc-backend: 1.5.2 -> 1.5.3
  onap/sdc-backend-init: 1.5.2 -> 1.5.3
  onap/sdc-cassandra: 1.5.2 -> 1.5.3
  onap/sdc-cassandra-init: 1.5.2 -> 1.5.3
  onap/dcae-be: 1.3.2 -> 1.3.2-1
  onap/dcae-tools: 1.3.2 -> 1.3.2-1
  onap/dcae-dt: 1.3.2 -> 1.3.2-1
  onap/dcae-fe: 1.3.2 -> 1.3.2-1
  onap/sdc-elasticsearch: 1.5.2 -> 1.5.3
  onap/sdc-init-elasticsearch: 1.5.2 -> 1.5.3
  onap/sdc-frontend: 1.5.2 -> 1.5.3
  onap/sdc-kibana: 1.5.2 -> 1.5.3
  onap/sdc-onboard-backend: 1.5.2 -> 1.5.3
  onap/sdc-onboard-cassandra-init: 1.5.2 -> 1.5.3

These are "OOM only" (change in helm charts, no new images):
* Fixing missing apiVersion in etcd chart (OOM-2156)
* NBI to SDC: API is HTTPS with port 8443 (EXTAPI-341)
* VNFM-adapter health check failing (SO-2517)
* Fix the deployment issue (CLAMP-551)
* docs: Replace include directives for non existent file (OOM-2203)
* docs: Ensure literalinclude directive rendering (OOM-1612)
* Type in deployment.yaml forf cds-ui branch:elAlto (CCSDK-1953)
* Fix multicloud log message output issue (MULTICLOUD-966)
* update cert using secrets (DMAAP-1422)
* fix for the expiring cert (DMAAP-1438)
* [DMaaP] Remove "BOM" Character (OOM-2364)
* [GENERIC] follow elalto branches for submodules (OOM-2364)
* [AAI|ROBOT] track latest commits on submodules (OOM-2364)
* Workaround for cert expiration (DMAAP-1424)
* Portal certificate renewal (PORTAL-878)
* Fix: make all - returns multiple warnings (OOM-2412)
* deploy.sh does not work on Mac os x because untar directory is create… 
(OOM-2407)
* [COMMON] Align Makefile with last changes (OOM-2412)
* 

[onap-tsc] Request for new CCSDK repository ccsdk/oran

[TIMONEY, DAN]

The CCSDK project requests permission to create a new repository for work that 
is being done within the CCSDK project that must align with the O-RAN 
community’s deliverable schedule.  I have updated the ONAP Releases and 
Repositories page (https://wiki.onap.org/display/DW/Resources+and+Repositories) 
with this new repository and documented the need, and have marked the requested 
row in green.

The team would appreciate your prompt attention on this matter, as they have 
code contributions they are anxious to commit.

Thank you for your help!
Dan Timoney
PTL – CCSDK


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

View/Reply Online (#6759): https://lists.onap.org/g/onap-tsc/message/6759
Mute This Topic: https://lists.onap.org/mt/75503179/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] Project maturity review for SDNC

[TIMONEY, DAN]

TSC,

I would like to present the SDNC project maturity review materials for your 
review :
https://wiki.onap.org/display/DW/Project+Maturity+Review+for+SDNC?src=contextnavpagetreemode

Thank you for your consideration,
Dan

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

View/Reply Online (#6724): https://lists.onap.org/g/onap-tsc/message/6724
Mute This Topic: https://lists.onap.org/mt/75383134/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] Project maturity review CCSDK

[TIMONEY, DAN]

TSC,

I would like to present the project maturity review material for CCSDK for your 
review at the following URL :
https://wiki.onap.org/display/DW/Project+Maturity+Review+for+CCSDK

Thank you for your consideration,
Dan

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

View/Reply Online (#6722): https://lists.onap.org/g/onap-tsc/message/6722
Mute This Topic: https://lists.onap.org/mt/75382765/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] Approval needed for new repository creation

[TIMONEY, DAN]

TSC,

On last week’s TSC meeting, one of the topics discussed in the “Administrative 
Pains” section was a proposal to allow PTLs to request repo creation without 
requiring approval.  On our PTL call this week, this topic was also discussed.

I wanted to clarify whether the TSC has approved this change, or whether we are 
still required to get approval from the ONAP infrastructure coordinator for new 
repo creation.  I need to create a new repository ccsdk/oran  for ORAN related 
work in CCSDK – which must be aligned with the ORAN schedule (and thus would 
benefit from being released separately).

Thanks!
Dan


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

View/Reply Online (#6721): https://lists.onap.org/g/onap-tsc/message/6721
Mute This Topic: https://lists.onap.org/mt/75382215/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-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

[TIMONEY, DAN]

Eric,

Thanks for that feedback!

Let me discuss with your concerns with the CDS team and come back with a plan 
to make sure we’re being as transparent as possible.

Thanks!

Dan

From:  on behalf of "Eric Debeau via lists.onap.org" 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, July 1, 2020 at 4:40 PM
To: "onap-tsc@lists.onap.org" , 
"onap-...@lists.onap.org" , 
"dmcbr...@linuxfoundation.org" 
Cc: Kenny Paul 
Subject: Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 
9 #guilin

Hello

CDS has not a good visibility. CDS is not described in the Architecture figure 
as an example.
We believe that CDS will take a more important role in the coming releases. 
There is more and more PoD deployed for CDS and we should have more Health 
Check dedicated to CDS for example.

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de TIMONEY, 
DAN [dtimo...@att.com]
Envoyé : mercredi 1 juillet 2020 18:14
À : onap-...@lists.onap.org; dmcbr...@linuxfoundation.org; onap-tsc
Cc : Kenny Paul
Objet : Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 
#guilin
Eric,

I’m not sure I understand your ask to track CDS as a separate project.  As you 
know, CDS is part of CCSDK.   Can you please say a little more about what you 
had in mind?

Dan



From:  on behalf of David McBride 

Reply-To: "onap-...@lists.onap.org" , 
"dmcbr...@linuxfoundation.org" 
Date: Wednesday, July 1, 2020 at 10:59 AM
To: onap-tsc 
Cc: "onap-...@lists.onap.org" , Kenny Paul 

Subject: Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 
9 #guilin

Hi Eric,

I received feedback during the Frankfurt release that many of the "standard" 
release management tasks are not applicable to OOM and INT.  I'm trying to do a 
limited amount of customization of the tasks to ensure that the tasks are 
meaningful to the projects that they are assigned to.  If you could review the 
M1 tasks and let me know which you believe are applicable to OOM and INT, I 
would be happy to generate the issues and track status.  Thanks.

David

On Tue, Jun 30, 2020 at 11:40 PM Eric Debeau via 
lists.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.onap.org=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=3iMe5LrAmPH95HS6qeK7GKQsUa5Ej6kQ8oB3mAFSn_M=u21xDaekPZG17IEAFXe5xtzy6r7BBgWSruCk8b39zbc=>
 mailto:orange@lists.onap.org>> 
wrote:
Hi David

I notice that some projects are not tracked (Documentation, Integration, OOM) 
while other are still there (Logging)

We should also consider CDS as a separate project.

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] de la part de David 
McBride [dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
Envoyé : mercredi 1 juillet 2020 01:25
À : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc : onap-tsc; Kenny Paul
Objet : [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin
Team,

In reviewing the Guilin Milestone 
Status<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_x_FboLBQ=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=3iMe5LrAmPH95HS6qeK7GKQsUa5Ej6kQ8oB3mAFSn_M=lNfC_payfzzA1Hv_sN-msT7FUtnSqB6nJv5X9mYUQUc=>,
 I was startled to see that 18/26 projects tracked still have 7+ of their 8 
milestone tasks still in the Open state (see attachment), with just 9 days to 
go until M1!

Please get started with your project milestone tasks ASAP.  Remember that the 
Guilin release has a short schedule of just 4 months.  We need to hit our 
milestone dates in order to stay on track.

If you are blocked for some reason, or need help, please let me or Catherine 
know.

Thanks

David

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

_



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 

Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

[TIMONEY, DAN]

Eric,

I’m not sure I understand your ask to track CDS as a separate project.  As you 
know, CDS is part of CCSDK.   Can you please say a little more about what you 
had in mind?

Dan



From:  on behalf of David McBride 

Reply-To: "onap-...@lists.onap.org" , 
"dmcbr...@linuxfoundation.org" 
Date: Wednesday, July 1, 2020 at 10:59 AM
To: onap-tsc 
Cc: "onap-...@lists.onap.org" , Kenny Paul 

Subject: Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 
9 #guilin

Hi Eric,

I received feedback during the Frankfurt release that many of the "standard" 
release management tasks are not applicable to OOM and INT.  I'm trying to do a 
limited amount of customization of the tasks to ensure that the tasks are 
meaningful to the projects that they are assigned to.  If you could review the 
M1 tasks and let me know which you believe are applicable to OOM and INT, I 
would be happy to generate the issues and track status.  Thanks.

David

On Tue, Jun 30, 2020 at 11:40 PM Eric Debeau via 
lists.onap.org
 mailto:orange@lists.onap.org>> 
wrote:
Hi David

I notice that some projects are not tracked (Documentation, Integration, OOM) 
while other are still there (Logging)

We should also consider CDS as a separate project.

Best Regards

Eric

De : onap-tsc@lists.onap.org 
[onap-tsc@lists.onap.org] de la part de David 
McBride [dmcbr...@linuxfoundation.org]
Envoyé : mercredi 1 juillet 2020 01:25
À : onap-...@lists.onap.org
Cc : onap-tsc; Kenny Paul
Objet : [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin
Team,

In reviewing the Guilin Milestone 
Status,
 I was startled to see that 18/26 projects tracked still have 7+ of their 8 
milestone tasks still in the Open state (see attachment), with just 9 days to 
go until M1!

Please get started with your project milestone tasks ASAP.  Remember that the 
Guilin release has a short schedule of just 4 months.  We need to hit our 
milestone dates in order to stay on track.

If you are blocked for some reason, or need help, please let me or Catherine 
know.

Thanks

David

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

_



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.


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


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

View/Reply Online (#6639): https://lists.onap.org/g/onap-tsc/message/6639
Mute This Topic: https://lists.onap.org/mt/75238995/21656
Mute #guilin: https://lists.onap.org/g/onap+onap-tsc/mutehashtag/guilin
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-ptl] [ONAP] [Frankfurt] Integration status for RC2

[TIMONEY, DAN]

Morgan,

I see that my change to Frankfurt was merged last night (thanks, OOM team!).

Dan

From:  on behalf of "Morgan Richomme via 
lists.onap.org" 
Reply-To: "onap-tsc@lists.onap.org" 
Date: Tuesday, June 2, 2020 at 2:35 AM
To: "onap-tsc@lists.onap.org" , 
"onap-...@lists.onap.org" , David McBride 
, "LEFEVRE, CATHERINE" 

Cc: Krzysztof Opasiak , "ZWARICO, AMY" , 
'Pawel Pawlak' , David Perez Caparros 

Subject: Re: [onap-tsc] [onap-ptl] [ONAP] [Frankfurt] Integration status for RC2

Hi Dan

thanks for clarification
so just wait for Frankfurt merge and it should be OK
I moved both JIRA to DELIVERED (merged in Master) and will close them as soon 
as they are merged in Frankfurt

/Morgan



De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de TIMONEY, 
DAN [dtimo...@att.com]
Envoyé : lundi 1 juin 2020 13:40
À : onap-...@lists.onap.org; RICHOMME Morgan TGI/OLN; David McBride; LEFEVRE, 
CATHERINE
Cc : onap-tsc@lists.onap.org; Krzysztof Opasiak; ZWARICO, AMY; 'Pawel Pawlak'; 
David Perez Caparros
Objet : Re: [onap-tsc] [onap-ptl] [ONAP] [Frankfurt] Integration status for RC2
Morgan,

The change you referenced below ( 

We did create RC2 versions for the parts of CCSDK and SDNC that changed since 
RC1 and updated the master branch of OOM with the corresponding version numbers 
(see 
 
https://gerrit.onap.org/r/c/oom/+/108346<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_c_oom_-2B_108346=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=j0hegKYxjT_l0mjIWay2PqSKb_XuYY9CHJQLZxjx8h4=zJ99qHV47hCVsb1higYy7Cr7OqHyzjc5WZn4F3qM5X0=>).
  Note that the OOM team has asked that we NOT push to frankfurt directly but 
rather that we update master.  It was my understanding that the OOM team had 
taken responsibility for cherry-picking changes to frankfurt after merging to 
master, but it appears I was mistaken. I  just cherry picked that change to 
their frankfurt branch.

FYI – the  CCSDK release notes and SDNC release notes  each contain a table 
with the correct released versions for our dockers.   Please see:

CCSDK release notes : 
https://onap-doc.readthedocs.io/projects/onap-ccsdk-distribution/en/latest/release-notes.html#dockercontainers<https://urldefense.proofpoint.com/v2/url?u=https-3A__onap-2Ddoc.readthedocs.io_projects_onap-2Dccsdk-2Ddistribution_en_latest_release-2Dnotes.html-23dockercontainers=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=j0hegKYxjT_l0mjIWay2PqSKb_XuYY9CHJQLZxjx8h4=7s9BhmkVP4xHZTGn2KPPJZ0o1SkDjnI7FxNEbVm4Qmk=>
SDNC release notes : 
https://onap-doc.readthedocs.io/projects/onap-sdnc-oam/en/latest/release-notes.html#dockercontainers<https://urldefense.proofpoint.com/v2/url?u=https-3A__onap-2Ddoc.readthedocs.io_projects_onap-2Dsdnc-2Doam_en_latest_release-2Dnotes.html-23dockercontainers=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=j0hegKYxjT_l0mjIWay2PqSKb_XuYY9CHJQLZxjx8h4=snT7aWf8k1iDvoDHZtoJOfXyXh3U_mwvlkwq5aMW3Uc=>

Dan

From:  on behalf of "Morgan Richomme via 
lists.onap.org" 
Reply-To: "onap-...@lists.onap.org" , 
"morgan.richo...@orange.com" 
Date: Monday, June 1, 2020 at 6:29 AM
To: David McBride , "LEFEVRE, CATHERINE" 
, "onap-...@lists.onap.org" 

Cc: "onap-tsc@lists.onap.org" , Krzysztof Opasiak 
, "ZWARICO, AMY" , 'Pawel Pawlak' 
, David Perez Caparros 
Subject: [onap-ptl] [ONAP] [Frankfurt] Integration status for RC2

Hi

I will not be able to attend this afternoon (Public holiday in Europe).
I updated the status for the PTL meeting

1) Do we have all our RC2 dockers?
*
the Readiness board is up to date: 
https://wiki.onap.org/display/DW/Frankfurt+Readiness+dashboard<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Frankfurt-2BReadiness-2Bdashboard=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=5lQ48DiHBsslnrO5hsuDG9f0ckOFxIRm3lw8lOkrC_s=K-fhErY-fhGs9RmHIQql9ToGDab8FBk7L2ByPD06HVM=>

RC2 dockers are missing for some projects
They have been merged in Master Gate and are still in Frankfurt Gate for OOF, 
SDC and AAI
They are still in Master Gate for AAF and SO

I need also some clarification for SDNC and CDS
for CDS:  there are some patches for frankfurt in CCSDK gerrit (for SDNC: As 
the docker versions of the master branches are different than the ones of the 
frankfurt branch, I just need to be sure that the versions in Master are for 
Guilin and the ones in Frankfurt are the right 
ones.

Otherwise the integration in OOM is 
missing.
 

Finally I did not get any feedback from 
VFC.
I imagine that the versions are the right ones - no changes since M4..and 
possibly no lots of changes from El 
Alto.
But I need a confirmation to close the 
JIRA.
 


I updated the follow up pod by pod: 

 
https://docs.google.com/spreadsheets/d/1t3GNRtabdkVxG4ZAxqBJ-X7OO-Zv6xRwd8KrR52V9zU/

Re: [onap-tsc] [onap-ptl] [ONAP] [Frankfurt] Integration status for RC2

[TIMONEY, DAN]

Morgan,

The change you referenced below 
(https://gerrit.onap.org/r/c/ccsdk/features/+/108581) is really just to roll 
our version numbers to the next snapshot version – not a code change.  I may 
have created confusion by associating that with the same Jira I used to build 
the release itself – since that the final step in creating a new version is 
rolling the versions to the next snapshot.  Sorry for the confusion.

We did create RC2 versions for the parts of CCSDK and SDNC that changed since 
RC1 and updated the master branch of OOM with the corresponding version numbers 
(see https://gerrit.onap.org/r/c/oom/+/108346).  Note that the OOM team has 
asked that we NOT push to frankfurt directly but rather that we update master.  
It was my understanding that the OOM team had taken responsibility for 
cherry-picking changes to frankfurt after merging to master, but it appears I 
was mistaken. I  just cherry picked that change to their frankfurt branch.

FYI – the  CCSDK release notes and SDNC release notes  each contain a table 
with the correct released versions for our dockers.   Please see:

CCSDK release notes : 
https://onap-doc.readthedocs.io/projects/onap-ccsdk-distribution/en/latest/release-notes.html#dockercontainers
SDNC release notes : 
https://onap-doc.readthedocs.io/projects/onap-sdnc-oam/en/latest/release-notes.html#dockercontainers

Dan

From:  on behalf of "Morgan Richomme via 
lists.onap.org" 
Reply-To: "onap-...@lists.onap.org" , 
"morgan.richo...@orange.com" 
Date: Monday, June 1, 2020 at 6:29 AM
To: David McBride , "LEFEVRE, CATHERINE" 
, "onap-...@lists.onap.org" 

Cc: "onap-tsc@lists.onap.org" , Krzysztof Opasiak 
, "ZWARICO, AMY" , 'Pawel Pawlak' 
, David Perez Caparros 
Subject: [onap-ptl] [ONAP] [Frankfurt] Integration status for RC2

Hi

I will not be able to attend this afternoon (Public holiday in Europe).
I updated the status for the PTL meeting

1) Do we have all our RC2 dockers?
*
the Readiness board is up to date: 
https://wiki.onap.org/display/DW/Frankfurt+Readiness+dashboard

RC2 dockers are missing for some projects
They have been merged in Master Gate and are still in Frankfurt Gate for OOF, 
SDC and AAI
They are still in Master Gate for AAF and SO

I need also some clarification for SDNC and CDS
for CDS:  there are some patches for frankfurt in CCSDK gerrit 
(https://gerrit.onap.org/r/c/ccsdk/features/+/108581)
 but I did not find any corresponding OOM patches yet
for SDNC: As the docker versions of the master branches are different than the 
ones of the frankfurt branch, I just need to be sure that the versions in 
Master are for Guilin and the ones in Frankfurt are the right ones.
Otherwise the integration in OOM is missing.

Finally I did not get any feedback from VFC.
I imagine that the versions are the right ones - no changes since M4..and 
possibly no lots of changes from El Alto.
But I need a confirmation to close the JIRA.

I updated the follow up pod by pod: 
https://docs.google.com/spreadsheets/d/1t3GNRtabdkVxG4ZAxqBJ-X7OO-Zv6xRwd8KrR52V9zU/edit?usp=sharing

the RC1 1/06 (=RC2 candidate) column = results of the Frankfurt Daily run 
executed today: 
https://gating-results.onap.eu/results/onap_daily_pod4_frankfurt-574930638-06-01-2020_02-06/
the RC2 target includes the versions currently in gate in Frankfurt or in 
Master (announced for Frankfurt in patch), the ?? corresponds to the open 
question (tracked in the JIRA)
the Master column = results of the Master Daily branch executed today: 

Re: [onap-tsc] [onap-ptl] [OOM] Guilin Release Plan

[TIMONEY, DAN]

All,

Capturing these all on a wiki page would be helpful.  However,  my concern is 
that, when the time comes for us to commit to M1 for Guilin, we PTLs need to 
have a definitive list of what we're being asked to commit to so that there are 
no missed expectations.

I was thinking that items like "Logs must be written to STDOUT" should be 
captured as REQ Jiras, and then each project would create its own Jiras to 
track compliance - like we do for other non-functional requirements.  That way, 
we'll have better visibility on project impacts and compliance.  

Does that make sense?

Thanks!


Dan 

On 4/29/20, 9:45 AM, "sylvain.desbure...@orange.com" 
 wrote:

Well, yes it's a good idea!
As part of it comes from SECCOM, I propose someone who has the two hats to 
initiate the writing, a.k.a you :-P

De : Krzysztof Opasiak [k.opas...@samsung.com]
Envoyé : mercredi 29 avril 2020 15:37
À : DESBUREAUX Sylvain TGI/OLN; TIMONEY, DAN; onap-...@lists.onap.org; 
onap-tsc@lists.onap.org
Cc : RICHOMME Morgan TGI/OLN; Mike Elliott; CLOSSET, CHRISTOPHE; 
dmcbr...@linuxfoundation.org; Kenny Paul
Objet : Re: [onap-ptl] [OOM] Guilin Release Plan

Hi,

On 29.04.2020 15:11, sylvain.desbure...@orange.com wrote:
> Hey Dan,
>
> Nope I didn't create any stories.
>
> What I can do (if possible) is to create one story per requirement (I
> count roughly 15) and create a sub task per project (if possible in
> project board).
> That would add 15 tasks per project (knowing that some will be
> irrelevant for the project, like "check postgresql 12.2 is ok for your
> project" for you)
>
> Or, we don't do that and create Jira tickets when we find that one
> requirement is not met (like "all logs to STDOUT" for you).

I think Sylvain that sth else what we could do is to create a wiki page
with the list of requirements that has to be fulfilled in order to get
your patch accepted in OOM

>
> it's up to you PTLS, as you prefer
> --------
> *De :* TIMONEY, DAN [dt5...@att.com]
> *Envoyé :* lundi 27 avril 2020 20:33
> *À :* onap-...@lists.onap.org; DESBUREAUX Sylvain TGI/OLN;
> onap-tsc@lists.onap.org
> *Cc :* RICHOMME Morgan TGI/OLN; Krzysztof Opasiak; Mike Elliott;
> CLOSSET, CHRISTOPHE; dmcbr...@linuxfoundation.org; Kenny Paul
> *Objet :* Re: [onap-ptl] [OOM] Guilin Release Plan
>
> Sylvain,
>
> Thank you for the excellent summary, which was also explained quite well
> at last week’s virtual face to face event.
>
> One process question, though: are there already user stories created for
> these items (perhaps SECCOM user stories)?  I want to make sure we’re
> tracking these requirements when we do our release planning for Guilin.
>
> Thanks!
>
> Dan
>
> *From: * on behalf of "Sylvain Desbureaux via
> lists.onap.org" 
> *Reply-To: *"onap-...@lists.onap.org" ,
> "sylvain.desbure...@orange.com" 
> *Date: *Monday, April 27, 2020 at 12:22 PM
> *To: *"onap-...@lists.onap.org" ,
> "onap-tsc@lists.onap.org" 
> *Cc: *RICHOMME Morgan TGI/OLN , Krzysztof
> Opasiak , Mike Elliott ,
> "CLOSSET, CHRISTOPHE" ,
> "dmcbr...@linuxfoundation.org" , Kenny
> Paul 
> *Subject: *[onap-ptl] [OOM] Guilin Release Plan
>
> Dear PTLs, dear TSC members,
>
> as RC0 is (almost) passed and Frankfurt branch will be soon created, I
> think it's important to share with you all the OOM release plan for 
Guilin.
>
> As you'll eventually push your changes in OOM, I think it's important
> that you know our plans.
>
> # TL;DR;
>
> * If you don't retrieve your certificates automatically, this is the
> __first__ thing you must do. See
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_onap_oom_tree_master_kubernetes_nbi=DwIF-g=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=Pnxdi9dPOhDjWDeEd_T-D7eRN37ZhE4E7yc3_7Dg8S4=5R9ip71ETCZ99dfV957JvUThqpBQRB60hZLGYaaXiR4=
 
> 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D1cb18522-2D4162d9ad-2D1cb00e6d-2D0cc47a31ce52-2De8686001521714c3-26q-3D1-26u-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fgithub.com-5Fonap-5Foom-5Ftree-5Fmaster-5Fkubernetes-5Fnbi-2526d-253DDwQFAw-2526c-253DLFYZ-2Do9-5FHUMeMTSQicvjIg-2526r-253DqLcfee4a2vOwYSub0bljcQ-2526m-253DHceOARp59TvXni8a6PJgJVBW81QZ4IHOTjrxRGuNiU0-2526s-253DKJ89qSlgfhIhQT-2DfXkbJYG8mmP0FgLxU

Re: [onap-tsc] [onap-ptl] [OOM] Guilin Release Plan

[TIMONEY, DAN]

Sylvain,

Thank you for the excellent summary, which was also explained quite well at 
last week’s virtual face to face event.

One process question, though: are there already user stories created for these 
items (perhaps SECCOM user stories)?  I want to make sure we’re tracking these 
requirements when we do our release planning for Guilin.

Thanks!
Dan


From:  on behalf of "Sylvain Desbureaux via 
lists.onap.org" 
Reply-To: "onap-...@lists.onap.org" , 
"sylvain.desbure...@orange.com" 
Date: Monday, April 27, 2020 at 12:22 PM
To: "onap-...@lists.onap.org" , 
"onap-tsc@lists.onap.org" 
Cc: RICHOMME Morgan TGI/OLN , Krzysztof Opasiak 
, Mike Elliott , "CLOSSET, 
CHRISTOPHE" , "dmcbr...@linuxfoundation.org" 
, Kenny Paul 
Subject: [onap-ptl] [OOM] Guilin Release Plan

Dear PTLs, dear TSC members,

as RC0 is (almost) passed and Frankfurt branch will be soon created, I think 
it's important to share with you all the OOM release plan for Guilin.

As you'll eventually push your changes in OOM, I think it's important that you 
know our plans.

# TL;DR;

* If you don't retrieve your certificates automatically, this is the __first__ 
thing you must do. See 
https://github.com/onap/oom/tree/master/kubernetes/nbi
 as an example. `certInit` template (a.k.a `aafInit`) is the **strongly** 
preffered way to do that.
* No more than 1 main process per container. If you have more, it'll be a 
blocker for updates
* All logs to STDOUT
* No direct commit to Frankfurt but master then cherry-pick
* All upstream components should use an upstream (dockerhub, googlehub) version
* Common chart version bump
* Mariadb common chart will be upgraded to 10.4.12
* PostgreSQL common chart will be upgraded to 12.2
* Cassandra common chart will be upgraded to 3.11.6
* MongoDB common chart will be upgraded to 4.2.2
* ElasticSearch common chart may be upgraded, waiting for SECCOM proposed 
version
* AAF is an optional requirement, meaning your component must work without AAF 
(certificates and RBAC), even on degraded mode
* MSB is an optional requirement, meaning your component must work without MSB
* Your component can use http as **server** and **client**
* Password removal will continue on common charts (postgreSQL at least) and 
start on your component, be prepared to receive so call for help
* Commit messages must be meaningful and follow the format shown below.
* Proper crash (if your component fails, it must exit with code > 0, and not 
wait or exit with code 0)
* Ingress will be the default deployment option (via Nginx Ingress). No more 
access via NodePort per default
* New code will be submitted only if pods + healthchecks + basic tests are OK
* No root access to any Database from application container
* No configuration generation using sed in the application container

# Certificates

Certificates in Docker are not allowed in Francfurt release per SECCOM 
recommendation.
They won't be allowed either in helm chart starting branching of Frankfurt. 
This means you must move to automatic retrieval at boot.
You'll either have to:

* use `certInit` template (formerly known as `aafInit` template) (see 
[NBI](https://github.com/onap/oom/tree/master/kubernetes/nbi)
 as an example)
* do it by your own + explain why you can't use `certInit` template (will be 
subject to acceptance / not acceptance from both SECCOM and OOM team)

# No More than 1 main process per container

Several containers uses several process (main component + database(s)) in the 
same docker.

Each container should have only one concern. Decoupling applications into 
multiple containers makes it easier to scale horizontally and reuse containers. 
For instance, a web application stack might consist of three separate 
containers, each with its own unique image, to manage the web application, 
database, and an in-memory cache in a decoupled manner.

Limiting each container to one process is a good rule of thumb, but it is not a 
hard and fast rule. For example, not only can containers be spawned with an 
init process, some programs might spawn additional processes of their own 
accord. For instance, Celery can spawn multiple worker processes, and Apache 
can create one process per request.


This will not be accetped anymore as it's a very bad pattern 

Re: [onap-tsc] [Onap-release] Gerrit usage too heavy with local HTTP calls

[TIMONEY, DAN]

Jess,

Out of curiosity, I did a reverse DNS lookup on 142.93.109.98 and got this:

$ host 142.93.109.98
98.109.93.142.in-addr.arpa domain name pointer comoros.bitergia.net.

So maybe biterga is the culprit?  Can that be updated to do its pulls from 
github maybe?

Dan

From:  on behalf of 
"jwagant...@linuxfoundation.org" 
Date: Thursday, April 23, 2020 at 1:47 PM
To: "FRANEY, JOHN J" , "Krzysztof Opasiak 
(k.opas...@samsung.com)" 
Cc: onap-discuss , onap-release 
, onap-tsc 
Subject: Re: [Onap-release] Gerrit usage too heavy with local HTTP calls

@Krzysztof Opasiak (k.opas...@samsung.com) , the 
most active IP is 142.93.109.98

@FRANEY, JOHN J we encourage the local usage of Github 
and APAC as much as possible. If you need to push code, you can always add a 
local
remote to gerrit even if you fetched the code using Github.

Thanks!
Jess

On Thu, Apr 23, 2020 at 10:34 AM FRANEY, JOHN J 
mailto:jf2...@att.com>> wrote:
Jess,

Under which use case should I use which link?

Sorry, I was using only:  
https://wiki.onap.org/display/DW/Resources+and+Repositories


John




From: onap-rele...@lists.onap.org 
mailto:onap-rele...@lists.onap.org>> On Behalf Of 
jwagant...@linuxfoundation.org
Sent: Thursday, April 23, 2020 1:16 PM
To: onap-disc...@lists.onap.org; 
onap-release mailto:onap-rele...@lists.onap.org>>; 
onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: [Onap-release] Gerrit usage too heavy with local HTTP calls

Dear team,

We have noticed several times that ONAP Gerrit is being flooded with HTTP 
requests
which causes the server to be overloaded and drop causing backlogs in Jenkins 
too and
requiring a lot of work to restore these services.

I would like to remind you to please use Github for cloning the repos you need 
instead.

Also, please remember we have the APAC mirror too:

git://gerrit-mirror-ap.onap.org/mirror/${PROJECT}
Example clone:
git clone 
git://gerrit-mirror-ap.onap.org/mirror/ci-management.git

Thanks so much!
Jess


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

View/Reply Online (#6188): https://lists.onap.org/g/onap-tsc/message/6188
Mute This Topic: https://lists.onap.org/mt/73223689/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] CCSDK Committer promotion requests : Kapil Singal and Kevin Smokowski

[TIMONEY, DAN]

TSC

The CCSDK project would like to recommend the following 2 developers for 
promotion to committer:

Kapil Singal : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+CCSDK+-+Kapil+Singal
Kevin Smokowski : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+CCSDK+-+Kevin+Smokowski

Both of them have a strong record of contributions to our project and have the 
support of our existing committers.I would greatly appreciate your approval 
to promote them to committers.

Thanks!
Dan

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

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

View/Reply Online (#5608): https://lists.onap.org/g/onap-tsc/message/5608
Mute This Topic: https://lists.onap.org/mt/54324215/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-release] Self-Release Process Issues

[TIMONEY, DAN]

All

For those new to global-jjb, you can tell if your repo has the problem Kenny 
describes below by looking in the console log of your staging job for the 
string “autorelease”. You should only find that string AFTER the maven build 
succeeds. If you see it in the body
of the build, you’re still using the nexus staging plugin somewhere (e.g. using 
oparent 1.x instead of 2.0.0)

I posted this tip on the wiki page for self release as well earlier today.

Dan

Sent from MyOwn, an AT BYOD solution.

From: "Kenny Paul" mailto:kp...@linuxfoundation.org>>
Date: Thursday, August 8, 2019 at 5:25:44 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-rele...@lists.onap.org" 
mailto:onap-rele...@lists.onap.org>>
Subject: [Onap-release] Self-Release Process Issues

All,

Self-release is something the community has been asking the LF for since 2017.  
That is now possible however the process is unfairly getting a bad reputation.  
Some growing pains are to be expected with any transition, but there has been a 
rush to judgement that  the process is somehow fundamentally flawed. Indeed 
there was an issue identified as a bug on the LF side, which the RelEng team 
quickly rectified. The remainder of the tickets unfortunately have primarily 
come from project teams that have not made the updates necessary to enable 
self-release, or are not following the documented process.

An example of this was a ticket opened today because a successful build did not 
but produce all of the required artifacts.  The root cause of this problem was 
the continued use of the deprecated nexus-staging-maven-plugin which 
pre-packaged and deployed some artifacts before lftools compiled the official 
auto-release package.  Eliminating the plugin in the example above was 
discussed during numerous TSC and PTL calls related to the global-jjb 
migration. No one should still be using that plugin, however it is the process 
and tools that have been blamed for the failure.

Please help us help you; read and follow the instructions found here:  Self 
Releases Workflow 
(Nexus2)


Thanks!
-kenny



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

View/Reply Online (#5337): https://lists.onap.org/g/onap-tsc/message/5337
Mute This Topic: https://lists.onap.org/mt/32803561/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] Attn PTLs: Review El Alto early drop status

[TIMONEY, DAN]

Jim

I attached a copy with the updates for CCSDK (CDS) and SDNC.  Not all the 
images are available yet (waiting on CCSDK docker images to be released, and 
then I can build the SDNC images), but I did already submit changes to OOM to 
reflect what the image versions will be – which is what’s in this chart.

Here are the OOM changes:

Staging : https://gerrit.onap.org/r/c/oom/+/92798
Master : https://gerrit.onap.org/r/c/oom/+/93113

FYI – I marked the oom master update as “work in progress” so that it can’t be 
accidentally merged until the images are actually released (chances are the oom 
verify build would fail anyway, preventing that, but I also wanted to clearly 
indicated it’s not ready yet).

Dan

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

From:  on behalf of Jim Baker 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, August 7, 2019 at 6:49 PM
To: onap-tsc 
Subject: [onap-tsc] Attn PTLs: Review El Alto early drop status

PTLs,
Please take a look at the attached spreadsheet and note any changes that need 
to be made for your projects. We're trying to get a good assessment of our 
Early Drop contents and your review/corrections will help.

Please send any corrections back to me and I'll consolidate. Please complete 
this by end of you day Thursday (Aug 8).
Thanks for your help.

--
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 (#5335): https://lists.onap.org/g/onap-tsc/message/5335
Mute This Topic: https://lists.onap.org/mt/32793300/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]
-=-=-=-=-=-=-=-=-=-=-=-



sdnc_cds_images.xlsx
Description: sdnc_cds_images.xlsx

[onap-tsc] SDNC PTL 2019 Election

[TIMONEY, DAN]

I am pleased to announce that I have the honor of serving for another year as 
SDNC PTL.   Thanks to the committers for their vote of confidence.  I updated 
the voting results page on the wiki with the results , including a link to the 
“official” poll results.

Dan

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

From: "TIMONEY, DAN" 
Date: Monday, July 22, 2019 at 2:17 PM
To: DAVE STILWELL , "SOMASUNDARAM, PRABHURAM" 
Cc: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

SDNC committers,

You should have received a ballot earlier today for our annual PTL election.  
I’m the only nominee, but the rules still require a vote.  So if you can please 
vote by 9 AM EDT Thursday, I’d appreciate it.

Thanks!
Dan


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

From: "TIMONEY, DAN" 
Date: Wednesday, July 17, 2019 at 9:03 AM
To: DAVE STILWELL , "SOMASUNDARAM, PRABHURAM" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

SDNC committers,

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan


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

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

View/Reply Online (#5300): https://lists.onap.org/g/onap-tsc/message/5300
Mute This Topic: https://lists.onap.org/mt/32645717/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] [ccsdk] CCSDK PTL 2019 Election results

[TIMONEY, DAN]

CCSDK team,

The election results are in, and it is my pleasure to announce that I have the 
honor of serving another year as your PTL.

Thank you as always for your support.  I look forward to continuing to work 
with you all.

Thanks,

Dan



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

From: "TIMONEY, DAN" 
Date: Wednesday, July 17, 2019 at 9:01 AM
To: "HU, JUN NICOLAS" , "LUCAS, JACK" 
, "gaurav.agra...@huawei.com" 
, "brindasa...@in.ibm.com" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [ccsdk] Call for nominations of CCSDK PTL 2019

CCSDK committers,

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan

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

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

View/Reply Online (#5291): https://lists.onap.org/g/onap-tsc/message/5291
Mute This Topic: https://lists.onap.org/mt/32598490/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] [ccsdk] Call for nominations of CCSDK PTL 2019

[TIMONEY, DAN]

CCSDK committers,

You should have received a ballot earlier today for our annual PTL election.  
I’m the only nominee, but the rules still require a vote.  So if you can please 
vote by 9 AM EDT Thursday, I’d appreciate it.

Thanks!
Dan

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

From: "TIMONEY, DAN" 
Date: Wednesday, July 17, 2019 at 9:01 AM
To: "HU, JUN NICOLAS" , "LUCAS, JACK" 
, "gaurav.agra...@huawei.com" 
, "brindasa...@in.ibm.com" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [ccsdk] Call for nominations of CCSDK PTL 2019

CCSDK committers,

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan

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

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

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

Re: [onap-tsc] [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

[TIMONEY, DAN]

SDNC committers,

You should have received a ballot earlier today for our annual PTL election.  
I’m the only nominee, but the rules still require a vote.  So if you can please 
vote by 9 AM EDT Thursday, I’d appreciate it.

Thanks!
Dan


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

From: "TIMONEY, DAN" 
Date: Wednesday, July 17, 2019 at 9:03 AM
To: DAVE STILWELL , "SOMASUNDARAM, PRABHURAM" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

SDNC committers,

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan


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

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

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

Re: [onap-tsc] [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

[TIMONEY, DAN]

I would like to self-nominate for the position of SDNC PTL.

It has been my pleasure to work with this team for the past 2 years and look 
forward to continuing to improve our platform!

Dan

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

From:  on behalf of "TIMONEY, DAN" 
Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, July 17, 2019 at 9:03 AM
To: DAVE STILWELL , "SOMASUNDARAM, PRABHURAM" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

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

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections-23AnnualCommunityElections-2DPTLElections=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=M1EENOwc_fF_DwJuVC4I3Oj2cukQmmW6cH_uoUP7IHg=7RVbrVxjly8ED_KCNBKYSFNckTLp7JDzX_wkCgYL7uY=>

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan


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


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

View/Reply Online (#5250): https://lists.onap.org/g/onap-tsc/message/5250
Mute This Topic: https://lists.onap.org/mt/32502947/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] [ccsdk] Call for nominations of CCSDK PTL 2019

[TIMONEY, DAN]

I would like to self-nominate for the position of CCSDK PTL.

It has been my pleasure to work with this team for the past 2 years and look 
forward to continuing to improve our platform!

Dan


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

From:  on behalf of "TIMONEY, DAN" 
Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, July 17, 2019 at 9:01 AM
To: "HU, JUN NICOLAS" , "LUCAS, JACK" 
, "gaurav.agra...@huawei.com" 
, "brindasa...@in.ibm.com" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] [ccsdk] Call for nominations of CCSDK PTL 2019

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

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections-23AnnualCommunityElections-2DPTLElections=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=i2mPlBS0KDctDBBgqI2x4YMFmbTAhYl8YNpJBUt9Juo=2IN-R_-2WAURmLJPaIdyl5Zy83U6HlGZbrcm7gLF6Kc=>

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan

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


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

View/Reply Online (#5251): https://lists.onap.org/g/onap-tsc/message/5251
Mute This Topic: https://lists.onap.org/mt/32502932/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] [onap-tsc[ [sdnc] Call for nominations of SDNC PTL 2019

[TIMONEY, DAN]

SDNC committers,

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan


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

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

View/Reply Online (#5248): https://lists.onap.org/g/onap-tsc/message/5248
Mute This Topic: https://lists.onap.org/mt/32502947/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] [ccsdk] Call for nominations of CCSDK PTL 2019

[TIMONEY, DAN]

CCSDK committers,

Annual PTL elections have started. The process is described here:
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 19 at 5:00 PM EST

Thanks!
Dan

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

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

View/Reply Online (#5246): https://lists.onap.org/g/onap-tsc/message/5246
Mute This Topic: https://lists.onap.org/mt/32502932/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] Committer promotion request for CCSDK : Brinda Santh Muthuramalingam

[TIMONEY, DAN]

TSC:

Please consider the following committer promotion request for Brinda Santh 
Muthuramalingam for the CCSDK project:

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+CCSDK+-+Brinda+Santh+Muthuramalingam

Brinda has been an outstanding contributor to the CDS project team, where he is 
one of our development leads.   He has the unanimous support of all existing 
CCSDK committers.

Thanks!
Dan

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

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

View/Reply Online (#5203): https://lists.onap.org/g/onap-tsc/message/5203
Mute This Topic: https://lists.onap.org/mt/32407768/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] FW: SUPPORT-178 ONAP 6 and 9 accounts disabled

[TIMONEY, DAN]

Kenny,

Fair enough.  I certainly wouldn’t expect to see every ticket opened by every 
user, but it would be helpful if there was a way to let us see tickets that 
apply across projects, like the Zoom issue this morning or like some of the 
Jenkins issues we’ve had in the past.  That way we can maybe keep LF IT from 
being flooded with duplicate tickets.  In the old email based system, we could 
forward the ticket to others if we ran across a case like that.  That was 
probably about the only advantage of that system over the new one, so if we can 
deal with that sharing issue somehow, it’d be a win/win.

Dan





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

From:  on behalf of Kenny Paul 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, June 26, 2019 at 1:12 PM
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] FW: SUPPORT-178 ONAP 6 and 9 accounts disabled

I appreciate Jim being much more polite in a different response, but I need to 
throw a yellow card on this play as being just plain unfair.

As far as I’m aware you all couldn’t even see your own tickets using the old 
system ticketing system.

As with 99% of the IT ticketing systems I’ve ever worked with over the course 
of 32 years, you can only see tickets that you opened yourself.  That is a 
standard IT helpdesk  security feature to keep folks from nosing around in 
someone else’s business,  or account information, or passwords…   That missing 
% above? That is the old system we just got rid of.

On the separate issue of IT telling folks to contact me for zoom technical 
issues (not related to meeting creation, change or deletion) I can understand 
the confusion. It is however correct.  All IT manages is the account.  
Community support for using Zoom is ultimately the TPM’s responsibility to 
figure out and when appropriate the TPM will engage IT.

With regards to that, I am in direct contact with IT and have been since 6am 
local time. We are setting up a call with the Zoom account Manager for the LF 
to understand why this was done.

-kenny

From: onap-tsc@lists.onap.org  On Behalf Of TIMONEY, 
DAN
Sent: Wednesday, June 26, 2019 9:03 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] FW: SUPPORT-178 ONAP 6 and 9 accounts disabled

Also, note that it seems like we can only see our own tickets in this system.  
I couldn’t see this ticket and, when I tried to view all tickets, I saw none at 
all.

This clearly needs work.

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

From: mailto:onap-tsc@lists.onap.org>> on behalf of 
"DRAGOSH, PAM" mailto:pdrag...@research.att.com>>
Reply-To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Date: Wednesday, June 26, 2019 at 11:40 AM
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] FW: SUPPORT-178 ONAP 6 and 9 accounts disabled

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


Kenny/Jim,

I’m not sure I see the point of moving to this new system if all they do is 
tell me to contact you directly.

Pam


From: Johnson Nguyen 
mailto:notificati...@jira.linuxfoundation.org>>
Date: Wednesday, June 26, 2019 at 10:56 AM
To: "DRAGOSH, PAMELA L (PAM)" 
mailto:pdrag...@research.att.com>>
Subject: SUPPORT-178 ONAP 6 and 9 accounts disabled


Johnson Nguyen changed the status to Resolved.



Johnson Nguyen resolved this as Won't Do.

How was our service for this request?
☆<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.linuxfoundation.org_servicedesk_customer_portal_4_SUPPORT-2D178_feedback-3Ftoken-3D9cd56c304158137884e238e37b6a4ef4c9c64a85-26rating-3D1=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=qXs11WgABwQrgwRt7_wj5Y5fC3jxmVDI7j3jCPxYGW4=v8pX3LkyHKLhEAfX3fhePleLUIKxCSrxwM6D6vL7kSE=>

Very poor

☆<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.linuxfoundation.org_servicedesk_customer_portal_4_SUPPORT-2D178_feedback-3Ftoken-3D9cd56c304158137884e238e37b6a4ef4c9c64a85-26rating-3D2=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=qXs11WgABwQrgwRt7_wj5Y5fC3jxmVDI7j3jCPxYGW4=OuXo507P3FMH0vifSxOJkqRKjjV46waxV1pXJSkS4tY=>

Poor

☆<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.linuxfoundation.org_servicedesk_customer_portal_4_SUPPORT-2D178_feedback-3Ftoken-3D9cd56c304158137884e238e37b6a4ef4c9c64a85-26rating-3D3=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aU

Re: [onap-tsc] FW: SUPPORT-178 ONAP 6 and 9 accounts disabled

[TIMONEY, DAN]

Also, note that it seems like we can only see our own tickets in this system.  
I couldn’t see this ticket and, when I tried to view all tickets, I saw none at 
all.

This clearly needs work.

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

From:  on behalf of "DRAGOSH, PAM" 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, June 26, 2019 at 11:40 AM
To: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] FW: SUPPORT-178 ONAP 6 and 9 accounts disabled

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


Kenny/Jim,

I’m not sure I see the point of moving to this new system if all they do is 
tell me to contact you directly.

Pam


From: Johnson Nguyen 
Date: Wednesday, June 26, 2019 at 10:56 AM
To: "DRAGOSH, PAMELA L (PAM)" 
Subject: SUPPORT-178 ONAP 6 and 9 accounts disabled


Johnson Nguyen changed the status to Resolved.



Johnson Nguyen resolved this as Won't Do.

How was our service for this request?
☆

Very poor

☆

Poor

☆

Neither good nor poor

☆

Good

☆

Very good



View 
request
 · Turn off this request's 
notifications

This is shared with Pamela Dragosh.

Help Center, powered by Jira Service 
Desk,
 sent you this message.


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

View/Reply Online (#5156): https://lists.onap.org/g/onap-tsc/message/5156
Mute This Topic: https://lists.onap.org/mt/32216246/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] RC0 completion plan

[TIMONEY, DAN]

Jim,

Just wanted to confirm that the SDNC containers for RC0 are available, and the 
OOM helm charts have been updated to use the released versions.

Dan

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

From:  on behalf of Jim Baker 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Tuesday, May 7, 2019 at 12:46 PM
To: onap-tsc 
Subject: [onap-tsc] RC0 completion plan

Recounting the conversation about the phasing of the integration targets for 
Dublin from the PTL meeting...
Wave 1 (Due May 7) RC0 is: portal, sdc, dmaap, aai, so , sdnc, vid , aaf
Wave 2 (Due May 9) RC0 is: appc, policy, clamp, oof, dcae

This was the plan we discussed. If you cannot make your deliverables today 
PLEASE let myself/Yang know.
Thanks folks.

--
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 (#4939): https://lists.onap.org/g/onap-tsc/message/4939
Mute This Topic: https://lists.onap.org/mt/31533882/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] URGENT: open jira tickets in Dublin

[TIMONEY, DAN]

Jim,

There are several cases where it still makes sense for there to be open Dublin 
tickets:


  1.  Some tickets are being used to track test cases.
  2.  Some tickets are associated with release activities, like creating 
release artifacts and rolling snapshot versions.

On my projects, we’ve been creating those types of Jira as “tasks” (as opposed 
to stories or defects), so as not to confuse them with actual code 
deliverables.  Maybe it’d be helpful if we also added a label to these types of 
tickets so you’d know those are not cause for concern?

Dan

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

From:  on behalf of Jim Baker 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, May 1, 2019 at 9:48 AM
To: onap-tsc 
Subject: [onap-tsc] URGENT: open jira tickets in Dublin

Dublinites,
Cursory screening of the RC0 checklist suggest the very first item is being 
misinterpreted. The item reads:

Product Management:  Are all tasks associated with the release been marked as 
"Closed" in Jira?

What this really means is all tickets associated with Dublin Release need to be 
resolved... moved to El-Alto/Frankfurt, closed or somehow resolved. The reason 
this is important is product management and docs use the jira tickets 
associated with the Dublin release to determine what has been worked on...
Obviously there will be a few defects still open but MOST Epics, Stories, 
Tasks, Sub-tasks should be closed (or relating to the release process).

I put together a wiki page to show the magnitude of the 
problem
 (currently 739 OPEN Dublin tickets) - please get this resolved so we can 
complete this milestone! Please also check for "In Process" or "Reopened" 
tickets...

Let me know if you have any questions.
--
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 (#4904): https://lists.onap.org/g/onap-tsc/message/4904
Mute This Topic: https://lists.onap.org/mt/31432469/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] Proposed Dublin Architecture Slides

[TIMONEY, DAN]

Stephen,

I wanted to note that in Dublin, CDS is not yet integrated with SDC.   I’m fine 
with showing CDS inside the SDC bubble since that is where we believe CDS 
belongs in the architecture.  However, it might be helpful to add a note to 
that effect in the CDS description so that readers won’t expect to find a CDS 
link from the SDC UI in Dublin.  For example, maybe add the following to the 
CDS description on page 5:

Note: in Dublin, CDS is a standalone design component but will be integrated 
with SDC in a future ONAP release.


Dan


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

From:  on behalf of Stephen Terrill 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Monday, April 15, 2019 at 7:38 AM
To: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find attatched the proposed Dublin architecture slides.  This is a 
reduced slide set compared to the previous release due to that we are working 
to capture the functional component descriptions and it was thought that the 
effort was better focussed on that.

Best Regards,

Steve

[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

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

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

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

Our commitment to Technology for 
Good
 and Diversity and 
Inclusion
 contributes to positive change.
Follow us on: 
Facebook
 
LinkedIn
 
Twitter

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


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

View/Reply Online (#4840): https://lists.onap.org/g/onap-tsc/message/4840
Mute This Topic: https://lists.onap.org/mt/31187054/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] WindRiver lab - removing VMs plan and exemptions

[TIMONEY, DAN]

Jim,

Please add ccsdk-sdnc-heat-env to the list exempted from deletion.  Our 
CCSDK/SDNC team uses that environment for testing and debugging.

Thanks!
Dan

From: onap-tsc@lists.onap.org  On Behalf Of Jim Baker
Sent: Monday, March 18, 2019 11:52 AM
To: onap-tsc 
Subject: Re: [onap-tsc] WindRiver lab - removing VMs plan and exemptions

Dear ONAP users of the WIndRiver lab,

Please find attached the FINAL LIST of VM exempted from deletion.

The attached spreadsheet has the list of the VMs in the WindRiver lab. If the 
VMs are highlighted in Yellow, they are targeted for deletion UNLESS they are 
in a strikethrough font.
This is your last chance to indicated certain VMs should be saved
Deletions will occur later this week.
Thanks for your help in making resources available for the Dublin integration 
testing!
Jim


On Mon, Mar 11, 2019 at 5:08 PM Jim Baker via 
Lists.Onap.Org
 
mailto:linuxfoundation@lists.onap.org>>
 wrote:
Greetings ONAP developers!
Please review the attached spreadsheet. All the items highlighted in yellow are 
over 100 days since creation and are targeted for blanket removal. If you have 
an older VM that is listed for removal AND you'd like an exemption,  you need 
to respond to this email with the ID of the VM to exclude. Please use the ID as 
the Name is non-unique. Exemptions will be gathered through Thursday 2019-03-14 
with VM removal scheduled for 2019-03-18.

Thank you for helping to create some spare capacity for the upcoming testing 
crunch!
--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


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

[TIMONEY, DAN]

Wow – congratulations!





--
Dan Timoney
SDN-CP Development
ONAP Project Technical Lead : CCSDK and SDNC

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of "FREEMAN, BRIAN D" 
Reply-To: "onap-tsc@lists.onap.org" 
Date: Friday, February 22, 2019 at 9:29 AM
To: "CHO, TAKAMUNE" , 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 , "LEFEVRE, CATHERINE" 
, Jim Baker 
Subject: Re: [onap-tsc] APPC reaches 80% line coverage 2/22/2019

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


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 (#4663): https://lists.onap.org/g/onap-tsc/message/4663
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: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

[TIMONEY, DAN]

All,

One clarification I wanted to make, re: Robert’s question about the list we’d 
provided.

The Nexus IQ server also reports on third party libraries that are embedded 
within other jars.  For example, ODL Oxygen doesn’t ship netty 4.0.30, but the 
jar for narayana-osgi-jta contains that version of netty.  I can tell that 
because when I look at “Occurrences” of that library in the Nexus IQ Server 
report, I see this:

netty-all-4.0.30.Final.jar located at 
opendaylight/oxygen/target/docker-stage/karaf-0.8.3.tar.gz/karaf-0.8.3/system/org/jboss/narayana/osgi/narayana-osgi-jta/5.5.2.Final/narayana-osgi-jta-5.5.2.Final.jar


I really wish we could just share the report, but unfortunately Sonatype told 
us in no uncertain terms that sort of thing is a violation of their software 
license terms.

I just wanted to reassure you  all that I really did do my best to be careful 
about separating out the vulnerabilities we’re inheriting from ODL from any 
that we’re introducing ourselves.

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.


From: Abhijit Kumbhare 
Date: Friday, February 8, 2019 at 11:06 AM
To: "onap-tsc@lists.onap.org" 
Cc: Robert Varga , "TIMONEY, DAN" 
Subject: Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

Sure Alexis - I will add this to the agenda next week. Earlier this week Anil 
Belur was asking for the same to be on the agenda - but there was no time this 
week to have this.

On Fri, Feb 8, 2019 at 7:06 AM Alexis de Talhouet 
mailto:adetalhoue...@gmail.com>> wrote:



On Feb 8, 2019, at 10:00 AM, Brian mailto:bf1...@att.com>> 
wrote:

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.

I tend to think we can. This is one of the things I want to discuss during ODL 
TSC when it is the good time.



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

View/Reply Online (#4593): https://lists.onap.org/g/onap-tsc/message/4593
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: [onap-tsc] [Onap-release] Quick Gerrit restart to fix HTTP Auth

[TIMONEY, DAN]

Jess, all:

Somehow, my gerrit http password was reset after this patch and I had to 
regenerate it.  Not a big deal, but wanted to give a heads up in case people 
notice their git pulls are failing.   It’s not that gerrit is still broken – 
it’s that your http password needs to be reset, and then you’ll need to reset 
it in your local environment.

Dan

--
Dan Timoney
SDN-CP Development
ONAP Project Technical Lead : CCSDK and SDNC

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of Jessica Wagantall 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Thursday, January 31, 2019 at 3:50 PM
To: onap-discuss , onap-release 
, onap-tsc , 
"onap-lf-annou...@lists.onap.org" 
Subject: Re: [onap-tsc] [Onap-release] Quick Gerrit restart to fix HTTP Auth

HTTP should be fixed now.

Thanks!
Jess

On Thu, Jan 31, 2019 at 12:24 PM 
mailto:jwagant...@linuxfoundation.org>> wrote:
Dear ONAP team.

We need to add urgently a Gerrit fix needed after the recent update related to
https://www.gerritcodereview.com/2.14.html#http-digest-authentication-removed

This will take just a few minuted for Gerrit to restart.

Jenkins is now placed in quietDown mode and the restart will happen right after.

Thanks again for your patience!
Jess


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

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

[TIMONEY, DAN]

The slow downs I saw this morning happened in 2 specific cases :

1)  I had done a search for issues by project/status/type/fix version to list 
all the open Epics for SDNC in the Casablanca release and was trying to update 
the epic name on one of the issues.  It hung and eventually told me that the 
system could not access that issue.

2) I had clicked the link to "add a comment" to an existing Jira I'd received 
in email, and when I committed my change the system hung and again told me it 
could not access that issue.

At that point I gave up.



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

On 7/18/18, 1:35 PM, "bf1...@att.com via RT" 
 wrote:

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

[onap-tsc] Jira issues - again

[TIMONEY, DAN]

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

--- Begin Message ---
LF IT team,

 

I don’t know if this is related to last night’s maintenance, but Jira is very, 
very slow this morning.  If I do a search for issues, I see the list, but it’s 
greyed out and I can’t click on any of the issues to update them. 

 

Thanks,

Dan

 

Dan Timoney 

Principal Technical Staff Member

AT

Email : dtimo...@att.com

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873

 

From:  on behalf of Jessica Wagantall 

Date: Tuesday, July 10, 2018 at 5:22 PM
To: onap-discuss , onap-release 
, onap-tsc , 
"onap-lf-annou...@lists.onap.org" , Jordan 
Evans 
Subject: Re: [onap-tsc] [it-infrastructure-alerts] Nexus2, Nexus3 and Jenkins 
unavailable at 2:00pm PT time

 

This is now completed.  

 

Thanks!

Jess

 

On Tue, Jul 10, 2018 at 12:40 PM, Jessica Wagantall 
 wrote:

What: The Linux Foundation will be performing maintenance in Nexus instances

 

When: Tuesday July 10 at 2:00pm Pacific

 

Why: Our infra team will be performing an upsize of both Nexus2 and Nexus3 
instances.

 

Impact: Jira wil be paused, Nexus2 and Nexus3 will be unavailable during this 
time. 

 

Thanks so much!

Jess

 

_._,_._,_

Links: 

You receive all messages sent to this group. 

View/Reply  Online (#3351) | Reply To Sender | Reply To Group | Mute This Topic 
| New Topic

Your  Subscription | Contact Group Owner | Unsubscribe [dtimo...@att.com]

_._,_._,_

--- End Message ---

[onap-tsc] Casablanca release participation - SDN Controller

[TIMONEY, DAN]

TSC:

Please be advised that SDN Controller (SDNC) plans to participate in the 
Casablanca release.

Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Casablanca release participation - CCSDK

[TIMONEY, DAN]

TSC:

This is to inform you that the CCSDK project plans to participate in the 
Casablanca release

Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

[TIMONEY, DAN]

All,

I think perhaps when thinking about the relationship between SDN-R and SDN-C, 
it might be helpful to draw a parallel to OpenDaylight.   OpenDaylight consists 
of many projects (the project list on their Gerrit is 4 pages long, with about 
25 per page – so close to a hundred), but a given deployment of the 
OpenDaylight platform will generally use only a handful of those that it needs 
to implement its specific domain.

I see the SDNC project in ONAP as being similar.  SDNC is the sole Network 
Controller project in ONAP, which contains a set of components that can be used 
for different network domains / functions.   As we add more and more 
functionality over time, we are likely to find that carriers will choose to 
deploy only a subset of those components, or to deploy multiple instances of 
SDNC-based controllers with different components installed/enabled in order to 
segment their traffic load.  We’re not prescribing or proscribing any of those 
deployment options:  we’re just providing a base platform that we’ve tested in 
a specific configuration with specific use cases.


I think perhaps the confusion is that we’ll often use that term SDN-R to refer 
to 2 different things:


  1.  A software development deliverable (Epic) for the ONAP Casablanca 
release, which will deliver a number of new components to SDNC that are useful 
for radio configuration.
  2.  A specific instance of a network controller that uses those components to 
implement radio network configuration.

That first usage above is the work we’re planning for Casablanca.  The second 
is a possible deployment option that we suspect many carriers will choose.  
However, if for whatever reason a carrier wanted to also use that same instance 
to support other functionality, that really just boils down to an engineering 
decision.  Our software architecture won’t require the SDN-R functionality to 
be deployed separately from other SDN functionality.

I hope this helps,

Dan


--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of Parviz Yegani 

Date: Thursday, May 17, 2018 at 5:38 AM
To: Alla Goldner , "Vladimir Yanover (vyanover)" 
, Dhananjay Pavgi , 
"SHANKARANARAYANAN, N K" , 
"onap-usecase...@lists.onap.org" 
Cc: onap-discuss , onap-tsc 

Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Agree with Alla. The name doesn’t matter. You can call it “Pineapple”.

What we need to do is to review the ONF architecture and other relevant specs 
to see if this module, indeed, implements only a subset of the SDN-C functions. 
 I glanced through some of these documents. The good news is like SDNC (and 
APPC) SDNR is also modeled after ODL. This is evident from the many POCs 
conducted by ONF (see the ONF white papers that have been published since 
2015). The same point is also echoed in the project objectives below. It says: 
“Because the controller is based on OpenDaylight, it is consistent with the 
ONAP architecture, and we believe that the majority of the software for the 
applications can be ported into ONAP with only minor modifications.”

Well, the devil is in the details;) We (in ONAP) have to do our due diligence 
to make sure SDNR can leverage SDNC+CCSDK functions to support target use cases 
for both fixed and wireless access scenarios. Some questions may arise. For 
example, how are we going to use the device models developed for RAN equipment 
by BBF (based on TR-069)? This doesn’t exist in ONAP today, AFAIK. We can 
possibly tweak the DG config node in SDNC to adapt to vendor’s SBI 
implementation (proprietary adaptor), similar to what we did for the VoLTE use 
case in R1/Amsterdam. If so, then SDNR would be a better fit for the 3rd party 
controller, sitting below SDNC (as a downstream controller), no?

Said that, we certainly need to figure out how this module fits into the rest 
of the ONAP architecture. Architecture discussion should focus on SDNC (and 
perhaps APPC) functional mapping/alignment with SDNR first. SDNR is designed to 
support multi-vendor equipment (presumably physical devices/PNFs in initial 
deployment phases). If so, then this question crosses one’s mind: Shouldn’t PNF 
PnP support a key requirement for this project?

SDN-R 

Re: [onap-tsc] [Onap-release] [VID][VFC][SO][AAF][AAI][APPC][CCSDK][DCAE][DMAAP][CLAMP][SDNC][SDC][INT][PORTAL][POLICY][MUSIC][MULTICLOUD][MSB] Nexus3 Fix breaks deployment - PTLs please reply to the

[TIMONEY, DAN]

Michael

Please see the comment I just added to this ticket.  This is a much bigger 
issue than just releasing the existing docker containers.  If we can’t use 
snapshot or staging versions of Dockers any longer in integration, you are 
probably going to be looking at an average turnaround for fixes of no better 
than 24 hours (since each and every one will need 2 releases done : first of 
Maven artifact, then a rebuild Docker based on updated Maven, and then finally 
released version of Docker).

Also, if we do as requested and request release builds for our docker 
containers, there is a possibility for discrepancies between our released Maven 
artifacts and released Docker containers.

Due to this potential discrepancy, I think we need to discuss this at our PTL 
call on Monday.  We need to make the TSC aware of this potential discrepancy 
and to go on record accepting that risk.

Dan


--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From:  on behalf of "OBRIEN, FRANK 
MICHAEL" 
Date: Saturday, April 28, 2018 at 5:39 PM
To: onap-discuss , onap-release 
, onap-tsc , 
"helpd...@onap.org" 
Subject: [Onap-release] 
[VID][VFC][SO][AAF][AAI][APPC][CCSDK][DCAE][DMAAP][CLAMP][SDNC][SDC][INT][PORTAL][POLICY][MUSIC][MULTICLOUD][MSB]
 Nexus3 Fix breaks deployment - PTLs please reply to the LF email to release 
your snapshot dockers to return the build to de...


Team,

   Please assist the LF and Gildas to get the snapshot docker images released 
so we can pull again for Beijing deployments

   The list of containers failing because of images unable to pull are listed 
below and in the jira



See JIRA

https://jira.onap.org/browse/CIMAN-157



Check the projects below and reply to the mail below to fix your images

https://lists.onap.org/pipermail/onap-discuss/2018-April/009317.html

PTL?

sniro

common - postgres

smsdb

vault

consul



PTLs verified

vid

vfc

so

aaf

aai

appc

ccsdk

dcae

dmaap

clamp

sdnc

sdc

integration

portal

music

policy

multicloud

msb




(+) proposal - dont wait for PTL approval - we already were running with these 
50 images - just reenable them



All CD deployments fail except those with a proxy

http://jenkins.onap.info/job/oom-cd-master/

http://jenkins.onap.info/job/oom-cd-master2-aws/

passing (with proxy?) 
https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/



(+) before

http://jenkins.onap.info/job/oom-cd-master2-aws/24/console

6

{noformat}

13:25:59 onap  dev-so-db-684dffd45-cmsth  0/1   
ErrImagePull0  1h

13:25:59 onap  dev-smsdb-00/2   
ErrImagePull0  1h

13:25:59 onap  dev-portal-zookeeper-db466fc-lfgf7 0/1   
ErrImagePull0  1h

13:25:59 onap  dev-policydb-5dbb9b54df-ngxwd  0/1   
ErrImagePull0  1h

13:25:59 onap  dev-consul-b5d9d5564-85vn2 0/1   
ErrImagePull0  1h

13:25:59 onap  

Re: [onap-tsc] Review of SDC known vulnerability Analysis

[TIMONEY, DAN]

Steve,

The dgbuilder is a design time tool.  We use it to create and update the 
directed graphs, which then get stored in Gerrit and managed from there as 
source code.

Eventually we’d like to support using the dgbuilder as an editor integrated 
with SDC at run time to update and deploy new versions of directed graphs – 
especially to allow rapid deployment of patches.  However, in its current form, 
dgbuilder is really only appropriate as a design time tool.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

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.

From: Stephen Terrill <stephen.terr...@ericsson.com>
Date: Monday, April 2, 2018 at 3:45 AM
To: "TIMONEY, DAN" <dt5...@att.com>
Cc: "onap-sec...@lists.onap.org" <onap-sec...@lists.onap.org>, onap-tsc 
<onap-tsc@lists.onap.org>
Subject: Review of SDC known vulnerability Analysis

Hi Dan,

Thank-you for the report on the SDC known vulernabilities - 
https://wiki.onap.org/pages/viewpage.action?pageId=28379582<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D28379582=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=x8Wp_D96pTUjVbq-IlNOKq0bcI_Q7jStYYn85kwu5ng=KFQ0VD5WzMK0Uee8vdmax_TTVkvrWD4B7pQUz48a3QI=>
 .

For most of the impacts it states that low risk – only occurs in design tool 
(dgbuilder).  How is this tool used by SDNC?  Is it used in the runtime 
environment, or can it be called in the run-time environment?

Best Regards,

Steve


[Ericsson]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=x8Wp_D96pTUjVbq-IlNOKq0bcI_Q7jStYYn85kwu5ng=dvIuAGk7lYrgBW79T5b84l0tES3M_WCdVC-iSh_iIIw=>


STEPHEN TERRILL
Technology Specialist
POA Architecture and Solutions
Business Unit Digital Services

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=x8Wp_D96pTUjVbq-IlNOKq0bcI_Q7jStYYn85kwu5ng=Rj15sDWPAmSm8uvT67wxWVGcsrSht4bSJlLSwpFoVZ8=>


[http://www.ericsson.com/current_campaign]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_current-5Fcampaign=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=x8Wp_D96pTUjVbq-IlNOKq0bcI_Q7jStYYn85kwu5ng=Hyh61ley0RtumqI-7OhH694lkDNAm2Ikh_WgkctKeag=>

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<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_email-5Fdisclaimer=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=x8Wp_D96pTUjVbq-IlNOKq0bcI_Q7jStYYn85kwu5ng=cvBx3VQtp9l5EsGasxUgp9ZlGJqxAoTDsEAllFjqIWk=>

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

Re: [onap-tsc] Outcomes of Usecase subcommittee meeting today

[TIMONEY, DAN]

Alla,

FYI - none of the authors of the functional requirements contacted me as PTL of 
CCSDK or SDNC.   Does that mean that neither of my projects is impacted, or are 
they just behind schedule?

Dan




--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of Alla Goldner 

Date: Wednesday, December 13, 2017 at 8:00 PM
To: "onap-usecase...@lists.onap.org" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] Outcomes of Usecase subcommittee meeting today

Hi all,

Thanks a lot to those attending our meeting today, both f2f and in remote 
mode!!!

Here is the summary/list of action items:


  1.  Needed to have contact person details per each requirement – Alla to 
provide (in the attached)
  2.  Scaling out requirement is merged with auto/manual scaling requirement, 
assuming both VFC and APPC support
  3.  Enhancements for service onboarding requirement merges with PNF support 
requirement
  4.  5G task force ned to discuss VFC support with VFC team, as currently this 
is missing from the table of affected entities
  5.  The next level of details for discussions with PTLs must be provided by 
the requirements authors and this should include, at least:
 *   Sequence diagrams
 *   VNFs
 *   Full list of involved companies (in terms of number of developers each 
company is willing to put on the specific development)
 *   Model information
 *   Description of how the requirement will be tested
 *   APIs (existing and new) – nice to have, if information is available
  6.  It is up to requirements’ authors to have discussions with PTLs during 
the next week (as the following one is Christmas Holidays). PTLs must get all 
information related to specific functional requirements (as per described 
above) and discuss it with the teams by the end of the next week, so, when they 
come back from Christmas vacation (January 2nd), they can analyze and discuss 
it with their teams, and come up with their estimations by January 8th. By 
January 18 (during the following 10 days) they will need to build harmonized 
view on all functional requirements plus S3P, and define what they can 
implement.

Those requirements which will not be discussed with PTLs next week will be 
defined as a stretch goal.

Monday’s Usecase subcommittee meeting will be dedicated to review the 
additional information available by Monday. We can also use some of the meeting 
time for discussions with the PTLs, if requirements team makes sure PTL attends 
our call.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D37B3E.1C631280]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Outcomes of Usecase subcommittee meeting today

[TIMONEY, DAN]

Alla,

Just to clarify, there’s also this larger list on the wiki: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates

I was assuming (maybe wrongly?) that the 12 requirements presented in that 
spreadsheet are sort of higher level requirements that summarize those 60.   If 
so, can we ask for an updated spreadsheet that has an additional column with a 
list of requirement numbers from the wiki page covered by each item?   I think 
that would be very helpful to us PTLs as we evaluate what resources we’ll need 
to meet these for Beijing.

Thanks!
Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of Alla Goldner 

Date: Wednesday, December 13, 2017 at 8:00 PM
To: "onap-usecase...@lists.onap.org" 
Cc: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] Outcomes of Usecase subcommittee meeting today

Hi all,

Thanks a lot to those attending our meeting today, both f2f and in remote 
mode!!!

Here is the summary/list of action items:


  1.  Needed to have contact person details per each requirement – Alla to 
provide (in the attached)
  2.  Scaling out requirement is merged with auto/manual scaling requirement, 
assuming both VFC and APPC support
  3.  Enhancements for service onboarding requirement merges with PNF support 
requirement
  4.  5G task force ned to discuss VFC support with VFC team, as currently this 
is missing from the table of affected entities
  5.  The next level of details for discussions with PTLs must be provided by 
the requirements authors and this should include, at least:
 *   Sequence diagrams
 *   VNFs
 *   Full list of involved companies (in terms of number of developers each 
company is willing to put on the specific development)
 *   Model information
 *   Description of how the requirement will be tested
 *   APIs (existing and new) – nice to have, if information is available
  6.  It is up to requirements’ authors to have discussions with PTLs during 
the next week (as the following one is Christmas Holidays). PTLs must get all 
information related to specific functional requirements (as per described 
above) and discuss it with the teams by the end of the next week, so, when they 
come back from Christmas vacation (January 2nd), they can analyze and discuss 
it with their teams, and come up with their estimations by January 8th. By 
January 18 (during the following 10 days) they will need to build harmonized 
view on all functional requirements plus S3P, and define what they can 
implement.

Those requirements which will not be discussed with PTLs next week will be 
defined as a stretch goal.

Monday’s Usecase subcommittee meeting will be dedicated to review the 
additional information available by Monday. We can also use some of the meeting 
time for discussions with the PTLs, if requirements team makes sure PTL attends 
our call.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D374CE.3E084250]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Amsterdam Branching Timeline

[TIMONEY, DAN]

Kenny,

Excellent - what service!

Thanks much,
Dan

Sent from MyOwn, an AT BYOD solution.




From: "Kenny Paul" <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>
Date: Thursday, November 16, 2017 at 5:08:06 PM
To: "TIMONEY, DAN" <dt5...@att.com<mailto:dt5...@att.com>>
Cc: "onap-tsc" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>, 
"Jeremy Phelps" 
<jphe...@linuxfoundation.org<mailto:jphe...@linuxfoundation.org>>
Subject: Re: [onap-tsc] Amsterdam Branching Timeline

Hi Dan,

yes the LF will handle that.

Best Regards,
-kenny

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

On Nov 16, 2017, at 1:22 PM, TIMONEY, DAN 
<dt5...@att.com<mailto:dt5...@att.com>> wrote:

Kenny,

After the release branches are created, we’ll also need to create new Jenkins 
jobs to compile against the new release branch.  Is that the responsibility of 
each project team, or was LF planning to handle that?

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

Re: [onap-tsc] Amsterdam Branching Timeline

[TIMONEY, DAN]

Kenny,

After the release branches are created, we’ll also need to create new Jenkins 
jobs to compile against the new release branch.  Is that the responsibility of 
each project team, or was LF planning to handle that?

Thanks!
Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of Kenny Paul 

Date: Thursday, November 16, 2017 at 4:06 PM
To: onap-tsc 
Cc: Jeremy Phelps 
Subject: [onap-tsc] Amsterdam Branching Timeline

Here is the plan from Rel-Eng  for branching

Short answer-  completed by EOD pacific tomorrow at the very latest.
-Jeremy is working on dockerhub +  1/2 branching
-Jess is working on pending requests, any new requests  + 1/2 branching

Tasks per repo X 193 repos :
- branching creation from the last released tag
- 2 
version.properties
 and pom file gerrit changes.
 (Must be merged by the dev teams since LF doesn't have rights to do so)
- 1 change for the master branch
  - 1 change for the new amsterdam branch
Best Regards,
-kenny

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

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

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

[TIMONEY, DAN]

All,

I wanted to second Lusheng’s excellent comments below, and add perhaps a bit 
more.

I think it’s important to bear in mind that some of the code that is 
contributed might not be entirely new.  For example, much of the seed code that 
we submitted for openecomp was existing code that we had developed and used 
internally within AT and then open sourced.   It is likely that we’ll come 
across similar examples as ONAP continues to evolve, where one company or 
another finds that they have existing code that can be integrated into ONAP 
that they would like to contribute.   So, while we absolutely should encourage 
developers to add code in small increments as they’re working (upstream first) 
but we should also not ask them to expend extra effort to break up 
contributions they’d like to make to meet some imposed limitation on number of 
lines.   Instead, perhaps there is some other process that should be followed 
for such commits (e.g. some comments within the commit message indicating this 
code is in use today by company X and is being contributed to ONAP?).. I’m sure 
other open source projects have had similar block commits, so it would be good 
to hear how other projects handle those types of contributions.

Dan

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

From:  on behalf of "JI, LUSHENG" 

Date: Friday, August 4, 2017 at 1:43 AM
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Dear TSC and ONAP community,

As I am reading through this thread, I can certainly appreciate David’s good 
intention behind the suggestion.  Perhaps this is a minority opinion here, but 
as a PTL and committer I have to say I am also concerned about “enforcing” 
things such as hard limit on submission LOC.


  1.  Contributions come in the shapes that they are in.  Some large some 
small.  Putting a submission size limit will not change that, but it would 
impact the integrity of large contributions though.  Say someone wants to 
contribute a new complex function but LOC too large, it is not like he would be 
able to break this one large contribution into several smaller contributions.  
The more likely outcome is that he will simply break the contribution into 
several smaller commits, each smaller than the LOC limit but only fragment of 
the original contribution file tree.  This would make committer’s job much 
harder because he now must review ALL of these commits together, equal amount 
of LOC, and spread in multiple submissions.  Individual commits like these 
cannot be reviewed individually effectively because it is difficult to assess 
its value to the whole project, without mentioning that individual submission 
may even break the CICD and testing of the project.
  2.  The “commit small commit often” practice of devops really relies on the 
rich support of features and branches of git.  We essentially have ONLY ONE 
branch, the master.  This is the key reason for why I am not sure we should 
follow the devops manual to a tee here.  None of those sophisticated branching 
workflows is applicable here.  ONAP gerrit is not best suited for being used as 
dev repo.  With this limitation, I would much prefer to have the head of master 
branch relatively clean and stable, only advanced by good quality, tested, and 
self-contained contributions, not by work-in-progress fragments.
  3.  Large submission does not necessarily equal to behind-door development.  
Gitlab is cheap.  Self-formed herds, even individual ONAP projects, can set up 
their own git server and apply all fancy workflows there, then make the whole 
contribution to ONAP when they are ready.  I actually believe this is more 
community based development.
  4.  Studies show that there is a loglog relationship between number of 
submissions and submission sizes for open source commits.  Large submissions do 
happen, but are rare.  We only see more of those now because we are pre-R1, 
many contributions are ports from OpenO, OpenECOMP, or member companies own 
code.  As ONAP grows, more and more code will be developed along with ONAP, and 
I have no doubt we will see fewer and fewer mega submissions.



  1.  With all the above said, I do wish that it would be great if the 36 hour 
review deadline rule can be flexible based on submission size.

Thank you for reading.

Lusheng
ONAP DCAE

From:  on behalf of Stephen Terrill 

Date: Thursday, August 3, 2017 at 1:42 PM
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] Enforcing an "Upstream