Weekly on Wednesdays at 8:00 AM PST / 11:00 AM EST.
Join Zoom Meeting: https://zoom.us/j/598290523
One tap mobile
+16699006833,,598290523# US (San Jose)
+16465588656,,598290523# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
+1 877 369 0926 US Toll-free
+1 855 880 1246 US Toll-free
Meeting ID: 598 290 523
Find your local number: https://zoom.us/u/acimKOClJk
Notes
March 27, 2019
Agenda:
- New committers to project
- New meeting time. Propose Wednesdays 10-11 (an hour earlier)
- Using IRC? Let's try the channel #akraino
- Let's try to clarify the project scope: passing the mandatory validation tests is a part of the Akraino process to mature a process, so it is very important to agree in the Akraino TSC what the mandatory tests are. There can be tests that are supported by the framework but which are not mandatory. The logic should be:
- If the blueprint installs Kubernetes, Kubernetes e2e conformance tests are mandatory
- If the blueprint installs OpenStack, OpenStack Tempest and Rally are mandatory
We also discussed making some HA tests mandatory. - Then we need to agree on how to move forward. Let's say you run a test; what happens next? If you run the test from LF Jenkins, it would be great to sync the results to the LF Jenkins. This requires that you are running your lab in a DMZ or you are opening a lot of ports on the firewall to run a slave Jenkins. So the easier alternative is to copy the results of the tests to the LF Nexus. To make it easy (for scripts) to understand the logs, we need to agree on a common format. For this, we propose running all tests using the Robot Framework.
- Will BVal.yaml be an optional component to make it easy to chain together a number of tests?
- To run the tests, I want to run something like "docker run --env-file abcd.txt --volume output.log akraino_k8s_tests". For this we need
- The docker container
- Definition of the env-file format: we need to figure out what information the test will require and write it to the environment file
- The actual code to read the environment file, launch the Robot Framework, run the tests with Robots, and copy the output to the output.log
- Once I have all this, I can make a Jenkins job in my lab which will launch the tests, and I can also configure it to copy the output somewhere.
March 6, 2019
Discussion about scope of testing + continue discussion about role of xtesting
The plan is to use the Xtesting part of the OPNFV Functest project as the basis for the Akraino Blueprint Validation project. There will be separate containers for the different test sets, hosted at the Docker Hub. The "source code" (docker yaml etc) will be hosted in the Gerrit repository, a Jenkins job will build the images, and then they will be uploaded. We need to identify the mandatory tests that all Akraino Blueprint projects must pass. There will be a centralized database to store test results, to make it easy to follow the progress of different projects. A web interface to the database would be nice.
Specific notes:
- The Nexus repository does not work well for storing Docker images that must support different architectures, as there is no support for manifest files. So it is best to use the Docker Hub for images
- Xtesting has two different modes, a "tutorial" one that installs a Jenkins instance, and one for the "Functest" type, where the xtesting framework only creates the Jenkins jobs.
- There is no need to have support for voting in the Jenkins jobs
- Trevor Bramwell has set up the OPNFV test database, should ask him
- Cedric is working on rewriting the web page code that shows the test results
February 27, 2019
Discussion about Xtesting.
February 13, 2019
Agenda/notes
- Weekly meetings
- Time is ok?
- Need to make official somehow
- Recording or not?
- Next week?
- Will use Jira
- Clarification of workflow
- Will BVF do testing or just provide the tools?
- Next tasks
- Collection of test tools
- Define "MVP"
- Get an introduction from OPNFV team
- What are we missing with this approach?
- ONAP VFN SDK project