Creation and Deployment of Vendor Device Adapters

Introduction

This section of the document provides information on how to create and deploy VDAs.

Vendor Device Adapters (VDA) are needed when a vendorAN

Standard Device Adapters

SDAs are device adapters that represent the standard data model for a type of device (e.g., DPU, OLT).

This release of OB-BAA, SDAs for the DPU and OLT are available in the obbaa/resources/models/standard-adapters directory.

The following is a example of a SDA for a DPU. Note that the SDA is identified by its type, interfaceVersion, model and vendor attributes.

Sample SDA device-adapter.xml

<?xml version="1.0" encoding="UTF-8"?>
<Adapter type="DPU" interfaceVersion="1.0" model="standard" vendor="BBF"
         xmlns="http://www.bbf.org/obbaa/schemas/adapter/1.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.bbf.org/obbaa/schemas/adapter/1.0
                    ../../../../../adapter-schema-fwk/src/main/xsd/device-adapter.xsd">
  
    <capabilities>
        <value>urn:ietf:params:netconf:base:1.0</value>
        <value>urn:ietf:params:netconf:base:1.1</value>
        <value>urn:ietf:params:netconf:capability:writable-running:1.0</value>
        <value>urn:ietf:params:netconf:capability:notification:1.0</value>
        <value>urn:ietf:params:netconf:capability:interleave:1.0</value>
        <value>urn:ietf:params:netconf:capability:interleave:1.0</value>
    </capabilities>
  
</Adapter>

Vendor Device Adapters

VDAs are device adapters that are specific to a vendor's implementation of a type of standard device. VDAs are defined for a vendor's specific version, model and type of vendor AN that is translated to a pAN that is represented using a SDA.

Multiple instances of a vendorAN can use the same instance of a VDA,

Because a VDA is to be translated into a pAN, any request for a device created using the VDA is validated against their corresponding SDA. If the validation of the VDA fails against the definition of the SDA, the creation will of the device instance will fail.

Creation of a VDA

A VDA is comprised of 2 main artifacts - An artifact that identifies the features of the VDA and a code bundle for each feature.

This release of OB-BAA provides 2 examples of a VDA located in the obbaa/resources/examples/adapters directory. These examples are:

The diagram below depicts the structure for protocol translation example. Note the two artifacts (feature: protocol-transl-feature, code: protocol-transl-sample-adapter). The adapter bundle artifact is created as Karaf kar file.

VDA Adapter Bundle artifact

The example adapter bundle that we will review is located at: obbaa/resources/examples/adapters/protocol-translation-example/protocol-transl-sample-adapter.

In this adapter bundle we see that the model and associated YANG modules that the VDA supports is located in the adapter bundle's resource directory.

Example device-adapter.xml for protocol tls

<?xml version="1.0" encoding="UTF-8"?>
<Adapter type="DPU" interfaceVersion="1.0" model="protocol-tls" vendor="sample"
         xmlns="http://www.bbf.org/obbaa/schemas/adapter/1.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://www.bbf.org/obbaa/schemas/adapter/1.0
                    ../../../../../adapter-schema-fwk/src/main/xsd/device-adapter.xsd">

    <capabilities>
        <value>urn:ietf:params:netconf:base:1.0</value>
        <value>urn:ietf:params:netconf:base:1.1</value>
        <value>urn:ietf:params:netconf:capability:writable-running:1.0</value>
        <value>urn:ietf:params:netconf:capability:notification:1.0</value>
        <value>urn:ietf:params:netconf:capability:interleave:1.0</value>
    </capabilities>

    <developer>Sample developer for Protocol Translation</developer>
    <revisions>
        <revision>2019-01-05</revision>
        <revision>2018-12-30</revision>
    </revisions>
    <isNetconf>false</isNetconf>

</Adapter>

VDA Feature artifact

The example feature artifact that we will review is located at: obbaa/resources/examples/adapters/protocol-translation-example/protocol-transl-feature.

In this feature artifact we see that the VDA lists the feature that represents the VDA along with the associated adapter bundle and a dependent 3rd party bundle.

Deploying a VDA

Once the VDA is created, the VDA needs to be deployed into the BAA layer. The steps to accomplish this are:

  1. Build a Karaf kar file that represents the VDA

  2. Place the VDA into the data store for the device adapters (/baa/stores/deviceAdapter)

  3. Request that the BAA layer deploy the VDA into the running BAA layer's runtime environment

