Content Comparison

START RECORDING

PARTICIPANT LIST

Open from last meeting

•  Healthcheck not reporting DCAE service components (DCAEGEN2-2433)  (cm-container 3.3.2)

•  Race condition between Cloudify pod and bootstrap (DCAEGEN2-2430) (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 - No longer bug for VES

•  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

• DCAEGEN2-2471: DCAE Offline install issue with new types not included in docker - 
•  DCAEGEN2-2463: DCAE multisite-init-container Docker image build fails  - Move to H release
•  DCAEGEN2-2465: DCAE Cloudify Manager readiness probe timeout too short - Merged into OOM
•  DCAEGEN2-2455: DCAE dockers contain GPLv3
•  DCAEGEN2-2457: DCAE deployment failing (integration daily) - Resource limit for Cloudify to be increased; planned with OOM submission later today by Jack
•  DCAEGEN2-2469: TCA-gen2 CL output Request-ID not valid UUID
•  DCAEGEN2-2470: TCA-gen2 nullpointer exception when sourcing policy config via CBS

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 

Upcoming milestone RC0 - DCAEGEN2-2442

• Review Guilin packages (

• see below)

• dcaegen2
• dcaegen2/deployments
• dcaegen2/platform/blueprints
• dcaegen2/services

• dcaegen2

Branching for dcaegen2 (documentation) will be done toward end of RC1.  Until then pls DO NOT merge any changes targeted POST Guilin on “master” branch for above dcaegen2 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. Path submitted to reflect R8 path on master (Guilin will stay on R7); new updates >R7 can progress on these except for last two repo  (pending branching and merging patch submitted)

• 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)