Gitiles
Code Review Sign In
gerrit.opencord.org / pyvoltha / 415a296cda162631839b27095130dc2465d25e25
commit415a296cda162631839b27095130dc2465d25e25[log] [tgz]
authorYongjie Zhang <yzhang@furukawalatam.com>Wed Jul 03 15:46:50 2019 -0400
committerYongjie Zhang <yzhang@furukawalatam.com>Thu Jul 04 10:24:24 2019 -0400
treed191104651ef35b635d7714f6081afcd8712ca10
parentaa829332fae6b37cf31ec24629d6a5255f997246 [diff]
[VOL-1698] OMCI PM does not work

Pass ONU's serial number to OnuPmMetrics

Change-Id: Ia45f551c185414b71be6502a7bb71665f9050541
5 files changed
tree: d191104651ef35b635d7714f6081afcd8712ca10
  1. .coveragerc
  2. .gitignore
  3. .gitreview
  4. CHANGES.txt
  5. LICENSE.txt
  6. MANIFEST.in
  7. Makefile
  8. README.md
  9. VERSION
  10. env.sh
  11. pyvoltha/
  12. requirements.txt
  13. setup.py
  14. test-requirements.txt
  15. test/
  16. tox.ini
README.md

PyVOLTHA

PyVOLTHA is a collection of shared Python libraries that are use to create Python-based VOLTHA Device Adapters and other Python utilities (CLI, ...) that need to work with the VOLTHA v2.0 and later Golang core.

Initially PyVOLTHA will target only Python 2.7, but contributors are encouraged to write or refactor any library methods to eventually support Python 3.6.x or later.

Installation instruction

pip install pyvoltha

Release History

VersionDateNotes
v0.1.02019-02-01Initial pypy release available. This is primarily for testing out pip install support and is not expected to be useful outside of that.

Detailed Release History

v0.1.0 (2019-02-01)

  • Experimental release of pyvoltha to test pip install capabilities. This version has manually created protobuf definitions and will probably not be very usable by any device adapters.
  • This version is not under source control management at this time. Initial VCS support is anticipated in the very near future when portions of this project can be consumed by a device adapter developer.
  • Protobuf files in the 'proto' directory were hand copied over from the voltha-go repository. These will eventually be in a separate repo that developers will need to include.
  • Most all import paths fixed but that does not mean everything works
  • A fair number of original unit tests are working after import changes. Others need work.