diff options
author | 2017-10-13 12:07:01 -0400 | |
---|---|---|
committer | 2017-10-13 12:07:01 -0400 | |
commit | 03575373024593fd1cac6812f0992152edde4d37 (patch) | |
tree | 689a8dadbfa42740e2b160d7584df423705ced9b /generic-resource-api/provider/src/main/resources/initial | |
parent | dd3f74074787dfd14e8aec0b48883b780dd8ccba (diff) |
Fix installation issues with generic-resource-api
Updated generic-resource-api to use Aries blueprint to install and
resolved issues preventing it from installing properly in karaf.
Change-Id: Iaef8bdb7a9e6aaf149a8e8a0d847197cf3f704a9
Issue-ID: SDNC-109
Signed-off-by: Dan Timoney <dtimoney@att.com>
Diffstat (limited to 'generic-resource-api/provider/src/main/resources/initial')
-rw-r--r-- | generic-resource-api/provider/src/main/resources/initial/generic-resource-api-provider.xml | 51 |
1 files changed, 0 insertions, 51 deletions
diff --git a/generic-resource-api/provider/src/main/resources/initial/generic-resource-api-provider.xml b/generic-resource-api/provider/src/main/resources/initial/generic-resource-api-provider.xml deleted file mode 100644 index a9d3e639..00000000 --- a/generic-resource-api/provider/src/main/resources/initial/generic-resource-api-provider.xml +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!-- vi: set et smarttab sw=4 tabstop=4: --> -<snapshot> - <configuration> - <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> - <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"> - <module> - - <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang file - The prefix: inside type should match the prefix of the yang file. --> - <type xmlns:prefix="org:onap:sdnc:northbound:GENERIC-RESOURCE-API:provider:impl"> - prefix:GENERIC-RESOURCE-API-provider-impl - </type> - <name>GENERIC-RESOURCE-API-provider-impl</name> - - <!-- The following sections contain bindings to services defined in the - *-provider-impl yang file. For example the rpc-registry is required - because we have a dependency (or augmentation) named "rpc-registry" - and which binds to the md-sa-binding-registry. If you remove those - dependencies from the yang file then you can remove them from here. --> - <rpc-registry> - <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type> - <name>binding-rpc-broker</name> - </rpc-registry> - - <data-broker> - <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type> - <name>binding-data-broker</name> - </data-broker> - - <notification-service> - <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl"> - binding:binding-new-notification-publish-service - </type> - <name>binding-notification-broker</name> - </notification-service> - </module> - - </modules> - </data> - - </configuration> - - <!-- Required capabilities are basically a listing of all modules that need to be imported before - our service can be resolved. Capabilities for dependencies defined above are implied which is - why we do not have define a required capability for the data broker, for example. --> - <required-capabilities> - <capability>org:onap:sdnc:northbound:GENERIC-RESOURCE-API:provider:impl?module=GENERIC-RESOURCE-API-provider-impl&revision=2017-08-24</capability> - </required-capabilities> - -</snapshot> |