1 .. This work is a derivative of https://wiki.onap.org/display/DW/PNF+Simulator+Day-N+config-assign+and+config-deploy+use+case
2 .. This work is licensed under a Creative Commons Attribution 4.0
3 .. International License. http://creativecommons.org/licenses/by/4.0
4 .. Copyright (C) 2020 Deutsche Telekom AG.
6 PNF Simulator Day-N config-assign/deploy
7 ========================================
12 This use case shows in a very simple way how a blueprint model of a PNF is created in CDS and how the day-n configuration is
13 assigned and deployed through CDS. A Netconf server (docker image `sysrepo/sysrepo-netopeer2`) is used for simulating the PNF.
15 This use case (POC) solely requires a running CDS and the PNF Simulator running on a VM (Ubuntu is used by the author).
16 No other module of ONAP is needed.
18 There are different ways to run CDS, to run PNF simulator and to do configuration deployment. This guide will show
19 different possible options to allow the greatest possible flexibility.
21 Run CDS (Blueprint Processor)
22 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
24 CDS can be run in Kubernetes (Minikube, Microk8s) or in an IDE. You can choose your favorite option.
25 Just the blueprint processor of CDS is needed. If you have desktop access it is recommended to run CDS in an IDE since
26 it is easy and enables debugging.
28 * CDS in Microk8s: https://wiki.onap.org/display/DW/Running+CDS+on+Microk8s (RDT link to be added)
29 * CDS in Minikube: https://wiki.onap.org/display/DW/Running+CDS+in+minikube (RDT link to be added)
30 * CDS in an IDE: https://docs.onap.org/projects/onap-ccsdk-cds/en/latest/userguide/running-bp-processor-in-ide.html
32 Run PNF Simulator and install module
33 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
35 There are many different ways to run a Netconf Server to simulate the PNF, in this guide `sysrepo/sysrepo-netopeer2`
36 docker image is commonly used. The easiest way is to run the out-of-the-box docker container without any
37 other configuration, modules or scripts. In the ONAP community there are other workflows existing for running the
38 PNF Simulator. These workflows are also using `sysrepo/sysrepo-netopeer2` docker image. These workflow are also linked
39 here but they are not tested by the author of this guide.
43 .. tab:: sysrepo/sysrepo-netopeer2 (latest)
46 Currently there is an issue for the SSH connection between CDS and the netconf server because of unmatching
47 exchange key algorhithms
48 (see `Stackoverflow <https://stackoverflow.com/questions/64047502/java-lang-illegalstateexception-unable-to-negotiate-key-exchange-for-server-hos>`_).
49 **Use legacy version (right tab) until the issue is resolved.**
51 Download and run docker container with ``docker run -d --name netopeer2 -p 830:830 -p 6513:6513 sysrepo/sysrepo-netopeer2:latest``
53 Enter the container with ``docker exec -it netopeer2 bin/bash``
55 Browse to the target location where all YANG modules exist: ``cd /etc/sysrepo/yang``
57 Create a simple mock YANG model for a packet generator (:file:`pg.yang`).
62 module sample-plugin {
65 namespace "urn:opendaylight:params:xml:ns:yang:sample-plugin";
66 prefix "sample-plugin";
69 "This YANG module defines the generic configuration and
70 operational data for sample-plugin in VPP";
72 revision "2016-09-18" {
73 description "Initial revision of sample-plugin model";
76 container sample-plugin {
78 uses sample-plugin-params;
79 description "Configuration data of sample-plugin in Honeycomb";
82 // curl -u admin:admin http://localhost:8181/restconf/config/sample-plugin:sample-plugin
85 // curl http://localhost:8181/restconf/operational/sample-plugin:sample-plugin
89 grouping sample-plugin-params {
90 container pg-streams {
106 Create the following sample XML data definition for the above model (:file:`pg-data.xml`).
107 Later on this will initialise one single PG stream.
110 :caption: **pg-data.xml**
112 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
116 <is-enabled>true</is-enabled>
121 Execute the following command within netopeer docker container to install the pg.yang model
125 sysrepoctl -v3 -i pg.yang
128 This command will just schedule the installation, it will be applied once the server is restarted.
130 Stop the container from outside with ``docker stop netopeer2`` and start it again with ``docker start netopeer2``
132 Enter the container like it's mentioned above with ``docker exec -it netopeer2 bin/bash``.
134 You can check all installed modules with ``sysrepoctl -l``. `sample-plugin` module should appear with ``I`` flag.
136 Execute the following the commands to initialise the Yang model with one pg-stream record.
137 We will be using CDS to perform the day-1 and day-2 configuration changes.
142 > connect --host localhost --login root
144 > get --filter-xpath /sample-plugin:*
145 # shows existing pg-stream records (empty)
146 > edit-config --target running --config=/etc/sysrepo/yang/pg-data.xml
147 # initialises Yang model with one pg-stream record
148 > get --filter-xpath /sample-plugin:*
149 # shows initialised pg-stream
151 If the output of the last command is like this, everything went successful:
156 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
160 <is-enabled>true</is-enabled>
166 .. tab:: sysrepo/sysrepo-netopeer2 (legacy)
168 Download and run docker container with ``docker run -d --name netopeer2 -p 830:830 -p 6513:6513 sysrepo/sysrepo-netopeer2:legacy``
170 Enter the container with ``docker exec -it netopeer2 bin/bash``
172 Browse to the target location where all YANG modules exist: ``cd /opt/dev/sysrepo/yang``
174 Create a simple mock YANG model for a packet generator (:file:`pg.yang`).
177 :caption: **pg.yang**
179 module sample-plugin {
182 namespace "urn:opendaylight:params:xml:ns:yang:sample-plugin";
183 prefix "sample-plugin";
186 "This YANG module defines the generic configuration and
187 operational data for sample-plugin in VPP";
189 revision "2016-09-18" {
190 description "Initial revision of sample-plugin model";
193 container sample-plugin {
195 uses sample-plugin-params;
196 description "Configuration data of sample-plugin in Honeycomb";
199 // curl -u admin:admin http://localhost:8181/restconf/config/sample-plugin:sample-plugin
202 // curl http://localhost:8181/restconf/operational/sample-plugin:sample-plugin
206 grouping sample-plugin-params {
207 container pg-streams {
223 Create the following sample XML data definition for the above model (:file:`pg-data.xml`).
224 Later on this will initialise one single PG (packet-generator) stream.
227 :caption: **pg-data.xml**
229 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
233 <is-enabled>true</is-enabled>
238 Execute the following command within netopeer docker container to install the pg.yang model
242 sysrepoctl -i -g pg.yang
244 You can check all installed modules with ``sysrepoctl -l``. `sample-plugin` module should appear with ``I`` flag.
246 In legacy version of `sysrepo/sysrepo-netopeer2` subscribers of a module are required, otherwise they are not
247 running and configurations changes are not accepted, see https://github.com/sysrepo/sysrepo/issues/1395. There is
248 an predefined application mock up which can be used for that. The usage is described
249 here: https://asciinema.org/a/160247. You need to run the following
250 commands to start the example application for subscribing to our sample-plugin YANG module.
254 cd /opt/dev/sysrepo/build/examples
255 ./application_example sample-plugin
257 Following output should appear:
261 ========== READING STARTUP CONFIG sample-plugin: ==========
263 /sample-plugin:sample-plugin (container)
264 /sample-plugin:sample-plugin/pg-streams (container)
267 ========== STARTUP CONFIG sample-plugin APPLIED AS RUNNING ==========
270 The terminal session needs to be kept open after application has started.
272 Open a new terminal and enter the container with ``docker exec -it netopeer2 bin/bash``.
273 Execute the following commands in the container to initialise the Yang model with one pg-stream record.
274 We will be using CDS to perform the day-1 configuration and day-2 configuration changes.
279 > connect --host localhost --login netconf
280 # passwort is netconf
281 > get --filter-xpath /sample-plugin:*
282 # shows existing pg-stream records (empty)
283 > edit-config --target running --config=/opt/dev/sysrepo/yang/pg-data.xml
284 # initialises Yang model with one pg-stream record
285 > get --filter-xpath /sample-plugin:*
286 # shows initialised pg-stream
288 If the output of the last command is like this, everything went successful:
293 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
297 <is-enabled>true</is-enabled>
302 You can also see that there are additional logs in the subscriber application after editing the configuration of our
305 .. tab:: PNF simulator integration project
308 This method of setting up the PNF simulator is not tested by the author of this guide
310 You can refer to `PnP PNF Simulator wiki page <https://wiki.onap.org/display/DW/PnP+PNF+Simulator>`_
311 to clone the GIT repo and start the required docker containers. We are interested in the
312 `sysrepo/sysrepo-netopeer2` docker container to load a simple YANG similar to vFW Packet Generator.
314 Start PNF simulator docker containers. You can consider changing the netopeer image verion to image:
315 `sysrepo/sysrepo-netopeer2:iop` in docker-compose.yml file If you find any issues with the default image.
321 git clone https://github.com/onap/integration.git
325 cd ~/integration/test/mocks/pnfsimulator
329 Verify that you have netopeer docker container are up and running. It will be mapped to host port 830.
333 docker ps -a | grep netopeer
336 Config-assign and config-deploy in CDS
337 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
339 In the following steps the CBA is published in CDS, config-assignment is done and the config is deployed to to the
340 Netconf server through CDS in the last step. We will use this CBA: :download:`zip <media/pnf-simulator-demo-cba.zip>`.
341 If you want to use scripts instead of Postman the CBA also contains all necessary scripts.
347 **There will be different scripts depending on your CDS installation. For running it in an IDE always use scripts with**
348 **-ide.sh prefix. For running CDS in Kubernetes use scripts with -k8s.sh ending. In scripts with -ide.sh prefix**
349 **host will be localhost and port will be 8081. For K8s host ip adress gets automatically detected, port is 8000.**
353 Unzip the downloaded CBA and go to ``/Scripts/`` directory.
355 The below script will call Bootstrap API of CDS which loads the CDS default model artifacts into CDS DB.
356 You should get HTTP status 200 for the below command.
360 bash -x ./bootstrap-cds-ide.sh
361 # bash -x ./bootstrap-cds-k8s.sh
363 Call ``bash -x ./get-cds-blueprint-models-ide.sh`` / ``bash -x ./get-cds-blueprint-models-k8s.sh`` to get all blueprint models in the CDS database.
364 You will see a default model ``"artifactName": "vFW-CDS"`` which was loaded by calling bootstrap.
366 Push the PNF CDS blueprint model data dictionary to CDS by calling ``bash -x ./dd-microk8s-ide.sh ./dd.json`` /
367 ``bash -x ./dd-microk8s-k8s.sh ./dd.json``.
368 This will call the data dictionary endpoint of CDS.
370 Check CDS database for PNF data dictionaries by entering the DB. You should see 6 rows as shown below.
372 **For running CDS in an IDE (accessing mariadb container):**
376 sudo docker exec -it mariadb_container_id mysql -uroot -psdnctl
378 > select name, data_type from RESOURCE_DICTIONARY where updated_by='Aarna service <vmuthukrishnan@aarnanetworks.com>';
380 +---------------------+-----------+
382 +---------------------+-----------+
383 | netconf-password | string |
384 | netconf-server-port | string |
385 | netconf-username | string |
387 | pnf-ipv4-address | string |
388 | stream-count | integer |
389 +---------------------+-----------+
393 Replace the container id with your running mariadb container id.
396 **For running CDS in K8s (accessing MariaDB pod):**
400 ./connect-cds-mariadb-k8s.sh
402 select name, data_type from RESOURCE_DICTIONARY where updated_by='Aarna service <vmuthukrishnan@aarnanetworks.com>';
404 +---------------------+-----------+
406 +---------------------+-----------+
407 | netconf-password | string |
408 | netconf-server-port | string |
409 | netconf-username | string |
411 | pnf-ipv4-address | string |
412 | stream-count | integer |
413 +---------------------+-----------+
419 Move to the main folder of the CBA with ``cd ..`` and archive all folders with ``zip -r pnf-demo.zip *``.
422 The provided CBA is already enriched, the following step anyhow will enrich the CBA again to show the full workflow.
423 For Frankfurt release this causes an issue when the configuration is deployed later on. This happens because some parameters
424 get deleted when enrichment is done a second time. Skip the next step until Deploy/Save Blueprint if you use
425 Frankfurt release and use the CBA as it is. In future this step should be fixed and executed based on an unenriched CBA.
427 Enrich the blueprint through calling the following script. Take care to provide the zip file you downloader earlier.
432 bash -x ./enrich-and-download-cds-blueprint-ide.sh ../pnf-demo.zip
433 # bash -x ./enrich-and-download-cds-blueprint-k8s.sh ../pnf-demo.zip
435 Go to the enriched CBA folder with ``cd /tmp/CBA/`` and unzip with ``unzip pnf-demo.zip``.
437 **Deploy/Save the Blueprint into CDS database**
439 Go to Scripts folder with ``cd Scripts``.
441 Run the following script to save/deploy the Blueprint into the CDS database.
445 bash -x ./save-enriched-blueprint-ide.sh ../pnf-demo.zip
446 # bash -x ./save-enriched-blueprint-k8s.sh ../pnf-demo.zip
448 After that you should see the new model "artifactName": "pnf_netconf" by calling ``bash -x ./get-cds-blueprint-models.sh``
452 The assumption is that we are using the same host to run PNF NETCONF simulator as well as CDS. You will need the
453 IP Adress of the Netconf server container which can be found out with
454 ``docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' netopeer2``. In the
455 following examples we will use 172.17.0.2.
461 bash -x ./create-config-assing-data-ide.sh day-1 172.17.0.2 5
462 # bash -x ./create-config-assing-data-k8s.sh day-1 172.17.0.2 5
464 You can verify the day-1 NETCONF RPC payload looking into CDS DB. You should see the NETCONF RPC with 5
465 streams (fw_udp_1 TO fw_udp_5). Connect to the DB like mentioned above and run the below statement. You should
466 see the day-1 configuration as an output.
470 MariaDB [sdnctl]> select * from TEMPLATE_RESOLUTION where resolution_key='day-1' AND artifact_name='netconfrpc';
472 <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
478 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
482 <is-enabled>true</is-enabled>
486 <is-enabled>true</is-enabled>
490 <is-enabled>true</is-enabled>
494 <is-enabled>true</is-enabled>
498 <is-enabled>true</is-enabled>
506 Create PNF configuration for resolution-key = day-2 (stream-count = 10).
507 You can verify the CURL command JSON pay load file /tmp/day-n-pnf-config.json
511 bash -x ./create-config-assing-data-ide.sh day-2 172.17.0.2 10
512 # bash -x ./create-config-assing-data-k8s.sh day-2 172.17.0.2 10
514 You can verify the day-2 NETCONF RPC payload looking into CDS DB. You should see the NETCONF RPC with 10
515 streams (fw_udp_1 TO fw_udp_10). Connect to the DB like mentioned above and run the below statement. You should
516 see the day-2 configuration as an output.
520 MariaDB [sdnctl]> select * from TEMPLATE_RESOLUTION where resolution_key='day-2' AND artifact_name='netconfrpc';
522 <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
528 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
532 <is-enabled>true</is-enabled>
536 <is-enabled>true</is-enabled>
540 <is-enabled>true</is-enabled>
544 <is-enabled>true</is-enabled>
548 <is-enabled>true</is-enabled>
552 <is-enabled>true</is-enabled>
556 <is-enabled>true</is-enabled>
560 <is-enabled>true</is-enabled>
564 <is-enabled>true</is-enabled>
568 <is-enabled>true</is-enabled>
577 Until this step CDS did not interact with the PNF simulator or device. We just created the day-1 and day-2
578 configurations and stored it in CDS database
582 Now we will make the CDS REST API calls to push the day-1 and day-2 configuration changes to the PNF simulator.
584 If you run CDS in Kubernetes open a new terminal and keep it running with ``bash -x ./tail-cds-bp-log.sh``,
585 we can use this to review the config-deploy actions. If you run CDS in an IDE you can have a look into the IDE terminal.
587 Following command will deploy day-1 configuration.
588 Syntax is ``# bash -x ./process-config-deploy.sh RESOLUTION_KEY PNF_IP_ADDRESS``
592 bash -x ./process-config-deploy-ide.sh day-1 127.17.0.2
593 # bash -x ./process-config-deploy-k8s.sh day-1 127.17.0.2
595 Go back to PNF netopeer cli console like mentioned above and verify if you can see 5 streams fw_udp_1 to fw_udp_5 enabled. If the 5 streams
596 appear in the output as follows, the day-1 configuration got successfully deployed and the use case is successfully done.
600 > get --filter-xpath /sample-plugin:*
602 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
606 <is-enabled>true</is-enabled>
610 <is-enabled>true</is-enabled>
614 <is-enabled>true</is-enabled>
618 <is-enabled>true</is-enabled>
622 <is-enabled>true</is-enabled>
626 <is-enabled>true</is-enabled>
632 The same can be done for day-2 config (follow same steps just with day-2 configuration).
635 Through deployment we did not deploy the PNF, we just modified the PNF. The PNF could also be installed by CDS
636 but this is not targeted in this guide.
640 Download the Postman collection :download:`json <media/pnf-simulator.postman_collection.json>` and import it into
641 your Postman application. Set the collection variables `ip adress` and `port` depending on your CDS installation.
642 This can be done by right clicking the collection, click `edit` and then go to variables.
643 For running CDS in an IDE host should be localhost and port should be 8081. If you run CDS in Kubernetes you can find
644 out ip adress and port number of CDS blueprint processor by executing following command:
648 kubectl get svc -n onap | grep 'cds-blueprints-processor-http'
650 cds-blueprints-processor-http ClusterIP 10.152.183.211 <none> 8080/TCP 3h19m
654 First run `Bootstrap` request which will call Bootstrap API of CDS. This loads the CDS default model artifacts into CDS DB.
655 You should get HTTP status 200 as a response.
657 You can execute `Get Blueprints` to get all blueprint models in the CDS database. You will see a default
658 model "artifactName": "vFW-CDS" in the response body which was loaded by calling bootstrap.
660 Push the PNF CDS blueprint model data dictionary to CDS with `Data Dictionary` request. Request body contains the
661 data from ``dd.json`` of the CBA. This will call the data dictionary endpoint of CDS.
664 For every data dictionary entry CDS API needs to be called seperately. The postman collection contains a loop to
665 go through all entries of :file:`dd.json` and call data dictionary endpoint seperately. To execute this loop,
666 open `Runner` in Postman and run `Data Dictionary` request like it is shown in the picture below.
668 |imageDDPostmanRunner|
670 Check CDS database for PNF data dictionaries by entering the DB in a terminal. You should see 6 rows as shown below.
672 For running CDS in an IDE (accessing mariadb container):
676 sudo docker exec -it mariadb_container_id mysql -uroot -psdnctl
678 > select name, data_type from RESOURCE_DICTIONARY where updated_by='Aarna service <vmuthukrishnan@aarnanetworks.com>';
680 +---------------------+-----------+
682 +---------------------+-----------+
683 | netconf-password | string |
684 | netconf-server-port | string |
685 | netconf-username | string |
687 | pnf-ipv4-address | string |
688 | stream-count | integer |
689 +---------------------+-----------+
691 Replace the container id with your running mariadb container id.
694 For running CDS in K8s (accessing MariaDB pod):
696 Open a terminal and go to ``/Scripts`` directory of your CBA.
700 ./connect-cds-mariadb-k8s.sh
702 select name, data_type from RESOURCE_DICTIONARY where updated_by='Aarna service <vmuthukrishnan@aarnanetworks.com>';
704 +---------------------+-----------+
706 +---------------------+-----------+
707 | netconf-password | string |
708 | netconf-server-port | string |
709 | netconf-username | string |
711 | pnf-ipv4-address | string |
712 | stream-count | integer |
713 +---------------------+-----------+
719 The provided CBA is already enriched, the following steps anyhow will enrich the CBA again to show the full workflow.
720 For Frankfurt release this causes an issue when the configuration is deployed later on. This happens because some parameters
721 get deleted when enrichment is done a second time. Skip the next steps until Deploy/Save Blueprint if you use
722 Frankfurt release and use the CBA as it is. In future this step should be fixed and executed based on an unenriched CBA.
724 Enrich the blueprint through executing the `Enrich Blueprint` request. Take care to provide the CBA file which you
725 downloaded earlier in the request body. After the request got executed save the response body, this will be the
731 **Deploy/Save the Blueprint into CDS database**
733 Run `Save Blueprint` request to save/deploy the Blueprint into the CDS database. Take care to provide the enriched
734 CBA file in the request body.
736 After that you should see the new model "artifactName": "pnf_netconf" by calling `Get Blueprints` request.
740 The assumption is that we are using the same host to run PNF NETCONF simulator as well as CDS. You will need the
741 IP Adress of the Netconf server container which can be found out in terminal with
742 ``docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' netopeer2``. In the provided
743 postman collection 172.17.0.2 is set as default.
745 For creating the day-n config we are using the template file ``day-n-pnf-config.template`` in the folder
746 ``Scripts/templates`` of the CBA. ``CONFIG_NAME``, ``PNF_IP_ADDRESS`` and ``STREAM_COUNT`` are replaced with specific values.
750 Execute the request `Create Config Assign Day-1`. Replace the values in the reqest body if needed.
752 You can verify the day-1 NETCONF RPC payload looking into CDS DB. You should see the NETCONF RPC with 5
753 streams (fw_udp_1 TO fw_udp_5). Connect to the DB like mentioned above and run the below statement. You should
754 see the day-1 configuration as an output.
758 MariaDB [sdnctl]> select * from TEMPLATE_RESOLUTION where resolution_key='day-1' AND artifact_name='netconfrpc';
760 <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
766 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
770 <is-enabled>true</is-enabled>
774 <is-enabled>true</is-enabled>
778 <is-enabled>true</is-enabled>
782 <is-enabled>true</is-enabled>
786 <is-enabled>true</is-enabled>
795 **Day-2 configuration:**
797 Execute the request `Create Config Assign Day-2`. It will do the same request like in day-1-config just with
798 different values (resolution-key = day-2, stream-count = 10).
800 You can verify the day-2 NETCONF RPC payload looking into CDS DB. You should see the NETCONF RPC with 10
801 streams (fw_udp_1 TO fw_udp_10). Connect to the DB like mentioned above and run the below statement. You should
802 see the day-2 configuration as an output.
806 MariaDB [sdnctl]> select * from TEMPLATE_RESOLUTION where resolution_key='day-2' AND artifact_name='netconfrpc';
808 <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
814 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
818 <is-enabled>true</is-enabled>
822 <is-enabled>true</is-enabled>
826 <is-enabled>true</is-enabled>
830 <is-enabled>true</is-enabled>
834 <is-enabled>true</is-enabled>
838 <is-enabled>true</is-enabled>
842 <is-enabled>true</is-enabled>
846 <is-enabled>true</is-enabled>
850 <is-enabled>true</is-enabled>
854 <is-enabled>true</is-enabled>
863 Until this step CDS did not interact with the PNF simulator or device. We just created the day-1 and day-2
864 configurations and stored it in CDS database
868 Now we will make the CDS REST API calls to push the day-1 and day-2 configuration changes to the PNF simulator.
870 If you run CDS in Kubernetes open a terminal in `/Scripts` folder and keep it running with ``bash -x ./tail-cds-bp-log.sh``,
871 we can use this to review the config-deploy actions. If you run CDS in an IDE you can have a look into the IDE terminal.
873 Executing `Config Assign Day-1 Deploy` request will deploy day-1 configuration. Take care to provide the right PNF
874 IP Adress in the request body.
876 Go back to PNF netopeer cli console like mentioned above and verify if you can see 5 streams fw_udp_1 to fw_udp_5 enabled. If the 5 streams
877 appear in the output as follows, the day-1 configuration got successfully deployed and the use case is successfully done.
881 > get --filter-xpath /sample-plugin:*
883 <sample-plugin xmlns="urn:opendaylight:params:xml:ns:yang:sample-plugin">
887 <is-enabled>true</is-enabled>
891 <is-enabled>true</is-enabled>
895 <is-enabled>true</is-enabled>
899 <is-enabled>true</is-enabled>
903 <is-enabled>true</is-enabled>
907 <is-enabled>true</is-enabled>
913 Day-2 configuration can be deployed the same way, just use `day-2` as a resolution key in the `Config Assign Depoy`
917 Through deployment we did not deploy the PNF, we just modified the PNF. The PNF could also be installed by CDS
918 but this is not targeted in this guide.
922 Both CBA file and Postman collection should be integrated into source code of CDS. There is already an approach for that,
923 see https://gerrit.onap.org/r/c/ccsdk/cds/+/112288. Updated Scripts and Postman collection needs to be added to this change.
926 Creators of this guide
927 ~~~~~~~~~~~~~~~~~~~~~~~
931 Jakob Krieg (Rocketchat @jakob.Krieg); Eli Halych (Rocketchat @elihalych)
933 This guide is a derivate from https://wiki.onap.org/display/DW/PNF+Simulator+Day-N+config-assign+and+config-deploy+use+case.
936 .. |saveResponseImage| image:: media/save-response-postman.png
939 .. |imageDDPostmanRunner| image:: media/dd-postman-runner.png