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

Compare with Current View Page History

« Previous Version 3 Next »

Summary

The development of SDN-R bases on ONAP elements CCSDK, SDNC, OOM and ONAP Documentation.

Each of this elements is represented by different gerrit repositories for the path of service delivery:

  • CCSDK provides features and feature bundles 
  • SDNC provides an image, prepared to run in the the ONAP service environment
  • OOM provides scripts and configurations for deployment in the complex ONAP solution targeting Helm and Kybernetes as platform
  • ONAP Documentation is providing user developer documentation, delivered via INTERNET

SDN-R is not listed. This is because it is a specific configuration of the SDNC container, established during provisioning by OOM Scripts.

Development steps

This description is using SDNR WT microservice or feature as example.

The general steps to provide this feature are descibed by the list below with examples in the following sections.
There are four pieces and steps to consider during development. The changes have to be delivered into repositories of ONAP gerrit.  Checkin precodures are following ONAP prozesses and rules:

  1. ccsdk/features → Provide here the features as single ZIP Installer for all bundles
    1. Bundles with service functionality as ZIP archive containing a maven repository that is later added/installed into the Opendaylight/karaf repository
    2. Provide feature xml that can be added to Opendaylight/karaf to manage the installation
  2. ccsdk/distribution → Add the dependency and the repository
    1. Provide an intermediate container with an Opendaylight/karaf repository containing a specific collection of services
    2. Provide the related repositories via the $ODL_HOME/etc/org.apache.karaf.features.cfg feature repository list, specified by featuresRepositories=
  3. sdnc/oam → Image for activating the service
    1. Add to startODL.sh functionality to startup service if configured to be active. (But be aware .. this script is normally overwritten by oom .. see next step)
  4. oom → Add functionality to configure and start your service
    1. Add to startODL.sh the functionality to startup service if configured to be active.
    2. Extend script to set related ENV variables with configuration of specific feature bundel.

For development purpose and local testing there is a further github repository available with less strict access. It is located here: https://github.com/onap-oof-pci-poc/ccsdk. This repository is a merge of the gerrit repositories ccsdk/feature and ccsdk/distribution using the bold marked elements as subdirectories in difference to the ONAP gerrit, but using the same directory structure below. There are further ReadTheDocs and OOM/HELM related information available in this repository.

The github/ccsdk/distributions are designed to allow a simpler setup using docker on a development server.

Provide feature code

In the gerrit ccsdk/feature repository in the path sdnr/wt the sources for all bundles located.

In the following directory tree there are two sdnr services northbound and wt:

sdnr/
├── northbound
│   ├── energysavings
│   └── oofpcipoc
└── wt
	├── featureaggregator
	├── apigateway
	├── helpserver
	├── devicemodel
	├── devicemanager
	├── websocketmanager2
	├── odlux
	├── pom.xml
	└── README.md

The sdnr/wt bundles apigateway, helpserver, devicemodel, devicemanager, websocketmanager2, odlux are providing the functionality.

The sdnr/wt/featureaggregator

  • is packaging all the above sdnr wt feature bundles (apigateway, .. ,odlux) into one ZIP installer to integrate them into a distribution
  • providing a single karaf feature that can be used to install the complete service ""

Provide distribution




  • No labels