New cord-tester cross connect app to configure the leaf switch for cord-tester.
This is required when cord-tester is running on the head node on the PODD.
And compute node access is needed to test vcpes from inside the podd head node.
For now, we don't enable the configuration of the app as one cannot overwrite default xconnect flows.
Like eg: 222 which would be already configured.
In this case, we would just need new entries in olt config or use a new subscriber vcpe list
to open up for cord-tester vsg testing.

Change-Id: Ie96c3eba79aded235e67f05d806722abe6024ffa
9 files changed
tree: dc9c8b8c563ba7054399746076c1f72473586c8e
  1. .gitignore
  2. COPYRIGHT.txt
  3. Dockerfile.onos-builder
  4. Dockerfile.quagga
  5. Dockerfile.radius
  6. Dockerfile.tester
  7. LICENSE.txt
  8. README.md
  9. Vagrantfile
  10. apply_license.sh
  11. build-onos-docker.sh
  12. build.gradle
  13. buildSrc/
  14. config/
  15. cord-tester-deploy.yml
  16. cord-tester-verify.yml
  17. docs/
  18. gradle/
  19. gradlew
  20. gradlew.bat
  21. libs/
  22. roles/
  23. src/
README.md

cord-tester

CORD Automated Tester Suite

The CORD Automated Tester Suite (CATS) is an extensible end-to-end system test suite targeting CORD PODs. It is typically deployed as one or more Docker containers, either on the CORD POD or adjacent to the POD and interacts with the POD through the PODs interfaces.

Its intended use includes:

  • Regression testing for CORD related component development
  • Acceptance testing of a deployed CORD POD
  • Health-testing of an existing CORD POD (including non-service-impacting and possibly service-impacting tests)

The strength of the CATS will come from the collaboration of the whole CORD/ONOS community, and as such we welcome contributions.

For further information, please browse in the ~/docs directory.