...
- etcd ha test cases
- Issue is that there are two implementations, depending on how the k8s cluster has been deployed
- It would be better to have a single implementation that would work with both
- Juha and Cristina do not have access to an Airship deployment
- Docker makefile bug
- Fixed now
- Run tests using bluval
- UI implementation
- Discussion was about how to push jobs to validate different blueprints in different labs, since there are three kinds:
- The public community lab that runs in UNH-IOL
- 'Private
- ' company labs which can operate in
- a 'master/agent' Jenkins model
- Company labs that run in a peer model whereby the Edge lab jenkins only pulls and pushes but is not a slave to the LF jenkins.
- UNH
- Company run, but conne
- Purely internal
- All of these will push the results in the LF Nexus, but only the two first ones can take jobs from LF Jenkins (and hence the UI)
- Discussion was about how to push jobs to validate different blueprints in different labs, since there are three kinds:
May 29, 2019
- Pass variables to robot testcases (838)
- As discussed earlier, we want to make a single file with all variables
- Decision: go with the YAML version
- Organize file structure for tests (887)
- Proposal is to create a structure for storing the different tests
- Additional idea is to add "layer" to the structure
- Decision: Go ahead
- New idea: there should be a single container per layer, use bluval to select what tests to run
- Add container script for k8s ha (839): looks ok
- UI discussion: the web UI can run in Docker containers, Ioakeim will make the instructions available on how to build them
...