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

Compare with Current View Page History

« Previous Version 21 Next »

The Portal is a web-based user interface that provides access to all of the subsystems of an instance of OpenECOMP. It offers both design-time tools and run-time monitoring and control.

Any user seeking access to an OpenECOMP application will first visit the Portal, where authentication will be performed. Based on the user’s configured access level, the Portal will let the user access different application widgets, and might also redirect the user to a specific run-time environment.

From the Portal, users access applications and Key Performance Indicators. Administrators onboard and manage applications and hosted application widgets, and manage user access.

The Portal is also a platform that integrates different OpenECOMP applications into a centralized core. The Portal platform provides common management services and connectivity, while the applications run separately.

Here are two views of the Portal landing screen, one for administrators, and one for users:

Figure 1. Portal landing screen for administrators


Figure 2. Portal landing screen for users

Designing Services

The Portal provides the following design-time features:

  • Service Design and Creation (SDC): visual design tools for Services
  • Policy creation (editing and conflict identification tools)
  • Visual design tools for Analytic Applications (out-of-scope for first OpenECOMP release)

Instantiating Services

The Portal offers a Virtual Instantiation Deployment (VID) GUI to trigger MSO instantiation of Services and components that have been certified and distributed for production. These services may include:

  • Infrastructure Services (such as compute and storage resources)
  • Network Services (Virtual Network Functions)
  • Application Services (such as a load-balancing function)

VID reads the models created in SDC, and, in turn, forwards the appropriate information to AAI and MSO during the Service instantiation process.

See the Installing and Running the OpenECOMP Demo page for a scenario that uses the VID interface. 

Monitoring and Reports: the Dashboard

The Portal also provides a customizable Dashboard containing dynamic widgets that display content from applications running in separate environments. The available widgets are tailored for each user based on access level. Examples of Dashboard elements include:

  • Reports and visualizations, including topology visualizations
  • Collaborative services (video, text chatting, and screen sharing)
  • Application administration (manual on-boarding and management)
  • System monitoring, alarms, and auditing

Figure 3. Portal's KPI Dashboard for DCAE metrics

Administration

From the ECOMP 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

User Guide

The forthcoming User Guide <<DocRef: User Guide>> will provide a comprehensive description of the features of the Portal.

The Portal as a Developer Platform: Adding Applications and Widgets

For developers who wish to add applications that interact with OpenECOMP components, and offer a user interface exposed through the Portal, there is a <<DocRef: Portal Software Development Kit (SDK)>>. This SDK includes bundled tools, technologies, and built-in capabilities such as services, APIs, and User Interface controls. By adhering to the SDK, developers create applications that have a consistent look and feel, and can interact with other applications. Applications can be developed as full web pages or as functional widgets to facilitate a seamless user experience

Applications and widgets developed using the Portal SDK are onboarded via the tools available to an OpenECOMP Administrator. The Administrator creates or assigns roles for the application, and makes the application visible to users via menus or links.

  • No labels