Versions Compared

Version Old Version 17 New Version 18
Changes made by

A. Seaudi

Yuriy Malakov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

The purpose of this page is to describe the vDNS use case instantiation using the Controller Design Studio in ONAP Dublin Release.


What's new:

We can see from the demo that now we don't need to perform SDNC Preloading to instantiate the service. The VNF naming and IP addressing will be auto assigned.

...

And later during the instantiation process, the configuration is deployed on the VF module by CDS via the new ConfigDeployBB.


Video demo of the vDNS instantiation

View file
namevdns-cds-dublin-7-6-2019.mp4
height250

Summary of the video demo

Before running the instantitation, we need to distribute the vDNS service model in ONAP.

...



  • 1st Rest call will give us the service model details like UUID, Invariant UUID, and Service Model Name.


  • 2nd Rest call will give us the VNF and VF Module details.
Note
titleSTEP CDS2: Expose SO Catalog API

SO Catalog DB is NOT exposed by default, you will need something like the command below to be able to send the CDS #2 rest call to SO Catalog and get back the service VNF model details.

Code Block
kubectl -n onap expose pod onap-so-so-catalog-db-adapter-56d9cc554b-9fszd --type=LoadBalancer



  • 3rd Rest call will pull the details from the 1st and 2nd calls, and build the SO Service Assignment and Activation request.
  • I added a 4th Rest call in the collection that will pull the request id from the 3rd call coming from SO, and will show us the status of the requets, so we can track the progress, and see if it completes successfully.

Stack creation in Openstack

We can see the final stack created in Openstack, and the final network topology below.

Environment preparation for the Postman Collection:

In order to run the Postman collection correctly, we need to create 3 environment variables in Postman:

...

  • lcpCloudRegionId : the cloud-region name 
  • tenantId : the tenant id
  • public_net_id : the public network id in Openstack
  • onap_private_net_id : the private network id in Openstack, we need this as this is not created by the auto assignment service
  • onap_private_subnet_id : and the private subnet id
  • pub_key : the public key to be put on the VMs
  • image_name : Ubuntu 16 image name
  • flavor_name : flavor
  • sec_group : security group that will be applied to the VMs

SO Workflow BBs

After the Service Instantiation Rest Call to SO, we can see that SO decomposes the service into 1 VNF + 4 VF Modules, and SO created 18 Building Blocks that will be executed to instantiate the use case.

...

Code Block
titleSO BPMN Logs
collapsetrue
2019-06-07T03:15:10.440Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - Found Service - 1    Vnf - 1    VfModule - 4    VolumeGroup - 0    Network - 0    VirtualLink - 0    NetworkCollection - 0    Configuration - 0    InstanceGroup - 0    
...
2019-06-07T03:15:10.519Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - List of BuildingBlocks to execute:
2019-06-07T03:15:10.520Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - AssignServiceInstanceBB
2019-06-07T03:15:10.520Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - AssignVnfBB
2019-06-07T03:15:10.521Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - AssignVfModuleBB
2019-06-07T03:15:10.521Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - AssignVfModuleBB
2019-06-07T03:15:10.522Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - AssignVfModuleBB
2019-06-07T03:15:10.522Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - AssignVfModuleBB
2019-06-07T03:15:10.523Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ConfigAssignVnfBB
2019-06-07T03:15:10.523Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - CreateVfModuleBB
2019-06-07T03:15:10.524Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - CreateVfModuleBB
2019-06-07T03:15:10.524Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - CreateVfModuleBB
2019-06-07T03:15:10.525Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - CreateVfModuleBB
2019-06-07T03:15:10.525Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ActivateVfModuleBB
2019-06-07T03:15:10.526Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ActivateVfModuleBB
2019-06-07T03:15:10.526Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ActivateVfModuleBB
2019-06-07T03:15:10.527Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ActivateVfModuleBB
2019-06-07T03:15:10.527Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ConfigDeployVnfBB
2019-06-07T03:15:10.528Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ActivateVnfBB
2019-06-07T03:15:10.528Z|f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3| o.o.s.b.i.workflow.tasks.WorkflowAction - ActivateServiceInstanceBB


