This repository has been archived by the owner on Jun 9, 2020. It is now read-only.
Placeholder for roles & playbooks to address OpenEBS issue #463 #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a need to reduce the time taken for the integration test suite execution
that is triggered by jenkins. This should be approached in different ways, one way
being - loading pre-pulled test images just before tests, so as to avoid pulling a
test image freshly during the suite
This commit addresses the above by introducing the following :
a) Ansible role and playbook to pull test images specified by a list
b) Ansible role and playbook to load this into test k8s nodes (vagrantVM /baremetal)
c) Updates to ci.yml to include load step
d) Updates to global var specification file all.yml to hold some test labels
Expected to reduce test time by having the image tar file ready
The load step, where the images are loaded into the test nodes via docker load command
takes time on the vagrant VMs. Need to identify machines w/ better resource OR a more
optimal load technique.
Sometimes , docker load can be a bursty Write spike on the VM storage which can take
up system resources making the process slow. One approach is to have multiple load operations
than one single large load. This will also help with versioning/maintenance of test images.
However, the current changes will first have to be tested to identify the efficacy before moving
on to enhancements. This is yet to be done due to certain issue on the local jenkins setup.