summaryrefslogtreecommitdiffstats
path: root/v3po/Readme.adoc
diff options
context:
space:
mode:
authorMaros Marsalek <mmarsale@cisco.com>2016-07-27 11:05:51 +0200
committerMaros Marsalek <mmarsale@cisco.com>2016-07-29 16:32:07 +0200
commit0578156b721fa01c8c645b8f9625ecebdb6449e4 (patch)
tree49d36f24e5d984a8c9f151b1440de88619f8b7de /v3po/Readme.adoc
parent007d4542388ca89be409ce1a4a4c7a36ddcb538f (diff)
HONEYCOMB-130: Separate v3po plugin from HC infra
Creating folders: - common/ - infra/ - v3po/ - vpp-common/ Change-Id: I2c39e1b17e39e7c0f0628f44aa5fe08563fa06e4 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
Diffstat (limited to 'v3po/Readme.adoc')
-rw-r--r--v3po/Readme.adoc67
1 files changed, 0 insertions, 67 deletions
diff --git a/v3po/Readme.adoc b/v3po/Readme.adoc
deleted file mode 100644
index 33e882f8c..000000000
--- a/v3po/Readme.adoc
+++ /dev/null
@@ -1,67 +0,0 @@
-= Honeycomb
-
-Honeycomb is an VPP agent that runs the same host as a VPP instance
-and exposes YANG models via NETCONF and RESTCONF to allow management of that VPP instance.
-Honeycomb uses jAPI to communicate with the VPP.
-
-[ditaa, "hc-architecture"]
-....
- /------------------\
- ODL | RESTCONF/NETCONF |
- \-+--------------+-/
- | ^
----------------------|--------------|---------------------
- v |
- /------------------\
- | Data layer |
- \-+--------------+-/
- | ^
- Honeycomb v |
- /-----+--------------+-----\
- | Translation layer |
- \----+----------------+----+
- | VPP SPI impl |
- +---+------+-----+
- | ^
-------------------------|------|--------------------------
- v |
- ++------++
- | jAPI |
- VPP /----+--------+------\
- | VPP |
- \--------------------/
-
-....
-
-== NETCONF/RESTCONF layer
-
-NETCONF and RESTCONF support is provided by ODL (Honeycomb is an ODL application).
-In the future we plan to minimize ODL dependencies or completely remove karaf.
-
-Transaction functionality is provided by the data layer.
-
-== Data layer
-
-Models CONFIG data store as a DataTree.
-
-OPERATIONAL data store reads are passed directly to the translation layer.
-
-Provides transaction functionality for NETCONF/RESTCONF layer.
-
-
-== Translation layer
-
-Extensible API for translation between Binding Aware data and actual device data.
-Consists of readers and writers responsible for communication with the device.
-
-Provides registry of readers and writers for the data layer.
-
-== Supported features
-
-List of supported requests for RESTCONF northbound interface can be found in
-postman_rest_collection.json within the codebase.
-It is a POSTMAN compatible collection and can be imported into POSTMAN application.
-
-
-
-