tag | 5dae9596ee172c2d4532e2fb504b3db889df60eb | |
---|---|---|
tagger | Jenkins <do-not-reply@opennetworking.org> | Tue Feb 23 17:46:49 2021 +0000 |
object | 2c046fa1fae020b98ed929e997fe6c16cb262c92 |
Tagged by CORD Jenkins version-tag job: 6158, for Gerrit patchset: 23003
commit | 2c046fa1fae020b98ed929e997fe6c16cb262c92 | [log] [tgz] |
---|---|---|
author | Chip Boling <chipboling@gmail.com> | Tue Feb 23 11:30:29 2021 -0600 |
committer | Chip Boling <chipboling@gmail.com> | Tue Feb 23 11:30:29 2021 -0600 |
tree | a650d8171f737407e239cc661e61df8fe2391445 | |
parent | 8c8018efe056238d86d12ff545578834bad05c05 [diff] |
VOL-3864: recently added generated ME Class IDs did not get added to Class ID map Change-Id: I7ce97b28e928bd8b716cdc3532c0da8a5627118d
OMCI gopacket library supports the encoding and decoding of ITU G.988 OMCI messages.
The following OMCI message types currently have been coded and are covered satisfactory by unit tests.
The following OMCI message types currently have been coded and are partially covered by unit tests, but work still remains for sufficient/better unit test coverage.
The following OMCI message types currently have been coded but do not have any unit test coverage.
The following OMCI message types currently have not been coded.
The coverage.sh and coverage.cmd scripts can be used to create code coverage support for the library. The current coverage (as of 2/11/2020) is:
File | Statement Coverage |
---|---|
layers.go | 100% |
mebase.go | 87.5% |
meframe.go | 54.8% |
messagetypes.go | 48.1% |
omci.go | 81.6% |
Besides OMCI Message decode/serialization, and associated unit tests, the following items would be needed or useful in a first official release of this library. Some changes are to be done in the generated OMCI ME code as well.
The following would be 'nice' to have but are not necessary for initial code release
Also searching through the code for TODO statements will also yeild additional areas of work to be performed.
This library is not a full OMCI stack for either an OLT or an ONU. It is focused primarily on packet decode/serialization and a variety of structs and functions that are useful for handling the creation of OMCI frames and handling decoded frames from the PON.
For an OLT-side OMCI stack, you would still need to write:
For an ONU-side OMCI stack, you would still need to write: