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

...

Former user (Deleted) 

Stasys Jurgaitis 

Krupa Nagabhushan 

dushyant thakur 

Francisco Javier Paradela Vila (Unlicensed) 

...

AgendaMinutes (Draft to be updated during call)
Slides

High Priority Bugs


High priority defects :

 

Jira Legacy
serverSystem Jira
jqlQueryproject = "Service Design and Creation" AND issuetype = Bug AND status not in (closed) AND priority in (High, Highest) ORDER BY priority DESC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Open review
Jakarta Release timeplan

 

M1 (Global requirement freeze) scheduled for 2nd December

Release Planning: Jakarta

 

Tasks for M1:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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

 

First delivery for Jakarta (1.10.0) built and submitted to OOM (https://gerrit.onap.org/r/c/oom/+/126602). Content can be seen here: https://docs.onap.org/projects/onap-sdc/en/latest/release-notes.html#version-1-10-0

Still in review in OOM

1.10.1 built and submitted to OOM (https://gerrit.onap.org/r/c/oom/+/127003)

M2 passed last Thursday 3rd Feb. Next milestone is M3 on 3rd March


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 practice

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-441
promoted to Global Requirement for Jakarta as
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-1070
 

Proposed impact for Jakarta:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-1044

Concerns raised at modeling subcommittee on ASD POC, was discussed at TSC last Thursday, to be further discussed at modeling subcomittee today to see if agreement can be reached on way forward


Q&A

ds00528024 expressed an interest in working on multi tenancy. Already existing ticket for multi tenancy in ONAP :

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-761
and specifically in SDC:
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3188

Dasarathi to check with those associated to these tickets the latest status


...