Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#246 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, tex
Área
devops, networking

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C
Estrellas
10
Forks
8
Merge medio
21 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FriendsofECCE/ECCE

Todos los issues de FriendsofECCE/ECCE

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.