Versions Compared

Key

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

Table of Contents

Bridge

[dcaegen2] Team ONAP11, Wed UTC 14:30

...

One tap mobile
+13126266799,,98967242523# US (Chicago)
+16465588656,,98967242523# US (New York)
Dial by your location
+1 312 626 6799 US (Chicago)
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Germantown)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
877 369 0926 US Toll-free
855 880 1246 US Toll-free
Meeting ID: 989 6724 2523
Find your local number: https://zoom.us/u/ad1U59khic?

Recording:

Attendees:

Host: Vijay Kumar

Discussion Topics:

...



...

START RECORDING

PARTICIPANT LIST

ACTION REQUIRED BY ALL COMMUNITY MEMBERS

Everyone should immediately begin following the model used by many other OSS communities and change your Zoom name to First-name FAMILY-NAME (company) – capitalization of family name here is intentional to help our global community.
Example:  Hosty MCHOSTFACE (Fetzervalve)

WAITING ROOM ENABLED - by default (requires HOST/MOD to accept attendeer

Recording:


Attendees:

Host: Vijay Kumar




Discussion Topics:



 Time (est) Topics Requester/Assignee Notes/Links




START RECORDING

PARTICIPANT LIST






1
Project Status & General updates

New issues reported 

  • DCAEGEN2-2471: DCAE Offline install issue with new types not included in docker 
  • DCAEGEN2-2463: DCAE multisite-init-container Docker image build fails
  • DCAEGEN2-2465: DCAE Cloudify Manager readiness probe timeout too short
  • DCAEGEN2-2455: DCAE dockers contain GPLv3
  • DCAEGEN2-2457: DCAE deployment failing (integration daily)


Open from last meeting

  •  Healthcheck not reporting DCAE service components (DCAEGEN2-2433)
- OOM merge pending
  •   (cm-container 3.3.2)
  •  Race condition between Cloudify pod and bootstrap (DCAEGEN2-2430)
- Delivered
  • (cm-container 3.3.1)
  •  k8s-bootstrap-container:2.1.6 release pending (include everything on 2.1.5 + holmes + son-handler)
  •  DCAEGEN2-2140: escaped string in spec file not included on the blueprint generated
  •  DCAEGEN2-2454: RuntimeAPI appends empty plugin import
  •  DCAEGEN2-2453: Failed to fetch configuration from CBS
  •  DCAEGEN2-2450 : Cloudify password can be set to value not working with CLI


Note: Bootstrap revision/release to be consolidated (btw now and RC1)

  • First patch merged must include version bump
  • Subsequent patches can be merged without version bump as long as not release
  • Selfrelease yaml snapshot must include latest snapshot 




Guilin Reference 




Upcoming milestone (M4 - 9/10) - DCAEGEN2-2389 

  • Review Guilin packages (see below)


2
DCAE Outstanding Jira & MED priority bugs (Guilin)

Guilin (Bugs)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryfilter=12333
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Jira Legacy
serverSystem Jira
jqlQueryfilter=12436
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

3
Review Guilin Branching 

Repositories branched

  • PM-mapper

Vijay Kumar  will create Guilin branch for rest of DCAE Repository by 09/25 COB

  • CI jobs for guilin will be added
  • Frankfurt CI job will be disabled

Branching on following will be deferred by a week

  • dcaegen2/collector/ves
  • dcaegen2/platform/blueprint
  • dcaegen2/platform

Frankfurt CI will be disabled 

VES repo - frankfurt branch fixed

Branched majority of DCAE repositories for Guilin release with corresponding CI jobs in place – with the exception of following repositories

As there are outstanding updates pending on above, these repo has not been branched yet (targeting next week except for dcaegen2 which will be done post RC0). Until then pls DO NOT merge any changes targeted POST Guilin on “master” branch for above repositories.

Couple of guidelines on approvals/merged on branched components

  1. Guilin branch
    1. Only critical bug fixes must be merged into guilin branches
    2. patch version must be incremented for every bugfix
    3. Self-release can be submitted into guilin branch
  2. Guilin Maintenance  (schedule TBD)
    1. Any change targeted for Guilin maintenance must go under “Guilin” branch only after release tagging is complete (around RC2)
    2. Bug-fixes for Guilin-maintenance can go under “master” and later cherry-picked and released
  3. Master branch
    1. Post Guilin enhancement/optimization can be worked and approved but would suggest to hold merge until RC0.
    2. Work with contributor to Cherry-pick any bug fix submitted under Guilin branch into master branches
    3. Ensure master version is updated and do not conflict with guilin (typically we bump the minor version on master)

For following repository, the builds are dependent on artifacts being sourced from/pushed into nexus raw. I will be submitting patch to update to R8 path on master (Guilin will stay on R7) and hence please hold off merging new updates on these components until nexus/path updates are complete. 

  • dcaegen2/collectors/snmptrap
  • dcaegen2/platform/plugins
  • dcaegen2/utils
  • dcaegen2/deployment
  • dcaegen2/platform/blueprint


https://gerrit.onap.org/r/q/topic:%22R8-tag-branch%22+(status:open%20OR%20status:merged)

4
Network Slicing usecase 

Discuss current issues and test plan for Guilin

Current status:

  • DES - Docker not ready (docker build TBC)
  • Slice-Analysis - Docker build WIP
  • DL-Handler  (NFR)  - Validate and initiate selfrelease; recommended to be combined with DES/Slice analysis delivery
  • Pm-Mapper - 
    • KPI computation enhancement will be deferred to G point release (based on M4 as 9/17 if approved by TSC)
    • CSIT enhancements for KPI computation to be added (can be tracked separate with Integration team and not block 111629 merge)
    • CL and Intelligent slicing can be validated using current PM-Mapper


Integration Test plan

  • Network Slicing  (CL and intelligent slicing in WR)
  • DES (CMCC)
  •  Test plan to be shared
  •  Automated test to be synced with Morgan
  • CSIT  - Slice analysis CSIT WIP, other components not starte












Post Guilin 


REQ-363 - ONAP components should be able to run without AAF  - DCAEGEN2-2363  

  •  Vijay Kumar  - Create jira/subtask for components not having TLS enable/disable among current configuration.Will be tracked for H release and separare Jira created for sub-components

...

Frankfurt Artifacts Release versions

Check "Artifacts released" section under RTD - https://docs.onap.org/en/latest/submodules/dcaegen2.git/docs/sections/release-notes.html

Open Action Items


...