You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

STATUS: Draft

Portal:


1 High Level Component Definition and Architecteral Relationships 



Portal is as common capability used by other components, hence not an architectural functional entity in itself.

Portal is a GUI platform that provides the ability to integrate different ONAP platform GUIs into a centralized portal.

It provides:

  • The capability to allow other ONAP components to run within their own infrastructure while providing common management services and capabilities in a centralized way
  • Provides common capabilities such as application on-boarding and management, centralized access management and hosting application widgets
  • Provides SDK capabilities to access portal capabilities

Portal is used by:

  • VID, Policy, AAI, SDC, MSB and CLI

In addition to regular user, there are admin roles available for Portal to perform some administrative activities of Portal itself and the administration of on-boarded apps.

From the ONAP Portal, administrators:

  • access the same functionality accessible to users
  • manage users and application admins
  • onboard applications and widgets (developed using the Portal as a platform)
  • edit the functional menu

2. API definitions

Portal does not in itself provide APIs to other ONAP components, the Portal users do. [Please replace this statement, as Portal do provide APIs like - https://docs.onap.org/en/beijing/submodules/portal.git/docs/platform/offeredapis.html]

Clamp however provides multi-language support. [I am not sure about CLAMP, CLAMP PTL have to confirm if this is true]

The multi-language support provides:

  • Login user langage settings
  • Update user language settings
  • Language options to user
  • Ability to add/remove and query supported languages.

 3. Component Description:

A more detailed figure and description of the component.

4. known system limitations

Runtime: none

Language capability limitations:

  • Language support for different screens
  • Portal applications that do not use the portal SDK will not get multi-language support. 

5. Used Models

none

6. System Deployment Architecture

None.  Dependent on the user.


  • No labels