#opendaylight-meeting: UNI Manager

Meeting summary

1. Using the OVS QoS 'MaxRate' parameter to implement UNI Speed attribute (KLuehrs, 21:04:07)
   1. Mohamed spoke with OVSDB project lead. They will push a new patch that enables changing data rate via OVSDB (KLuehrs, 21:05:43)
   2. Mohamed thinks OVSDB project will push that patch next week - week of January 18-22 (KLuehrs, 21:07:11)
   3. The current UNI Manager plug in implementation supports the ability to update ingress and egress speed (KLuehrs, 21:08:30)
   4. Mohamed will add documentation for APIs to update Egress and Ingress speed (KLuehrs, 21:09:39)
   5. Northbound API implementation - LSOAPI EVC Manager - will need to be updated to make correct calls to update speed (KLuehrs, 21:10:13)
   6. EVC Manager will need to call both Update Egress Speed and Update Ingress Speed (KLuehrs, 21:11:16)
   7. Does UNI Manager listener code need to be updated to provide the correct OVSBD Update Speed commands? Yes. (KLuehrs, 21:12:40)
   8. Suggest: request OVSDB project for patch code for MaxRate even before the code freeze, so we can implement the feature as soon as possible (KLuehrs, 21:15:32)
   9. Our understanding is current OVSDB YANG model does not have MaxRate (KLuehrs, 21:18:03)
   
   
2. UNI Manager unit test development for Beryllium release (KLuehrs, 21:20:24)
   1. Mufaddal contacted Gabriel to ask about UNI Manager (KLuehrs, 21:20:56)
   2. Mohamed said Gabriel pushed a UNI Manager patch with unit tests. We don't know which classes he added unit tests for. Mufaddal is available to help with unit tests. (KLuehrs, 21:21:55)
   3. Inocybe is also working on Integration tests for UNI Manager (KLuehrs, 21:22:47)
   
   
3. UNI Manager Demo (KLuehrs, 21:27:20)
   1. Mufaddal shared via Zoom web conference screen sharing the work he has done to show markers on a map where UNIs can be created (KLuehrs, 21:28:06)

Action items

1. (none)

People present (lines said)

1. KLuehrs (19)
2. odl_meetbot (4)