From 9324d283cc0ab26ab7bc687c4bdaa55614c6753f Mon Sep 17 00:00:00 2001 From: Michal Dygas Date: Sun, 9 Nov 2025 23:45:38 +0100 Subject: [PATCH 1/4] feat(docs): added ROADMAP.md file --- .gitignore | 1 + docs/ROADMAP.md | 26 ++++++++++++++++++++++++++ 2 files changed, 27 insertions(+) create mode 100644 docs/ROADMAP.md diff --git a/.gitignore b/.gitignore index 5291a32..c2c4b18 100644 --- a/.gitignore +++ b/.gitignore @@ -43,6 +43,7 @@ workflows/ *.fits *.tbl *.hdr +test-output/* # Environment variables .env diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md new file mode 100644 index 0000000..2c470e8 --- /dev/null +++ b/docs/ROADMAP.md @@ -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. From e2787ff15c27a66848b5eb54142d44713d206f83 Mon Sep 17 00:00:00 2001 From: m00lecule Date: Mon, 17 Nov 2025 17:28:07 +0100 Subject: [PATCH 2/4] fix(docs/ROADMAP.md): applied requested changes --- docs/ROADMAP.md | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index 2c470e8..af5036d 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -1,26 +1,27 @@ # High-level roadmap overview -* execute HyperFlow job based on LLM prompt processed by Montage MCP server +* execute HyperFlow job based on an LLM prompt processed by Montage MCP Server -This final goal is to perform following test case: +The final goal is to perform the 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 +- Montage prepares a workflow definition +- LLM schedules workflow execution on HyperFlow (LLM native kubectl support or 3rd party Kubernetes MCP server) +- user monitors the execution progress +- the user gets the requested astronomical image mosaic * architecture design -The objective is to conclude the Montage MCP server and HyperFlow communication. +The objective is to define 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 +- design a solution using two MCP servers: the Montage and one supporting Kubernetes +- the LLM prepares kubectl or helm commands to execute HyperFlow task * 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. +The goal is to investigate the capabilities of the Kubernetes MCP server. The objective is to determine whether it is capable of creating a HyperFlow task. * HyperFlow task monitoring -The objective is to inform the LLM the task calculation status. +The objective is to inform the LLM of the task calculation status. From ac0b20ee42f90c1c768c081b3d39ebd000404906 Mon Sep 17 00:00:00 2001 From: m00lecule Date: Mon, 17 Nov 2025 17:50:27 +0100 Subject: [PATCH 3/4] fix(docs/ROADMAP.md): highlighted sections --- docs/ROADMAP.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index af5036d..74aa554 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -1,8 +1,10 @@ # High-level roadmap overview -* execute HyperFlow job based on an LLM prompt processed by Montage MCP Server +This document contains a brief `montage-mcp-server` roadmap -The final goal is to perform the following test case: +## HyperFlow task execution using Montage MCP Server + +The project top level goal is to sucessfully finish following test case: - user prompts LLM about astronomical image mosaic - LLM passes the question to Montage MCP Server - Montage prepares a workflow definition @@ -10,7 +12,7 @@ The final goal is to perform the following test case: - user monitors the execution progress - the user gets the requested astronomical image mosaic -* architecture design +## architecture design The objective is to define the Montage MCP Server and HyperFlow communication. @@ -18,10 +20,10 @@ Currently there are two options: - design a solution using two MCP servers: the Montage and one supporting Kubernetes - the LLM prepares kubectl or helm commands to execute HyperFlow task -* assess the Kubernetes MCP servers maturity +## assess the Kubernetes MCP servers maturity The goal is to investigate the capabilities of the Kubernetes MCP server. The objective is to determine whether it is capable of creating a HyperFlow task. -* HyperFlow task monitoring +## HyperFlow task status monitoring The objective is to inform the LLM of the task calculation status. From edb492f84fe880c399da1a60c3ca81d74d9bf41e Mon Sep 17 00:00:00 2001 From: m00lecule Date: Mon, 17 Nov 2025 17:59:44 +0100 Subject: [PATCH 4/4] fix(ROADMAP.md): adjusted document structure --- docs/ROADMAP.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index 74aa554..af3f690 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -1,10 +1,10 @@ # High-level roadmap overview -This document contains a brief `montage-mcp-server` roadmap +*Abstract of the `montage-mcp-server` project roadmap* -## HyperFlow task execution using Montage MCP Server +The project top level goal is to **sucessfully finish HyperFlow task execution using Montage MCP Server integrated with an external LLM**. -The project top level goal is to sucessfully finish following test case: +Expected sequence of actions: - user prompts LLM about astronomical image mosaic - LLM passes the question to Montage MCP Server - Montage prepares a workflow definition @@ -12,18 +12,20 @@ The project top level goal is to sucessfully finish following test case: - user monitors the execution progress - the user gets the requested astronomical image mosaic -## architecture design +## Short term goals -The objective is to define the Montage MCP Server and HyperFlow communication. +### solution architecture design -Currently there are two options: +The objective is to define the Montage MCP Server and HyperFlow communication architecture. + +Options: - design a solution using two MCP servers: the Montage and one supporting Kubernetes - the LLM prepares kubectl or helm commands to execute HyperFlow task -## assess the Kubernetes MCP servers maturity +### assess the Kubernetes MCP servers maturity The goal is to investigate the capabilities of the Kubernetes MCP server. The objective is to determine whether it is capable of creating a HyperFlow task. -## HyperFlow task status monitoring +### HyperFlow task status monitoring The objective is to inform the LLM of the task calculation status.