Portal R4 M3 Architecture Review

Owned by Manoop Talasila
Last updated: Feb 25, 2019
2 min read

  1. Project Overview

    • The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core. 

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

    • The Portal core 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 Portal platform (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 Portal and 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

  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 Portal you will support this feature? Just the Portal home screen or all screens? (mostly the home screen based on the impact of changes)

      2. Let’s take Portal 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

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

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

    1. None.