1 <?xml version="1.0" encoding="UTF-8"?>
3 ============LICENSE_START=======================================================
5 ================================================================================
6 Copyright (C) 2017-2018 AT&T Intellectual Property. All rights reserved.
7 ================================================================================
8 Copyright (C) 2017 Amdocs
9 =============================================================================
10 Licensed under the Apache License, Version 2.0 (the "License");
11 you may not use this file except in compliance with the License.
12 You may obtain a copy of the License at
14 http://www.apache.org/licenses/LICENSE-2.0
16 Unless required by applicable law or agreed to in writing, software
17 distributed under the License is distributed on an "AS IS" BASIS,
18 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
19 See the License for the specific language governing permissions and
20 limitations under the License.
22 ============LICENSE_END=========================================================
25 <!-- vi: set et smarttab sw=4 tabstop=4: -->
28 <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
29 <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
32 <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang
33 file The prefix: inside type should match the prefix of the yang file. -->
34 <type xmlns:prefix="org:onap:appc:provider:impl">
35 prefix:appc-provider-impl
37 <name>appc-provider-impl</name>
39 <!-- The following sections contain bindings to services defined in
40 the *-provider-impl yang file. For example the rpc-registry is required because
41 we have a dependency (or augmentation) named "rpc-registry" and which binds
42 to the md-sa-binding-registry. If you remove those dependencies from the
43 yang file then you can remove them from here. -->
46 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
47 <name>binding-rpc-broker</name>
52 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
53 <name>binding-data-broker</name>
56 <notification-service>
58 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">
59 binding:binding-notification-service
61 <name>binding-notification-broker</name>
62 </notification-service>
67 <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang
68 file The prefix: inside type should match the prefix of the yang file. -->
69 <type xmlns:prefix="org:onap:appc:provider:lcm:impl">
70 prefix:appc-provider-lcm-impl
72 <name>appc-provider-lcm-impl</name>
74 <!-- The following sections contain bindings to services defined in
75 the *-provider-impl yang file. For example the rpc-registry is required because
76 we have a dependency (or augmentation) named "rpc-registry" and which binds
77 to the md-sa-binding-registry. If you remove those dependencies from the
78 yang file then you can remove them from here. -->
81 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
82 <name>binding-rpc-broker</name>
87 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
88 <name>binding-data-broker</name>
91 <notification-service>
93 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">
94 binding:binding-notification-service
96 <name>binding-notification-broker</name>
97 </notification-service>
106 <!-- Required capabilities are basically a listing of all modules that need
107 to be imported before our service can be resolved. Capabilities for dependencies
108 defined above are implied which is why we do not have define a required capability
109 for the data broker, for example. -->
110 <!-- <required-capabilities> -->
111 <!-- <capability>appc:training:sample:provider:impl?module=sample-provider-impl&revision=2014-05-23</capability> -->
112 <!-- </required-capabilities> -->
113 <required-capabilities>
114 <capability>org:onap:appc:provider:impl?module=appc-provider-impl&revision=2014-05-23
116 <capability>org:onap:appc:provider:lcm:impl?module=appc-provider-lcm-impl&revision=2016-01-08
118 </required-capabilities>