vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/contrib/test/integration
History
Nalin Dahyabhai 492f758176 Playbooks: don't assume the default network is eth0 
Replace instances of "ansible_eth0.ipv4.address" with
"ansible_default_ipv4.address" in the integration test playbook, so that
we can run tests without depending on the name of the primary network
interface being "eth0".

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
2017-12-14 14:23:53 -05:00
..
build Playbooks: don't assume the default network is eth0 2017-12-14 14:23:53 -05: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
critest.yml CI: wire in critest 2017-11-21 11:19:37 +01:00
e2e.yml Playbooks: don't assume the default network is eth0 2017-12-14 14:23:53 -05:00
golang.yml CI: drop git-validation as it's never used 2017-11-28 11:40:06 +01:00
main.yml CI: split critest from e2e 2017-12-14 00:09:36 +01: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 test: Add networking settings for critest 2017-10-31 13:14:50 -07:00
test.yml CI: wire in critest 2017-11-21 11:19:37 +01:00
vars.yml Revert "integration-playbook: Idempotent Swapping" 2017-10-24 09:36:56 -07:00

README.md

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