Teuthology docker targets hack (5/5)

The teuthology container hack is improved to run teuthology-suite. For instance:

./virtualenv/bin/teuthology-suite \
  --distro ubuntu \
  --suite-dir $HOME/software/ceph/ceph-qa-suite \
  --config-file docker-integration/teuthology.yaml \
  --machine-type container \
  --owner loic@dachary.org \
  --filter 'rados:basic/{clusters/fixed-2.yaml fs/btrfs.yaml \
     msgr-failures/few.yaml tasks/rados_cls_all.yaml}' \
  --suite rados/basic --ceph ANY \
  $(pwd)/docker-integration/ubuntu.yaml

schedules a single job out of the rados suite and the results can be collected in the teuthology-worker archive directory:

$ tail -5 /tmp/a/loic-2015-06-06_16:06:57-rados:\
    basic-ANY---basic-container/22/teuthology.log
06:57-rados:basic-ANY---basic-container/22/teuthology.log
    tasks/rados_cls_all.yaml}', duration: 1017.5819008350372, \
  flavor: basic, owner: loic@dachary.org,
  success: true}
2015-06-06T16:24:38.634 WARNING:teuthology.report:No result_server \
  in config; not reporting results
2015-06-06T16:24:38.634 INFO:teuthology.run:pass

tox integration tests

The docker-delegate tox environment can be used to setup a teuthology cluster to run integration tests such as lock –list –all.
A container is created with tox -e docker-delegate, a cluster setup and tox run again in the container to take advantage of it with tox -e docker-integration.

$ tox -e docker-delegate
GLOB sdist-make: /home/loic/software/ceph/teuthology/setup.py
docker-delegate runtests: PYTHONHASHSEED='1772658356'
...
docker run --rm --privileged --name teuthology-ubuntu-14.04 \
   --hostname teuthology-ubuntu-14.04 \
   -v /tmp:/tmp -v /packages \
   -v /var/run/docker.sock:/run/docker.sock \
   -v /usr/bin/docker:/bin/docker \
   -v /home/loic:/home/loic \
   -w /home/loic/software/ceph/teuthology \
   --user 1000 teuthology-ubuntu-14.04 \
   env HOME=/home/loic tox -e docker-integration
...
GLOB sdist-make: /home/loic/software/ceph/teuthology/setup.py
docker-integration recreate: /home/loic/software/ceph/teuthology/.tox/docker-integration
...
docker-integration/test.py::TestLock::test_list PASSED

=========================== 1 passed in 0.12 seconds ===========================
___________________________________ summary ____________________________________
  docker-integration: commands succeeded
  congratulations :)
___________________________________ summary ____________________________________
  docker-delegate: commands succeeded
  congratulations :)

container based teuthology-suite

The container created for tox integration tests can be re-used to manually run jobs.

docker run \
  --privileged \
  --rm --name teuthology-ubuntu-14.04 \
  -v /srv/hosts \
  -v /tmp:/tmp/tmp \
  -v /home/tmp:/packages \
  -v /var/run/docker.sock:/run/docker.sock \
  -v $(which docker):/bin/docker \
  -v $HOME:$HOME -w $(pwd) \
  --user $(id -u) -t -i \
  teuthology-ubuntu-14.04 bash

The /home/tmp directory must first be populated with make-debs.sh

$ make-debs.sh /home/tmp

Once in the container, the teuthology cluster is created with

loic@85fdacf1c0e3:~/software/ceph/teuthology$ docker-integration/setup.sh
docker-integration/setup.sh
Current branch master is up to date.
New python executable in ./virtualenv/bin/python
...
loic@85fdacf1c0e3:~/software/ceph/teuthology$ ps
  PID TTY          TIME CMD
    1 ?        00:00:01 bash
  215 ?        00:00:04 pecan
  221 ?        00:00:00 beanstalkd
12126 ?        00:00:00 teuthology-worker

The beanstalkd bus is used by teuthology-schedule to communicate with the teuthology-worker which will teuthology-lock machines from paddles (the pecan daemon). When the machines are locked, it calls teuthology to run the job and stores the results in the archive directory for forensic analysis (/tmp/a in the example above).

This entry was posted in ceph, docker. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>