You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2020. It is now read-only.
Currently we can execute GOADs lambda functions on a local docker service. To be able to execute GOAD on a Kubernetes Cluster, Docker Swarm or Openshift we need to address two issues.
First GOADs commandline interface needs to be able to connect to the rabbitmq gathering the results of the individual test runners. Right now the cli tries to connect to a rabbitmq on a virtual docker network. A possible solutions would be to open an ssh tunnel to the docker swarm client that runs rabbitmq and map the port over to the local machine.
Secondly we need to provision the docker container with the goad runner code and payload. Right now a directory containing the code to be executed is mounted to the container. To remove this dependency to the local file system we could copy the code into the container and create a new container snapshot to be executed on the swarm, effectively baking the runner code into a container file system layer.
The text was updated successfully, but these errors were encountered:
@cwaltken-edrans please revive the docker based WebUI... that should be an easy to use L&P that anybody can install in its Kubernetes cluster. On top of that, we need to reach (with ssh port forwarding) the same CLI UI behaviour as we have right now against AWS
Currently we can execute GOADs lambda functions on a local docker service. To be able to execute GOAD on a Kubernetes Cluster, Docker Swarm or Openshift we need to address two issues.
First GOADs commandline interface needs to be able to connect to the rabbitmq gathering the results of the individual test runners. Right now the cli tries to connect to a rabbitmq on a virtual docker network. A possible solutions would be to open an ssh tunnel to the docker swarm client that runs rabbitmq and map the port over to the local machine.
Secondly we need to provision the docker container with the goad runner code and payload. Right now a directory containing the code to be executed is mounted to the container. To remove this dependency to the local file system we could copy the code into the container and create a new container snapshot to be executed on the swarm, effectively baking the runner code into a container file system layer.
The text was updated successfully, but these errors were encountered: