Contents
[hide]
- 1 Project Name
- 2 Features
- 3 Non-Code Aspects (user docs, examples, tutorials, articles)
- 4 Architectural Issues
- 5 Security Considerations
- 6 Quality Assurance (test coverage, etc)
- 7 End-of-life (API/Features EOLed in Release)
- 8 Bugzilla (summary of bug situation)
- 9 Standards (summary of standard compliance)
- 10 Schedule (initial schedule and changes over the release cycle)
Table of Contents maxLevel 3 include .* exclude Contents
Project Name
Open vSwitch Database Integration Project
...
- Sonar: UT: 29.8%, IT:16.3%
- The UT coverage is actually better since 30% of the missing UT is from deprecated ADSAL components. The larger openstack OpenStack component is probably 80% covered along with the library at 50% coverage. The southbound has barely any UT coverage.
- The IT coverage is actually better also for the same reason as 30% of the code is deprecated ADSAL components. Also, the majority of the southbound and openstack OpenStack code is MDSAL-based which the Sonar IT inspection does not handle well. The majority of the code paths in the southbound are covered by IT and 50% of the code paths in openstack OpenStack are covered.
- System The system test is covered mainly via the OpenStack upstream which runs tempest tests against the latest OpenDaylight Lithium release.
- There are limited southbound and openstack OpenStack integration tests within the integration CSIT.
...
- library: 2 bugs on scaling
- openstackOpenStack: 2 bugs for new features, 3 for updates to l3 and 3 for updates to LBaaS
- southbound: 2 bugs
- deprecated code: 22 bugs from helium, most likely to be marked as resolved, wont won't fix
Standards (summary of standard compliance)
...
Code hardening was a primary driver for this release but the introduction of the MDSAL to OVSDB impacted that deliverable as resources were diverted to the new MDSAL southbound. Also, the instability of a reliable OpenStack and ODL integration test framework impacted testing coverage.
...