Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DayTimeMeeting IDZoom LinkJoin by phone
Monday[sdc] Team ONAP3, Mon UTC 11:00 / China 19:00 / Eastern 06:00 / Pacific 03:00https://lists.onap.org/g/onap-meetings/calendarSee Groups.io calendar invite

See Groups.io Calendar Invite

...

AgendaMinutes (Draft to be updated during call)
Slides

High Priority Bugs


High priority defects :

 

Jira
serverONAP JIRA
jqlQueryproject = "Service Design and Creation" AND issuetype = Bug AND status not in (closed) AND priority in (High, Highest) ORDER BY priority DESC
serverId425b2b0a-557c-3c0c-b515-579789cceedb


Open review
Jakarta Release timeplan

 

M1 (Global requirement freeze) scheduled for 2nd December

Release Planning: Jakarta

 

Tasks for M1:

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-3786

 

M1 postponed by 1 week from 2nd to 9th Dec. Other milestones unaffected

We should plan to release more often in Jakarta to move towards a more CI way of working. 

 

M1 approved by TSC

 

M2 milestone scheduled for 27th January


Jakarta Impacts

Portal is in unmaintained state in Istanbul and is proposed to be removed in Jakarta, need to consider how user authentication for SDC UI to be performed if portal is removed

Jakarta Release Requirements

 

Proposed new global requirement: REQ-441 ONAP application log to stdout and stderr

Proposed new best practice: Standardized Logging Fields, see Jakarta Best Practice Proposal for Standardized Logging Fields - v2

 

Previous best practise

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-441
promoted to Global Requirement for Jakarta as
Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-1070
 


Log4j security vulnerability

New vulnerability identified related to log4j-core versions 2.0. to 2.15:

https://nvd.nist.gov/vuln/detail/CVE-2021-44228

the vulnerability is specific to log4j-core - no usage of log4j-core in SDC. 


Dormant issues

Following issues will be closed by the release manager as they have not been updated in 18 months unless they are reactivated

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerylabels = not_updated_18_months and project = "Service Design and Creation" and status != Closed
serverId425b2b0a-557c-3c0c-b515-579789cceedb

 

Will review to see what can be closed and what should be kept open. Split up the list between volunteers to review and provide feedback over the coming weeks. Have until 21st January to review the full list


LFN DTF

LFN Developer & Testing Forum  takes place January 10-13 and is now open for registration, for further details see:

https://wiki.lfnetworking.org/pages/viewpage.action?pageId=53609047


LogicticsNext meeting will take place on 10th January
Q&A



...