9f14e51938
* The README.md doesn't metion an EPEL requirement, however it's needed for installing python-boto on RHEL. Add it to the list of requirements. * Some gramatical errors were fixed. * The ``system.yml`` install timeout (10 minutes) is cutting things aweful close, esp. since it's dependent on both networking and external services. Double it to head-off possible future headaches. Signed-off-by: Chris Evich <cevich@redhat.com> |
||
|---|---|---|
| .. | ||
| build | ||
| callback_plugins | ||
| ansible.cfg | ||
| critest.yml | ||
| e2e.yml | ||
| golang.yml | ||
| main.yml | ||
| node-e2e.yml | ||
| README.md | ||
| results.yml | ||
| system.yml | ||
| test.yml | ||
| vars.yml | ||
Fedora and RHEL Test execution
This directory contains playbooks to set up and run, all the CRI-O CI tests for both RHEL and Fedora hosts. Two entry-point playbooks exist:
main.yml: sets up the machine and runs tests.results.yml: gathers test output to/tmp/artifacts.
When running the main.yml playbook, multiple tags are present:
setup: run all tasks to set up the system for testing.e2e: build CRI-O from source and run Kubernetes end-to-end tests.node-e2e: build CRI-O from source and run Kubernetes 'node' end-to-end tests.integration: build CRI-O from source and run the local integration suite.
The playbooks assume the following things about your system:
- On RHEL, the repositories for EPEL, rhel-server, and extras repos are configured and functional.
- The system has been rebooted after installing/updating low-level packages, to ensure they're active.
- Ansible is installed, and functional with access to the 'root' user.
- The
$GOPATHis set and present for all shells (e.g. written in/etc/environment). - The CRI-O repository is present in the desired state at
${GOPATH}/src/github.com/kubernetes-incubator/cri-o.