feat(docs): added ROADMAP.md file #1
Conversation
docs/ROADMAP.md
Outdated
|
|
||
| * execute HyperFlow job based on LLM prompt processed by Montage MCP server | ||
|
|
||
| This final goal is to perform following test case: |
There was a problem hiding this comment.
adjusted the typo
docs/ROADMAP.md
Outdated
| - 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) |
There was a problem hiding this comment.
I suggest "Using Hyperflow or Kubernetes MCP server" - Montage MCP will only be used for generating workflow.
There was a problem hiding this comment.
removed the Montage MCP server mention, as agreed it's purpose is only generating workflow file
docs/ROADMAP.md
Outdated
| - 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 |
There was a problem hiding this comment.
Before that add another bullet:
- User monitors the execution progress
docs/ROADMAP.md
Outdated
| 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 |
There was a problem hiding this comment.
Workflow execution is not Montage-specific (except for configuration details, such as docker image names), so it should be delegated to another server.
There was a problem hiding this comment.
Removed that bullet point, replaced with the LLM prepares kubectl or helm commands to execute HyperFlow task
m00lecule
force-pushed
the
roadmap-intro
branch
from
c383d02 to
e2787ff
Compare
No description provided.