User Tools

Site Tools


lsoapi:documents:architecture

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
lsoapi:documents:architecture [2015/08/28 17:44]
Steven Saunders
lsoapi:documents:architecture [2015/09/11 21:00] (current)
Kevin Luehrs
Line 89: Line 89:
 The contents of the __<​xxxmgr>​__ directory in general is structured as follows: The contents of the __<​xxxmgr>​__ directory in general is structured as follows:
  
-  ​evcmgr/​src/​main/​java/​com/​cablelabs/​vcpe/​xxx/​xxxmgr/​*.java ... contains code for serving xxx rest requests+  ​xxxmgr/​src/​main/​java/​com/​cablelabs/​vcpe/​xxx/​xxxmgr/​*.java ... contains code for serving xxx rest requests 
 +   
 +== UNI manager emulator == 
 + 
 +The one exception the the directory structures defined above is <​unimgr>​ directory. ​ The lsoapi service layers do NOT include a UNI service layer (i.e. UNI manager), but rather, the UNI Manager will be contained within OpenDaylight. 
 + 
 +However, the lsoapi code base does provide a nodejs UNI Manager Emulator, which can receive and process all REST messages defined by the ODL UNI Manager northbound interface. ​ The emulator can be useful if you do not have OpenDaylight installed on you development machine, but you would like to test the UNI Northbound REST API messaging. 
 + 
 +Specifically,​ the <​evcmgr>​ code consumes the ODL Uni manager northbound REST interface (i.e. it makes NETCONF REST calls to OpenDaylight,​ which can be alternately served by the emulator). 
 + 
 +The details for configuring and running the emulator can be found in the lsoapi/​README.md file 
 + 
 +Return to [[https://​wiki.opnfv.org/​lsoapi| main project page]] 
 +  ​
lsoapi/documents/architecture.1440783868.txt.gz · Last modified: 2015/08/28 17:44 by Steven Saunders