SO ConfigAssignBB

In this BB, a configlet is generated and saved in CDS DB.

...

Code Block
titleConfiglets pushed into CDS DB
collapsetrue
SELECT * FROM sdnctl.RESOURCE_RESOLUTION_RESULT where resolution_key="fr2_ONAP-NF_20190607T031522008Z";

+--------------------------------------+--------------------+----------------+-------------------+---------------------+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| resource_resolution_result_id        | artifact_name      | blueprint_name | blueprint_version | creation_date       | resolution_key                  | result                                                                                                                                                                         |
+--------------------------------------+--------------------+----------------+-------------------+---------------------+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 15ba611c-62f9-4701-aa5f-c7e698a96a3a | incremental-config | test           | 1.0.0             | 2019-06-07 03:16:02 | fr2_ONAP-NF_20190607T031522008Z | {
    "vdns-instance": [
        {
            "ip-addr": "192.168.20.181",
            "oam-ip-addr": "10.0.101.187",
            "enabled": true
        }
    ]
}   |
| 40d33748-a61a-421a-80ac-ca3fee8c4996 | baseconfig         | test           | 1.0.0             | 2019-06-07 03:16:02 | fr2_ONAP-NF_20190607T031522008Z |      {
    "vdns-instance": [
        {
            "ip-addr": "192.168.20.181",
            "oam-ip-addr": "10.0.101.187",
            "enabled": false
        }
    ]
} |
+--------------------------------------+--------------------+----------------+-------------------+---------------------+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)


SO ConfigDeployBB

In this BB, the config generated by ConfigAssign from teh CDS DB, and push the config to the network element.

...

