Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Gateways: Support self-hosted fleet and update management

オープン
  • 何か問題がありますか？
#3,373 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
22/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
docker, java, linux, raspberry-pi
領域
devops, documentation, embedded-iot, infrastructure

調査の方向性

This is a design and integration epic, not a first patch. Start from the previous OTA investigation in issue #2449 and locate how OpenRemote currently provisions and updates gateways with Balena. Compare openBalena, Hawkbit, and any other self-hosted option against the acceptance criteria (version visibility, group/individual deploy, failure recovery, x86_64 and arm64). Done means a chosen stack that plugs into the existing provisioning workflow, with operational docs; existing Balena deployments must still be accounted for.

索引モデルが issue の本文から書いたものです。

説明

Gateways

User Story

As an operator managing OpenRemote gateways, I want to centrally manage gateway software and updates using a self-hosted solution, so that gateway fleets can be maintained without depending on an external managed service.

Description

OpenRemote currently uses Balena for deploying and managing fleets of gateway devices.

For deployments that require the gateway management infrastructure to be self-hosted, we should support an alternative that provides the required fleet and update management functionality while keeping the gateway management workflow as simple as possible.

A self-hosted option can help:

  • reduce recurring costs as the number of managed gateways grows;
  • reduce dependency on third-party hosted services;
  • avoid vendor lock-in for a critical part of the gateway lifecycle;
  • support deployments where infrastructure or device-management data must remain under the operator's control;
  • improve control over availability, upgrades and long-term operation of the gateway management infrastructure.

Possible approaches include using openBalena or integrating another self-hosted solution such as Hawkbit.

Hawkbit and other OTA update solutions have previously been investigated in #2449.

Ideally, the self-hosted solution should provide similar functionality to the functionality currently used from Balena and integrate with the OpenRemote gateway provisioning workflow.

Acceptance Criteria

  • Gateway fleet and update management can be operated using a self-hosted solution.
  • Administrators can centrally see which OpenRemote version is running on each gateway.
  • Administrators can remotely deploy a selected OpenRemote version to gateways.
  • Updates can be applied to individual gateways or groups of gateways.
  • Gateway update status and failures can be monitored centrally.
  • Failed or interrupted updates can be recovered from safely.
  • Gateways with intermittent connectivity can receive updates when connectivity is restored.
  • Both Intel/AMD (x86_64) and Raspberry Pi Compute Module (arm64) gateways are supported.
  • The solution integrates with the OpenRemote gateway provisioning workflow.
  • Existing Balena-based gateway deployments and workflows are taken into account.
  • The selected solution and operational setup are documented.

Options to evaluate

  • openBalena
  • Hawkbit
  • Other suitable self-hosted solutions where needed

See #2449 for the previous investigation into Hawkbit and other firmware/OTA update solutions.

主要言語
Java
スター
1.9k
フォーク
478
30日以内にマージされた PR はありません

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

openremote/openremote のほかの issue

openremote/openremote の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。