Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Galaxy runner for Nomad #8

Open
innovate-invent opened this issue Jan 26, 2021 · 1 comment
Open

Implement Galaxy runner for Nomad #8

innovate-invent opened this issue Jan 26, 2021 · 1 comment

Comments

@innovate-invent
Copy link
Collaborator

innovate-invent commented Jan 26, 2021

https://pypi.org/project/python-nomad/
https://github.com/hashicorp/levant - relevant but not directly useable

The runner should take a HCL template and populate it with the job specifics. This way the template can be swapped out with the deployment and every possible parameter for running a job on Nomad doesn't need to be forwarded via the Galaxy config.

@innovate-invent
Copy link
Collaborator Author

innovate-invent commented May 21, 2021

The k8s and docker runners need to be rewritten to accept templates as well.
For k8s, it should take a k8s YAML file, and for docker it should take a docker compose YAML file.
For k8s, pykube needs to be replaced with https://github.com/kubernetes-client/python
For docker, compose functionality can be directly imported from https://github.com/docker/compose

All YAML files should be passed through a templating engine first. Because YAML uses # as comments, it would be ideal to use Galaxies existing Cheetah template engine as Cheetah uses # to demark template directives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant