Support for deployment with single docker-compose file

[Tails]

I'm trying to compose a docker-compose file for my app with Telepat.io as a dependency. However, it is unclear to me how I'm supposed to link the two parts of Telepat.io. In the documentation it is stated that one should first start the shared dependencies for Telepat and wait for the logs to settle. How would you do that when combining the Telepat.io parts in a multi-container app if you want to retain the promise of docker compose to run your infrastructure with a single command?

[andreimarinescu]

Hi @Tails,

First of all sorry for the really late reply, I somehow missed this issue.

Secondly: the reason we've split these dependencies was that we wanted to make sure that the Telepat workers and API connected to a fully functional infrastructure. Since then, we've added quite a few mechanisms in place so that if the dependencies aren't up and running yet, Telepat will wait around and try to reconnect from time to time.

The issue is mainly with Kafka, since connecting to a transitioning Kafka cluster often leaves the whole system in a "locked" state. The consumers report to be connected but no messages are coming through.

I'll test this out again, but if your use-case demands it, you should be able to paste the contents of both docker-compose.yml files into 1 file and run it directly. Apart from having a lot of logs from the Telepat side being unable to connect to Couchbase or Kafka, things should run smoothly with the re-connection logic we've put in place.

I'm leaving this ticket open until we test everything out ourselves and create proper documentation for this use-case.

Let us know if you hit any other issues!

[Tails]

Thanks for the reply. I tried pasting them in a single file (and specifying the common stuff as dependency so it will run first) and it seems to work! I haven't tested it with real application code or a deployment to an external server though, so I could still get back to this.

On Tue, Jul 7, 2015 at 11:21 AM, Andrei Marinescu [email protected] wrote:

Hi @Tails https://github.com/Tails,

First of all sorry for the really late reply, I somehow missed this issue.

Secondly: the reason we've split these dependencies was that we wanted to make sure that the Telepat workers and API connected to a fully functional infrastructure. Since then, we've added quite a few mechanisms in place so that if the dependencies aren't up and running yet, Telepat will wait around and try to reconnect from time to time.

The issue is mainly with Kafka, since connecting to a transitioning Kafka cluster often leaves the whole system in a "locked" state. The consumers report to be connected but no messages are coming through.

I'll test this out again, but if your use-case demands it, you should be able to paste the contents of both docker-compose.yml files into 1 file and run it directly. Apart from having a lot of logs from the Telepat side being unable to connect to Couchbase or Kafka, things should run smoothly with the re-connection logic we've put in place.

I'm leaving this ticket open until we test everything out ourselves and create proper documentation for this use-case.

Let us know if you hit any other issues!

— Reply to this email directly or view it on GitHub https://github.com/telepat-io/telepat-docker-compose-files/issues/1#issuecomment-119134916 .