Dear TSC,
For the E2E Network Slicing use case, during the Integration testing for
Frankfurt, we identified that for one of the test scenarios, an attribute which
was required to be presented to the user (UUI) was missing in the OOF API
response towards SO. As a result, one of the scenarios for
SECCOM has identified the Logging project as a potential blocker to the Java 11
and Python 3 upgrade requirements for Guilin. We will present the information
and potential solutions on the 30 April TSC call and would like the TSC to
recommend a path forward.
Potential blocker
* Logging nee
+1, separate REQ JIRA will help tracking.
Sylvain,
The logging changes will also need some discussion. In earlier release,
logging project put out very detailed standards for log file formats and
mandated four separate log files. For consolidation of logs, filebeat
mechanism was suggeste
+1 Dan - these should all be captured as Guilin Release Requirements REQ
JIRA's. Just like what was done in Frankfurt.
Pam
On 4/29/20, 10:08 AM, "onap-...@lists.onap.org on behalf of TIMONEY, DAN"
wrote:
*** Security Advisory: This Message Originated Outside of AT&T ***.
Reference ht
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
I knew that if I say anything in this thread it will mean I'll have to
do some extra work xD
but OK, I may start putting sth together but after a while I think that
actually a page in read the docs like documentation team has (doc
developer guide) would be more suitable. Any thoughts?
On 29.
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; T
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 proje
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 "c
Good morning Xinhui,
Can you please review this request? Thanks
KR
Catherine
From: onap-tsc@lists.onap.org On Behalf Of Morgan
Richomme via lists.onap.org
Sent: Monday, April 27, 2020 3:15 PM
To: onap-tsc@lists.onap.org
Cc: p.wieczor...@samsung.com
Subject: [onap-tsc] [ONAP [integration] Committ
Good morning Xinhui,
Can you please review this request? Thanks
KR
Catherine
From: onap-tsc@lists.onap.org On Behalf Of Morgan
Richomme via lists.onap.org
Sent: Monday, April 27, 2020 3:15 PM
To: onap-tsc@lists.onap.org
Cc: andreas-geiss...@telekom.de
Subject: [onap-tsc] [ONAP [integration] Comm
Good morning Xinhui,
Can you please review this request? Thanks
KR
Catherine
From: onap-tsc@lists.onap.org On Behalf Of Morgan
Richomme via lists.onap.org
Sent: Monday, April 27, 2020 3:15 PM
To: onap-tsc@lists.onap.org
Cc: Kuzmicki, Krzysztof (Nokia - PL/Wroclaw)
Subject: [onap-tsc] [ONAP [int
12 matches
Mail list logo
