OVSDB Project

Major Features

odl-ovsdb-southbound-api

odl-ovsdb-southbound-impl

odl-ovsdb-southbound-impl-rest

odl-ovsdb-hwvtepsouthbound-api

odl-ovsdb-hwvtepsouthbound

odl-ovsdb-hwvtepsouthbound-rest

  • Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/features/src/main/features/features.xml
  • Feature Description: This feature is the wrapper feature that installs the odl-ovsdb-hwvtepsouthbound-api & odl-ovsdb-hwvtepsouthbound feature with other required features for restconf access to provide a functional OVSDB Hardware vTEP plugin. Users, who want to develop application that manages the hardware vTEP supported devices but want to runs the application outside of the OpenDaylight controller must install this feature.
  • Top Level: Yes
  • User Facing: Yes
  • Experimental: Yes
  • CSIT Test: Currently no CSIT Tests are available, but work is in progress and will be available by nitrogen release.

Documentation

Security Considerations

  • Do you have any external interfaces other than RESTCONF? Yes, Southbound Connection to OVSDB/Hardware vTEP devices.

  • Other security issues?

    Plugin’s connection to device is by default unsecured. User need to explicitly enable the TLS support through ovsdb library configuration file. User can refer to the wiki page here for the instructions.

Quality Assurance

Migration

  • Is is possible migrate from the previous release? If so, how? Yes. User facing features and interfaces are not changed, only enhancements are done.

Compatibility

  • Is this release compatible with the previous release? No
  • Any API changes? No changes in the YANG models from previous release. Only one minor enhancement is being done. https://git.opendaylight.org/gerrit/#/c/50993/
  • Any configuration changes? No

Known Issues

End-of-life

  • List of features/APIs which are EOLed, deprecated, and/or removed in thisrelease

    None

Release Mechanics

  • Link to release plan

  • Describe any major shifts in release schedule from the release plan

    We planned to do some exploratory work to improve the performance, scalability and robustness, but it didn’t make the expected progress in this release. Project will continue this effort in the next release.