Hi Brian,

My suggestion is to update this the project definition to include this: 
https://wiki.onap.org/display/DW/Logging+Enhancements+Project+Proposal.  This 
enables a clean project definition for approval (supporting material as you 
have done to explain why is still appreciated).

Just a question, in the deliverables section, is there parts of that that are 
release invariant.  My personal view is that the project definition shouldn't 
have to change from release to release if there is not scope change to the 
project; and to do so in case there is scope change to the project as in this 
case; meaning that the parts that are release variant could be shortened (just 
a personal opinion).

Best, Regards,

Steve.

From: onap-tsc-boun...@lists.onap.org <onap-tsc-boun...@lists.onap.org> On 
Behalf Of Michael O'Brien
Sent: Wednesday, June 13, 2018 7:29 PM
To: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: [onap-tsc] [LOG] Logging scope change for POMBA TSC vote (post 
orchestration model based audit)

Team,
   Heads up for the next TSC meeting - I added an item for a vote on expanding 
the scope of the logging-analytics project for POMBA (post orchestration model 
based audit)
   Jon Fannar Karlsson Taylor and Sharon Chisholm have hosted two 1 hour 
meetings over the last 3 weeks with the Architecture Subcommittee on Tuesdays.
   There are notes from both meetings and a faq below for your reference.


The POMBA (post orchestration model based audit) has had 2 meetings with the 
Architecture subcommittee detailed on

Logging Scope Change for POMBA seed 
code<https://wiki.onap.org/display/DW/Logging+Scope+Change+for+POMBA+seed+code>

Frequently Asked 
Questions<https://wiki.onap.org/display/DW/Frequently+Asked+Questions>

The last meeting gave the OK to start working in the logging-analytics repo 
from the arch and security principals.
https://wiki.onap.org/display/DW/TSC+2018-06-14+Meeting+Agenda


thank you
/michael
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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to