On 17/03/2016 05:34, Nadeesh Dilanga wrote:
Hi team,
I am Nadeesh, a final year undergraduate in Computer Science from Sri
Lanka.
Hello Nadeesh
I found Docker as an excellent solution for scaling, easy deployment and
obviously a hot topic these days in enterprises who want to implement micro
services based architecture/deployment for low footprint servers/services.
I presume the idea behind Docker support for Taverna is NOT from a micro
service standpoint, but more like from a packaging and deployment
perspective. Please correct me if I am wrong.
There are two separate issues:
https://issues.apache.org/jira/browse/TAVERNA-901 is to allow Taverna
workflows to include steps that are tools that inside docker containers.
That would be deployment of an existing docker.
https://issues.apache.org/jira/browse/TAVERNA-879 is to create docker
containers for Taverna workflows. That is packaging and (because the
containers will be part of a CWL workflow) deployment.
If that is the case, can you please clarify what is the current packaging
deployment model ?
There is no current mechanism for packaging up something to run a
specific Taverna workflow. You can run workflows from the command line
tool or on a Taverna Server.
Like puppet for example. So that I can go through them
to understand how things works and then reuse or port those to docker.
Thanks
/nadeesh
Alan
