blob: fd2ccbeebadd265a11374d31431fffa139f90497 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
============LICENSE_START=======================================================
openECOMP : SDN-C
================================================================================
Copyright (C) 2017 AT&T Intellectual Property. All rights
reserved.
================================================================================
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
============LICENSE_END=========================================================
-->
<!-- 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:openecomp:sdnc:sliapi:provider:impl">
prefix:sliapi-provider-impl
</type>
<name>sliapi-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">
binding:binding-notification-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:openecomp:sdnc:sliapi:provider:impl?module=sliapi-provider-impl&revision=2014-05-23</capability>
</required-capabilities>
</snapshot>
|
