@@ -97,13 +97,23 @@ Following are some of the management operations supported:
97
97
- Currently committing configurations from Candidate to Running database
98
98
is only allowed, and not vice versa.
99
99
100
+ Front-End Native Protobuf API
101
+ """""""""""""""""""""""""""""
100
102
The exact set of message-based APIs are represented as Google Protobuf
101
103
messages and can be found in the following file distributed with FRR codebase.
102
104
103
105
.. code-block :: frr
104
106
105
107
lib/mgmt.proto
106
108
109
+ Front-End Native (non-protobuf) API
110
+ """""""""""""""""""""""""""""""""""
111
+ Additionally there exists a "native" API that does not utilize ``protobuf``s
112
+ this native API and the front-end messages and structures it supports are
113
+ documented in the header file ``lib/mgmt_msg_native.h ``.
114
+
115
+ Connecting to MGMTd
116
+ """""""""""""""""""
107
117
The MGMT daemon implements a MGMT Frontend Server that opens a UNIX
108
118
socket-based IPC channel on the following path to listen for incoming
109
119
connections from all possible Frontend clients:
@@ -124,7 +134,9 @@ specification of this library can be found at:
124
134
125
135
lib/mgmt_fe_client.h
126
136
127
- Following is a list of message types supported on the MGMT Frontend Interface:
137
+ Following is a list of protobuf message types supported on the MGMT Frontend
138
+ Interface:
139
+
128
140
- SESSION_REQ<Client-Connection-Id, Destroy>
129
141
- SESSION_REPLY<Client-Connection-Id, Destroy, Session-Id>
130
142
- LOCK_DB_REQ <Session-Id, Database-Id>
@@ -139,8 +151,21 @@ Following is a list of message types supported on the MGMT Frontend Interface:
139
151
- COMMIT_CONFIG_REPLY <Session-Id, Source-Db-id, Dest-Db-Id, Status>
140
152
- GET_DATA_REQ <Session-Id, Database-Id, Base-Yang-Xpath>
141
153
- GET_DATA_REPLY <Session-Id, Database-id, Base-Yang-Xpath, Yang-Data-Set>
142
- - REGISTER_NOTIFY_REQ <Session-Id, Database-Id, Base-Yang-Xpath>
143
- - DATA_NOTIFY_REQ <Database-Id, Base-Yang-Xpath, Yang-Data-Set>
154
+
155
+ Following is a list of native messages types supported by the MGMTd Front-End
156
+ API:
157
+
158
+ - ERROR (receive) - received in response to any sent native message.
159
+ - TREE_DATA (receive) - returned data from a datastore
160
+ - GET_DATA (send) - get a tree of data
161
+ - NOTIFY (receive) - a notification received from mgmtd
162
+ - EDIT (send) - edit configuration datastore
163
+ - EDIT_REPLY (receive) - reply for an edit operation
164
+ - RPC (send) - sending (invoking) an RPC.
165
+ - RPC_REPLY (receive) - reply from invoking an RPC
166
+ - NOTIFY_SELECT (send) - specify the sub-set of notifications the front-end
167
+ wishes to receive, rather than the default of receiving all.
168
+
144
169
145
170
Please refer to the MGMT Frontend Client Developers Reference and Guide
146
171
(coming soon) for more details.
0 commit comments