The following is a list of example commands and actions to deploy the VDA into the BAA layer's runtime environment:

Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
	<get>
		<filter type="subtree">
			<network-manager xmlns="urn:bbf:yang:obbaa:network-manager">
				<device-adapters xmlns="urn:bbf:yang:obbaa:network-manager">
				 <device-adapter>
					 <type/>
					 <interface-version/>
					 <model/>
					 <vendor/>
					 <is-netconf/>
				 </device-adapter>
				</device-adapters>
			</network-manager>
		</filter>
	</get>
</rpc>


Sample response: See that the SDAs are deployed:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <data>
    <baa-network-manager:network-manager xmlns:baa-network-manager="urn:bbf:yang:obbaa:network-manager">
      <device-adapters xmlns="urn:bbf:yang:obbaa:network-manager">
        <device-adapter>
          <type>DPU</type>
          <interface-version>1.0</interface-version>
          <model>standard</model>
          <vendor>BBF</vendor>
          <is-netconf>true</is-netconf>
        </device-adapter>
        <device-adapter>
          <type>OLT</type>
          <interface-version>1.0</interface-version>
          <model>standard</model>
          <vendor>BBF</vendor>
          <is-netconf>true</is-netconf>
        </device-adapter>
      </device-adapters>
    </baa-network-manager:network-manager>
  </data>
</rpc-reply>

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="10101">
	<action xmlns="urn:ietf:params:xml:ns:yang:1">
		<deploy-adapter xmlns="urn:bbf:yang:obbaa:device-adapters">
			<deploy>
				<adapter-archive>protocol-transl-feature-2.0.0.kar</adapter-archive>
			</deploy>
		</deploy-adapter>
	</action>
