summaryrefslogtreecommitdiffstats
path: root/appc-provider/appc-provider-bundle/src/main/resources/initial
diff options
context:
space:
mode:
Diffstat (limited to 'appc-provider/appc-provider-bundle/src/main/resources/initial')
-rw-r--r--appc-provider/appc-provider-bundle/src/main/resources/initial/appc-provider.xml120
1 files changed, 0 insertions, 120 deletions
diff --git a/appc-provider/appc-provider-bundle/src/main/resources/initial/appc-provider.xml b/appc-provider/appc-provider-bundle/src/main/resources/initial/appc-provider.xml
deleted file mode 100644
index b7de48c5a..000000000
--- a/appc-provider/appc-provider-bundle/src/main/resources/initial/appc-provider.xml
+++ /dev/null
@@ -1,120 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- ============LICENSE_START=======================================================
- ONAP : APPC
- ================================================================================
- Copyright (C) 2017-2018 AT&T Intellectual Property. All rights reserved.
- ================================================================================
- Copyright (C) 2017 Amdocs
- =============================================================================
- 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:onap:appc:provider:impl">
- prefix:appc-provider-impl
- </type>
- <name>appc-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>
-
- <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:appc:provider:lcm:impl">
- prefix:appc-provider-lcm-impl
- </type>
- <name>appc-provider-lcm-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>appc:training:sample:provider:impl?module=sample-provider-impl&amp;revision=2014-05-23</capability> -->
- <!-- </required-capabilities> -->
- <required-capabilities>
- <capability>org:onap:appc:provider:impl?module=appc-provider-impl&amp;revision=2014-05-23
- </capability>
- <capability>org:onap:appc:provider:lcm:impl?module=appc-provider-lcm-impl&amp;revision=2016-01-08
- </capability>
- </required-capabilities>
-
-</snapshot>