service waiting logic

[ppanero]

Example execution with ES7 (slowest):

$ docker-services-cli up  es postgresql redis mysql
Creating network "docker_services_cli_default" with the default driver
Creating docker_services_cli_redis_1      ... done
Creating docker_services_cli_es_1         ... done
Creating docker_services_cli_mysql_1      ... done
Creating docker_services_cli_postgresql_1 ... done
es not ready at 1 retries, waiting 2s
es not ready at 2 retries, waiting 4s
es not ready at 3 retries, waiting 8s
es up and running!
postgresql up and running!
redis up and running!
mysql up and running!
Services up!

[diegodelemos]

In my opinion, I think that this code belongs to the wait_for_services implementation, it is just what in other languages would be a switch/case etc.. so no need for the comment.

[ppanero]

Fine. I am still not convinced because by that line of thought we should have the services configuration (e.g. MYSQL) also in the services.py file.

In any case to be able to keep going I opened an question issue #4 and removed the comment.

[ppanero]

@diegodelemos sample of usage running here: https://travis-ci.org/github/ppanero/invenio-records-rest/builds/721264883 (I checked the devel failing ones and is because some issue with the Flask-Login version - i.e. out of scope of this PR)

[diegodelemos]

services needs a default (which should be all services). If one does:

$ docker-services-cli up

The wait_for_services doesn't do anything because services is an empty list.

[diegodelemos]

LGTM, solution for #2 (comment) discussed over videocall.