Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and functional requirements

[David McBride]

Hi Steve,

My intent was to begin doing that for the Frankfurt release; however, I'm
aware that it can take some time to turn a big ship.  How difficult would
it be to put those requirements into REQ?

David

On Thu, Aug 22, 2019 at 12:34 PM Stephen Terrill <
stephen.terr...@ericsson.com> wrote:

> Hi David,
>
>
>
> I think it’s a good idea as an ambition, For which release were you
> thinking that this should be applied.  I ask as in the Architecture
> sub-committee we have been capturing the architecture lead requirements
> (which are not too many but some) in that JIRA project currently, and have
> a link to that from the release requirement list, and that is they way I
> have requested for Frankfurt as well.
>
>
>
> BR,
>
>
>
> Steve
>
> *From:* onap-tsc@lists.onap.org  *On Behalf Of *David
> McBride via Lists.Onap.Org
> *Sent:* Thursday, 22 August 2019 19:54
> *To:* Scott Blandford 
> *Cc:* Alla Goldner ;
> onap-usecase...@lists.onap.org; onap-tsc@lists.onap.org
> *Subject:* Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases
> and functional requirements
>
>
>
> Team,
>
>
>
> I didn't realize that Alla was going to send that mail. I've been working
> on a process for documenting requirements in JIRA.  I was going to roll it
> out a little later, but since Alla pushed the issue, let's go with it.
>
>
>
> Overview:
>
>- I setup a new JIRA project called "Release Requirements (REQ)",
>where I expect all requirements issues to be created.
>- I created a template for new release requirements from which I
>expect all requirements JIRA issues to be cloned (REQ-1
>
> 
>).
>- I drafted some instructions
>
> 
>for creating new requirements issues.
>
> I still have some things to figure out around workflow, but I think that
> we have enough to get started. I'd be interested in your feedback on this
> proposal.
>
>
>
> David
>
>
>
> On Thu, Aug 22, 2019 at 10:03 AM Scott Blandford  wrote:
>
> Alla,
>
> Under which project should the Use Case JIRAs be registered?
>
>
>
> Scott Blandford
>
>
>
> *From:* onap-usecase...@lists.onap.org  *On
> Behalf Of *Alla Goldner
> *Sent:* Thursday, August 22, 2019 11:25 AM
> *To:* onap-usecase...@lists.onap.org
> *Cc:* onap-tsc@lists.onap.org
> *Subject:* Re: [Onap-usecasesub] JIRA entries for use cases and
> functional requirements
>
>
>
> Resending – got error message of “undeliverable mail”
>
>
>
> *From:* Alla Goldner
> *Sent:* Thursday, August 22, 2019 6:06 PM
> *To:* onap-usecase...@lists.onap.org
> *Cc:* onap-tsc@lists.onap.org
> *Subject:* JIRA entries for use cases and functional requirements
>
>
>
> Hi all,
>
>
>
> It was communicated during today’s TSC call that documenting all use cases
> and associated requirements should be done in JIRA, starting from Frankfurt
> Release.. The idea is to be able to replace the release requirements tables
> in the wiki with a JIRA dashboard, so it would be easier and shorten
> processes for PTLs.
>
>
>
> Requirements owners – *please document your newly proposed requirements
> for Frankfurt in JIRA ASAP*, as presence/lack of the requirement
> fulfillment may become one of prioritization criteria.
>
>
>
> Best Regards, Alla
>
> *This email and the information contained herein is proprietary and
> confidential and subject to the Amdocs Email Terms of Service, which you
> may review at* *https://www.amdocs.com/about/email-terms-of-service*
> 
>
>
>
>
> --
>
> *David McBride*
>
> Release Manager, OPNFV
>
> Mobile: +1.805.276.8018
>
> Email/Google Talk: dmcbr...@linuxfoundation.org
>
> Skype: davidjmcbride1
>
> IRC: dmcbride
>
> 
>
>

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride

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

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

Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and functional requirements

