Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

handling orchestrator options #35

Closed
2 tasks done
TathagataChakraborti opened this issue Mar 6, 2020 · 1 comment
Closed
2 tasks done

handling orchestrator options #35

TathagataChakraborti opened this issue Mar 6, 2020 · 1 comment
Assignees
@flipper83
Labels
enhancement New feature or request feature request New feature request. orchestration Associated with the orchestrator.

Comments

@TathagataChakraborti
Copy link
Member

TathagataChakraborti commented Mar 6, 2020 •
edited
Loading

Currently, the orchestration patter is specified in code [link]

  • We should move it to a config file -- configPlugins.json -- where the user can specify which orchestration pattern to use (and potentially install) at the time of installing CLAI.

  • Add command line option to change this option at runtime: e.g. >> clai orchestrate max_orchestration (this might require installing dependencies of the new pattern)
@TathagataChakraborti TathagataChakraborti added enhancement New feature or request feature request New feature request. orchestration Associated with the orchestrator. labels Mar 6, 2020
@flipper83 flipper83 mentioned this issue Mar 16, 2020
Merged
1 task
@TathagataChakraborti
Copy link
Member Author

Done with PR40. 🎉

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@flipper83 flipper83

Labels
enhancement New feature or request feature request New feature request. orchestration Associated with the orchestrator.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flipper83 @TathagataChakraborti