Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ workflows/
*.fits
*.tbl
*.hdr
test-output/*

# Environment variables
.env
Expand Down
26 changes: 26 additions & 0 deletions docs/ROADMAP.md
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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The final

Copy link
Collaborator Author

@m00lecule m00lecule Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adjusted the typo

- 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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest "Using Hyperflow or Kubernetes MCP server" - Montage MCP will only be used for generating workflow.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed the Montage MCP server mention, as agreed it's purpose is only generating workflow file

- users gets the requested astronomical image mosaic
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before that add another bullet:

  • User monitors the execution progress

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added


* 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Workflow execution is not Montage-specific (except for configuration details, such as docker image names), so it should be delegated to another server.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed that bullet point, replaced with the LLM prepares kubectl or helm commands to execute HyperFlow task

- 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.