Versions Compared

Old Version 2

changes.mady.by.user Vijay Kumar

Saved on

compared with

New Version Current

changes.mady.by.user Vijay Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minutes and recording updates

Bridge

[dcaegen2] Team ONAP11, TUESDAY UTC 14:30  (10.30 AM EDT)

ONAP Meeting 11 is inviting you to a scheduled Zoom meeting.

...

All attendees must set their Zoom name in First-name FAMILY-NAME (company) format

Recording:

TBADCAEWeekly_05022023_video1584560581.mp4

Attendees:

Vijay Kumar (Host)

Jack Lucas 

Tony Hansen 

Discussion Topics:


S.NO Time (est)

 Topics

 Requester/Assignee Notes/Links




Notes to moderator

  • Start recording
  • Participants List







DCAE/PTL resposibilities Coverage Host

Updates: TSC is planning to form a special squad or task force to manage changes to projects that lack a PTL. Chaker will take the lead of in forming the team.


Feedback from committers on DCAE London Milestone support


Responsibilities to be distributed among DCAE Committers

The TSC has been advised that there is no coverage for milestones M3 and beyond.

M4 is coming on 2023-04-27;  patches rescheduled to 05/04/2023 -   patches need to be merged by thenin DCAE, new containers released, and OOM updates for new versions need to be submitted.

05/02/2023 -  Bi-weekly scheduled meetings will conclude with 05/30/2023; next 2 meetings are primarily to facilitate any remaining London release support.  Future enhancement/feature discussion any to be scheduled on-demand (pending TSC decision on project proceeding for Montreal and beyond)




London Release PlanningHost

https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/DCAE+R12+London+M2+Release+Planning



ML-prediction Ms London delivery

Vijay Kumar 

Wipro team unavailable to complete remainder process for container certification and delivery

https://gerrit.onap.org/r/c/dcaegen2/services/+/127490

05/02/2023 : ML-Predcition MS will be handled as POC for London and not included in release branch. Corresponding Jira's will be updated to POC (can be mainstreamed if team later has necessity)



Review JIRA backlogHost
  • Review JIRA backlog:
    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
    maximumIssues20
    jqlQueryproject = DCAEGEN2 AND status not in (Closed) AND labels not in (relman, dcae-mod-poc) and fixVersion = "London Release"
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Reviewed planned container deliveries

05/02/2023 - No new updates


Review what containers will be updated/added for the London release  (See below on 

London Artifacts Tracker)



DR timeout issue

Viresh Navalli 

05/02/2023 - Status on  DCAEGEN2-3313 to be checked with Capgemini team.

04/18/2023 DMAAP-1875 fix ready to submit; waiting for confirmation from Henning/DT on solution.

2023-04-04: continue with plans as detailed below. The JIRA has been updated.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-3315
moved to DMAAP

2023/03/07: Following parameters needs to be updated on DR; Fiachra Corcoran informed code updates required. 

waitForFileProcessFailureTimer = 60.000 --> 1min (former was 10min)
maxfailuretimer = 600.000 --> 10min (former was 1h)

Jira moved to DMAAP project: DMAAP-1875



Release branching and DCAE release notes

Vijay Kumar 



CMPv2 support

Jack Lucas 

CMPv2 cert generation has some dependency on truststore created through AAF init container - without testing hard to claim this feature works as desired currently.

Jack Lucas will update the documentation to

be submitted next week		ML-prediction Ms London delivery

Vijay Kumar 

Wipro team unavailable to complete remainder process for container certification and delivery

reflect OOM/London plans for supporting without AAF and remove any obsolete references.



Documentation ErrorsVijay Kumar 

Errors/warning reported under docuementation verify jobs (e.g https://jenkins.onap.org/job/rtdv3-global-verify-master/21304/console) to be addressed to have clean/successful job - until then committers must verify impacted files manually and override jenkins failure to merge. 

Tony Hansen will evaluate handling these errors (post M4)

(Doc team preferred config - https://gerrit.onap.org/r/gitweb?p=doc/doc-best-practice.git;a=blob_plain;f=docs/tox.ini;h=b9d7eb44b6a83884651385f7174c7ef0d6ab948c;hb=HEAD)



SliceAnalysis MS updates 

Vijay Kumar 

Reg : https://gerrit.onap.org/r/c/dcaegen2/services/+/134057

Couple of issues with this merge

  • Firstly it should not have been self-merged - no change must be self-merged (unless there is an exception from TSC)
  • This looks like an enhancement feature - nly bugfixes/critical issues submission can be accepted post M3
  • This change doesnt appear to address the jira scope in entirety? Where is check on requested bandwidth and provisioned bandwidth done? Noticed new class/function introduced for publish however dont see where rest of logic/invocation for this method is done?
  • Why existing topic (DCAE_CL_OUTPUT) cannot be leveraged to notify this communication (i.e instead of creating new topic)


05/02/2023 - London release/branching will not be including this patch. Branching will be done for London excluding this patch. Any  new patches for SliceAnalysis should be considered for Montreal.














Topics/Demos' for future meetings

<Topics can be added below by presenters as they are ready>


...