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

Compare with Current View Page History

« Previous Version 4 Next »

STATUS: Draft

Portal:


1 High Level Component Definition and Architecteral Relationships 



Portel is as common capability used by other components, hence not a architectural functional entitiy 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 capabitilities in a centralised way
  • Provides common capablities such as application onboarding and management, centralized access management and hosting application widgets
  • Provides SDK capabilities to access portal capabilities

Portal is used by:

  • SDC
  • ...... Others? 

2. API definitions

Portal does not in itself provide APIs to other ONAP components, the Portal users do.

Clamp however provides multi-language support.

The multilanguage support provides:

  • Login user langage settins
  • Update user langage 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.

<< For later inclusion >>

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.  Dependant on the user.


  • No labels