Code Block
titleConfigDeploy logs from Blueprint Processor
collapsetrue
2019-06-07 03:17:50,060|||DefaultDispatcher-worker-3||||INFO||||||| processing request id f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3
2019-06-07 03:17:50,062|||DefaultDispatcher-worker-3||||INFO||||||| cba file name(test), version(1.0.0) already present(/opt/app/onap/blueprints/deploy/test/1.0.0)
2019-06-07 03:17:50,062|||DefaultDispatcher-worker-3||||INFO||||||| blueprint base path /opt/app/onap/blueprints/deploy/test/1.0.0
2019-06-07 03:17:50,065|||DefaultDispatcher-worker-3||||INFO||||||| Reading blueprint path(/opt/app/onap/blueprints/deploy/test/1.0.0) and entry definition file (Definitions/vDNS-CDS.json)
2019-06-07 03:17:50,069|||grpc-default-executor-3||||INFO||||||| Completed
2019-06-07 03:17:50,081|||DefaultDispatcher-worker-3||||INFO||||||| assign workflow config-deploy input value ({"resolution-key":"fr2_ONAP-NF_20190607T031522008Z","config-deploy-properties":{"service-instance-id":"1a0fbd43-0ab6-4d67-99f4-14a890505a8d","vnf-id":"1bed94d9-9a12-458a-b891-7c04796b5af4","vnf-name":"fr2_ONAP-NF_20190607T031522008Z","service-model-uuid":"ad40aa27-b3fe-4fc3-8755-ebb1494f5913","vnf-customization-uuid":"6409e9d9-a469-4546-a7b4-e508ecc1e77f"}})
2019-06-07 03:17:50,081|||DefaultDispatcher-worker-3||||INFO||||||| Executing workflow(config-deploy) NodeTemplate(config-deploy), derived from(tosca.nodes.Component)
2019-06-07 03:17:50,081|||DefaultDispatcher-worker-3||||INFO||||||| executing node template(config-deploy) component(component-netconf-executor) interface(ComponentNetconfExecutor) operation(process)
2019-06-07 03:17:50,084|||DefaultDispatcher-worker-3||||INFO||||||| preparing request id(f804a2b6-0e0d-49c4-bd67-7ba3ec0694b3) for workflow(config-deploy) step(config-deploy)
2019-06-07 03:17:50,085|||DefaultDispatcher-worker-3||||INFO||||||| resolveNodeTemplateInterfaceOperationInputs for node template (config-deploy),interface name (ComponentNetconfExecutor), operationName(process)
2019-06-07 03:17:50,085|||DefaultDispatcher-worker-3||||INFO||||||| input definition for node template (config-deploy), values ({script-type="jython", script-class-reference="Scripts/python/ConfigDeploy.py", instance-dependencies=[], dynamic-properties="*config-deploy-properties"})
2019-06-07 03:17:50,085|||DefaultDispatcher-worker-3||||INFO||||||| creating component function of script type(jython), reference name(Scripts/python/ConfigDeploy.py) and instanceDependencies([resource-resolution-service])
2019-06-07 03:17:50,085|||DefaultDispatcher-worker-3||||INFO||||||| Getting Jython Script Class(ConfigDeploy)
2019-06-07 03:17:50,137|||DefaultDispatcher-worker-3||||INFO||||||| Component Object org.python.proxies.__main__$ConfigDeploy$1@3b40b947
{'ResolutionHelper': <class common.ResolutionHelper at 0x2>, '__name__': '__main__', 'log': Logger[ConfigDeploy], 'netconf_constant': <module 'netconf_constant' from '/opt/app/onap/scripts/jython/ccsdk_netconf/netconf_constant.py'>, 'NetconfClient': <class netconfclient.NetconfClient at 0x3>, '__builtins__': <module '__builtin__' (built-in)>, '__doc__': None, 'NetconfComponentFunction': <type 'org.onap.ccsdk.cds.blueprintsprocessor.functions.netconf.executor.NetconfComponentFunction'>, 'sys': <module 'sys' (built-in)>, 'ConfigDeploy': org.python.proxies.__main__$ConfigDeploy$1@3b40b947, '__package__': None}
2019-06-07 03:17:50,139|||DefaultDispatcher-worker-3||||INFO||||||| resolveNodeTemplateCapabilityProperties for node template(netconf-device) capability (netconf)
2019-06-07 03:17:50,273|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Connecting to Netconf Device with timeouts C:5, R:5, I:99999
2019-06-07 03:17:50,282|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Starting SSH session
2019-06-07 03:17:50,293|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: SSH session created
2019-06-07 03:17:50,359|||sshd-SshClient[6f8f3e0f]-nio2-thread-3||||WARN||||||| Server at /84.39.43.58:2831 presented unverified DSA key: SHA256:5/3iUYqX/3rf1lFQ0BxF4GZlxRGBV8MkHp6mqX/2JtM
2019-06-07 03:17:50,380|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: SSH session authenticated
2019-06-07 03:17:50,402|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: SSH NETCONF subsystem channel opened
2019-06-07 03:17:50,402|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
    <capability>urn:ietf:params:netconf:base:1.1</capability>
  </capabilities>
