Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions doc/source/locale/de/LC_MESSAGES/user_guide/index.po
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ msgstr "Benutzerhandbuch"
msgid "Model usage"
msgstr "Modellnutzung"

#: ../../source/user_guide/index.rst
msgid "Deployment"
msgstr "Bereitstellung"

#: ../../source/user_guide/index.rst
msgid "Operations and security"
msgstr "Betrieb und Sicherheit"
Expand Down
185 changes: 185 additions & 0 deletions doc/source/locale/de/LC_MESSAGES/user_guide/using_docker_swarm.po
Original file line number Diff line number Diff line change
@@ -0,0 +1,185 @@
# Copyright (C) 2026, XINFERENCE HOLDINGS PTE. LTD.
# Distributed under the same license as Xinference.
msgid ""
msgstr ""
"Project-Id-Version: Xinference\n"
"Report-Msgid-Bugs-To: https://github.com/xorbitsai/inference/issues\n"
"POT-Creation-Date: 2026-10-04 00:00+0800\n"
"PO-Revision-Date: 2026-10-04 00:00+0800\n"
"Last-Translator: Xinference contributors\n"
"Language-Team: de\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

msgid "Docker Swarm: Deployment Considerations"
msgstr "Docker Swarm: Überlegungen zur Bereitstellung"

msgid ""
"This is a community experience report and architecture discussion, not a "
"ready-to-run deployment guide. The contributor tested Xinference 2.2.0 with "
"Docker 29.2.1, Ubuntu 22.04 and NVIDIA driver 570 on three machines, each "
"with one NVIDIA L20. Xinference 3.x has not been validated in this Swarm "
"setup."
msgstr ""
"Dies ist ein Erfahrungsbericht aus der Community mit einer "
"Architekturdiskussion, keine direkt ausführbare Bereitstellungsanleitung. "
"Der Beitragende testete Xinference 2.2.0 mit Docker 29.2.1, Ubuntu 22.04 und "
"NVIDIA-Treiber 570 auf drei Rechnern mit jeweils einer NVIDIA L20. "
"Xinference 3.x wurde in diesem Swarm-Aufbau nicht validiert."

msgid "Why consider Swarm?"
msgstr "Warum Swarm in Betracht ziehen?"

msgid ""
"For a small team managing a dozen or so similar GPU servers, Swarm can "
"reduce the manual work of deploying, restarting and updating containers "
"across machines. It is built into Docker Engine. This was the contributor's "
"reason for choosing it, not a rule that small clusters should always prefer "
"Swarm."
msgstr ""
"Für ein kleines Team mit etwa einem Dutzend ähnlicher GPU-Server kann Swarm "
"den manuellen Aufwand für Bereitstellung, Neustart und Aktualisierung von "
"Containern auf mehreren Rechnern reduzieren. Es ist in Docker Engine "
"integriert. Dies war der Grund für die Wahl des Beitragenden, keine "
"allgemeine Empfehlung für alle kleinen Cluster."

msgid ""
"Consider existing operational expertise, GPU management and availability "
"requirements as well as cluster size. Teams already operating Kubernetes or "
"needing its device-plugin ecosystem may prefer :ref:`using_kubernetes`."
msgstr ""
"Berücksichtigen Sie neben der Clustergröße auch Betriebserfahrung, GPU-"
"Verwaltung und Verfügbarkeitsanforderungen. Teams, die bereits Kubernetes "
"betreiben oder dessen Geräte-Plugin-Ökosystem benötigen, bevorzugen "
"möglicherweise :ref:`using_kubernetes`."

msgid "Two layers of scheduling"
msgstr "Zwei Planungsebenen"

msgid ""
"Swarm managers schedule container tasks on Docker nodes and maintain the "
"services' desired state. Managers can also run tasks. A Xinference "
"supervisor manages model placement and requests; Xinference worker processes "
"register with it and run models. The supervisor does not provision worker "
"containers: container orchestration and model serving are separate "
"responsibilities."
msgstr ""
"Swarm-Manager planen Container-Tasks auf Docker-Knoten und erhalten den "
"gewünschten Zustand der Dienste. Manager können selbst Tasks ausführen. Ein "
"Xinference-Supervisor verwaltet Modellplatzierung und Anfragen; Xinference-"
"Worker-Prozesse registrieren sich dort und führen Modelle aus. Der "
"Supervisor stellt keine Worker-Container bereit: Container-Orchestrierung "
"und Modellbereitstellung sind getrennte Aufgaben."

