Page Comparison

...

1. Changes since Amsterdam

   1. No scope changes for Multi VIM/Cloud R2 Architecture
   2. Core components updates for supporting R2 Use Case 
       

      Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-148

   3. Stretch goal
      1. Standardized Infrastructure Resource Information Model (Under going)
      2. FCAPS modeling (under going)
      3. TOSCA-based orchestration to deploy workload on multiple clouds (need discussion with Architecture CommitteeSub-committee)
      4. MultiCloud support for Azure (under discussion and will not allocate JIRA or repo input code into epo for tracking purpose)
      5. POC of Containerized VNF through some use cases (will not allocate JIRA or repo; will invite the team to review POC once ready for formal plan of Casablanca)
         
         

2. S3P Updates

   1. Security 

      1. Jira Legacy
         server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-175

      2. CII Badge: Image Added
      3. WIP:Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
      4. WIP:Increase test code coverage to reach 50%
   2. Manageability-Logging 
      

      1. Jira Legacy
         server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-151

      2. Update log configuration for Multi VIM/Cloud components according to Logging guideline 
      3. Filebeat container packed with Multi VIM existing container for shipping logs to ONAP ELK logging stack.
   3. Resiliency and Scalability  
      

      1. Jira Legacy
         server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-150

      2. Depend on kubernetes to manage multiple instances of Multi VIM/Cloud stateless components
      3. Research the configuration in OOMadd Multi VIM service and recovery capability
      4. depends on geographic scaling
   4. Usability  
      

      1. Jira Legacy
         server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-152

      2. Document APIs in Swagger and solve inconsistent problem between code and API
      3. Improve the deployment and configuration documentationNo UI and tutorial documentation need more work
   5. Performance and stability
      

      1. Jira Legacy
         server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-149

      2. VF-C Multi VIM/Cloud team will work with Integration team to do performance testing 
         
         

3. IM/DM Alignment

4. Multi VIM/Cloud internal discussion and team discussion (with VES)
Stretch goal: Draft IM/DM proposals for the modelling subcommittee

1. Jira Legacy
   server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-153

2. Jira Legacy
   server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-154

   
   
   

API Updates

1. https://

   wiki

   lf-onap.

   onap

   atlassian.

   org

   net/wiki/display/DW/Externally+Consumable+APIs