Roll to Istanbul release version

Roll master to Istanbul release version

Change-Id: I8f87f404d6e8f44ad7cb4abb60b7335c4caad84e
Issue-ID: SDNC-1495
Signed-off-by: Dan Timoney <dtimoney@att.com>

1 files changed, 0 insertions, 35 deletions

diff --git a/vnfapi/README.txt b/vnfapi/README.txt
deleted file mode 100644
index f9f4a2ab..00000000
--- a/vnfapi/README.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-======================
-Introduction
-======================
-You have generated an MD-SAL module using the Brocade Archetype. 
-
-* You should be able to successfully run 'mvn clean install' on this project.
-* This will produce a .zip file under the karaf.extension directory which you can deploy using
-Brocade's extension deployment mechanism.
-
-======================
-Next Steps:
-======================
-* run a 'mvn clean install' if you haven't already. This will generate some code from the yang models.
-* Modify the model yang file under the model project.
-* Follow the comments in the generated provider class to wire your new provider into the generated 
-code.
-* Modify the generated provider model to respond to and handle the yang model. Depending on what
-you added to your model you may need to inherit additional interfaces or make other changes to
-the provider model.
-
-======================
-Generated Bundles:
-======================
-* model
-    - Provides the yang model for your application. This is your primary northbound interface.
-* provider
-    - Provides a template implementation for a provider to respond to your yang model.
-* features
-    - Defines a karaf feature. If you add dependencies on third-party bundles then you will need to
-      modify the features.xml to list out the dependencies.
-* karaf.extension
-    - Bundles all of the jars and third party dependencies (minus ODL dependencies) into a single
-      .zip file with the necessary configuration files to work correctly with the Brocade extension
-      mechanism.
-