1. Click to edit Master subtitle style
DriverManager Design
Click to edit Master subtitle style

2. DriverMgr Schematic Diagram
SDN-O/NFV-O
SendPost ("snc-1", "/openoapi/sbi-l3vpn/v1/l3vpns", data) 1
DriverMgr
DriverMgr register
MicroserviceBus 3 2 4
Plugin
Query sys type 7 6
Query usable drivers
Deliver messages to drivers 5 8
Driver register
ExternalSys Reg
Driver 9
register
vCloud/vCenter/SNC

3. SDNO/NFVO URI URI Pattern:
/openoapi/{sbiServiceName}/{version}/{resource-path}
Header:” X-Driver-Parameter:extSysID={extsys_id}”
Methods: POST / PUT / DELETE / GET / PATCH
Parameter
Description
Located in
sbiServiceName
SBI Service name, the name is not fixed and bases on the particular service.
URI
version
Version number. V1 indicates the first version.
extSysID
The ID of external system. For example:controller ID
Header|Query
resource-path
service URL needed be upper layer business.
path
URI Example:
/openoapi/sbi-l3vpn/v1/2.0/vpn/l3vpn/...
Note that in this URI, sbiServiceName = sbi-l3vpn; service_url = 2.0/vpn/l3vpn
URI Introduction:
{sbiServiceName} is not fixed, which bases on the particular service. The {extSysType} and {extSysID} are stored in the Header and they are not mandatory,the upper layer business can provide only one of these two parameters. {resource-path} is only used to represent the service-url.

4. DriverMgr Provides Interfaces
Interface Description
URI
Operation Type
URI Parameter
Query Parameter
Return Value
Driver Register
/openoapi/drivermgr/v1/drivers
POST
Status code
Driver Unregister
/openoapi/drivermgr/v1/drivers/{instanceid}
DELETE
instanceid:
Instance ID
Exact Query Driver
/openoapi/drivermgr/v1/drivers? X-Driver-Parameter={parameterstring}&service_url={service_url}
GET
X-Driver-Parameter: extSysID stored in Header
service_url: service URL supported by a driver
See details below.
Batch Query Driver
About the plug-in
The bus transparently transmits an upper-layer business to the plug-in. Upon receipt of the request, the plug-in parses it, invokes the DriverMgr query interface to obtain a target URL, parses DriverMgr response information, and returns target URL information to the bus. Compared with the request URL, the target URL only need to modify the “ parts of the service_url. The plug-in is provided by Huawei, and the plug-in mechanism is provided by ZTE.
information returned to plug-in by the Exact Query Driver interface:
A URL String is returned. The URL is in the format of + {service_url}
For example:
Information returned by the Batch Query Driver interface:
The JSON body array is returned to the driver. For details, see wiki.
Register and Unregister interface return values:
A status code is returned by default. For details, see wiki.

5. JSON Pattern of Driver Body{
"driverInfo": {
"driverName": "vnfm-1",
"instanceID": "vnfm-0-1",//release1: Each service constructs an instance ID by itself. DriverMgr checks whether the value is unique. If the value is duplicate, registration fails.
release2: It is automatically generated by the API. It is reserved for multi-instance.
"ip": " ",
"port": "23456",
"protocol": "http",
"services": [
"service_url":"/openoapi/sbi-l3vpn/v1",
"support_sys":[
{ "type":"Agile Controller-DCN",
"version":"V100R002" },
"version":"V100R003" } ] },
"service_url":"/openoapi/sbi-l2vpn/v1",
{ "type":"Agile Controller-DCN",
"version":"V100R003--Maybe reg pattern supported here in future” } }
In release 1, only involve the driver and the controller one to one scenarios,other Multi-instance scenarios are not involved.

6. WIKI Web Site Driver Manager API Documentation:
Driver Manager Release Plan:
Driver Manager Release Functionalities:

7. Thank You 谢谢！ www.open-o.org For more details on OPEN-O: Marc Cohn