Skip to end of metadata
Go to start of metadata

Purpose

These pages provide a user-focused view of the capabilities of the ONAP platform for designers and operators.

Audience

ONAP user interfaces are intended for users in variety of roles:

  • System and network administrators who need to instantiate, manage, and monitor Resources, Services, and Products on an existing ONAP system
  • ONAP administrators who create user accounts, assign roles, and install applications within ONAP
  • Providers of the various assets managed by ONAP :
    • Vendors who need to create and integrate ("onboard") low-level Resources, such as VNFs (virtual network functions) or other single-purpose functions
    • Service designers who need to compose complex Services from Resources
    • Testers/Approvers who need to test and certify Resources and Services before they are added to the ONAP catalog
    • Product managers who need to define Products from Services (Products include billing and customer support definitions for external Business Support Systems)

Contents

The ONAP end-user documentation describes how to use the application UIs available from the ONAP Portal, as well as the Portal itself. 

Additional resources


  • No labels

2 Comments

  1. Hello, I managed to deploy ONAP using pom.xml. In the pom.xml it is configured to deploy the portal. Nevertheless, I'm not able to access it on the installed server, any ideas how can I verify if the deployment was sucessful? This is the log output

    [INFO] Reactor Summary:
    [INFO]
    [INFO] oparent ............................................ SUCCESS [ 0.323 s]
    [INFO] oparent/checkstyle ................................. SUCCESS [ 0.598 s]
    [INFO] oparent/oparent .................................... SUCCESS [ 2.338 s]
    [INFO] aai-aai-common ..................................... SUCCESS [ 0.866 s]
    [INFO] aai-annotations .................................... SUCCESS [ 3.321 s]
    [INFO] aai-schema ......................................... SUCCESS [ 11.680 s]
    [INFO] aai-core ........................................... SUCCESS [ 15.901 s]
    [INFO] aai-auth ........................................... SUCCESS [ 1.108 s]
    [INFO] aai-utils .......................................... SUCCESS [ 0.653 s]
    [INFO] aai-champ .......................................... SUCCESS [ 32.753 s]
    [INFO] aai-rest-client .................................... SUCCESS [ 1.582 s]
    [INFO] aai-sparky-fe ...................................... SUCCESS [01:41 min]
    [INFO] aai-traversal ...................................... SUCCESS [ 0.760 s]
    [INFO] aai-traversal ...................................... SUCCESS [ 14.252 s]
    [INFO] CCSDK Parent POM : ODL project, Carbon SR1 ......... SUCCESS [ 2.802 s]
    [INFO] clamp .............................................. SUCCESS [01:09 min]
    [INFO] cli ................................................ SUCCESS [ 0.487 s]
    [INFO] cli/validate ....................................... SUCCESS [ 0.473 s]
    [INFO] cli/validate/sample-mock-generator ................. SUCCESS [ 0.640 s]
    [INFO] cli/framework ...................................... SUCCESS [ 1.603 s]
    [INFO] cli/plugins ........................................ SUCCESS [ 0.473 s]
    [INFO] cli/plugins/msb .................................... SUCCESS [ 0.814 s]
    [INFO] cli/plugins/aai .................................... SUCCESS [ 0.527 s]
    [INFO] cli/plugins/sdc .................................... SUCCESS [ 0.636 s]
    [INFO] cli/plugins/so ..................................... SUCCESS [ 0.536 s]
    [INFO] cli/plugins/sample ................................. SUCCESS [ 0.535 s]
    [INFO] cli/validate/sample-yaml-generator ................. SUCCESS [ 0.527 s]
    [INFO] cli/main ........................................... SUCCESS [ 1.055 s]
    [INFO] cli/deployment ..................................... SUCCESS [ 0.471 s]
    [INFO] cli/deployment/zip ................................. SUCCESS [ 2.703 s]
    [INFO] cli/deployment/docker .............................. SUCCESS [ 0.961 s]
    [INFO] cli/validate/validation ............................ SUCCESS [ 0.565 s]
    [INFO] oparent/license .................................... SUCCESS [ 0.016 s]
    [INFO] oparent/oparent-python ............................. SUCCESS [ 1.676 s]
    [INFO] ECOMP Portal SDK Project (parent) .................. SUCCESS [ 0.456 s]
    [INFO] ECOMP Portal SDK Framework ......................... SUCCESS [ 0.746 s]
    [INFO] ECOMP Portal SDK Core .............................. SUCCESS [ 1.880 s]
    [INFO] ECOMP Portal SDK Analytics ......................... SUCCESS [ 4.001 s]
    [INFO] ECOMP Portal SDK Workflow .......................... SUCCESS [ 0.296 s]
    [INFO] ECOMP Portal SDK Webapp Common Classes ............. SUCCESS [ 0.761 s]
    [INFO] ECOMP Portal SDK Webapp Overlay Files .............. SUCCESS [ 3.859 s]
    [INFO] ECOMP SDK Webapp for OpenSource .................... SUCCESS [ 11.748 s]
    [INFO] ncomp-maven-base ................................... SUCCESS [ 0.004 s]
    [INFO] ncomp-maven-xcore .................................. SUCCESS [ 0.003 s]
    [INFO] ncomp-maven ........................................ SUCCESS [ 0.003 s]
    [INFO] portal ............................................. SUCCESS [ 1.773 s]
    [INFO] ecompportal-be-common .............................. SUCCESS [ 9.222 s]
    [INFO] ecompportal-be-os .................................. SUCCESS [ 14.501 s]
    [INFO] ecompportal-FE-os .................................. SUCCESS [04:00 min]
    [INFO] widget-ms-parent ................................... SUCCESS [ 0.483 s]
    [INFO] common-widgets ..................................... SUCCESS [ 0.930 s]
    [INFO] widget-microservice ................................ SUCCESS [ 1.645 s]
    [INFO] security-utils ..................................... SUCCESS [ 1.167 s]
    [INFO] common-app-api ..................................... SUCCESS [ 1.875 s]
    [INFO] common-be .......................................... SUCCESS [ 0.715 s]
    [INFO] catalog-dao ........................................ SUCCESS [ 2.082 s]
    [INFO] catalog-model ...................................... SUCCESS [ 4.264 s]
    [INFO] catalog-ui ......................................... SUCCESS [02:13 min]
    [INFO] catalog-fe ......................................... SUCCESS [ 7.811 s]
    [INFO] asdc-tests ......................................... SUCCESS [ 18.148 s]
    [INFO] sdc-os-chef ........................................ SUCCESS [ 0.073 s]
    [INFO] sdc-jtosca ......................................... SUCCESS [ 0.695 s]
    [INFO] sdc-sdc-tosca ...................................... SUCCESS [ 0.208 s]
    [INFO] sdnc-adaptors ...................................... SUCCESS [ 0.489 s]
    [INFO] sdnc-core .......................................... SUCCESS [ 0.478 s]
    [INFO] sdnc-core .......................................... SUCCESS [ 1.027 s]
    [INFO] sdnc-plugins ....................................... SUCCESS [ 0.476 s]
    [INFO] so ................................................. SUCCESS [ 1.612 s]
    [INFO] MSO Common classes ................................. SUCCESS [ 3.100 s]
    [INFO] API Handler ........................................ SUCCESS [ 0.493 s]
    [INFO] mso-requests-db .................................... SUCCESS [ 2.771 s]
    [INFO] mso-catalog-db ..................................... SUCCESS [ 2.380 s]
    [INFO] ECOMP MSO API Handler common ....................... SUCCESS [ 0.790 s]
    [INFO] MSO Status Control module .......................... SUCCESS [ 0.697 s]
    [INFO] mso-api-handler-infra .............................. SUCCESS [ 7.143 s]
    [INFO] MSO Adapters ....................................... SUCCESS [ 0.488 s]
    [INFO] mso-adapter-utils .................................. SUCCESS [ 1.242 s]
    [INFO] mso-adapters-rest-interface ........................ SUCCESS [ 2.082 s]
    [INFO] mso-network-adapter-async-client ................... SUCCESS [ 3.016 s]
    [INFO] mso-network-adapter ................................ SUCCESS [ 5.504 s]
    [INFO] mso-sdnc-adapter ................................... SUCCESS [ 2.763 s]
    [INFO] mso-tenant-adapter ................................. SUCCESS [ 4.197 s]
    [INFO] mso-vnf-adapter-async-client ....................... SUCCESS [ 2.858 s]
    [INFO] mso-vnf-adapter .................................... SUCCESS [ 7.979 s]
    [INFO] mso-requests-db-adapter ............................ SUCCESS [ 3.987 s]
    [INFO] mso-catalog-db-adapter ............................. SUCCESS [ 1.948 s]
    [INFO] mso-workflow-message-adapter ....................... SUCCESS [ 2.357 s]
    [INFO] mso-vfc-adapter .................................... SUCCESS [ 2.533 s]
    [INFO] asdc-controller .................................... SUCCESS [ 3.322 s]
    [INFO] BPMN Subsystem ..................................... SUCCESS [ 0.478 s]
    [INFO] MSOCoreBPMN ........................................ SUCCESS [ 1.687 s]
    [INFO] MSOMockServer ...................................... SUCCESS [ 2.572 s]
    [INFO] MSO REST Client API ................................ SUCCESS [ 0.569 s]
    [INFO] MSOCommonBPMN ...................................... SUCCESS [ 20.856 s]
    [INFO] MSOInfrastructureBPMN .............................. SUCCESS [ 15.947 s]
    [INFO] MSOCockpit ......................................... SUCCESS [ 4.605 s]
    [INFO] MSO Packages ....................................... SUCCESS [ 0.484 s]
    [INFO] MsoDeliveries ...................................... SUCCESS [ 24.108 s]
    [INFO] onap.root .......................................... SUCCESS [ 0.004 s]
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 14:43 min
    [INFO] Finished at: 2017-11-10T00:03:20-05:00
    [INFO] Final Memory: 523M/3438M

  2. Andres, welcome to ONAP.  I would point you to the running ONAP pages.  Building the entire system via the root pom is good, it will generate most of the artifacts but deployment will be via HEAT or OOM.  You can target an individual component and a single service like the portalapps container that runs in 8989 in a deployment but can run from 8080 in eclipse or intelij.

    Deployment/Installation

    ONAP on Kubernetes#QuickstartInstallation

    ONAP Installation in Vanilla OpenStack - needs to be updated for R1 (open-lab)

    Runtime

    Running the ONAP Demos


    To get a feel for the system you can deploy all or parts of ONAP where the artifacts will be pulled from nexus and not your local build.  Later when you wish to modify or debug a component you can swap out an artifact and attach your debugger.

    Development Guides

    /michael