Hi bigtop/.
I got some time to work on bigtop-1235, finally.
I'd like to add a docker based "test" of it as part of the patch.
Im wondering if we;'ve decided on a way we are planning on
organizing the work around docker.
Options:
1) possibly we could add a new directory, each with a docker
recipe and README for a given task , like this:
bigtop-docker/
build-all-rpm/
Dockerfile
README
build-all-deb/
run-smoke-tests/
Dockerfile
README
test-puppet-hcfs/
Dockerfile
README
This way, the dockerized tasks are centralized into a part of the codebase,
rather
than being strewn about in various places.
2) Another way we can do it , is we can agree that certain directories will
contain a Dockerfile+README instructions about how to use that Dockerfile.
And each directory
manages this on its own.
Other thoughts on where the docker functionality should go, and how we will
maintain it?
--
jay vyas