[Stephen Terrill]

Hi David,

I think it’s a good idea as an ambition, For which release were you thinking 
that this should be applied.  I ask as in the Architecture sub-committee we 
have been capturing the architecture lead requirements (which are not too many 
but some) in that JIRA project currently, and have a link to that from the 
release requirement list, and that is they way I have requested for Frankfurt 
as well.

BR,

Steve
From: onap-tsc@lists.onap.org  On Behalf Of David 
McBride via Lists.Onap.Org
Sent: Thursday, 22 August 2019 19:54
To: Scott Blandford 
Cc: Alla Goldner ; onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and 
functional requirements

Team,

I didn't realize that Alla was going to send that mail. I've been working on a 
process for documenting requirements in JIRA.  I was going to roll it out a 
little later, but since Alla pushed the issue, let's go with it.

Overview:

  *   I setup a new JIRA project called "Release Requirements (REQ)", where I 
expect all requirements issues to be created.
  *   I created a template for new release requirements from which I expect all 
requirements JIRA issues to be cloned 
(REQ-1).
  *   I drafted some 
instructions
 for creating new requirements issues.
I still have some things to figure out around workflow, but I think that we 
have enough to get started. I'd be interested in your feedback on this proposal.

David

On Thu, Aug 22, 2019 at 10:03 AM Scott Blandford 
mailto:cb1...@att.com>> wrote:
Alla,
Under which project should the Use Case JIRAs be registered?

Scott Blandford

From: onap-usecase...@lists.onap.org 
mailto:onap-usecase...@lists.onap.org>> On 
Behalf Of Alla Goldner
Sent: Thursday, August 22, 2019 11:25 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: Re: [Onap-usecasesub] JIRA entries for use cases and functional 
requirements

Resending – got error message of “undeliverable mail”

From: Alla Goldner
Sent: Thursday, August 22, 2019 6:06 PM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: JIRA entries for use cases and functional requirements

Hi all,

It was communicated during today’s TSC call that documenting all use cases and 
associated requirements should be done in JIRA, starting from Frankfurt 
Release.. The idea is to be able to replace the release requirements tables in 
the wiki with a JIRA dashboard, so it would be easier and shorten processes for 
PTLs.

Requirements owners – please document your newly proposed requirements for 
Frankfurt in JIRA ASAP, as presence/lack of the requirement fulfillment may 
become one of prioritization criteria.

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


--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride


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

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

Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and functional requirements

[David McBride]

Team,

I didn't realize that Alla was going to send that mail. I've been working
on a process for documenting requirements in JIRA.  I was going to roll it
out a little later, but since Alla pushed the issue, let's go with it.

Overview:

   - I setup a new JIRA project called "Release Requirements (REQ)", where
   I expect all requirements issues to be created.
   - I created a template for new release requirements from which I expect
   all requirements JIRA issues to be cloned (REQ-1
   ).
   - I drafted some instructions
   
   for creating new requirements issues.

I still have some things to figure out around workflow, but I think that we
have enough to get started. I'd be interested in your feedback on this
proposal.

David

On Thu, Aug 22, 2019 at 10:03 AM Scott Blandford  wrote:

