appc-provider/appc-provider-bundle/src/main/resources/initial/appc-provider.xml

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <!--
   3   ============LICENSE_START=======================================================
   4   ONAP : APPC
   5   ================================================================================
   6   Copyright (C) 2017 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
  13
  14        http://www.apache.org/licenses/LICENSE-2.0
  15
  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.
  21
  22   ECOMP is a trademark and service mark of AT&T Intellectual Property.
  23   ============LICENSE_END=========================================================
  24   -->
  25
  26 <!-- vi: set et smarttab sw=4 tabstop=4: -->
  27 <snapshot>
  28         <configuration>
  29                 <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  30                         <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
  31                                 <module>
  32
  33                                         <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang
  34                                                 file The prefix: inside type should match the prefix of the yang file. -->
  35                                         <type xmlns:prefix="org:onap:appc:provider:impl">
  36                                                 prefix:appc-provider-impl
  37                                         </type>
  38                                         <name>appc-provider-impl</name>
  39
  40                                         <!-- The following sections contain bindings to services defined in
  41                                                 the *-provider-impl yang file. For example the rpc-registry is required because
  42                                                 we have a dependency (or augmentation) named "rpc-registry" and which binds
  43                                                 to the md-sa-binding-registry. If you remove those dependencies from the
  44                                                 yang file then you can remove them from here. -->
  45                                         <rpc-registry>
  46                                                 <type
  47                                                         xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
  48                                                 <name>binding-rpc-broker</name>
  49                                         </rpc-registry>
  50
  51                                         <data-broker>
  52                                                 <type
  53                                                         xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
  54                                                 <name>binding-data-broker</name>
  55                                         </data-broker>
  56
  57                                         <notification-service>
  58                                                 <type
  59                                                         xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">
  60                                                         binding:binding-notification-service
  61                                                 </type>
  62                                                 <name>binding-notification-broker</name>
  63                                         </notification-service>
  64                                 </module>
  65
  66                                 <module>
  67
  68                                         <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang
  69                                                 file The prefix: inside type should match the prefix of the yang file. -->
  70                                         <type xmlns:prefix="org:onap:appc:provider:lcm:impl">
  71                                                 prefix:appc-provider-lcm-impl
  72                                         </type>
  73                                         <name>appc-provider-lcm-impl</name>
  74
  75                                         <!-- The following sections contain bindings to services defined in
  76                                                 the *-provider-impl yang file. For example the rpc-registry is required because
  77                                                 we have a dependency (or augmentation) named "rpc-registry" and which binds
  78                                                 to the md-sa-binding-registry. If you remove those dependencies from the
  79                                                 yang file then you can remove them from here. -->
  80                                         <rpc-registry>
  81                                                 <type
  82                                                                 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
  83                                                 <name>binding-rpc-broker</name>
  84                                         </rpc-registry>
  85
  86                                         <data-broker>
  87                                                 <type
  88                                                                 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
  89                                                 <name>binding-data-broker</name>
  90                                         </data-broker>
  91
  92                                         <notification-service>
  93                                                 <type
  94                                                                 xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">
  95                                                         binding:binding-notification-service
  96                                                 </type>
  97                                                 <name>binding-notification-broker</name>
  98                                         </notification-service>
  99                                 </module>
 100
 101
 102                         </modules>
 103                 </data>
 104
 105         </configuration>
 106
 107         <!-- Required capabilities are basically a listing of all modules that need
 108                 to be imported before our service can be resolved. Capabilities for dependencies
 109                 defined above are implied which is why we do not have define a required capability
 110                 for the data broker, for example. -->
 111         <!-- <required-capabilities> -->
 112         <!-- <capability>appc:training:sample:provider:impl?module=sample-provider-impl&amp;revision=2014-05-23</capability> -->
 113         <!-- </required-capabilities> -->
 114         <required-capabilities>
 115                 <capability>org:onap:appc:provider:impl?module=appc-provider-impl&amp;revision=2014-05-23
 116                 </capability>
 117                 <capability>org:onap:appc:provider:lcm:impl?module=appc-provider-lcm-impl&amp;revision=2016-01-08
 118                 </capability>
 119         </required-capabilities>
 120
 121 </snapshot>