b0da62fcb0
Signed-off-by: Mrunal Patel <mrunalp@gmail.com> Signed-off-by: Antonio Murdaca <runcom@redhat.com> |
||
|---|---|---|
| .. | ||
| build | ||
| callback_plugins | ||
| ansible.cfg | ||
| e2e.yml | ||
| golang.yml | ||
| main.yml | ||
| README.md | ||
| results.yml | ||
| system.yml | ||
| test.yml | ||
| vars.yml | ||
Fedora and RHEL Integration and End-to-End Tests
This directory contains playbooks to set up for and run the integration and end-to-end tests for CRI-O on RHEL and Fedora hosts. Two entrypoints exist:
main.yml: sets up the machine and runs testsresults.yml: gathers test output to/tmp/artifacts
When running main.yml, three tags are present:
setup: run all tasks to set up the system for testinge2e: build CRI-O from source and run Kubernetes node E2Esintegration: build CRI-O from source and run the local integration suite
The playbooks assume the following things about your system:
- on RHEL, the server and extras repos are configured and certs are present
ansibleis installed and the host is boot-strapped to allowansibleto run against it- the
$GOPATHis set and present for all shells (e.g. written in/etc/environment) - CRI-O is checked out to the correct state at
${GOPATH}/src/github.com/kubernetes-incubator/cri-o - the user running the playbook has access to passwordless
sudo