veyepar: Test your Docker images with Python

Author(s):	Jamie Hewland
Location	Yellowwood
Date	oct Thu 11	Days Raw Files
Start	14:40	First Raw Start	14:32
Duration	00:45:00	Offset	0:07:27
End	15:25	Last Raw End	15:32
Chapters	00:00 0:14:26
Total cuts_time	33 min.

https://za.pycon.org/talks/31-test-your-docker-images-with-python/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Test_your_Docker_images_with_Python.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	As more and more software is packaged in Docker images, it has become increasingly important that the Dockerfiles and scripts that these images are built from are correct. If Docker images are built and deployed as part of an automated pipeline, it is also important that they continue to work as expected when changes are made upstream. Start testing your Docker images without relying on Bash scripts! We’ll cover why we decided to write a testing library and how to use it. We’ll also talk about some of the test fixtures we developed for common infrastructure such as RabbitMQ and PostgreSQL. Finally, we’ll explore some of the limitations and workarounds of creating a test environment of Docker containers. Some of the best tools for working with Docker are already written in Python, for example, docker-compose. Bringing together the Python ecosystems around Docker and test frameworks, we created a new Python library called Seaworthy. Seaworthy can be used to verify that a Docker image works as expected in an isolated environment. It provides rich tools for asserting on processes, logs, and HTTP requests. markdown
Comment:	production notes

2018-10-11/14_32_33.ts Apply: 14:48:06 - 15:02:33 ( 00:14:26 ) S: 14:32:33 - E: 15:02:33 D: 00:30:00 (Start: 933.99402) show more...

vlc ~/Videos/veyepar/pyconza/pyconza2018/dv/yellowwood/2018-10-11/14_32_33.ts :start-time=0933.99402 --audio-desync=0

	Raw File	Cut List
	14:32:33		seconds: 933.99402 Wall: 14:48:06
Duration	00:30:00
	15:02:33		seconds: 0.0 Wall: 14:32:33
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2018-10-11/15_02_33.ts Apply: 15:21:58 - 15:32:32 ( 00:10:34 ) S: 15:02:33 - E: 15:32:32 D: 00:29:59 (Start: 1165.0) show more...

vlc ~/Videos/veyepar/pyconza/pyconza2018/dv/yellowwood/2018-10-11/15_02_33.ts :start-time=01165.0 --audio-desync=0

	Raw File	Cut List
	15:02:33		seconds: 1165.0 Wall: 15:21:58
Duration	00:29:59
	15:32:32		seconds: 0.0 Wall: 15:02:33
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this