Define use case scenario for docker_deploy and provide document/configuration for them

[s1061123]

docker deploy is firstly designed for PoC use-case, that is, launching jenkins-master/ELK stack in container of laptop PC and put jenkins slave to baremetal. At that time all jenkins job will be run at jenkins slave because jenkins_master of laptop PC is not powerful.

Bu on the other side, we would like to launch container with powerful baremetal. In this case, we'd like to run jenkins jobs at jenkins_mater. So there are several use case scenarios in docker deploy.

We need to clarify various use cases for docker deploy and provide configuration for them with document.

Here is current scenario:

• image downloader jobs on jenkins master or slave
• other jobs runs at slave, not master
• run TOAD with proxy setting (http_proxy / https_proxy), as config file or variables.

[s1061123]

One scenario is run PoC:

• run container in laptop or low spec machine
• need to run various task in baremetal (i.e. jenkins slave)

[zshi-redhat]

it's convenient to run image downloader jobs on jenkins master and distribute images to slaves; it's particularly useful in below scenario: 1) you have multiple slaves and each need to download the same images from internet, 2) downloading large images like undercloud and overcloud image is time-consuming.

[s1061123]

@zshi-redhat thanks, I will add above description. Let's listed up in this week (Mar 3, 2017), then implement (ansible/documnet).

[zshi-redhat]

in order to install toad behind proxy, need to add http_proxy & https_proxy support in docker-compose.yml or dockerfiles

[s1061123]

@zshi-redhat , thank you for your comment!

[zshi-redhat]

build and tag stable images and push to docker hub for easy consumption.
maybe adding a feature that making toad deployment environment into container where docker-compose and some extra configuration are executed after pulling the functional images(kibana, logstash, elasticsearch, jenkins_master)