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 steps to provide this feature are descibed by the following sections
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 featureaggregator
- is packaging all above feature bundle into one ZIP installer
- providing a single karaf feature that can be used to install the complete service in a distibution container.