tag | 6f436bd0e06f1895ba62cb078b015dfcd37d2f4d | |
---|---|---|
tagger | Jenkins <do-not-reply@opencord.org> | Fri Feb 21 17:52:25 2020 +0000 |
object | 6e27b35a7a6d05eb1ae8893539e83fe52d29cb99 |
Tagged by CORD Jenkins version-tag job: 3878, for Gerrit patchset: 17575
commit | 6e27b35a7a6d05eb1ae8893539e83fe52d29cb99 | [log] [tgz] |
---|---|---|
author | Chip Boling <chipboling@gmail.com> | Fri Feb 14 09:10:01 2020 -0600 |
committer | Chip Boling <chipboling@gmail.com> | Tue Feb 18 17:29:39 2020 +0000 |
tree | 771f52a9676544247a2c1300cc445fe22f9acfd4 | |
parent | 410183e2ddeb70ec6be268661ec6718b46474143 [diff] |
Import of https://github.com/cboling/omci at commit 7495182a09db38a9b6454a4a457fdd111c1618ac Change-Id: I3250449080300b21b9d81c64dcc33f98f2e4cd1b
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: