cri-o/contrib/test/integration
Mrunal Patel b0e9f0eba8 Revert "Move crio default sock to /var/run/crio/crio.sock"
Signed-off-by: Mrunal Patel <mrunalp@gmail.com>
2017-10-19 10:13:49 -07:00
..
build Revert "Move crio default sock to /var/run/crio/crio.sock" 2017-10-19 10:13:49 -07:00
callback_plugins integration: Add color + readable logging 2017-09-28 14:05:25 -04:00
ansible.cfg integration: Add color + readable logging 2017-09-28 14:05:25 -04:00
e2e.yml contrib: test: fix e2e cmdline 2017-10-19 16:37:26 +02:00
golang.yml test: Update go to 1.8.4 2017-10-05 11:30:15 -07:00
main.yml integration: Use vars_files in plays 2017-09-28 14:05:25 -04:00
README.md Install Go directly from upstream, not through RPM 2017-10-02 07:18:41 -07:00
results.yml integration: Use vars_files in plays 2017-09-28 14:05:25 -04:00
system.yml Look up the container's name for kpod-stop-by-name 2017-10-12 17:54:47 -04:00
test.yml Install Go directly from upstream, not through RPM 2017-10-02 07:18:41 -07:00
vars.yml Install Go directly from upstream, not through RPM 2017-10-02 07:18:41 -07:00

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 tests
  • results.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 testing
  • e2e: build CRI-O from source and run Kubernetes node E2Es
  • integration: 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
  • ansible is installed and the host is boot-strapped to allow ansible to run against it
  • the $GOPATH is 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