Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Local broker with a remote data server (cloud/VM data server deployment)

未關閉
#246 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
12/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
c, tex
領域
devops, networking

研究方向

This is a design question, so start by reading the Deployment modes section of GETTING_STARTED to see how the three modes are wired. The open items are which broker topics must be shared between users in mode 2, whether any server-side code publishes to the broker, and how eccejobstore/eccejobmonitor behave when the client is closed. Done means a written decision on those points and a proposed selection option, not code.

由索引模型根據 Issue 內容生成。

描述

Summary

Allow a client to use a per-user local broker together with a remote data server, with jobs running on registered remote machines.

Current state

There are three deployment modes (GETTING_STARTED, "Deployment modes"):

  1. local: per-user broker on a Unix socket, local data (FileEDSI);
  2. central server (-remote): the server's broker (TCP 8088) and its data server;
  3. shared system broker.

There is no way to combine a local broker with a remote data server.

Motivation

A small group can run a data server on a rented cloud VM or a campus virtual server. Keeping the broker on the client means:

  • one fewer port open on the server;
  • broker passwords never leave the client;
  • the server needs only the HTTP(S) data server.

Compute on the same or another host is a registered machine, as today.

To establish

  • Which messages in mode 2 require a broker shared between users? Machine-registration change notices are one. Do any others exist, or are all topics per user (ecce/<user>/)?
  • Does anything server-side (data server, scripts) publish to the broker? If so, it has no path to a client-local broker.
  • Job monitoring: eccejobstore/eccejobmonitor run on the client and reach the compute host over ssh. With the client closed, monitoring pauses and resumes on the next start. Document this. Whether a server-side monitor is wanted is a separate question.
  • How it is selected: an option of "Connect to a server", or a site/user setting. The first-start question should not gain a third choice unless needed.

Constraint

Mode 2 (central server with its broker) stays supported unchanged.

主要語言
C
星號
10
分支
8
平均合併
2 小時 7 分鐘
30 天內合併 PR
4

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。