Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-1038

DCAE Transformation to support Helm (Phase3/final)

XMLWordPrintable

    • DCAE Transformation to support Helm (Phase3/final)
    • Feature
    • Not yet performed
    • Original Scope
    • L
    • Not used for this release
    • Not used for this release

      Before editing please read instructions here.

      Description of Use Case / Requirement:

      DCAE Architecture includes currently DCAE Platform and DCAE Services component (collector/analytics etc). DCAE platform provides LCM (through Cloudify workflows) and several standardized functions for DCAE services such as 

      • Configuration management and retrieval through CBS
      • DMaap Topic provisioning
      • Policy Interaction abstracted and managed by Policy Handler
      • Postgres DB initialization

      Goal of the transformation  is to offer these platform function as k8s based function (using k8s operator/sidecar/init-container etc) and enable onboarding and deployment of DCAE MS through helm directly, thereby simplifying the DCAE architecture and removing 3rd party component dependencies.

      Primary Tranformation goals :

      • Decentrailization of platform functions 
      • Remove centralized configuration management (and enable application use K8S configmap)
      • Facilitate flexible onboarding and deployment of DCAE services
      • CI/CD based workflow automation
      • Moving toward Cloud Native options for supporting current platform capabilities

      **This will be multi-release effort and work per release will be scoped based on community support.

      In Phase1 (Honolulu release) , certain DCAE service were migrated to Helm deployment (tracked under DCAEGEN-2488/REQ-479),  Cloudify was primary orchestration for dynamic deployments (MOD/CLAMP flows). 

      Phase2 (Istanbul release) continued Helm transformation initaitives; delivered following features

      • [DCAE] Migrated remaining DCAE services (13) into Helm deployment
      • [DMAAP/OOM] Secure Topic/feedprovisioning under helm deployment
      • [DCAE] Standardized App Configuration (including Policy, Dmaap etc.) management outside of Consul*
      • [DCAE-MOD] MOD support for onboarding helm based services and integration with ONAP deployment*

                  *  Partial delivery

      Phase 3 (J release)  - Complete deferred/partial stories from Istanbul release (integrate MOD to support helm flows & migrating DCAE services to new SDK to remove consul dependency) + 

      • [DCAE] Deprecate Cloudify components from ONAP deployments
      • [INTEGRATION] Migrate all current Integration & gating test to leverage DCAE service component helm charts for functional/usecase validation
      • [Policy] CLAMP/Control Loop design integration for Helm based deployment (TEST)*

      Owners (one of these should be the Assignee - use @ notation):

      vv770d, jackl

      Link to HLD/LLD (if any):

      https://wiki.onap.org/pages/viewpage.action?pageId=92997528

      https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/installation_oom.html

      https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/dcaeservice_helm_template.html

       

      API Changes

      Cloudify/handlers API's will be deprecated; this includes

      • Dashboard
      • InventoryAPI
      • Deployment-Handler
      • ServiceChange Handler
      • ConfigBindingServices

       

      Dependency Relationships with Other Projects:

       

      DCAE IMPACT: C

      • Impact Type: C
      • Company Engagement:  AT&T, Nokia, Ericsson, Wipro, Independent 
      • Resources:  X
      • Support Status: S
      • Non-Functional Requirement Support: TBD

      HOLMES IMPACT: C

      • Impact Type: C
      • Company Engagement:  ZTE
      • Resources:  X
      • Support Status: S
      • Non-Functional Requirement Support: TBD

      OOM IMPACT: C

      • Impact Type: C
      • Company Engagement:  AT&T, Independent 
      • Resources:  X
      • Support Status: S
      • Non-Functional Requirement Support: TBD

      INTEGRATION IMPACT:C  

      • Impact Type: C
      • Company Engagement:  Nokia
      • Resources:  X
      • Support Status: S
      • Non-Functional Requirement Support: TBD

       POLICY(CLAMP) IMPACT: TO 

      •  Policy/CLAMP project work for DCAE integration covered under REQ-716 (CL Tosca)

       

      Integration Leads (use @ notation): TBD

       

            vv770d vv770d
            vv770d vv770d
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: