Gitiles
Code Review Sign In
gerrit.opencord.org / pyvoltha / 72469f2625cae1fe2ff20df7111c4cd2d1ca0d64
commit72469f2625cae1fe2ff20df7111c4cd2d1ca0d64[log] [tgz]
authorMatt Jeanneret <mj3580@att.com>Tue Mar 05 21:07:05 2019 -0500
committerMatt Jeanneret <mj3580@att.com>Tue Mar 05 21:07:34 2019 -0500
tree1b4f83b4254a2e19aeb8a6734cd73a5f644783bb
parent15ee2cc8c2928152e84eede93bf05f58fc29f7dd [diff]
VOL-1474 Implement get all child devices and get child device by proxy address

Change-Id: Ic9056df6cc03a4f7cdd68b974726ed71d51ec980
1 file changed
tree: 1b4f83b4254a2e19aeb8a6734cd73a5f644783bb
  1. .coveragerc
  2. .gitignore
  3. .gitreview
  4. CHANGES.txt
  5. LICENSE.txt
  6. MANIFEST.in
  7. Makefile
  8. README.md
  9. VERSION
  10. docker/
  11. env.sh
  12. pyvoltha/
  13. requirements.txt
  14. setup.py
  15. test-requirements.txt
  16. test/
  17. 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.