Versions Compared

Version Old Version 3 New Version 4
Changes made by

Seshu Kumar Mudiganti

Seshu Kumar Mudiganti

Saved on

Key

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

  1. Project Overview

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

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

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

    • VNFM SOL003 adapter support : Resources commitment from Ericsson and Nokia
    • CCVPN extension : Resources commitment from CMCC, VDF, ZTE.
    • Change Management Extension : Commitment based on support from ATT resources.(Scope TBD)
    • PNF extension  : Resource commitment from Nokia.
    • HPA extension (Hardening) for the other existing usecases : Support from Intel
    • Support Multi Cloud for cloud agnostic orchestration : Support from Intel and VMware.
    • Consistent ID of a cloud region : Support from ATT (Testing effort)
    • Internal architecture improvements and work towards modularity:
      • So Monitoring pagination
      • S3P
      • Documentation improvements
      • UT and CSIT improvements
    • BBS : Resource commitment under discussion (Nokia/Huawei/Swisscom??).
    • 5G Support : (Under discussion ATT/Intel/vmware/Ericcson/Amdocs??)
    • Removal of Manual interventions : (Under discussion Tech mahindra, ATT...??)
    • SOL005 adapter support : Resources from Verizon (under discussion of the usecsase to be used is not yet clear)

  3. New or modified interfaces

    Interface naming

    *Multi-Language Functionality API List:

  4. GET  /auxapi/languageSetting/user/{loginId}                    Gets login user language setting in Portal
  5. PUT  /auxapi/languageSetting/user/loginId}                     Updates login user language setting in Portal
  6. POST  /auxapi/language                                                          Adds a language option in Portal
  7. DELETE  /auxapi/language                                                     Deletes a language option in Portal
    8. GET  /auxapi/languages                                                          Gets all language options in Portal
    • --

  8. Interface naming


  9. Reference to the interfaces

    1. Internationalization language support (Dublin Release)

  10. 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.

  11. Involved use cases, architectural capabilities or functional requirements

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

  12. Listing of new or impacted models used by the project (for information only)

    1. None.