1 <?xml version="1.0" encoding="UTF-8"?>
2 <!-- vi: set et smarttab sw=4 tabstop=4: -->
5 <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
6 <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
9 <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang file
10 The prefix: inside type should match the prefix of the yang file. -->
11 <type xmlns:prefix="org:onap:sdnc:northbound:GENERIC-RESOURCE-API:provider:impl">
12 prefix:GENERIC-RESOURCE-API-provider-impl
14 <name>GENERIC-RESOURCE-API-provider-impl</name>
16 <!-- The following sections contain bindings to services defined in the
17 *-provider-impl yang file. For example the rpc-registry is required
18 because we have a dependency (or augmentation) named "rpc-registry"
19 and which binds to the md-sa-binding-registry. If you remove those
20 dependencies from the yang file then you can remove them from here. -->
22 <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
23 <name>binding-rpc-broker</name>
27 <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
28 <name>binding-data-broker</name>
31 <notification-service>
32 <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">
33 binding:binding-notification-service
35 <name>binding-notification-broker</name>
36 </notification-service>
44 <!-- Required capabilities are basically a listing of all modules that need to be imported before
45 our service can be resolved. Capabilities for dependencies defined above are implied which is
46 why we do not have define a required capability for the data broker, for example. -->
47 <required-capabilities>
48 <capability>org:onap:sdnc:northbound:GENERIC-RESOURCE-API:provider:impl?module=GENERIC-RESOURCE-API-provider-impl&revision=2014-05-23</capability>
49 </required-capabilities>