This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
lsoapi:documents:architecture [2015/08/28 17:51] Steven Saunders |
lsoapi:documents:architecture [2015/09/11 21:00] (current) Kevin Luehrs |
||
---|---|---|---|
Line 93: | Line 93: | ||
== UNI manager emulator == | == 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 is contained within OpenDaylight. | + | 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 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 open daylight installed in you development machine, but you would like to test the UNI Northbound REST messaging APIs. | + | 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 | 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]] | ||
| |