Versions Compared

Old Version 1

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

compared with

New Version 2

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

Key

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

  1. Changes since Amsterdam

    1. Support the Homing through OOF
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySO-390
    2. Support the Scale-Out feature
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySO-391
    3. Support PNF Orchestration
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySO-436
    4. Support Change Management
    5. TOSCA Orchestrator demonstration(Stretch goal).
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySO-22
    6. Enhance the SO code
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySO-368


  2. S3P Updates
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-375

    1. Security 

      1. WIP: CII Badge
      2. WIP: Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
      3. WIP: Increase test code coverage to reach 50%
      4. Pilot the security static checking for Beijing
    2. Manageability-Logging 
      1. Update log configuration for SO components according to Logging guidelines 
    3. Resiliency and Scalability  
      1. Depend on kubernetes to manage instance(s) of SO component(s)
      2. Research the configuration in OOM
    4. Usability  
      1. Document APIs in readthedocs (Swagger) and solve inconsistent problem between code and API
      2. Improve the deployment and configuration documentation
    5. Performance and Stability
      1. Defining the performance criteria with Bench marking team.
      2. SO team will work with Integration team to do performance testing

  3. IM/DM Alignment

    1. SO team is participating the modeling discussion about Service/Resource IM/DM
    2. Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee

  4. API Updates

    1. Support the homing through OOF through new API.