msgid ""
"A global Swarm service runs one task per eligible node, not one per GPU. GPU "
"reservations and placement constraints must match the intended worker "
"layout. Internal actor addresses must identify reachable individual "
"processes; a load-balanced service address is not a substitute for each "
"worker's address."
msgstr ""
"Ein globaler Swarm-Dienst führt einen Task pro geeignetem Knoten aus, nicht "
"pro GPU. GPU-Reservierungen und Platzierungsbedingungen müssen zur "
"vorgesehenen Worker-Anordnung passen. Interne Actor-Adressen müssen "
"erreichbare einzelne Prozesse identifizieren; eine lastverteilte "
"Dienstadresse ersetzt nicht die Adresse jedes Workers."

msgid "GPU management"
msgstr "GPU-Verwaltung"

msgid ""
"Swarm generic resources are manually advertised scheduling resources, not "
"automatic GPU discovery or health monitoring. With the resource kind "
"``NVIDIA-GPU``, Swarm exports allocated UUIDs through "
"``DOCKER_RESOURCE_NVIDIA-GPU``. NVIDIA runtime configuration must read that "
"same variable: ``swarm-resource = \"DOCKER_RESOURCE_NVIDIA-GPU\"``. "
"Scheduling reservations alone do not enforce GPU visibility."
msgstr ""
"Generische Swarm-Ressourcen sind manuell deklarierte Planungsressourcen, "
"keine automatische GPU-Erkennung oder Zustandsüberwachung. Beim "
"Ressourcentyp ``NVIDIA-GPU`` exportiert Swarm zugewiesene UUIDs über "
"``DOCKER_RESOURCE_NVIDIA-GPU``. Die NVIDIA-Runtime muss dieselbe Variable "
"lesen: ``swarm-resource = \"DOCKER_RESOURCE_NVIDIA-GPU\"``. Reservierungen "
"allein erzwingen keine Einschränkung der GPU-Sichtbarkeit."

msgid ""
"Operators must keep advertised GPU UUIDs current and handle failed GPUs. "
"This manual work was acceptable for the contributor's stable, homogeneous "
"machines, but it is an important trade-off when hardware changes frequently. "
"See the `NVIDIA runtime implementation <https://github.com/NVIDIA/nvidia-"
"container-toolkit/blob/main/cmd/nvidia-container-runtime-hook/"
"hook_config.go>`_ for how the configured variable is selected."
msgstr ""
"Betreiber müssen die deklarierten GPU-UUIDs aktuell halten und ausgefallene "
"GPUs behandeln. Für die stabilen, homogenen Rechner des Beitragenden war "
"dieser manuelle Aufwand akzeptabel; bei häufig wechselnder Hardware ist er "
"jedoch ein wichtiger Kompromiss. Die Auswahl der konfigurierten Variable "
"zeigt die `NVIDIA-Runtime-Implementierung <https://github.com/NVIDIA/nvidia-"
"container-toolkit/blob/main/cmd/nvidia-container-runtime-hook/"
"hook_config.go>`_."

msgid "Persistence and recovery"
msgstr "Persistenz und Wiederherstellung"

msgid ""
"In current Xinference, disabling authentication does not make the supervisor "
"stateless. Its default ``XINFERENCE_HOME`` contains launch history "
"(including autostart configuration), monitoring configuration and system "
"settings. Persist this state; persist authentication data and keys too when "
"authentication is enabled. Environment variables for download settings do "
"not replace these databases."
msgstr ""
"Im aktuellen Xinference wird der Supervisor durch das Abschalten der "
"Authentifizierung nicht zustandslos. Sein standardmäßiges "
"``XINFERENCE_HOME`` enthält den Startverlauf (einschließlich Autostart-"
"Konfiguration), Überwachungskonfiguration und Systemeinstellungen. Speichern "
"Sie diesen Zustand dauerhaft; bei aktivierter Authentifizierung auch "
"Authentifizierungsdaten und Schlüssel. Umgebungsvariablen für Download-"
"Einstellungen ersetzen diese Datenbanken nicht."

msgid ""
"A host bind mount stays on that host. Use placement on the specific storage "
"host, or suitable durable storage available after rescheduling. A manager-"
"role constraint alone does not select a unique host in a multi-manager "
"cluster. Persist worker caches and engine environments separately."
msgstr ""
"Die Daten eines Host-Bind-Mounts bleiben auf diesem Host. Binden Sie die "
"Platzierung an den konkreten Speicherhost oder nutzen Sie geeigneten "
"dauerhaften Speicher, der nach einer Neuplatzierung erreichbar bleibt. Eine "
"reine Manager-Rollenbedingung wählt in einem Cluster mit mehreren Managern "
"keinen eindeutigen Host. Worker-Caches und Engine-Umgebungen sind separat zu "
"persistieren."

msgid ""
"Swarm can replace failed containers, but that does not establish Xinference "
"model recovery or uninterrupted service. Test worker reconnection and model "
"recovery for the chosen release. A single-manager Swarm cannot reschedule "
"tasks while that manager is unavailable; surviving tasks can continue "
"running. See `Swarm administration <https://docs.docker.com/engine/swarm/"
"admin_guide/>`_."
msgstr ""
"Swarm kann ausgefallene Container ersetzen, garantiert damit aber weder die "
"Wiederherstellung von Xinference-Modellen noch einen unterbrechungsfreien "
"Dienst. Testen Sie Worker-Wiederverbindung und Modellwiederherstellung für "
"die gewählte Version. Bei nur einem Manager kann Swarm während dessen "
"Ausfall keine Tasks neu platzieren; verbleibende Tasks können weiterlaufen. "
"Siehe `Swarm-Verwaltung <https://docs.docker.com/engine/swarm/admin_guide/"
">`_."

msgid "Further reading"
msgstr "Weiterführende Informationen"

msgid ""
"See `Swarm concepts <https://docs.docker.com/engine/swarm/key-concepts/>`_ "
"for the orchestration model, :ref:`using_docker_compose` for the existing "
"Compose setup, and :doc:`/getting_started/migration_3_0` for Xinference 3.x changes. A "
"complete Swarm configuration and current-version cluster validation are "
"outside the scope of this report."
msgstr ""
"Siehe `Swarm-Konzepte <https://docs.docker.com/engine/swarm/key-concepts/>`_ "
"zum Orchestrierungsmodell, :ref:`using_docker_compose` zur vorhandenen "
"Compose-Konfiguration und :doc:`/getting_started/migration_3_0` zu Änderungen in Xinference "
"3.x. Eine vollständige Swarm-Konfiguration und Cluster-Validierung der "
"aktuellen Version liegen außerhalb dieses Berichts."
4 changes: 4 additions & 0 deletions doc/source/locale/es/LC_MESSAGES/user_guide/index.po
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,10 @@ msgstr "GUÍA DEL USUARIO"
msgid "Model usage"
msgstr "Uso de modelos"

#: ../../source/user_guide/index.rst
msgid "Deployment"
msgstr "Despliegue"

#: ../../source/user_guide/index.rst
msgid "Operations and security"
msgstr "Operaciones y seguridad"
Expand Down
186 changes: 186 additions & 0 deletions doc/source/locale/es/LC_MESSAGES/user_guide/using_docker_swarm.po
Original file line number Diff line number Diff line change
@@ -0,0 +1,186 @@
# Copyright (C) 2026, XINFERENCE HOLDINGS PTE. LTD.
# Distributed under the same license as Xinference.
msgid ""
msgstr ""
"Project-Id-Version: Xinference\n"
"Report-Msgid-Bugs-To: https://github.com/xorbitsai/inference/issues\n"
"POT-Creation-Date: 2026-10-04 00:00+0800\n"
"PO-Revision-Date: 2026-10-04 00:00+0800\n"
"Last-Translator: Xinference contributors\n"
"Language-Team: es\n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

msgid "Docker Swarm: Deployment Considerations"
msgstr "Docker Swarm: consideraciones de despliegue"

msgid ""
"This is a community experience report and architecture discussion, not a "
"ready-to-run deployment guide. The contributor tested Xinference 2.2.0 with "
"Docker 29.2.1, Ubuntu 22.04 and NVIDIA driver 570 on three machines, each "
"with one NVIDIA L20. Xinference 3.x has not been validated in this Swarm "
"setup."
msgstr ""
"Este documento es un informe de experiencia de la comunidad y una discusión "
"de arquitectura, no una guía de despliegue lista para ejecutar. El "
"colaborador probó Xinference 2.2.0 con Docker 29.2.1, Ubuntu 22.04 y el "
"controlador NVIDIA 570 en tres máquinas, cada una con una NVIDIA L20. "
"Xinference 3.x no se ha validado en esta configuración Swarm."

