Nice to have: Better print out on the client for what's going on

[aronchick]

I ran something that was a fairly long running container - but didn't expect it to be.

bf30a0f63dd2:~# bacalhau docker run ubuntu echo "Hello, Bacalhau"
Job successfully submitted. Job ID: j-d0683fe4-962c-4300-a739-5a54f38c6f99
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

 TIME          EXEC. ID    TOPIC            EVENT
 16:31:33.842              Submission       Job submitted
 16:31:33.845  e-bd8269ab  Scheduling       Requested execution on fd9ff673
 16:31:35.432  e-bd8269ab  Execution        Running
 16:32:02.689  e-bd8269ab  Execution        Completed successfully

To get more details about the run, execute:
	bacalhau job describe j-d0683fe4-962c-4300-a739-5a54f38c6f99

To get more details about the run executions, execute:
	bacalhau job executions j-d0683fe4-962c-4300-a739-5a54f38c6f99

bf30a0f63dd2:~#

This was clearly because it had to download a container in order to run. It' be really nice to display that better for the user for more visibility around the job.

16:31:35.437 | INF pkg/executor/docker/executor.go:121 > starting execution [NodeID:fd9ff673] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [executionID:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99] [jobID:j-d0683fe4-962c-4300-a739-5a54f38c6f99]
16:31:53.49 | INF pkg/executor/docker/executor.go:213 > waiting on execution [executionID:e-bd8269ab-9890-46b8-bcef-1b232c00d306]
16:31:53.49 | INF pkg/executor/docker/handler.go:70 > starting container execution [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99]
16:32:02.679 | INF pkg/executor/docker/handler.go:139 > received status from container [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99] [status:0]
16:32:02.68 | INF pkg/executor/docker/handler.go:164 > captured stdout/stderr for container [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99]
16:32:02.68 | INF pkg/executor/docker/handler.go:172 > container execution ended [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99] [status:0]
16:32:02.68 | INF pkg/executor/docker/handler.go:186 > destroying the container [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99]
16:32:02.68 | INF pkg/executor/docker/handler.go:178 > killing the container [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99]
16:32:02.681 | INF pkg/executor/docker/handler.go:195 > removing container [container:c5e428e7ad252db72b2f9dc6b45605ee05b2cfd29fceeec28c6c95b5752bdfb2] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99]
16:32:02.687 | INF pkg/executor/docker/executor.go:223 > received results from execution [executionID:e-bd8269ab-9890-46b8-bcef-1b232c00d306]
16:32:02.688 | INF pkg/compute/executor.go:193 > cleaning up execution [NodeID:fd9ff673] [execution:e-bd8269ab-9890-46b8-bcef-1b232c00d306] [job:j-d0683fe4-962c-4300-a739-5a54f38c6f99]

[linear]

ENG-422 Nice to have: Better print out on the client for what's going on