</hello>
]]>]]>
2019-06-07 03:17:50,421|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId: -1  
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:xml:ns:yang:ietf-interfaces?module=ietf-interfaces&revision=2014-05-08</capability>
<capability>urn:ietf:params:xml:ns:yang:iana-if-type?module=iana-if-type&revision=2014-05-08</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl?module=opendaylight-sal-binding-broker-impl&revision=2013-10-28</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?module=ietf-netconf-monitoring&revision=2010-10-04</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:config:legacy-entity-ownership-service-provider?module=opendaylight-legacy-entity-ownership-service-provider&revision=2016-02-26</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2010-09-24</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:northbound:notification?module=netconf-northbound-notification&revision=2015-08-06</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:config:netconf:northbound:impl?module=netconf-northbound-impl&revision=2015-01-12</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:northbound:notification:impl?module=netconf-northbound-notification-impl&revision=2015-08-07</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding?module=opendaylight-md-sal-binding&revision=2013-10-28</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:v1:codec?module=opendaylight-md-sal-binding-v1-codec&revision=2016-07-14</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:general-entity?module=general-entity&revision=2015-08-20</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom?module=opendaylight-md-sal-dom&revision=2013-10-28</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote?module=sal-remote&revision=2014-01-14</capability>
<capability>urn:opendaylight:params:xml:ns:yang:md:sal:config:impl:cluster-singleton-service?module=cluster-singleton-service-impl&revision=2016-07-18</capability>
<capability>urn:opendaylight:yang:extension:yang-ext?module=yang-ext&revision=2013-07-09</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:rest:connector?module=opendaylight-rest-connector&revision=2014-07-24</capability>
<capability>urn:ietf:params:xml:ns:yang:rpc-context?module=rpc-context&revision=2013-06-17</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?module=ietf-netconf-notifications&revision=2012-02-06</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:config:netconf:auth?module=netconf-auth&revision=2015-07-15</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:spi:operational-dom-store?module=opendaylight-operational-dom-datastore&revision=2014-06-17</capability>
<capability>urn:ietf:params:netconf:capability:exi:1.0</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:north:mapper?module=netconf-northbound-mapper&revision=2015-01-14</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&revision=2011-06-01</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring?module=ietf-restconf-monitoring&revision=2017-01-26</capability>
<capability>urn:TBD:params:xml:ns:yang:network-topology?module=network-topology&revision=2013-10-21</capability>
<capability>urn:opendaylight:params:xml:ns:yang:vlb-business-vnf-onap-plugin?module=vlb-business-vnf-onap-plugin&revision=2016-09-18</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-yang-types?module=ietf-yang-types&revision=2013-07-15</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:northbound:ssh?module=netconf-northbound-ssh&revision=2015-01-14</capability>
<capability>urn:TBD:params:xml:ns:yang:network-topology?module=network-topology&revision=2013-07-12</capability>
<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-restconf?module=ietf-restconf&revision=2013-10-19</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:spi:entity-ownership-service?module=opendaylight-entity-ownership-service&revision=2015-08-10</capability>
<capability>urn:sal:restconf:event:subscription?module=sal-remote-augment&revision=2014-07-08</capability>
<capability>instance:identifier:patch:module?module=instance-identifier-patch-module&revision=2015-11-21</capability>
<capability>subscribe:to:notification?module=subscribe-to-notification&revision=2016-10-28</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-restconf?module=ietf-restconf&revision=2017-01-26</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:northbound:tcp?module=netconf-northbound-tcp&revision=2015-04-23</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:mdsal:mapper?module=netconf-mdsal-mapper&revision=2015-01-14</capability>
<capability>urn:opendaylight:params:xml:ns:yang:md:sal:config:spi:cluster-singleton-service?module=cluster-singleton-service-spi&revision=2016-07-18</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:common?module=opendaylight-md-sal-common&revision=2013-10-28</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:sal:restconf:service?module=sal-restconf-service&revision=2015-07-08</capability>
<capability>urn:opendaylight:params:xml:ns:yang:health-vnf-onap-plugin?module=health-vnf-onap-plugin&revision=2016-09-18</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:inmemory-datastore-provider?module=opendaylight-inmemory-datastore-provider&revision=2014-06-17</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:config?module=config&revision=2013-04-05</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:mdsal:notification?module=netconf-mdsal-notification&revision=2015-08-03</capability>
<capability>urn:ietf:params:xml:ns:netconf:notification:1.0?module=notifications&revision=2008-07-14</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netconf:mdsal:monitoring?module=netconf-mdsal-monitoring&revision=2015-02-18</capability>
<capability>urn:ietf:params:xml:ns:netmod:notification?module=nc-notifications&revision=2008-07-14</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring-extension?module=ietf-netconf-monitoring-extension&revision=2013-12-10</capability>
<capability>urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?module=odl-general-entity&revision=2015-09-30</capability>
<capability>urn:ietf:params:netconf:base:1.1</capability>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:spi:config-dom-store?module=opendaylight-config-dom-datastore&revision=2014-06-17</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:config:netconf:northbound?module=netconf-northbound&revision=2015-01-14</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:netty?module=netty&revision=2013-11-19</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:threadpool?module=threadpool&revision=2013-04-09</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-yang-library?module=ietf-yang-library&revision=2016-06-21</capability>
<capability>urn:opendaylight:params:xml:ns:yang:controller:protocol:framework?module=protocol-framework&revision=2014-03-13</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2013-07-15</capability>
</capabilities>
<session-id>3</session-id>
</hello>

2019-06-07 03:17:50,423|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Connected to Netconf Device
2019-06-07 03:17:50,423|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: lock: messageId(1)
2019-06-07 03:17:50,423|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(1)
2019-06-07 03:17:50,423|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lock>
<target>
<candidate/>
</target>
</lock>
</rpc>
]]>]]>
2019-06-07 03:17:50,429|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:17:55,426|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: discard: messageId(2)
2019-06-07 03:17:55,426|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(2)
2019-06-07 03:17:55,426|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<discard-changes/>
</rpc>
]]>]]>
2019-06-07 03:17:55,434|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:00,428|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: editConfig: messageId(3)
2019-06-07 03:18:00,428|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(3)
2019-06-07 03:18:00,428|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="3" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<default-operation>none</default-operation>
<config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
{
    "vdns-instance": [
        {
            "ip-addr": "192.168.20.181",
            "oam-ip-addr": "10.0.101.187",
            "enabled": true
        }
    ]
}
</config>
</edit-config>
</rpc>
]]>]]>
2019-06-07 03:18:00,434|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:05,429|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: editConfig: messageId(4)
2019-06-07 03:18:05,429|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(4)
2019-06-07 03:18:05,429|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="4" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<default-operation>none</default-operation>
<config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
{
    "vdns-instance": [
        {
            "ip-addr": "192.168.20.181",
            "oam-ip-addr": "10.0.101.187",
            "enabled": false
        }
    ]
}
</config>
</edit-config>
</rpc>
]]>]]>
2019-06-07 03:18:05,436|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:10,430|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(5)
2019-06-07 03:18:10,430|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="5" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<validate>
<source>
<candidate/>
</source>
</validate>
</rpc>
]]>]]>
2019-06-07 03:18:10,437|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:15,431|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: commit: messageId(6)
2019-06-07 03:18:15,431|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(6)
2019-06-07 03:18:15,432|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="6" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit>
</commit>
</rpc>
]]>]]>
2019-06-07 03:18:15,438|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:20,432|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: unLock: messageId(7)
2019-06-07 03:18:20,433|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(7)
2019-06-07 03:18:20,435|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="7" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<unlock>
<target>
<candidate/>
</target>
</unlock>
</rpc>
]]>]]>
2019-06-07 03:18:20,443|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:25,436|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: closeSession: messageId(8)
2019-06-07 03:18:25,436|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(8)
2019-06-07 03:18:25,436|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="8" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<close-session/>
</rpc>
]]>]]>
2019-06-07 03:18:25,444|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:30,437|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: closeSession: messageId(9)
2019-06-07 03:18:30,437|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: send asyncRpc with messageId(9)
2019-06-07 03:18:30,438|||DefaultDispatcher-worker-3||||INFO||||||| 84.39.43.58:2831: Sending message: 
 <?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="9" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<kill-session/>
</rpc>
]]>]]>
2019-06-07 03:18:30,445|||Thread-27||||INFO||||||| 84.39.43.58:2831: Received message with messageId:   
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>rpc</error-type>
<error-tag>malformed-message</error-tag>
<error-severity>error</error-severity>
<error-message>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</error-message>
<error-info>
<cause>java.lang.IllegalStateException: Malformed chunk header encountered (byte 0)</cause>
</error-info>
</rpc-error>
</rpc-reply>

2019-06-07 03:18:35,446|||DefaultDispatcher-worker-3||||INFO||||||| Preparing Response...
2019-06-07 03:18:35,446|||DefaultDispatcher-worker-3||||INFO||||||| resolveNodeTemplateInterfaceOperationOutputs for node template (config-deploy),interface name (ComponentNetconfExecutor), operationName(process)
2019-06-07 03:18:35,446|||DefaultDispatcher-worker-3||||INFO||||||| resolveWorkflowOutputs for workflow(config-deploy)


Results of the Postman Rest calls:

Below the output of the calls shown in the video:

...