msgid "Why consider Swarm?"
msgstr "¿Por qué considerar Swarm?"

msgid ""
"For a small team managing a dozen or so similar GPU servers, Swarm can "
"reduce the manual work of deploying, restarting and updating containers "
"across machines. It is built into Docker Engine. This was the contributor's "
"reason for choosing it, not a rule that small clusters should always prefer "
"Swarm."
msgstr ""
"Para un equipo pequeño que administra una docena de servidores GPU "
"similares, Swarm puede reducir el trabajo manual de desplegar, reiniciar y "
"actualizar contenedores en varias máquinas. Está integrado en Docker Engine. "
"Este fue el motivo del colaborador para elegirlo, no una regla que obligue a "
"los clústeres pequeños a preferir Swarm."

msgid ""
"Consider existing operational expertise, GPU management and availability "
"requirements as well as cluster size. Teams already operating Kubernetes or "
"needing its device-plugin ecosystem may prefer :ref:`using_kubernetes`."
msgstr ""
"Considere la experiencia operativa, la gestión de GPU y los requisitos de "
"disponibilidad además del tamaño del clúster. Los equipos que ya operan "
"Kubernetes o necesitan su ecosistema de complementos de dispositivos pueden "
"preferir :ref:`using_kubernetes`."

msgid "Two layers of scheduling"
msgstr "Dos capas de planificación"

msgid ""
"Swarm managers schedule container tasks on Docker nodes and maintain the "
"services' desired state. Managers can also run tasks. A Xinference "
"supervisor manages model placement and requests; Xinference worker processes "
"register with it and run models. The supervisor does not provision worker "
"containers: container orchestration and model serving are separate "
"responsibilities."
msgstr ""
"Los managers de Swarm asignan tareas de contenedores a nodos Docker y "
"mantienen el estado deseado de los servicios. También pueden ejecutar "
"tareas. Un supervisor de Xinference gestiona la ubicación de modelos y las "
"solicitudes; los procesos worker de Xinference se registran en él y ejecutan "
"modelos. El supervisor no crea contenedores worker: la orquestación de "
"contenedores y el servicio de modelos son responsabilidades distintas."

msgid ""
"A global Swarm service runs one task per eligible node, not one per GPU. GPU "
"reservations and placement constraints must match the intended worker "
"layout. Internal actor addresses must identify reachable individual "
"processes; a load-balanced service address is not a substitute for each "
"worker's address."
msgstr ""
"Un servicio global de Swarm ejecuta una tarea por nodo apto, no por GPU. Las "
"reservas de GPU y las restricciones de ubicación deben corresponder a la "
"distribución prevista de workers. Las direcciones internas de los actors "
"deben identificar procesos individuales accesibles; una dirección de "
"servicio con balanceo de carga no sustituye a la dirección de cada worker."

msgid "GPU management"
msgstr "Gestión de GPU"

msgid ""
"Swarm generic resources are manually advertised scheduling resources, not "
"automatic GPU discovery or health monitoring. With the resource kind "
"``NVIDIA-GPU``, Swarm exports allocated UUIDs through "
"``DOCKER_RESOURCE_NVIDIA-GPU``. NVIDIA runtime configuration must read that "
"same variable: ``swarm-resource = \"DOCKER_RESOURCE_NVIDIA-GPU\"``. "
"Scheduling reservations alone do not enforce GPU visibility."
msgstr ""
"Los recursos genéricos de Swarm se declaran manualmente para la "
"planificación; no ofrecen descubrimiento automático ni supervisión del "
"estado de las GPU. Con el tipo ``NVIDIA-GPU``, Swarm exporta los UUID "
"asignados mediante ``DOCKER_RESOURCE_NVIDIA-GPU``. El runtime de NVIDIA debe "
"leer esa misma variable: ``swarm-resource = \"DOCKER_RESOURCE_NVIDIA-"
"GPU\"``. Las reservas de planificación por sí solas no restringen la "
"visibilidad de GPU."

