MiniWDL added Podman support; Testers and Pings to Verticals Needed
Hi Podman community, Short info that there is another open source project that can run on Podman now. See: https://github.com/chanzuckerberg/miniwdl/issues/520#issuecomment-981051895 MiniWDL is an engine that can run task-trees, sometimes called Pipelines or Flows or CI/CD engine and probably others, from the bioscience and bioinformatics world. Each task is wrapped in a container, and that is where Podman can come in handy. A huge advantage of MiniWDL is that it uses the standardised format WDL to represent its task-trees. Standardised data format means more integrations and more solution independence for the users. For Podman this integration is valuable in two ways: - It extends the capabilities to run multiple containers together for a shared purpose. But where kube play makes life easier for web service maintainers, MiniWDL makes life easier for event-driven data processors, e.g. in Big Data, IoT, or similar scenarios. - It might help grow awareness for Podman in these communities: science, bioinformatics, pharma, medical, police forces. I think, after having an integration between both projects, it would make sense, if someone could have a look if the right Podman commands have been used, technical limitations and security have been considered enough, and what else? Also, a product manager could check in with the corresponding vertical communities if that could open some collaboration opportunities elsewhere. And last but not least, maybe it could extend the use cases for which Podman is useful, right? Let me know what you think! Best, Erik
On 11/28/21 05:08, Erik Bernoth wrote:
Hi Podman community,
Short info that there is another open source project that can run on Podman now. See: https://github.com/chanzuckerberg/miniwdl/issues/520#issuecomment-981051895
MiniWDL is an engine that can run task-trees, sometimes called Pipelines or Flows or CI/CD engine and probably others, from the bioscience and bioinformatics world. Each task is wrapped in a container, and that is where Podman can come in handy. A huge advantage of MiniWDL is that it uses the standardised format WDL to represent its task-trees. Standardised data format means more integrations and more solution independence for the users.
For Podman this integration is valuable in two ways: - It extends the capabilities to run multiple containers together for a shared purpose. But where kube play makes life easier for web service maintainers, MiniWDL makes life easier for event-driven data processors, e.g. in Big Data, IoT, or similar scenarios. - It might help grow awareness for Podman in these communities: science, bioinformatics, pharma, medical, police forces.
I think, after having an integration between both projects, it would make sense, if someone could have a look if the right Podman commands have been used, technical limitations and security have been considered enough, and what else?
Also, a product manager could check in with the corresponding vertical communities if that could open some collaboration opportunities elsewhere.
And last but not least, maybe it could extend the use cases for which Podman is useful, right?
Let me know what you think!
Best, Erik
_______________________________________________ Podman mailing list --podman@lists.podman.io To unsubscribe send an email topodman-leave@lists.podman.io
Great news. Tom didn't we talk about making a site up with links to different places where Podman works?
On Mon, Nov 29, 2021 at 9:10 PM Daniel Walsh <dwalsh@redhat.com> wrote:
On 11/28/21 05:08, Erik Bernoth wrote:
Hi Podman community,
Short info that there is another open source project that can run on Podman now. See: https://github.com/chanzuckerberg/miniwdl/issues/520#issuecomment-981051895
MiniWDL is an engine that can run task-trees, sometimes called Pipelines or Flows or CI/CD engine and probably others, from the bioscience and bioinformatics world. Each task is wrapped in a container, and that is where Podman can come in handy. A huge advantage of MiniWDL is that it uses the standardised format WDL to represent its task-trees. Standardised data format means more integrations and more solution independence for the users.
For Podman this integration is valuable in two ways: - It extends the capabilities to run multiple containers together for a shared purpose. But where kube play makes life easier for web service maintainers, MiniWDL makes life easier for event-driven data processors, e.g. in Big Data, IoT, or similar scenarios. - It might help grow awareness for Podman in these communities: science, bioinformatics, pharma, medical, police forces.
I think, after having an integration between both projects, it would make sense, if someone could have a look if the right Podman commands have been used, technical limitations and security have been considered enough, and what else?
Also, a product manager could check in with the corresponding vertical communities if that could open some collaboration opportunities elsewhere.
And last but not least, maybe it could extend the use cases for which Podman is useful, right?
Let me know what you think!
Best, Erik
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Great news. Tom didn't we talk about making a site up with links to different places where Podman works?
@Máirín Duffy <duffy@redhat.com> is assembling a list of such projects for the upcoming website.
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
participants (3)
-
Daniel Walsh -
Erik Bernoth -
Valentin Rothberg