Content Comparison

1. Project Overview

   • The ONAP SO provides the highest level of orchestration functionality in the ONAP platform. 

   • The intention is to allow decentralized applications to run within their own infrastructure while providing common management services and connectivity. 

   • The SOcore provides capabilities including application onboarding & management, centralized access management, and hosted application widgets. 

   • Using the provided SDK, application developers can leverage the built-in capabilities (Services / API / UI controls) along with bundled tools and technologies.

2. New component capabilities for Dublin, i.e. the functional enhancements

   1. 5G Usecase Impacts on SOplatform (AT&T resources - Former user (Deleted) )
      • Impact on Functional Menu for the usecase flows to different components.
      • User next step recommendation feature can help new users that are not familiar with the 5G steps.
   2. New features (Chinamobile , AT&T, IBM resources)
   1. • Locale/Internationalization language support – UsecaseUI project integration. (Chinamobile resources committed for this feature - Tao Shen)
      • Reporting feature enhancement in portal/sdk (AT&T resources - Former user (Deleted) )
      • Angular 6 Upgrade of ONAP SOand SDK with 1 or 2 new UI screens (IBM and AT&T resources partially committed - Deven and Saravanan Madheswaran)
   1. • • may impact partnering apps like Policy and VID 

3. New or modified interfaces

   • SOR4 M1 Release Planning (Dublin Release)#APIOutgoingDependencies

4. Interface naming

   1. *Multi-Language Functionality API List:

      • GET  /auxapi/languageSetting/user/{loginId}                    Gets login user language setting in Portal
      • PUT  /auxapi/languageSetting/user/loginId}                     Updates login user language setting in Portal
      • POST  /auxapi/language                                                          Adds a language option in Portal
      • DELETE  /auxapi/language                                                     Deletes a language option in Portal
      • GET  /auxapi/languages                                                          Gets all language options in Portal

5. Reference to the interfaces

   1. Internationalization language support (Dublin Release)

6. What are the system limits

   1. Language Support: The changes that are described about fetching list of languages, presenting to login user and saving the chosen language setting looks good. However, we will be more interested in few samples on how you are planning to use “angular-translate” that is mentioned in the slide 4 of the slide deck

      Specific questions like:

      1. Which UI screens in SOyou will support this feature? Just the SOhome screen or all screens? (mostly the home screen based on the impact of changes)
      2. Let’s take SO home screen, how do you plan to have the translation providers defined? Do you have to handle every text element on the screen? So is the reason to request for an example or sample code, so that we can understand the “angular-translate” usage.
   2. Here is the status on ONAP Portal's Dublin risks 
      
      1. Risk#3 – Remains high on probability of occurrence and high on impact due to no commitment from any resources.
      2. Risk#4 – Remains high on occurrence, but medium on impact as we are getting partial help from Michael O’Brien on the logging aspects. However, no resource commitment for footprint optimization.

7. Involved use cases, architectural capabilities or functional requirements

   5G use cases - exposing the appropriate functional menus from various components under design and runtime top menus of Portal.

   • A new Microservice for the VNFM Adapter will be added to the SO as a separate pod

   • SO would be upgraded to the Spring boot 2.0

   • SO should support the workflows designed in SDC (extension from the R3 Release)
   • SO should support List type  for resource orchestration

8. New or modified interfaces

   • Interfaces added in Dublin:
     • VNF InPlaceSoftwareUpdate
     • VNF ConfigUpdate

     • Update Service (Add site) 
       
       

9. Interface naming

   1. Details of the new APIs of Change Management:
      • VID-SO WFD API – VNF InPlaceSoftwareUpdate
      • VID-SO WFD API – VNF ConfigUpdate
   2. Details of the APIs modified for the CCVPN :
      • Update Service Instance

10. Reference to the interfaces

    1. SO Dublin - Change Management
       
    2. SO Dublin - CCVPN Extension

11. What are the system limits

    1. 
       

12. Involved use cases, architectural capabilities or functional requirements

SO will contribute to the following use cases as part of the functional requirements.

• • • SO Adapter to Multicloud Improvements
    • SO Dublin - Change Management
    • SO Dublin - Existing use-cases HPA Extension and Hardening
    • SO Plug-in Support for VNFM (SO VNFM Adapter)
    • Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO

• • • SO Building Block [Casablanca]
    • 5G - PNF Plug and Play
    • VNF and PNF Building Block Strategy[Dublin]
    • CCVPN Use Case (Dublin)#ServiceInstantiation(SI).1

• • • BBS Broadband Service Use Case (Dublin)
    • Continuation of HPA (Dublin) - Extension to R3
• Listing of new or impacted models used by the project (for information only)

1. 1. .None

.