Introduce custom baseimage override

[morganekmefjord]

To streamline better test projects In this suggested commit there are a new structure to allow for overriding of parameters.

version: '3.7'
services:
  client:
    build:
      context: .
      dockerfile: components/client/Dockerfile
      args:
        baseimage: "tensorflow/tensorflow:latest"

Illustrated by an example

docker-compose -f docker-compose.yaml -f reducer.yaml -f combiner.yaml -f client.yaml **-f tensorflow.yaml** --build --scale client=5

where tensorflow.yaml in this example is overriding the BASEIMAGE variable to the Dockerimage and instructs which base image to initiate the client image from.

In this sense the tests we construct can have the same basic structure but depending on framework selected can inherit base image from for example tensorflow to ensure the execution context is present.

[ahellander]

Looks good but you accidentally made the PR to master...

[morganekmefjord]

Looks good but you accidentally made the PR to master...

Changed base to develop..

[morganekmefjord]

@ahellander But what do you think of this as an alternative approach to handle underlaying framework dependencies?

[sztoor]

If we want to support different versions of TensorFlow, I think it will be a good strategy. But it may introduce extra complexity in the framework.

[ahellander]

Yes, I think this is a good idea. Also because we will need to link in a different environment depending on the helper class we are using (TF, Torch, Sklearn) also for the Combiners.