Create some acceptance tests.

[tomprince]

This should at least include running through the tutorial, to ensure that it works.

[itamarst]

I added links to some potentially relevant tools in #577.

[exarkun]

We've previously discussed not duplicating the steps documented in the tutorial as a requirement for this issue. In the interest of making some progress, we're going to drop that requirement for now. To resolve this issue we should have some kind of automated acceptance tests covering much or all of the same material as is covered in the tutorial but if we need to duplicate that material in the implementation of the acceptance tests, okay.

[exarkun]

Some rough notes from a discussion about how to go about implementing this:

• acceptance test run in docker - each node is run in a docker container (unlike tutorial which has VM per node)
  • requirement: docker-in-docker
  • requirement: zfs from inside docker
  • question: how separate are different storage pools on one machine?
  • limitation: doesn't exactly test our vagrant image
• use packer to build vagrant image and docker image
• checks out flocker from git

Out of scope:

• doesn't discover packaging bugs
  • run the test suite against a package install to find those

[itamarst]

Also need to be able to configure the name of the pool for a Flocker install, instead of current hard coding of "flocker".

[itamarst]

As first pass we should assume we're running on a Linux host machine with ZFS and Docker installed.

[tomprince]

I have in progress code to build a tutorial image, and then start it up, on buildbot. It would be easy to then run some code against those nodes.

[adamtheturtle]

See http://blog.docker.com/2013/09/docker-can-now-run-within-docker/ about running Docker in Docker

[adamtheturtle]

Tom by tutorial image you mean Vagrant image, right?

[tomprince]

The tutorial vagrant image, yes.