Uploaded image for project: 'ONAP Architecture Committee'
  1. ONAP Architecture Committee
  2. ONAPARC-299

Decompose controller framework in CCSDK to simplify footprint and increase use of common services and data management

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None

      As part of Architecture Subcommittee's ONAP Modularity, this epic specifies initial steps on how the Controller framework in CCSDK is to be decomposed and simplified.  

      1. Enable controller personas to be created
      2. Decouple data layer from controller application layer utilizing platform data management's DBaaS
      3. Migrate select current controller functions to become ONAP platform’s common services for the other ONAP Components to utilize (IP Address Assignment, Model Parser, Ansible Server are Dublin candidate common services)
      4. Pivot to a microservices approach that enables select modules in the Controller to auto-heal and auto-scale as load increases (candidates: NB API handler, some SB adapters, DG/service logic)

      see this link for detail: ONAP_Modularization_ATT_Huawei_10_26_2018_Final.pdf

            auztizza auztizza
            johnng johnng
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: