vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/contrib/test/integration
History
umohnani8 e5fdb6bc9e Vendor in latest k8s.io changes 
These changes allow for the container's pid namespace to be set to the same
as the pod infra container's namespace if the pid namespace mode is set to POD

Signed-off-by: umohnani8 <umohnani@redhat.com>
2018-03-02 09:31:34 -05:00
..
build test: Bump up runc to 9f9c96235cc97674e935002fc3d78361b696a69e 2018-01-23 11:06:21 -08: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 Don't skip a critest that we now pass 2017-12-14 14:23:53 -05:00
e2e.yml Update code for latest k8s 2018-02-21 11:03:56 -08:00
golang.yml CI: drop git-validation as it's never used 2017-11-28 11:40:06 +01:00
main.yml Vendor in latest k8s.io changes 2018-03-02 09:31:34 -05:00
node-e2e.yml contrib: test: add node-e2e job 2018-01-11 16:56:47 +01:00
README.md integration/README.md: add missing newline 2018-02-02 10:18:27 +01:00
results.yml integration: Use vars_files in plays 2017-09-28 14:05:25 -04:00
system.yml Playbooks: install the atomic-registries package 2017-12-14 14:23:53 -05: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