...
The design-time framework is an integrated development environment with tools, techniques, and repositories for defining and describing deployable assets. It supports the development of new capabilities, augmentation of existing capabilities and continuous operational improvement throughout the lifecycle of a service. The execution-time framework uses closed-loop, policy-driven automation to drive down operational costs. Built-in dynamic, policy-enforced functions are provided for component and workload shaping, placement, execution, and administration. Access to the design-time and execution-time frameworks are provided by the OpenECOMP Portal, a role-based user interface.
...
Figure 1. OpenECOMP architecture
...
The OpenECOMP Portal (henceforth, Portal) is the web-based end-user interface to OpenECOMP. It offers both design-time tools and run-time monitoring and control.
Any user seeking access to an OpenECOMP application will first land on the Portal, where authentication will be performed. Based on the user’s access level (determined by OpenECOMP administrators), the Portal will let the user access different application widgets, and may also redirect the user to a specific run-time environment.
The Portal provides the following design-time features:
- Visual design tools for Services
- Policy creation (editing and conflict identification tools)
- Visual design tools for Analytic Applications
...
- 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
Applications make themselves visible in the Portal via service registration and discovery.
Design-time framework
The design-time framework consists of the following subsystems:
...
- Active and Available Inventory (A&AI)
- Controllers
- Dashboard
- Data Collection, Analytics and Events (DCAE)
- Master Service Orchestrator (MSO)
- Security Framework
...