The objective of this page is to give you some basics about setting up ONAP PNF simulator and how to create a simple CDS blueprint model to perform config-assign and config-deploy using CDS REST API interfaces.
- Setting up PNF simulator integration project
You can refer to PnP PNF Simulator wiki page to clone the GIT repo and start the required docker containers. We are interested in the sysrepo
/sysrepo-netopeer2
docker container to load a simple YANG similar to vFW Packet Generator.
- Start PNF simulator docker containers
cd $HOME
git clone https://github.com/onap/integration.git
Start PNF simulator
cd ~/integration/test/mocks/pnfsimulator
./simulator.sh stop
./simulator.sh stop
- Verify the you have netopeer docker container are up and running. It will be mapped to host port 830
docker ps -a | grep netopeer
- Create a simple packet generator YANG model (pg.yang)
module sample-plugin { yang-version 1; description revision "2016-09-18" { container sample-plugin { // READ // WRITE } grouping sample-plugin-params { key id; leaf is-enabled { |
---|
- Sample XML data definition for the above model to initialise one single PG stream (pg-data.xml)
<sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin"> |
---|
- Copy the above two files into netopeer docker container (pg.yang & pg-data.xml) under /etc/sysrepo/data folder
Execute the following command within netopeer docker container to install the pg.yang model
sysrepoctl -i -g /etc/sysrepo/yang/pg.yang
- Connect to netopeer docker container and execute the following commands to initialise the pg.yang model
cd /opt/dev/Netopeer2/cli/build > quit exit |
---|
- Now create a simple CDS blue print to update the number of streams using NETCONF.
- You can use the attached demo-pnf-bp.zip.zip file to enrich, save, publish and deploy from CDS UI.
- You can extract the above BP archive to find the Scripts/dd.json & Scripts/dd.sh. You execute the below command to populate the data dictionary (CDS_UI_PORT = 3000)
bash -x ./dd.sh CDS_UI_PORT ./dd.json
- CDS UI you should the all operation successful as shown below
Config-Assign
- The assumption is that all the below parameters for config-assign will sent as part of config-assing REST call
Day-0 : config-assign parameters
pnf-ipv4-address, netconf-server-port, netconf-username, netconf-password, stream-count
Day-1 : config-assign parameters
pnf-ipv4-address, netconf-server-port, netconf-username, netconf-password, stream-count
- TODO : REST API CURL Command with JSON payload
Config-Deploy
- config-deploy request will send the Day-0 or Day-1 resolution key as part of the REST call.
"resolution-key" : "day-1" (OR) "resolution-key" : "day-2"
- config-deploy should retrieve the Day-1 or Day-2 configuration based on the resolution-key and executes the NETCONF command processor Kotlin code
- TODO: REST API CURL Command for Day-1 configuration deployment
- TODO: REST API CURL Command for Day-2 configuration deployment