msgid ""
"Operators must keep advertised GPU UUIDs current and handle failed GPUs. "
"This manual work was acceptable for the contributor's stable, homogeneous "
"machines, but it is an important trade-off when hardware changes frequently. "
"See the `NVIDIA runtime implementation <https://github.com/NVIDIA/nvidia-"
"container-toolkit/blob/main/cmd/nvidia-container-runtime-hook/"
"hook_config.go>`_ for how the configured variable is selected."
msgstr ""
"Los operadores deben mantener actualizados los UUID declarados y gestionar "
"las GPU averiadas. Este trabajo manual era aceptable para las máquinas "
"estables y homogéneas del colaborador, pero es un compromiso importante "
"cuando el hardware cambia a menudo. Consulte la `implementación del runtime "
"de NVIDIA <https://github.com/NVIDIA/nvidia-container-toolkit/blob/main/cmd/"
"nvidia-container-runtime-hook/hook_config.go>`_ para conocer cómo se "
"selecciona la variable configurada."

msgid "Persistence and recovery"
msgstr "Persistencia y recuperación"

msgid ""
"In current Xinference, disabling authentication does not make the supervisor "
"stateless. Its default ``XINFERENCE_HOME`` contains launch history "
"(including autostart configuration), monitoring configuration and system "
"settings. Persist this state; persist authentication data and keys too when "
"authentication is enabled. Environment variables for download settings do "
"not replace these databases."
msgstr ""
"En Xinference actual, desactivar la autenticación no convierte al supervisor "
"en un servicio sin estado. Su ``XINFERENCE_HOME`` predeterminado contiene el "
"historial de lanzamientos (incluida la configuración de inicio automático), "
"la configuración de monitorización y los ajustes del sistema. Haga "
"persistente este estado, así como los datos de autenticación y las claves "
"cuando se active la autenticación. Las variables de entorno de descarga no "
"sustituyen estas bases de datos."

msgid ""
"A host bind mount stays on that host. Use placement on the specific storage "
"host, or suitable durable storage available after rescheduling. A manager-"
"role constraint alone does not select a unique host in a multi-manager "
"cluster. Persist worker caches and engine environments separately."
msgstr ""
"Los datos de un montaje vinculado al host permanecen en ese host. Fije la "
"ubicación al host de almacenamiento concreto o use almacenamiento duradero "
"adecuado que siga disponible tras la reubicación. Una restricción del rol "
"manager no selecciona un host único en un clúster con varios managers. Haga "
"persistentes por separado las cachés y los entornos de motores de los "
"workers."

msgid ""
"Swarm can replace failed containers, but that does not establish Xinference "
"model recovery or uninterrupted service. Test worker reconnection and model "
"recovery for the chosen release. A single-manager Swarm cannot reschedule "
"tasks while that manager is unavailable; surviving tasks can continue "
"running. See `Swarm administration <https://docs.docker.com/engine/swarm/"
"admin_guide/>`_."
msgstr ""
"Swarm puede sustituir contenedores fallidos, pero esto no garantiza la "
"recuperación de modelos de Xinference ni un servicio ininterrumpido. Pruebe "
"la reconexión de workers y la recuperación de modelos con la versión "
"elegida. Un Swarm con un solo manager no puede reubicar tareas mientras ese "
"manager no esté disponible; las tareas supervivientes pueden seguir "
"ejecutándose. Consulte la `administración de Swarm <https://docs.docker.com/"
"engine/swarm/admin_guide/>`_."

msgid "Further reading"
msgstr "Lecturas adicionales"

msgid ""
"See `Swarm concepts <https://docs.docker.com/engine/swarm/key-concepts/>`_ "
"for the orchestration model, :ref:`using_docker_compose` for the existing "
"Compose setup, and :doc:`/getting_started/migration_3_0` for Xinference 3.x changes. A "
"complete Swarm configuration and current-version cluster validation are "
"outside the scope of this report."
msgstr ""
"Consulte los `conceptos de Swarm <https://docs.docker.com/engine/swarm/key-"
"concepts/>`_ para el modelo de orquestación, :ref:`using_docker_compose` "
"para la configuración Compose existente y :doc:`/getting_started/migration_3_0` para los "
"cambios de Xinference 3.x. Una configuración Swarm completa y la validación "
"en clúster de la versión actual quedan fuera del alcance de este informe."
Loading
Loading