-
Notifications
You must be signed in to change notification settings - Fork 0
feat(docs): added ROADMAP.md file #1
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
base: master
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -43,6 +43,7 @@ workflows/ | |
| *.fits | ||
| *.tbl | ||
| *.hdr | ||
| test-output/* | ||
|
|
||
| # Environment variables | ||
| .env | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| # High-level roadmap overview | ||
|
|
||
| * execute HyperFlow job based on LLM prompt processed by Montage MCP server | ||
|
|
||
| This final goal is to perform following test case: | ||
| - user prompts LLM about astronomical image mosaic | ||
| - LLM passes the question to Montage MCP Server | ||
| - Montage prepares workflow definition | ||
| - LLM schedules workflow execution on HyperFlow (using Montage or 3rd party Kubernetes MCP server) | ||
|
||
| - users gets the requested astronomical image mosaic | ||
|
||
|
|
||
| * architecture design | ||
|
|
||
| The objective is to conclude the Montage MCP server and HyperFlow communication. | ||
|
|
||
| Currently there are two options: | ||
| - implement the HyperFlow tasks execution in Montage MCP server | ||
|
||
| - design a solution using two MCP servers: Montage and one supporting Kubernetes | ||
|
|
||
| * assess the Kubernetes MCP servers maturity | ||
|
|
||
| The goal is to investigate the capabilities of Kubernetes MCP server. The objective is to conclude if they are capable of creating a HyperFlow task. | ||
|
|
||
| * HyperFlow task monitoring | ||
|
|
||
| The objective is to inform the LLM the task calculation status. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The final
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adjusted the typo