> Alla,
>
> Under which project should the Use Case JIRAs be registered?
>
>
>
> Scott Blandford
>
>
>
> *From:* onap-usecase...@lists.onap.org  *On
> Behalf Of *Alla Goldner
> *Sent:* Thursday, August 22, 2019 11:25 AM
> *To:* onap-usecase...@lists.onap.org
> *Cc:* onap-tsc@lists.onap.org
> *Subject:* Re: [Onap-usecasesub] JIRA entries for use cases and
> functional requirements
>
>
>
> Resending – got error message of “undeliverable mail”
>
>
>
> *From:* Alla Goldner
> *Sent:* Thursday, August 22, 2019 6:06 PM
> *To:* onap-usecase...@lists.onap.org
> *Cc:* onap-tsc@lists.onap.org
> *Subject:* JIRA entries for use cases and functional requirements
>
>
>
> Hi all,
>
>
>
> It was communicated during today’s TSC call that documenting all use cases
> and associated requirements should be done in JIRA, starting from Frankfurt
> Release.. The idea is to be able to replace the release requirements tables
> in the wiki with a JIRA dashboard, so it would be easier and shorten
> processes for PTLs.
>
>
>
> Requirements owners – *please document your newly proposed requirements
> for Frankfurt in JIRA ASAP*, as presence/lack of the requirement
> fulfillment may become one of prioritization criteria.
>
>
>
> Best Regards, Alla
>
> *This email and the information contained herein is proprietary and
> confidential and subject to the Amdocs Email Terms of Service, which you
> may review at* *https://www.amdocs.com/about/email-terms-of-service*
> 
>
> 
>
>

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride

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

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

Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and functional requirements

[Scott Blandford]

Alla,
Under which project should the Use Case JIRAs be registered?

Scott Blandford

From: onap-usecase...@lists.onap.org  On Behalf 
Of Alla Goldner
Sent: Thursday, August 22, 2019 11:25 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: Re: [Onap-usecasesub] JIRA entries for use cases and functional 
requirements

Resending - got error message of "undeliverable mail"

From: Alla Goldner
Sent: Thursday, August 22, 2019 6:06 PM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: JIRA entries for use cases and functional requirements

Hi all,

It was communicated during today's TSC call that documenting all use cases and 
associated requirements should be done in JIRA, starting from Frankfurt 
Release.. The idea is to be able to replace the release requirements tables in 
the wiki with a JIRA dashboard, so it would be easier and shorten processes for 
PTLs.

Requirements owners - please document your newly proposed requirements for 
Frankfurt in JIRA ASAP, as presence/lack of the requirement fulfillment may 
become one of prioritization criteria.

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


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

View/Reply Online (#5373): https://lists.onap.org/g/onap-tsc/message/5373
Mute This Topic: https://lists.onap.org/mt/32991994/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] JIRA entries for use cases and functional requirements

[Alla Goldner]

Hi all,

It was communicated during today's TSC call that documenting all use cases and 
associated requirements should be done in JIRA, starting from Frankfurt 
Release.. The idea is to be able to replace the release requirements tables in 
the wiki with a JIRA dashboard, so it would be easier and shorten processes for 
PTLs.

Requirements owners - please document your newly proposed requirements for 
Frankfurt in JIRA ASAP, as presence/lack of the requirement fulfillment may 
become one of prioritization criteria.

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


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

View/Reply Online (#5372): https://lists.onap.org/g/onap-tsc/message/5372
Mute This Topic: https://lists.onap.org/mt/32990970/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] JIRA entries for use cases and functional requirements

[Alla Goldner]

Resending - got error message of "undeliverable mail"

From: Alla Goldner
Sent: Thursday, August 22, 2019 6:06 PM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: JIRA entries for use cases and functional requirements

Hi all,

It was communicated during today's TSC call that documenting all use cases and 
associated requirements should be done in JIRA, starting from Frankfurt 
Release.. The idea is to be able to replace the release requirements tables in 
the wiki with a JIRA dashboard, so it would be easier and shorten processes for 
PTLs.

Requirements owners - please document your newly proposed requirements for 
Frankfurt in JIRA ASAP, as presence/lack of the requirement fulfillment may 
become one of prioritization criteria.

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


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

View/Reply Online (#5371): https://lists.onap.org/g/onap-tsc/message/5371
Mute This Topic: https://lists.onap.org/mt/32990970/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] Request: Joss Armstrong step down an APPC committer

[Taka Cho]

Dear TSC member,

I am officially removing Joss Armstrong@Ericsson from the APPC committer due to 
internal Reorganization, Please see the attached email.

Sorry for the late request

Taka Cho
APPC PTL

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

View/Reply Online (#5370): https://lists.onap.org/g/onap-tsc/message/5370
Mute This Topic: https://lists.onap.org/mt/32989931/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]
-=-=-=-=-=-=-=-=-=-=-=-

--- Begin Message ---
Hi Taka,



I can reaffirm you that Joss is moved out of ONAP. Unfortunately due to IPR 
issues Ericsson employees cannot continue to work in Open source technology 
unless they move to EST (Ericsson Software Technology a newly formed Ericsson 
subsidiary company). However it is the discretion of the employee to choose and 
Joss preferred to stay in Ericsson. This was a hard decision for Joss and he 
expressed his gratitude for the opportunity provided to work in ONAP. We didn't 
communicate this sooner as it was a personal decision for Joss and it was not 
our business to preempt his decision.

In the future all contributions from Ericsson should be coming through the EST 
company so hopefully we avoid future poor communication as happened in this 
case.



Br,

Lathish

--- End Message ---

Re: [onap-tsc] Committer Promotion Request for [logging-analytics]

[Prudence Au]

Hello Catherine,

Yes Lee Breslau is no longer an active committer, however, I did include him in 
the email but didn't receive a response.

Thanks,
Prudence


From: onap-tsc@lists.onap.org  on behalf of Catherine 
LEFEVRE 
Sent: August 22, 2019 6:11 AM
To: Prudence Au ; onap-tsc ; 
jba...@linuxfoundation.org 
Subject: Re: [onap-tsc] Committer Promotion Request for [logging-analytics]


Good morning Prudence,



I have reviewed your committer’s request.

Can you please confirm that Lee Breslau is no more an active committer and this 
is why he did not provide his vote?



Many thanks & regards

Catherine



From: Prudence Au [mailto:prudence...@amdocs.com]
Sent: Tuesday, August 20, 2019 3:01 PM
To: onap-tsc ; Lefevre, Catherine 
; jba...@linuxfoundation.org
Subject: Committer Promotion Request for [logging-analytics]



Hi TSC,



The logging-analytics team would like to promote Pierre Rioux as a committer.  
The supporting page can be found: 
https://wiki.onap.org/pages/viewpage.action?pageId=58232905



Thanks,

Prudence Au

PTL - logging-analytics

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


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


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

View/Reply Online (#5369): https://lists.onap.org/g/onap-tsc/message/5369
Mute This Topic: https://lists.onap.org/mt/32967133/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 Sonar Waiver Requests

[Jim Baker]

The current status of each is:

AAF – Need confirmation – Target is to reach 45% by end of El-Alto? What’s
the current status today? = Line coverage 46.1%

 Policy – Need clarification – what’s the current status and what’s the
target plan for El-Alto = Line coverage 51.2%

 Portal - Need clarification – what’s the current status and what’s the
target plan for El-Alto = Line coverage 21.7%

On Thu, Aug 22, 2019 at 4:35 AM Catherine LEFEVRE <
catherine.lefe...@intl.att.com> wrote:

> Good morning Jim,
>
>
>
> Please find my feedback
>
> ·CCSDK – +1 – great progress – keep going
>
> ·AAF – Need confirmation – Target is to reach 45% by end of
> El-Alto? What’s the current status today?
>
> ·Policy – Need clarification – what’s the current status and
> what’s the target plan for El-Alto
>
> ·Portal - Need clarification – what’s the current status and
> what’s the target plan for El-Alto
>
> ·OOF - fgps - fgps is not being released in El Alto
>
> Need clarification.
>
> Will it be used for Frankfurt? Will the associated artifacts remove from
> the OOF El Alto container?
>
>
>
> Many thanks & regards
>
> Catherine
>
>
>
> *From:* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *On
> Behalf Of *Jim Baker
> *Sent:* Monday, August 19, 2019 10:47 PM
> *To:* onap-tsc 
> *Subject:* [onap-tsc] ONAP Sonar Waiver Requests
>
>
>
> Folks, Below are the set of waiver requests that I've collected for the El
> Alto release. There is one more for Multicloud that we'll hear from at the
> TSC. Please review these and ask any questions of the respective PTLs. I'll
> ask for approval later this week.
>
> Jim
>
>
>
> =
>
> El Alto Sonar Waivers
> CCSDK
>
>
>
> I need to request a waiver for the CCSDK ccsdk/dashboard repository.   As
> you know, this repository was at 69.1% coverage before javascript was
> added.  After javascript was added, coverage dropped to 16.9%.
>
>
>
> We have been able to get the line coverage on that repository up to
> 41.5%.  We are not likely to be able to improve further on that due to
> resource limitations.  Our plan would be to get back to 55% line coverage
> in the Frankfurt release timeframe.  Of course, if we can improve sooner,
> we will, but at this time the best we can commit to would be Frankfurt.
>
>
>
>
> AAF
>
>
>
>   There is no real chance for AAF to increase its JUnits to 55% for El Alto
>
>   The reasons for this are:
>
> ·AAF has a very big resource shortage.
>
> o   The only people contributing REAL code is Sai Gandham and I.  There
> are other Contributors, but they are just working Sonar reported "Concerns".
>
> o   AT&T has only funded a ".8" person for ONAP, so, according to AT&T
> rules, we can only spend 40% of our time on ONAP (though, frankly, I
> contribute a lot more)
>
> o   Sai will be on 3 weeks vacation soon
>
> o   I am SUPPOSED to have Vacation soon.  I have had no break this year
> whatsoever.
>
> ·AAF has massive ONAP required changes already in play
>
> o   Release process has changed
>
> o   There is a new Staging Process/env
>
> o   OOM is being redone
>
> ·Additionally, I am committed to improving Security for all ONAP
> Apps
>
> o   OUT of the "manual Cert" process
>
> o   INTO the Auto-Gen of Configs and Certs at runtime
>
> o   These two elements make ONAP MORE Secure by
>
> §  NOT putting Certs in Repos
>
> §  2-way TLS Authentication is Configured in from the start
>
> §  MORE Apps can move forward on Security, since they don't have to
> understand
>
> ·For that reason, I'm asking only to be working on IMPROVEMENT,
> which may be 45%, but given our absences, it may be hard to promise 50%.
>
> ·HOWEVER, also part of the Plan is that I have already undertaken
> to figure out if there is a way to accelerate this work, even with 25-40%
> Contractor to do the work.
>
> o   I analyzed WHERE the code could really benefit from JUnits
>
> o   Not surprisingly, all the people working so far we working "Low
> Hanging Fruit".  There's not much left at the bottom branches.
>
> o   THEREFORE, I undertook to develop and demonstrate one of the HARDEST
> areas to Junit, and while it took me more than a Day, I was able to
>
> §  Develop an Inheritance Strategy and code REUSE strategy so that Good
> Junits in the most important/least number of JUnits can be built faster and
> more effectively
>
> §  I found additional APIs in the JUnit tool which allows us to more
> easily Isolate the DB, without losing access to the reusable Helper
> Functions critical for AAF Use.
>
> §  This strategy also provides MORE coverage of critical code per JUnit,
> which should make percentages rise faster.
>
> §  I already showed this to Sai, who will be utilizing when he's not on
> vacation.
>
>
>
> I hope these plans will show a path forward that gets us out of JUnit
> issues faster.
>
>
> Policy
>
>
>
> Regarding the TSC call today and the policy/engine coverage dropping below
> 55% due to Javascript coverag

Re: [onap-tsc] SDC repositories follow-up

[Catherine LEFEVRE]

Good morning Ofir,

I have added your request to today's TSC agenda so we can finalize it.

Best regards
Catherine

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

View/Reply Online (#5366): https://lists.onap.org/g/onap-tsc/message/5366
Mute This Topic: https://lists.onap.org/mt/32931347/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 Sonar Waiver Requests

[Catherine LEFEVRE]

Good morning Jim,

Please find my feedback

·CCSDK – +1 – great progress – keep going

·AAF – Need confirmation – Target is to reach 45% by end of El-Alto? 
What’s the current status today?

·Policy – Need clarification – what’s the current status and what’s the 
target plan for El-Alto

·Portal - Need clarification – what’s the current status and what’s the 
target plan for El-Alto

·OOF - fgps - fgps is not being released in El Alto

Need clarification.

Will it be used for Frankfurt? Will the associated artifacts remove from the 
OOF El Alto container?

Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of Jim 
Baker
Sent: Monday, August 19, 2019 10:47 PM
To: onap-tsc 
Subject: [onap-tsc] ONAP Sonar Waiver Requests

Folks, Below are the set of waiver requests that I've collected for the El Alto 
release. There is one more for Multicloud that we'll hear from at the TSC. 
Please review these and ask any questions of the respective PTLs. I'll ask for 
approval later this week.
Jim

=

El Alto Sonar Waivers

CCSDK



I need to request a waiver for the CCSDK ccsdk/dashboard repository.   As you 
know, this repository was at 69.1% coverage before javascript was added.  After 
javascript was added, coverage dropped to 16.9%.



We have been able to get the line coverage on that repository up to 41.5%.  We 
are not likely to be able to improve further on that due to resource 
limitations.  Our plan would be to get back to 55% line coverage in the 
Frankfurt release timeframe.  Of course, if we can improve sooner, we will, but 
at this time the best we can commit to would be Frankfurt.





AAF



  There is no real chance for AAF to increase its JUnits to 55% for El Alto

  The reasons for this are:

·AAF has a very big resource shortage.

o   The only people contributing REAL code is Sai Gandham and I.  There are 
other Contributors, but they are just working Sonar reported "Concerns".

o   AT&T has only funded a ".8" person for ONAP, so, according to AT&T rules, 
we can only spend 40% of our time on ONAP (though, frankly, I contribute a lot 
more)

o   Sai will be on 3 weeks vacation soon

o   I am SUPPOSED to have Vacation soon.  I have had no break this year 
whatsoever.

·AAF has massive ONAP required changes already in play

o   Release process has changed

o   There is a new Staging Process/env

o   OOM is being redone

·Additionally, I am committed to improving Security for all ONAP Apps

o   OUT of the "manual Cert" process

o   INTO the Auto-Gen of Configs and Certs at runtime

o   These two elements make ONAP MORE Secure by

§  NOT putting Certs in Repos

§  2-way TLS Authentication is Configured in from the start

§  MORE Apps can move forward on Security, since they don't have to understand

·For that reason, I'm asking only to be working on IMPROVEMENT, which 
may be 45%, but given our absences, it may be hard to promise 50%.

·HOWEVER, also part of the Plan is that I have already undertaken to 
figure out if there is a way to accelerate this work, even with 25-40% 
Contractor to do the work.

o   I analyzed WHERE the code could really benefit from JUnits

o   Not surprisingly, all the people working so far we working "Low Hanging 
Fruit".  There's not much left at the bottom branches.

o   THEREFORE, I undertook to develop and demonstrate one of the HARDEST areas 
to Junit, and while it took me more than a Day, I was able to

§  Develop an Inheritance Strategy and code REUSE strategy so that Good Junits 
in the most important/least number of JUnits can be built faster and more 
effectively

§  I found additional APIs in the JUnit tool which allows us to more easily 
Isolate the DB, without losing access to the reusable Helper Functions critical 
for AAF Use.

§  This strategy also provides MORE coverage of critical code per JUnit, which 
should make percentages rise faster.

§  I already showed this to Sai, who will be utilizing when he's not on 
vacation.



I hope these plans will show a path forward that gets us out of JUnit issues 
faster.

Policy



Regarding the TSC call today and the policy/engine coverage dropping below 55% 
due to Javascript coverage.



We have assigned one SME resource to working on this as soon as he is free from 
current requirements. There is a possibility other resources from Bell Canada 
will be able to help. And we will see if others can jump in on it.



The JIRA for this work is covered here: 
https://jira.onap.org/browse/POLICY-1937



This repo has both Java and Javascript.

· The Java coverage is >55%, but extremely difficult to move the needle 
on this repo 

Re: [onap-tsc] Modeling project Committer Promotion Requests

[Catherine LEFEVRE]

Good morning DENG Hui,

I have reviewed your request and approve it.
Can I ask you to update the wiki page accordingly and create a similar table 
than onap-gerrot-modeling-committers, 
onap-gerrit-modeling-javatoscachecker-committers etc
to capture the committers for the generic-parser? Thanks
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling

Congratulations Maopeng !

[cid:image001.jpg@01D558E4.DF110500]

Many thanks and regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
denghui (L)
Sent: Tuesday, August 20, 2019 9:45 AM
To: onap-tsc@lists.onap.org; Jim Baker ; Lefevre, 
Catherine 
Cc: zhang.maope...@zte.com.cn
Subject: [onap-tsc] Modeling project Committer Promotion Requests

Dear TSC,

I'd like to kindly request your review one committer promotion request for the 
repo of modeling/genericparser
Maopeng was the original seed code contributor in genericparser/catalog  of 
VFC, now genericparser/catalog has moved to independent modeling project, 
Maopeng also contributed genericparser/catalog in modeling project.


*Maopeng Zhang, ZTE: 
https://wiki.onap.org/display/DW/Maopeng+Zhang%3A+New+Committer+Promotion+Request+for+Modeling+genericparser

Thanks and regards,

DENG Hui


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

View/Reply Online (#5364): https://lists.onap.org/g/onap-tsc/message/5364
Mute This Topic: https://lists.onap.org/mt/32965143/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 [logging-analytics]

[Catherine LEFEVRE]

Good morning Prudence,

I have reviewed your committer's request.
Can you please confirm that Lee Breslau is no more an active committer and this 
is why he did not provide his vote?

Many thanks & regards
Catherine

From: Prudence Au [mailto:prudence...@amdocs.com]
Sent: Tuesday, August 20, 2019 3:01 PM
To: onap-tsc ; Lefevre, Catherine 
; jba...@linuxfoundation.org
Subject: Committer Promotion Request for [logging-analytics]


Hi TSC,



The logging-analytics team would like to promote Pierre Rioux as a committer.  
The supporting page can be found: 
https://wiki.onap.org/pages/viewpage.action?pageId=58232905



Thanks,

Prudence Au

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

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

View/Reply Online (#5363): https://lists.onap.org/g/onap-tsc/message/5363
Mute This Topic: https://lists.onap.org/mt/32967133/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] SO PTL Election results

[Catherine LEFEVRE]

Congratulations Seshu !

Can I ask you to update the following wiki page accordingly? Thank you
https://wiki.onap.org/display/DW/Voting+Results+History

Best regards
Catherine

From: Seshu m [mailto:seshu.kuma...@huawei.com]
Sent: Thursday, August 22, 2019 8:59 AM
To: onap-tsc@lists.onap.org
Cc: Lefevre, Catherine ; Jim Baker 
(jba...@linuxfoundation.org) 
Subject: SO PTL Election results

Dear ONAP TSC,

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

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

Current SO PTL  Seshu 
(seshu.kuma...@huawei.com) is re-elected.


Thanks and Regards,
M Seshu Kumar
Senior System Architect
Single OSS India Branch Department. S/W BU.
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---


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

View/Reply Online (#5362): https://lists.onap.org/g/onap-tsc/message/5362
Mute This Topic: https://lists.onap.org/mt/32987517/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]
-=-=-=-=-=-=-=-=-=-=-=-