blob: 33e882f8c164b3a92ce71de8fc357c744bd525f6 (
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
|
= 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.
|
