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.

Sign up for GitHub

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

Jump to bottom

Custom Execution Backends #1185

Closed
brollb opened this issue Sep 21, 2018 · 2 comments
Closed

Custom Execution Backends #1185

brollb opened this issue Sep 21, 2018 · 2 comments
Labels
discussion enhancement job execution pipeline execution

Comments

@brollb
Copy link
Contributor

brollb commented Sep 21, 2018

Users should be able to specify different execution backends such as executing locally or on other HPC resources.

This is a pretty vague, open-ended issue and will just contain discussion/thoughts around how custom backends should be supported. This includes questions like should backends be packaged with deepforge or be separate extensions?
@brollb brollb mentioned this issue Sep 21, 2018
Closed
@brollb
Copy link
Contributor Author

brollb commented Sep 19, 2019

They would be easier to manage (at least at the start) as packaged with deepforge.

@brollb brollb mentioned this issue Sep 19, 2019
Closed
@brollb
Copy link
Contributor Author

brollb commented Oct 8, 2019

Closing this as custom execution backends are now supported as of #1244 and #1227. Custom execution backends are packaged with deepforge and enabled/disabled in the config/components.json. Users can then set their desired backend upon executing a pipeline/job

@brollb brollb closed this as completed Oct 8, 2019
@brollb brollb mentioned this issue Oct 8, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion enhancement job execution pipeline execution
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brollb