Content Comparison

Honolulu Reference  (Important Links)

• Honolulu Release Requirements
• Honolulu Impact View per Component
• Honolulu Integration Blocking Points
• Release planning 
• Release EPIC's 
  • M1 - DCAEGEN2-2552
  • M2 - DCAEGEN2-2561
  • M3 - DCAEGEN2-2601
  • RC0 - DCAEGEN2-2643
  • RC1 - DCAEGEN2-2677
• CSIT - https://jenkins.onap.org/view/CSIT/
• Honolulu Exceptions for DCAE (TBD)

Honolulu Release Key Updates

• Release notes updates for new feature add-on/reference are done
• To DO - Reference appropriate jira# and revise component version (pending RC1) - Vijay Kumar
• OOM submissions for Istanbul must hashtag set to "istanbul"

To-Do

• Python CBS client lib updates required for configmap retrieval  - Looking for volunteer 
  •  Separate Jira to be created - Vijay Kumar

Focus topics (To be discussed next week)

• Configuration managements
  • App configuration
    • Dmaap
  • Policy

• CCSDK-3233 - Dashboard (1.4.2) - https://gerrit.onap.org/r/c/oom/+/119992
• DCAEGEN2-2654  - TCA-gen2 (1.2.2) - https://gerrit.onap.org/r/c/dcaegen2/analytics/tca-gen2/+/119944  

Followup from previous discussion  (TOSCA CL POC)

Presentation : 

https://wiki.onap.org/download/attachments/93011619/CL%20LCM%20for%20ONAP.pdf?version=1&modificationDate=1617206485000&api=v2

-----

Meeting notes from 03/24/2021 discussion

• Leverage existing components/API in CLAMP for CLoudiy workflow/deployment instead of adding new components
• Add sample tosca CL model with helm chart based DCAE components (https://git.onap.org/oom/tree/kubernetes/dcaegen2-services/components)
• Followup in few weeks to determine actual scope for DCAE work in Istanbul release

I release DCAE integration candidates

• DCAE Handling (CL Handler) should be made generic to support both cloudify/Helm deployment
  • Separate consul handling/loader not reguired in either deployments (PMSH hardcoding to be fixed)
  • Under helm deployment of DCAE service, consul-loader-container is used for uploading configuration into consul
• DCAE Handling (CL Handler) will be deployed as standalone container/process handling all CL updates/tracking for DCAE services (this could be also generalized at ONAP level as all components are deployed under same cluster)
• POC supporting components (which are Cloudify Workflow specific) may be retained under CLAMP/Policy for interim time
• Helm chart generation support from MOD (based on template introduced in H release) and integration to CL/Tosca workflow

(Deferred to next week)

Pubish syncronization