Content Comparison

...

This page is a consolidation of links that should help any developers, users, architects and owners get up to speed on the ONAP project.

Developer Best Practices

Quickstart Setup

Running the root pom on almost all the projects under - for example - RHEL 7.3 - you should be able to build the entire ONAP system and also import/build them in IntelliJ

Image Removed

Open Import the root pom.xml of the project or the entire onap as a maven project

Image Added

Try to be outside your company firewall and proxy - otherwise open your firewall for the following ports as required

...

Verify you have access to Git, Gerrit (port), Nexus, JIRA and Jenkins, Sonar, biterg for your Linux Foundation ID see http://onap.readthedocs.io/en/latest/index.html

Familiarize with existing and future proposed architecture components of ONAP and additional repositories on github (evel-library, cdp-pal)

Get Rackspace Cloud or Openstack Ocata LAB access and deploy the demo VMs and verify URLs (portal, policy, vid, sdc) and VM deployments (TBD: 33 docker compose orchestrated containers on 12 VMS)

Setup git, maven (~.m2/settings.xml), java, python, (npm, bower), docker and one or both Eclipse and IntelliJ IDEs and optionally Sourcetree

Git checkout all ONAP repos via sh script at Building Entire ONAP#Clone/pullallreposshscript

Maven build all or part of ONAP

...

Subscribe to ONAP Newsgroups.  Note: as of 20170603 there are 3 groups Onap-arc, onap-discuss (this one has a lot of good dev/build/deploy/demo technical discussion even though the description lists non-technical), ONAP-TSC

Watch all ONAP or specific Confluence pages and questions, review TSC meeting minutes

Run the updated ONAP 1.0.0 demo

Specifications

White Paper http://about.att.com/content/dam/snrdocs/ecomp.pdf

...

Get the "Network Function Virtualization" 2016 book by Ken Gray and Thomas D. Nadeau - their successor to their "SDN: Software Defined Networks" book of 2013

Karaf | Kubernetes (ONAP Operations Manager / ONAP on Containers)  - ONAP on Kubernetes

Known Issues

Confluence links from JIRA work but don't display - 

Root POM

This is a root reactor pom.xml that can be used to build all or parts of onap

Some repos like dcae-inventory will require docker installed to build the images.

for speed build with all 5 repos in (~.m2/settings.xml) and the maven options below

...

   <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.onap</groupId>

  <artifactId>org.onap</artifactId>

  <version>1.1.0-SNAPSHOT</version>

  <packaging>pom</packaging>

  <name>onap.root</name>

  <url>http://maven.apache.org</url>

  <modules>

    <module>aai/aai-common</module> <!-- needs yang exclude -->

    <module>aai/aai-service</module>

    <module>aai/logging-service</module>

    <module>aai/model-loader</module>

    <module>aai/rest-client</module> <!-- org.openecomp.aai.logging-service:logging-api:jar:1.0.0 solved by staging onap repo-->

    <module>aai/router-core</module>

    <module>aai/search-data-service</module>

    <module>appc/deployment</module> <!-- emf resolution via public onap repo -->

    <module>dcae/apod/analytics</module>

    <module>dcae/collectors/ves</module>

    <module>dcae/controller/analytics</module>

    <module>dcae/controller/dcae-controller-core</module>

    <module>dcae/controller/dcae-controller-service/dcae-controller-service-dmaap-drsub</module>

    <module>dcae/controller/dcae-controller-service-cdap</module>

    <module>dcae/controller/dcae-controller-service-docker</module>

    <module>dcae/controller/dcae-controller-service-vm</module>

    <module>dcae/dcae-inventory</module> <!-- required docker to build images -->

    <module>dcae/demo</module>

    <module>dcae/dmaapbc</module>

    <module>dcae/operation/utils</module> <!-- emf solved by public onap repo -->

    <module>demo</module> <!-- error in parent refs in sample_plugin -->

    <module>ecompsdkos/ecomp-sdk</module>

    <module>ecompsdkos/ecomp-sdk/epsdk-app-os</module> <!-- until PORTAL-8 -->

    <module>mso</module>

    <module>ncomp/cdap</module>

    <module>ncomp/core</module>

    <module>ncomp/docker</module>

    <module>ncomp/maven</module>

    <module>ncomp/openstack</module>

    <module>ncomp/utils</module>

    <module>policy/common</module>

    <module>policy/docker</module>

    <module>policy/drools-applications</module>

    <module>policy/drools-pdp</module>

    <module>policy/engine</module>

    <module>portal/ecomp-portal-FE-common</module> <!-- parent not referenced -->

    <module>portal</module>

    <module>sdc</module> <!-- in catalog-be org/openrdf/sesame/sesame-rio-rdfjson/2.7.10/sesame-rio-rdfjson-2.7.10.jar; error in opening zip file?-->

    <module>sdnc/adaptors</module> <!-- sdnc/sli/aai/AAIClient.java:30  in sdnc/core/sliPluginUtils-->

    <module>sdnc/core</module> <!-- Felix issues in sdnc/core/slapi/provider -->

    <module>sdnc/northbound</module>

    <module>sdnc/oam</module>

    <module>sdnc/plugins</module>

    <module>ui/dmaapbc</module>

    <module>vid</module>

  </modules>

...

Please follow upstream first approach (better to submit code as-is incrementally) - https://lists.onap.org/pipermail/onap-tsc/2017-August/001449.html

Root POM

Building Entire ONAP#Rootpom.xml