Gitiles
Code Review Sign In
gerrit.opencord.org / pyvoltha / c607ac9d6fa00366c678d2e5c788c88e11b38c1a
commitc607ac9d6fa00366c678d2e5c788c88e11b38c1a[log] [tgz]
authorMatt Jeanneret <mj3580@att.com>Sat Apr 27 17:41:33 2019 -0400
committerMatt Jeanneret <mj3580@att.com>Tue Apr 30 15:51:54 2019 -0400
tree9b4d3656cdf53445fb5c1ee39f9f0aefdce0e522
parentece067c9899b0982e1851c7fc3690d0c7e3b9c17 [diff]
VOL-1489 Fully support tunnel_id openflow field

Change-Id: Ib148c59d79f40a2f3859a739c65fdf5eb1dcfbbd
2 files changed
tree: 9b4d3656cdf53445fb5c1ee39f9f0aefdce0e522
  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.