</rpc>
	karaf@root()> kar:list
	KAR Name
	--------------------------------------
	protocol-transl-feature-2.0.0
	karaf@root()> list
	START LEVEL 100 , List Threshold: 50
	 ID | State  | Lvl | Version             | Name
	------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
	 10 | Active |  50 | 1.59                | bcprov
	 11 | Active |  50 | 1.59                | bctls
	 22 | Active |  80 | 1.1.0               | ClassMate
	 23 | Active |  80 | 3.18.1.GA           | Javassist
	 25 | Active |  80 | 2.1.0.v201304241213 | Java Persistence API 2.1
	 32 | Active |  80 | 1.8.2.2             | Apache ServiceMix :: Bundles :: ant
	 33 | Active |  80 | 2.7.7.5             | Apache ServiceMix :: Bundles :: antlr
	 34 | Active |  80 | 1.6.1.5             | Apache ServiceMix :: Bundles :: dom4j
	 35 | Active |  80 | 1.9.2.1             | Apache ServiceMix :: Bundles :: jasypt
	 63 | Active |  80 | 4.0.4.Final         | hibernate-commons-annotations
	 64 | Active |  80 | 4.3.6.Final         | hibernate-core
	 65 | Active |  80 | 4.3.6.Final         | hibernate-entitymanager
	 66 | Active |  80 | 4.3.6.Final         | hibernate-osgi
	 67 | Active |  80 | 1.2.2.Final         | Java Annotation Indexer
	 68 | Active |  80 | 3.1.4.GA            | JBoss Logging 3
	 69 | Active |  80 | 1.0.2.Final         | JACC 1.4 API
	 70 | Active |  80 | 1.5.0               | OPS4J Base - Service Provider Access
	 71 | Active |  80 | 1.1.0               | OPS4J Pax JDBC Generic Driver Extender
	 72 | Active |  80 | 1.1.0               | OPS4J Pax JDBC Config
	 73 | Active |  80 | 1.1.0               | OPS4J Pax JDBC Pooling Support Base
	 78 | Active |  80 | 1.0.0.201505202023  | org.osgi:org.osgi.service.jdbc
	 79 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/Aggregator
	 80 | Active |  80 | 1.14                | animalsniffer-annotations
	 81 | Active |  80 | 1.46                | bcprov
	 82 | Active |  80 | 23.6.1.jre          | Guava: Google Core Libraries for Java
	 83 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/Device Adapter framework
	 84 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/Device Manager
	 85 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/Device Manager Entities
	 86 | Active |  80 | 2.4.3               | ehcache-core
	 87 | Active |  80 | 2.0.18              | errorprone-annotations
	 88 | Active |  80 | 4.1.16.Final        | Netty/Buffer
	 89 | Active |  80 | 4.1.16.Final        | Netty/Codec
	 90 | Active |  80 | 4.1.16.Final        | Netty/Common
	 91 | Active |  80 | 4.1.16.Final        | Netty/Handler
	 92 | Active |  80 | 4.1.16.Final        | Netty/Resolver
	 93 | Active |  80 | 4.1.16.Final        | Netty/Transport
	 94 | Active |  80 | 1.1                 | j2objc-annotations
	 96 | Active |  80 | 1.2.0               | CDI APIs
	 97 | Active |  80 | 1.2                 | javax.interceptor API
	 98 | Active |  80 | 3.0.1               | Java Servlet API
	 99 | Active |  80 | 1.2                 | javax.transaction API
	100 | Active |  80 | 2.0                 | javax.ws.rs-api
	101 | Active |  80 | 1.1.3               | jdom
	103 | Active |  80 | 2.8                 | Joda-Time
	104 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/Library Consult
	105 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/NBI Adapter
	106 | Active |  80 | 4.7.1               | ANTLR 4 Runtime
	117 | Active |  80 | 2.3.0               | Apache Aries JPA Container API
	118 | Active |  80 | 2.3.0               | Apache Aries JPA blueprint
	119 | Active |  80 | 2.3.0               | Apache Aries JPA container
	120 | Active |  80 | 2.3.0               | Apache Aries JPA support
	121 | Active |  80 | 1.1.1               | Apache Aries Transaction Blueprint
	122 | Active |  80 | 2.1.0               | Apache Aries Transaction Blueprint
	123 | Active |  80 | 1.3.0               | Apache Aries Transaction Manager
	124 | Active |  80 | 1.9.2               | Apache Commons BeanUtils
	125 | Active |  80 | 3.2.1               | Commons Collections
	126 | Active |  80 | 2.1.1               | Apache Commons DBCP
	127 | Active |  80 | 2.4.0               | Commons IO
	128 | Active |  80 | 1.3                 | Commons JXPath
	129 | Active |  80 | 2.6                 | Commons Lang
	130 | Active |  80 | 3.5.0               | Apache Commons Lang
	131 | Active |  80 | 2.4.2               | Apache Commons Pool
	132 | Active |  80 | 1.0.2               | Apache Felix Coordinator Service
	147 | Active |  80 | 4.0.4               | Apache Karaf :: JDBC :: Core
	159 | Active |  80 | 1.0.0.6             | Apache ServiceMix :: Bundles :: aopalliance
	160 | Active |  80 | 3.2.4.1             | Apache ServiceMix :: Bundles :: cglib
	161 | Active |  80 | 1.0.0.2             | Apache ServiceMix :: Bundles :: javax.inject
	164 | Active |  80 | 1.3.0               | Apache Mina SSHD :: Core
	166 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-lib/netconf-api
	167 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-fwk/auth-spi
	168 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-lib/netconf-client
	169 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-lib/netconf-notification-app
	170 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-fwk/netconf-persistence-app
	171 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-lib/netconf-server
	172 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-fwk/netconf-server-modelnode-fwk
	173 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-fwk/stack-api
	174 | Active |  80 | 1.0.0.SNAPSHOT      | netconf-fwk/stack-logging-api
	176 | Active |  80 | 1.3.172             | H2 Database Engine
	177 | Active |  70 | 4.3.6.Final         | hibernate-ehcache
	178 | Active |  80 | 2.3.4               | HSQLDB
	180 | Active |  80 | 1.5.9.0             | MariaDB JDBC Client
	181 | Active |  80 | 2.0.11              | concepts
	182 | Active |  80 | 2.0.11              | odlext-model-api
	183 | Active |  80 | 2.0.11              | odlext-parser-support
	184 | Active |  80 | 2.0.11              | openconfig-model-api
	185 | Active |  80 | 2.0.11              | openconfig-parser-support
	186 | Active |  80 | 2.0.11              | rfc6536-model-api
	187 | Active |  80 | 2.0.11              | rfc6536-parser-support
	188 | Active |  80 | 2.0.11              | rfc7952-model-api
	189 | Active |  80 | 2.0.11              | rfc7952-parser-support
	190 | Active |  80 | 2.0.11              | rfc8040-model-api
	191 | Active |  80 | 2.0.11              | rfc8040-parser-support
	192 | Active |  80 | 1.0.11              | triemap
	193 | Active |  80 | 2.0.11              | util
	194 | Active |  80 | 2.0.11              | yang-common
	195 | Active |  80 | 2.0.11              | yang-model-api
	196 | Active |  80 | 2.0.11              | yang-model-util
	197 | Active |  80 | 2.0.11              | yang-parser-api
	198 | Active |  80 | 2.0.11              | yang-parser-impl
	199 | Active |  80 | 2.0.11              | yang-parser-reactor
	200 | Active |  80 | 2.0.11              | yang-parser-rfc7950
	201 | Active |  80 | 2.0.11              | yang-parser-spi
	202 | Active |  80 | 1.1.0               | OPS4J Pax JDBC HSQLDB Driver Adapter
	203 | Active |  80 | 1.1.0               | OPS4J Pax JDBC MariaDB Driver Adapter
	204 | Active |  80 | 1.1.0               | OPS4J Pax JDBC Pooling DBCP2
	207 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/Persistence Management Agent
	208 | Active |  80 | 1.0.0.SNAPSHOT      | Broadband Access Abstraction/SBI Connectors
	209 | Active |  80 | 0                   | wrap_file__baa_baa-dist-2.0.0_system_com_google_errorprone_error_prone_annotations_2.1.3_error_prone_annotations-2.1.3.jar
	210 | Active |  80 | 0                   | wrap_file__baa_baa-dist-2.0.0_system_org_checkerframework_checker-compat-qual_2.0.0_checker-compat-qual-2.0.0.jar
	214 | Active |  80 | 0.1.54              | jsch
	215 | Active |  80 | 1.0.0.SNAPSHOT      | Sample adapter for protocol translation
	karaf@root()> kar:list
	KAR Name
	--------------------------------------
	protocol-transl-feature-2.0.0
	karaf@root()> list | grep -v Active
	START LEVEL 100 , List Threshold: 50
	 ID | State   | Lvl | Version             | Name
	-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
	217 | Failure |  80 | 1.0.0.SNAPSHOT      | Sample adapter for protocol translation
	karaf@root()> diag
	Sample adapter for protocol translation (217)
	---------------------------------------------
	Status: Failure
	Blueprint
	2/11/19 12:19 PM
	Exception:
	Unable to find a matching constructor on class org.broadband_forum.obbaa.device.adapter.CodedAdapterServiceImpl for arguments [org.apache.aries.blueprint.container.ReferenceRecipe$ServiceProxyWrapper@1a0b1639, protocol-transl-sample-adapter [217], class org.broadband_forum.obbaa.pma.DeviceXmlStore, org.apache.aries.blueprint.container.BeanRecipe$UnwrapperedBeanHolder@26c17a2d] when instanciating bean codedAdapterServiceImpl
	org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to find a matching constructor on class org.broadband_forum.obbaa.device.adapter.CodedAdapterServiceImpl for arguments [org.apache.aries.blueprint.container.ReferenceRecipe$ServiceProxyWrapper@1a0b1639, protocol-transl-sample-adapter [217], class org.broadband_forum.obbaa.pma.DeviceXmlStore, org.apache.aries.blueprint.container.BeanRecipe$UnwrapperedBeanHolder@26c17a2d] when instanciating bean codedAdapterServiceImpl
	    at org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:354)
	    at org.apache.aries.blueprint.container.BeanRecipe.getInstance(BeanRecipe.java:282)
	    at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:830)
	    at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:811)
	    at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)
	    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	    at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)
	    at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:255)
	    at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:186)
	    at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:712)
	    at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:399)
	    at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:273)
	    at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)
	    at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)
	    at org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)
	    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
	    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
	    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
	    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
	    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
	    at org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)
	    at org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:731)
	    at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:486)
	    at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4541)
	    at org.apache.felix.framework.Felix.startBundle(Felix.java:2172)
	    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
	    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
	    at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1199)
	    at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:840)
	    at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)
	    at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)
	    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	    at java.lang.Thread.run(Thread.java:748)
	2019-02-11 12:24:40,940 | INFO  | f]-nio2-thread-6 | DeviceAdapterActionHandlerImpl   | 207 - pma - 1.0.0.SNAPSHOT | Received request for deploying coded adapter protocol-transl-feature-2.0.0.kar
	2019-02-11 12:24:40,940 | INFO  | f]-nio2-thread-6 | DeviceAdapterActionHandlerImpl   | 207 - pma - 1.0.0.SNAPSHOT | Installing kar
	2019-02-11 12:24:40,949 | INFO  | f]-nio2-thread-6 | KarServiceImpl                   | 149 - org.apache.karaf.kar.core - 4.0.4 | Added feature repository 'mvn:org.bbf.obbaa/protocol-transl-feature/2.0.0/xml/features'
	2019-02-11 12:24:40,950 | INFO  | f]-nio2-thread-6 | FeaturesServiceImpl              | 8 - org.apache.karaf.features.core - 4.0.4 | Adding features: protocol-transl-feature/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
	2019-02-11 12:24:41,442 | WARN  | f]-nio2-thread-6 | KarServiceImpl                   | 149 - org.apache.karaf.kar.core - 4.0.4 | Unable to install Kar feature protocol-transl-feature/1.0.0.SNAPSHOT
	org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=protocol-transl-feature; type=karaf.feature; version="[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]"; filter:="(&(osgi.identity=protocol-transl-feature)(type=karaf.feature)(version>=1.0.0.SNAPSHOT)(version<=1.0.0.SNAPSHOT))" [caused by: Unable to resolve protocol-transl-feature/1.0.0.SNAPSHOT: missing requirement [protocol-transl-feature/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=protocol-transl-sample-adapter; type=osgi.bundle; version="[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve protocol-transl-sample-adapter/1.0.0.SNAPSHOT: missing requirement [protocol-transl-sample-adapter/1.0.0.SNAPSHOT] osgi.wiring.package; filter:="(osgi.wiring.package=com.jcraft.jsch)"]]
		at org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
		at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
		at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
		at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[8:org.apache.karaf.features.core:4.0.4]
		at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[8:org.apache.karaf.features.core:4.0.4]
		at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[8:org.apache.karaf.features.core:4.0.4]
		at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[8:org.apache.karaf.features.core:4.0.4]
		at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_131]
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_131]
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_131]
		at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]
    Request :
	<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
		<get>
			<filter type="subtree">
				<network-manager xmlns="urn:bbf:yang:obbaa:network-manager">
					<device-adapters xmlns="urn:bbf:yang:obbaa:network-manager">
					 <device-adapter>
						 <type/>
						 <interface-version/>
						 <model/>
						 <vendor/>
						 <is-netconf/>
					 </device-adapter>
					</device-adapters>
				</network-manager>
			</filter>
		</get>
	</rpc>

	Sample response: see that along with the standard adapters , the newly deployed coded adapter is also present
	<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
	  <data>
	    <baa-network-manager:network-manager xmlns:baa-network-manager="urn:bbf:yang:obbaa:network-manager">
	      <device-adapters xmlns="urn:bbf:yang:obbaa:network-manager">
	        <device-adapter>
	          <type>DPU</type>
	          <interface-version>1.0</interface-version>
	          <model>standard</model>
	          <vendor>BBF</vendor>
	          <is-netconf>true</is-netconf>
	        </device-adapter>
	        <device-adapter>
	          <type>OLT</type>
	          <interface-version>1.0</interface-version>
	          <model>standard</model>
	          <vendor>BBF</vendor>
	          <is-netconf>true</is-netconf>
	        </device-adapter>
	        <device-adapter>
	          <type>DPU</type>
	          <interface-version>1.0</interface-version>
	          <model>protocol-tls</model>
	          <vendor>sample</vendor>
	          <is-netconf>false</is-netconf>
	        </device-adapter>
	      </device-adapters>
	    </baa-network-manager:network-manager>
	  </data>
	</rpc-reply>

Undeploying a VDA

Do a get on the device adapters and check the the VDA is undeployed:

Request :
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
	<get>
		<filter type="subtree">
			<network-manager xmlns="urn:bbf:yang:obbaa:network-manager">
				<device-adapters xmlns="urn:bbf:yang:obbaa:network-manager">
				 <device-adapter>
					 <type/>
					 <interface-version/>
					 <model/>
					 <vendor/>
					 <is-netconf/>
				 </device-adapter>
				</device-adapters>
			</network-manager>
		</filter>
	</get>
</rpc>


Sample get response after undeployment of coded adapter:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <data>
    <baa-network-manager:network-manager xmlns:baa-network-manager="urn:bbf:yang:obbaa:network-manager">
      <device-adapters xmlns="urn:bbf:yang:obbaa:network-manager">
        <device-adapter>
          <type>DPU</type>
          <interface-version>1.0</interface-version>
          <model>standard</model>
          <vendor>BBF</vendor>
          <is-netconf>true</is-netconf>
        </device-adapter>
        <device-adapter>
          <type>OLT</type>
          <interface-version>1.0</interface-version>
          <model>standard</model>
          <vendor>BBF</vendor>
          <is-netconf>true</is-netconf>
        </device-adapter>
      </device-adapters>
    </baa-network-manager:network-manager>
  </data>
</rpc-reply>

<–Using OB-BAA