BIGTOP-2254. Replace the Docker orchestration tool from Vagrant to Do…

[evans-ye]

No description provided.

[evans-ye]

OK. I've pushed a new commit:
evans-ye@b6579c9

Basically updated the REAME to drop vagrant and switch to docker-compose.
I've also rename the config file name all around the code.

This is for you to review what has been changed.
I'll strip these two into one patch when actually committed.
Thanks!

[evans-ye]

No. I'll still go to a feature branch so that we don't have confusing things inside 1.1 release.
The feature is completely switched from vagrant to docker-compose. I've removed vagrant name entirely in the new commit. :)

[ghost]

Let's do the branch and keep on working around it. I think your stuff is pretty much ready, but want to play with it a little bit if you don't mind.

[evans-ye]

How so? It should be just two command:
$ curl -L https://github.com/docker/compose/releases/download/1.5.2/docker-compose-`uname -s-uname -m` > /usr/local/bin/docker-compose
$ chmod +x /usr/local/bin/docker-compose

The docker engine, OTOH, is much complicated on ubuntu 14...

[ghost]

Dunno, I've tried it about a month ago - it was a complete mess. I will try again today or tomorrow and comment here. Thanks!

[evans-ye]

I just tried. It should work instantly :)

[evans-ye]

I'll check in to a branch and iterate on it. That way I can also setup a CI for it. Thanks for the review!

[ghost]

Cool, and I will use of the branch to test in my environment. Thanks!

[ghost]

Yeah, looks like I know what my problem with the installation was. I've tried to do 'pip install' which was an idiotic idea, cause nothing really works in Python world out of the box. the way you suggested it, indeed, worked well. Thanks!

[evans-ye]

Awesome! Glad it works!

[ghost]

One more though: perhaps, it makes sense to add a version of README to the new provisioner directory? It is a bit awkward to read about compose in the README belonging to vagrant provisioner. No?

[evans-ye]

I'm not quite sure what you mean by:
It is a bit awkward to read about compose in the README belonging to vagrant provisioner. No?

Right now we have bigtop/provisioner/docker/README.md for docker-compose.
There will be bigtop/provisioner/vagrant/REAME.md for vagrant provisioner onece we moved it from bigotp-deploy.

[ghost]

I don't see bigtop/provisioner/docker/README.md file at all. Looks like that changes to README were made to bigtop-deploy/vm/vagrant-provisioner-docker/REAME.md
Sorry if I am confusing something, but the first location doesn't seem to have any readme files.

[evans-ye]

It's in the right place:
https://github.com/apache/bigtop/blob/BIGTOP-2253/provisioner/docker/README.md
Would you mind to check again?

[ghost]

Sorry, you're right. Getting tired...
Do you think we need to provide a mechanism for ppl to get into these containers via ssh or 'docker attach' or else? Thanks!

[evans-ye]

Sure. That what I plan to do in BIGTOP-2273.