Skip to content

Commit c383d02

Browse files
committed
fix(docs/ROADMAP.md): applied requested changes
1 parent 9324d28 commit c383d02

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

docs/ROADMAP.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,27 @@
11
# High-level roadmap overview
22

3-
* execute HyperFlow job based on LLM prompt processed by Montage MCP server
3+
* execute HyperFlow job based on an LLM prompt processed by Montage MCP Server
44

5-
This final goal is to perform following test case:
5+
The final goal is to perform the following test case:
66
- user prompts LLM about astronomical image mosaic
77
- LLM passes the question to Montage MCP Server
8-
- Montage prepares workflow definition
9-
- LLM schedules workflow execution on HyperFlow (using Montage or 3rd party Kubernetes MCP server)
10-
- users gets the requested astronomical image mosaic
8+
- Montage prepares a workflow definition
9+
- LLM schedules workflow execution on HyperFlow (LLM native kubectl support or 3rd party Kubernetes MCP server)
10+
- user monitors the execution progress
11+
- the user gets the requested astronomical image mosaic
1112

1213
* architecture design
1314

14-
The objective is to conclude the Montage MCP server and HyperFlow communication.
15+
The objective is to define the Montage MCP Server and HyperFlow communication.
1516

1617
Currently there are two options:
17-
- implement the HyperFlow tasks execution in Montage MCP server
18-
- design a solution using two MCP servers: Montage and one supporting Kubernetes
18+
- design a solution using two MCP servers: the Montage and one supporting Kubernetes
19+
- allow the LLM to prepare kubectl or helm commands to execute HyperFlow task
1920

2021
* assess the Kubernetes MCP servers maturity
2122

22-
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.
23+
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.
2324

2425
* HyperFlow task monitoring
2526

26-
The objective is to inform the LLM the task calculation status.
27+
The objective is to inform the LLM of the task calculation status.

0 commit comments

Comments
 (0)